Im trying to root my n2 and odin gives this error, <ID:0/003> Can't open the serial(COM) port. What do I do? Also, my phone does not boot, it stays on the samsung screen.
You are in soft brick my friend, which I unfortunately i cant help you out of. I woukd edit your post and change the name to [Q] Soft Bricked Please Help....youll get more responses from smarter people than me. But dont worry, soft bricks are easily fixed....it just may take until the smart people wake up is all.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Probably going to need some more info. 1st, did you install the drivers prior to trying to root with Odin. 2nd, are you in download mode when Odin can't see the phone. 3rd, before attempting root did you do anything else to the phone. Let's start with that. Also try and pull the battery and boot the phone again to see if you continue to bootloop.
Also try a different cable
Sent from my SAMSUNG-SGH-I317 using xda premium
I followed this thread to the T. I ended up do a factory reset from the factory recovery. My phone boots now, and has su icon. Im not sure if it is really rooted though because the wifi tether app does not work and it asks me if Im rooted, not sure what state the phone is please reboot.
So you were successful with Odin or did you use another root method? Grab root checker from the market to see if you have root. If not, just grab CF's exploit apk to root or start over with auto root through Odin.
It says I do not have proper root access.
Here's the exploit apk thread. Use it to root then I would grab goo manager from the market to install twrp. After that, boot to recovery and make a backup.
http://forum.xda-developers.com/showthread.php?t=2050297
Will cwm touch work?
Sure. I just prefer twrp thats why I mentioned it. You can flash cwm with Odin or ROM manager, but I wouldn't use ROM manager for anything else. Do your backups and flashing manually in recovery.
So there is a chance my camera might not work? Also do I need to remove su from my current appst? I don't understand how this method linked above can be turned rooted access on and off? I please explain thx
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
The app takes advantage of an exploit to root. Rooting will not break your camera. If you use the patch after, it might. As far as Supersu...if you have the Superuser app, I would delete it as they are two different apps. If you have the Supersu then you can probably keep it. Most likely will overwrite it.
How do I delete su app? It will not uninstall through playstore. I guess I do not understand what the patch is. Ive never used a method like this.
The su app most likely installed as a system app so you can't remove it without root. Read through that thread I linked for more about the patch and the exploit. It would be too much to try to explain here. If you initially tried to use cf-auto root, then don't worry about removing su. It's the same developer and the same su app. Just use the app to root and apply the patch. Check your camera. If the screen is green then remove the patch to use the camera. It won't harm anything.
OK thanks for all the help. Hey, how do I unroot?
The supersu app can full unroot in settings.
Thats awesome! every root should be this simple. wifi tether still does not work. What do you recommend?
Wifi tether works for me natively, but I heard foxfi is good. No root needed for that one of course. Other than that I'm not too familiar with those apps.
playstore says foxfi is not available for my carrier. Are you paying for hotspot on your phone/?
Family bundle. It's included. I think you can grab foxfi from their website.
---------- Post added at 09:21 PM ---------- Previous post was at 09:19 PM ----------
At&t is probably blocking it in the playstore
Related
So I've ran into a huge problem or what seems like a huge problem to me. I just got a new Galaxy S3 16 GB from T-Mobile last Friday. Three days later, I rooted it. I used the instructions from this guy who I now think doesn't know what he's talking about.
Can't upload the link because I'm new but it's called "How to Root T-Mobile Galaxy S3 SGH-T999" by High On Android and it's on YouTube.
Now there's me all happy getting ready to have some fun with my new root. I try downloading a game in which I need to use Titanium Backup. It tells me that I'm not rooted. I go to Superuser and it says I'm not rooted. So now I go to Root Checker and you already know what it says.... NOT ROOTED! Now I'm thinking I should do that new software update that adds Google Wallet but it want allow it probably because it's sort of rooted. So I thought to myself maybe I should just unroot it and restart all over again so I go to some unrooting instructions. It tells me to download an app called TriangleAway which also tells me that I'm not rooted. So now I can't update software, use Kies, and at the same time, can't get any benefits from being rooted. What is the problem here and what do I do?
You don't need triangle away to Odon to stock
Sent from my SGH-T999 using xda premium
ktetreault14 said:
You don't need triangle away to Odon to stock
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I needed Triangle Away to remove root and I'm a noob to andoid so everything you said after triangle away flew past my mind.
Do you have a custom recovery?
psykhotic said:
Do you have a custom recovery?
Click to expand...
Click to collapse
I have no idea. I followed all instructions in this video if that helps you: Youtube Title: "How to Root T-Mobile Galaxy S3 SGH T999" by High On Android.
Try the toolkit.
It's simpler
Odin can be confusing at first
Sent from my SGH-T999 using xda premium
---------- Post added at 04:39 AM ---------- Previous post was at 04:38 AM ----------
http://forum.xda-developers.com/showthread.php?t=1746682
Sent from my SGH-T999 using xda premium
Watch the video in my signature. Impossible to mess it up.
Did you root it? We are here if you still need help.
Sent from my SGH-T999 using xda app-developers app
I've only used Odin once and found it very simple. Look for the guide that says no trip root method. All you do is simply download a stock rom that already has root injected in it. Unzip the file and you should now have some file called "root666....something".tar
Place phone in download mode. Connect usb to pc and launch Odin. Make sure the phone shows up in com window and there's 2 settings you need to select auto reboot and one other setting, its in the guide. The use pda and select the tar file and flash and the phone will automatically reboot when everything's done and you're good to go
Sent from my SGH-T999 using xda app-developers app
I followed the video and no problem. After doing odin for flashing the recovery did you boot into recovery and flash the zip file you were instructed to install? Since it is and older video you must update the super user app that you install from the play store. After updating the app open it and it will tell you it needs to install new binaries. To your phone.
Sent from my SGH-T999 using xda app-developers app
You checked "Yes this is a question"
Guess where it belongs?
Moved to Q&A
Friendly Neighborhood Moderator
Aerowinder said:
Watch the video in my signature. Impossible to mess it up.
Click to expand...
Click to collapse
Same guy from the other video I took instructions from. In the description it says "Here's how to root your Sprint Galaxy S3 SPH-L710 or T-Mobile Galaxy S2 SGH-T999 or AT&T Galaxy S3 SGH-i747!" I have a hard time following instructions from someone who has errors in their description in addition to following instructions from his other video and ending up posting a thread in this forum.
The SGH-T999 is the S3, so that's a typo. And I know it is accurate because it's how I rooted my phone months ago. In my signature I provide all information necessary to root, including updated files (the files he links to are outdated - use mine instead). I don't know what video you saw before, but I assure you, this one works.
Odin CWM > flash Superuser in CWM > rooted.
There are only two ways to root. This one is easier than flashing a pre-rooted firmware, wiping your data.
Aerowinder said:
The SGH-T999 is the S3, so that's a typo. And I know it is accurate because it's how I rooted my phone months ago. In my signature I provide all information necessary to root, including updated files (the files he links to are outdated - use mine instead). I don't know what video you saw before, but I assure you, this one works.
Odin CWM > flash Superuser in CWM > rooted.
There are only two ways to root. This one is easier than flashing a pre-rooted firmware, wiping your data.
Click to expand...
Click to collapse
I'm currently trying this method right now: http://forum.xda-developers.com/showthread.php?t=1746682
If that doesn't work I guess I'll try your method.
Android_Monsters said:
Try the toolkit.
It's simpler
Odin can be confusing at first
Sent from my SGH-T999 using xda premium
---------- Post added at 04:39 AM ---------- Previous post was at 04:38 AM ----------
http://forum.xda-developers.com/showthread.php?t=1746682
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
HUGE PROBLEM I get to the point where I get to Odin3 v3.07 but for some strange reason I can't do the part where I hit start because the whole bottom part of that window is hidden by the toolbar at the bottom(Windows 7). I ran into a similar problem on Kies where I couldn't install new firmware because the bottom part wasn't visible or hidden by the toolbar. What should I do?
I've seen this happen when changing font size from the Control Panel. "Accessibility" or "Ease of access". Could also be a custom theme. Can we get a screenshot of you running Odin?
Aerowinder said:
I've seen this happen when changing font size from the Control Panel. "Accessibility" or "Ease of access". Could also be a custom theme. Can we get a screenshot of you running Odin?
Click to expand...
Click to collapse
Nvrmind I hit the button using the Tab key. But now that I got done with all that I get to the part of going to Superuser and it never asks me to Allow or Deny. So then I install Titanium Backup and when I open it, instead of it asking me for root permissions it gives me this message:
"Sorry, I could not acquire root priviledges. This application will *not* work ! Please verify that your ROM is rooted and inlcudes BusyBox, and try again.
This attempt was made using the "/system/bin/su" command."
Using CWM Touch 6.0.1.2 (which is in my signature), flash Superuser 3.2 (which is also in my signature). I warned you against using the provided flashing tools from the YoutTube videos because they are outdated. Use the files in my signature. The CWM is the newest version available, as is the Superuser, which already contains the newest binaries. I didn't build these packages because I got bored, I built them because I needed them. And it looks like you do also.
You don't need to allow Superuser root access. Well, you may for some options within the app, but not for giving other apps root access.
This attempt was made using the "/system/bin/su" command."
Click to expand...
Click to collapse
I'm not sure what you mean by this, but if su is in /system/bin (it shouldn't be), then you need a symlink to /system/xbin. Or just flash the version I provide in my signature, which puts it in the proper place to begin with (it will remove the not working root app/binaries).
Also, if you have Set DNS installed, remove it. It has a tendency to prevent root access from working sometimes.
Aerowinder said:
Using CWM Touch 6.0.1.2 (which is in my signature), flash Superuser 3.2 (which is also in my signature). I warned you against using the provided flashing tools from the YoutTube videos because they are outdated. Use the files in my signature. The CWM is the newest version available, as is the Superuser, which already contains the newest binaries. I didn't build these packages because I got bored, I built them because I needed them. And it looks like you do also.
You don't need to allow Superuser root access. Well, you may for some options within the app, but not for giving other apps root access.
I'm not sure what you mean by this, but if su is in /system/bin (it shouldn't be), then you need a symlink to /system/xbin. Or just flash the version I provide in my signature, which puts it in the proper place to begin with (it will remove the not working root app/binaries).
Also, if you have Set DNS installed, remove it. It has a tendency to prevent root access from working sometimes.
Click to expand...
Click to collapse
Sorry, I actually meant to reply to Android_Monsters as I'm still using his method.
This takes two minutes, tops. You don't need the toolkit. The toolkit is very useful for sure (easy adb, for one; odin tar creation, etc.), but I think in this particular case, less is more. Also, the toolkit contains outdated CWM/Superuser.
You are trying to reinvent the wheel. Just borrow mine for crying out loud.
This is work in progress, have got some ideas to disable Knox(only if you are rooted). Will be updating this thread tomorrow after testing the steps on the loserskater 4.3 release.
This may work but only time will tell.
Don't forget to set SELinux to permissive
Remove the following files:
Code:
(along with any associated .odex files)
/system/app/ContainerAgent.apk
/system/app/ContainerEventsRelayManager.apk
/system/app/KLMSAgent.apk
/system/app/KNOXAgent.apk
/system/app/KnoxAttestationAgent.apk
/system/app/KNOXStore.apk
(entire folders)
/system/containers
/system/etc/secure_storage/com.sec.knox.store
(doubt this one is necessary)
/system/lib/libknoxdrawglfunction.so
And I'm not sure SELinux set to permissive is actually necessary. Been running enforced with root and haven't had any issues yet.
Root persisted through reboot?
mrhaley30705 said:
Root persisted through reboot?
Click to expand...
Click to collapse
Just removed knox, rebooted, restored TiBU, rebooted, and root is still intact.
That is very good to hear :thumbsup:
loserskater said:
Remove the following files:
Code:
(along with any associated .odex files)
/system/app/ContainerAgent.apk
/system/app/ContainerEventsRelayManager.apk
/system/app/KLMSAgent.apk
/system/app/KNOXAgent.apk
/system/app/KnoxAttestationAgent.apk
/system/app/KNOXStore.apk
(entire folders)
/system/containers
/system/etc/secure_storage/com.sec.knox.store
(doubt this one is necessary)
/system/lib/libknoxdrawglfunction.so
And I'm not sure SELinux set to permissive is actually necessary. Been running enforced with root and haven't had any issues yet.
Click to expand...
Click to collapse
Can i just rename this files ?
EDIT: I renamed and restarted. Root are present after restart..
loserskater said:
Just removed knox, rebooted, restored TiBU, rebooted, and root is still intact.
Click to expand...
Click to collapse
Have you or anyone else tried Root->freeze Knox in TiBu as an alternative?
stoobie-doo said:
Have you or anyone else tried Root->freeze Knox in TiBu as an alternative?
Click to expand...
Click to collapse
I tried this, but SuperSU is still crashing. So no root for apps that didn't get root access before you installed 4.3.
norbarb said:
Can i just rename this files ?
EDIT: I renamed and restarted. Root are present after restart..
Click to expand...
Click to collapse
Did you root with CF AutoRoot or Kingo?
Evilweasel47 said:
I tried this, but SuperSU is still crashing. So no root for apps that didn't get root access before you installed 4.3.
Click to expand...
Click to collapse
Update samsung security and SU will work. Just after SU FC go to notification and there is policy info, click on it and agree to update. After this SU should work just fine.
Sent from my GT-N8013 using XDA Premium HD app
---------- Post added at 01:39 PM ---------- Previous post was at 01:38 PM ----------
stoobie-doo said:
Did you root with CF AutoRoot or Kingo?
Click to expand...
Click to collapse
With CF-Auto
Sent from my GT-N8013 using XDA Premium HD app
norbarb said:
Update samsung security and SU will work. Just after SU FC go to notification and there is policy info, click on it and agree to update. After this SU should work just fine.
Sent from my GT-N8013 using XDA Premium HD app
---------- Post added at 01:39 PM ---------- Previous post was at 01:38 PM ----------
With CF-Auto
Sent from my GT-N8013 using XDA Premium HD app
Click to expand...
Click to collapse
One more q... are you having the same root behavior that others have had, i.e., previously authorized apps continue to work, but no new ones can acquire root?
stoobie-doo said:
One more q... are you having the same root behavior that others have had, i.e., previously authorized apps continue to work, but no new ones can acquire root?
Click to expand...
Click to collapse
I am able to authorize new apps. However after removing Knox supersu fcs. I do not receive a prompt as mentioned above.
stoobie-doo said:
One more q... are you having the same root behavior that others have had, i.e., previously authorized apps continue to work, but no new ones can acquire root?
Click to expand...
Click to collapse
No i did not notice this.. I just tryed app with root requairment and no problem. Everything working like before update.
Just wanted to add more information to the table
Yesterday after I found out that 4.3 finally released officially, I Odin'd back to stock and worked my way to 4.1.2, and then 4.3. So my phone is completely virgin, the way it would be if I just bought it and upgraded.
I Used CF-Auto Root to give me root and Superuser. The Odin flash did the job, it rebooted into recovery, did its dark magic, and started the phone normally.
As soon as the phone booted up, it FC. I ignored it, and proceeded to use root explorer to go rename the files given by Loserskater to remove Knox off the system.
As soon as I go to rename the first file, SU again crashes and I get a note about security policy needs to be update. Reading what other users were saying, I let it update.
It then blocked Super User. It won't open, and anything that tries to access it will crash (like using root explorer to do tasks that require root)
I said "Okay, maybe we'll try this again" Second flash of CF-Auto Root worked like it should. SuperUser is still blocked.
I factory reset the phone. SuperUser was there as soon as I boot up, and it FC immediately. Knox still had it blocked.
I was forced to turn off SU for now as to stop getting pop ups.
So, there has been my first few hours with Knox. Not very pleasant.
Any ideas?
tyrantsbane said:
Yesterday after I found out that 4.3 finally released officially, I Odin'd back to stock and worked my way to 4.1.2, and then 4.3. So my phone is completely virgin, the way it would be if I just bought it and upgraded.
I Used CF-Auto Root to give me root and Superuser. The Odin flash did the job, it rebooted into recovery, did its dark magic, and started the phone normally.
As soon as the phone booted up, it FC. I ignored it, and proceeded to use root explorer to go rename the files given by Loserskater to remove Knox off the system.
As soon as I go to rename the first file, SU again crashes and I get a note about security policy needs to be update. Reading what other users were saying, I let it update.
It then blocked Super User. It won't open, and anything that tries to access it will crash (like using root explorer to do tasks that require root)
I said "Okay, maybe we'll try this again" Second flash of CF-Auto Root worked like it should. SuperUser is still blocked.
I factory reset the phone. SuperUser was there as soon as I boot up, and it FC immediately. Knox still had it blocked.
I was forced to turn off SU for now as to stop getting pop ups.
So, there has been my first few hours with Knox. Not very pleasant.
Any ideas?
Click to expand...
Click to collapse
I think you have to agree to securituy polices before you remove/dissable/rename knox files.
Edit: i post pictures to see that my SU is working fine and no problem. I did what i post allover this forums.
ali3n8 said:
I am able to authorize new apps. However after removing Knox supersu fcs. I do not receive a prompt as mentioned above.
Click to expand...
Click to collapse
I think you can somehow agree to new polices before you remove knox files and in security in settings... (sorry but i don't realy know how). All i know you need to agree in order to SU work until someone will find some other way. I did same with my S4 and last update to 4.3 and twice to leak to on S3 MJ6.
BTW: I got sim card out on my S3 this maybe case and is wort to try.
tyrantsbane said:
Yesterday after I found out that 4.3 finally released officially, I Odin'd back to stock and worked my way to 4.1.2, and then 4.3. So my phone is completely virgin, the way it would be if I just bought it and upgraded.
I Used CF-Auto Root to give me root and Superuser. The Odin flash did the job, it rebooted into recovery, did its dark magic, and started the phone normally.
As soon as the phone booted up, it FC. I ignored it, and proceeded to use root explorer to go rename the files given by Loserskater to remove Knox off the system.
As soon as I go to rename the first file, SU again crashes and I get a note about security policy needs to be update. Reading what other users were saying, I let it update.
It then blocked Super User. It won't open, and anything that tries to access it will crash (like using root explorer to do tasks that require root)
I said "Okay, maybe we'll try this again" Second flash of CF-Auto Root worked like it should. SuperUser is still blocked.
I factory reset the phone. SuperUser was there as soon as I boot up, and it FC immediately. Knox still had it blocked.
I was forced to turn off SU for now as to stop getting pop ups.
So, there has been my first few hours with Knox. Not very pleasant.
Any ideas?
Click to expand...
Click to collapse
To revert back to a fresh state on 4.3 I had to CF autoroot to get the stock recovery installed. Then while in stock recovery I selected apply update from external sdcard. I have found that when using a custom recovery I was not able to go back to a stock 4.3 state. First boot after doing this will take a bit and may even require a reflash.
so...
Does anyone know how to reset the security policies so I can test some more methods?
Or do I need to Odin down again and trudge my way back up
tyrantsbane said:
does anyone know how to reset the security policies so i can test some more methods?
Or do i need to odin down again and trudge my way back up
Click to expand...
Click to collapse
do not use odin to downgrade after installing the ota!!! You will brick your phone
Ok,
I know this is a hot question but I am hoping someone can point me in the right direction. Stupidly, in hindsight, I let KIES update my SGH-I747M to 4.3. After it rebooted, SuperSU/Triangle Away, etc would not load or work. So, I tried using ODIN to put 4.1.2 back on but all attempts have failed so far as my counters are now at 3 and state is custom. Normally , I would run TriangleAway and all would be good. But SuperSU will no longer load and stick around so that I can run TriangleAway. I have not tried any other custom ROMs yet.
I have also used the latest SuperSU v1.80 but it does not stay installed and I cannot use Triangle Away to reset the counters. Anyone have any ideas on how to get SuperSU to work? That would allow me to reset the warnings and all would be great.
Marsch52 said:
Ok,
I know this is a hot question but I am hoping someone can point me in the right direction. Stupidly, in hindsight, I let KIES update my SGH-I747M to 4.3. After it rebooted, SuperUS/Triangle Away, etc would not load or work. So, I tried using ODIN to put 4.1.2 back on but all attempts have failed so far. I have not tried any other custom ROMs yet.
I have also used the latest SuperUS v1.80 but it does not stay installed and I cannot use traingle Away to reset the counters.
Anyone have any ideas on how to get SuperUS to work? That would allow me to reset the warnings and all would be great.
Click to expand...
Click to collapse
You have to re root your phone. Use cf auto root and when that's done find superSU in the play store and install/update it. Then open SUPERSU and when it asks you to disable knox say yes. Also update its binaries. Now you have root and you can use any root application you want.
Sent from my SGH-I747M using Tapatalk
Florad77 said:
You have to re root your phone. Use cf auto root and when that's done find superSU in the play store and install/update it. Then open SUPERSU and when it asks you to disable knox say yes. Also update its binaries. Now you have root and you can use any root application you want.
Sent from my SGH-I747M using Tapatalk
Click to expand...
Click to collapse
Ok... I see the path. just want to know where I can find the proper "cf auto root" files for the SGH-I747M. I will search the web again, but if you happen to have a pointer that would be great.
:fingers-crossed:
Success . . . . .
Marsch52 said:
Ok... I see the path. just want to know where I can find the proper "cf auto root" files for the SGH-I747M. I will search the web again, but if you happen to have a pointer that would be great.
:fingers-crossed:
Click to expand...
Click to collapse
I just did as you said and it updated SuperSU by itself, turned of KNOX and Voila!!!!!! :good: :good: :good:
THANK YOU!!!!!!! and Chainfire....need to donate to him for his excellent work
Florad77 said:
You have to re root your phone. Use cf auto root and when that's done find superSU in the play store and install/update it. Then open SUPERSU and when it asks you to disable knox say yes. Also update its binaries. Now you have root and you can use any root application you want.
Sent from my SGH-I747M using Tapatalk
Click to expand...
Click to collapse
I just did this and it keeps telling me "Unfortunately, SuperSU has stopped. And I'm pretty sure knox is preventing it..
NEVERMIND! Apparently it didn't update SuperSU automatically. Now it updated, normally updated binaries, rebooted, and checked root with Titanium Backup. All's good!
Hi I am new to this forum and a casual user. I wanted to root my note 2 tmobile android version 4.3 and actually rooted it once but knox created a lot of problem. I could not even launch titanium backup to freeze knox. Or was completely unable to disable knox. Now as android 4.3 has been released for quite a few months. Does anyone know of a method which will root my galaxy note 2 tmobile (SGH-T889) for sure and let me completely disable knox? If so please give me step by step instruction of rooting my device or alteratively you can provide me a link of the instruction so I can root my note 2 phone. I appreciate your help.
cooljd1 said:
Hi I am new to this forum and a casual user. I wanted to root my note 2 tmobile android version 4.3 and actually rooted it once but knox created a lot of problem. I could not even launch titanium backup to freeze knox. Or was completely unable to disable knox. Now as android 4.3 has been released for quite a few months. Does anyone know of a method which will root my galaxy note 2 tmobile (SGH-T889) for sure and let me completely disable knox? If so please give me step by step instruction of rooting my device or alteratively you can provide me a link of the instruction so I can root my note 2 phone. I appreciate your help.
Click to expand...
Click to collapse
cf auto root should work for root. what did you use to root? if you are rooted install a custom recovery and flash a knoxfree rom from the dev section
Flash CF auto root via Odin then download latest superuser from play store and you are ready to go.
All credits to ChainFire
Did you try this method, if so did it work for you? Im having similar issues with my tmobile note 2 running 4.3 too. I'd appreciate it, thanks in advance...
Sent from my SGH-T889 using XDA Premium 4 mobile app
J3D1mineTR1X said:
Did you try this method, if so did it work for you? Im having similar issues with my tmobile note 2 running 4.3 too. I'd appreciate it, thanks in advance...
Sent from my SGH-T889 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Just as a suggestion, something that happened to me while playing around with the phone: if you're running Stock rom and then flash a custom recovery via Odin (I used Philz Touch) upon booting on recovery just to wipe cache/dalvik I found something interesting: my phone wasn't rooted, so when chosing the option "reboot system now" a message that said something like "root is broken, would you like to root your phone before rebooting" appeared. I was curious, as I normally use a website called Kingo root that does it in a one-click kinda way. When I chose Yes in the recovery, upon booting my phone it was rooted. After, I just intalled Chainfire's SuperSU from the play store and it was all good.
It's worth trying I believe.
Cheers
Sobaro said:
Flash CF auto root via Odin then download latest superuser from play store and you are ready to go.
All credits to ChainFire
Click to expand...
Click to collapse
wavv.drama said:
Just as a suggestion, something that happened to me while playing around with the phone: if you're running Stock rom and then flash a custom recovery via Odin (I used Philz Touch) upon booting on recovery just to wipe cache/dalvik I found something interesting: my phone wasn't rooted, so when chosing the option "reboot system now" a message that said something like "root is broken, would you like to root your phone before rebooting" appeared. I was curious, as I normally use a website called Kingo root that does it in a one-click kinda way. When I chose Yes in the recovery, upon booting my phone it was rooted. After, I just intalled Chainfire's SuperSU from the play store and it was all good.
It's worth trying I believe.
Cheers
Click to expand...
Click to collapse
+wavv.drama
I have a question. If you don't run odin as a administrator do you get this error message: Windows cannot access the specific device path or file. You may not have the appropriate permissions to access. The last time I tried to root my phone i didn't run odin in administrator mode. I'm just finding out about this recently. I have all of the files installed on the computer and ready. Odin, recovery, keis, and supersu zip on sd card. Im just trying to figure out why I got that error message. Any ideas or suggestions would be appreciated. Thanks in advance... Awaiting your response...
"What good is knowledge if it's not to be shared"...
Sent from my SGH-T889 using XDA Premium 4 mobile app
J3D1mineTR1X said:
+wavv.drama
I have a question. If you don't run odin as a administrator do you get this error message: Windows cannot access the specific device path or file. You may not have the appropriate permissions to access. The last time I tried to root my phone i didn't run odin in administrator mode. I'm just finding out about this recently. I have all of the files installed on the computer and ready. Odin, recovery, keis, and supersu zip on sd card. Im just trying to figure out why I got that error message. Any ideas or suggestions would be appreciated. Thanks in advance... Awaiting your response...
"What good is knowledge if it's not to be shared"...
Sent from my SGH-T889 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The only answer that pops up in my mind would be that you weren't running Odin as an administrator, like you mentioned. Maybe try running Odin as an admin, or alternatively (and I haven't tried this myself but Chainfire's thread gives a good step-by-step and people in the forum do help) use mobile Odin ------> http://forum.xda-developers.com/showthread.php?t=1347899. The first time I wanted to root my phone I was having issues too, not being able to do it because of lack of experience. I stumbled upon this website: http://www.kingoapp.com/. Check it out, if you would like. This kingo app is a downloadle app (kind of like Odin) that Roots yourm phone alone, without needing to flash anything. The step-by-step's are there, just turn on your developer options and then turn on USB debugging. I personally rooted A Galaxy Tab, SIII, a Note I i717 and an Asus MemoPad with that website and it worked perfectly for me. Rooting via custom recovery is something that I learned recently, and by chance. I do not know whether it trips the Knox counter or not to be honest with you, to me it doesn't make a difference since I will not be returning any of the devices I rooted, After rooting the phone like so you could potentially download mobile Odin from Chainfire's thread and then use Odin without needing to use your computer.
Hope this helps
+wavv. Drama
Yeah that was it, i rooted it earlier today. I do have another question for you. I ran root checker pro and it says I'm rooted. I tried to install busybox but it said remove supersu permissions reinstall supersu and to delete and reinstall busybox. Also the adb shell doesn't have root access either. So is that a common occurrence, or is it the norm after rooting and installing custom recovery? Awaiting your reply. Thanks in advance...
What good is knowledge if it's not to be shared...
Sent from my SGH-T889 using XDA Premium 4 mobile app
Sorry for the late reply, hadn't been to the forum in a minute. To be honest with u, I don't know for sure. I haven't personally yet served myself from adb so I can't tell u. However, the reason why you received that response from busybox may be because when u were partially rooted it gained root access (if it ever did, I only assume).
Try what was asked of u and I'm sure busybox will work no problems. Also, if u have the terminal emulator apk try entering the command "root" (without the ") and if u gain roots access it will definitely mean you are rooted for sure.
What do you want to use adb for, if I may ask?
Sent from my SGH-T889V using XDA Premium 4 mobile app
I've got a friend with an AT&T Note 2 with the latest 4.4.2 OTA. He wants to root so he can backup and transfer everything to a new device. I'm assuming towelroot won't do the trick since it's an Exynos CPU, but will Chainfire's auto root still work? I'm assuming Knox is on the newest OTA and wasn't on it originally when CFAR was released. I searched, but I don't see anything recent about rooting, and I just want to be relatively assured of not bricking him. Any help is appreciated.
tedkord said:
I've got a friend with an AT&T Note 2 with the latest 4.4.2 OTA. He wants to root so he can backup and transfer everything to a new device. I'm assuming towelroot won't do the trick since it's an Exynos CPU, but will Chainfire's auto root still work? I'm assuming Knox is on the newest OTA and wasn't on it originally when CFAR was released. I searched, but I don't see anything recent about rooting, and I just want to be relatively assured of not bricking him. Any help is appreciated.
Click to expand...
Click to collapse
Towel root will NOT work. Cf auto root will. It's the method I used. You may need to manually install the latest super user and after.
As stated above. . Use CF....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Ok I used cf auto root and it seems to have worked except as soon as my phone reboots I get "Unfortunately SuperSU has stopped"......now what I'm a Lil confused....it's there...just doesn't work.
I'm on official 4.4.2
Shortbus-Driver said:
Ok I used cf auto root and it seems to have worked except as soon as my phone reboots I get "Unfortunately SuperSU has stopped"......now what I'm a Lil confused....it's there...just doesn't work.
I'm on official 4.4.2
Click to expand...
Click to collapse
Now just install supersu from the play store and then go to the app after you download it and if it says to update it do it and you'll be fine
Shortbus-Driver said:
Ok I used cf auto root and it seems to have worked except as soon as my phone reboots I get "Unfortunately SuperSU has stopped"......now what I'm a Lil confused....it's there...just doesn't work.
I'm on official 4.4.2
Click to expand...
Click to collapse
Many people have encountered that problem.
here's the solution
marckusdavis said:
Sorry, I need to make sure I fully understand this too. So you have an SGH-i317 and were rooted. You installed the OTA update to 4.4.2 which unrooted you. Then you ran CF-AutoRoot and were able to successfully re-root on 4.4.2?
UPDATE:
Well, after reading another post where this worked, I decided to give it a try. It seemed to work, but then I get the message "Unfortunately SuperSU has stopped". I tried the solution using ES File Explorer to reinstall SuperSU.apk to no avail and there is no "UPDATE" button in Google Play, only OPEN, ENABLE or DISABLE so I can't update the binary. Any help would be greatly appreciated!
UPDATE 2:
Got it working, sort of! Since rooting seemed to work, but the old binary for SuperSU kept stopping, I downloaded the updated SuperSU zip file from here and then used ES File Explorer to look into the zip and find and run/install the Superuser.apk file. That works, but it does not appear to survive a reboot, so for each reboot I have to redo this process. Good enough work-around for now though as I'm sure there will be a complete solution down the road.
UPDATE 3 (probably final):
Was able to use the "Clean up for reinstallation from Google Play" option in the SuperSU settings. After reboot, Google Play then gave me the option to Install SuperSU which I did. It now survives reboot and it also, FINALLY, disabled the stupid Knox (which from what I read, was the cause of all of these problems in the first place. You have to be quick with the fingers though because as soon as SuperSU gave the option to disable Knox, a second later Knox closed it. I had to fire up SuperSU again and then click the disable Knox OK button IMMEDIATELY to kill it). I'm a happy, rooted Note 2 user on KitKat now! Hope all of this info. is helpful to someone else.
Click to expand...
Click to collapse
terpin32 said:
Now just install supersu from the play store and then go to the app after you download it and if it says to update it do it and you'll be fine
Click to expand...
Click to collapse
Cf auto root already installed supersu as a system app and market only gives the option to "open" it....I do not have root access and therefore can't unistall nor remove it ....lol this is frustrating. ...
I've never had this much problems and I currantly have an s4 and have had pretty much the entire "S" line starting from the Vibrant :-/
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
---------- Post added at 07:41 PM ---------- Previous post was at 07:39 PM ----------
SockmanTGR said:
Many people have encountered that problem.
here's the solution
Click to expand...
Click to collapse
All that isn't making any sense either I'm afraid.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Shortbus-Driver said:
Cf auto root already installed supersu as a system app and market only gives the option to "open" it....I do not have root access and therefore can't unistall nor remove it ....lol this is frustrating. ...
I've never had this much problems and I currantly have an s4 and have had pretty much the entire "S" line starting from the Vibrant :-/
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
---------- Post added at 07:41 PM ---------- Previous post was at 07:39 PM ----------
All that isn't making any sense either I'm afraid.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The solution I stated above works. try it. I had the same problem and that solved it.
Solved just had to get cwmr installed and flash a rom with root on it.