Related
All,
Has anyone on Verizon done the OTA update and kept root? From what I've been reading, sounds like if you rooted with MotoRoot then you're okay, but not if you used PwnMyMoto.
As far as people getting a bootloop, that does make some sense because the recovery partition is really just the boot image... So I can flash the stock recovery to the recovery partition before running the update, and that should theoretically prevent a bootloop. However, if this is going to erase my root, then I don't want to do the update.
So, has anyone on verizon done the OTA and kept their root? How did you do it?
First item, this is a question so it should belong in the question and answer threads! Secondly look here http://forum.xda-developers.com/showthread.php?t=2466191
Sent on my Moto X
Sorry, and thanks! I'll probably give this a shot, make that camera work a little better...
You can always install the SafeStrap ROM here. That's what I did.
http://forum.xda-developers.com/showthread.php?t=2484908
[Rom] [VZW] SafeStrap 139.12.57
Sent from my Moto X
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
dymmeh said:
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
Click to expand...
Click to collapse
This method makes it so SafeStrap is no longer available though, right? If that's not the case then... Don't know what I've been waiting for!
Sent from my Moto X
mercado79 said:
This method makes it so SafeStrap is no longer available though, right? If that's not the case then... Don't know what I've been waiting for!
Sent from my Moto X
Click to expand...
Click to collapse
I searched around and can't really find an answer to that. I don't use SafeStrap so I have no idea. I'd assume you can try the method I posted and try using SafeStrap after. If that doesn't work then just RSD back to pre-update and hang on to SafeStrap until it's figured out. No guarantees if it'd work / break stuff, though. You'd be the guinea pig for that one.
dymmeh said:
I searched around and can't really find an answer to that. I don't use SafeStrap so I have no idea. I'd assume you can try the method I posted and try using SafeStrap after. If that doesn't work then just RSD back to pre-update and hang on to SafeStrap until it's figured out. No guarantees if it'd work / break stuff, though. You'd be the guinea pig for that one.
Click to expand...
Click to collapse
@jcase Any chance you can answer this for us? Just cause someone was able to keep root (the one shot kind you mentioned), does that mean that using RSD is still on the table?
Sent from my Moto X
mercado79 said:
@jcase Any chance you can answer this for us? Just cause someone was able to keep root (the one shot kind you mentioned), does that mean that using RSD is still on the table?
Sent from my Moto X
Click to expand...
Click to collapse
If you take the OTA you dont have wY to revert to old stock Motorola block the reverts already and @jcase already said that he will be back for root in this device till 4.3 is out
Sent from my XT1060 using Tapatalk
juancaperez2000 said:
If you take the OTA you dont have wY to revert to old stock Motorola block the reverts already and @jcase already said that he will be back for root in this device till 4.3 is out
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
That's what I thought too. Thanks.
MikeyNick said:
All,
Has anyone on Verizon done the OTA update and kept root? From what I've been reading, sounds like if you rooted with MotoRoot then you're okay, but not if you used PwnMyMoto.
As far as people getting a bootloop, that does make some sense because the recovery partition is really just the boot image... So I can flash the stock recovery to the recovery partition before running the update, and that should theoretically prevent a bootloop. However, if this is going to erase my root, then I don't want to do the update.
So, has anyone on verizon done the OTA and kept their root? How did you do it?
Click to expand...
Click to collapse
For sure have I just updated my Moto X the other day on VZW and kept root. Here is a link to the process on how to do it
http://forum.xda-developers.com/showthread.php?t=2466191
will2live said:
For sure have I just updated my Moto X the other day on VZW and kept root. Here is a link to the process on how to do it
http://forum.xda-developers.com/showthread.php?t=2466191
Click to expand...
Click to collapse
I think that's not up for debate. The issue is that even though you kept root, you're now blocked from using safestrap or ever gaining root again in the future (once another ota comes through). The update has now patched root going forward and it sounds like you won't be able to keep it after this update.
MikeyNick said:
All,
Has anyone on Verizon done the OTA update and kept root? From what I've been reading, sounds like if you rooted with MotoRoot then you're okay, but not if you used PwnMyMoto.
As far as people getting a bootloop, that does make some sense because the recovery partition is really just the boot image... So I can flash the stock recovery to the recovery partition before running the update, and that should theoretically prevent a bootloop. However, if this is going to erase my root, then I don't want to do the update.
So, has anyone on verizon done the OTA and kept their root? How did you do it?
Click to expand...
Click to collapse
mercado79 said:
I think that's not up for debate. The issue is that even though you kept root, you're now blocked from using safestrap or ever gaining root again in the future (once another ota comes through). The update has now patched root going forward and it sounds like you won't be able to keep it after this update.
Click to expand...
Click to collapse
Safestrap i know about and dont care about as i dont use it. As for moving forward with root I'll be surprised if that is the case but I wont disagree either. It is very possible they patch something to actually block root down the road. From my understanding tho currently the patch is blocking ppl to root the update not keeping root if the process is followed correctly. My guess is odds are it will be the same on the next OTA just like we had to do on the original Razr line to keep root until the bootloader was unlocked. However if the next OTA is 4.3 tha tcould all change for sure as anything is possible. Even so when that time comes I'll just unlock mine. I do have a Dev edition i just haven't unlocked with it being brand new and not wanting to void warranty yet to make sure hardware is cool but i do want root so i went the long route for now is all.
dymmeh said:
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
Click to expand...
Click to collapse
So I installed PwnMyMoto, SuperSU and OTA Root Keeper, then decided not to root. I installed the Verizon update and boom, I'm rooted. Is that what you're saying is needed? I was surprised that root apps all work fine for me, I really didn't do anything but install those apks before I installed the camera update!
boardrx182 said:
So I installed PwnMyMoto, SuperSU and OTA Root Keeper, then decided not to root. I installed the Verizon update and boom, I'm rooted. Is that what you're saying is needed? I was surprised that root apps all work fine for me, I really didn't do anything but install those apks before I installed the camera update!
Click to expand...
Click to collapse
As long as you had PwnMyMoto and never ran it / not rooted you were good to go. SuperSU could be installed before or after. I dont think OTA Root Keeper was needed at all. PwnMyMoto runs after a reboot so once you installed the OTA and rebooted it did its rooting magic automatically for you. Glad it all worked out for you
dymmeh said:
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
Click to expand...
Click to collapse
dymmeh said:
As long as you had PwnMyMoto and never ran it / not rooted you were good to go. SuperSU could be installed before or after. I dont think OTA Root Keeper was needed at all. PwnMyMoto runs after a reboot so once you installed the OTA and rebooted it did its rooting magic automatically for you. Glad it all worked out for you
Click to expand...
Click to collapse
That's awesome, didn't realize that would happen automatically. I completely expected that I'd have to complete the entire root process steps that were outlined in an earlier post if I wanted root. Thanks for the reply.
will2live said:
Safestrap i know about and dont care about as i dont use it. As for moving forward with root I'll be surprised if that is the case but I wont disagree either. It is very possible they patch something to actually block root down the road. From my understanding tho currently the patch is blocking ppl to root the update not keeping root if the process is followed correctly. My guess is odds are it will be the same on the next OTA just like we had to do on the original Razr line to keep root until the bootloader was unlocked. However if the next OTA is 4.3 tha tcould all change for sure as anything is possible. Even so when that time comes I'll just unlock mine. I do have a Dev edition i just haven't unlocked with it being brand new and not wanting to void warranty yet to make sure hardware is cool but i do want root so i went the long route for now is all.
Click to expand...
Click to collapse
people who have moto employee friends say they are moving to 4.3 next. Also, there may be a work around for you to keep root with the next release, but because people who aren't on dev phones that must be sure they can retain root would not have used this method (as it is a one chance type of method). so it is more likely that any new workarounds that people come up with will be for those that still have the ability to downgrade to original stock firmware. Also, SS is nice because it gives you the ability to run the phone just like you normally would but you can create complete backups of the device so you don't have to set everything up all over again if you screw something up with your phone. Even if you don't use SS for flashing roms it is still useful for back ups.
jayboyyyy said:
people who have moto employee friends say they are moving to 4.3 next. Also, there may be a work around for you to keep root with the next release, but because people who aren't on dev phones that must be sure they can retain root would not have used this method (as it is a one chance type of method). so it is more likely that any new workarounds that people come up with will be for those that still have the ability to downgrade to original stock firmware. Also, SS is nice because it gives you the ability to run the phone just like you normally would but you can create complete backups of the device so you don't have to set everything up all over again if you screw something up with your phone. Even if you don't use SS for flashing roms it is still useful for back ups.
Click to expand...
Click to collapse
I have my Moto contacts and yes they are moving to 4.3 next last i was told when I asked. As for downgrading stock software that isn't going to happen once updated as you can't go backwards. Moto devices have been that way going back to the original Droid Razr. Its few and far between where you could actually go backwards after an OTA. So unless you mean stock of the current build installed then ppl will have issues for sure. That said if ppl OTA and have root now but for whatever reason need to use the new fastboot file that was just posted they will in fact be SOL for gaining root. This is exactly why I refuse to buy consumer units from the carrier besides a few other reason I wont go into. My theory is simple we want to mess with device buy an unlockable one or be ready to suffer/wait for an exploit after an OTA hits.
As far as root moving forward what process you talking about tho? There is 2 ways to do it. The one posted right above your post in this thread, or the link I posted above. If the info in this thread was used yes there may be an issue because of the patch. However I will be very surprised to see ppl not be able to keep root if they updated using the process in the link I posted above. Besides having to fastboot the boot.img to recovery in that process its the same way original Droid Razr owners had to update to be able to keep root if there was no root process for the OTA being pushed. Moving forward my guess is there will be an issue once 4.3 hits tho. I'm not sure you will be able to use the old kernel from 4.2.2 to overwrite recovery and boot the 4.3 /system so you can restore root and pull the actual 4.3 boot.img so that can be used for the recovery highjack. Bottom line is only time will tell at this point as you never know what Moto/Google will do with the next update.
Agreed on SS for backups even if not flashing ROMs, but personally i just dont mess with my device enough to worry about a full back i guess. For apps/settings I just use MyBackup PRO. I've also have an app a buddy made that creates a full XML if i wanted to use it. In the old days I use to make alot of backups for ROM flashing when I used SS. Guess in my old age I've just got lazy and dont worry about it that much anymore. I really hose the device I'll just swap to one of my others til i get back to fixing the messed up one.
will2live said:
I have my Moto contacts and yes they are moving to 4.3 next last i was told when I asked. As for downgrading stock software that isn't going to happen once updated as you can't go backwards. Moto devices have been that way going back to the original Droid Razr. Its few and far between where you could actually go backwards after an OTA. So unless you mean stock of the current build installed then ppl will have issues for sure. That said if ppl OTA and have root now but for whatever reason need to use the new fastboot file that was just posted they will in fact be SOL for gaining root. This is exactly why I refuse to buy consumer units from the carrier besides a few other reason I wont go into. My theory is simple we want to mess with device buy an unlockable one or be ready to suffer/wait for an exploit after an OTA hits.
As far as root moving forward what process you talking about tho? There is 2 ways to do it. The one posted right above your post in this thread, or the link I posted above. If the info in this thread was used yes there may be an issue because of the patch. However I will be very surprised to see ppl not be able to keep root if they updated using the process in the link I posted above. Besides having to fastboot the boot.img to recovery in that process its the same way original Droid Razr owners had to update to be able to keep root if there was no root process for the OTA being pushed. Moving forward my guess is there will be an issue once 4.3 hits tho. I'm not sure you will be able to use the old kernel from 4.2.2 to overwrite recovery and boot the 4.3 /system so you can restore root and pull the actual 4.3 boot.img so that can be used for the recovery highjack. Bottom line is only time will tell at this point as you never know what Moto/Google will do with the next update.
Agreed on SS for backups even if not flashing ROMs, but personally i just dont mess with my device enough to worry about a full back i guess. For apps/settings I just use MyBackup PRO. I've also have an app a buddy made that creates a full XML if i wanted to use it. In the old days I use to make alot of backups for ROM flashing when I used SS. Guess in my old age I've just got lazy and dont worry about it that much anymore. I really hose the device I'll just swap to one of my others til i get back to fixing the messed up one.
Click to expand...
Click to collapse
3 ways to maintain root are the one in the thread, SS, and the one you posted. The one you posted actually allows you to flash the original stock firmware on the phone because the BL was never touched thus the security (keeping you from downgrading) was never installed. That was what I was referring to when I said those that must make sure they will retain root in the future would not have done the install pwnmymmoto without running then take ota then run pwnmymoto. As you said those people will be screwed if the next root requires you to flash back to original stock or use part of the pwnmymoto exploit that will only be accessible to those that got the OTA with SS or the link you posted. I don't toy with my phone as much as I used to especially this one, but bypasing exchange security is pretty essential for me. I don't want an encrypted device with mandatory pin. I never lose my phone and I would know within minutes of losing it if i ever did so I could shut it down remotely.
And I'm not sure about the new kernel situation either. This is why I wanted to make sure I could go back to original firmware as I see that being our best bet to retain root through 4.3, assuming jcase doesn't release another exploit for it to get some cash.
jayboyyyy said:
3 ways to maintain root are the one in the thread, SS, and the one you posted. The one you posted actually allows you to flash the original stock firmware on the phone because the BL was never touched thus the security (keeping you from downgrading) was never installed. That was what I was referring to when I said those that must make sure they will retain root in the future would not have done the install pwnmymmoto without running then take ota then run pwnmymoto. As you said those people will be screwed if the next root requires you to flash back to original stock or use part of the pwnmymoto exploit that will only be accessible to those that got the OTA with SS or the link you posted. I don't toy with my phone as much as I used to especially this one, but bypasing exchange security is pretty essential for me. I don't want an encrypted device with mandatory pin. I never lose my phone and I would know within minutes of losing it if i ever did so I could shut it down remotely.
And I'm not sure about the new kernel situation either. This is why I wanted to make sure I could go back to original firmware as I see that being our best bet to retain root through 4.3, assuming jcase doesn't release another exploit for it to get some cash.
Click to expand...
Click to collapse
Gotchya, makes total sense now what you are saying. I think there is just confusion at times when talking about root & OTA because of different ways to do it in a case like this device. Being a Moto guy for so long tho i'm use to all the BS they throw at us.....lol. That said that is why i posted the link I did. Imho it's a bad plan to update using the other method of installing pwnmymoto and not running it first before taking the OTA. Doing the process to protect root before updating is a much safer bet atm imo. Sure its a little more work but at the end of the day you dont have to be worried as much moving forward. Only concern I have still for doing it the longer way is if that process will work when they push out 4.3. It had alot of changes in it so lord only knows what will be up for keeping root. And really in my case its no concern but for all the folks with consumer version it is still a concern i think for the time being
[Q] Having trouble figuring out rooting & recovery works on Moto X coming from Nexus
I'm no noob, I've been rooting for a while, but I can't figure out how to root this damn thing . On a Nexus, I just unlocked, flashed TWRP, then flashed superuser from TWRP, and I was done. How does it work on this phone? Can I just flash TWRP and then from TWRP flash a root zip? I'd rather not use any toolkits and such (which seem to be all the rage on this forum). Running Pure edition btw. On latest Lollipop OTA.
mateopase said:
I'm no noob, I've been rooting for a while, but I can't figure out how to root this damn thing . On a Nexus, I just unlocked, flashed TWRP, then flashed superuser from TWRP, and I was done. How does it work on this phone? Can I just flash TWRP and then from TWRP flash a root zip? I'd rather not use any toolkits and such (which seem to be all the rage on this forum). Running Pure edition btw. On latest Lollipop OTA.
Click to expand...
Click to collapse
Yes its pretty much the same, the forums are abit immature at the moment there aernt any proper guides, i just did things the Nexus way
unlock your bootloader first through motorola, following the instructions (make sure there are no spaces in the unlock key): https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
flash twrp, then install the superSU zip from adb sideload or from your internal storage if it was already downloaded
youre done
also, you could flash the stock logo image to remove the warning boot image, http://forum.xda-developers.com/moto-x-2014/development/warning-message-unlocked-bootloader-t2871478 to make things look nicer
IINexusII said:
Yes its pretty much the same, the forums are abit immature at the moment there aernt any proper guides, i just did things the Nexus way
unlock your bootloader first through motorola, following the instructions (make sure there are no spaces in the unlock key): https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
flash twrp, then install the superSU zip from adb sideload or from your internal storage if it was already downloaded
youre done
also, you could flash the stock logo image to remove the warning boot image, http://forum.xda-developers.com/moto-x-2014/development/warning-message-unlocked-bootloader-t2871478 to make things look nicer
Click to expand...
Click to collapse
Awesome, thanks. Looks like that's what I'll end up doing. I really messed up my phone though when trying to get back to stock. Hopefully my stock image request will be approved soon and I'll be able to go through the process again.
One more question, if I kinda messed up restoring everything to 4.4.4, but I can boot the phone properly, will updating to 5.0 via an OTA update fix any mistakes I made along the way?
mateopase said:
One more question, if I kinda messed up restoring everything to 4.4.4, but I can boot the phone properly, will updating to 5.0 via an OTA update fix any mistakes I made along the way?
Click to expand...
Click to collapse
Not necessarily. The ota contains only changed files (not all files) and therefore if something is wrong with a file that wasn't changed (including anything in /data) then it will still be broken after the update.
crpalmer said:
Not necessarily. The ota contains only changed files (not all files) and therefore if something is wrong with a file that wasn't changed (including anything in /data) then it will still be broken after the update.
Click to expand...
Click to collapse
Alright. Do you know of any way to return to stock without going through Motorola's waiting game. It's been a few hours now and I still haven't been approved for the download.
mateopase said:
Alright. Do you know of any way to return to stock without going through Motorola's waiting game. It's been a few hours now and I still haven't been approved for the download.
Click to expand...
Click to collapse
Honestly, I haven't looked at what options are available for images to flash.
When I asked for firmware, I believe that I asked on a Friday evening and received access on the following Monday morning. So maybe you'll get access in another 15-16 hours? That is your safest bet if your phone is working well enough to last you until then.
OK, I've read so much that things are just getting jumbled in my brain now. There's so much information in these threads that I don't know where to start. The world of Android apparently moves too fast for me to keep up. I've got a Verizon LG G2 that is stuck on 4.4.2, software version 24A. Right after I took the OTA KK upgrade I rooted with IORoot25. I don't think I've done anything other than root, however I have somehow can create the mobile hot spot without permissions. Not sure if there was an .apk that was put on when I rooted or how I did it because it was over a year ago.
Ever since I rooted, my phone tries to push OTA updates but they are always unsuccessful. Every morning I have to hit "Install Later" becasue it tried over night and failed. Besides this being a bit annoying, I haven't been concerned becasue the only OTAs since I got 4.4.2 was supposedly some small patch that didn't really do much (from what I read). But, the other day it notified me that it wanted to push Lollipop and needless to say, I want it.
My problem: I don't know what the hell to do! Besides rooting, I'm pretty sure the only thing I've done is download Flashify and backup my stock recovery. Flashify doesn't show that I have a custom recovery, nor do I ever remember installing one. Just whatever came with the IORoot25. Oh, and it looks like I Quarantined LGSetupWizard using App Quarentine. Pretty sure that's it. So, where do I go from here?? I'm wanting to move to Lollipop, then possibly de-bloat it, and would like a custom recovery so that I can create nandroid backups and possibly start trying out other custom ROMs.
I had an OG Droid for years and would flash ROMs frequently until I upgraded to a RAZR MAXX. Once I got the MAXX, and now the LG, all I've really done is root and hack the wifi, so I'm REALLY out of the loop now! Everything seems so complicated becasue there's just too much info out there. Could somebody please guide me in the right direction to make this as smooth as possible??
Thanks for reading and helping a NooB out. Ugh...can't believe I have to start calling myself that again!!
You could 'freeze' the update so it doesn't pop up every morning. IF you want to update- you can unroot it and then take the update and re-root it and fix the hotspot thing. I'm in the same boat, I'm about to do the same myself.
caecusscius said:
You could 'freeze' the update so it doesn't pop up every morning. IF you want to update- you can unroot it and then take the update and re-root it and fix the hotspot thing. I'm in the same boat, I'm about to do the same myself.
Click to expand...
Click to collapse
Thanks for the response. Hoe do I "freeze" the update? If I do decide to take the update and re-root, and especially if I start loading custom ROMs, I know I'm going to want to do this in the future. I've been getting theses OTA update notifications everyday for months now!!
Also, what's the easiest way to unroot?
AS long as you are running stock I believe you can accept the OTA without unrooting: I haven't done it yet as I haven't had a few free hours, but I'm going to try it tonight.
there are plenty of apps that allow you to freeze apps- titanium Backup Pro is one that comes to mind.
I have a TMobile Note 4 SM-N910T. It's currently on 5.1.1 stock and I just got the OTA Marshmallow update notification. I'd like to try Marshmallow out, but if I allow the OTA update, will I be able to root it later? Or is 6.0.1 unrootable (for now)? If I root it now (before updating to MM) will I still get the OTA update? And will it still be rooted after the update? So many questions!
ota then root
I OTA'ed, now the phone randomly reboots several times a day, and some apps don't work correctly. Great.
factory reset.
*sigh* I was afraid you were going to say that. Now the problem is backing it up. I have a Titanium Backup Pro license, but I only use it on my old rooted GS2. The Note 4 is not rooted so TB won't run on it. All the rooting tutorials say "back up your phone before you root" but you need root to run TB. Chicken or egg? I guess I could try Samsung Kies, don't know if it will back up everything. My photos are backed up to Google Photos, I guess everything else is replaceable, but I would really rather not have to reinstall all my apps one by one after a factory reset.
That brings up another question: when you to go Settings/Backup and Reset, I have "Backup my data" set to On and linked to my Google account, but nowhere can I find documentation of exactly WHAT gets backed up or to WHERE (it says to "Google servers" but what the heck does that mean? I can't find it on my Google Drive or anywhere else on my Google account dashboard.)
I do greatly appreciate your help, by the way.
You could try reinstalling through kies or smart switch. Make sure to clear caches before and after. And see if that works. If it doesnt help, you could flash recovery, root, try to backup as much as you can between reboots and then factory reset. Your apps should automatically download from play store. But without the titbackup files you'll lose settings and data in a lot of apps that Google doesn't backup.
I unlocked your mum's bootloader.
kydar said:
I have a TMobile Note 4 SM-N910T. It's currently on 5.1.1 stock and I just got the OTA Marshmallow update notification. I'd like to try Marshmallow out, but if I allow the OTA update, will I be able to root it later? Or is 6.0.1 unrootable (for now)? If I root it now (before updating to MM) will I still get the OTA update? And will it still be rooted after the update? So many questions!
Click to expand...
Click to collapse
Were you able to downgrade back to 5.1.1? My phone also download the MM ota but I haven't installed it. I rooted 5.1.1 first and am trying to locate where exactly the MM ota downloaded to.
Been hearing too much about problems with MM.
Shad0wsabr3 said:
Were you able to downgrade back to 5.1.1? My phone also download the MM ota but I haven't installed it. I rooted 5.1.1 first and am trying to locate where exactly the MM ota downloaded to.
Been hearing too much about problems with MM.
Click to expand...
Click to collapse
There aren't that many problems with MM. Just superficial stuff like not having mobile data toggle. The problems you are hearing about a factory reset will fix. Like lag, jankyness, apps loading, phone freezing temporarily. You won't be able to do OTA. It will fail because of root. You need to titanium backup or whatever method you prefer of backing up data and flash through kies, odin or smart switch. Probably easier to go that route unless you only did minor things with root like just block ads, then you can probably get away with flashing stock recovery and then OTA. You still might have to factory reset like I had to even though I flashed whole rom through smart switch. If you have xposed or modified something like swapping recent apps and back key like me, then you'll need to flash marshmallow whole and start over after backing up.
Afaik, you can't downgrade to 5.1.1 unless somebody figured out a workaround or you only flashed everything except bootloader.
I unlocked your mum's bootloader.
@Shad0wsabr3, my phone gave me the choice to delay the upgrade for a while, but eventually just did it without my consent. I suppose you could download stock 5.1.1 from sammobile if you really wanted to downgrade. I just wish I could figure out how to back up my (unrooted) phone so I could then do a factory reset and see if it helps the problems I'm having.
kydar said:
@Shad0wsabr3, my phone gave me the choice to delay the upgrade for a while, but eventually just did it without my consent. I suppose you could download stock 5.1.1 from sammobile if you really wanted to downgrade. I just wish I could figure out how to back up my (unrooted) phone so I could then do a factory reset and see if it helps the problems I'm having.
Click to expand...
Click to collapse
Iv never backed up an unrooted device so I wouldn't know. Glad you nrought that up as Iv been meaning to look into that.
Would you happen to know where the downloaded ota file location is? My phone downloaded it and I keep postponing it.
Sorry, idk exactly where in the file system it is. All I can caution you again is, I kept postponing it and postponing it, and then one day the phone just popped up a message saying it was going to reboot and update, whether I liked it or not. Well, it didn't actually SAY whether I liked it or not but it did decide that I had postponed the update long enough and it was going to apply the update, giving me no option to postpone it any longer. That sort of pissed me off.
Please let me know if you come up with a backup solution. I've tried SimpleADB or whatever it is called these days, and another app that claimed to be able to back up an unrooted phone. Neither of them worked as advertised.
Where are the root instructions for completely stock 910T with MM update?
vernj123 said:
Where are the root instructions for completely stock 910T with MM update?
Click to expand...
Click to collapse
http://forum.xda-developers.com/not...overy-n910t-t3-marshmallow-pe3-guide-t3406870
kydar said:
Sorry, idk exactly where in the file system it is. All I can caution you again is, I kept postponing it and postponing it, and then one day the phone just popped up a message saying it was going to reboot and update, whether I liked it or not. Well, it didn't actually SAY whether I liked it or not but it did decide that I had postponed the update long enough and it was going to apply the update, giving me no option to postpone it any longer. That sort of pissed me off.
Please let me know if you come up with a backup solution. I've tried SimpleADB or whatever it is called these days, and another app that claimed to be able to back up an unrooted phone. Neither of them worked as advertised.
Click to expand...
Click to collapse
I'm still researching what your dealing with. As for me I found the ota file. For those looking for it this is how and where I found it....
With RomToolbox I went to root browser. Then to data folder and a folder named fota. Within the fota folder is the ota update named update.zip. I erased that and then went into Titanium Backup and chose to freeze both software update files. So far no constant reminders that I have an update ready to be installed.
Hope this may help.
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.