Related
In order to root your Nexus S (from Gingerbread to ICS!) I have made a script that all you need to do is launch with your PC! (credits to saurik for the exploit)
Hope this will help you
All you need to do, is run the script! Then, plug-in your phone (needs to be on with USD ADB DEBUG ON) and done!
You can download it here: http://www.mediafire.com/?qhefhtgs20fdtsd
This will root your phone, and then you can afterwards flash ClockworkMod from the market and then reboot into recovery =)
Peace be with you.
xian1243 said:
In order to root your Nexus S (from Gingerbread to ICS!) I have made a script that all you need to do is launch with your PC! (credits to saurik for the exploit)
Hope this will help you
All you need to do, is run the script! Then, plug-in your phone (needs to be on with USD ADB DEBUG ON) and done!
You can download it here: http://www.mediafire.com/?qhefhtgs20fdtsd
This will root your phone, and then you can afterwards flash ClockworkMod from the market and then reboot into recovery =)
Peace be with you.
Click to expand...
Click to collapse
I'll test it later. Does this use fast boot to unlock?
And saurik? He's the king of cydia. He got the exploit?
Sent from my Nexus S using Tapatalk
It worked great, thanks guys
haha..rooted..thanx!!!!!!...
is there a way to make this work with a xoom?
When I try this it shows that it worked, but it doesn't seem to load properly since ROM manager says superuser not found. When I try to update the bineries it also fails on "checking current install path".. failed to find currently installed su binary.
Any ideas?
Edit: I'm running gb 2.3.6
Zorrich said:
When I try this it shows that it worked, but it doesn't seem to load properly since ROM manager says superuser not found. When I try to update the bineries it also fails on "checking current install path".. failed to find currently installed su binary.
Any ideas?
Edit: I'm running gb 2.3.6
Click to expand...
Click to collapse
same here...
does it work with all android phones.like xperia phone.
Thanks!
Just ordered my wife a Nexus S, will try this Friday and report back!
Nice!
Ran it and it worked. Well, ran it and then had to do a few things to prove that it had worked.
After running the script, you have to install Superuser in Google Play Store (Market). Then, I installed MyBackup Pro (paid version) which does a few more fancy things if it has root access. When I ran MyBackup Pro, it said that I have superuser access.
Sweet!
I ran this on a Nexus S i9023 running ICS 4.0.3.
It looks like root access remained after reboot. Pretty good!
COOL! Thanks for sharing! The Nexus is en route!
ivd269 said:
Nice!
Ran it and it worked. Well, ran it and then had to do a few things to prove that it had worked.
After running the script, you have to install Superuser in Google Play Store (Market). Then, I installed MyBackup Pro (paid version) which does a few more fancy things if it has root access. When I ran MyBackup Pro, it said that I have superuser access.
Sweet!
I ran this on a Nexus S i9023 running ICS 4.0.3.
It looks like root access remained after reboot. Pretty good!
Click to expand...
Click to collapse
This is an early April Fool right? The Nexus S is completely open and doesn't need exploits to gain root. Unlock the bootloader then you can use fastboot to install a custom recovery image. Simples.
Hi there, have you made one for the MyTouch4G or do you know if one does exist for it ?
Thanks
Envoyé depuis mon Nexus S avec Tapatalk
Didn't work for me.
Ran the zip, plugged phone in. Downloaded superuser, and then Rom Manager. Rom Manager couldn't see root.
Modified version of this:
http://theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s/
worked for me.
I had to transfer Rom Manager to the phone via email because I couldn't get it to download anything from the market on wifi. Flashed recovery through CW. MIUI is now on the pone.
SWEET!
got it to work to install ota 4.0.4 manually via cwm...only thing is i lost root and it seems this exploit doesnt work on ota 4.0.4 so i cant run it again...
this is cool
thanks for this man...i used it when i got 4.0.3 and worked well on my i9023...ini 4.0.4 it diddnt work...but i restore back to 4.0.3 and installed voodoo ota root keeper from the market...and i restored the the root ran with the script in this poost in one click in 4.0.4 . awsome
Does it wipe your phone in the process?
chushev said:
Does it wipe your phone in the process?
Click to expand...
Click to collapse
nope....
How can we use this in 4.0.4?
flibblesan said:
This is an early April Fool right? The Nexus S is completely open and doesn't need exploits to gain root. Unlock the bootloader then you can use fastboot to install a custom recovery image. Simples.
Click to expand...
Click to collapse
That requires wiping your phone, and unlocking your bootloader. Appears this works with a locked bootloader.
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!
SM-T700 UK version stock 5.0.2
1. Root using Kingroot 4.5
2. ONLY now !!! install and run Super-Sume
3. Update SuperSu binaries
That's all : you have root, SuperSu and Knox still "O" and Kingroot it's gone...
Would people please post the full build version of the firmware they have success or failure with, so others are aware of which ones work.
has this method been verified by other users?
Share your experience please!
It's brand new...
Verified by myself
Have you maintained root after reboot?
ashyx said:
Already tried it, v4.5 is posted in my kingroot thread, didn't work on lollipop for t805.
Neither did supersu me, binary always fails to update, once it did manage after several tries, but root is lost after reboot.
Supersu me is just the same script as posted in the kingroot thread. Root always lost after reboot.
Have you maintained root after reboot?
Click to expand...
Click to collapse
Just following your thread, messing with Kingroot 4.5 (from your tread) I obtained root.
Also someone there suggesting SuperSume to remove Kingroot.
I use it and that's it
Yes the root it's permanent
stefan.pilsu said:
Just following your thread, messing with Kingroot 4.5 (from your tread) I obtained root.
Also someone there suggesting SuperSume to remove Kingroot.
I use it and that's it
Yes the root it's permanent
Click to expand...
Click to collapse
Can you then install SuperSu or do you need to keep the SuperSume?
Anyone else confirm this method ?
louiscar said:
Can you then install SuperSu or do you need to keep the SuperSume?
Anyone else confirm this method ?
Click to expand...
Click to collapse
Super-Sume install SuperSu
Update binaries and done
I waiting also others to confirm
stefan.pilsu said:
I waiting also others to confirm
Click to expand...
Click to collapse
Ok Thanks for putting this up, if it's reliable it will save a lot time for many.
..guys try install first busy box while with kingo root, then install supersu. update binary. if successful,
..uninstall kingoroot . reboot supersu rules!!!!!!
angelshie said:
..guys try install first busy box while with kingo root, then install supersu. update binary. if successful,
..uninstall kingoroot . reboot supersu rules!!!!!!
Click to expand...
Click to collapse
Super_Sume make all this "work" with one click !
Ok guys, thanks for confirming, Sweet
Thanks for the tip. This worked perfectly. I installed Kingroot 4.5. When Kingroot runs scroll down and press "Try it" and it rooted. I then immediately installed Busybox from the Google Play store and ran the smart installer. After a successful install of Busybox, I then installed Super-Sume from the Play store. I ran Super-Sume and it installed Super SU and removed Kingroot. After that, I opened Super SU and allowed it to update the binary. Rebooted. I checked root with Root Checker app and checked Knox with an app called Knox Status on the Play store. Root is still active and Knox is still at "0". I powered off, then restarted again. Root has stayed.
I did this on a brand new US region SM-T700 pulled straight from the box and updated to Lolilipop from OTA.
System Version:
SM-T700
LRX22G.T700XXU1BOE3
*ROOT WORKING !! SMT-700 OTA 'lollipop'
Confirmed working on Lollipop NEE-T805XXU1BOE3 firmware.
Reflashed back to complete stock then ran Kingroot v4.5, root succeeded first time.
Ran Supersu me to remove Kingroot and install Supersu then updated the su binary.
Rebooted then checked root status. Full root access still available.
No need to install busybox as Supersu me already installs busy box.
Looks like we have a winner, no need to downgrade to Kitkat any more. :good:
Hopefully now T807/707 users can now get root.
Credits go to the devs of Kingroot, Chainfire and Supersu me.
ashyx said:
Confirmed working on Lollipop T805XXU1BOE3 firmware.
Reflashed back to complete stock then ran Kingroot v4.5, root succeeded first time.
Ran Supersu me to remove Kingroot and install Supersu then updated the su binary.
Rebooted then checked root status. Full root access still available.
No need to install busybox as Supersu me already installs busy box.
Looks like we have a winner, no need to downgrade to Kitkat any more. :good:
Hopefully now T807/707 users can now get root.
Credits got to the devs of Kingroot, Chainfire and Supersu me.
Click to expand...
Click to collapse
I've told you ...
ashyx said:
Confirmed working on Lollipop T805XXU1BOE3 firmware.
Reflashed back to complete stock then ran Kingroot v4.5, root succeeded first time.
Ran Supersu me to remove Kingroot and install Supersu then updated the su binary.
Rebooted then checked root status. Full root access still available.
No need to install busybox as Supersu me already installs busy box.
Looks like we have a winner, no need to downgrade to Kitkat any more. :good:
Hopefully now T807/707 users can now get root.
Credits go to the devs of Kingroot, Chainfire and Supersu me.
Click to expand...
Click to collapse
It does not appear to work on T707a with 5.0.2.
Maybe ashyx could help.
What exactly didn't work for you ?
stefan.pilsu said:
I've told you ...
Click to expand...
Click to collapse
Do you think this is likely to work for KitKat ANL1? I already downgraded as part of Ashyx's tutorial to ANF7.
My only reservation to going to Lollipop is that I want to use the Xposed framework which I think is still in it's infancy for 5.x or still not compatible.
So before this my options are to keep the original Kitkat by Flashfire - ANL1 or go directly to Lollipop. For the latter I could just get the OTA and do this method now. But not sure if I go to ANL1 kingroot will work as easily
If not I'll continue in the normal way I guess.
Once you have root with Kingroot install Super Sume and run it.
Kingroot 4.5 from ashyxs tread works for me.
Super-Sume just install busybox, SuperSu and get rid of Kingroot.
Why not use Flashfire to install whatever you want: KK or L ?
I rooted my phone using KingRoot. but when I try SuperSu Me it takes KingRoot away however despite using the updated google play store SuperSU from chainfire it can't update the binaries at all. One time it said there wasn't any installed and couldn't install any. I haven't unlocked my boot loader or recovery because I don't have a computer. Any help?
Edit: I'm running stock 4.4.2 using the latest Google play store version.
I have tried to use both update methods, despite not having a custom recovery. When using the normal method I just get installation failed and an okay an a reboot option. Ive tried rebooting but it doesn't help. I can't seem to use supersu me to transfer root control to super su. I also DO have Xposed installed but Im not sure if that's the cause. I do regularly use it. I may try to uninstall and I'll post an update on that.
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