Related
Good Morning XDA!!!
I went through the Odin Rooting process last night and everything went as planned. I downloaded CWM Manager through Google Play and when I go to open it up it is telling me that the Super User file is not there. I have put Super USer on my phone but again it tells me I need to root my phone. I will admit I am a bit confused, I can boot into CWM mode but since I am not flashing a new rom at the moment I don't know what I did wrong. I did go into the CWM manager to "Flash ClockworkMod Rocovery" but it downloads then tells me there was na error with command lines..........Is there anyone who can help me out.....I really don't get where I went wrong, cause everything says I rooted the phone.....Thanks for any help......
>'.'<
How did you root? Do you have superuser or supersu installed?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
nicky9door said:
How did you root? Do you have superuser or supersu installed?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yes I did but it also was telling me that it wasn't rooted.....however the only thing that I had was the Superuser App. Is there something i need on the SD card? Or to psychically flash to the phone.....thanks for getting back to me with this....
Go into Settings>Apps>Superuser and clear cache and data. Go into the market and go to SuperUser and see if there is an update. This should update the binaries. Then try a Root App to see if you get the SU toast.
2nd option is to boot into recovery and go to wipe /Cache then advanced and wipe /Dalvik-Cache. While in Advanced, hit Fix Permissions and let it run. Reboot and try a Root App.
Btw, you never said how you rooted. Your title says Odin, so I am assuming mrRobinson's method.
Woodrube said:
Go into Settings>Apps>Superuser and clear cache and data. Go into the market and go to SuperUser and see if there is an update. This should update the binaries. Then try a Root App to see if you get the SU toast.
2nd option is to boot into recovery and go to wipe /Cache then advanced and wipe /Dalvik-Cache. While in Advanced, hit Fix Permissions and let it run. Reboot and try a Root App.
Btw, you never said how you rooted. Your title says Odin, so I am assuming mrRobinson's method.
Click to expand...
Click to collapse
Sorry about that......I used the method from this site....http://www.androidauthority.com/galaxy-s3-sgh-t999-t-mobile-easy-root-99302/
It did everything that was explained was supposed to happen.....its just I get the feeling I missed something somewhere.....I hope this helps....I haven't rooted anything in years.....lol
Ok, so you downloaded ROM manger from the market and tried to run the recovery script and it is saying that you don't have Root correct?
I agree, I think that you did miss a step somewhere. I suspect it was in between the CWR and SuperUser zips.
Are you familiar with Odin? I assume so since your first post said you Odin'd, but just double checking. I suggest you either start over from the link you posted or try mrRobinson's method. It is real easy and gives you stock ROM, rooted and has the option to install a custom recovery (like CWR or TWRP) also.
Here are Odin versions of both CWR and TWRP. Do this after you've done mrRobinson's method. Once it is done with first reboot (don't forget this take the longest time to boot bc it is rebuilding the /Dalvik), reboot back into download mode and flash either CWR or TWRP that way and you should be good to go after that.
Woodrube said:
Ok, so you downloaded ROM manger from the market and tried to run the recovery script and it is saying that you don't have Root correct?
I agree, I think that you did miss a step somewhere. I suspect it was in between the CWR and SuperUser zips.
Are you familiar with Odin? I assume so since your first post said you Odin'd, but just double checking. I suggest you either start over from the link you posted or try mrRobinson's method. It is real easy and gives you stock ROM, rooted and has the option to install a custom recovery (like CWR or TWRP) also.
Here are Odin versions of both CWR and TWRP. Do this after you've done mrRobinson's method. Once it is done with first reboot (don't forget this take the longest time to boot bc it is rebuilding the /Dalvik), reboot back into download mode and flash either CWR or TWRP that way and you should be good to go after that.
Click to expand...
Click to collapse
The last phone I rooted was a Mytouch 4G. I am not familiar with Odin. I just went to the site that I posted in my last reply and followed the directions exactly. I only downloaded the IMG file for ClockworkMod that it supplied. It never told me to install or download a SuperUser zip file. I can boot the phone into CWM after shutting down, but when I open the CWM Manager that I downloaded from Google Play it tells me the following:
" You must root your phone for ROM Manger to function. Superuser was not found at "/system/bin/su" or "/system/xbin/su". Use Google search on your computer to find instructions to root your phone."
I am a uber novice. That's strike one....two....I'm a girl.....lol I just don't want to mess up my phone....it was really expensive......lol Thanks again for all the help you are giving me......it is greatly appreciated......
Ok then. I think you missed something then.
Let's do this. You want to download the latest version of Odin (It is here aboout half way down). Install it on your PC.
Then go to mrRobinson's thread and download this This is based off of the stock image TMO T999UVALH2
Perm Mirrorownload - MD5 Sum: 4abdcf029f248e66caa83c9c8477bdff root66_TMO_T999UVALH2.7z
and follow the directions. Unzip it and put the Root66 file on you PC where you know it is. Put your phone in Download Mode (see instructions in the link above on how to do this) and open Odin.
Click PDA in Odin and point it to Root66 file from above and make sure that nothing else is ticked above or below PDA. Click start. It should take about 5mins but less than 10 and you'll reboot and have a Pass.
Once that is done and your phone is rebooted, you can either install CWM or TWRP in odin or from the market. CWR= ROM Manager app; TWRP=Goo.IM app. Those will install your custom recovery.
Above all read the OPs f the threads I linked. They have valuable info in them.
Also, just because you are a girl has nothing to do with it. I know a few girls and women that are power users and will run circles around most in this forum. Don't sell yourself short.
I gotta get to work, but I'll check in on ya later on. Good luck.
Flash root 666 with Odin then u will have root
Sent from my SGH-T999 using xda app-developers app
Signature.
jinx0117,
Were you able to get it to work ?
Woodrube said:
Ok then. I think you missed something then.
Let's do this. You want to download the latest version of Odin (It is here aboout half way down). Install it on your PC.
Then go to mrRobinson's thread and download this This is based off of the stock image TMO T999UVALH2
Perm Mirrorownload - MD5 Sum: 4abdcf029f248e66caa83c9c8477bdff root66_TMO_T999UVALH2.7z
and follow the directions. Unzip it and put the Root66 file on you PC where you know it is. Put your phone in Download Mode (see instructions in the link above on how to do this) and open Odin.
Click PDA in Odin and point it to Root66 file from above and make sure that nothing else is ticked above or below PDA. Click start. It should take about 5mins but less than 10 and you'll reboot and have a Pass.
Once that is done and your phone is rebooted, you can either install CWM or TWRP in odin or from the market. CWR= ROM Manager app; TWRP=Goo.IM app. Those will install your custom recovery.
Above all read the OPs f the threads I linked. They have valuable info in them.
Also, just because you are a girl has nothing to do with it. I know a few girls and women that are power users and will run circles around most in this forum. Don't sell yourself short.
I gotta get to work, but I'll check in on ya later on. Good luck.
Click to expand...
Click to collapse
Ok, I have gone and downloaded the 3.7 version of Odin and installed it.....I am now waiting as the root666 TMO file is downloading.....and I will try to pick it up from there.......I will keep you posted.... : )
Ok. Good luck. Don't forget to Unzip it before putting in the PDA. Read mrRobinson's OP.
I won't be on until later in the day but there are some very talented people on here that will be able to help.
Woodrube said:
Ok then. I think you missed something then.
Let's do this. You want to download the latest version of Odin (It is here aboout half way down). Install it on your PC.
Then go to mrRobinson's thread and download this This is based off of the stock image TMO T999UVALH2
Perm Mirrorownload - MD5 Sum: 4abdcf029f248e66caa83c9c8477bdff root66_TMO_T999UVALH2.7z
and follow the directions. Unzip it and put the Root66 file on you PC where you know it is. Put your phone in Download Mode (see instructions in the link above on how to do this) and open Odin.
Click PDA in Odin and point it to Root66 file from above and make sure that nothing else is ticked above or below PDA. Click start. It should take about 5mins but less than 10 and you'll reboot and have a Pass.
Once that is done and your phone is rebooted, you can either install CWM or TWRP in odin or from the market. CWR= ROM Manager app; TWRP=Goo.IM app. Those will install your custom recovery.
Above all read the OPs f the threads I linked. They have valuable info in them.
Also, just because you are a girl has nothing to do with it. I know a few girls and women that are power users and will run circles around most in this forum. Don't sell yourself short.
I gotta get to work, but I'll check in on ya later on. Good luck.
Click to expand...
Click to collapse
Ok...I have tried to download the file twice.....it takes about an hour and then when it is done it tells me the file is not there or damaged.....Oh heavens......now what?
jinx0117 said:
Ok...I have tried to download the file twice.....it takes about an hour and then when it is done it tells me the file is not there or damaged.....Oh heavens......now what?
Click to expand...
Click to collapse
Hold on BRB
Ok according to your original post you have recovery. so go here http://forum.xda-developers.com/showthread.php?t=1726088 and download the superuser.zip file and place it on your internal sd card.
Reboot into recovery and flash the superuser.zip and reboot and you will be rooted.
saldebot said:
Hold on BRB
Ok according to your original post you have recovery. so go here http://forum.xda-developers.com/showthread.php?t=1726088 and download the superuser.zip file and place it on your internal sd card.
Reboot into recovery and flash the superuser.zip and reboot and you will be rooted.
Click to expand...
Click to collapse
Ok....I just did what you asked...got the zip and placed it on the internal storage.....booted into CWM and found the file, it installed ok.....here goes nothing....lol
saldebot said:
Hold on BRB
Ok according to your original post you have recovery. so go here http://forum.xda-developers.com/showthread.php?t=1726088 and download the superuser.zip file and place it on your internal sd card.
Reboot into recovery and flash the superuser.zip and reboot and you will be rooted.
Click to expand...
Click to collapse
:victory::victory::victory::victory: It worked!!!!! Thank you so much......every one of you guys who helped me.....Thank you Thank you Thank You!!!!!!!!!!!!!!!!!!!!!!
jinx0117 said:
:victory::victory::victory::victory: It worked!!!!! Thank you so much......every one of you guys who helped me.....Thank you Thank you Thank You!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
You go girl, do your thing...lol i'm happy it worked. Now happy flashing :thumbup:
Good job man. Looks like we may have converted another crack-flasher.
Jinx, first thing you need to do is boot into CWR and make a Nandroid. Save a copy of it to your PC for safe keeping. This will help you recover from any "mishaps".
Why it didn't work
When the phone reboots, it destroys the flags on the root software that was added via Odin.
To get around that problem,
do the odin process again, but uncheck the auto reboot before you start.
Then when the process is finished, take out the battery on the phone.
reinstall the battery after a few seconds, and then....
BE SURE YOU DON'T MISS THIS STEP,
GO INTO cwm PROCESS TO FLASH THE FILE YOU LOADED WITH ODIN.
if you miss the 3 button CWM load it messes up the file and you again have to reload it with odin, so that part is where you might be having the phone not actually root.
Go to this website and watch HOW TO DO IT till you can do it in your mind without any missteps...
Then, It WILL WORK!
Here is the link:
http://galaxys3root.com/galaxy-s3-root/how-to-root-u-s-and-canada-galaxy-s3-sgh-t999sgh-i747sph-l710-fail-proofnoob-proof/
Good Luck!
[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!
Before I get linked to a thread full of geeky complicated replies, please; I already checked 4 threads & came to the conclusion I just wont understand it.
I basically rooted my phone using odin; just used the simple instructions on Max lee's website. Did the Vol up + Power Button + Home, plugged it into my laptop; clicked pda & chosen the .tar file of the note 2 (cwm6-root-note2.tar) Everything went well & my device started without any issues.
My phone works fine, but at first SuperSu would give me this message ' unfortunately supersuhas stopped' So I updated it in the playstore and now get this message 'There is no SU binary installed, this is a problem!'
Its a note II N1705 running Andriod 4.4; any help would be appreciated; I think I have to flash SuperSu or something along these lines, but hope someone can explain me how to do so.
I also read that my phone is 'technically' rooted, so I made sure to try out titanium backup which didn't work because I don't have root access.
Thanks in advance,
5parc said:
Before I get linked to a thread full of geeky complicated replies, please; I already checked 4 threads & came to the conclusion I just wont understand it.
I basically rooted my phone using odin; just used the simple instructions on Max lee's website. Did the Vol up + Power Button + Home, plugged it into my laptop; clicked pda & chosen the .tar file of the note 2 (cwm6-root-note2.tar) Everything went well & my device started without any issues.
My phone works fine, but at first SuperSu would give me this message ' unfortunately supersuhas stopped' So I updated it in the playstore and now get this message 'There is no SU binary installed, this is a problem!'
Its a note II N1705 running Andriod 4.4; any help would be appreciated; I think I have to flash SuperSu or something along these lines, but hope someone can explain me how to do so.
I also read that my phone is 'technically' rooted, so I made sure to try out titanium backup which didn't work because I don't have root access.
Thanks in advance,
Click to expand...
Click to collapse
Here is the Link to cwm recovery that you need to flash with odin 3.09.
http://galaxynote2root.com/cwm-recovery/
I think your phone is 7105 (lte), so download 1 for that. It should be a tar file.
Once it is installed, reboot to recovery and flash supersu zip using option "install zip"
Make sure the supersu zip is for your device. Flashing wrong supersu might brick ur device.
U will find it on chainfire's Web.
Press thumps up if you found this suggestion helpful.
ceomaverick said:
Here is the Link to cwm recovery that you need to flash with odin 3.09.
I think your phone is 7105 (lte), so download 1 for that. It should be a tar file.
Once it is installed, reboot to recovery and flash supersu zip using option "install zip"
Make sure the supersu zip is for your device. Flashing wrong supersu might brick ur device.
U will find it on chainfire's Web.
Press thumps up if you found this suggestion helpful.
Click to expand...
Click to collapse
I downloaded the .tar file? Am I going to use Odin ? Or am I going to do this by only using my phone?
'Flash supersu zip using option install zip?' What do you mean flash
'Makee sure the supersu zip is for your device. Flashing wrong supersu might brick ur device.' You first say I need a tar file then start talking about a zip file? Am completely confused.
Explain this as if you are explaining it to a noob, I don't get it.
EDIT:
I managed to fix my problem after tons of research to translate your post to something more understandable; regardless of that! You got my upvote
5parc said:
I downloaded the .tar file? Am I going to use Odin ? Or am I going to do this by only using my phone?
'Flash supersu zip using option install zip?' What do you mean flash
'Makee sure the supersu zip is for your device. Flashing wrong supersu might brick ur device.' You first say I need a tar file then start talking about a zip file? Am completely confused.
Explain this as if you are explaining it to a noob, I don't get it.
EDIT:
I managed to fix my problem after tons of research to translate your post to something more understandable; regardless of that! You got my upvote
Click to expand...
Click to collapse
Tons of research, really?
You are the first guy who found it difficult to understand my instructions.
Anyway, I am happy you found your way and in the process gained more knowledge.
hlp
i m also having the same trouble,n i also.dun knw wat u saying,but u nid ur hlp,i nid u to show me the step clearly pls,can?
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.
Looked at ALL the referenced similar threads, and none applied to my device. So, with your permission, I would like to ask for information.
I bought a used, off-contract T-Mobile variant of Galaxy S3, SGH-T999. It IS SIM-unlocked, as I am using a Straight Talk-provided AT&T SIM without any problems. Also, it is rooted, as confirmed by Root Checker and running Terminal--I get the "#" prompt. SuperSU is installed and appears functional. However, neither CWM nor TWRP recovery programs are on the device.
How can I tell if my bootloader is unlocked? If it is not, what would you suggest to use to accomplish unlocking? I would like to be able to flash a custom ROM such as CyanogenMod.
Thank you for your help and patience.
Its not locked
The T-Mobile version has an unlocked bootloader. Feel free to flash CWM or TWRP through Odin or by using ADB if you want to use that method.
tonytien said:
The T-Mobile version has an unlocked bootloader. Feel free to flash CWM or TWRP through Odin or by using ADB if you want to use that method.
Click to expand...
Click to collapse
Many thanks to you both, Serio22 and Tonytien! I had no idea that the T999 had an unlocked bootloader; just another good reason to buy it vs. the AT&T variant.
I have read (MANY TIMES!!!) the procedure for using Odin to root the device and install a recovery program. There is one in particular on androidcentral forums (can't post the link just yet!) that uses GalaxyS3RootSprint.zip to root either the Verizon or the T-Mobile variants. The second step uses GalaxyS3RootSprint to flash CWM; then, a third step uses CWM-SuperSU-v0.87.zip to flash a super user program. Since my phone is already rooted and has a working SuperSU program, I wonder if I could use Odin just to flash CWM?
Have either of you ever used Flashify? That was mentioned in another thread on androidcentral as a way to flash with Odin or entering download mode.
I'm kind of spoiled: my last two Samsung smartphones have both had CyanogenMod already installed, with CWM, and I got used to entering recovery mode via the Restart menu.
Anyway, thanks again, and best retards to you both.
tonytien said:
The T-Mobile version has an unlocked bootloader. Feel free to flash CWM or TWRP through Odin or by using ADB if you want to use that method.
Click to expand...
Click to collapse
Oh, one other question. My phone has stock T-Mobile Android 4.3, the "*MJC" software. I have read a number of cautions concerning the MJC software, and that one might not be able to flash CWM or custom ROM's to it. Might that be a problem for installing CWM?
Incidentally, Knox is installed on the phone, but NOT running.
stahlwird said:
Many thanks to you both, Serio22 and Tonytien! I had no idea that the T999 had an unlocked bootloader; just another good reason to buy it vs. the AT&T variant.
I have read (MANY TIMES!!!) the procedure for using Odin to root the device and install a recovery program. There is one in particular on androidcentral forums (can't post the link just yet!) that uses GalaxyS3RootSprint.zip to root either the Verizon or the T-Mobile variants. The second step uses GalaxyS3RootSprint to flash CWM; then, a third step uses CWM-SuperSU-v0.87.zip to flash a super user program. Since my phone is already rooted and has a working SuperSU program, I wonder if I could use Odin just to flash CWM?
Have either of you ever used Flashify? That was mentioned in another thread on androidcentral as a way to flash with Odin or entering download mode.
I'm kind of spoiled: my last two Samsung smartphones have both had CyanogenMod already installed, with CWM, and I got used to entering recovery mode via the Restart menu.
Anyway, thanks again, and best retards to you both.
Click to expand...
Click to collapse
You can flash CWM through Odin, but it'll take some repackaging (.img to .tar.md5) or you can search for one to download since CWM comes in .img form. Again, you could use ADB on a computer to install CWM in its .img form since your phone is already rooted. You could also just download TWRP or some other recovery that comes in .tar or .tar.md5 form, which will already be ready to flash in Odin. I haven't used Flashify, but some of the screenshots on the app listing show some kind of recovery install feature. I can't personally recommend it since I've never used it before.
stahlwird said:
Oh, one other question. My phone has stock T-Mobile Android 4.3, the "*MJC" software. I have read a number of cautions concerning the MJC software, and that one might not be able to flash CWM or custom ROM's to it. Might that be a problem for installing CWM?
Incidentally, Knox is installed on the phone, but NOT running.
Click to expand...
Click to collapse
The latest software version causes some weird things indirectly. I haven't noticed any issues with the latest CM12.1 nightlies, but you may run into issues when trying to flash a custom ROM in recovery. It seems the updater_script (a part of custom ROM zip files that tells the phone what to do when flashing in recovery) doesn't include the latest version in the line that determines if the ROM will work with the phone or not (a simple software version text comparison to make sure you won't brick your phone). This can be easily fixed since it's just a text file inside a custom ROM that can be easily modified. The software itself doesn't cause issues with system modification other than some interference with root (which, since you've told me your phone is already rooted, I assume you've figured it out). Keep in mind that the stock ROM could replace your custom recovery upon reboot (I think), which could be fixed by deleting the files 'install-recovery.sh' and 'recovery-from-boot.p' located in /system/etc/. If you're installing a custom ROM, you won't need to worry about that. Also, your Knox Warranty Bit will be tripped (your phone now definitely has a void warranty) but I'm sure you know since you're rooting and stuff. Sorry about the late response, let me know if you have any questions on anything I missed, I'm kind of jumping around with things that come to mind.
I have used flashify and do recommend it. Very easy to use and can select from different recoveries. MJC is not a problem as far as flashing recoveries or roms. Probably one of the only problem is as the poster above stated, but it may be fixed by now by developers
tonytien said:
The T-Mobile version has an unlocked bootloader. Feel free to flash CWM or TWRP through Odin or by using ADB if you want to use that method.
Click to expand...
Click to collapse
Hope you two guys (Serio22 and tonytien) don't mind if I pick your brains a bit more. Flashing via phone download mode and Odin doesn't look too bad, but I keep reading all these posts about guys bricking their phones. I CAN'T do that--- this is my PHONE, not a PC I can play around with! Seems you have to have a version of Odin that matches your installed OS AND your particular phone variant, then the CWM version must match both of those. If anything doesn't match, it's brick city! I did finally find a site that lists the current version of Odin (3.07) for the T-Mobile SGH-T999 running the MJC version of 4.3 JellyBean, and it lists the matching version of CWM (6.0.1.2). So, using that site as a guide, I think I might get brave and try to flash CWM that way rather than use Flashify. But, thanks for your comments on it as well.
Far cry from flashing the next nightly on CM using CWM! There was usually a natural path of progression---CM 9.1 to 9.2, then to 10.0, 10.1, etc. There was never a need to jump around and risk bricking. AND, going into Recovery for CWM was a simple option in the Reboot menu, not having to hold down 3 keys and release one at just the right time. I lived thru two phones with CyanogenMod and ClockworkMod, and only went backwards once: I flashed a nightly that I didn't really like. It was a simple matter to go into CWM and restore from the previous Nandroid backup.
Anyway, thanks for your suggestions, help, encouragement, and your ears (eyes?).
tonytien said:
The T-Mobile version has an unlocked bootloader. Feel free to flash CWM or TWRP through Odin or by using ADB if you want to use that method.
Click to expand...
Click to collapse
Oh, one more thing I forgot to mention, and ask about.
When I boot my phone into download mode, the items on the screen are these:
Product name: SGH-T999
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
Qualcomm Secure Boot: Enable
Warranty Bit: 0
Bootloader RP Swrev: 1
Not sure how to interpret these, as I've not found anywhere they are defined, other than the presence of the "Warranty Bit" line indicates I'm on 4.3, JellyBean. I'm assuming the Status of Custom is because I'm rooted.
stahlwird said:
Oh, one more thing I forgot to mention, and ask about.
When I boot my phone into download mode, the items on the screen are these:
Product name: SGH-T999
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
Qualcomm Secure Boot: Enable
Warranty Bit: 0
Bootloader RP Swrev: 1
Not sure how to interpret these, as I've not found anywhere they are defined, other than the presence of the "Warranty Bit" line indicates I'm on 4.3, JellyBean. I'm assuming the Status of Custom is because I'm rooted.
Click to expand...
Click to collapse
Yes and yes. Warranty Bit was introduced in 4.3 bootloader
serio22 said:
Yes and yes. Warranty Bit was introduced in 4.3 bootloader
Click to expand...
Click to collapse
Well, successfully flashed CWM 6.0.1.2 non-touch to my phone (I think--more below). Used the Odin/TAR method, and it was painless.
When I boot into Recovery mode, the line at the top of the screen does say "ClockworkMod Recovery v6.0.1.2", but the rest of the options on that screen look just as they did before. Went to "Advanced" and chose "Show log", and I saw some lines that concern me, to wit:
Checking for extendedcommand
Skipping execution of extendedcommand. file not found...
Can't partition non-vfat: datamedia
Can't partition unsafe device: /dev/block/mmcblklpl
Can't format unknown volume: /emmc
init.svc.recovery=running
service.adb.root=1
init.svc.adbd=running
Then, when I run my X-plore File manager, I see NO ClockworkMod folder, either on my Internal or External SD cards. Do I really have it?
One last point: while looking around for the procedures to do this, I came across a video that showed using ROM Manager to load CWM. Even tho the Odin procedure seemed to work, I wonder...... Any opinions on that?
Thanks again for your reading this.
stahlwird said:
Well, successfully flashed CWM 6.0.1.2 non-touch to my phone (I think--more below). Used the Odin/TAR method, and it was painless.
When I boot into Recovery mode, the line at the top of the screen does say "ClockworkMod Recovery v6.0.1.2", but the rest of the options on that screen look just as they did before. Went to "Advanced" and chose "Show log", and I saw some lines that concern me, to wit:
Checking for extendedcommand
Skipping execution of extendedcommand. file not found...
Can't partition non-vfat: datamedia
Can't partition unsafe device: /dev/block/mmcblklpl
Can't format unknown volume: /emmc
init.svc.recovery=running
service.adb.root=1
init.svc.adbd=running
Then, when I run my X-plore File manager, I see NO ClockworkMod folder, either on my Internal or External SD cards. Do I really have it?
One last point: while looking around for the procedures to do this, I came across a video that showed using ROM Manager to load CWM. Even tho the Odin procedure seemed to work, I wonder...... Any opinions on that?
Thanks again for your reading this.
Click to expand...
Click to collapse
Did you flash recovery and then reboot straight into recovery without it letting boot the system? If not, do so. You shouldn't need any app to boot recovery, but you can use one if you like. Just a preference
serio22 said:
Did you flash recovery and then reboot straight into recovery without it letting boot the system? If not, do so. You shouldn't need any app to boot recovery, but you can use one if you like. Just a preference
Click to expand...
Click to collapse
No. I checked the restart box in Odin, and it did restart the system normally into JB. Then, I shut down completely and did the 3-button boot into Recovery.
Got an update, however. Since I saw those entries in the log, I decided to try the ROM Manager flash of CWM. Downloaded ROM Manager from the Play Store, and started it. It said it needed to update the recovery, and I let it update to CWM v. 6.0.4.5, and everything looked good. Checked the log, and no entries for concern. BTW, it offered the "Touch" version of CWM, but I declined that, going with the old fashioned side-button version.
Got one other question, however. On my CyanogenMod phones, when I got into CWM, the backup option was for Nandroid backup. But, the version I have on this phone doesn't even mention that. Is that an add-on of some sort?
Thanks again for your help!
Best regards,
Stahlwird
stahlwird said:
No. I checked the restart box in Odin, and it did restart the system normally into JB. Then, I shut down completely and did the 3-button boot into Recovery.
Got an update, however. Since I saw those entries in the log, I decided to try the ROM Manager flash of CWM. Downloaded ROM Manager from the Play Store, and started it. It said it needed to update the recovery, and I let it update to CWM v. 6.0.4.5, and everything looked good. Checked the log, and no entries for concern. BTW, it offered the "Touch" version of CWM, but I declined that, going with the old fashioned side-button version.
Got one other question, however. On my CyanogenMod phones, when I got into CWM, the backup option was for Nandroid backup. But, the version I have on this phone doesn't even mention that. Is that an add-on of some sort?
Thanks again for your help!
Best regards,
Stahlwird
Click to expand...
Click to collapse
Not sure, I use twrp. Haven't used cwm in ages