I'm new here so I'm not sure if this is the right place for this, but here goes. I've been trying to root my '19 Galaxy Tab A T290 [T290XXU3CUF8] for a couple months now on and off. I manage to get a success message from Odin when flashing TWRP but when I try to reboot into it, it goes straight back to the OEM recovery. I have the bootloader unlocked. I have read every forum and website I could find, but to no avail. I've tried different versions of Odin and the TWRP for my model. I'd imagine once I get TWRP flashed I'll be able to successfully install SuperSU. I've read to take the battery out after getting the success message from Odin but the battery isn't removable in my model. Any help would be greatly appreciated.
SuperSU doesn't root Android: it's an application which lets you manage root permissions for apps which require root access.
Android is rooted when SU-cmdlet - by whatever method - got added to Android and is system-wide accessible.
BTW: TWRP isn't needed at all to root Android.
jwoegerbauer said:
SuperSU doesn't root Android: it's an application which lets you manage root permissions for apps which require root access.
Android is rooted when SU-cmdlet - by whatever method - got added to Android and is system-wide accessible.
BTW: TWRP isn't needed at all to root Android.
Click to expand...
Click to collapse
I'm obviously not very good with Android. Do you have any suggestions for me ? From what I've read, it sounded like, among other methods, I needed to flash SuperSU via TWRP in order to get root.
Related
Hi every one,
I currently am using an LG G2 from tmobile (801 model). My device says its rooted but it doesnt have root access because I forgot to flash supersu binaries before i flashed the 4.4.2 version of the software. But now my custom recovery doesnt exist anymore.
I've tried using LG flash tools to flash back to 4.2. stock settings to start over but I am unable to do so for some reason. LG Flash tools isnt able to recognize my G2 in download mode. My computer is able to recognize my G2 when it is turned on though.
So is there anyway to flash a custom recovery without root access?
Or is there anyway to flash supersu binaries without a custom recovery using ADB?
I've tried trouble shooting with multiple threads and multiple downgrade methods but none of them are giving me any luck. I really want to flash a custom rom on my LG g2 and have the benefits of root access.
Any help would be greatly appreciated.
sai.nissankula said:
Hi every one,
I currently am using an LG G2 from tmobile (801 model). My device says its rooted but it doesnt have root access because I forgot to flash supersu binaries before i flashed the 4.4.2 version of the software. But now my custom recovery doesnt exist anymore.
I've tried using LG flash tools to flash back to 4.2. stock settings to start over but I am unable to do so for some reason. LG Flash tools isnt able to recognize my G2 in download mode. My computer is able to recognize my G2 when it is turned on though.
So is there anyway to flash a custom recovery without root access?
Or is there anyway to flash supersu binaries without a custom recovery using ADB?
I've tried trouble shooting with multiple threads and multiple downgrade methods but none of them are giving me any luck. I really want to flash a custom rom on my LG g2 and have the benefits of root access.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
All you need to do is install the towelroot.apk to give instant temporary root. Then install SuperSU from the dev thread here on xda or from the play store. After installing SuperSU go to its settings and select install as a system app and reboot when finished. It might take 2 attempts before it successful (it always takes me 2 tries). Then uninstall towelroot as it's no longer required since you've gained permanent root. Now install the autorec.apk and you'll install TWRP recovery. Now that you have root and recovery and have control of your device you can customise to taste. In my case I always install busybox and a terminal emulator so I can further fine tune my system.
I hope this helps
Ciao
still got issues :/
Odysseus1962 said:
All you need to do is install the towelroot.apk to give instant temporary root. Then install SuperSU from the dev thread here on xda or from the play store. After installing SuperSU go to its settings and select install as a system app and reboot when finished. It might take 2 attempts before it successful (it always takes me 2 tries). Then uninstall towelroot as it's no longer required since you've gained permanent root. Now install the autorec.apk and you'll install TWRP recovery. Now that you have root and recovery and have control of your device you can customise to taste. In my case I always install busybox and a terminal emulator so I can further fine tune my system.
I hope this helps
Ciao
Click to expand...
Click to collapse
However even when i go into supersu, it keeps saying my binaries are not up to date. So i cant install anything and I cant do anything to install a custom recovery without root access.
sai.nissankula said:
However even when i go into supersu, it keeps saying my binaries are not up to date. So i cant install anything and I cant do anything to install a custom recovery without root access.
Click to expand...
Click to collapse
So you have installed Towelroot, achieved root then having issues installing the SuperSU.apk this is indeed an issue. Towelroot should allow for it to be installed. When you install Towelroot do you get the warnings from the installer and Lookout that the package contains an exploit? Do you interrupt or stop it from fully installing when you see the warnings? The only thing I can think of is you are doing something wrong when installing towelroot which is prohibiting it from doing its job in gaining root.
I can't find a guide for dummies for it, nor any compatible automatized program or a rom created for it...
Pizzadelivefr said:
I can't find a guide for dummies for it, nor any compatible automatized program or a rom created for it...
Click to expand...
Click to collapse
Been away for a while now so can't vouch if there is a custom ROM available at this moment for your specific K2 variant. However, rooting is very possible. Simply unlocking your bootloader and booting up TWRP recovery is enough to do the job since TWRP will root the device for you. TWRP will or should detect if the device is rooted or not. If it is not then when you select to reboot your system it should ask if you would like to install SuperSU or in lamen terms, to root your device. Obviously you will say yes at this point. When the device reboots then go to the play store to update SuperSU. Once it is updated open the SuperSU app so it can update the su binary. It will ask to update the su binary either normally (by writing to your system with write permissions) or via twrp\cwm. To select the normal option you must either be S-Off or have a custom kernel specific to your K2 variant which has write protection removed. Otherwise, you must select the twrp\cwm method where it will reboot back to the custom recovery and make the change from there. Once the su binary is successfully updated then you are now properly rooted. Do not EVER flash a custom ROM unless the ROM Developer states that it is compatible for your device.
Hi, I have an HTC One M8 on 5.0.1 and I have little knowledge with rooting. I want to root my phone because there are some apps I want to use that are only capable of being used if my phone is rooted. I've tried Kingo root and it doesn't work on my phone so I was wondering if someone can give me instructions and download links so I can root my phone. If you can it would be much appreciated, thanks.
Boltz111 said:
Hi, I have an HTC One M8 on 5.0.1 and I have little knowledge with rooting. I want to root my phone because there are some apps I want to use that are only capable of being used if my phone is rooted. I've tried Kingo root and it doesn't work on my phone so I was wondering if someone can give me instructions and download links so I can root my phone. If you can it would be much appreciated, thanks.
Click to expand...
Click to collapse
You have 2 options at the moment.
1) Ship device to one of the many great people with a Java Card/XTC2 Clip - Look at the OP of this thread to see where the people are located.
2) With some time and luck - King Root, which has been proven to work for a number of M8 users.
http://forum.xda-developers.com/showpost.php?p=61920423&postcount=3652
http://forum.xda-developers.com/showpost.php?p=62161028&postcount=47
I was able to get S-Off using the KingRoot and Sunshine method. Now what? Although I did get root long enough to get S-off, I lose it after each time I get temp root with the KingRoot app again. KingRoot will say that I have root, but I can't get SuperSU to install.
I am doing a factory reset now and will try to use KingRoot to get temp root, then install SuperSU. Will I then be able to install TWRP after SuperSU is installed correctly?
Koblek said:
I was able to get S-Off using the KingRoot and Sunshine method. Now what? Although I did get root long enough to get S-off, I lose it after each time I get temp root with the KingRoot app again. KingRoot will say that I have root, but I can't get SuperSU to install.
I am doing a factory reset now and will try to use KingRoot to get temp root, then install SuperSU. Will I then be able to install TWRP after SuperSU is installed correctly?
Click to expand...
Click to collapse
If you are S-OFF, then I would flash a custom recovery and then a custom ROM (if you want)
or flash superSU in the custom recovery if you just want root.
Once S-OFF you are in full control of your device, so do some reading about it as you can end up with an expensive paperweight easily if you don't know what you're doing.
Or try vroot, i rooted my phone in just 1 tap
dexter0218, I think it would be BIG BIG news here if there were a one-click root solution for the newest M8. 5.01 phones aren't rootable easily.
boltz111, no need to fiddle with SuperSU. Now that you are S-Off, make sure you have ADB and get the latest TWRP for the M8. Drop to your ADP shell and do:
adb reboot bootloader
fastboot flash recovery twrp.zip
(sub in the name of your zip)
That's it. Then:
- Power down
- Power up in bootloader (hold down vol)
- Go to recovery
You have to go to recovery before booting or else the rom will overwrite the recovery.
Once you're in TWRP, you can load up SuperSU from a .zip and it will do its thing.
Or flash a rooted ruu from fastboot, loads you back to stock but with perm root, never had an issue
I'm using a T-Mobile Galaxy S7 SM-G930T. I rooted the phone (or so I thought) using ODIN per Max Lee's guide. I have been unable to get SuperSU to work, so I removed that and downloaded phh's Superuser from the Play Store. I have Root Checker installed which tells me phone is rooted. Whenever I try to use apps that require root access (Busybox, Titanium Backup, and Greenify), I'm told that the apps don't have root access. I can't seem to find any way to grant any apps root access with phh's Superuser, nor was I able to find a way to do so with SuperSU. I also attempted to flash stock firmware back on to my device to unroot it via ODIN, but that failed as well. I can't seem to unroot my device, nor can I utilize root capabilites. I'm stuck in some kind of limbo and I don't know where to go. Can somebody help me solve my root issues or unroot the device altogether if the first option doesn't work?
wolfpls254 said:
I'm using a T-Mobile Galaxy S7 SM-G930T. I rooted the phone (or so I thought) using ODIN per Max Lee's guide. I have been unable to get SuperSU to work, so I removed that and downloaded phh's Superuser from the Play Store. I have Root Checker installed which tells me phone is rooted. Whenever I try to use apps that require root access (Busybox, Titanium Backup, and Greenify), I'm told that the apps don't have root access. I can't seem to find any way to grant any apps root access with phh's Superuser, nor was I able to find a way to do so with SuperSU. I also attempted to flash stock firmware back on to my device to unroot it via ODIN, but that failed as well. I can't seem to unroot my device, nor can I utilize root capabilites. I'm stuck in some kind of limbo and I don't know where to go. Can somebody help me solve my root issues or unroot the device altogether if the first option doesn't work?
Click to expand...
Click to collapse
What version of Android are you on? From what I remember Max Lee had an outdated engboot.
---------- Post added at 04:43 PM ---------- Previous post was at 04:40 PM ----------
If you are on nougat download and use the adb root files in this thread https://forum.xda-developers.com/tmobile-galaxy-s7/development/rom-t3636434
Inside the adb root folder there should be an updated eng boot that you can flash through Odin.
I have been reading more articles about getting root access on an Android device and am finding the information to be contradictary. It might be the way I am reading it but when it says
"How To Install TWRP Custom Recovery On Any Android Phone (Without Root)"
I assume it actually means any Android, but it requires a custom recovery image for a particular phone so therefore it can only be for an android device where a custom image is available.
When I was running android 5.1 I installed TWRP so as to backup and restore my phone in case things went wrong, now I am running Android 7 it seems I cannot get a version of TWRP.
Can anyone assist as to what recovery tools I could install on a Ruggex 2 phone running android 7 please
thanks Roy
recovery is "independent" from main android OS. if you already have custom recovery installed on your device, it will even work without any OS installed, so it doesn't care if your phone is running Lollipop or Nougat. you can however check download source for newer version
If that is the case then why does the forum state
How to install TWRP on any Android device
but then goes on to say
Downloading TWRP for your device
which implies it is device dependant and not generic?
thanks Roy
Thx, I got it first time. of course custom recovery is device dependant. but that's not what I said. I said recovery mode is independent from android version. (at least till < 11)
btw it's not contradictory to say the Installation is generic for "any" android device (despites the difference device has recovery in partition or in ramdisk) while the Download is device dependant.
also take note that installing custom recovery and rooting android are two different tasks that do not depend on each other.
I think I am just getting more confused the deeper I go, it was fairly easy on my Android 5.1 device but with Android 7 it just seems to fight at every corner. I just cannot install and access TWRP on my device which is important for so many task.
what exactly is the problem?
I am trying to get root access on my Ruggex Rhino device, I had it all working when it was running Android 5.1 but the OS had to be upgraded to Android 6 or above for the new program to work, it is now on Android 7 .
I tryed the original method using King root but that fails to root and having read these forums it appears the way forward is to use Magisk rather than super user but that is another issue. This device on Android 7 does not have any recovery mode, power button and volume up just states no command and not sure if this is anything to do with my problems.
My ideal end goal would be a device running just the one navigation program and all the rest gone including phone module but have been told that is not possible so have to live with the bloated.
Roy
So you are the one who is confusing different things.
King root is so called one-click rooting app that tries to find exploit in its online database and provides root. This method is outdated, you can read more about here
https://android.stackexchange.com/questions/205706
the only one-click rooting app still working I am aware of is mtk-easy-su based on mtk-su exploit and magisk.
the "no command" screen is part of your stock recovery. this indicates your custom recovery has been replaced by stock recovery. read about "no command" screen here
https://android.stackexchange.com/questions/155705
installing custom recovery on android devices will break boot chain of trust. device will boot-loop and deny booting. therefore android will restore stock recovery on each boot, unless you disabled that feature.
read about dm-verity and stock recovery failsafe here
https://android.stackexchange.com/questions/214902
systemless-root is the root method available with SuperSU or Magisk, where system partition no longer is modified (to keep it healthy for updates). instead, the boot partition is modified, that requires bootloader to be unlocked (most devices).
bootloader unlocking will factory reset your device. some older devices allow installing custom recovery on locked bootloader, but you need to find a way to flash it.
Thats good information, move on away from Kingroot due to obsolescence and look into systemless root which from what I have gathered so far is not detected by the system. I will initially look into SuperSu as that was running on Android 5.1, I remember it used to ask for permision to access root and so far Magisk has just taken me round in circles. But first I will look at those articles and see what I can learn.
thanks Roy
actually, rooting with SuperSU is done by flashing SuperSU zip from TWRP. I couldn't find TWRP for your device, but we can help you porting generic TWRP for your device.
rooting with Magisk is done without TWRP
- unlock bootloader (+ factory reset)
- install Magisk apk
- patch boot.img with Magisk app
- flash patched boot.img
(see Installation Instructions)