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!

[Q]Help! With SuperSU Root Lost on L90 D415 Lollipop

This is my first time rooting and ive googled all that i can, forgive me if i dont understand right away.
I rooted my L90 D415 TMobile with lollipop 5.0.2 using this on youtube: watch?v=mQoERPnQ8Qk method but with LG One Click v1.3.
Everything went fine and it ended up rooted. And then I went on to install Flashify and flash TWRP with it so that I could install Xposed Framework. I then followed this on youtube: watch?v=bet8K238SSk method to install Xposed. Finished that method and rebooted and I still had root and i also had xposed activated.
The problem started when my phone kept reading low storage space when I had plenty of space, space i usually have left. I remember reading that this was a problem. I followed the method right with Clearing CACHE/Dalvik after flashing xposed zip in TWRP, just like everyone said so I was confused as to why I got it.
So rebooted into TWRP with Flashify and cleared Cache and Dalvik again and rebooted back into system and it still said low storage space and it also said "there is no su binary installed, supersu cannot install it" root checker told me the root wasnt installed right and that my phone was no longer rooted. Now i cannot get into twrp through flashify to flash my recovery either. I am worried because this is my very first time rooting.
I just need my root back.
Can someone please help me and keep it in dumb terms because im new and dont understand all the Root lingo.

biblicachanel said:
This is my first time rooting and ive googled all that i can, forgive me if i dont understand right away.
I rooted my L90 D415 TMobile with lollipop 5.0.2 using this on youtube: watch?v=mQoERPnQ8Qk method but with LG One Click v1.3.
Everything went fine and it ended up rooted. And then I went on to install Flashify and flash TWRP with it so that I could install Xposed Framework. I then followed this on youtube: watch?v=bet8K238SSk method to install Xposed. Finished that method and rebooted and I still had root and i also had xposed activated.
The problem started when my phone kept reading low storage space when I had plenty of space, space i usually have left. I remember reading that this was a problem. I followed the method right with Clearing CACHE/Dalvik after flashing xposed zip in TWRP, just like everyone said so I was confused as to why I got it.
So rebooted into TWRP with Flashify and cleared Cache and Dalvik again and rebooted back into system and it still said low storage space and it also said "there is no su binary installed, supersu cannot install it" root checker told me the root wasnt installed right and that my phone was no longer rooted. Now i cannot get into twrp through flashify to flash my recovery either. I am worried because this is my very first time rooting.
I just need my root back.
Can someone please help me and keep it in dumb terms because im new and dont understand all the Root lingo.
Click to expand...
Click to collapse
Don't feel too bad. We all had to go through it at one time. It took me about 10 days to realize what all it took to do this so I didn't hard brick my phone.
This storage space can become a problem due to the fact that Android only allows certain amount of space for /system partition. With a stock ROM, its almost crammed full then. Add Xposed to it, and I'm surprised the app framework installed.....anyhow...can you boot normally into your OS? If so, use this method to obtain root....I know it says for G2, Flex G2, and G3, but this works for most LGs including the 415. It's the method I've used several times without problem.....http://highonandroid.com/android-smartphones/how-to-root-lg-g-flex-2-g2-g3-on-lollipop/
Let me know if that works.
Sent from my LG-D415 using Tapatalk

Build.prop won't save changes on reboot + Trouble with temp root (using Kingroot)

Hi all.. I am having some issues with both rooting and modding my build.prop.
My ultimate goal right now is to have a stable root, on essentially stock rom, with a modded/bypassed native tether app (I have unlimited data and verizon blocks it). I am having issues with both processes, and if anybody can help it would be greatly appreciated!
First, I am having a ton of trouble with the temp root process; I am using Kingroot, and although I have been able to gain root successfully, it seems completely random when the process works and when it doesn't. About a quarter of the time, the root seemingly works.. the rest of the time, I either get force crashes on all running apps until system reboot, I am told I have root but cant access system files still, or the root fails altogether. Perhaps there is a flaw in my process? I also have been unable to update the SU binaries.. I have tried using both the latest stable and beta APKs from Chainfire. Is there a specific process that someone has used more successfully, order of installations, etc?
Secondly, when I have gained root successfully, I have been trying to add a line into my build prop to bypass the tether subscription check, which I believe will work.. but whenever I reboot my phone, it overwrites my saved changes to Build.prop. I will successfully get r/w (Using root explorer btw), mod the build.prop just adding in a single line, save, and then reopen confirming that the changes stuck. However, when I reboot, the stock Build.prop comes right back. I have also attempted to copy a modded brand new build.prop into /System instead, which also appeared to work, but ends with the same problem on reboot.
Please note that if possible I want to keep running stock, I do not want to have to flash a modded rom.
TL;DR - Root is finnicky, SU binaries won't update and build.prop resets to stock on reboot even after confirmed edits.

I just read the tldr.
You need to use kingroot to root. This will be a very crappy root and all changes will be lost on every boot at first.
To obtain a proper root and permanent write access do the following.
Download twrp for quark
Download supersu flashable zip
Download and install flashify
Download and install sunshine
Download and install kingroot
Run kingroot and root the device
Run sunshine pay $25 for unlocked bootloader
Reboot
Run kingroot and root the device
Run flashify and flash the twrp for quark recovery.
Reboot into recovery run twrp
In twrp it will ask you a question that has to do with write access SWIPE YES.
Reboot
Run kingroot and root the device.
Kingroot is now stable.
Uninstall kingroot from the 3 dots in the app
Reboot into recovery and start twrp
Flash the flashable chainfire supersu zip
Reboot.
You now have root and the ability to make permanent changes to system.
P.S.
There is currently no way to do this without sunshine.
Sent from my XT1254 using XDA Free mobile app

mrkhigh said:
I just read the tldr.
You need to use kingroot to root. This will be a very crappy root and all changes will be lost on every boot at first.
To obtain a proper root and permanent write access do the following.
Download twrp for quark
Download supersu flashable zip
Download and install flashify
Download and install sunshine
Download and install kingroot
Run kingroot and root the device
Run sunshine pay $25 for unlocked bootloader
Reboot
Run kingroot and root the device
Run flashify and flash the twrp for quark recovery.
Reboot into recovery run twrp
In twrp it will ask you a question that has to do with write access SWIPE YES.
Reboot
Run kingroot and root the device.
Kingroot is now stable.
Uninstall kingroot from the 3 dots in the app
Reboot into recovery and start twrp
Flash the flashable chainfire supersu zip
Reboot.
You now have root and the ability to make permanent changes to system.
P.S.
There is currently no way to do this without sunshine.
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the input..
I was hoping to avoid unlocking the bootloader, but I suppose I might as well. Kingroot does give me root, even if unstable, and Root Explorer tells me I have right access to /system.. plus, I can see that the changes have been implemented to build.prop, so it doesn't really make sense to me how/why it would revert to the stock build.prop on a reboot. Oh well.

The ROM checks the system on reboot. If it sees a change it reverts to what it was.
To fix that you need write protection disabled. Which twrp can do on an unlocked boot loader
Sent from my XT1254 using XDA Free mobile app

I may be wrong but I don't think you need to install TWRP to get rid of kingroot. I didn't feel like installing twrp partially because I'm lazy and partially because I dont plan on installing any other rom any time soon. Anyway, what I did was install kingroot, pay my $25 to sunshine and unlock the bootloader, then ran a script to remove kingroot an install supersu. The result was a perm rooted phone with super-su.
Maybe root checker is lying when it says i have root but adblocker can write to the hosts file so i don't think it is.

Kingroot cannot gain u permission for edit system partition. It only gain permission for run some script, program, it not true root, form what i read then even flash root by mofo, we still can't edit system partition
So u need unlock your bootloader

Okie Dokie smokie. I'm not here to convince anyone, I'm just letting you know what worked for me. I have su persistent in /system/xbin and have never installed TWRP. Root lives through reboots and superSU is installed and processing root requests. Kingroot is gone off the device. Feel free to PM me. I would be interested to see if it works without an unlocked bootlaoder. As i said, I unlocked with sunshine but never installed TWRP.
Are you sure recovery doesn't just check the recovery partition and restore it if it finds it has been modified. I have seen that behavior in the past very often. It seems a little wonky that every time the system boots it would check the whole /system partition.

Yes, it reverts all changes.
This is the first device I've owned that did this as well.
Sent from my XT1254 using XDA Free mobile app

mrkhigh said:
Yes, it reverts all changes.
This is the first device I've owned that did this as well.
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
As I said, I think you may be mistaken. i am looking through the script i used to replace kingroot. What does TWRP modify to allow persistent recovery. I wonder if booting into recovery will wipe out the persistent root. A normal reboot does not effect it. Maybe build.prop gets restored while other files do not. As i said, my hosts with adblockign persists through reboots.
As far as the first post, there is an app out there which will add the line needed on the fly. com.ncsoftwaresolutions.entitlementbypass It worked perfectly on my Moto X running 5.1
I did not write the script i used and take no credit for it. Lets get that out of the way.

I am not completely sure as to how they accomplish this. Since there are things that can get "stuck" there such as kingroot app.
Perhaps someone else would like to chime in.
But I do assure you that write protection exists on this device.
And that the changes you're attempting to make requires it to be off.
Sent from my XT1254 using XDA Free mobile app

mrkhigh said:
I am not completely sure as to how they accomplish this. Since there are things that can get "stuck" there such as kingroot app.
Perhaps someone else would like to chime in.
But I do assure you that write protection exists on this device.
And that the changes you're attempting to make requires it to be off.
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
I don't doubt that is your experience. I was sharing mine. I rebooted into recovery and root stayed. What i am saying, with confidence because i have done it, is that you do not need to install TWRP to keep root persistent through reboot.
Here is the script i ran.
http://pastebin.com/w7MqXBZZ
After looking more my best guess is that the Sunshine process disabled nand lock which is why i am able to write to the system partition.

Thanks for the help guys.. interesting notes.
It turns out I can pay 30$ a month now even with unlimited data to unlock hotspot, which is good enough for an interim solution. I also don't plan on flashing any roms.. I prefer to do my own tweaks. I will probably proceed with unlocking the bootloader for persistent root and /system write permissions, once I get some time.

Cryptrix said:
Thanks for the help guys.. interesting notes.
It turns out I can pay 30$ a month now even with unlimited data to unlock hotspot, which is good enough for an interim solution. I also don't plan on flashing any roms.. I prefer to do my own tweaks. I will probably proceed with unlocking the bootloader for persistent root and /system write permissions, once I get some time.
Click to expand...
Click to collapse
That option has been around for a long time.
Sent from my DROID Turbo using XDA Free mobile app

Not Quite
cstone1991 said:
That option has been around for a long time.
Sent from my DROID Turbo using XDA Free mobile app
Click to expand...
Click to collapse
Actually, the rest of the users on my line were on a very outdated plan, so Verizon blocked both the free hotspot on the current plans for limited data users, and my option to pay for it on my own line. So instead I spend two hours on the phone convincing them to put the other lines on a "sub-plan", and upgrade them collectively to an Everything More, while mine is singular on the cycle but technically still on the same plan. And NOW I have the option to pay.
Now I just need to figure out how to utilize my upgrade without losing Unlimited data..

I said this a few posts up, it may be of no concern now.
As far as the first post, there is an app out there which will add the line needed on the fly. com.ncsoftwaresolutions.entitlementbypass It worked perfectly on my Moto X running 5.1.
You need root and you need to run it every time your phone is rebooted but ti works to bypass the entitlement check.

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

Titanium Backup Error After Freezing Unused Apps

I've had the phone rooted last year and haven't really messed with freezing unused apps until recently, bringing my battery life length to normal.
One of the apps I have frozen was Kingroot. Out of all the apps I've frozen, I'd think that one would be the culprit.
Here's a list of the relevant apps I've also frozen:
Root Browser
Root Checker
If there isn't a way around this, could I possibly reinstall or update Kingroot? Thanks in advance.

If your bootloader is unlocked and you have TWRP installed, you can use SuperSU instead of Kingroot.
Kingroot has issues and should only be used when absolutely necessary. Someone said it sends data back to China for no good reason.
Here's a post that details how to completely remove Kingroot and use SuperSu instead. I've only posted the relevant parts.
TheSt33v said:
However, if you absolutely cannot use a computer, you can do this, although I do not recommend it:
1. Google Kingroot, download, install it onto your phone and use it to root your phone. Be aware that Kingroot is developed by a Chinese company, and part of their rooting process involves sending lots of personal info to them for reasons that aren't entirely clear. There is some debate over how legit they are, but their root method should work on a phone with an unlocked bootloader.
5. Uninstall Kingroot.
6. Download this to your phone and install it using TWRP:
http://forum.xda-developers.com/droid-turbo/development/rom-su4tl-49-100-stock-t3390041.
This will remove all of the Kingroot files from your phone that probably were left on it after you uninstalled it.
7. Download this to your phone and install it using TWRP:
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.78-201609011115.zip
You should now have a rooted, TWRP-equipped phone.
Click to expand...
Click to collapse

Thanks for the tip on KingRoot, Chazz.
I've just figured out the solution; Settings/Apps/Menu option in upper right-hand corner/Reset app preferences :good::good::good:

coconutt said:
Thanks for the tip on KingRoot, Chazz.
I've just figured out the solution; Settings/Apps/Menu option in upper right-hand corner/Reset app preferences :good::good::good:
Click to expand...
Click to collapse
I edited my post to incluede @TheSt33v instructions on how to completely remove Kingroot. There is no valid reason for keeping it on your phone.