[Q] GT-P 7510, I can't get Root - Galaxy Tab 10.1 Q&A, Help & Troubleshooting

I've looked at several guides here, but despite following the details, I can't seem to obtain Root on my Tab.
I have got TWRP installed (via Odin) and also this Android 7.1.1 Nougat ROM, I've flashed Samsung_Galaxy_Tab_10.1_root.zip (multiple times now), but still no Root.
I must have missed something?y
Edit: I had previously obtained root using the Kingroot tool, but then read that it might not be a trustworthy tool and I uninstalled it. Could that be stopping me from getting root this time?

I gave up in the end and installed a Lollipop ROM, I do have Root with that. That said, I'm wondering if there was some other setting within the Nougat ROM that I should have enabled?

UKseagull said:
I have got TWRP installed (via Odin) and also this Android 7.1.1 Nougat ROM, I've flashed Samsung_Galaxy_Tab_10.1_root.zip (multiple times now), but still no Root.
Click to expand...
Click to collapse
Why did you even try flashing that root package? It's sooo old... Did you actually follow the steps in the OP for the 7.1.1 ROM to install either phh SuperUser, ot SuperSU? It's an extra step, along with the gapps install.

Related

[Q] Rooting Successfuly but not recognized?

Hello everyone,
I have the Galaxy S3 GT-I9300 / I9300XXUGMK6 (international version) with Android 4.3 installed (Original Samsung stock ROM). I've decided to root it and flash it with a new ROM. However, since I haven't decided which ROM yet I just want to root it for now, but I just can't manage to do it!
Here's what I did:
I have backed it up, installed all drivers, enabled dev mode and followed this thread, but it seems like I can't root the phone. I tried using Odin 3.07 and 1.85. I tried disabling "auto reboot" and pull the battery, and tried CF-Auto-Root as well.
Looks like the whole process happens exactly as described in those threads, no errors or extra steps happens, however at the end of each process, even when Odin says it's successful, I run Titanium Backup which says the phone is not rooted.
The phone works normally now, so my question is what can be the issue and how can I still root it? I've tried searching for the answer in the forum but to no avail.
Many thanks!
Try installing manually installing superSU from the play store, but cf auto root should have installed a super user app.
boomboomer said:
Try installing manually installing superSU from the play store, but cf auto root should have installed a super user app.
Click to expand...
Click to collapse
SuperSU was indeed installed during rooting, but I have re-installed it (or rather upgraded it) from the Play Store and voila, I now have root access!
Thanks a bunch! Is it something I did? Can i trust installing a new ROM to be safe?
Rooting stock rom is irrelevant to flashing a custom rom, most important is you backup your efs now and follow the instructions exactly.

Can I even root my phone? Or at least install a rooted rom? (I545VRUGOC1 Build)

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.

Flash Factory Image on Nexus 5X with TWRP Installed

I'm wanting to manually install the April 2016 update to my Nexus 5X (currently running February 2016) but due to being rooted (with SuperSU BETA 2.67) and having TWRP as my recovery. I've looked for ways of doing it and trying to be a cautious as I can (when I tried to root las time, I soft-bricked my phone for a few hours). So far the best way I've found is simply through the Google Developers page (link below) with instructions and all the files I need.
Before I go through with it however, I'm wanting to know whether TWRP will prevent the install, if there's a better method, and do I install the latest image, or the one currently installed on my device, then update? Let me know if you need more details too.
Google page:
developers.google.com/android/nexus/images#instructions
Just follow the directions on Google's page, then redo twrp and root all over again.
zelendel said:
Just follow the directions on Google's page, then redo twrp and root all over again.
Click to expand...
Click to collapse
So just to be clear, manually updating will get rid of TWRP too?
sebowow said:
I'm wanting to manually install the April 2016 update to my Nexus 5X (currently running February 2016) but due to being rooted (with SuperSU BETA 2.67) and having TWRP as my recovery. I've looked for ways of doing it and trying to be a cautious as I can (when I tried to root las time, I soft-bricked my phone for a few hours). So far the best way I've found is simply through the Google Developers page (link below) with instructions and all the files I need.
Before I go through with it however, I'm wanting to know whether TWRP will prevent the install, if there's a better method, and do I install the latest image, or the one currently installed on my device, then update? Let me know if you need more details too.
Google page:
developers.google.com/android/nexus/images#instructions
Click to expand...
Click to collapse
Look at this very good guide. It helped me very much.
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Dont be afraid to brick it. As long as you are carefully flashing the bootloader, nothing really bad can happen. It is a Nexus.
Bad news is, March brought a new bootloader. So if you dont want to fool around with the bootloader, I would recommend flashing System, recovery and boot of Febraury and then update via OTA. Have fun

[HOW TO] Install Xposed Framework on SM-G530AZ

Okay so I have not seen anything new in regards to us unfortunate enough to have the Cricket variant of the grand prime, so I decided to put together a little step by step to get xposed installed and running on this device, I think it may work on others as well, but since I have not attempted it then do not just assume it will. This guide is as stated in the sub line of the post for the SM-G530AZ running 5.1.1 Lollipop. I am not responsible if you brick or bootloop etc etc your device. So long as you can follow directions you should be fine.
1. First of all you must already have root access on your device, mine is using SUPERSU to handle root requests. If you do not have root yet then check forums for way to do so it is there already, however you must root with kingroot or manually with the same exploit that kingroot is leveraging in order to obtain it before attempting the install of xposed, otherwise it will fail.
2. You need to download the zip file attached to this post to your desktop or device and unzip it into your device sdcard.
3. Once you have extracted the apk and zip files into the sdcard you need to install the xposed installer apk so make sure you have enabled Unknown Sources from your settings/Security menu and you may get a warning from the device as well that is okay just tap okay and finish the install.
4. Now you need to download flashfire from the play store and install it as well. Open flashfire and flash the xposed-v80.0-sdk22-arm-custom-build-by-wanam-20160211.zip that you will have extracted Choose flash zip in flashfire and make sure you leave automount unchecked. You can open the xposed installer app to make sure it recognized it, which it should if you flashed it properly.
5. Now you can enjoy the Xposed Framework on your device.
I am currently attempting to learn as much as I can about the trust zone and smc as I can tell you that is the only way we are going to get custom recovery and roms on this thing sadly. I am also following someone who claims to be able to rollback android from 5.0+ to 4.0-4.4.4 via jtag which is something I too have pondered on if it was possible and honestly I think it would be, I would like to explore the possibility that their may have been more vulnerabilities within the device prior to the 5.1.1 update I currently have 5.1.1 installed which is what the device had at time of purchase for me, however some may still be running 4.4.4 if you happen to be using 4.4.4 still then I cannot say whether this guide will work or not for you I think it would but you would probably need to use a little older version of the xposed installer but I am not certain, I would probably just update to lollipop if you really want to be safe about it and the firmware has been posted on these forums as well. Please hit the thanks if this helped you out at all, and if you are confused or have an issue you can pm me and I will try my best to get back to you whenever possible. But this is how I got xposed working on my device by simply rooting with kingroot, then using the mrw script to remove kingroot and replace with supersu and enabling unknown sources. The root guide that exists for this device however stated to flash some other boot.img and I actually had issues when I did that step, so after i went back to stock again I did the root guide with kingroot and did not ever flash that other boot image and all worked fine for me.
Awesome thanks. I assume install King root then flashfire then SuperSU binary then uninstall king root. For SuperSU?
Sent from my DROID Turbo using XDA-Developers mobile app
THANK YOU THANK YOU THANK YOU! Thank you so much!!!!!! I have been trying to do this for 3 days now!!! I have soft bricked my device, restored it, got it going again, soft bricked again. Over and over. Until finally, today on my first day off all week I took the time to read your posts over again. I found this one and it finally got me there! I have the same exact phone, Cricket Samsung Galaxy Grand Prime Model SM-G530AZ. I have been struggling to find a TWRP or CWP recovery and I am pretty sure there isn't one available currently. So then I found this method and FINALLY SUCCESS!!!!! Anywhere I can donate to you?

[Fire HD 6] Downgrade to 4.5.3 to root, went back to 5.3.1 and lost TWRP

Hi guys,
first of all I want to salut everybody here as I am completely new to the Android world and that's indeed the best resource online. Thanks for that.
Now my big problem. As from the title, I downgrade my Fire HD 6 (4th gen) to 4.5.3 with adb sideload to root it with kingroot and everything went fine. I have then installed TWRP and everything went fine. I have then used TWRP to go back to 5.3.1 and I lost root and recovery. I managed to gain my root privileges back but as for the recovery not a chance. I tried to install TWRP again with dd from adb shell (as I can su) but once again nothing. Checking with fastback getval all, I do have a locked bootload:
Is this the reason why TWRP doesn't run anymore?
If yes, how can I unlock it back?
Is this what's meant with boot loader loop?
Thank you all in advance!
Edit 1:
maybe cuber.py may help but I can't find this file.
Edit 2:
ok found the tools here https://forum.xda-developers.com/kindle-fire-hdx/development/tools-create-unlock-img-fix-boot-img-t3050689
Edit 3:
I tried with cuber.py but the tool can't sign the img because it's not ANDROID. That's what it says. Now I am really stuck. Help please!
LM
I was in the exact same situation, so maybe I can offer some insight. I also have an HD 6 running 5.3.1 that I have downgraded to get root then upgraded a few times. Let me say that I am still learning too, and am by no means an expert but I can try to help.
As far as losing root, i'm not sure as that never happened to me. Did you flash the most up-to date SuperSu with TWRP or did you just answer yes when TWRP prompted you if you wanted root privileges? Flashing a SuperSu through TWRP will give you the SuperSu icon on your home screen once you upgrade back to 5.3.1, whereas just letting TWRP grant root access won't. You will still have root, but without the icon there's no direct control over it (at least not that I could find) so it's still there, just hidden.
My TWRP also replaced by the stock recovery upon updating back to 5.3.1. As far as I know, this is unavoidable. I believe it's as you suspect and is due to the 5.3.1 bootloader being locked. This would also explain why the process for rooting 5.3.1 is so involved as opposed to just using something like Kingroot. I also don't think there's anyone still doing active development on the HD 6 / HD 7.
If you really want to have both root and TWRP, you could try downgrading to an older OS that still has the feel of 5.3.1. I'm not sure about any other versions, but 5.1.1 is rootable via Kingroot (which should mean that it has an unlocked bootloader) and has the same exact UI as 5.3.1. So if you're feeling adventurous try downgrading to 4.5.3, installing TWRP, and upgrading to 5.1.1 instead of 5.3.1 (just be sure to block automatic updates!) and see if TWRP is still active. If so, root with Kingroot and you're good. If you still don't have TWRP, at least you're no worse off than you were.
If you do try this, please post your results here. I might try this myself. I am currently running stock. As I said, I went through the process a few times. For some reason SuperSu was causing erratic behavior in some of my apps and when I tried to switch my SU app to kingroot I lost root completely. I really didn't care about root enough to repeat the whole process again, but if I could keep TWRP it might be worth it. Anyway, good luck.
P.S. You may need to try rooting with Kingroot several times for it to work. I know for a fact that it can root 5.1.1 since I've done it on my own HD 6 when I was running 5.1.1. I'm not sure why it fails, but keep trying and eventually it will get root access. You may have to try 6 or 7 times but eventually it will work.
I went back and re-read this thread more carefully:https://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950 and it turns out that TWRP doesn't play well with any 5.X.X bootloaders. Oh well, I was kind of hoping my idea would work. It turns out that you can use TWRP on your current rooted 5.3.1, but only on a temporary basis. Refer to the above thread post #2 for instructions. Basically, you put the correct 5.3.1 bootloader on your device then run AutoTWRP which will flash 4.5.3 bootloaders and TWRP for you. Reboot into recovery and you have your TWRP. You can then do whatever you want. The downside is that since you are running a 4.5.3 bootloader you can't get back into your OS, only TWRP. And once you flash your 5.3.1 bootloader to get back into your OS, TWRP no longer works. I know it's a pain in the arse having to connect to a PC and run a batch file every time you need to use TWRP, but at least it's a sort of workaround.

Categories

Resources