I have rooted Samsung Galaxy S5 on build PA2 (downgraded from marshmallow) 5.1.1 lollipop using kingroot. Initially wouldn't work but it worked when I booted the device after being dead for days and during a flood of notifications, I ran kingroot again and during the process the device soft rebooted, which seemed like a good sign. Once I rebooted I went to kingroot again and it completed the root process (though it reported failure) but I went to root checker and it confirmed that I have root. Also on full reboot, I see on the initial boot screen a grey lock that is unlocked and the word custom right below it. I was able to successfully change my boot animation and install busybox and use other root applications. Xposed does not work! I have not found any recoveries that will work with the device so I can't do custom roms (yet). I have not checked if Knox was tripped yet. If you have the PA2 update and want to root, try kingroot, it worked for me. I have not found out how to change superuser without removing root because I dislike kingroot su, I tried doing so using supersu but supersu failed. I hope for further progress on the root of this version and some recoveries for this build.
Related
I have a OnePlus One mobile.
I have rooted it installed multirom on it everything was working fine .
Then i installed cyan hacker rom using twrp and multirom.
But after two days when i rebooted device into stock(internal) rom Super Su stopped working .
I was getting error "Super Su binary not found and super su can't install it).
i tried everything removed old Super Su ,flashed new one but same problem.
Tried disabling and enabling it but same problem.
But in my cyan hacker ROM when i checked i found "Your device has root access"using Root Checker app but in my stock rom it is showing as your device does not has root access.
When i am opening Multirom app it is showing you don't have root access.But in twrp recovery i have that multirom utility there and it's working fine.
I don't know what to do whether my device is rooted or not.
Shall i need to unlock the bootloader again and perform same activity of rooting again.
Please help.
Hi guys ! I decided to root my moto g3 with kingroot for the first 4-5 hours everything was working fine , I even downloaded some root essentials apps like BusyBox , SuperSU , Titanium backup . Then all of a sudden when i was playing a game the phone automatically reboots and the next thing I know the wifi and my 3G connections was not working . I searched on the net for hours but found no solution pls help :crying::crying: PLS HELP AND LET ME KNOW IF YOU NEED ANY OTHER INFORMATION
same issue for me.
after updtating to 6.0.1, i've tryed to root with supersu 2.67 systemless -> stuck on boot.
reflash, try to root with kingroot -> after reboot: no ril, no wifi
strange
Maybe we need to report to the developer! (KingRoot team)
Sent from my MotoG3 using Tapatalk
Never use crappy apps like King root.. Sorry but the only clean way of rooting is unlocking your bootloader and flash superSU. You can fix your WiFi by flashing the stock firmware files
I know kingroot is the last chance for rooting. Did you try to root the last official 6.0.1, it's stuck with supersu.
murigny64 said:
I know kingroot is the last chance for rooting. Did you try to root the last official 6.0.1, it's stuck with supersu.
Click to expand...
Click to collapse
I was in 6.0 rooted with SuperSU
I came back to stock ROM in 6.0.1 and tried to root again with SuperSu.. and it is stuck in boot loop...
General issue or just me?
murigny64 said:
same issue for me.
after updtating to 6.0.1, i've tryed to root with supersu 2.67 systemless -> stuck on boot.
reflash, try to root with kingroot -> after reboot: no ril, no wifi
strange
Click to expand...
Click to collapse
So why didn't you try 2.62-3? There are numerous reports of being stuck on bootloader after flashing 2.67. 2.62-3 has seemed to work the best for the original root of a G3.
Yes , i saw that, i retry and work fine with 2.62-3
On Builds OK7 and OG5 We Have Temp Kingroot, But SuperSU causes bootloop, right.
Verizon Galaxy S7s have a custom SuperSU to stop the phone from bootlooping, they are in the same boat we are in:
Both VZW S6 and S7 Have Engineering Kernals (EasyRootTools Seems to just flash Kernal 3.10.61-6309174-eng for S6)
The Theory Is If We can flash the custom SU it might just work...
STEPS
1.Flash Kernal Via ERT.
2.Root Via Kingroot 4.5.0
3.Run SuperSU-ME 6.7
4.??? Somehow Install S7 SU binary and remove standard to stop bootloop. ???
5.profit (perm SuperSU root)
COME ON, WE ARE SO CLOSE!
I Don't Have Time Today, But HAS ANYONE TRIED Flashing the S7 SU zip via Flashfire....
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.
Hey guys, had a little problem pop while while setting up my moto 9 g plus.
I have already successfully rooted and verified it on my phone once, and after flashing stock rom, it says in Root Checker App it says "Sorry! Root access is not properly installed on this device.
I thought once successfully rooted, you did not have to worry. I flashed the stock rom, used adb to remove some basic bloatware, and started installing some apps. I already flashed magisk and it shows it is installed successfully, as well as xposed framework, but when I tried to give root access to youtube vanced, it wouldn't let me. That's when I downloaded the root checker again and seen this message.
Anyone have any idea why this happened and how I can fix it? If I need to root my phone again, it's just that I don't know where to begin because I've done it all once. I already have done all the steps to have twrp and magisk. Where do I go from here to get the root verified again?
Thanks!
As soon as you re-flash a ROM all modifications you applied to existing ROM are gone.
jwoegerbauer said:
As soon as you re-flash a ROM all modifications you applied to existing ROM are gone.
Click to expand...
Click to collapse
So where do I go from here? (I edited my main message with a little more info).
Yesi Trotamundos said:
Hey guys, had a little problem pop while while setting up my moto 9 g plus.
I have already successfully rooted and verified it on my phone once, and after flashing stock rom, it says in Root Checker App it says "Sorry! Root access is not properly installed on this device.
I thought once successfully rooted, you did not have to worry. I flashed the stock rom, used adb to remove some basic bloatware, and started installing some apps. I already flashed magisk and it shows it is installed successfully, as well as xposed framework, but when I tried to give root access to youtube vanced, it wouldn't let me. That's when I downloaded the root checker again and seen this message.
Anyone have any idea why this happened and how I can fix it? If I need to root my phone again, it's just that I don't know where to begin because I've done it all once. I already have done all the steps to have twrp and magisk. Where do I go from here to get the root verified again?
Thanks!
Click to expand...
Click to collapse
Already solved...I did verify root after flash and installing magisk, but I did not realize that the security patches would cause screw up root. Just had to reflash magisk and root verification works again.