Database Info

[Q] root question

Just got a Sensation this last Sat, my first Android phone, and am interested in rooting it. Never done this on any phone and am a little confused as many guides are for people who want to flash roms. For now, I would just like to root in order to get rid of some preinstalled apps. Is there a guide that has the minimal steps needed to just root? Also, does rooting do anything to my settings or apps that are there now?

MANTI5 said:
Just got a Sensation this last Sat, my first Android phone, and am interested in rooting it. Never done this on any phone and am a little confused as many guides are for people who want to flash roms. For now, I would just like to root in order to get rid of some preinstalled apps. Is there a guide that has the minimal steps needed to just root? Also, does rooting do anything to my settings or apps that are there now?
Click to expand...
Click to collapse
Follow steps one to three on the first post of this.. and that is it

Ok, didn't quite understand the guide here but found a video that made it easy and now I'm rooted. Will this keep me from receiving updates? When I get updates will this unroot the phone? Also, which apps are safe to remove without messing anything up?

Bump for answers.

MANTI5 said:
Ok, didn't quite understand the guide here but found a video that made it easy and now I'm rooted. Will this keep me from receiving updates? When I get updates will this unroot the phone? Also, which apps are safe to remove without messing anything up?
Click to expand...
Click to collapse
Hello and welcome to the forums.
To property receive OTA updates you need a stock recovery - that's a must! We cannot predict what HTC is going to update next so if you delete a package that is going to be updated - yeah, this may cause troubles. So deleting kinda anything as root may cause a OTA update to fail. I suggest that you buy a application that does a backup when uninstalling a package. I'm using Root Uninstaller Pro to "freeze" some apps just in case HTC releases a OTA that needs one of those disabled apps.
In case you have any other questions feel free to ask.

Jackos said:
Hello and welcome to the forums.
To property receive OTA updates you need a stock recovery - that's a must! We cannot predict what HTC is going to update next so if you delete a package that is going to be updated - yeah, this may cause troubles. So deleting kinda anything as root may cause a OTA update to fail. I suggest that you buy a application that does a backup when uninstalling a package. I'm using Root Uninstaller Pro to "freeze" some apps just in case HTC releases a OTA that needs one of those disabled apps.
In case you have any other questions feel free to ask.
Click to expand...
Click to collapse
If you are running the stock ROM you can just update OTA right? I'm not running a stock ROM so i dont have any OTA at all, but just curious...

I'm running stock rom, nothing changed except it's rooted. Are you saying I won't get any OTA updates from HTC? Would I get them if I took the phone in to a T-Mobile store, say when ICS is released or would it still not update because it's rooted?

MANTI5 said:
Ok, didn't quite understand the guide here but found a video that made it easy and now I'm rooted. Will this keep me from receiving updates? When I get updates will this unroot the phone? Also, which apps are safe to remove without messing anything up?
Click to expand...
Click to collapse
what video did you follow?

Not sure of it's exact location because I didn't bookmark it, but it was on youtube.
Anyone know the answer to my last question?

to find your answer boot into recovery on your phone, if you see it orange or blue with lots of options and on top it says CWM custom recovery, then no you will not receive OTA's, but to be honest thats ok, usually we root users get OTA leaks before its even released, expamle ICS some one is already working on ICS port so we will see ICS before even official release is even out
and if your rooted i found best way to remove bloat is to use titanium backup
back up the apps you want to remove in there and from the same app there is an option to uninstall it

Ok, got TB. Is there a list somwhere of apps that are safe to remove from the sensation? Also, when ICS is released, will putting it on my phone myself erase anything I currently have or not work at all if I start removing apps? Sorry for all the questions, this is my first smartphone.

Successful Update to MF3, and Retaining Root

First off, I am not responsible for anything that happens to your device.
Secondly, the only way I have tested this is with a FULLY STOCK, ROOTED ROM with NO SYSTEM APPS REMOVED (frozen is okay).
I was able to update my I337 to the 7/9 release of MF3 and retain root.
1. Install VooDoo OTA Root Keeper, make sure all 5 boxes are checked (may have to reinstall superuser if "Google Play" displays and grant root to the app)
2. Reboot, double check VooDoo OTA Root Keeper again has all checked boxes, then tell it to save root
3. Defrost/Enable all AT&T update apps, including AT&T Software Update, download the update through the check for software updates option in settings, and apply it.
4. Reboot, Use VooDoo OTA Root Keeper to restore root
5. Profit
props to @gokartracer5 for being the first to find this
SOME USERS WITH CUSTOM RECOVERIES, KERNELS, or DELETED SYSTEM APPS HAVE EXPERIENCED PROBLEMS.

Great news. I posted this in the other thread:
http://forum.xda-developers.com/showpost.php?p=43504854&postcount=407

The real question is, if you have working root on MF3, how to extract it so that everyone on MF3 can reroot.

I have a few questions.
1. did you have a custom recovery?
2. did you go stock before update
3. did you wipe data factory reset

WoodburyMan said:
The real question is, if you have working root on MF3, how to extract it so that everyone on MF3 can reroot.
Click to expand...
Click to collapse
scott14719 said:
Great news. I posted this in the other thread:
http://forum.xda-developers.com/showpost.php?p=43504854&postcount=407
Click to expand...
Click to collapse
..
I am guessing that Voodoo creates a file with all needed files and install locations when it is prompted to save root. If that created file can be found (temporary stored location), extracted, and then put on someone else's phone, Voodoo could theoretically reinstall root on the other phone. The file structure would need to be the same (same build / ROM) and it would only work if Voodoo doesn't give each created file a unique ID that only matches the original phone the file(s) were created on.
A better way would be to simply figure out where and how Voodoo re-injects root and then make a script that follows the same method.

Roadk1ng said:
I have a few questions.
1. did you have a custom recovery?
2. did you go stock before update
3. did you wipe data factory reset
Click to expand...
Click to collapse
At the time I was stock rooted with Xposed framwork and with Nottach's mod, no custom recovery.
I did not have to factory reset.

Maybe the key is that with VooDoo, root remains physically on the device, so there was no need to try to put it back on through an external device.
Which makes me think it may not work for a new unrooted MF3 device...
However, I am no Dev... hopefully this gives the real geniuses something to work with.

Voodoo Description from Play store page...there is also an XDA link:
"Free tool trying to protect root across manufacturer's OTA updates.
Also serves as temporary un-root (see statement)
Distributed as free of charge - no warranty. Open Source license: WTFPL.
Alternative download link: http://dl.project-voodoo.org/apps/VoodooOTARootKeeper.apk
This application makes a backup or a protected backup of your device's root.
This device must already be rooted: OTA RootKeeper doesn't have the ability to root devices.
If several conditions are matched, OTA RootKeeper will make root survive OTAs and... pretty much well anything − except /system partition formatting.
Requirement:
- /system partition as Ext2, Ext3 or Ext4
- Upgrades not formatting or overwriting completely the /system partition.
Typical systems where its perfectly effective:
- Nexus S
- Galaxy Nexus
- Every Honeycomb tablet
Typical system where the protection won't work:
- HTC Desire
- Samsung Galaxy Spica
- Samsung Galaxy S / SII
The application doesn't support original Superuser and not SuperSU for a very simple reason. The same feature OTA protection feature is already present in SuperSU.
In most case, only manufacturer's original recovery is able to install OTAs. It should not interfere with OTA update process itself.
A bonus feature is present, allowing you to un-root your device while keeping a su backup.
This way you can naively hide root until you choose to restore it via without further complications.
This nifty feature work on every rooted device.
** Temporary un-root statement **
This feature is designed for dev purposes in order to test their app with or without root.
The goal here is not to encourage stupid and unacceptable behaviors by movie or content sellers trying to prevent you to purchase or watch digital media you purchased if your device is rooted.
Vote with your dollars: Don't accept being a customer of companies restricting your freedom with defective and and inefficient technical measures.
Source code is available here:
https://github.com/project-voodoo/ota-rootkeeper-app
OTA root keeper is Open Source. Contributions, reviews and comments are welcome!
If you like this app, feel free to donate via PayPal to [email protected] & make my day in the process "
XDA Developers thread: http://forum.xda-developers.com/showthread.php?t=1241517
I posted this for several reasons.
1. The Dev said SuperSU has the same OTA protection feature built in. Has anyone simply tried it?
2. Although the Dev states that Voodoo does not inject root, he did state that it created a "protected" backup...so it still might be possible to locate that protected backup and inject it into someone else's similar device?
3. More information may be available via the XDA link.
I'm not a Developer either, but it seems something could come of this for those that are already on the MF3 firmware without root.

Active devices came with MF3 and we have a working root. Has anyone with a regular S4 on MF3 tried it?
Sent from my S4 Active

TwoStroker37 said:
Active devices came with MF3 and we have a working root. Has anyone with a regular S4 on MF3 tried it?
Sent from my S4 Active
Click to expand...
Click to collapse
Tried, discussed, and tried some more. There is a lot of info available about it in the various threads. I think the general consensus is that the exploit used in the Active Root might work on the New MF3 (non-Active) OTA, however the APK geohot put together verifies that the phone is an AT&T Active or it aborts. People have tried to contact him, but I don't think anyone has heard anything yet.

I'm on Verizon, so its not exactly the same, but I'm having a hell of a time recreating your success. My device keeps error-ing out in the middle of the update

Yeah this is the method I used yesterday. It works. One thing you have to do after is open the supersu app and install the binaries. It will give two options. Choose normal.
Sent from my SAMSUNG-SGH-I497 using xda premium

I have used Voodoo's OTA Keeper on all by devices for years and I had placed the app on my phone and "saved" my Root immediately after I got my phone. I am on Stock and had Froze all update apps so I never got the update and then when I read about update and people losing Root I posted in some thread about possible OTA Keeper use prior to update. The comments I got back was that it would not work for some technical reason. Since I am not a developer I said OK and just went on. I still not done the update and the only thing I really wanted to try in update was the new modem which I just downloaded and Flashed. Still it good to see that OTA Keeper does appear to work. I will keep watching this thread and if everyone that is the trying app and it working I may Unfreeze and get update.

gokartracer5 said:
Yeah this is the method I used yesterday. It works. One thing you have to do after is open the supersu app and install the binaries. It will give two options. Choose normal.
Sent from my SAMSUNG-SGH-I497 using xda premium
Click to expand...
Click to collapse
Yep. I mentioned you in the OP.
SGS4 non stock

If you have root on this update now, would someone be willing to try installing Goo Manager and installing a custom recovery and then flashing a Loki ROM? Now we can finally move forward a little bit at least.

I'm on step 3. Keep getting "Software update interrupted"

AmesCell said:
I'm on step 3. Keep getting "Software update interrupted"
Click to expand...
Click to collapse
Try defrosting all frozen apps first.
SGS4 non stock

I did that. Set TiB to show only frozen and it's got nothing. I tried a few reboots to be safe. This thing has no mods other than root. I use TiB to wipe the ATT updater data and still same thing.

Is anything different about this if you're using custom recovery? I'm on rooted-MDL with CWM.

someone correct me if I'm wrong, but I believe that custom recoveries won't flash OTA updates.
on my s3 I used mobile Odin for flashing firmware .tar files and ota .zip files as it would always root and inject supersu. while mobile Odin is available for the us market s4, it is NOT available for the att s4.

I have rooted my device and changed soft-key buttons, any easy way to get back stock?

Hello, i have asked many questions regarding my current state of the device but i just wanted to clarify for one more time, because if i mess something up there is no way i can fix it with my budget, the device is the most expensive thing i have, so please understand me and my repetitive questions regarding this.
So, i had completely stock 4.4.4 KitKat, then without any backups or anything i installed the Towelroot app, clicked a button and i was rooted. I didn't expect that at all, because from my past old experience, in order to root a device it needed a lot of work and flashing and stuff. I really do not know what i was thinking when i installed that app and pressed the button, but whats done is done.
So i had this rooted 4.4.4 KitKat device and i saw these first screenshots of LollyPop and its softkeys, soon after that i found an app on market called SoftKeyz RooT and i installed it, again without backups changed the look of buttons. At the time i did not really understood that i had modified system files (even though the app warned me all the time about it).
Also i installed app called SuperSU and it installed some binaries.
So, i have no backups of my softkey buttons (perhaps anyone can share them?) and i have rooted device, i have not done anything else, but as far as i understand i will not get OTA right?
Are there any easy way to fix my device without having to do hard-looking flashing instructions?
I am seeing many threads that have small zip files that are also flashable, and that can fix these issues, but i have 0 understanding about that and there are no instructions nowhere to be found.
If i get the backup files for my buttons, and install them using the SoftKeyZ root app, and then unroot my device using some app (suggestions?) will i be able to install OTA then?
Also, can i just flash lollypop from these .zip files, using my current state of my device ? https://developers.google.com/android/nexus/images

http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
That thread has instructions for getting back to stock. It is really quite easy.
The short version is that you download the zip from google, make sure fastboot works(which it should if you were able to root) and basically run the bat file.
There isn't really an easier way. You just have to read the instructions step by step.

To sum up:
In order to restore the stock navbar buttons:
• don't you see the stock buttons into SoftkeyZ app?
• you can flash system.img from the KK factory images
Lollipop factory images aren't available yet but if you want to upgrade you can use flashable zips (from vomer's or syko's threads) - clean flash recommended.
About OTA you should read this: http://forum.xda-developers.com/google-nexus-5/general/info-rooted-user-learn-to-update-t2927876
Finally you say that your N5 is the most expensible you have... so you should take better care of it (do not so something that you do not understand, backup your data on your PC/in the cloud,....)

Thank you both for answers, but when the lollypop image comes out at the google site, can i just flash that using the instructions you posted without doing anything else?

nikssims said:
Thank you both for answers, but when the lollypop image comes out at the google site, can i just flash that using the instructions you posted without doing anything else?
Click to expand...
Click to collapse
To update to LP through the factory images use the mentioned guide: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701

nikssims said:
Also i installed app called SuperSU and it installed some binaries.
Click to expand...
Click to collapse
For some reason, this made me smile.

Urgent problem with ota update 5.0

HI was downloading the new update 5.0 but it stopped and now the tablet says me "your system is updated" but with the 6.0.1.I can't restart the download now,what i have to do???

Same thing happened to me. Don't know why yet.

Same here. Where are you from?

Nvidia might have pulled it to fix something wait patiently it will come.

I had a similar problem as well. I got the notification to download the update, and when I clicked on the "Download" button in the notification, it did nothing. When I went into my settings and opened the OTA updater, it kept telling me that "Your system is up to date," even after repeatedly pressing the "Check Now" button, selecting "Clear data," rebooting, and messing with the advanced settings. I hope they fix this soon, I was really excited about this update!

Exact same issue here.

If you haven't root/twrp etc:
Download from here:
https://forum.xda-developers.com/shield-tablet/general/5-0-update-nougat-incoming-t3553612/page2 (there are two version - k1 & standard).
Paste it to internal memory, boot into recovery and apply update from zip.

Just wait a little. That's what NVIDIA calls "staggered rollout".

Just wanted to update and say that I got my OTA this morning and will apply it later this afternoon. Guess, just as suggested earlier, they staggered them. It's strange though that they actually pulled it back, but then again it might have been an issue with it.

if you have "nougat launcher apk" just delete it.

Been a while since I rooted mine and I'd prefer not to lose root. Anyone know if there's going to be a pre-rooted version available that won't require going through the whole process again? Honestly I don't recall if it was difficult or not but I know for previous phones I've had there was a rooted version of the OTA that someone would post within a day or two of the release. Made the whole update process quicker and easier.
Also, for those who have updated, how is the performance compared to Marshmallow?

My 2 cents: if the root is confirmed to work, there is no "process" per se.
D/L the root zip to the tablet, boot into recovery, flash that zip and reboot into system.
Should be within 2-3 min the whole thing.

Wayno-san said:
Been a while since I rooted mine and I'd prefer not to lose root. Anyone know if there's going to be a pre-rooted version available that won't require going through the whole process again? Honestly I don't recall if it was difficult or not but I know for previous phones I've had there was a rooted version of the OTA that someone would post within a day or two of the release. Made the whole update process quicker and easier.
Also, for those who have updated, how is the performance compared to Marshmallow?
Click to expand...
Click to collapse
Performance feels good so far. Don't know if there will be a pre-rooted version, but it's fairly simple and fast to root since your bootloader is unlocked and you'll get to keep all your data. If you want custom recovery I had to use the TWRP app after root to flash the recovery. Couldn't get it to stick using fastboot. There's a good rooting guide here:
http://nvidiashieldzone.com/shield-...ndroid-7-nougat/root-shield-tablet-k1-nougat/

pucka said:
Performance feels good so far. Don't know if there will be a pre-rooted version, but it's fairly simple and fast to root since your bootloader is unlocked and you'll get to keep all your data. If you want custom recovery I had to use the TWRP app after root to flash the recovery. Couldn't get it to stick using fastboot. There's a good rooting guide here:
http://nvidiashieldzone.com/shield-...ndroid-7-nougat/root-shield-tablet-k1-nougat/
Click to expand...
Click to collapse
Thanks for the info and the guide link. If I'm rooted can I let the update to nougat proceed and then just follow the procedure in the link? Thought I read somewhere that I need to unroot it first.

Wayno-san said:
Thanks for the info and the guide link. If I'm rooted can I let the update to nougat proceed and then just follow the procedure in the link? Thought I read somewhere that I need to unroot it first.
Click to expand...
Click to collapse
Yes you can just apply the update and there's no need to flash stock first. If you want to flash TWRP I would recommend getting root first by sideloading (like in the guide) and then using the TWRP app to flash TWRP.
I'm now rooted again with TWRP as custom recovery.

updating if rooted

My rooted moto G7 is still on stock android 9, security level 1 October 2019, build PPOS29.114-134-4. My wife has the identical Moto G7 phone, but unrooted, and I know she has received several OTA system updates since then.
My rooted phone is so far behind in updates because every non-OTA update method I've read about results in losing root. I know that regaining root is a simple thing to the experts but every time *I* attempt to root this (or any other phone) I end up getting into trouble. I don't even remember how rooting was originally done on this phone and obviously I am not doing things correctly.
Could a kind expert please give me step by step instructions suitable for a newbie on how to update the system on this rooted phone and then simply regain root?
My phone has twrp installed and I do have recent nandroid backups. If my memory is correct, I originally used twrp to root this phone but my memory may or may not be correct.
Thank you.
(To explain, the only reason I root this phone is
1) to use Titanium Backup which I've used many times to restore apps
2) for easy nandroid backups in case I mess something up
3) to hopefully install a Google free rom one day. I used lineageos on another phone but understand it still has problems on this phone)

maybeme2 said:
My rooted phone is so far behind in updates because every non-OTA update method I've read about results in losing root.
Click to expand...
Click to collapse
EVERY update of your firmware requires a new installation of Magisk.
New firmware = new boot.img => Magisk will be deinstalled

Thank you
Actually I cannot get any updates unless I unrooted first. When I tell the phone to look for updates it does and tells me I'm up-to-date. Which I'm obviously not.
So it seems something is preventing update. I assumed it's because I'm rooted. What do I need to do to receive ota updates and after updates how do I regain root?

maybeme2 said:
Thank you
Actually I cannot get any updates unless I unrooted first. When I tell the phone to look for updates it does and tells me I'm up-to-date. Which I'm obviously not.
So it seems something is preventing update. I assumed it's because I'm rooted. What do I need to do to receive ota updates and after updates how do I regain root?
Click to expand...
Click to collapse
You have to manually flash the firmware via fastboot. There're a lot of tutorials here in this forum for that.

Do It manually
https://forum.xda-developers.com/moto-g7/how-to/manually-update-g7-using-fastboot-t3917381
Just pay attention to not erase user data and it won't wipe anything

maybeme2 said:
Thank you
Actually I cannot get any updates unless I unrooted first. When I tell the phone to look for updates it does and tells me I'm up-to-date. Which I'm obviously not.
So it seems something is preventing update. I assumed it's because I'm rooted. What do I need to do to receive ota updates and after updates how do I regain root?
Click to expand...
Click to collapse
Theres a magisk module called Safety Net something-another and if you install hat module, reboot, go back to magislk-settings and towards the mid to bottom check the box that says Hide Magisk to protect from various forms of detection
Then you can reboot again or just wait awhile and you should be able to update BUT, as stated above, you'll have to reinstall magisk every update.

Thanks. It is hard to know what to believe anymore. In my searches I also read that accepting ota updates on a rooted Moto G7 will brick the phone.

maybeme2 said:
Thanks. It is hard to know what to believe anymore. In my searches I also read that accepting ota updates on a rooted Moto G7 will brick the phone.
Click to expand...
Click to collapse
Because some people also tell a lot of nonsense!
An ota.zip is a block based update process. You MUST verify the partitions before doing any changes! Otherwise it could lead to a fully damaged device.
"Hide the manager..." Thanks a lot!!
@maybeme2 flash the correct firmware to update your device.

WoKoschekk said:
Because some people also tell a lot of nonsense!
Click to expand...
Click to collapse
Very true. But .....it takes knowledge (which I am slowly acquiring) to tell the difference. And, if the person asking already had enough 'knowledge' to know it is nonsense, they would not need to search for information. A classic Catch-22 dilemma for a newbie. That's why searching for help is so dangerous.
QUOTE=WoKoschekk;82901585]An ota.zip is a block based update process. You MUST verify the partitions before doing any changes! Otherwise it could lead to a fully damaged device.[/QUOTE]
What do you mean by "a block based update process". I think I know, but it is dangerous to guess. If you have the time, could you explain?
Also, what do you mean by "verify the partitions before doing any changes!"? Verify for what? And after verifying the partitions, do what with that knowledge?
These are summary statements. Similar to "you must do the correct thing". It does not tell me what the correct thing is.
What people asking for help need is
1. Click on. ....
2. Copy. .. to. ... because. ..
etc.
3. Be sure to. ....
HTA123's answer was helpful that way.
"There are plenty of tutorials" is not helpful because some of these tutorials are incorrect and will brick your phone.
QUOTE=WoKoschekk;82901585]"Hide the manager..." Thanks a lot!!.[/QUOTE]
What do you mean by ""Hide the manager..."?

maybeme2 said:
What do you mean by "a block based update process". I think I know, but it is dangerous to guess. If you have the time, could you explain?
Also, what do you mean by "verify the partitions before doing any changes!"? Verify for what?
Click to expand...
Click to collapse
Android uses a ext4 filesystem that allocates storage space in units of "blocks". Your system partition is read only and Android will not change anything on it. So Motorola's developers know the block address of each file. Instead of replacing a updated file they replace an updated block.
But on a modified partition the block addresses may have changed for each file. While an update replaces a block with the correct address, this block could stored incorrect files/data.
block based OTA
To avoid such problems an OTA verifies your whole system. The easiest way to verify a partition is to build hashes/checksums.
Hide Magisk Manager
This option is helpful to hide root for some apps that check your device for root. But it's not for a device update/OTA.

WoKoschekk, that is very informative. Thank you so much! I've learned a lot and it explains a lot of things about ota's, and other things.
Excellent. I will copy and keep in my notes.
Thank you again.

maybeme2 said:
WoKoschekk, that is very informative. Thank you so much! I've learned a lot and it explains a lot of things about ota's, and other things.
Excellent. I will copy and keep in my notes.
Thank you again.
Click to expand...
Click to collapse
Attached you find a system log of a failed OTA update process grabbed from my Moto G6 plus. I know there are more interesting things in life than that. But it shows you what I have explained in my post before.
After trying to verify the partitions it fails due to a mismatched hash and the update process exits with a error (time: 04:34:25, somewhere in the middle of the log).