Here is a method that can potentially let you OTA and keep root, try at your own risk:
1. Install VooDoo OTA Root Keeper, make sure all boxes are checked (may have to reinstall superuser and grant to the app)
2. Reboot, double check VooDoo OTA Root Keeper again has all checked boxes, then tell it to save root
3. Defrost/Enable AT&T Software Update, download it and apply
4. Reboot, Use VooDoo OTA Root Keeper to restore root
5. Profit
Thanks to gokartracer5
Click to expand...
Click to collapse
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
For the past few weeks, i've been on a quest to get root and have official status. I've created a few thread related to the issue, and out of all the people that responded, only one has given me the answer that worked.
Still today, i stumble across many people with the custom status issue a little everywhere in the forum, so maybe having one thread explaining it would be a good idea.
This thread is for those that want OTAs, that wanna stay stock but just have root, and that switching from Superuser to SuperSU and rebooting twice did not work.
This has the best chances of working for those who are stock and rooted with no custom or kernel recovery and just want OTAs. It has also been reported to work with stock, custom kernel and/or recovery and even those with custom ROMS (but if you have custom ROM, OTAs should not be your priority
These methods have been tested with i337 (US Version) and i337m (Canadian Version) and have been, for most, a permanent solution.
You can start by Method 1 or 2, ONLY USE METHOD 3 or 4 as a final solution as it has a danger of hard-bricking your device.
Method 1:
REPLACE SUPERUSER WITH SUPERSU BEFORE YOU DO THIS!!!
Step 1: Download ES File Explorer
Step 2: Open ES and press Menu key on phone (grant root when asked)
Step 3: Click Tools -> Root Explorer
Step 4: Click Mount R/W and select RW for all options and click OK
Step 5: Click / on top
Step 6: Navigate to System -> xbin and delete Busybox
Step 7: Reboot x2
Step 8: Once that OTA comes, simply use rootkeeper to freeze it up, update and restore root
Method 2:
Root with motochopper
Step 1: Download ES File Explorer
Step 2: Open ES and press Menu key on phone (grant root when asked)
Step 3: Click Tools -> Root Explorer
Step 4: Click Mount R/W and select RW for all options and click OK
Step 5: Click / on top
Step 6: Navigate to System -> xbin and delete Busybox
Step 7: Install SuperSU, let it update binary and remove other superuser app
Step 8: Went into SuperSU settings and un-check "Enable Superuser"
Step 9: Reboot x2
Step 10: Once that OTA comes, simply use rootkeeper to freeze it up, update and restore root
Method 3:
THIS IS A DANGEROUS OPERATION AND COULD POTENTIALLY BRICK YOUR DEVICE. PROCEED AT YOUR OWN RISK. A USB JIG IS PREFERRED IF YOU HAVE A WORKING ONE.
( and by brick I mean brick - only a board replacement or a JTAG unit will be able to save you, don't mess with boot(loader) stuff unless you really mean it! )
REPLACE SUPERUSER WITH SUPERSU BEFORE YOU DO THIS!!! This method only works on stock firmware & recovery.
Step 1: Download Triangle Away from playstore
Step 2: Open and grant root
Step 3: Confirm your device
Step 4: Download Add-On
Step 5: Hit "Reset Flash Counter"
Step 6: Once it reboots, hit "Volume Up" to reset flash counter
Method 4:
Special thanks to Aou, [email protected] and dwitherell
This method is a sure method. This eliminates the source of the custom status itself. SysScope is the system app that scans for files that are potentially on a custom phone, once one of those files is detected, it triggers the "Custom Status" and lock at boot. This method eliminates that scanner. It's possible that you already have to have an Official status for this to work, the OP of the thread will look into the issue, please follow his thread closely for more info
Step 1: Head over to the "Removing SysScope Thread" in the dev section or just click the link and follow his instructions
Step 2: Thank Aou
Thanks to everybody that has given their feedback and help develop this thread into a multi-method solution.
Credit to: haloimplant (for method 2), Chainfire (for method 3), Aou [email protected] and dwitherell (for method 4)
I hope one of these has works for you, Thumbs up if it did!:good:
I just tried it here and it didn't work. I followed your instructions to a T
thats because you're not stock, you have custom recovery
Ok. I didn't have it when it was stock.
Didn't work for me either. I don't have a recovery, I'm just on rooted stock
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
If you're talking about padlock and "custom" on the boot screen I still have it as well. Just rooted, stock with no recovery.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Worked for me. I'm simply rooted w/unlocked sim, no other mods. Thanks OP!
yungskeeme said:
If you're talking about padlock and "custom" on the boot screen I still have it as well. Just rooted, stock with no recovery.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
As far as i'm concerned, the "Padlock" is related to a locked bootloader because canadian S4s don't have it, we just get a custom status. There are a multitude of thread that explain how to get rid of the padlock, i think you just have to install SuperSU, update the binaries and uninstall superuser and reboot twice. That or you can simply root the Mr_Qs modded motochopper that bypasses superuser, i couldnt find the thread where he link his version of the tool so i've uploaded my copy to my dropbox, here is the link
https://dl.dropboxusercontent.com/u/4937149/motochopper_modified_supersu.rar
polish_pat said:
Now, once that OTA comes, simply use rootkeeper to freeze it up, update and restore
This has worked flawless, any other method of rooting, unrooting and rooting again, or flashing firmware with ODIN and rooting again, and a bunch of other stuff, nothing worked,
:
Click to expand...
Click to collapse
Worked on my 32Gb i337.
Nice, i'm glad to hear it. Also i was able to try this on an ATT version and it worked perfectly the first time.:good:
I tried it on mine, I am running a custom recovery. It didn't work, but I appreciate the info!
Sent from GT-I9505 transformed SGH-I337
yeah, this only works on stock recoveries, cause you dont really need an official status of you have a rom, official is really only to get OTAs
In an interesting turn of events, the busybox method i originally posted seems to have worked well, but something in my 64GB SD card keep triggering my status to custom. Every time i take out my SD and reboot, the status becomes official, but when i boot with my SD in, it's custom. I dont know what could do that, the only thing i have on my SD is music that was synced up using isyncr. Can isyncr be the cause of all this??
You can use the method above..and it works...but if you are going to start flashing roms..that screen will return...whats the big deal. I like it better than the original galaxy screen...
TheAxman said:
You can use the method above..and it works...but if you are going to start flashing roms..that screen will return...whats the big deal. I like it better than the original galaxy screen...
Click to expand...
Click to collapse
What?? No. I dont get why you're saying this...you obviously have not read this thread.
Which way is the most prefered to get rod of mister custom screeno?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
polish_pat said:
What?? No. I dont get why you're saying this...you obviously have not read this thread.
Click to expand...
Click to collapse
Why do you really care about the custom screen..just curious?
If you do not want it there..return to stock and and do not root.
galaxyS4fandom said:
Which way is the most prefered to get rod of mister custom screeno?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Nothing works 100%. In other news, "Rod of Mister Custom Screeno" would be a great name for a band
alacrify said:
Nothing works 100%. In other news, "Rod of Mister Custom Screeno" would be a great name for a band
Click to expand...
Click to collapse
+1..rock an roll.
alacrify said:
Nothing works 100%. In other news, "Rod of Mister Custom Screeno" would be a great name for a band
Click to expand...
Click to collapse
Haha gotta love fat fingers and auto correct.... but youre right... excellent name! Ima trademark it xD
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Related
Assuming the phone is already unlocked?
Could not find a way... please help!
Assuming your boot loader was already unlocked, you can use abd to install a custom recovery and flash the latest superuser zip file. The SU zip is on here but I'm on my phone at the moment so you'll have to do a little searching.
That happens. Simply root your phone again using superuser.
Here is the page:
http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/
Follow the part after the how to unlock bootloader.
Thank you, but...
I did that, put again the super user app after flashing the recovery, but it doesn't seem to work.
The super user app is still there, but it doesn't give su permissions...
(for instance, in ROM MANAGER it can't get permissions and also in a terminal doing "su")
Okay are you sure your phone is rooted?
If your answer is yes, click the superuser app. Once in there, there should be a ROM Manager logo in apps. Click that and check your status. The status should be allowed. If not on the bottom left click the button with an android face and a grey line in the middle. That will allow the app. Visa versa if you want to deny. Now just to confirm, go back to your main superuser page. Swipe left to go into log and your recent entry should be allowed for rom manager.
Now heres a tip. Back up your current rom and everything you want. Play around with the settings and apps so you know in the future what "this, that" is. If you stuff up, it doesnt matter. You have a backup. Just restore that in recovery.
dosnt work :/
the allow option doesnt work. perhaps there should be a different su file for
this version...
You may try to uninstall super user and reinstall it again. I had similar issue. And it was fixed by doing so. But I am not sure if it works for you. Good luck, mate.
Sent from my Nexus S using xda premium
danagu said:
the allow option doesnt work. perhaps there should be a different su file for
this version...
Click to expand...
Click to collapse
Google search superuser 3.0.7 and flash it while in recovery. You shouldn't have a problem unless your root process went wrong somewhere.
Sent from my Nexus S 4G using Tapatalk
Thanks!
I installed a new version and it worked
Hi guys since today im a proud owner of a Galaxy Note 10.1 N8000 stock 4.1.2, but now comes the question, is it possible to Root it without flashing anything?
I only need root access to install a few apps, FolderMount, Titanium, Root explorer, etc.
I own too a Galaxy S2 that I rooted by the method of "rooting without flashing unsecure kernel" is it possible to apply the same method to the Note 10.1?
THANKS for any help given.
pedrohell said:
Hi guys since today im a proud owner of a Galaxy Note 10.1 N8000 stock 4.1.2, but now comes the question, is it possible to Root it without flashing anything?
I only need root access to install a few apps, FolderMount, Titanium, Root explorer, etc.
I own too a Galaxy S2 that I rooted by the method of "rooting without flashing unsecure kernel" is it possible to apply the same method to the Note 10.1?
THANKS for any help given.
Click to expand...
Click to collapse
Welcome to the club. Take a look at all the sections for the tablet and make sure you read the stickies too.
Method #2 and youl be good to go.
http://forum.xda-developers.com/showthread.php?t=1831152
I had already read that stickie and if I have correctly read, Method 2 (and the others) involves Odin and flashing something and that is what I dont want.
Isnt there a way to root without flashing?
pedrohell said:
I had already read that stickie and if I have correctly read, Method 2 (and the others) involves Odin and flashing something and that is what I dont want.
Isnt there a way to root without flashing?
Click to expand...
Click to collapse
Let me ask you this, why no flashing? As far as I know it's either Odin or flash. You need to get a custom recovery on it in order to root.
---------- Post added at 05:31 PM ---------- Previous post was at 05:30 PM ----------
Also with the s2 the recovery and kernel are in one. This is not.
Thanks for your help and time spent helping me, but I think I will pass the root on the Note, I thought there was a more easier/safe method like that on the S2.
Thanks
pedrohell said:
Thanks for your help and time spent helping me, but I think I will pass the root on the Note, I thought there was a more easier/safe method like that on the S2.
Thanks
Click to expand...
Click to collapse
No problem, but it don't get any easier than odin or recovery.
pedrohell said:
Thanks for your help and time spent helping me, but I think I will pass the root on the Note, I thought there was a more easier/safe method like that on the S2.
Thanks
Click to expand...
Click to collapse
There was an Exynos exploit method but Samsung patched the security hole a few updates ago.
The method in the link that was posted does alter your flash count and that can be correct but you are the owner of the device and if you are not comfortable flashing you tablet I wouldn't.
I have flashed mine and tried a few rom's but I always ended up resetting my flash counter and going back to stock.
Folder mount works great and that was the reason I rooted in the first place but you can store your files on the ext drive and transfer them back and forth manually but I found with my fast wifi I'm better off re-downloading the data along with "Helium - App Sync and Backup" to backup and restore my data and you do not need root, only draw back is that you have to have a computer connection for backup and restore to work.
.
Yes, its just a matter of not feeling confortable, and there is also the risk of blocking the camera. (had a similar issue with 4.1.2 on S2 needed to downgrade to 4.0.4).
But it seeems to me a bit odd that to grant root access we need to flash the rom.
I don't think you read that right. You're not flashing a ROM, just a custom recovery through ODIN, then a root app. It's actually very simple. (Any simpler and I would be concerned about rogue app exploits)
Fyi: I'm also new to Samsung devices and bought my tablet this week. Rooted it this morning by following the stickies, but sticking with the stock ROM for now. I'm more than happy with the tablet so far.
Sent from my GT-N8013 using xda app-developers app
pedrohell said:
Yes, its just a matter of not feeling confortable, and there is also the risk of blocking the camera. (had a similar issue with 4.1.2 on S2 needed to downgrade to 4.0.4).
But it seeems to me a bit odd that to grant root access we need to flash the rom.
Click to expand...
Click to collapse
There is no flashing a rom with method 2. You Odin the custom recovery then you have to flash the superuser into the system. You need superuser to get root and Odin is the easiest way.
Trust me we have all been in your shoes about being nervous, I've been doing this a long time and this method is really easy.
You can also use this method - http://forum.xda-developers.com/showthread.php?t=1957002
It does require ODIN but as has been stated this is the norm. You are not replacing any kernels or flashing another rom, you are just adding the root components. Using this method also leaves stock recovery intact...
If you woory about flash counter then run triangleaway after to reset the flash counter and recoveries....
I found doing this, doing a factory reset from settings then reflashing the Stock rom using Mobile ODIN pro gave me a stock standard, but rooted, rom with all statuses "Official" and 0 flash count....
A lot of work I know but then worthwhile things generally require it...
Ok, I followed the Method 2 made everything like on video, after pressing Power+Volume Up, I entered on STOCK Recovery, not the CWM,even so, I apply the .zip and I get:
MANUAL MODE
--Appling Multi-CSC....
Applied the CSC-code:LUX
Successfully applied multi-CSC.
--Install /sdcard....
Finding update package....
Opening update package....
Verifying update package.....
E:FAILED TO VERIFY WHOLE-FILE SIGNATURE
E:FAILED TO VERIFY WHOLE-FILE SIGNATURE
E:signature verification failed
I also retryed and turned off auto-reboot in Odin before starting the process but I get the same thing, now what should I do?
Its not rootable?
Ok, Its finally rooted, What I had to do,
On Odin unthick auto-reboot, When Odin finished doing its thing, dont shutdown the Tablet but press Power+Volume Up and go directly to CWM recovery and there follow the rest of instructions.
Thanks to everybody that took time to help me, thats why I love this forum.
A BIG THANK YOU.
pedrohell said:
I had already read that stickie and if I have correctly read, Method 2 (and the others) involves Odin and flashing something and that is what I dont want.
Isnt there a way to root without flashing?
Click to expand...
Click to collapse
I see that I'm probably too late now to answer the OP.
But maybe others can be interested.
I find that the easiest way to root (without odin and without installing a custom recovery) is Framaroot.
It uses some Exynos exploits, and has been also recently updated by the developer to counteract Samsung's patches.
It may work or it may not work on some devices and with some of the more recent firmware.
In any case giving it a try doesn't cost anything. It's just an app.
If it works the app can also be used to temporarily remove the root.
For me it worked with Firmware N8000XXCLL3 and I know that it works with some more recent fw too.
Furthermore it doesn't change the counter and even the Devices Status remains "Official". Well, actually the devices status may change to "Custom" after few days with the tablet on, but it returns Official after a simple reboot.
pedrohell said:
Ok, Its finally rooted, What I had to do,
On Odin unthick auto-reboot, When Odin finished doing its thing, dont shutdown the Tablet but press Power+Volume Up and go directly to CWM recovery and there follow the rest of instructions.
Thanks to everybody that took time to help me, thats why I love this forum.
A BIG THANK YOU.
Click to expand...
Click to collapse
Awesome to hear! I ran into the same thing you did, forgot to go straight to recovery from odin.
Enjoy!
Stuck
Please help..
I get this error when i try to install: View attachment 2066244
What did i do wrong ?
brix696 said:
Please help..
I get this error when i try to install: View attachment 2066244
What did i do wrong ?
Click to expand...
Click to collapse
I don't use CWM, but see if there is a signature seeing to turn it off. Also make sure your md5 of the zip is correct.
brix696 said:
Please help..
I get this error when i try to install: View attachment 2066244
What did i do wrong ?
Click to expand...
Click to collapse
What were your options on the page right before that? What option did you select to initiate that?
Maybe try using the files from here instead:
http://droidviews.com/2013/root-and...ung-galaxy-note-10-1-n8000-n8010-n8013-n8020/
bigtoysrock said:
I don't use CWM, but see if there is a signature seeing to turn it off. Also make sure your md5 of the zip is correct.
Click to expand...
Click to collapse
Where should i look for a signature ? I have downloaded the file 3 times, just to manke sure that i wasen't bad.
Before that, it was the page where i choose "apply update from external storage"
I have tryed the CF, still the same
brix696 said:
Where should i look for a signature ? I have downloaded the file 3 times, just to manke sure that i wasen't bad.
Before that, it was the page where i choose "apply update from external storage"
I have tryed the CF, still the same
Click to expand...
Click to collapse
I would use the touch cwm, and what rom are you trying to install?
I've never rooted a device, but have found an app I need that requires root access. So, before going through with the process, I just want to cover my bases to make sure I don't end up with a bricked device. So, first, a few questions:
- Is unlocking the bootloader the same thing as rooting? Are the terms synonymous, or are they two separate things? If the latter, which comes first?
- Do I need to back up my apps somewhere before going through the process? In other words, does rooting wipe the phone? If so, can I still download the apps that are stored in "My Apps" in Google Play?
- After rooting, will I still have access to and be able to download apps from Play?
- Does rooting make the device more vulnerable to viruses and malware attacks? No change from unrooted?
- Are there any general risks or drawbacks to rooting (aside from the potential of bricking the device)? Any standard functionality I lose by rooting?
Finally, I found ChainFire's root process. Seems to be pretty simple/straightforward. Is that all I need to do to gain root access? Anything else I should be sure to do?
Thanks!
Have you read the stickies at the top of this forum and the top of general? All your answers are there.
flick0416 said:
I've never rooted a device, but have found an app I need that requires root access. So, before going through with the process, I just want to cover my bases to make sure I don't end up with a bricked device. So, first, a few questions:
- Is unlocking the bootloader the same thing as rooting? Are the terms synonymous, or are they two separate things? If the latter, which comes first?
- Do I need to back up my apps somewhere before going through the process? In other words, does rooting wipe the phone? If so, can I still download the apps that are stored in "My Apps" in Google Play?
- After rooting, will I still have access to and be able to download apps from Play?
- Does rooting make the device more vulnerable to viruses and malware attacks? No change from unrooted?
- Are there any general risks or drawbacks to rooting (aside from the potential of bricking the device)? Any standard functionality I lose by rooting?
Finally, I found ChainFire's root process. Seems to be pretty simple/straightforward. Is that all I need to do to gain root access? Anything else I should be sure to do?
Thanks!
Click to expand...
Click to collapse
1. Unlocking the bootloader is just that - giving you access to the partitions on the phone. Gaining root access is like having administrator privileges on a Windows PC - you can install/do anything to the OS
2. Unlocking the bootloader wipes the phone, rooting does not (as the phone is already unlocked)
3. Yes, although some apps don't work on a rooted phone
4. Of sorts, yes, but so long as you're careful you'll be OK
5. Not really, and you'll usually gain functionality if you move to a custom ROM
I hadn't
rootSU said:
Have you read the stickies at the top of this forum and the top of general? All your answers are there.
Click to expand...
Click to collapse
I hadn't, but since you pointed it out, I'm finding abaaaabbbb63's FAQ post to be helpful. Thanks for the direction.
flick0416 said:
I hadn't, but since you pointed it out, I'm finding abaaaabbbb63's FAQ post to be helpful. Thanks for the direction.
Click to expand...
Click to collapse
No probs.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Thanks
EddyOS said:
1. Unlocking the bootloader is just that - giving you access to the partitions on the phone. Gaining root access is like having administrator privileges on a Windows PC - you can install/do anything to the OS
2. Unlocking the bootloader wipes the phone, rooting does not (as the phone is already unlocked)
3. Yes, although some apps don't work on a rooted phone
4. Of sorts, yes, but so long as you're careful you'll be OK
5. Not really, and you'll usually gain functionality if you move to a custom ROM
Click to expand...
Click to collapse
Thanks for the info. Also, regarding #3, how do you tell if an app <i>won't</i> work on a rooted phone? Just trial and error?
Also
Is ChainFire's process the easiest way for me to get what I need (namely, root access to download an app)?
flick0416 said:
Is ChainFire's process the easiest way for me to get what I need (namely, root access to download an app)?
Click to expand...
Click to collapse
I have always done the following:
1. Unlock bootloader (make sure you back up any files on your phone before hand as they WILL be deleted)
2. Flash CWM/TWRP (I've always been a CWM man myself, but it's your choice) through fastboot using 'fastboot flash recovery recovery.img' - where 'recovery.img' is the name of the file you downloaded. I always rename mine 'recovery' purely for ease of use
3. Boot the phone and copy this to the phones memory - http://download.chainfire.eu/365/SuperSU/UPDATE-SuperSU-v1.69.zip?retrieve_file=1
4. Boot into CWM/TWRP and flash the file you've just copied to the phone
5. Reboot and enjoy!
Haha
EddyOS said:
I have always done the following:
1. Unlock bootloader (make sure you back up any files on your phone before hand as they WILL be deleted)
2. Flash CWM/TWRP (I've always been a CWM man myself, but it's your choice)
3. Boot the phone and copy this to the phones memory - ttp://download.chainfire.eu/365/SuperSU/UPDATE-SuperSU-v1.69.zip?retrieve_file=1
4. Boot into CWM/TWRP and flash the file you've just copied to the phone
5. Reboot and enjoy!
Click to expand...
Click to collapse
Haha, that's way above my head. I'll try to break down what you said:
1. This is done by turning the phone off, then holding Power + Volume down, correct?
2. Are these custom ROM's? I don't really care about a custom ROM right now, just having root access.
3. When you say Boot, do you mean turn it off again, then turn back on normally? Also, would I turn it off again after copying the SuperSU file?
4. No idea what you mean by this.
5. Getting there slowly...
flick0416 said:
Haha, that's way above my head. I'll try to break down what you said:
1. This is done by turning the phone off, then holding Power + Volume down, correct?
2. Are these custom ROM's? I don't really care about a custom ROM right now, just having root access.
3. When you say Boot, do you mean turn it off again, then turn back on normally? Also, would I turn it off again after copying the SuperSU file?
4. No idea what you mean by this.
5. Getting there slowly...
Click to expand...
Click to collapse
1. Check this thread out - it outlines the entire process http://forum.xda-developers.com/showthread.php?t=2507905
2. No - that is custom recovery that you need to perform nandroid backups (full system backup)
3. Yes
4. Go back into your newly installed recovery (step 2) to install the SuperSU file
But again, check out the link I provided above - fairly straightforward.
jj14 said:
1. Check this thread out - it outlines the entire process http://forum.xda-developers.com/showthread.php?t=2507905
2. No - that is custom recovery that you need to perform nandroid backups (full system backup)
3. Yes
4. Go back into your newly installed recovery (step 2) to install the SuperSU file
But again, check out the link I provided above - fairly straightforward.
Click to expand...
Click to collapse
OK cool, I think it's all starting to make sense. I could really accomplish the same end result without flashing a custom recovery, right? I most likely will flash a custom recovery, but as I understand it, a customer recovery isn't an essential part of the process, correct? The essentials are:
1) Unlock bootloader
2) Copy the SuperSU file to the phone
3) Boot back into recovery mode, flash the SuperSU file
Is that accurate?
flick0416 said:
OK cool, I think it's all starting to make sense. I could really accomplish the same end result without flashing a custom recovery, right? I most likely will flash a custom recovery, but as I understand it, a customer recovery isn't an essential part of the process, correct? The essentials are:
1) Unlock bootloader
2) Copy the SuperSU file to the phone
3) Boot back into recovery mode, flash the SuperSU file
Is that accurate?
Click to expand...
Click to collapse
That is correct. Only 'issue' is that you won't be able to take a full system backup (aka nandroid) before rooting.
(make sure that after you start your phone up after step 3, and get your accounts set up, update the SU app from the play store - new vulnerabilities were fixed)
jj14 said:
That is correct. Only 'issue' is that you won't be able to take a full system backup (aka nandroid) before rooting.
(make sure that after you start your phone up after step 3, and get your accounts set up, update the SU app from the play store - new vulnerabilities were fixed)
Click to expand...
Click to collapse
Cool, thanks. Would it be correct to say that Chainfire's thing automated steps 2 and 3?
flick0416 said:
Cool, thanks. Would it be correct to say that Chainfire's thing automated steps 2 and 3?
Click to expand...
Click to collapse
not sure which thing you are referring to - chainfire developed the SU app. Not sure what automation you are referring to.
In my opinion, run those commands manually - not that complicated, and you know what it is doing
jj14 said:
not sure which thing you are referring to - chainfire developed the SU app. Not sure what automation you are referring to.
In my opinion, run those commands manually - not that complicated, and you know what it is doing
Click to expand...
Click to collapse
This. The CF-Auto Root.
flick0416 said:
This.
Click to expand...
Click to collapse
yep - it should
jj14 said:
yep - it should
Click to expand...
Click to collapse
Alright cool, thanks. Now that I feel like I have a better conceptual understanding of what each step is doing, I think I'd rather go through it manually, too.
flick0416 said:
Alright cool, thanks. Now that I feel like I have a better conceptual understanding of what each step is doing, I think I'd rather go through it manually, too.
Click to expand...
Click to collapse
This is the important thing - read up and make sure you understand what you're doing and be comfortable with it all. Once you do it a few times it becomes second nature
an advice which came useful to me:
use original usb cable!
i've spent hours by trying to install custom recovery after unlocking bootloader.. tried number of times but having the error logo while booting to recovery.. then switched to original usb cable and everything worked fine at first attempt.
maybe this will helps =)
Recovery is important
I'd suggest this procedure:
1) Unlock bootloader
2) Copy the SuperSU file to the phone
3) Boot back into recovery mode, flash the SuperSU file
4) Flash a recoverylike cwm
FINALLY SUCCESS !! This is how I did it. Download ->..*Kingroot 4.5 apk*.. After you install is press the circle button it will then root your Tab.. But then we need to get rid of Kingroot and all of it dependencies. What you want to do is download busybox install, open and grant root access to busybox through King root, make sure to hit the install button at the bottom of the busybox app . After that go to play store download *Supersume*..... Yes Supersume! After you install Supersume open it it and click on the button and it will install Supersu with the binaries updated and uninstall all of King root dependencies for you. Okay now we have supersu installed, now for the tricky part. You do not want to reboot your phone or you will lose supersu and have to start from the beginning. I repeat do not reboot your device yet... Go to play store download and install Flashfire apk by Chainfire and then go to XDA Supersu tread by Chainfire and download the latest flashable Supersu.zip.. Okay now that we have those two things, go back and open up Flashfire app and look for where it says OTA firmware / zips click that button and look for your Supersu.zip that you downloaded from XDA click on it an hit the check mark at the top.. Now look for where it says *Ever root* click on that make sure to hit the check mark at the top. FIND reboot and make sure that normal is checked click on the check mark at the top and that will take to back out to where there's a circle and lightning bolt Press that... Flashfire is now flashing the new Supersu. Zip for you and also inject root into your system via Ever root.... Once it reboots you will have the latest supersu and be able to reboot without losing root. This does not trip Knox.. Have fun and hit the thanks button if it helped. But please give thanks to those who made the apps King root, Supersume, Busybox, Supersu and Flashfire.. Because without those Developer's this would not be possible..
I can verify this roots the t217a. I had to unmount my sdcard and do the flashfire option to get su to stick but it did and does work. Hopefully we can get a recovery and toms now. This is a nice little tablet for free since I use it tethered through tmo and got it as payment for moving files from one laptop to another with a usb stick lol
If you havnt checked yet KNOX is still intacted.. So it doesn't trip KNOX. Which means warranty is still available if your still covered.. Also, I'm going to message Chainfire to find out if it is possible to create a Odin flashable Backup using some of the file's I have from my Flashfire Backup.. If it is possible we will have a way to recover from a boot loop or a softbick for that matter.. If so I will Experiment with flashing T-Mobile or the International TouchWiz Custom Roms using Flashfire.. I have two AT&T note 3's and I have had success installing T Mobile and international roms on both devices, if I'm not mistaken even a few Sprint custom TouchWiz Roms work on those phone's.. We have everything needed to have a Custom TouchWiz Rom except a restorable Backup.... Keep your eyes on development for this tab cause if I manage to get one to Load an that Runs well I will ask permission to post their Rom with a how to for At&t Tab 3...
Thanks for the hard work, if I can help please let me know.
Hey is there anyway to get 442 to directly save to the external sd card with the os as is?
I think I tripped Knox. My tablet boots up with the Samsung logo and "CUSTOM" underneath it and I can't find anything Knox related in settings now
No you didn't trip Knox... Mine also had the Custom pad lock when booting up.. If you would like to get rid of it just download and install xposed framework. After you install it open the xposed app and look for downloads, there you will find an app called Wanam Xposed. Open that app and look for security hacks, click on that and you will see where it says firmware status official or custom make sure its check marked. That will make your firmware official and get rid of the padlock after two reboots. If you would like to check your Knox you can download Samsung Phone Info apk I use the plus version but the free one should have you're Knox info also. Hope that helps.
Ok cool. Is there a recovery yet?
Does this add twrp or is just for rooting?
Sent from my Nexus 6 using XDA Free mobile app
azz72 said:
Does this add twrp or is just for rooting?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
As far as I know, the bootloader is locked so there won't be any custom recovery unless that is unlocked.
PLAY POKEMON GO WITH ROOT SWITCH NEW METHOD (CANT BE PATCHED)
i did this on my samsung s7 edge g935f and have not tested on anything else but should apply across the board realy
before we get started
u will need to have your phone at stock with no root and pokemon go working on that stock rom
(been trying on lots of note 7 port roms with no look hopefuly crack that one day)
IF U ARE NOT DOING THIS ON A SAMSUNG INSTALL TWRP ON YOUR DEVICE AND START AT STEP 5 IT WILL WORK
AND I MANAGED TO GET THIS TO WORK WITH EVERY COUSTEM ROM TO IF ANYONE WOULD LIKE ME TO ADD SUPORT FOR THAT PLZ LET ME KNOW
STEP ONE
download all files
no-verity-opt-encrypt-2.1.zip
https://drive.google.com/file/d/0B6bGIsDu5O5pV3JkX2JUV290MEU/view
systemless super su
https://drive.google.com/file/d/0B6bGIsDu5O5pbWNHSFJEQjhLY2s/view
coppy them two to a micro sd card and put in your phone
samsung smart switch for pc
http://www.samsung.com/uk/smart-switch/samsung-desktop-app.html
twrp for g935f ONLY
download the one for your device
https://drive.google.com/file/d/0B6bGIsDu5O5pMnRfRmxUYThWZ1E/view
odin
https://drive.google.com/file/d/0B6bGIsDu5O5pbGlobkVTZWFkYmM/view
for use on pc
STEP TWO
on your phone go to settings/about phone/software info/ and tap the biuld number 5 times to unlock developer options
and and go into developer options turn on usb debuging and and oem unlock
STEP THERE
install smart switch (only used for the phones drivers) and extract odin and run it click on the ap tab and load the twrp and click start
and instal twrp and w8 for reboot and boot stright to twrp (vol-up and power and home)
STEP FOUR
insatl no-verity-opt-encrypt-2.1.zip in twrp from the instal tab and reboot after and instal pokemon go and test it (if working carry on)
STEP FIVE
boot into twrp again and go to the backup tab. untick everythin but boot(40mb) select storage as sd card and swipe to back up then reboot
on your phone go to myfile and go to sd/twrp and find your backup it will begin with a date and rename that folder to stock
STEP SIX
boot back into twrp and install super su system less DONT reboot.
go back and backup boot only again then reboot
go to myfile again and go to sd/twrp and find your backup it will begin with a date again and rename that folder to root
not u can switch between stock and root just b flashing tho boot files and takes seconds
i have been useing this for days now and u can istall as mennt root apps as u like aslong as u flash the stock boot it will allways let u use any app thats blocks root
thank you this is the fist time i have releced my of work due to not being able to read and wright
Got it working on the note 7 port Rom
I'm on a Note 5 and going to give this a try using my version of TWRP. Will edit this post and report findings!
Able to boot after flashing the first .zip. Always got boot loop previous after flashing TWRP but not flashing root! Thanks for the solution!
Basically the minimum I want is the ability to remove my boot sound and update my hosts file. This lets me do that but otherwise be stock. Good enough. Wish I had xposed, root, but still Android Pay and PGO without reboots but that's ok.
henderjr said:
I'm on a Note 5 and going to give this a try using my version of TWRP. Will edit this post and report findings!
Able to boot after flashing the first .zip. Always got boot loop previous after flashing TWRP but not flashing root! Thanks for the solution!
Basically the minimum I want is the ability to remove my boot sound and update my hosts file. This lets me do that but otherwise be stock. Good enough. Wish I had xposed, root, but still Android Pay and PGO without reboots but that's ok.
Click to expand...
Click to collapse
If u need a hand let me know
I can not install "no-verity-opt-encrypt-2.1.zip" it says :
"Error: Unpacking boot image failed!"
I am using Note 4 (N910c)
Update : so i have learned that i dont need no-verity-opt-encrypt-2.1.zip
my phone dos not have encryption so i basically skipped that step and *bang* i am rooted and can play pokemon. Thanks much
Is this working on android nougat?
Thx
psxcis said:
Is this working on android nougat?
Thx
Click to expand...
Click to collapse
Anyone tried this yet? im itching to root my pixel xl but cant live without pokemon go and snapchat
Souler19 said:
Anyone tried this yet? im itching to root my pixel xl but cant live without pokemon go and snapchat
Click to expand...
Click to collapse
works fine if the root u use is systemless
Tut for pixel and pixel xl
http://www.androidpolice.com/2016/10/29/chainfire-releases-systemless-root-method-pixel-pixel-xl/
TLEAF-TOM-LEE said:
works fine if the root u use is systemless
Tut for pixel and pixel xl
http://www.androidpolice.com/2016/10/29/chainfire-releases-systemless-root-method-pixel-pixel-xl/
Click to expand...
Click to collapse
Can anybody confirm that this is true for me? I haven't seen anyone else mention this.
Hello, I would like your help.
First of all, sorry for my poor English.
I installed the Root Switch to use Pokemon Go, but my phone crashed and rebooted while I played. After that, I was not able to activate root again, including the SuperSU app says my cell does not have Root.
Does anyone know how I should proceed? Would redoing root solve my case?
Thank you.
Alison.Souza said:
Hello, I would like your help.
First of all, sorry for my poor English.
I installed the Root Switch to use Pokemon Go, but my phone crashed and rebooted while I played. After that, I was not able to activate root again, including the SuperSU app says my cell does not have Root.
Does anyone know how I should proceed? Would redoing root solve my case?
Thank you.
Click to expand...
Click to collapse
Yeah, just reroot and you will be fine
Sent from my SPH-L720 using Tapatalk
mattzeller said:
Yeah, just reroot and you will be fine
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Thanks mattzeller! It worked!
Just to clarify, this requires an unlocked bootloader correct? I am on the g930v with is locked.
Wetzel402 said:
Just to clarify, this requires an unlocked bootloader correct? I am on the g930v with is locked.
Click to expand...
Click to collapse
Yes that's correct
It looks like the Root Switch has stopped working, at least here on my S4 I9505 with Android 5.0.1.
Anyone else going through this?
Root Switch never work on my G900T S5 with Lollipop 5.1.1
There was a safetynet update last week that breaks RootSwitch. Had to go the Magisk route but now can use Android Pay along with PoGo