Develop Bugs

Odin Says "Pass", But phone is not rooted.

Hey guys I followed this guide
http://forum.xda-developers.com/show....php?t=2235366
I used a file called "CF-Auto-Root-d2spr-d2spr-sphl710.tar"
Everything goes well and I get a green pass from oden3, the phone reboots. But superSU is not installed and when I check "Root checker" there is no root....
I have 4.1.2
Thoughts?

Just download superuser and simply place it on your phones SD card it's really easy
Sent from my SPH-L710 using xda app-developers app

ricanjoe said:
Hey guys I followed this guide
http://forum.xda-developers.com/show....php?t=2235366
I used a file called "CF-Auto-Root-d2spr-d2spr-sphl710.tar"
Everything goes well and I get a green pass from oden3, the phone reboots. But superSU is not installed and when I check "Root checker" there is no root....
I have 4.1.2
Thoughts?
Click to expand...
Click to collapse
Your phone is not finishing the process it seems. After Odin says pass do you get a big red Android on the screen? If not flash the cf auto root file but uncheck auto reboot in Odin first. Then when it finishes, pull the cable and remove the battery. Reinsert the battery and manually boot to recovery by holding volume up+home+power and it should finish installing root.
I don't know what the post above me is taking about. Installing superuser isn't going to magically give you root. js

billard412 said:
Your phone is not finishing the process it seems. After Odin says pass do you get a big red Android on the screen? If not flash the cf auto root file but uncheck auto reboot in Odin first. Then when it finishes, pull the cable and remove the battery. Reinsert the battery and manually boot to recovery by holding volume up+home+power and it should finish installing root.
I don't know what the post above me is taking about. Installing superuser isn't going to magically give you root. js
Click to expand...
Click to collapse
Yes its a screen with red letters and numbers saying the phone will reboot in 10 seconds.... So I re root in oden? then I pull the battery out before reboot? Could this brick my phone?
Thanks foe the help

ricanjoe said:
Yes its a screen with red letters and numbers saying the phone will reboot in 10 seconds.... So I re root in oden? then I pull the battery out before reboot? Could this brick my phone?
Thanks foe the help
Click to expand...
Click to collapse
It wouldnt brick the phone but if you are seeing the red android then i was mistaken about what your issue is so disregard. Is your phone new? I bet the issue is related to one others are having where recovery cant mount partitions. To confirm that try this. Download this and place on pc http://goo.im/devs/billard412/d2spr/AUTOBOOT_RECOVERY/SPH-L710_TWRP_AUTOBOOT.exe
Its a odin one click that will autoboot you to twrp recovery just open it and click start with your phone connected in download mode.
Download this and place on your sd card. (preferably external)
http://forum.xda-developers.com/attachment.php?attachmentid=1584076&d=1356201390
If you can successfully flash that zip, it will root the phone.

billard412 said:
It wouldnt brick the phone but if you are seeing the red android then i was mistaken about what your issue is so disregard. Is your phone new? I bet the issue is related to one others are having where recovery cant mount partitions. To confirm that try this. Download this and place on pc http://goo.im/devs/billard412/d2spr/AUTOBOOT_RECOVERY/SPH-L710_TWRP_AUTOBOOT.exe
Its a odin one click that will autoboot you to twrp recovery just open it and click start with your phone connected in download mode.
Download this and place on your sd card. (preferably external)
http://forum.xda-developers.com/attachment.php?attachmentid=1584076&d=1356201390
If you can successfully flash that zip, it will root the phone.
Click to expand...
Click to collapse
About to give it a shot. Placing the root file on my external SD and phone into download mode, about to launch the odin app on pc.

billard412 said:
It wouldnt brick the phone but if you are seeing the red android then i was mistaken about what your issue is so disregard. Is your phone new? I bet the issue is related to one others are having where recovery cant mount partitions. To confirm that try this. Download this and place on pc http://goo.im/devs/billard412/d2spr/AUTOBOOT_RECOVERY/SPH-L710_TWRP_AUTOBOOT.exe
Its a odin one click that will autoboot you to twrp recovery just open it and click start with your phone connected in download mode.
Download this and place on your sd card. (preferably external)
http://forum.xda-developers.com/attachment.php?attachmentid=1584076&d=1356201390
If you can successfully flash that zip, it will root the phone.
Click to expand...
Click to collapse
my man, so far im in a 'team win recovery project screen' its all blue and stuff
this is pretty exiting for me.
So what do I press now? what does this screen mean?
(some personal insight, I have rooted my old evo 3d back in the day but il still pretty noobish, the twrp thing rings a bell)

ricanjoe said:
my man, so far im in a 'team win recovery project screen' its all blue and stuff
this is pretty exiting for me.
So what do I press now? what does this screen mean?
(some personal insight, I have rooted my old evo 3d back in the day but il still pretty noobish, the twrp thing rings a bell)
Click to expand...
Click to collapse
You want to press install then hit "up a level" until youre in the root "/" directory. Then choose "external_sdcard" then tap "root.zip" and swipe to confirm at the bottom.

billard412 said:
You want to press install then hit "up a level" until youre in the root "/" directory. Then choose "external_sdcard" then tap "root.zip" and swipe to confirm at the bottom.
Click to expand...
Click to collapse
sweet man, Im in root checker and it says "congratulations this device has root access"
I wanted to ask you how does this method differ from the method I was trying to perform?

ricanjoe said:
sweet man, Im in root checker and it says "congratulations this device has root access"
I wanted to ask you how does this method differ from the method I was trying to perform?
Click to expand...
Click to collapse
It's basically the same thing. Cf auto root will install a special recovery made by chainfire and a cache.img with a root zip. It's supposed to flash that zip then restore stock recovery. I've never seen cf auto root fail to do the job so im not sure what went wrong.
But the way you did it was you installed your own custom recovery and manually flashed a root zip created by me instead. Only thing different here is that you still have that custom recovery instead of stock recovery now.

billard412 said:
It's basically the same thing. Cf auto root will install a special recovery made by chainfire and a cache.img with a root zip. It's supposed to flash that zip then restore stock recovery. I've never seen cf auto root fail to do the job so im not sure what went wrong.
But the way you did it was you installed your own custom recovery and manually flashed a root zip created by me instead. Only thing different here is that you still have that custom recovery instead of stock recovery now.
Click to expand...
Click to collapse
Got it man, is this custom recovery better than the stock or is it essentially the same? I plan to install a custom rom soon.
(I didn't find many threads like this on google nor the search tool so hopefully people with the same strange problem as me will now find it. Should be useful)

ricanjoe said:
Got it man, is this custom recovery better than the stock or is it essentially the same? I plan to install a custom rom soon.
(I didn't find many threads like this on google nor the search tool so hopefully people with the same strange problem as me will now find it. Should be useful)
Click to expand...
Click to collapse
The custom recovery is the same with the exception that it gives you additional privileges over stock recovery. Like installing custom roms, so if you're planning on a custom rom soon then you may as well just stick with the custom one. I do however recommend you download goo manager from the playstore and updating your recovery to the newest with it before trying to flash anything. The recovery I gave you may be a little outdated. And if for any reason you want stock recovery back I'll make a odin tar of it and place it in this post
STOCK RECOVERY TAR

billard412 said:
The custom recovery is the same with the exception that it gives you additional privileges over stock recovery. Like installing custom roms, so if you're planning on a custom rom soon then you may as well just stick with the custom one. I do however recommend you download goo manager from the playstore and updating your recovery to the newest with it before trying to flash anything. The recovery I gave you may be a little outdated. And if for any reason you want stock recovery back I'll make a odin tar of it and place it in this post
Click to expand...
Click to collapse
I got the goo manager, which recovery do I update to?
The app wants me to update to open recovery twerp 2/6/2/0/d2spr.img

ricanjoe said:
I got the goo manager, which recovery do I update to?
The app wants me to update to open recovery twerp 2/6/2/0/d2spr.img
Click to expand...
Click to collapse
Just open it. Hit Menu then tap "install openrecoveryscript" Then "Yes". Then "Yes" again. It'll download the latest TWRP and flash it automatically.
Edit:sorry had to reread that. Twrp 2620 is right

advocatebutdfh
billard412 said:
Just open it. Hit Menu then tap "install openrecoveryscript" Then "Yes". Then "Yes" again. It'll download the latest TWRP and flash it automatically.
Click to expand...
Click to collapse
Alright man I wont waste anymore of your time here, just want to say thanks for all the help, this gives me the courage to continue to learn more about rooting and custom roms. I was about to give up last night because of this frustrating issue I had. Thanks again!

ricanjoe said:
Alright man I wont waste anymore of your time here, just want to say thanks for all the help, this gives me the courage to continue to learn more about rooting and custom roms. I was about to give up last night because of this frustrating issue I had. Thanks again!
Click to expand...
Click to collapse
No problem glad to help. And just in case u need it, the stock recovery tar is attached below.

billard412 said:
Just open it. Hit Menu then tap "install openrecoveryscript" Then "Yes". Then "Yes" again. It'll download the latest TWRP and flash it automatically.
Edit:sorry had to reread that. Twrp 2620 is right
Click to expand...
Click to collapse
about to install moar rom. I saw a video saying you should wipe dalvic cache and do several other things before.
Is there anything you reccomend I do before I flash this custom rom (Moar)

ricanjoe said:
about to install moar rom. I saw a video saying you should wipe dalvic cache and do several other things before.
Is there anything you reccomend I do before I flash this custom rom (Moar)
Click to expand...
Click to collapse
Just a factory reset. It should automatically wipe the cache and other areas that need wiped. I've ran moar before it's am awesome rom

billard412 said:
Just a factory reset. It should automatically wipe the cache and other areas that need wiped. I've ran moar before it's am awesome rom
Click to expand...
Click to collapse
Awesome im working on it now, also do you backup efs? Or is that just for the paranoid crowd?
(I will give you a shout out on my next vid

ricanjoe said:
Awesome im working on it now, also do you backup efs? Or is that just for the paranoid crowd?
(I will give you a shout out on my next vid
Click to expand...
Click to collapse
Personally I think the chances of your efs going bad are slim and a backup is more for paranoid people. With that said it never hurts to back it up. I just wouldn't restore it unless you have to.

[Q] Rooted SPH-L710 with ODIN & CF-Auto-Root, Root Checker shows NOT rooted. HELP?!

[Q] Rooted SPH-L710 with ODIN & CF-Auto-Root, Root Checker shows NOT rooted. HELP?!
I have had my Sprint Samsung Galaxy S3 for about a year now, and finally decided to give root access a try on the phone. I followed all of the step-by-steps tutorial, that Chainfire posted on his ([SPH-L710] CF-Auto-Root) thread, and have run into an issue. ODIN shows that the rooting procedure has passed, and the red android dude popped up, and the phone rebooted. Anytime I turn on my device, I immediately receive the notification that "unfortunately, SuperSU has stopped working". And running the app "root checker" returns the message "sorry! this device does not have proper root access". I went into download mode, and the flash counter shows that I have 1 custom rom/binary, whatever its called, and that my phone has the custom rom/binary status. I did some researching on the forums and threads, and it would seem that there's no clear cut way to fix this issue; given my phone's specific state. I don't want to brick my phone, so I need an experts solution! Thanks a million in advance!

If you want to leave root alone, you can reflash stock 4.4.2 is in Odin. But if you want to try to fix root you can flash a custom recovery is in Odin so you can flash an update to superuser using the custom recovery

Reply
thenexusgeneration said:
If you want to leave root alone, you can reflash stock 4.4.2 is in Odin. But if you want to try to fix root you can flash a custom recovery is in Odin so you can flash an update to superuser using the custom recovery
Click to expand...
Click to collapse
I would like the keep the phone rooted (which it has an issue with)....so as for fixing the root, by flashing a custom recovery....where do I find the custom recovery, and how exactly do I do this in ODIN, to specifically update superuser?
**NOTE: I downloaded a different superuser app on the google play store, (which will obviously not be saved/stored to system/app, like chainfire's SuperSU app is) and when I opened the Superuser app, it returns a message "SuperSU binary is out of date". I'm not sure what this means exactly, but maybe it might mean something to you, haha.

Have you tried this:
Go to the Google play store and find supersu. It should give you the option to "update" (versus "install")
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2

g_money said:
Have you tried this:
Go to the Google play store and find supersu. It should give you the option to "update" (versus "install")
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
All it says is" open". That's the only option on the Google play store.

Jayhawker69 said:
I would like the keep the phone rooted (which it has an issue with)....so as for fixing the root, by flashing a custom recovery....where do I find the custom recovery, and how exactly do I do this in ODIN, to specifically update superuser?
**NOTE: I downloaded a different superuser app on the google play store, (which will obviously not be saved/stored to system/app, like chainfire's SuperSU app is) and when I opened the Superuser app, it returns a message "SuperSU binary is out of date". I'm not sure what this means exactly, but maybe it might mean something to you, haha.
Click to expand...
Click to collapse
If you're looking for;
Odin
http://odindownload.com/
Philz
http://d-h.st/users/philz_touch/?fld_id=25216#files
SuperSU (zip)
http://download.chainfire.eu/396/SuperSU/
But as suggested try opening supersu first. Mine would fc, so I just flashed the supersu file above, from philz recovery.
I would also suggest Uninstall in the other su app. They never played well together (for me)
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2

Jessooca said:
Open it and if prompted select normal if it asks Normal or twrp/recovery
Click to expand...
Click to collapse
Any time I try to open it, it force closes with the message "unfortunately, SuperSU has stopped."

Reply
Everytime I try to flash the twrp recovery, windows error reports pops up and says "ODIN communicator has stopped working and needs to close." I have noooo idea. Why is it doing this! I have the worst luck

If you're ND8 or NDC bootloader, the only completely working custom recovery is the very latest Philz Touch Recovery.
[BATTERY] Plasma Battery! v2a ??? & wickeddecimalbarwide_colors
Charging still shot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v5.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.

Thanks a million!!
roirraW "edor" ehT said:
If you're ND8 or NDC bootloader, the only completely working custom recovery is the very latest Philz Touch Recovery.
[BATTERY] Plasma Battery! v2a ??? & wickeddecimalbarwide_colors
Charging still shot
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v5.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
Click to expand...
Click to collapse
roirraW "edor" ehT....THANKS A MILLION!! I have successfully in ODIN, flashed Philz Touch Recovery onto my S3. I booted into recovery, went in Philz settings, and clicked on the "re-root" option. I rebooted the device into the main system/shell, ran root checker to verify root status.....AND VOILA! ROOT STATUS GRANTED, BISH! I downloaded SuperSU from the play store, and everything seems to be running like butter. Consider this thread CLOSED!
Cheers from Lawrence, Kansas!,
-Brett

Jessooca said:
restart your computer and redownload odin
Everytime I try to flash the twrp recovery, windows error reports pops up and says "ODIN communicator has stopped working and needs to close." I have noooo idea. Why is it doing this! I have the worst luck
Click to expand...
Click to collapse
[/QUOTE]
Thanks for your help as well, much appreciated.

You're welcome and cheers right back from Columbus, Ohio. ☺
[BATTERY] Plasma Battery! v2a ??? & wickeddecimalbarwide_colors
Charging still shot
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v5.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.

I need help toooo!
i've been having the same issue! thank you for working it out. i really want to complete the root, but im having trouble.
I'm very new to this stuff and I don't understand some of the instrutions.
could someone made make a clear cut instruction on how to do this?
I have an SPH-L710
I used Odin with CF- Auto Root.
When I try to open SuperSU, I get, "Unfortunately, Supersu has stopped." and I can't update it in Play. Just like OP.
I'm unfamiliar with recoveries and how to install them. I have the latest philz touch and SuperSu Zips on my computer ready to go. I have odin 3.07.
If Jessooca could make a clear cut instruction that would be awesome. Or anyone really..I just need some help.
Oh, and my computer won't recognize my phone. It did for a moment, but It hasn't been working for the past hour.

thank you!
thank you! that worked like a charm. however, i really wanted some free tethering, but it looks like kitkat won't allow FoxFi to do it! a pop up comes through about subscribing to the service. I installed SlimKat, and I hate it. It's fast and I can do the free tethering, but it's so ugly. I want to go back to my rooted kitkat. What should I do?
I don't think i made a correct back up. i thought i did, but i guess i didn't.
I'm downloading the official ROM for my SPH-L710 right now.
How can I return to a normal rooted kitkat?:good:

Kalen_Christian said:
thank you! that worked like a charm. however, i really wanted some free tethering, but it looks like kitkat won't allow FoxFi to do it! a pop up comes through about subscribing to the service. I installed SlimKat, and I hate it. It's fast and I can do the free tethering, but it's so ugly. I want to go back to my rooted kitkat. What should I do?
I don't think i made a correct back up. i thought i did, but i guess i didn't.
I'm downloading the official ROM for my SPH-L710 right now.
How can I return to a normal rooted kitkat?:good:
Click to expand...
Click to collapse
You might want to check in philz for any backups. If you have 1 it's easy to reinstall. If not, then you would have to flash your stock tar in Odin. Then, flash philz and then root. The more you do it the easier it gets. But, make sure that you are not downgrading by trying to flash an older stock tar. Downgrading your boot loader will cause a hard brick...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2

g_money said:
You might want to check in philz for any backups. If you have 1 it's easy to reinstall. If not, then you would have to flash your stock tar in Odin. Then, flash philz and then root. The more you do it the easier it gets. But, make sure that you are not downgrading by trying to flash an older stock tar. Downgrading your boot loader will cause a hard brick...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
I checked Philz out very thoroughly and I don't think I did it correctly. So, I have to put a fresh 4.4.2 on. When I do want to creat a backup for recovery, What app should I use? Also, What are the main apps for superusers? I don't want to download a bunch of stuff I don't really need.
Thanks

**proper way to fix your problem!!**
Kalen_Christian said:
i've been having the same issue! thank you for working it out. i really want to complete the root, but im having trouble.
I'm very new to this stuff and I don't understand some of the instrutions.
could someone made make a clear cut instruction on how to do this?
I have an SPH-L710
I used Odin with CF- Auto Root.
When I try to open SuperSU, I get, "Unfortunately, Supersu has stopped." and I can't update it in Play. Just like OP.
I'm unfamiliar with recoveries and how to install them. I have the latest philz touch and SuperSu Zips on my computer ready to go. I have odin 3.07.
If Jessooca could make a clear cut instruction that would be awesome. Or anyone really..I just need some help.
Oh, and my computer won't recognize my phone. It did for a moment, but It hasn't been working for the past hour.
Click to expand...
Click to collapse
Ok, first off....no offense to the poster 'Jessooca', but the steps she has posted to solve your issue are in part, slightly incorrect and misguiding. The following steps are *EXACTLY* how you should proceed, in order to fix the problem/issue you are having (the EXACT same issue I dealt with for the past two days) :
Step One:
IF you haven't done so already, download the Samsung Galaxy S3 USB drivers from the following link. This should solve your connectivity problem. Following the link below, scroll down just a little bit, and click on the downloads tab located just to the right of the 'Manuals' tab. Click on the blue box that says "EXE", and this should get the proper driver downloaded for your Sprint Samsung Galaxy S3. And obviously, install the downloaded driver after it completes the download.
Link:
http://www.samsung.com/us/support/owners/product/SPH-L710MBBSPR?CID=AFL-hq-mul-0813-11000279#
Step Two:
I know that you have stated that you have already downloaded the 'Philz Touch Recovery'.zip file....but there is a chance you may not have downloaded the proper file for your specific and exact handset. So, here is the link for 'Philz Touch Recovery' that you should download and use for this process. It should be a direct link for the download file. I'll post a second link that you should only use as an alternative, in the event that the first link does not work. IF the first link didn't work, then make sure you download the most recently uploaded version of the Philz touch recovery from the alternative link; should be Sun, July 6th...and also be sure to click on the download link (there's two separate links) titled "philz_touch_6.48.4-d2lte.tar.md5"...as it will be much easier to work with than the .zip file.
Link One:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/philz_touch_6.48.4-d2lte.tar.md5
Alternative Link:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Step Three:
Now that we have the proper 'Philz Touch Recovery' file downloaded, you will need to download a different version of ODIN, as the 3.07 version you have will not suit our needs for this procedure. The link for the proper version of ODIN you will need is posted directly below. Download, extract it, and put the extracted folder somewhere on your computer that is handy or easy to find later. I'd suggest making a folder on your desktop from the very start of this procedure, and name it 'SPH-L710 Root Files', or w/e works best for you. Save all the files, or move all of the files you might have already downloaded at this point into that folder. Always nice to be organized and shizzz.
Link:
http://forum.xda-developers.com/attachment.php?attachmentid=581913
Step Four:
Alright, were getting closer to being done with this whole ordeal. Follow the link I have posted below, for the proper instructions on how to flash 'Philz Touch Recovery' in Odin to your device (the version of Odin we just downloaded from step three...obvi). Reading the instructions, you'll notice that it mentions that auto-reboot into recovery mode may not work properly after the file is flashed in Odin. This actually happened to myself....and seeing as how we have had the exact same problem with rooting our phones, I would suggest from the start, to uncheck the auto reboot option in Odin, and then manually boot into recovery mode after Odin successfully flashes the file to your phone. If you take my advice, and follow what I just said, your phone will still be in download mode after Odin flashes the file...assuming Odin says that the file successfully flashed ("PASS!"). From here, you will unplug your phone from your USB cord.....and now we will boot into the recovery file/mode we just flashed. To do this, HOLD down in this order: the Volume Up button + the Home key + the Power Button....continue to hold all 3 of these buttons down until the phone enters into recovery mode...you will be able to tell when you are in recovery.
Link:
http://forum.xda-developers.com/showpost.php?p=39433857&postcount=4
Step Five:
Ok, so hopefully if you did everything right to this point, and some other unforeseen issue has not arisen, you should be in Philz Touch Recovery Mode. Click on "PhilZ Settings" or "Advanced" , I can't remember for sure which one it is....but I'm almost positive it's in "PhilZ Settings"...click that option first. Within this settings menu, click on the option titled "Re-root" and click yes to proceed. After this is done, go back to the main menu and click on the "Reboot system/device" option on the very top.
Step Six:
Your phone should now boot up normally into your phones operating system/shell. Go to the Google Play store and search for and download an app called "Root Checker". Open the Root Checker app and click on the verify button. If everything worked properly, and if baby raptor Jesus loves you, the Root Checker will return the result that your phone has been properly rooted and you have root access/privileges. Now, go back to Google Play Store and download the "SuperSU" app....if it isn't already still on your phone (I had to re-download it). Open SuperSU from your apps menu/drawer and it might ask you to update the SuperSU binaries...mine did....and click on the normal method option, instead of the recommended option for HTC devices. SuperSU should update binary and your problems should all be melted away like butter by now.
** THIS IS THE EXACT SOLUTION(S) I TOOK TO FIX OUR SAME PROBLEM. I CAN'T GUARANTEE IT WILL WORK THE SAME FOR YOU, FOR WHATEVER REASON OR CIRCUMSTANCE THAT MIGHT BE. GOOD LUCK, YOU'LL DO GREAT KID :laugh::good:**

Kalen_Christian said:
I checked Philz out very thoroughly and I don't think I did it correctly. So, I have to put a fresh 4.4.2 on. When I do want to creat a backup for recovery, What app should I use? Also, What are the main apps for superusers? I don't want to download a bunch of stuff I don't really need.
Thanks
Click to expand...
Click to collapse
You would use philz recovery to make your backup. My apps that use root would be things like titanium backup, clean master, busy box. By going to the playstore and doing a search for root, you'll find apps that don't need root access but perform better when they have it...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2

Check this out !!!!
Jayhawker69 said:
Ok, first off....no offense to the poster 'Jessooca', but the steps she has posted to solve your issue are in part, slightly incorrect and misguiding. The following steps are *EXACTLY* how you should proceed, in order to fix the problem/issue you are having (the EXACT same issue I dealt with for the past two days) :
Step One:
IF you haven't done so already, download the Samsung Galaxy S3 USB drivers from the following link. This should solve your connectivity problem. Following the link below, scroll down just a little bit, and click on the downloads tab located just to the right of the 'Manuals' tab. Click on the blue box that says "EXE", and this should get the proper driver downloaded for your Sprint Samsung Galaxy S3. And obviously, install the downloaded driver after it completes the download.
Link:
http://www.samsung.com/us/support/owners/product/SPH-L710MBBSPR?CID=AFL-hq-mul-0813-11000279#
Step Two:
I know that you have stated that you have already downloaded the 'Philz Touch Recovery'.zip file....but there is a chance you may not have downloaded the proper file for your specific and exact handset. So, here is the link for 'Philz Touch Recovery' that you should download and use for this process. It should be a direct link for the download file. I'll post a second link that you should only use as an alternative, in the event that the first link does not work. IF the first link didn't work, then make sure you download the most recently uploaded version of the Philz touch recovery from the alternative link; should be Sun, July 6th...and also be sure to click on the download link (there's two separate links) titled "philz_touch_6.48.4-d2lte.tar.md5"...as it will be much easier to work with than the .zip file.
Link One:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/philz_touch_6.48.4-d2lte.tar.md5
Alternative Link:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Step Three:
Now that we have the proper 'Philz Touch Recovery' file downloaded, you will need to download a different version of ODIN, as the 3.07 version you have will not suit our needs for this procedure. The link for the proper version of ODIN you will need is posted directly below. Download, extract it, and put the extracted folder somewhere on your computer that is handy or easy to find later. I'd suggest making a folder on your desktop from the very start of this procedure, and name it 'SPH-L710 Root Files', or w/e works best for you. Save all the files, or move all of the files you might have already downloaded at this point into that folder. Always nice to be organized and shizzz.
Link:
http://forum.xda-developers.com/attachment.php?attachmentid=581913
Step Four:
Alright, were getting closer to being done with this whole ordeal. Follow the link I have posted below, for the proper instructions on how to flash 'Philz Touch Recovery' in Odin to your device (the version of Odin we just downloaded from step three...obvi). Reading the instructions, you'll notice that it mentions that auto-reboot into recovery mode may not work properly after the file is flashed in Odin. This actually happened to myself....and seeing as how we have had the exact same problem with rooting our phones, I would suggest from the start, to uncheck the auto reboot option in Odin, and then manually boot into recovery mode after Odin successfully flashes the file to your phone. If you take my advice, and follow what I just said, your phone will still be in download mode after Odin flashes the file...assuming Odin says that the file successfully flashed ("PASS!"). From here, you will unplug your phone from your USB cord.....and now we will boot into the recovery file/mode we just flashed. To do this, HOLD down in this order: the Volume Up button + the Home key + the Power Button....continue to hold all 3 of these buttons down until the phone enters into recovery mode...you will be able to tell when you are in recovery.
Link:
http://forum.xda-developers.com/showpost.php?p=39433857&postcount=4
Step Five:
Ok, so hopefully if you did everything right to this point, and some other unforeseen issue has not arisen, you should be in Philz Touch Recovery Mode. Click on "PhilZ Settings" or "Advanced" , I can't remember for sure which one it is....but I'm almost positive it's in "PhilZ Settings"...click that option first. Within this settings menu, click on the option titled "Re-root" and click yes to proceed. After this is done, go back to the main menu and click on the "Reboot system/device" option on the very top.
Step Six:
Your phone should now boot up normally into your phones operating system/shell. Go to the Google Play store and search for and download an app called "Root Checker". Open the Root Checker app and click on the verify button. If everything worked properly, and if baby raptor Jesus loves you, the Root Checker will return the result that your phone has been properly rooted and you have root access/privileges. Now, go back to Google Play Store and download the "SuperSU" app....if it isn't already still on your phone (I had to re-download it). Open SuperSU from your apps menu/drawer and it might ask you to update the SuperSU binaries...mine did....and click on the normal method option, instead of the recommended option for HTC devices. SuperSU should update binary and your problems should all be melted away like butter by now.
** THIS IS THE EXACT SOLUTION(S) I TOOK TO FIX OUR SAME PROBLEM. I CAN'T GUARANTEE IT WILL WORK THE SAME FOR YOU, FOR WHATEVER REASON OR CIRCUMSTANCE THAT MIGHT BE. GOOD LUCK, YOU'LL DO GREAT KID :laugh::good:**
Click to expand...
Click to collapse
WILL TRY TO BE BRIEF....maybe...
ONLY did the whole QUOTE for the fact this works on newer formats 4.4.x.... (for now)...
IMO, this SHOULD out in the main thread or something.
Seems that just trying to use Chainfire Auto root does not work on 4.4.x...HOWEVER THIS does honestly work right the first time!!! Do need to add that I have tried Auto w/Odin (3.09/3.07/an 1.85) so many times it Nuckin' Futz....
OK, have been in same boat and working extremely hard and long on this issue (rooting SGS3 on 4.4.2) for the past week or so! I do really mean work on this issue. Have read an researched tons ...Starting w/4.3 to 4.4.x, as well as what is coming down the darn pike on this matter. Look up what Mr. Chainfire has posted in the last month... might get folks thinking twice on that new phone purchase, not just the cost, but what they end up with.
Anyway, I want to thank you....
Seems to me, the main thing that has kept me from rooting was this little tid-bit>>> "After it says "PASS" unplug and go right into RECOVERY from this point, (meaning from download mode right to recovery)"....as well as Once in Phliz recovery> RE_ROOT, then boot into system
Truly hope this helps others with there SGS3 (l710)
Thanks Again.
P.S.
reason for the red>So hopefully others on stock 4.4.x, can see 1 honest easy way to root

Jayhawker69 said:
roirraW "edor" ehT....THANKS A MILLION!! I have successfully in ODIN, flashed Philz Touch Recovery onto my S3. I booted into recovery, went in Philz settings, and clicked on the "re-root" option. I rebooted the device into the main system/shell, ran root checker to verify root status.....AND VOILA! ROOT STATUS GRANTED, BISH! I downloaded SuperSU from the play store, and everything seems to be running like butter. Consider this thread CLOSED!
Cheers from Lawrence, Kansas!,
-Brett
Click to expand...
Click to collapse
These steps worked! Thank you both very much!

Stuck in Odin Mode [from attempt to install a recovery rom]

I'd appreciate any help I can get guys.
So today, for the first time ever I rooted my android.
Found a simple video on how to and it worked. I then wanted to try a custom rom [Cyanogenmod 12?] On a video it was said to have a custom recovery rom first. Well, I tried Flashing TWRP. It asked to reboot. I pressed "yes Please". After that it restarted and was stuck at:
"Could not do normal boot" Odin mode (High speed)
I did a reset and now its just at:
"Odin mode(high speed)"
I saw someone on a random forum describing the same problem. He said he fixed it installing a recovery rom. Im guess from odin
since I cant do things on my phone. But I don't even know how to go about it. I just now I need a Tar. file
Please give me direction .__.

Try TWRP tar from Odin with phone in download mode; TWRP recovery tar linked below.
http://www.techerrata.com/file/twrp2/trltespr/openrecovery-twrp-2.8.5.0-trltespr.img.tar
If that doesn't work, you may have to Odin the stock tar.
I'm wondering if you misread the CF Auto root prompt to update the su binary? Update the su binary but don't choose the TWRP option even if you have TWRP. If you get recovery working, delete the cache and dakvik cache and reboot.

Didn't work out...at least the way I did it. I'm still new to this. Id appreciate more broken down instructions if youre willing to help

Sixgotfangs said:
Didn't work out...at least the way I did it. I'm still new to this. Id appreciate more broken down instructions if youre willing to help
Click to expand...
Click to collapse
What version of Odin do you have? Should be 3.07 with C.F. auto root. What have you flashed in Odin? Not familiar with the Odin message you gave; did anything change with the new recovery tar flash in Odin?
Won't boot or flash recovery? If so, you need to factory reset and Odin stock tar.
https://www.androidfilehost.com/?fid=95853297432265112
The instructions for stock tar are below but it's important to remember when flashing stock tars to power down first prior to going to download. You may not have any choice but power down to reach download mode; pull battery if you can't power down.
http://forum.xda-developers.com/showthread.php?p=56853325
If you can't factory reset, Odin the stock tar and see if it boots.

Yes, I have the 3.07. Only thing ive done was Root. I tried the recovery rom from a mobile download. That's as far as I got. All the recovery files I get never end up showing in the pda file search. .tar or .md5 is what it calls for. If I CAN factory reset from where im at now how do I do so. If I can start ALL over with someone who is actually up to date and knows what theyre doing id feel more comfortable. right now nothings happened and my phone is still at "odin mode (hgh speed) --downloading.

Sixgotfangs said:
Yes, I have the 3.07. Only thing ive done was Root. I tried the recovery rom from a mobile download. That's as far as I got. All the recovery files I get never end up showing in the pda file search. .tar or .md5 is what it calls for. If I CAN factory reset from where im at now how do I do so. If I can start ALL over with someone who is actually up to date and knows what theyre doing id feel more comfortable. right now nothings happened and my phone is still at "odin mode (hgh speed) --downloading.
Click to expand...
Click to collapse
ok, check my post above for updates.
Also, don't use the phone to download tar files unless you're using Flashify from Google Play. Download the tars on PC, move to folder that Odin resides in to find easily. You'll need to open the archive and drag the files there if zipped. The stock tar should be zipped but not sure about the recovery tar.

Cant believe I didn't see the last section on that post. Sorry about that. Anyway, I am downloading those files. Looks like its gonna take some time though. I'll go through each step you said and let you know.

Forgot to mention that you should close Odin after each flash attempt. You may have already noticed by now.
To get to CM after stock tar:
1) Root with CF Auto root, update su binary/reboot (you should wait no longer than 5 minutes for Knox prompt from supersu.
2) Odin TWRP recovery tar using same method as stock tar; Odin will only write over stock recovery on this step.
3) factory reset and flash CM in recovery. But also follow suggested instructions in the ROM you choose.

So far so good. The lil blue loading bar is filling.

got back to rooting. but I didn't do anything else. haven't even went to super user

Sixgotfangs said:
got back to rooting. but I didn't do anything else. haven't even went to super user
Click to expand...
Click to collapse
Booted? That's good news!
Can't remember if you have to open it or not. You should get a superuser update and possibly a su binary update but not so important going to another ROM. The su binary update is the one that I was suggesting not to use the TWRP option; I think the option is normal? Eventually, you should get the pop-up to disable Knox notifications; reboot if takes longer than 5 minutes.
Ready for TWRP? Use Odin. Flashify is something you could look into for updating TWRP, as needed. It's good for backing up recoveries and kernels, too. But watch those kernels for installed lib modules; Flashify won't restore those properly. Rely on flash zips for those; same applies for stock kernels, zip should include the stock modules.
It's late; you're probably done for the night. I'm out too.

samep said:
Booted? That's good news!
Can't remember if you have to open it or not. You should get a superuser update and possibly a su binary update but not so important going to another ROM. The su binary update is the one that I was suggesting not to use the TWRP option; I think the option is normal? Eventually, you should get the pop-up to disable Knox notifications; reboot if takes longer than 5 minutes.
Ready for TWRP? Use Odin. Flashify is something you could look into for updating TWRP, as needed. It's good for backing up recoveries and kernels, too. But watch those kernels for installed lib modules; Flashify won't restore those properly. Rely on flash zips for those; same applies for stock kernels, zip should include the stock modules.
It's late; you're probably done for the night. I'm out too.
Click to expand...
Click to collapse
Yeah, things are back to normal. Thanks again. As for the next steps, pretty lost. Im going to check the play store for an superuser update but the SU binary update....that's where I start getting lost. sorry for not being up to date with the terminology. But I am gonna check back on those links and look for the TWRP. and then use it like I did for those last files...{that's what Im getting from your messages} correct me if im straying from the path lol. catch ya later

I'm confusing you a bit with the the su binary update and SuperSU update. To keep it simpler, that can wait until after you flash CM, if that's your goal. Those are prompts so don't be too concerned. Don't think you'll see Knox in CM.
So to keep it simple, you need TWRP to flash a custom ROM. I suggest the Odin tar in the link sent earlier.
After getting your custom ROM flashed in recovery, follow the prompts but if you see the su binary update prompt, don't choose the TWRP option. I think that caused your initial recovery issue but can't say for sure.

samep said:
I'm confusing you a bit with the the su binary update and SuperSU update. To keep it simpler, that can wait until after you flash CM, if that's your goal. Those are prompts so don't be too concerned. Don't think you'll see Knox in CM.
So to keep it simple, you need TWRP to flash a custom ROM. I suggest the Odin tar in the link sent earlier.
After getting your custom ROM flashed in recovery, follow the prompts but if you see the su binary update prompt, don't choose the TWRP option. I think that caused your initial recovery issue but can't say for sure.
Click to expand...
Click to collapse
Hey there, Ok so. After messing around I ended up getting that TWRP package to work. I thought It was a SINGLE file, that's where I got stuck. but the whole ?.rar showed up in the pda selection In odin and I ran it. Worked fine. didn't see anything about updates ...still.
I restarted and went to recoverymode. Teamwin popped up like ive seen from other videos. Guessing im on the right track. So right now I don't need to be worrying about SuperSu or Rashr? or should I be dealing with those two apps? ALSO is Rom installer anything to pay attention to?

At this point, you can look into a ROM installer or Flashify but I'd recommend just following the developer OP for whatever ROM you choose.
And yes, no need to worry with SuperSU or su binary update. Just follow the prompts when they appear after flashing ROM.

samep said:
At this point, you can look into a ROM installer or Flashify but I'd recommend just following the developer OP for whatever ROM you choose.
And yes, no need to worry with SuperSU or su binary update. Just follow the prompts when they appear after flashing ROM.
Click to expand...
Click to collapse
Thanks so much! The videos ive seen have been much simple-r for installing roms SO I may survive this whole experience after all...Yesterday was kind of a bad time to almost loose my phones functionality....being on the job hunt and all. need those phone calls Lol. So thanks again. Im hoping to try out cyanogenmod 12. I'll definitely shoot off a flare gun if I fail lol.

No problem. Glad to be of some help. Godspeed on your journey and best of wishes for your career and rooted ventures!

samep said:
No problem. Glad to be of some help. Godspeed on your journey and best of wishes for your career and rooted ventures!
Click to expand...
Click to collapse
SUCCESS! Thanks again Sensei Lol

samep said:
No problem. Glad to be of some help. Godspeed on your journey and best of wishes for your career and rooted ventures!
Click to expand...
Click to collapse
eh...celebrated too early I guess. Ever run into camera connection errors?

Sixgotfangs said:
eh...celebrated too early I guess. Ever run into camera connection errors?
Click to expand...
Click to collapse
Is the error while still on stock or CM?
Now that you can wipe data, you can factory reset and either Odin the stock tar or flash CM.
If you prefer to take least intrusive approach, try going into recovery and delete cache and dalvik cache and reboot. If still not working, the factory reset. If still having camera issues, then decide if you want to go with stock tar in Odin again or CM a clean install; wipe user data first.
Personally, I'd wipe everything except my titanium backups and go back to Odin stock tar and make sure stock works fully before going to CM. In a situation like you were in, I would have powered down, flashed the stock tar in Odin and let it auto boot. Flash the custom recovery so I could wipe everything and then power down again and flash the stock tar in Odin just to get a clean start with root and custom ROM.
Edit- what is camera connection error? Oh, I see; lost camera. New thread. Maybe someone on CM can help you.

[Help] Forgot to install SuperSu

When I 'reboot'ed to restore, I was clicking 'reboot' without thinking twice. I realized I didn't install SuperSu in it. I had SuperSu app but I didn't install it yet. So I went ahead, rebooting until the logo showed up but it shut. Again, the logo showed up and it shut. It was going on.
One simple question- HOW DO I FIX?!
I feel stupid as a elephant.
Thanks!

Go to the play store and install it.

w7excursion said:
Go to the play store and install it.
Click to expand...
Click to collapse
I already had it installed before. Nothing happened.

What are you trying to do that is related to super su?

w7excursion said:
What are you trying to do that is related to super su?
Click to expand...
Click to collapse
Well, at first, I added SuperSU and then I added TWRP. I realized I hadn't installed SuperSU from Play Store yet. Then BOOM. The logo kept restarting. What should I do?
I just wanted to add a Noterized rom later but....

What did you root with? I thought Cf auto root installed it during the root process. http://forum.xda-developers.com/showthread.php?t=1538053

w7excursion said:
What did you root with? I thought Cf auto root installed it during the root process. http://forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
I did follow what it said and nothing happened! I didn't understand!
http://grantbarker.com/samsung-galaxy-note-4.html --- This is what I followed Rooting and Flashing. SuperSu appeared in my Note 4. I thought it was all set. So I went ahead to reboot but it didn't work. The logo kept appearing and then disappearing. Forth and back. I didn't understand what did I do wrong.

Link which cf auto root file you used . Hit the thanks to chainfire http://forum.xda-developers.com/note-4/orig-development/sm-n910-cf-auto-root-t2897428 and should be this one https://download.chainfire.eu/585/CF-Root1/CF-Auto-Root-trltespr-trltespr-smn910p.zip

w7excursion said:
Link which cf auto root file you used . Hit the thanks to chainfire http://forum.xda-developers.com/note-4/orig-development/sm-n910-cf-auto-root-t2897428 and should be this one https://download.chainfire.eu/585/CF-Root1/CF-Auto-Root-trltespr-trltespr-smn910p.zip
Click to expand...
Click to collapse
That's the link I downloaded. :crying:

idavyko said:
Well, at first, I added SuperSU and then I added TWRP. I realized I hadn't installed SuperSU from Play Store yet. Then BOOM. The logo kept restarting. What should I do?
I just wanted to add a Noterized rom later but....
Click to expand...
Click to collapse
You're not very good at describing the steps, your current situation, firmware you started with or answering questions so my response may be out in left field; you decide.
Did you happen to have OE1 or OF5 build before you started?
When you you say the logo kept restarting, did you leave out a step? Sounds like you used Odin to flash CF Auto Root, TWRP and proceeded to flash a custom ROM and it didn't boot.
Did you forget to do a much needed step of taking a nandroid backup as soon as you got to TWRP recovery?
Did not restart... Two things you can do. If you have the nandroid backup from TWRP, use it.
If you don't have it, flash the Odin CF Auto Root and try to reboot. If it boots, note the build and make a nandroid.
Most common mistake made in XDA in past weeks is trying to downgrade builds OE1 and OF5 to take a custom ROM when it's not supposed to happen. Bugs and reboot issues galore. And no way to upgrade until a stock recovery is found or a tar released.
Read and you may find some answers to your situation, if I'm out of bounds.
Sent from my SM-N910P using Tapatalk

samep said:
You're not very good at describing the steps, your current situation, firmware you started with or answering questions so my response may be out in left field; you decide.
Did you happen to have OE1 or OF5 build before you started?
When you you say the logo kept restarting, did you leave out a step? Sounds like you used Odin to flash CF Auto Root, TWRP and proceeded to flash a custom ROM and it didn't boot.
Did you forget to do a much needed step of taking a nandroid backup as soon as you got to TWRP recovery?
Did not restart... Two things you can do. If you have the nandroid backup from TWRP, use it.
If you don't have it, flash the Odin CF Auto Root and try to reboot. If it boots, note the build and make a nandroid.
Most common mistake made in XDA in past weeks is trying to downgrade builds OE1 and OF5 to take a custom ROM when it's not supposed to happen. Bugs and reboot issues galore. And no way to upgrade until a stock recovery is found or a tar released.
Read and you may find some answers to your situation, if I'm out of bounds.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Whoa, what? What OE1 and OF5? How do I know? OMG, I feel stupider now. I thought backup was from TWRP but oops. Where do I find nandroid backup?

idavyko said:
Whoa, what? What OE1 and OF5? How do I know? OMG, I feel stupider now. I thought backup was from TWRP but oops. Where do I find nandroid backup?
Click to expand...
Click to collapse
If it boots to TWRP recovery, check both the ext and sd card for backup when selecting the restore tab. I think it defaults to where you backed it up but check anyway. There's a tab button to select location in the restore menu.
No backup? Reflash CF Auto Root and reboot. If it boots, go back to recovery and make a backup in TWRP recovery.
If you don't have TWRP, flash in Odin and do the above steps.
Sent from my SM-N910P using Tapatalk

samep said:
If it boots to TWRP recovery, check both the ext and sd card for backup when selecting the restore tab. I think it defaults to where you backed it up but check anyway. There's a tab button to select location in the restore menu.
No backup? Reflash CF Auto Root and reboot. If it boots, go back to recovery and make a backup in TWRP recovery.
If you don't have TWRP, flash in Odin and do the above steps.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I reflashed CF Auto Root and rebooted it. It said FAIL. Not working successfully.
https://download.chainfire.eu/585/CF-Root1/CF-Auto-Root-trltespr-trltespr-smn910p.zip - I used it for CF AUTO. I don't know how it happened. : (

In the settings go look in the "About Device" and see what the software version is. Hopefully not the two versions mentioned earlier.

There's also instructions in the CF Auto Root for flashes not taking. Something like if you don't see the red android in recovery, pull battery and reboot to recovery... Follow the OP.
Sent from my SM-N910P using Tapatalk

w7excursion said:
In the settings go look in the "About Device" and see what the software version is. Hopefully not the two versions mentioned earlier.
Click to expand...
Click to collapse
That's a major problem... I can't EVEN get in homescreen at all. I am at where Samsung logo restarting is. Not even get in homescreen at all.

samep said:
There's also instructions in the CF Auto Root for flashes not taking. Something like if you don't see the red android in recovery, pull battery and reboot to recovery... Follow the OP.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Done there, done that many times. There is NO red android in recovery. I see a green android every time I try to reboot.

I'm sure you tried this but it's a step process: Odin flash CF with auto boot enabled. If you don't see red Android, pull battery and boot directly into recovery.
No boot after that? Try boot into recovery again. Factory reset a few times and try to reboot. If that's a dead horse, you can try to flash OB7 modem in Odin (extract from OB7 stock tar) and flash noterized stable 2. Consider wiping all but ExtSdCard and flash again if still won't boot. But know you're in a realm of risks that you must weigh for yourself. I'm not liable for a brick.
Sent from my SM-N910P using Tapatalk

samep said:
I'm sure you tried this but it's a step process: Odin flash CF with auto boot enabled. If you don't see red Android, pull battery and boot directly into recovery.
No boot after that? Try boot into recovery again. If that's a dead horse, you can try to flash OB7 modem in Odin (extract from OB7 stock tar) and flash noterized stable 2. But know you're in a realm of risks that you must weigh for yourself. I'm not liable fit a brick.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
OK Show me OB7 link.
I haven't installed Noterized Stable 2 yet.

*rolls in a wheelbarrow full of bricks*

CWM RECOVERY doesn't work for me on Note 3 with Lollipop

I've used Odin 3.07 to flash n900t-cwm-recovery-6.0.4.4(1025) but it didn't pass. I'm tired now and I want to go to bed but it bugs me I don't have root.
On 4.2 I think it was easy but on 5.0 it won't work for me, now. I've scoured pages and pages, so for now I am kindly asking for some directions.

Try flashing the latest TWRP and then flash supersu from TWRP to get root.

audit13 said:
Try flashing the latest TWRP and then flash supersu from TWRP to get root.
Click to expand...
Click to collapse
Thanks, did it, it flashed it but now it gives me "Recovery is not Seandroid Enforcing". I pulled the battery right after the pass message, no change.
Read in thread about "Reactivation Lock" but I don't have that option in the stock Lollipop 5.0.
Any ideas?

So your phone is not booting? Boot into download mode and tell us what it says.

Oh no, the phone works fine. I can boot into stock Lollipop but it won't boot into recovery (Vol Up). It boots into Odin Vol Down.
All I want is to install su. First I tried to flash CWM recovery with Odin, didn't pass. Then I tried TWRP (their website is down), it passed but got "Recovery is not Seandroid Enforcing" error. So now I'm lost. I think all have to flash a modified ROM but I'm confused about their specs (what is Deoxified)
Wait wait, Oding IS the recovery, no? I'm totally confused now.

Try this: open Odin and uncheck everything except f.reset time, connect the phone, flash TWRP, when you see the word "reset" in the status window, remove USB cable, remove battery, replace battery, use button combination to boot into recovery.

Thanks for the help. I've tried that sequence before. It didn't work. I'll try it again.
But I've managed to install su using Chainfire's Auto Root for Kitkat (but I have Lollipop). Now I have an older recovery. Will that cause any troubles?
What I've learned from my "ordeal" is make sure you have the right versions. In my case particularly the phone model, N900T, and then the software versions, N900TUVUFOB6, where B6 is the Lollipop (right?).

No no no!
I've rebooted into old recovery now my user interface in Lollipop doesn't work. I guess the recovery deleted some cache (noticed some messages at the bottom)
I guess I'll burn the Lollipop + CF Autoroot for the N-th time and never boot into recovery.

Bogdan45 said:
I've used Odin 3.07 to flash n900t-cwm-recovery-6.0.4.4(1025) but it didn't pass. I'm tired now and I want to go to bed but it bugs me I don't have root.
On 4.2 I think it was easy but on 5.0 it won't work for me, now. I've scoured pages and pages, so for now I am kindly asking for some directions.
Click to expand...
Click to collapse
Do you still need help? If so reply back. I'll do way best to help. Had the three main custom recoveries and had my share of problems and learned from them haha.

LiftedDroid said:
Do you still need help? If so reply back. I'll do way best to help. Had the three main custom recoveries and had my share of problems and learned from them haha.
Click to expand...
Click to collapse
Yes, I do need a working recovery for stock Lollipop 5.0 on Note 3.

Bogdan45 said:
Yes, I do need a working recovery for stock Lollipop 5.0 on Note 3.
Click to expand...
Click to collapse
I used chain fires autoroot 9005, and installed TWRP
Sent from my SM-N9005 using Tapatalk

Bogdan45 said:
Yes, I do need a working recovery for stock Lollipop 5.0 on Note 3.
Click to expand...
Click to collapse
Sorry was busy last few days with minecraft lol. I will get that up in a few and have link for you

Hi there,
I have one question. I have rooted my phone with cf-autoroot method same as you and like you I can't installed custom recovery, weather it be TWARP or CWM. Buy my question isn't this.
I was just randomly checking my app manager for all my apps and found getroot version 1.0 was installed.
Can you confirm me that u have the same thing.
Because it has access to my camera SD card and sms.
Let me know.
Sent from my SM-N900W8 using XDA Free mobile app

No, I don't have it.

tenjohn23 said:
Hi there,
I have one question. I have rooted my phone with cf-autoroot method same as you and like you I can't installed custom recovery, weather it be TWARP or CWM. Buy my question isn't this.
I was just randomly checking my app manager for all my apps and found getroot version 1.0 was installed.
Can you confirm me that u have the same thing.
Because it has access to my camera SD card and sms.
Let me know.
Sent from my SM-N900W8 using XDA Free mobile app
Click to expand...
Click to collapse
Make sure you have patched sd access and set correct path for location.
SD patch
Or use this this version of twrp and open in Odin just as you would cf autoroot.
Uploading now
---------- Post added at 01:40 ---------- Previous post was at 01:30 ----------
tenjohn23 said:
Hi there,
I have one question. I have rooted my phone with cf-autoroot method same as you and like you I can't installed custom recovery, weather it be TWARP or CWM. Buy my question isn't this.
I was just randomly checking my app manager for all my apps and found getroot version 1.0 was installed.
Can you confirm me that u have the same thing.
Because it has access to my camera SD card and sms.
Let me know.
Sent from my SM-N900W8 using XDA Free mobile app
Click to expand...
Click to collapse
Make sure you have patched sd access and set correct path for location.
TWRP 2.8.7 Open Recovery
SD patch
Or use this this version of twrp and open in Odin just as you would cf autoroot.
TWRP 2.8.7.0 4.4
Also thesee are for smn900t I am sure as long as your using any snm900* you OK. Any issues try hard reset and last option do reflash of stock

Bogdan45 said:
Oh no, the phone works fine. I can boot into stock Lollipop but it won't boot into recovery (Vol Up). It boots into Odin Vol Down.
All I want is to install su. First I tried to flash CWM recovery with Odin, didn't pass. Then I tried TWRP (their website is down), it passed but got "Recovery is not Seandroid Enforcing" error. So now I'm lost. I think all have to flash a modified ROM but I'm confused about their specs (what is Deoxified)
Wait wait, Oding IS the recovery, no? I'm totally confused now.
Click to expand...
Click to collapse
the enforcing thing is because you have a custom recovery only, it just tells the user that it isn't factory