Database Develop

[ROOT] SGP312 FTF 10.3.1.C.0.136 Root (No need OTA)

Hi
I have tested the root tool from China forum. My device is SGP312 WIFI 32GB 10.3.1.C.0.136. No need to unlocked.
Download the attachment and install. One click and then it will reboot. It is rooted!
But the root-mangement software is Chinese. You can download Supersu or Superuser.
Use the Chinese root software to give Supersu or Superuser root access.
Run Supersu or Superuser and upgrade the binary. Exit and uninstall the Chinese root software.
Reboot. Then you are rooted with Supersu or Superuser.
This is the original link: http://www.mgyun.com/vroot

incredible...works on sgp321 .244......good job....juat install supersu afterwards and remove the chinese app....greatttttt

Good! I can confirm it works, just rooted my still locked SGP311FR with it.
What I don't like it's an exe file, install the app then run it to root.
If someone can extract the script and replace the root apk by superSU it would be cool.
Also I noticed while rooting my tablet that the screen became white two times (really fast for less than a second, sort of blink) like the Display tricks that were used before to root our xperia's.
Anyway thanks.
Btw : @insideccw posting a link to the source, and maybe the name of the autor of this tool, would be better if it's not your own tool.

babylonbwoy said:
Also I noticed while rooting my tablet that the screen became white two times (really fast for less than a second, sort of blink) like the Display tricks that were used before to root our xperia's.
Click to expand...
Click to collapse
That might be the exploit that is accessing the framebuffer causing it.

works like a charm on my sgp351 lte 16gb .244, recomended, thans for the post

Also working with Xperia sp
Sent from my C5303 using Tapatalk 4

I tried this with my 312, but upon removing the chinese superuser with Titanium-backup, i could no longer use Superuser or SuperSU from the play-store. Any insight on to what exactly you guys went about this? I have reset using PC Companion.

Word fine With 4.2.2 thx a lot
Sent from my SGP321 using XDA Premium 4 mobile app

bugger561 said:
I tried this with my 312, but upon removing the chinese superuser with Titanium-backup, i could no longer use Superuser or SuperSU from the play-store. Any insight on to what exactly you guys went about this? I have reset using PC Companion.
Click to expand...
Click to collapse
I think you need to install the alternative superuser app before deleting the Chinese one. I used superuser by chainsdd on my sp
Sent from my C5303 using Tapatalk 4

works great...thanks

That's pretty much what I did. I've tried SuperSU, superuser, and the cwm app. The problem seems to be that the updated binaries don't "stick", SuperSU claimed updating was a success but then prompted me to do so every time I opened it.

bugger561 said:
That's pretty much what I did. I've tried SuperSU, superuser, and the cwm app. The problem seems to be that the updated binaries don't "stick", SuperSU claimed updating was a success but then prompted me to do so every time I opened it.
Click to expand...
Click to collapse
I don't know if the info in this thread may be of any use : http://forum.xda-developers.com/showthread.php?t=1539711.
Specifically in the OP :
Remember, if you remove older first without installing newer one, you will lose Root n newer won't run.
One more thing market version will be regular application, so hard reset can delete it. So better install with flashable zip, to make it system application.
And in Post #8 :
Confirmed working fine! Recommended to install via CWM. It will replace the other (superuser) automatically so you don't have to manually remove it.
I used the above zip file and instructions a long time ago on my Galaxy S....but it may still be relevant for Tablet Z.

What I've been doing us installing from the play store, updating binaries, and then removing the Chinese app. Once I do that, I lose root in the market superSU and other root apps.
I'll probably end up unlocking the boot loader and flashing an image over adb.
Thanks for the help!

bugger
That is because you dont have /system r/w access.
bugger561 said:
What I've been doing us installing from the play store, updating binaries, and then removing the Chinese app. Once I do that, I lose root in the market superSU and other root apps.
I'll probably end up unlocking the boot loader and flashing an image over adb.
Thanks for the help!
Click to expand...
Click to collapse

bugger561 said:
What I've been doing us installing from the play store, updating binaries, and then removing the Chinese app. Once I do that, I lose root in the market superSU and other root apps.
I'll probably end up unlocking the boot loader and flashing an image over adb.
Thanks for the help!
Click to expand...
Click to collapse
It worked for me...I accidentally removed the Chinese app.
1. I did a reroot again.
2. installed dualrecovery and flashed the UPDATE-SuperSU-v1.65.zip.
3. It works now.

Supersu and cwm superuser caused my phone to go in a reboot loop when I tried updating the binaries. Superuser by ChainsDD is working fine though.
Sent from my C5303 using Tapatalk 4

insideccw,
Any tips on how t go about correcting this? Would I need to use adb or can I handle this form within android?
EDIT: Looks like others are having the same issue.

Doesn't work with SGP321 LTE tablet (on the newest firmware .244)
1. in order to uninstall the chinese root app one needs to have SuperSu
2. once you install SuperSU the root checker shows "OK, you're rooted"
3. once you get rid of the chinese root the root checker shows "you're NOT rooted" and the SuperSU binaries can't get updated (strange it needs another update)

Geezer said:
Doesn't work with SGP321 LTE tablet (on the newest firmware .244)
1. in order to uninstall the chinese root app one needs to have SuperSu
2. once you install SuperSU the root checker shows "OK, you're rooted"
3. once you get rid of the chinese root the root checker shows "you're NOT rooted" and the SuperSU binaries can't get updated (strange it needs another update)
Click to expand...
Click to collapse
Works on mine. Update the superuser binaries before deleting Chinese superuser app. On mine, supersu detected the Chinese one and deleted it for me
Sent from my C5303 using Tapatalk 4

bugger561 said:
That's pretty much what I did. I've tried SuperSU, superuser, and the cwm app. The problem seems to be that the updated binaries don't "stick", SuperSU claimed updating was a success but then prompted me to do so every time I opened it.
Click to expand...
Click to collapse
For those of you having this issue as I was, I just got mine to work with SuperSU. Hopefully these steps will work for you too:
-Gain root with the magical Chinese root tool
-install SuperSU
-update SuperSU binaries
-in SuperSU settings, choose "Switch superuser app"
-reboot the tablet and immediately go to the playstore and install SuperSU
-update SuperSU binaries
Let me know if it works!

Rooted, but no rooted apps work

Hello,
I recently used the toolkit to unlock and root my Sprint N6. Super user was installed and works. I installed Rootcheck after everything was complete and it verifies that the phone is rooted. I have installed Nexus 6 double tap to wake and LED control and both state that the phone is not rooted. Super user shows both those apps have super user access.
What am I missing? Thank you!!

itlbok333 said:
Hello,
I recently used the toolkit to unlock and root my Sprint N6. Super user was installed and works. I installed Rootcheck after everything was complete and it verifies that the phone is rooted. I have installed Nexus 6 double tap to wake and LED control and both state that the phone is not rooted. Super user shows both those apps have super user access.
What am I missing? Thank you!!
Click to expand...
Click to collapse
use the latest SuperSU

I am on version 2.65 and from what I can tell, that is the latest.

itlbok333 said:
I am on version 2.65 and from what I can tell, that is the latest.
Click to expand...
Click to collapse
you will also need to install busybox as well, as many root apps need it. install from the play store, then install from the app. search busybox in the play store, then choose stericsons version.
---------- Post added at 11:17 AM ---------- Previous post was at 11:15 AM ----------
and supersu 2.71 http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

Thank you for the reply, Sorry I failed to mention I do have the move listed busy box installed as well. I have clicked on install from within the app as well. Still none of the mentioned root apps work, all say phone appears to not be rooted...

itlbok333 said:
Thank you for the reply, Sorry I failed to mention I do have the move listed busy box installed as well. I have clicked on install from within the app as well. Still none of the mentioned root apps work, all say phone appears to not be rooted...
Click to expand...
Click to collapse
try flashing the supersu 2.71 with twrp recovery, you should have root when you boot up. dont use the toolkit.

simms22,
I flashed version 2.71 through recovery, after reboot it was installed. Same "phone does not appear to be rooted" when trying to use the root apps... Root check still says phone is rooted. This is puzzling!

itlbok333 said:
simms22,
I flashed version 2.71 through recovery, after reboot it was installed. Same "phone does not appear to be rooted" when trying to use the root apps... Root check still says phone is rooted. This is puzzling!
Click to expand...
Click to collapse
very odd! tell me, which rom are you using? and did you wipe your data before rooting? if not, you might have to wipe your data then reflash your rom/gapps, and supersu.

I am stock rooted. Yes I wiped data and started from scratch after unlock and root.

itlbok333 said:
I am stock rooted. Yes I wiped data and started from scratch after unlock and root.
Click to expand...
Click to collapse
when you try to use a root app, so you get a little popup that asks you to give the app root? do yoh have the supersu app installed as well?

Yes SuperSU 2.71 flashed, the popup comes up and I grant access. Then each app says not rooted. Makes zero sense... The apps even show up in SuperSU app.

Yes, there is a popup and I have granted SU access to the above root apps, still no joy. I have SuperSU 2.71 flashed and installed, Root check verifies root.

I had this. The fix is to uninstall Busybox and reinstall into an alternative directory where it can be found. Mine appears to work fine in /su/bin, but if that doesn't work for you try the others (/system/xbin, /system/bin etc.)
It may not even need to be uninstalled - you could just try installing into the different directories until you find the one that the root apps are checking for root, though I'm not sure whether that would clutter your device with redundant binaries. I'm sure someone will be able to advise on that.

N910T acting crazy after root

So after getting my replacement N910T, I rooted it using the method here, and it seemed to go well, but during the process of reinstalling apps, I noticed some erratic behavior like the device not allowing root access when root checker says it is rooted. Or SuperSu not asking for SU access on apps that normally do, thereby denying root access, like Root Explorer. When I go back and check root checker again, sometimes it shows that it has access and other times it says that it doesn't. For a device with a supposedly unlocked bootloader, I've never encountered so many issues. My AT&T S4 which has a locked BL never gave me any issues once it was rooted. With all the devices I've rooted over the years, I've never had this much trouble. So I'm wondering if it's corrupted somehow? Or is there something about this systemless root that is the issue?
Here are the basics:
Android 5.1.1
Baseband OK2
Kernel Version 3.10.40-6209177
Build Number LMY47X.N910TUVU2DOK2
I've read threads until I'm crosseyed and googled but couldn't really come up with anything, so I could use some help here.

I had the same problem with a Note 4 Tmo I am working with. What SuperSU version are you using?
I had root issue problems (root chk says rooted, issues in ES File Expl, etc) when I used anything higher than 2.65.
Try flashing SuperSU 2.65 stable through recovery (I use TWRP 2.8.?.?) and when exiting out of recovery DO NOT allow SuperSU to be installed as SuperSU installation says...

Thanks much for the response. I'm using SuperSu 2.71; I didn't choose this version, it came with the root I got from here. So where do I find this version you're referring to?
Sent from my iPad using Tapatalk

Hi have you figured out your issue yet. If not, Try using supersu 2.52. It's the last full system root I believe. I have had much better luck with full system than systemless.

noob4598 said:
Hi have you figured out your issue yet. If not, Try using supersu 2.52. It's the last full system root I believe. I have had much better luck with full system than systemless.
Click to expand...
Click to collapse
I haven't tried anything else yet, I giving my head some time to clear. I've been at this for hours now, so I need a rest. Can I find that version of SuperSu as a flash able zip?

I used the links from Chainfire's thread on XDA
http://forum.xda-developers.com/showthread.php?t=1538053
Download to stable 2.65 is in that thread points to this link:
https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip

https://download.chainfire.eu/743/supersu this is link to 2.52 zip if u need it

Thanks for all the help, I'm glad this happened to someone other than me. One thing though: I'm on OK2, I thought you couldn't have system root with that.
Sent from my iPad using Tapatalk

Okay, the installation of supersu 2.52 via TWRP has definitely made a difference! The device is noticeably stabler now. One last thing, though: root checker shows it's rooted, but says that a superuser app isn't installed, which is what I thought supersu was. So now what?

Did you flash over 2.71. And do you have a su app icon on your scrren.

noob4598 said:
Did you flash over 2.71. And do you have a su app icon on your scrren.
Click to expand...
Click to collapse
Yes, I just flashed it from TWRP without doing anything else. And no, there isn't a Su app icon on the screen. I have a nandroid backup that'll put it back to the way it was before I did that, just in case it crashed and burned.

Download the app from playstore and then go to settings and do a full unroot. Then reboot to recovery and flash 2.52 then wipe cache and dalviche and reboot

MUCH BETTER!!! I'm in the process of reinstalling all of my apps; I don't want to take a chance of restoring my backup from Titanium, just in case there's something that won't play right.
I'll report back in a day or so.
Thanks to everyone who provided answers, it is most appreciated!

Welcome bud.

Thank you for the information guys. I was having the same issue as OP. Reverted SU as described and everything is much smoother

Yes, it's been a few days and my device is working the way it is supposed to. Interestingly enough, my SuperSU has automatically updated to version 2.65 but it's still working fine.
I've since turned off automatic updates in Google Play for fear of getting a version that begins the cycle all over again.
I still have the issue with the device telling me that the recovery is not seandroid enforcing even though I've updated to TWRP 3.0, and the set warranty bit: kernel issue. In spite of these, my device seems to work just fine with no issues.
Thanks again to everyone who offered help. It's nice when people offer help instead of posting just to tell you to find the answer yourself.
Sent from my SM-N910T using Tapatalk

Your welcome. And I get kernel is not seandroid enforcing on every reboot. Thought it was normal ha

My research on this has taken me all over the place, but none of the suggestions or explanations seem to apply. The device isn't ostensibly crippled, so I don't know.
Sent from my SM-N910T using Tapatalk

I think it's normal...maybe...ha Im pretty sure it's the warranty bit

are there root for N910A 5.1.1

Systemless SuperSU has big problem on MIUI 8 ROM

Hello,
I'm using MIUI 8 on my phone, its based on marshmallow 6.0.1. I rooted my device using supersu stable 2.78 as systemless mode. The problem is all need-root apps take long time to call supersu at first time it launched. Sometimes need-root app crash if it does not get superuser access for long time. The culprit is on systemless supersu, Superuser.apk installed inside /data partition instead of /system so it won't load on system start. Although i already add SuperSU in startup list, but it was not much help. I did not get this issue on CM13 based rom. Temporary solution is I need to open SuperSU first before open need-root apps for first time.
How to get rid from this issue?
Cc: @Chainfire

Have you found solution yet. Me too facing similar problem, some of my personal apps crashing, I found a system based super Su zip let me flash and report back..

herecomesmaggi said:
Have you found solution yet. Me too facing similar problem, some of my personal apps crashing, I found a system based super Su zip let me flash and report back..
Click to expand...
Click to collapse
Yes. Use phh superuser + magisk latest version. :good:

actually this is not the right answer, wrong thread
Hi
I'm sorry for bumping old thread, I've same issue with very same ROM, MIUI 8 8.1.6 run on mi4W device, magisk 13.3
how I managed to solve this is somewhat ridiculously simple yet make me wandering over the internet for about 4 hours in 2AM,
I forgot to activate the "install from unknown source". after that everything run like magic.
FYI: I've done everything via adb shell via TWRP before the "what if" idea come to my head
Click to expand...
Click to collapse

[SOLVED]Magisk v10 - su binary out of date, but root still works

Since I upgraded from Magisk v9 to v10, every time I reboot my phone, I get a notification from phh's Superuser that says "Install Superuser" "The su binary is out of date." When I tap the notification, it just opens the Superuser app and doesn't ask me to update anything. Root still works normally, though. This is happening on a Nexus 5X running stock build NMF26F with no modifications other than Magisk itself, and no modules except for Superuser. The same thing happens whether Magisk Hide is on or off. I tried completely uninstalling and reinstalling Magisk, which didn't fix it either. What could be causing it, and how can I fix it?
EDIT: Solved: Magisk 10.2 includes a new version of the su binary that fixes this issue.

josephcsible said:
Since I upgraded from Magisk v9 to v10, every time I reboot my phone, I get a notification from phh's Superuser that says "Install Superuser" "The su binary is out of date." When I tap the notification, it just opens the Superuser app and doesn't ask me to update anything. Root still works normally, though. This is happening on a Nexus 5X running stock build NMF26F with no modifications other than Magisk itself, and no modules except for Superuser. The same thing happens whether Magisk Hide is on or off. I tried completely uninstalling and reinstalling Magisk, which didn't fix it either. What could be causing it, and how can I fix it?
Click to expand...
Click to collapse
This is because the su binary included in Magisk is a modified one & the official phh root manager detect that it is not equal to the lastest official su binary... just ignore that notification.

This happens on Magisk 9 as well I wish there was a way to turn it off but it's not really a big deal I guess.

Deic said:
This is because the su binary included in Magisk is a modified one & the official phh root manager detect that it is not equal to the lastest official su binary... just ignore that notification.
Click to expand...
Click to collapse
Yep, I did some poking around and confirmed that. (It's also entirely because of the new Superuser module, not the new Magisk). I guess as a workaround for now, I can block the Superuser app from sending notifications. The good news is this, though:
topjohnwu said:
Right now you still have to install the phh Superuser application, however the root management should move to Magisk Manager soon, please stay tuned.
Click to expand...
Click to collapse
This will take care of it. I'm not sure why he didn't wait to change the su version code until that was done, though, as that would have avoided this problem.
EDIT: And I also now see this listed as a known issue in the main Magisk post.

I am having the same issue, except none of my apps can see root.

kiefferbp said:
I am having the same issue, except none of my apps can see root.
Click to expand...
Click to collapse
It's not at all the same issue then. You should post about it in another thread.

josephcsible said:
It's not at all the same issue then. You should post about it in another thread.
Click to expand...
Click to collapse
Sorry if I sounded like one of those noobs that posts unrelated things in a random thread. I originally thought it was somewhat related since Magisk Manager said root was properly installed, but no other app recognized it.
I managed to fix that by un-installing and re-installing the phh superuser module. I am now just in the same boat as you, and I'll patiently wait for a fix.

kiefferbp said:
Sorry if I sounded like one of those noobs that posts unrelated things in a random thread. I originally thought it was somewhat related since Magisk Manager said root was properly installed, but no other app recognized it.
I managed to fix that by un-installing and re-installing the phh superuser module. I am now just in the same boat as you, and I'll patiently wait for a fix.
Click to expand...
Click to collapse
Can confirm. On Nexus 5x 7.1.1 with no other modifications, but lost root after I updated to v10. However, after an uninstall and reinstall I was back in business. One note though, the installation through magisk manager failed, and I had to manually flash the zip in recovery.

Fixed with Magisk 10.2.

josephcsible said:
Fixed with Magisk 10.2.
Click to expand...
Click to collapse
Magisk 10.2 here .. not fixed

warriorvibhu said:
Magisk 10.2 here .. not fixed
Click to expand...
Click to collapse
Make sure it automatically updated you to the topjohnwu r2 version of Superuser. If it didn't, do it manually from https://forum.xda-developers.com/apps/magisk/magisk-phh-s-superuser-android-pay-t3435921. If that doesn't fix the problem, then your problem isn't this problem.

josephcsible said:
Make sure it automatically updated you to the topjohnwu r2 version of Superuser. If it didn't, do it manually from https://forum.xda-developers.com/apps/magisk/magisk-phh-s-superuser-android-pay-t3435921. If that doesn't fix the problem, then your problem isn't this problem.
Click to expand...
Click to collapse
Yup all that done .. still have the same notification ..

I have the same problem.
1) i have tryed to flash magisk 10.2 by recovery but after flashing the s7 edge goes in bootloop (tyed with SuperSu disabled and without binary installed). So i had to flash the unistaller.
2) I even tryed enabled the chainfire SuperSu just for trying to flash the magisk+phh by magisk manager. Out of date. I think it cames cause magisk try to load the chainfire supersu binary and not the SU binary magisk has.
Help me please.
P.s. i have tryed with a clean boot image charged.

I had the same issue, and also noticed that su wasn't working in ADB. It looked like some permissions were wrong on the /magisk/phh directory. I solved it by uninstalling the phh superuser module from in Magisk Manager, then reflashing phh-superuser-topjohnwu-r2.zip in recovery.

Noxious Ninja said:
I had the same issue, and also noticed that su wasn't working in ADB. It looked like some permissions were wrong on the /magisk/phh directory. I solved it by uninstalling the phh superuser module from in Magisk Manager, then reflashing phh-superuser-topjohnwu-r2.zip in recovery.
Click to expand...
Click to collapse
Tryed, no well news!
Did y have SuperSu binary installed during flashing?

Mr.Fearless said:
Tryed, no well news!
Did y have SuperSu binary installed during flashing?
Click to expand...
Click to collapse
No, I haven't had SuperSU on here at all.

Noxious Ninja said:
No, I haven't had SuperSU on here at all.
Click to expand...
Click to collapse
I've just tryed deleting all the root binary files. Nothing, After flashing magisk 10.2 by recovery the phone goes to bootloop.

Thread closed at OP's request.