I have two Verizon Samsung Galaxy Note 3 phones, SM-N900V. One has Android version 5.0 and I haven't been able to root that one. The other one has Android version 4.3, and I was able to root it from Windows using mobilego_setup_full818.exe.
Now that the second phone is rooted, I get daily unidentified popups, presumably from Verizon, asking me to let it update the phone. It doesn't say what it's going to update; I guess it's the Android version. My only choices are to let it happen, or postpone it; no option to refuse it permanently.
So question: If I let it update, will it undo my root? I'm worried that if it updates Android and I lose the rooting, I won't be able to root it again, like with the other phone.
On one hand I'd like to update the Android system because the current older one is preventing me from installing some apps, like Wells Fargo Banking, and Pokemon Go. On the other hand, I really want to keep the root, because I rely on it for using my phone as a wifi spot for my laptop, blocking ads, using Titanium Backup, etc.
Advice?
You can unlock the bootloader now, so updating, installing custom recoveries and root are no longer an issue:
http://forum.xda-developers.com/ver...l/official-note-3-verizon-bootloader-t3359370
Don't update over the air though. Update via Odin, then unlock bootloader, install TWRP, and flash SuperSU zip. Make sure to back everything up to a safe place.
Thanks; I'll check this stuff out.
Related
Intro: I'm on the official Jelly Bean update, and by updating lost the root I had on ICS. I was one of the unfortunate users that backed up with an older version of Voodoo OTA RootKeeper, before the program updated to account for the JB changes, so my root got wiped even though it was backed up. Well I'm tired of sitting around waiting for exploits, and I treat my tablet with care anyways, so I figure it's finally time to take the plunge and unlock so I can root the thing, right?
Plan: According to this thread, I should run the unlock tool and then flash TWRP, after that I'll be free to flash custom updates and/or replace the whole OS/ROM.
Question: Do I really need to change ROMs in order to root? I've read vague mentions of flashing a zip with the su executable and such, if that works for an unlocked TF201 with the stock JB ROM, that'd save me a lot of trouble of backing up my apps and all that jazz. Does anybody have any info on this?
EDIT: Okay, it seems I can't do it right now. I'm currently getting network access via bluetooth tethering (pdanet app), but the unlock tool seems to explicitly demand wifi, as it tells me there's no network connection available even when I can browse just fine in the browsers and such... so this will have to wait until I can access some wifi.
I recently got s-off, updated from 1.15 to 2.06, installed abp and also flashed a no ads zip file for good measure because some ads would still get through. Everything was going great until the phone randomly froze. I held down the power button and rebooted into recovery and cleared my cache and dalvik cache, thinking that may have been the problem. Upon rebooting after that, I come to find out I've lost my root access. This is so weird. I am still s-off and have the 2222222 confirmation shown when I am in the bootloader, I still have super user installed, but when I run an app that needs root, such as adaway, it says I don't have root. I downloaded root checker and it confirmed that I didn't have root. I don't understand how this could have happened. Is there anyway to regain root? I have been having the worst luck with this phone :\
terrorist96 said:
I recently got s-off, updated from 1.15 to 2.06, installed abp and also flashed a no ads zip file for good measure because some ads would still get through. Everything was going great until the phone randomly froze. I held down the power button and rebooted into recovery and cleared my cache and dalvik cache, thinking that may have been the problem. Upon rebooting after that, I come to find out I've lost my root access. This is so weird. I am still s-off and have the 2222222 confirmation shown when I am in the bootloader, I still have super user installed, but when I run an app that needs root, such as adaway, it says I don't have root. I downloaded root checker and it confirmed that I didn't have root. I don't understand how this could have happened. Is there anyway to regain root? I have been having the worst luck with this phone :\
Click to expand...
Click to collapse
Send me a PM if you want me to help you out. You need to install a custom recovery and use that to install a rooted rom and kernel. It can be a stock rooted rom. Or mostly stock however you want to do it, I'll help you set it up and teach you some things along the way.
I can teach you all kinds of things via team viewer, it wont take long and it's a necessity for having a rooted phone in my opinion. I know it can be frustrating and over whelming but it will get better I promise.
Oh and also you don't need to worry about losing s off. It's at a much lower level than anything you've mentioned touching. So it will always be there regardless because you definitely don't want to be messing with hboots or s off type stuff.
Hey, I PMed you.
Try uninstalling superuser and installing either supersu or the other superuser.
Sent from my HTC6435LVW using xda app-developers app
I can't uninstall my Superuser unless I use Titanium Backup. I tried installing SuperSU (while still having my original Superuser installed) and the SuperSU said that "There is no SU binary installed"
terrorist96 said:
I can't uninstall my Superuser unless I use Titanium Backup. I tried installing SuperSU (while still having my original Superuser installed) and the SuperSU said that "There is no SU binary installed"
Click to expand...
Click to collapse
I got your PM. I'll pick your brain about the ideal setup for your needs and how you use the DNA via gtalk. Then we'll make a plan of attack and you can update the thread with your solutions opinions etc.
As long as your opinion of me is good. Otherwise, it's prohibited. I have a green title and seniority rules
HTC EVO CyanogenMod Cant use BEATS AUDIO
CharliesTheMan said:
Send me a PM if you want me to help you out. You need to install a custom recovery and use that to install a rooted rom and kernel. It can be a stock rooted rom. Or mostly stock however you want to do it, I'll help you set it up and teach you some things along the way.
I can teach you all kinds of things via team viewer, it wont take long and it's a necessity for having a rooted phone in my opinion. I know it can be frustrating and over whelming but it will get better I promise.
Oh and also you don't need to worry about losing s off. It's at a much lower level than anything you've mentioned touching. So it will always be there regardless because you definitely don't want to be messing with hboots or s off type stuff.
Click to expand...
Click to collapse
I need help with rooting my HTC EVO to stock or CyanogenMod. With CyanogenMod my phone will not play audio/BEATS or will not open
PLAYSTORE.
How to get root back after subsequent apps are denied root?
Over the last year, this has happened several times while having different custom roms installed. It happened several times with my Galaxy S4 and S5, and recently with my Galaxy Tab S 10.5. I have not lost root on my Nexus 7 (2013). The common denominator appears to be the Samsung devices.
Through SuperSu, I have removed root, rebooted, and installed root again with CF-Root which has not given me root access.
The only way I have been able to recover to date is to do a factory rest. It is interesting to note that I would have thought that the factory rest would take me back to the Samsung rom but in the last two time that I did this on either device, I ended up with the custom rom that I just had but without root or custom recovery.
To go back to a Samsung rom, I would think that if I started the device in download mode and did a flash with odin.
But rather than go through this, is there a reason why this happens and/or is there a way to avoid it?
Lastly, is there a true way of getting root back once it stops granting root?
cyaclone said:
How to get root back after subsequent apps are denied root?
Over the last year, this has happened several times while having different custom roms installed. It happened several times with my Galaxy S4 and S5, and recently with my Galaxy Tab S 10.5. I have not lost root on my Nexus 7 (2013). The common denominator appears to be the Samsung devices.
Through SuperSu, I have removed root, rebooted, and installed root again with CF-Root which has not given me root access.
The only way I have been able to recover to date is to do a factory rest. It is interesting to note that I would have thought that the factory rest would take me back to the Samsung rom but in the last two time that I did this on either device, I ended up with the custom rom that I just had but without root or custom recovery.
To go back to a Samsung rom, I would think that if I started the device in download mode and did a flash with odin.
But rather than go through this, is there a reason why this happens and/or is there a way to avoid it?
Lastly, is there a true way of getting root back once it stops granting root?
Click to expand...
Click to collapse
Best to post such things in your device specific forum.
This forum is for the Droid DNA.
However, gaining root is as simple as downloading the latest SuperSu zip and flashing it in recovery.
Very simple to do on any rom.
I had to send my phone back because of a defect with the power. anyways, they sent me back a refurbished S4 and i only updated it to firmware MI1, realizing i had 2 software updates available. My first thought was about rooting, because i had wanted to root my phone until i realized i had MJ7 or whatever the latest one was and wasn't fond of the ideas. My question to you guys is, should i root my S4 and stay on MI1? is there a way i can do this and bypass the warranty void in the system?
All versions are rootable, even the MK2 that came out recently. The only reason so far to stay old is for ROM loading.
I for one am totally ok with never seeing another alternate ROM again, after two years of ROMing my Galaxy Nexus and the two years before that ROMing an Incredible.
When you say ROM loading, can you elaborate? Do the benefits of rooting at this software stage outweigh the benefits of the more recent ones? are some ROMs not compatible with higher softwares? because i remember MJ7 came up as "custom" and i most importantly don't want to trip my warranty, if possible. Especially because i just got this phone and don't want them to add to the bill if they see that the warranty got tripped before they even received my original S4.
Any rooting will bring up the 'custom unlock icon.
A ROM is a completely standalone full operating system custom made by developers that know how to make them. They are usually based upon Google's Open Source Android operating system source code with customization to suit the developer. It requires the phone to be not locked down to be able to install a ROM. When the phone is not locked down, a 'Custom Recovery' can be installed. Custom recovery is needed to load a ROM into the phone. Only the originaal S4 firmware, the MDK level from back in June, can have a custom recovery.
Rooting lets you run apps requiring root, such as the popular Titanium Backup, Root Explorer, and many others.
Rooting just lets you pretty much do whatever you want within the installed OS, but just not replace the OS. As I said, all the firmware loads for the S4 to date are rootable.
JeeperDon said:
Any rooting will bring up the 'custom unlock icon.
A ROM is a completely standalone full operating system custom made by developers that know how to make them. They are usually based upon Google's Open Source Android operating system source code with customization to suit the developer. It requires the phone to be not locked down to be able to install a ROM. When the phone is not locked down, a 'Custom Recovery' can be installed. Custom recovery is needed to load a ROM into the phone. Only the originaal S4 firmware, the MDK level from back in June, can have a custom recovery.
Rooting lets you run apps requiring root, such as the popular Titanium Backup, Root Explorer, and many others.
Rooting just lets you pretty much do whatever you want within the installed OS, but just not replace the OS. As I said, all the firmware loads for the S4 to date are rootable.
Click to expand...
Click to collapse
Yeah, i just didn't want to void the warranty. I think i am going to root my s4 tonight. any suggestions?
ImportedPerfection said:
Yeah, i just didn't want to void the warranty. I think i am going to root my s4 tonight. any suggestions?
Click to expand...
Click to collapse
If sort of depends what you want to do. If you want the flexibility to run custom ROMs with Safestrap, you should stay on ME7 or MI1.
If you're on MI1 and want to root it, can you please try the rooting technique in this thread? I'm curious if it'll work on MI1.
Ok.. so.. I keep seeing people saying there is a way to root still if you are on GOC1.. but I can't find anything that says what that way is. I also see 5.1 roms for this phone, but nothing that says how to install the bootloader it requires to install them. On my old phone, a Droid X2 you had to root before you could install a bootloader before you could install a rom. I am not seeing any straight up guides on here for working with this S4.
What I really want is just a basic root, so I can uninstall all the hardcoded crapware on this phone (NFL Mobile, Trip Advisor, etc..)
Short of that I want to install CM 12.1, which is probably a better route anyway, but the page for that says you must be on so and so bootloader without telling you how to INSTALL said bootloader. I'm totally lost here, things were a bit more straight forward on that old phone.
Edit: Yeah, I think what I really want to do is install CM 12.1, but I don't even know where to start.
you can't install cm12.1 or any version of cyanogenmod. the bootloader on this device is locked, meaning no custom recovery and ROMs. there is one bootloader that is the target of an exploit called Loki (basically, boot images and recoveries have to be patched in order to work, most popular ones are) but it only works with VRUAMDK, a bootloader that shipped with the device in like July 2013 when the s4 first released.
for oc1, you can root using the kingroot desktop version. Google it
skepticmisfit said:
you can't install cm12.1 or any version of cyanogenmod. the bootloader on this device is locked, meaning no custom recovery and ROMs. there is one bootloader that is the target of an exploit called Loki (basically, boot images and recoveries have to be patched in order to work, most popular ones are) but it only works with VRUAMDK, a bootloader that shipped with the device in like July 2013 when the s4 first released.
for oc1, you can root using the kingroot desktop version. Google it
Click to expand...
Click to collapse
Kingroot doesn't work. I don't know what its saying in the orange text after I run it since its not in english, but it doesn't work.
I did some rough translations of kingroot statements here from someone's pictures using google trans. Maybe they'll help.
also, people have said that if kingroot fails the first time, uninstall, restart comp and reinstall before trying again, as the system tends to stay on even after closing the program.
p.s. probably not worth mentioning, but, remember to have USB debugging turned on.
As far as ROMs if and when you get root, you need flashfire and Stangs ROM. It's modded and debloated OC1
Try getting KingRoot desktop version 3.0 I just used it on Version I545VRUGOC1 that I did the OTA update with and got it rooted I can use Titanium Backup to remove all samsung Knox and other bloat wear.
bangdosa said:
I did some rough translations of kingroot statements here from someone's pictures using google trans. Maybe they'll help.
also, people have said that if kingroot fails the first time, uninstall, restart comp and reinstall before trying again, as the system tends to stay on even after closing the program.
p.s. probably not worth mentioning, but, remember to have USB debugging turned on.
Click to expand...
Click to collapse
I gave kingroot another try since I had rebooted a couple of times since making this post, it worked this time! Huge thanks for that tip.
XxD34THxX said:
As far as ROMs if and when you get root, you need flashfire and Stangs ROM. It's modded and debloated OC1
Click to expand...
Click to collapse
Thank your for that. Flashfire is in the process of installing the rom. We'll see how it goes.
DiaSin did everything work out for you? Kingroot desktop makes me nervous. I download the desktop version and it didn't work for me so I tried to uninstall the desktop version and it wouldn't uninstall from my computer.
DallasDave said:
DiaSin did everything work out for you? Kingroot desktop makes me nervous. I download the desktop version and it didn't work for me so I tried to uninstall the desktop version and it wouldn't uninstall from my computer.
Click to expand...
Click to collapse
Just use the KingRoot app to root. It worked for me on first try.
Hey guys,
I have my tablet since one week. I love it, all works fine, Xposed offers me OBB move and so on. But now I have a question:
How can I get the new Updates for my Tablet with ROOT/TWRP?I know OTA can't be updated due to TWRP, but is there any way to flash updates dirty?! (like with LineageOS, OxygenOS, ... )
At the moment, if I try to search for new updates, I get following message:
The operating system on your device hase been modified in an unauthorised way. Try downloading softwar updates using Smart Switch on PC or visit a customer service centre.
Maybe someone got an early version of the Tab S3 with early factory Android and can give some enlightenment.
Greetz,
CM
First, this should be posted in the q&a section. You're going to have to flash the upgrade firmware tar in odin. Then re-set up your device and re-root. It's a pita. Google has gotten better at saving your apps and data, which helps, or use something like titanium backup
isn't it enough flashing stock recovery and uninstall supersu via app?
I've been away from Samsung devices for awhile, I've been using Nexus but just got a tab3. I haven't tried this but it's possible that you could flash the update.zip that would be pushed to your device using flashfire. You would probably also be able to retain root and TWRP. Maybe someone with more recent samsung use could confirm that. However, based on the message you're getting the update looks like it won't be pushed to your device. And afik samsung doesn't publish the ota, only the full firmware so someone here would have to capture the ota and post it. Whenever samsung gets around to providing an update we can play around with it and see.
PS, do you have a flashable copy of the stock recovery?