hello ive tried rooting 4.4 jcase root but end up brick i followed all his instruction but yea anyway to the point.
does anyone know how to block ota? from showing on my screen or notification?
what app do i use?
No offense, but you shouldn't be rooting if you can't figure this out. If you give search "disable OTA moto x" you'll find threads telling you what to do.
Related
hey guys, i'm currently on 4.2.2 with root (SuperSU + boot to recovery disables write protection). after rooting it, i stopped keeping up with everything, so i never did any of the updates. however, i'm at a point now where i wish to update to the latest, and i'm hoping someone can help me with the steps i need to take to do that. i think i need to unroot and then update, but not sure how. thanks.
Here's a thread to help start you out. A little looking around and you'll find tonnes more about this. An extremely posted about topic.
http://forum.xda-developers.com/showthread.php?t=2603358
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
hmm OK is there a way to un-root without losing everything?
I'm on Verizon 4.4 never took update since no root (that I know of) woke up a few days ago and saw titanium backup said "unable to gain root access" somehow I lost it? I used jcades way with adb and gained root.. Killed WP. I downloaded root checker and said I had none.. Ideas?
Slapped my Moto
I don't know how root would go away without something on your phone changing...but best place to ask might be in the thread you got the root method from.
xpsychox said:
I'm on Verizon 4.4 never took update since no root (that I know of) woke up a few days ago and saw titanium backup said "unable to gain root access" somehow I lost it? I used jcades way with adb and gained root.. Killed WP. I downloaded root checker and said I had none.. Ideas?
Slapped my Moto
Click to expand...
Click to collapse
Sounds like you either accepted the OTA to 4.4.2, or the 4.4.2 OTA was FORCED on you. Double check your phone under Settings -> About.
With 4.4.2, the vulnerability that allowed MotoWpNoMo to disable write protection with a locked bootloader has been patched, and the ability to safely and successfully downgrade your ROM to 4.4 and below (in order to make use of MotoWpNoMo to disable write protection, and SlapyMyMoto or the like to root) has been taken away too. No new vulnerabilities have been found, nor has a replacement for MotoWpNoMo been found/created/released.
In short, if you have 4.4.2 or above on your X, and you can't unlock the booloader (like Verizon and ATT, unless you are able to make use of the Chinese web site or MiddleMan), you can't disable write protection (so any apps that need to write/save to /system, /system/bin, etc wont work even if you manage to gain root) and while PIE roots 4.4.2 it is "temporary" in that its lost every time you reboot (power off/on). NOTE: the vulnerability used is patched in 4.4.3 so PIE can't be used on 4.4.3 and above.
If by chance you are still on 4.4,I don't know why you would have lost root, but I would consider backing everything up,flashing the stock VZW 4.4 SBF, and following the SlapMyMoto/MotoWpNoMo processes from scratch. When completed find the /System/priv-app/3C_OTA.APK and rename it so your phone doesn't check for future OTA's.
I've got moto ota froze..
Slapped my Moto
xpsychox said:
I've got moto ota froze..
Slapped my Moto
Click to expand...
Click to collapse
And did you double check your version?
Yes..checked before postinf
Slapped my Moto
Screen shot that I just took
Slapped my Moto
xpsychox said:
Screen shot that I just took
Slapped my Moto
Click to expand...
Click to collapse
And you never flashed 4.4.2 and downgraded to 4.4, right?
Yes..I used the jcase method by adb shell before someone made a tool.. With slapmymoto etc.like in said wokebup one day (about a week ago?) And said no more root?
Slapped my Moto
xpsychox said:
Yes..I used the jcase method by adb shell before someone made a tool.. With slapmymoto etc.like in said wokebup one day (about a week ago?) And said no more root?
Slapped my Moto
Click to expand...
Click to collapse
I have no idea then. The only times I've seen root lost is those where update was forced on them. And the only time I've seen root lost when using SlapMyMoto/MotoWPNoMO on reboot was one or two who had 4.4.2 and did a partial down grade to 4.4 and tried Slap/WpNoMo.
When I get home I'll have to try and re root...
Slapped my Moto
I just noticed something strange as I was checking my root and updates status, system updates is now at the bottom of the menu .. used to be top. I rooted with slap and than renamed the 3c_ota.apk and .odex files and I force a system update check and it fails.. so im still good on root but dont know how the menu has changed on my phone. I dont freeze anything dont have titanium thing installed..
This is weird...lol
Slapped my Moto
so i've decided to go ahead and try to re root my moto x. I'm following the instructions i did last time, the slapmymoto (don't need to do motowpnomo cuz i did check the WP, i have 0), pushed rockmymoto but i can't get cydia impactor to connect, keeps saying "signature bugs unavailable" and if i click "usb" drop down and say "scan for device" it say "no device" ideas?
xpsychox said:
so i've decided to go ahead and try to re root my moto x. I'm following the instructions i did last time, the slapmymoto (don't need to do motowpnomo cuz i did check the WP, i have 0), pushed rockmymoto but i can't get cydia impactor to connect, keeps saying "signature bugs unavailable" and if i click "usb" drop down and say "scan for device" it say "no device" ideas?
Click to expand...
Click to collapse
Straight from jcase's slapmymoto thread: "This is a "root path" for the 4.4 update, and in this case you will retain your stock recovery so features like remote wipe will continue to work. It requires you downgrading to 4.2.2 or already be on 4.2.2 before updating to 4.4."
Your screenshot shows that you are running 4.4. Additionally, you start off saying you followed instructions for slapmymoto, then you reference rockmymoto... Which one are you using? Or are you using both?
Additionally, you need to be VERY careful if you downgrade. Follow jcase's instructions exactly. There is a big risk of bricking if you make even one innocent mistake.
Please advise...
samwathegreat said:
Straight from jcase's slapmymoto thread: "This is a "root path" for the 4.4 update, and in this case you will retain your stock recovery so features like remote wipe will continue to work. It requires you downgrading to 4.2.2 or already be on 4.2.2 before updating to 4.4."
Your screenshot shows that you are running 4.4. Additionally, you start off saying you followed instructions for slapmymoto, then you reference rockmymoto... Which one are you using? Or are you using both?
Additionally, you need to be VERY careful if you downgrade. Follow jcase's instructions exactly. There is a big risk of bricking if you make even one innocent mistake.
Please advise...
Click to expand...
Click to collapse
I was pushing both BC it says to..as I said in first post I did jcases root and had then somehow lost it... So idk how/why just did.. I was hoping I didn't have to downgrade but I had a feeling... But even so it wouldn't explain why I can't use the err.. That program that starts with a c.. Only thing I can remember from last time I think I had to play with my phone setting and put it from USB to photo mode or something like that... Other thing I have thought about is now I am using a cradle point mbr95 modem/router combo. Idk if it blocks it? I know HW to downgrade to 4.2.2 u have to edit one of the lines in the script for the fxz. Done it before... Just don't understand why that program wouldn't work?
Slapped my Moto
Have you tried going into SuperSU > settings tab > unchecking and checking "enable superuser"? I know this sounds like a stupid question but sometimes stating the obvious can help narrow things down. I had this problem on my old Skyrocket before where I would suddenly lose root but be able to gain it back again simply by refreshing this setting in SuperSU.
1ad_m12 said:
Have you tried going into SuperSU > settings tab > unchecking and checking "enable superuser"? I know this sounds like a stupid question but sometimes stating the obvious can help narrow things down. I had this problem on my old Skyrocket before where I would suddenly lose root but be able to gain it back again simply by refreshing this setting in SuperSU.
Click to expand...
Click to collapse
Wtf.... Wow disabled and renamed and it worked.... Never heard if it.. Thanks!!
Slapped my Moto
xpsychox said:
Wtf.... Wow disabled and renamed and it worked.... Never heard if it.. Thanks!!
Slapped my Moto
Click to expand...
Click to collapse
:good: glad to help!
1ad_m12 said:
:good: glad to help!
Click to expand...
Click to collapse
I still can't believe that worked... Lol
Slapped my Moto
*I'm getting this out of the way first.* I know this may be a very stupid question to some of you, but I've looked on multiple threads and posts about this topic and have gotten mixed results and answers, so I thought this would be the best site to get a definitive answer.
I just got my Nexus 6 through AT&T today and wanted to root it to get rid of the very annoying AT&T splash screen you get when you turn the phone on. I know how to root and unlock the bootloader, but when I do that will I still be able to get OTA updates from Google without any fancy flashing or things like that? I'm sticking with stock Android and I'm not installing any custom ROMs. I know on a lot of other phones you can get OTA updates when rooted, but you have to install them manually. If it's too much of a hassle I just won't root it.
Thanks in advance,
Robert (Mokedoke)
It's better explained in other threads. But no, you can't take OTA. If you unlock only I believe you'll be fine. But as soon as you modify system files it won't work for OTA. Lollipop checks for these changes and the install will fail out.
You won't be able to get the OTA, but you can manually flash your phone to get the latest ROM and with out loosing data. Search the forum there directions to show you how.
hey , like the thread how to disable this nagging OTA notification im on stock rom, Rooted, and s-on. And i dont have i clue where to start i have look some other threads but i dont find that file names, can some one advice where to start?
cappone said:
hey , like the thread how to disable this nagging OTA notification im on stock rom, Rooted, and s-on. And i dont have i clue where to start i have look some other threads but i dont find that file names, can some one advice where to start?
Click to expand...
Click to collapse
Quite honestly I would someone finding a solution for the persistent notification. maybe an xposed module could get rid of that if it is ever made.
Just because of the nagging notification I updated my phone in the ugliest way possible, relocking and unlocking it and using the firmware.zip from the OTA with a TWRP backup a guy made
cappone said:
hey , like the thread how to disable this nagging OTA notification im on stock rom, Rooted, and s-on. And i dont have i clue where to start i have look some other threads but i dont find that file names, can some one advice where to start?
Click to expand...
Click to collapse
the easystes way to get rid of OTA is to update the phone.
Just flash stock recovery, reboot phone, install OTA, re-flash TWRP.
Its a pain but its done properly.
You dont need to mess with bootloader.
i was thinking about an easier way
cappone said:
i was thinking about an easier way
Click to expand...
Click to collapse
it will take you about 15 minutes including the update.
some how i manage to Block the OTA pop up in TitaniumBackUp
I found this guide to rooting[NOTE: see below]. And then I just heard the news that the Moto G6 is confirmed to get a Pie upgrade. A couple of questions:
If I want to root, should I do it ahead of the Pie upgrade? Will my rooting be preserved? Will rooting cause trouble with the upgrade?
Will the upgrade likely break the rooting method?
Thanks!
NOTE: Apparently this forum censors Droid Views links. I inserted a space in the URL so the whole thing doesn't gets *'ed. The page title is "How to Unlock Bootloader, Install TWRP and Root Moto G6" in case you just want to Google it.
Updating will not keep root and will probably break things if you have root while updating. In fact, you'll definitely not be able to install an update if you've got TWRP installed in place of stock recovery.
If you've got the patience to wait for Pie to come through, I'd say wait for it.
After the update to Pie, will the same rooting process work? Or will there be a new process?
Is the update to Pie something I have to approve or initiate? Or could I wake up in the morning and find out my phone already updated?
Thanks so much for the help!
komi_9 said:
After the update to Pie, will the same rooting process work? Or will there be a new process?
Is the update to Pie something I have to approve or initiate? Or could I wake up in the morning and find out my phone already updated?
Thanks so much for the help!
Click to expand...
Click to collapse
The same rooting process should work in theory, granted root solutions such as Magisk have been updated to support Pie.
You usually have to recieve the notification and then initiate an update on any Android phone, but I can't tell you about this one in particular because I haven't received any sort of update since I got it.
Sounds good. I am planning to update to Pie (whenever that comes), and then I'll worry about rooting. But I was worried that down the road when we get to Q that it would auto-update and break my phone because it was incompatible with TWRP or something. But so long as I have the chance to decline it, I will hopefully be good.
Root now with magisk. When p comes you can flash the magisk Uninstaller and unroot. Then after you update to p you can boot a twrp.img again and flash magisk again.
Sent from my moto g(6) plus using Tapatalk