[SGH-I337M] CF-Auto-Root [CANADIAN MODELS ONLY] - AT&T Samsung Galaxy S 4 Original Android Developme

Check your device model ! Settings -> About device -> Model number. See the third post for exact supported model numbers. If your device is a totally different model, it will not work (may even brick) !
CF-Root is the root for "rooting beginners" and those who want to keep as close to stock as possible. CF-Root is meant to be used in combination with stock Samsung firmwares, and be the quickest and easiest way for your first root.
Donate
CF-Root has been available for many devices (Galaxy S1, Galaxy Tab 7", Galaxy S2, Galaxy Note, Galaxy Nexus, Galaxy S3, and many more) and has clocked over 13 million downloads. This is not even counting custom ROMs that already include it. Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every CF-Root user has donated me $1...
What's installed
- SuperSU binary and APK
- Stock recovery
Installation and usage
Flash the CF-Auto-Root package as PDA in ODIN (details on how to do that are in next post), and your device should reboot into a modified recovery (signified by a large red Android logo) and it will install SuperSU for you and restore the stock recovery, and reboot back into Android.
If you don't get to the red Android logo, boot into recovery manually ("adb reboot recovery", or boot while holding Power+VolUp+Home).
Using this root increases your flash counter. You should run Triangle Away (see below) after rooting to reset the counter. Note that if you want to run custom kernels or custom recoveries, your flash counter will be set to 1 at every boot. Either configure Triangle Away to reset the counter at every boot (Play version only) or only reset the counter when you need to go into warranty.
Did you see the red Android logo during rooting, but SuperSU does not appear? This may sometimes occur due to left-over files and settings, however, you can usually install SuperSU from Google Play at this stage and it'll just work.
Why isn't this just called CF-Root
The traditional CF-Root's included a custom recovery (CWM, TWRP, etc) and were meant for devices that had a single kernel/recovery combination. CF-Auto-Root doesn't include a custom recovery and is meant for devices that have kernel and recovery separate (so you can manually install any custom recovery you wish). The Auto part comes from the fact that a large part of the process is automated (though it constantly needs adjusting)
Not included - Triangle Away
Triangle Away can be used to reset the flash counter after installing CF-Root. The flash counter keeps track of how many custom firmwares you have flashed, as this voids warranty. (No idea what this about ? Read up on it, you will want to use this !)
Not included - adbd Insecure
As this CF-Root does not include a custom kernel, adb shell does not have root access by default (you can still get it by typing su inside the shell), nor is adb remount supported, nor will adb push and adb pull work on system files. adbd Insecure can be used to remedy this situation. (No idea what this is about ? Don't worry about it !)
CF-Auto-Root homepage
http://autoroot.chainfire.eu/
CF-Auto-Root main thread
[CENTRAL] CF-Auto-Root
For requests for new roots and generic discussion - please keep device specific discussion in the thread you are viewing now.

ODIN Installation (detailed)
Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Download and unzip the CF-Auto-Root-....zip file (see posts below this one)
- If you end up with a recovery.img and cache.img file, you've extracted twice. You need to end up with a .tar.md5 file - don't extract that one
- (USB) Disconnect your phone from your computer
- Start Odin3-vX.X.exe
- Click the PDA button, and select CF-Auto-Root-....tar.md5
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
- (USB) Connect the phone to your computer
- Make sure Repartition is NOT checked
- Click the Start button
- Wait for Android to boot
- Done (if it took you more than 30 seconds, you need practise!)
NOTE: Sometimes the device does *not* boot into recovery mode and root your device. Just do the entire procedure again if this happens. If it still will not install root and such, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
New to Samsung? Unfamiliar with Odin? Think all the above is a hassle? Get used to it. It's very simple, and us Samsung folk use Odin (or Mobile ODIN ) for everything! It's so very very convenient once you get used to it. Notice the 30 second comment above? For experienced users, the entire process indeed takes only 30 seconds!
You may now optionally want to install and run Triangle Away to reset the flash counter.

2013.05.20 --- CF-Auto-Root
SuperSU: v1.30
Download
SGH-I337M: CF-Auto-Root-jfltecan-jfltevl-sghi337m.zip
Other models
International Samsung Exynos GT-I9500: http://forum.xda-developers.com/showthread.php?t=2292615
International Qualcomm Snapdragon GT-I9505: http://forum.xda-developers.com/showthread.php?t=2219803
Sprint: http://forum.xda-developers.com/showthread.php?t=2291827
T-Mobile: http://forum.xda-developers.com/showthread.php?t=2294005
AT&T: Bootloader locked, do not use CF-Auto-Root on it
VZW: Bootloader locked, do not use CF-Auto-Root on it
History
2013.05.24: SuperSU v1.30

Worked wonderfully!
Sent from my SGH-I337M using xda app-developers app

Awesome work, any possibility of an ATT USA version? Just got my 32Gb Black Mist delivered today by UPS!

Exellent.
Perfect like always!!! UR the best

very nice thaks a lot i had my s4 almost 3 weeks i was wiating your post finly i got it today . love it so easy root it thanks again.
just i need to ask wen rooted s4 in stats says now custom not official if i flash Triangle Away it will come agian official in stats or not? thanks adv- .

one question, is this really easier than just installing samsung drivers, checking debug and pressing run.bat on motochopper??? if anybody thinks thats hard, maybe they need a motorola razr. I dont want to offend you chain because i love your work, but i dont understand why you invested time into this
---------- Post added at 02:08 AM ---------- Previous post was at 02:07 AM ----------
wasimahmad said:
just i need to ask wen rooted s4 in stats says now custom not official if i flash Triangle Away it will come agian official in stats or not? thanks adv- .
Click to expand...
Click to collapse
Check this thread:
http://forum.xda-developers.com/showthread.php?p=41845225#post41845225

highaltitude said:
Awesome work, any possibility of an ATT USA version? Just got my 32Gb Black Mist delivered today by UPS!
Click to expand...
Click to collapse
ATT version has a locked bootloader, and you already need root to apply a hack to flash and run custom firmwares on it. As such, CFAR wouldn't be much use on it. It may be so at a later stage (amongst other things that would probably require a different bootloader unlock method than is used now) that you need an old ATT firmware to be even to unlock, then need something like CFAR to root a newer firmware, but for now that seems unlikely. And even if that were the case, it would still be confusing and people would try to use CFAR on their locked device which could result in brickage (worst case).
wasimahmad said:
very nice thaks a lot i had my s4 almost 3 weeks i was wiating your post finly i got it today . love it so easy root it thanks again.
just i need to ask wen rooted s4 in stats says now custom not official if i flash Triangle Away it will come agian official in stats or not? thanks adv- .
Click to expand...
Click to collapse
Triangle Away can work to reset "flash counter" and "binary status" (though the current version sometimes the modification doesn't stick - update coming). As I've explained a hundred times probably but nobody listens and everybody keeps repeating the wrong information: the custom system status is scanned by the Samsung firmware and set in the bootloader. One of two truly reliable way to keep that status set to official is to unroot and flash a stock firmware. There are some other workarounds (like some of the advanced options in Triangle Away) that will keep that value official *most* of the time, but nothing 100% foolproof longterm - no matter what others tell you. The other reliable way is to first have that value reset to official using a forementioned method, than flash a modified system that has all the detection stuff patched out and/or removed.
polish_pat said:
one question, is this really easier than just installing samsung drivers, checking debug and pressing run.bat on motochopper??? if anybody thinks thats hard, maybe they need a motorola razr. I dont want to offend you chain because i love your work, but i dont understand why you invested time into this
Click to expand...
Click to collapse
Exploit vs firmware root. Think about it for a while.

Was definitely hoping and waiting that you release this, awesome work as always!!!

Thank you for CF Auto Root! Any chance there will be support for the SGH-I337M in Mobile Odin?
Sent from my SGH-I337M using xda app-developers app

hi
MR Chainfire bundle of thanks for reply your triangle away works flawlessly brought my phone s4 from custom to official and zero binary. i selected both options: auto reset at boot and allowed tracker to run. Then i restarted the phone and it says counter zero and status official
thanks for all the help and your hard work.
---------- Post added at 05:15 AM ---------- Previous post was at 04:57 AM ----------
is that mobile odin pro dos sport s4 yet or not thanks adv. ?

Finally! Rooting Right Away, the only method I trust in and from the best developer out there. Thanks man!
:thumbup:
Sent from my SGH-I337M using xda premium

When you say Canadian models, does that include the Wind variants too.. or is that a different? Would I have to use the T-Mobile version for the Wind variant?

Any chance to support triangle away? I tried the one linked in OP and it didn't work
I see that you said it doesn't stick, is that the same as it just never working? It worked great on my S3 but on my S4 it just reboots and does nothing

10cheesecakes said:
When you say Canadian models, does that include the Wind variants too.. or is that a different? Would I have to use the T-Mobile version for the Wind variant?
Click to expand...
Click to collapse
Yes that includes Wind, all Canadian variants. Do not use the t-mobile one.

just curious you did not mention the i337m bootloader is locked. Therefore after we flash this through odin are we able to flash custom roms. Just curious. thanks

casualt said:
just curious you did not mention the i337m bootloader is locked. Therefore after we flash this through odin are we able to flash custom roms. Just curious. thanks
Click to expand...
Click to collapse
Yes. I would make a nandroid first off course.
Sent from my SGH-I317M using Tapatalk 2

I think canadian models don't have bootlock
Sent from my SGH-I337M using xda premium

Now just mobile Odin and we're on top of the hill....
JKAY DELUXE [I9300 JB 4.1.2]

Related

Samsung Galaxy Relay 4G Information Portal

I'm going to start collecting the various little tid-bits of information that we have scattered across the threads here to hopefully compensate without having a dedicated forum. Eventually I'll add some other guides and such from personal experience, if you know of any Relay related threads or other information located on the interwebs, please drop a link here!
Standard Disclaimer: I am not responsible for what you do to your phone. The information contained in this thread is here to help you do [anything] correctly. If you follow the instructions listed there-in you will be fine, and ask questions if you don't understand something. I am not responsible for what you do with and/or to your phone. If you are unsure about a procedure's outcome, do not proceed with the procedure.
(1)
How to Get Into Download Mode:
1. Hold Power, Vol Down, and Home button simultaneously
2. When "Samsung" appears on the screen let go of the power button but keep the other two pressed down
3. Voila!
Click to expand...
Click to collapse
ROMS:
[CM9][ALPHA]Galaxy S Relay 4G [12/8]
(Use the updated link below instead.) Stock + Odin Flash (+ Rooted System Img File)(Simplified Instructions)
Updated Stock ROM (Has LH1 flash-able via ODIN) Post + tested Tethering Fix(1)
How I reverted my phone to stock + root.
Update from LH1 to LMA2 On Stock ROM w/ preserved root (doesn't remove if you have root, but doesn't give you root) (Untested)
Update from LJ1 to LMA2 on Stock ROM w/ preserved root (doesn't remove if you have root, but doesn't give you root) (Untested)
Root:
[root]\{cm9} samsung galaxy relay 4g (updated 11/19)
General Discussion:
Galaxy S Relay 4G Development Thread
Miscellaneous Information:
Keyboard Customization:
Dillalade's Explanation on How To Set Custom Key Mapping(1)
jarrodlombardo's Key Mapping (Follow Dillalades's guide first)
orange808's Key Mapping
Unsorted, Need to Organize and Determine Relevance (If still applicable or OLD information) or Flesh out supporting information:
nopty's Hiemdal Method (Need to use Heimdal 1.41RC1 or Higher from This Post) (gee ones building heimdal for ubuntu 12.04)
AndriodForums Relay Forum
Sim Unlocking (Need to Verify - Unknown Method) (Sorta Verified)
Nardholio's Links to Create an Odin Flashable Image
NV Dump Backup (Important in case of corrupted IMEI)
Nardholio's Flash Counter Information
gee one dive's into nard's stock rooted img in response to Qualcomm secure boot
nopty's CWM recovery post (10-11-201) Odin Flashable of nopty's CWM Recovery
kornyone's introduction
How to change/remove startup/shutdown sounds
dillalade has issue with 64gb card w/ resolution to issue
fantomex's Andriod WPA2 PSK Authentication issue and resolution
Skinomi Skins for the Relay
gee one fixes his bootloop
gee one's list of bloatware Bloatware gee one was able to remove
Sim Unlocking for those who purchased Retail (no contract)
dillalade's guide to getting Google Now to work on the stock ICS Rom
Nardholio's Untested Tethering Fix
T-mobiles KIES LH1 Update Support Page
gee one investigates the efs partition on the relay Nardholio's response
CWM-Only Flash-able LJ1 Modem
Some changes from stock LH1 to LJ1
Reserved
Reserved 2
Just in Case
how about a link to the original factory rom to restore back to before CM9 ?
Kaczman said:
how about a link to the original factory rom to restore back to before CM9 ?
Click to expand...
Click to collapse
I found one that might work for you, update the OP with the info.
I've got to flash my relay to stock and when I do I'll create a small guide. For now I found an older flash that could be used then KIES could update this ROM to the current LH1 (Need to verify build number).
I need a stock rooted rom, while traveling through the mountains the switching in CM9 isn't working correctly (phone constantly looses service when switching from 4g>3g>Edge frequently).
Here's another sim unlock. I can verify this one as working since I am now using my phone with Solavei. I purchased my phone directly from t-mobile (no contract). I used an AT&T sim to do this method.
http://forum.xda-developers.com/showpost.php?p=36400199&postcount=783
Sent from my SGH-T699 using Tapatalk
Spoxy said:
Here's another sim unlock. I can verify this one as working since I am now using my phone with Solavei. I purchased my phone directly from t-mobile (no contract). I used an AT&T sim to do this method.
http://forum.xda-developers.com/showpost.php?p=36400199&postcount=783
Sent from my SGH-T699 using Tapatalk
Click to expand...
Click to collapse
Thank you!
Update OP. It's still in the unorganized section, but it's there!
Thank you, is a very useful guide ! :good:
You should post your first post from this thread in the request thread to show everything going on. Should work better than just posting "Samsung Relay, please"
That's the plan after I get it organized. I'm also going to follow the instructions given by kinfauns.
It's a start.
Never really notice that many steps when you go through it quickly, but this is the process that I used to revert my CM9 + CWM recovery to Stock rom + Stock Recovery. I don't know if it was supposed to happen that way, but it did. After flashing the stock PDA file (via odin) I was able to flash the CWM recovery again while adding root to the stock rom.
All of the items talking about (roms, odin, root, ect) except a program to unzip the files can be found in links in the thread in my signature. For reference, I use 7zip and just rightclick>7zip>extract to folder.
How to go Back to stock w/root from CM9:
Download stock rom (newest is the LJ1 tar.rar).
Download Odin
Unzip LJ1 into it's own folder. Navigate to where you unzipped the file.
Rename unzipped file to remove .md5 so it ends in ".tar" instead of ".tar.md5"
Unzip Odin (into it's own folder, navigate to the folder)
Put phone in download mode (Instructions are quoted in the OP of the thread in my sig)
Start Odin (assuming that you have already plugged the usb cable into your computer)
Connect phone (that's in download mode) to computer via USB cable.
ODIN Will have blue "Added!" box after it's recognized the phone (2nd box from the top left)
In ODIN, click the "PDA" Box and select the .tar for LJ1 (the file you unzipped and renamed)
Uncheck the "auto-restart" radiobox under "Added!". Then Click Start.
Wait for odin to finish. Do not touch your phone or click any buttons in the odin program. After It's done, reboot the phone.
Go into recovery mode on the phone (Vol Up Instead of Vol Down)
Wipe SDCard and cache
Reboot phone. It may take a few minutes to pass the samsung screen. The phone will vibrate briefly as is finishes booting
Sign into the phone (google, facebook, ect...this is probably a skipable step).
Turn off phone. Reboot into download mode (Vol Down)
Download nopty's CWM recovery
Unzip file (into it's own folder, navigate to it), removing the .md5 like the file above
Connect phone to computer, after ODIN recognizes ("Added!") it click the PDA button
Navigate to the unzipped and renamed (".tar") CWM file and select it.
Unceck "Auto-Reboot". Click start
Wait to finish, then power off and reboot phone
After phone has re-booted connect to computer
After connected to computer, transfer SuperSU zip(CWM Flashable) to SD card (You'll need to download this too, can be found in the Updated Stock Roms link)
After that's transferred, reboot phone into recovery mode. (Vol Up)
Use CWM to flash the SuperSU zip
Reboot phone
Congrats, you now have a stock rooted phone!
Just the basic frame for the guide, will update with links and what little troubleshooting I know and add guide to OP after it's finished.
Working with you guys is awesome.
Anyways, you guys know the drill.
New Device Request Forum
I may be naive, but I would like to equivocate a thanks with a "signed" on the post above.
PM'd kinfauns, lets hope that he can help us get to the right people!
thanks
thanks
So, has anyone else gotte the software update notification and felt brave enough to run it? I don't want to have what happened with the G2 with their first update and lose root.
Also, the damn notification icon won't go away despite postponing the update.
zakiancel said:
thanks
Click to expand...
Click to collapse
your welcome
mikeybot said:
So, has anyone else gotte the software update notification and felt brave enough to run it? I don't want to have what happened with the G2 with their first update and lose root.
Also, the damn notification icon won't go away despite postponing the update.
Click to expand...
Click to collapse
Not yet for me. I'm playing around with a stock rooted (debloated) rom that gee one made right now, I didn't get the OTA update message though. If you do "update" you should still be able to flash CWM and enable root/superuser again. Keep up updated!
Help
I am thinking of buying this phone with such great hardware....but one important question....does this handset have a common 'broken compass' issue?!!!...came across a couple of post with such issues....btw why dont we have a dedicated forum for this famous device?
tany.jags said:
I am thinking of buying this phone with such great hardware....but one important question....does this handset have a common 'broken compass' issue?!!!...came across a couple of post with such issues....btw why dont we have a dedicated forum for this famous device?
Click to expand...
Click to collapse
Broken compass?
I remember seeing a few posts about it too, but I didn't flag them unfortunately. Post the question in the Development thread and we may be able to get you an answer quicker :good:.
tany.jags said:
I am thinking of buying this phone with such great hardware....but one important question....does this handset have a common 'broken compass' issue?!!!...came across a couple of post with such issues....btw why dont we have a dedicated forum for this famous device?
Click to expand...
Click to collapse
Broken? No, but on occasion, it does momentarily glitch up, but once you start moving it clears itself up. Nothing like what would happen with the G2. (I do also have GPS Status installed as well)
I did run the update after taking a look through the zips and deciding to take the plunge and see; and it does reflash the recovery, and while I do have Odin, I have as yet been unable to flash any CWM again. There are no errors, it just doesn't work. I am as yet hopeful though and will report my progress. I didn't see anywhere in the update where it updated the bootloader, so flashing should still work.

[Q] Where to start the root process?

I have a GT-N8013 Galaxy Note 10.1 Wireless 16G. It has been updated to Jelly Bean and has been updated to JB through the Keis OTA and has also just recently received one or two other updates, for what reason I am not sure.
I just recently rooted my Droid Razr Maxx and so far, I am happy that I did that. Now I want to go ahead and root my Note 10.1, however I am thoroughly confused as to where to start. Through all of my Google searches and message board searches, I keep coming across what seems to be older instructions for updating to JB, which I already have, or rooting based upon apps that were in existence as far back as say August, 2012.
Well now it is the end of March, and I do not know if I should be pursuing this using Odin (which version and where is the best place from which to download it) or is there an alternative or better approach using CM 10, etc. As I typed the question, the last similar threads that popped up were from November 30, 2012 and prior.
I wanted to avoid having to ask what to many of you seems to be such a basic question, but there just doesn't seem to be anything that I see out there that has a recommended method, post OTA JB.
Any advise will be greatly appreciated.
bookbean said:
I have a GT-N8013 Galaxy Note 10.1 Wireless 16G. It has been updated to Jelly Bean and has been updated to JB through the Keis OTA and has also just recently received one or two other updates, for what reason I am not sure.
I just recently rooted my Droid Razr Maxx and so far, I am happy that I did that. Now I want to go ahead and root my Note 10.1, however I am thoroughly confused as to where to start. Through all of my Google searches and message board searches, I keep coming across what seems to be older instructions for updating to JB, which I already have, or rooting based upon apps that were in existence as far back as say August, 2012.
Well now it is the end of March, and I do not know if I should be pursuing this using Odin (which version and where is the best place from which to download it) or is there an alternative or better approach using CM 10, etc. As I typed the question, the last similar threads that popped up were from November 30, 2012 and prior.
I wanted to avoid having to ask what to many of you seems to be such a basic question, but there just doesn't seem to be anything that I see out there that has a recommended method, post OTA JB.
Any advise will be greatly appreciated.
Click to expand...
Click to collapse
Some of the rooting methods have been defeated by Samsung with the last 2 updates.
Zedomax has a root method that does work will the most current firmware updates and his version of CWM that is installed with his root method seems to be more compatible with a few of the custom ROM's out there.
You should visit these links, they are very informative.
http://forum.xda-developers.com/showthread.php?t=1831152
http://rootgalaxynote.com/galaxy-note-10-1-root/how-to-root-galaxy-note-10-1-easiest-methodcwmmethod-2/
Root Video Link
http://www.youtube.com/watch?feature=player_embedded&v=nIYiXzcW7xs
Un-Root directions
http://rootgalaxynote.com/galaxy-note-10-1-2/how-to-unrootunbrick-galaxy-note-10-1-factory-firmware/
Did not succeed with root
kkretch said:
Some of the rooting methods have been defeated by Samsung with the last 2 updates.
Zedomax has a root method that does work will the most current firmware updates and his version of CWM that is installed with his root method seems to be more compatible with a few of the custom ROM's out there.
You should visit these links, they are very informative.
http://forum.xda-developers.com/showthread.php?t=1831152
http://rootgalaxynote.com/galaxy-note-10-1-root/how-to-root-galaxy-note-10-1-easiest-methodcwmmethod-2/
Root Video Link
http://www.youtube.com/watch?feature=player_embedded&v=nIYiXzcW7xs
Un-Root directions
http://rootgalaxynote.com/galaxy-note-10-1-2/how-to-unrootunbrick-galaxy-note-10-1-factory-firmware/
Click to expand...
Click to collapse
I carefully watched the video. After the CWM-SuperSU-v0.94.zip file was transferred onto my external drive, I ran odin3 v1.85exe and got to the green pass screen. After the reboot, I held down the power and volume up buttons until I saw the screen go off. When the logo came up, I let go of the power button and I kept holding onto the power up button, but I did not get to the ClockworkMod Recovery screen. Instead, I was brought to the Android Recovery Screen. I tried clicking on the file on the external SD from that screen, but all that I got were failures.
What other options are there?
Thank you, btw, for trying to assist me.
bookbean said:
I carefully watched the video. After the CWM-SuperSU-v0.94.zip file was transferred onto my external drive, I ran odin3 v1.85exe and got to the green pass screen. After the reboot, I held down the power and volume up buttons until I saw the screen go off. When the logo came up, I let go of the power button and I kept holding onto the power up button, but I did not get to the ClockworkMod Recovery screen. Instead, I was brought to the Android Recovery Screen. I tried clicking on the file on the external SD from that screen, but all that I got were failures.
What other options are there?
Thank you, btw, for trying to assist me.
Click to expand...
Click to collapse
You did something wrong....... Did you do power and vol down at the same time first 1:40 of video after that run odin again.
It maybe better to download video in1080p to your computer so you can watch easier.
Resolved with an alternative process
kkretch said:
You did something wrong....... Did you do power and vol down at the same time first 1:40 of video after that run odin again.
It maybe better to download video in1080p to your computer so you can watch easier.
Click to expand...
Click to collapse
I used Odin, but found another root method called CF-Auto-Root-p4notewifi-p4notewifiue-gtn8013.zip. That worked like a charm. I then installed Root Checker to ensure that it worked, which it did.
So now I need to know what applications I need to install next as a follow-up.
I don't believe Auto root installs CWM. You may need to get Mobile ODIN, there's a free version on XDA or a paid version in the play store... I prefer to get the licenced version as there's more things you can do.
After installing this, you can then put the CWM file on your sd card or internal memory and flash it or just flash a custom rom...
Flashing a custom rom should put a custom recovery on too...
You might want to download and run an app called triangleaway to reset your flash counter too...
Moving right along
ultramag69 said:
I don't believe Auto root installs CWM. You may need to get Mobile ODIN, there's a free version on XDA or a paid version in the play store... I prefer to get the licenced version as there's more things you can do.
After installing this, you can then put the CWM file on your sd card or internal memory and flash it or just flash a custom rom...
Flashing a custom rom should put a custom recovery on too...
You might want to download and run an app called triangleaway to reset your flash counter too...
Click to expand...
Click to collapse
Thank you all for helping this root noobie. So I am running CWM Recovery v6.0.0.1.1 right now and doing a full backup to my external card. Seems like it should be done pretty soon. The blue widget in Andy's belly doesn't seem to move too much, if at all, however I do see that the progress bar is moving along and the file names keep changing below "backup up data...".
On top of Andy's head are three little guys with the words "High on Android" across his head. Oops, now I'm getting messages about skipping backup of apps and the fact that No sd-ext found. I don't understand that as there is most certainly an ext SD card.
Assuming that this completes OK, I will next proceed for CM10 and Triangleaway, unless there are other recommendations. Now back to the main Backup and Restore screen. Sorry for the blow by blow, but this is all new to me. Would my Titanium license provide the same benefits?
Here are a few good must haves for me.
Triangle Away
https://play.google.com/store/apps/details?id=eu.chainfire.triangleaway&feature=search_result#?t=W251bGwsMSwxLDEsImV1LmNoYWluZmlyZS50cmlhbmdsZWF3YXkiXQ..
Carbon - App Sync and Backup
https://play.google.com/store/apps/details?id=com.koushikdutta.backup
AirDroid (better than Kies for wireless file transfer)
https://play.google.com/store/apps/details?id=com.sand.airdroid
MyScript Calculator
https://play.google.com/store/apps/details?id=com.visionobjects.calculator
.
Triangle Away
kkretch said:
Here are a few good must haves for me.
Triangle Away
https://play.google.com/store/apps/details?id=eu.chainfire.triangleaway&feature=search_result#?t=W251bGwsMSwxLDEsImV1LmNoYWluZmlyZS50cmlhbmdsZWF3YXkiXQ..
Carbon - App Sync and Backup
https://play.google.com/store/apps/details?id=com.koushikdutta.backup
AirDroid (better than Kies for wireless file transfer)
https://play.google.com/store/apps/details?id=com.sand.airdroid
MyScript Calculator
https://play.google.com/store/apps/details?id=com.visionobjects.calculator
.
Click to expand...
Click to collapse
I went ahead and downloaded Triangle Away. When I start in download mode, I receive the warning along with the big yellow triangle. After pressing volume up to continue, it goes into Odin Mode (in Red) and shows that the Custom Binary Download: Yes (5 counts), followed by Current Binary: Custom and then System Status: Custom. To get out of that screen, I have just held down the power button to turn off the device.
When I start up the Triangle Away app, the current status (under Flash Counter) says that Status cannot be determined, need to reboot into a special bootmode - tap "Reset flash counter".
In the Overview section on Play Store, it shows this warning:
On a number of devices, TriangleAway can work, but your firmware may not be supported directly. In that case, the app will tell you it needs to reboot into a special boot mode, which will be happen if you select "Reset flash counter". The device will reboot into a special mode which will allow you to review the current status and reset the binary and flash counter values (or abort and do nothing). On some devices this will actually trigger the counter to 1 if its 0 - so if you're "just checking", do that in download mode!
!!! THIS IS A DANGEROUS OPERATION AND COULD POTENTIALLY BRICK YOUR DEVICE. PROCEED AT YOUR OWN RISK. A USB JIG IS PREFERRED IF YOU HAVE A WORKING ONE !!! ( and by brick I mean brick - only a board replacement or a JTAG unit will be able to save you, don't mess with boot(loader) stuff unless you *really* mean it! )
Note#1: using Triangle Away may unmount your SD card. Reboot or manually remount it from Android settings.
Note#2: on new devices like the SGS3/SGNote2/SGNote10.1, status can only be reset on some firmwares - they must be stock firmwares!
I am not clear on how to interpret the warning, other than it makes me a bit nervous about bricking the device. I did a quick search of USB JIG for the SGN10 and I didn't see anything come up in the first few Google pages. One placed discussed making your own JIG which involves soldering. Not my thing!
So my question is has any other GT-N8013 user performed the step of selecting the reboot into the special mode, and if so, what happens after that? More importantly, did anyone experience having their SGN10/GT-N8013 bricked from this step?
Again, sorry if this is basic to most, but it is new to me, and we all have to start somewhere.
Thanks,
'Bean
bookbean said:
I went ahead and downloaded Triangle Away. When I start in download mode, I receive the warning along with the big yellow triangle. After pressing volume up to continue, it goes into Odin Mode (in Red) and shows that the Custom Binary Download: Yes (5 counts), followed by Current Binary: Custom and then System Status: Custom. To get out of that screen, I have just held down the power button to turn off the device.
When I start up the Triangle Away app, the current status (under Flash Counter) says that Status cannot be determined, need to reboot into a special bootmode - tap "Reset flash counter".
In the Overview section on Play Store, it shows this warning:
On a number of devices, TriangleAway can work, but your firmware may not be supported directly. In that case, the app will tell you it needs to reboot into a special boot mode, which will be happen if you select "Reset flash counter". The device will reboot into a special mode which will allow you to review the current status and reset the binary and flash counter values (or abort and do nothing). On some devices this will actually trigger the counter to 1 if its 0 - so if you're "just checking", do that in download mode!
!!! THIS IS A DANGEROUS OPERATION AND COULD POTENTIALLY BRICK YOUR DEVICE. PROCEED AT YOUR OWN RISK. A USB JIG IS PREFERRED IF YOU HAVE A WORKING ONE !!! ( and by brick I mean brick - only a board replacement or a JTAG unit will be able to save you, don't mess with boot(loader) stuff unless you *really* mean it! )
Note#1: using Triangle Away may unmount your SD card. Reboot or manually remount it from Android settings.
Note#2: on new devices like the SGS3/SGNote2/SGNote10.1, status can only be reset on some firmwares - they must be stock firmwares!
I am not clear on how to interpret the warning, other than it makes me a bit nervous about bricking the device. I did a quick search of USB JIG for the SGN10 and I didn't see anything come up in the first few Google pages. One placed discussed making your own JIG which involves soldering. Not my thing!
So my question is has any other GT-N8013 user performed the step of selecting the reboot into the special mode, and if so, what happens after that? More importantly, did anyone experience having their SGN10/GT-N8013 bricked from this step?
Again, sorry if this is basic to most, but it is new to me, and we all have to start somewhere.
Thanks,
'Bean
Click to expand...
Click to collapse
I think there's no USB jig to Note 10.1. I have used TriangleAway for my I9100 few times and N8010 (same that your device but european) once and both worked fine, no bricks. After you boot in "special mode", you'll be shown your counter, and it will confirm are you sure, you can cancel it there if you want and it does nothing to your device. Just check that your download mode's counters match TriangleAway's counters.
After Special Mode
niko0o said:
I think there's no USB jig to Note 10.1. I have used TriangleAway for my I9100 few times and N8010 (same that your device but european) once and both worked fine, no bricks. After you boot in "special mode", you'll be shown your counter, and it will confirm are you sure, you can cancel it there if you want and it does nothing to your device. Just check that your download mode's counters match TriangleAway's counters.
Click to expand...
Click to collapse
Thanks for giving me the courage to give it a shot, which I have now done. The counter in the special mode matched what Odin was showing, so I went ahead with it.
Now when I start up holding down the volume down button along with the power button, I am still getting the Triangle. However this time, below the Odin Mode (written in red), it shows Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
I take it that because there is still root on the device, that the System Status will continue to show "Custom" and I will continue to have the triangle? I thought that the idea was to get everything to "look" official stock. Please let me know if I am missing anything else.
Thanks,
'Bean
I Got All Things Official By Flashing A Stock Rom Through Mobile ODIN Onto The Note At This Point BUT You Will Need To Factory Reset. You Will Also Go Back To Stock Recovery. If You Want All These Things To Display Official Status.
I Haven't Got It Back To Not Show Official While Running A Custom Rom As Current Binary Changes To Custom When You Install Cwm Or System Status Does.
Theres Also A Status In Settings> About> Status That Will Also Say Custom Too. Shouldnt Be A Problem Unless You Try To Use The Allshare Cast Hub...
ultramag69 said:
I Got All Things Official By Flashing A Stock Rom Through Mobile ODIN Onto The Note At This Point BUT You Will Need To Factory Reset. You Will Also Go Back To Stock Recovery. If You Want All These Things To Display Official Status.
I Haven't Got It Back To Not Show Official While Running A Custom Rom As Current Binary Changes To Custom When You Install Cwm Or System Status Does.
Theres Also A Status In Settings> About> Status That Will Also Say Custom Too. Shouldnt Be A Problem Unless You Try To Use The Allshare Cast Hub...
Click to expand...
Click to collapse
My understanding is that Allshare is useful only if you have other Samsung devices. So first, please advise if my understanding on that is correct. Assuming that this is the case, then I suppose that I do not need to immediately concern myself with getting all three settings to be "official", as I am in no immediate need (hopefully) to go back to full factory settings with official software since I do not own any other Samsung Android device. I am only beginning the root journey. I guess that it is good to have the bread crumbs to find my way back home at first, but I also want to be adventurous and try out some of these really interesting things which root is supposed to lead me to.
Is it fair to say then, that the counter thing shouldn't be a concern for now?
bookbean said:
My understanding is that Allshare is useful only if you have other Samsung devices. So first, please advise if my understanding on that is correct. Assuming that this is the case, then I suppose that I do not need to immediately concern myself with getting all three settings to be "official", as I am in no immediate need (hopefully) to go back to full factory settings with official software since I do not own any other Samsung Android device. I am only beginning the root journey. I guess that it is good to have the bread crumbs to find my way back home at first, but I also want to be adventurous and try out some of these really interesting things which root is supposed to lead me to.
Is it fair to say then, that the counter thing shouldn't be a concern for now?
Click to expand...
Click to collapse
To zero that last you need to flash stock firmware with Odin, but thats not necessary except if you need to return your Note to warranty or something.
bookbean said:
My understanding is that Allshare is useful only if you have other Samsung devices.
Click to expand...
Click to collapse
I own an allsharecast hub and I use it at school to lecture.I project the tablet screen to an hdmi LED TV which is not a Samsung brand.So no;you have a misunderstanding at this.And since I have a GT-N8005 device and triangle away doesn't support this device I can't use the 'reset flash counter' method:crying:
Allshare
ordeniz said:
I own an allsharecast hub and I use it at school to lecture.I project the tablet screen to an hdmi LED TV which is not a Samsung brand.So no;you have a misunderstanding at this.And since I have a GT-N8005 device and triangle away doesn't support this device I can't use the 'reset flash counter' method:crying:
Click to expand...
Click to collapse
Thank you for clarifying the allsharecast hub use and I am sorry that you cannot change your flash counter. Is it possible for the author of the program to modify it for your device? Perhaps you can contact them about it.
bookbean said:
Thank you for clarifying the allsharecast hub use and I am sorry that you cannot change your flash counter. Is it possible for the author of the program to modify it for your device? Perhaps you can contact them about it.
Click to expand...
Click to collapse
Thanks.I posted a comment on google play store,and I will contact them soon.

How to root your samsung galaxy s3 (easily)

**** UPDATED 7-24-13 *****
Please read the tutorial now as I have added a new section on how to unlock the bootloader for your Verizon Samsung Galaxy S3. If you are not using a verizon SGS3
specifically model SCH-i535 then you do not have to worry about unlocking your bootloader as it comes unlocked by default. If you are using a verizon samsung galaxy s3 model sch-i535 and you do not fully unlock your bootloader you could run into problems when using certain root apps such as "mobile odin pro" or you could run into big problems when trying to flash custom roms such as cyanogenmod roms.
In this update I am adding one final step at the end of the root process to fully unlock the boot loader for the verizon samsung galaxy s3. There will be two ways to unlock the bootloader. One way will be to flash a final bootchain file with Odin, and the other will be to use an app to unlock the bootloader. Depending on what version of android you are using and your phones baseband version you will either need to use odin or you could use the application for any android version such as 4.1.1 or 4.1.2 and you can use the application for any baseband version your phone might be. I will leave the choice up to you, but I will show how to do it both ways.
Samsung users, don't forget if you plan on flashing a custom rom that with Samsung phones you could get the ugly yellow triangle warning. To get rid of this yellow triangle you can either go to google play store and get "yellow triangle away" app or go to this forum on this great xda developers site: http://forum.xda-developers.com/showthread.php?t=1494114
**NOTE** for those of you who would like to see a video of how to root your phone using these exact steps you can go to here: http://www.youtube.com/watch?v=K4b9hcWHrW8&feature=share&list=FL8Y3FM4mtznp0GQbwkkwaSg
A member on this thread gave me that link and it is a video by phone rebel and show you how to root your verizon SGS3 using the same steps i have outlined in this tutorial. Thank you so much for providing that link to my attention, I am sure it will help many users here!
Hello everyone,
Well this is one of my first tutorials for this forum on how to root your Verizon Samsung Galaxy S3.
I just recently got my Verizon Samsung Galaxy S3 and all of the tutorials I found were quite complicated and not very detailed so I thought that
I would write this tutorial and maybe it might help others out there....
Since the Galaxy S4 is getting ready to come out, the price has dropped considerably for the S3 and i believe more and more people will be getting this phone and wanting to root it.
Oh, and if you want an alternative guide you can use this very excellent tutorial from another post on this amazing forum:
http://forum.xda-developers.com/showthread.php?t=2046439
Here is the specs for the phone I am using and the step by step process I used to root it.
Verizon Samsung Galaxy SIII model I535 running Android 4.1.2
Okay step 1 you are going to need some files...
First thing you are going to need is the Samsung Drivers so you can connect your phone to your computer and your computer can recognize it.
All of the files you are going to need I am just going to reference the link from the other tutorial that I posted above, no sense in redoing work
that has already been done especially if it has been done well!
1. You can get the samsung driver files here: http://forum.xda-developers.com/showthread.php?t=2046439
click on the link that says samsung drivers
2. You are going to need Odin you can get it from the same link, click on the Odin Link
3. You are going to need the VRALEC BOOTCHAIN you can get it from the link I posted in step 1 make sure you get this file it is very
important.
Since I am using a Verizon Samsung Galaxy S3 the bootloader comes by default locked so we need this file to unlock the bootloader
so we can root the phone. If we were using any other phone besides Verizon we would not have to worry about this but since I have
Verizon I have to do this. IMPORTANT: if you are not using a VERIZON PHONE DO NOT download this file or use it in the step
process you do not need it.
4. Next you are going to need the exploit so that you can root your phone and you can grab that from a different website, here is the address:
http://autoroot.chainfire.eu/
This is the CF-AUTOROOT file and this is what roots your phone. If you have the same phone as me scroll down to the SCH-I535 link and
download that file.
Okay now that we have all of that downloaded lets get things moving...
First thing we are going to need to do is install the Samsung USB drivers, so do that.
After the drivers are installed plug in your phone and make sure that it connects to your computer correctly, after it connects disconnect
your phone from your computer.
Next thing we are going to need to do is extract the ODIN zip file and install the Odin executable.
Now we need to get to the critical stuff...
Step 1. Make sure that [USB Debugging] is enabled in your phone, if it is not go to Settings -> Developer Options and enable it.
Step 2. Put your phone in DOWNLOAD Mode. You do that by pressing Volume Down + Home + Power button and hold it down till you see
a warning screen. When you see the warning screen hit Volume Up to allow Download mode.
Step 3. Now that your phone is in Download Mode you are going to connect your phone to your computer with ODIN RUNNING if
everything connects correctly you will see ODIN highlight yellow (older versions of ODIN) or highlight blue (newer ODIN versions)
Step 4. Now this is where previous tutorials kind of messed up in my opinion (just my opinion). Now that your phone is in download mode
you need to only have the "auto boot" option selected in ODIN and click on the bootloader button and select the VRALEC file
you downloaded earlier. Every tutorial i read said to use this file with the PDA button/option but you need to use it with the bootloader
button/option in ODIN. Now that you have the VRALEC file selected under bootloader in ODIN select START. This will reboot your
phone and if everything goes correctly your phone's bootloader will be unlocked.
After reboot make sure to disconnect your phone from your computer.
Step 5. After your phone reboots from step 4 turn off your phone and then boot it back into DOWNLOAD mode. Vol Down + Home + Power
Step 6. Now that your phone is in Download Mode again (Reconnect your phone to your computer) and make sure ODIN is still running
Step 7. With your phone connected go to the PDA option/button and when you select it choose the CF-AUTOROOT file you downloaded earlier
Step 8. With your PDA option selected hit start. When this happens your phone will reboot and your will see a CUSTOM lock icon on your
screen don't worry it is okay. Now you will see some new text on your phone and if everything is working you will see things like
"Android is UPDATING"
Your phone is now rooted! but you are not done...
This is where all of the other tutorials I found also fell short...
Your phone is rooted but it will not work correctly without SuperSU
Step 9. Go to the Google Play Store and Download SuperSU. When the download is complete run SuperSU and now your phone is fully
rooted. You can test it by downloading Android Terminal and running the terminal and typing "su" or by downloading a root required
app Titanium Backup.
*****UPDATED STEP*****
IMPORTANT NOTE: i want to point that this step is completely optional. You do not have to unlock your bootloader but i would recommend it. If you just want to use a stock rom and have your phone rooted then you can ignore this last step. But...if you want to flash custom rom's or do any kind of serious customize your phone, then you will need to have your phones bootloader unlocked. Plus with the application I am going to show you further down this tutorial, it is so easy to unlock your bootloader, you might as well go for it.
Step 10. Okay now from the link that I gave you above: http://forum.xda-developers.com/showthread.php?t=2046439 you are going to need to download another bootchain file to fully unlock your verizon samsung galaxy s3 model sch-i535 phone.Go into your phone and under settings go into "about phone' and look at the section "baseband version". Now depending on what version of android you are using will determine your baseband version. On my Verizon SGS3 running 4.1.2 my baseband version is I535VRBMB1 the important part is -> "VRBMB1" now go to site i provided in this step and download the bootchain for your specific phone.
Since my phones baseband version is "VRBMB1" i will download that bootchain file obviously. VRBMB1 is for android 4.1.2
The other boothchain files are "VRBLK3" for android 4.1.1 and "VRBMD3" for android 4.1.2
Now take that bootchain file that you downloaded and load up Odin again. Connect your phone to your computer (MAKE SURE YOUR PHONE IS IN DOWNLOAD MODE -> VOL DOWN + HOME + POWER) and wait for Odin show a connection. Odin will show a blue light on newer Odin versions and a yellow light on older Odin versions.
When the connection is made hit the "bootloader" button and select the proper bootchain file for your specific phone. Before you hit start make sure that only "Auto Reboot" is selected on the left hand side.
Now go ahead and hit start and if all goes well your phones bootloader should be unlocked. You can tell that your phones bootloader is unlocked two ways.
One, when your phone reboots the Samsung Logo in white bold/block writing will disappear within 1-2 seconds. It will go by very fast.
Two, the custom lock icon that showed up after you ran the CF-AUTOROOT exploit will now disappear, if for any reason if you still see this logo then your phones bootloader is still locked and you can either try to flash the bootchain file again or use the application I am about to tell you about.
For my phone flashing this bootchain file worked fine, but for my brother's phone he has a verizon samsung galaxy s3 model sch-i535 this did not work and I had to use an application to unlock his bootloader.
****UPDATE UNLOCKING THE BOOTLOADER WITH EZ-UNLOCK*****
Okay so my brother who has a verizon samsung galaxy s3 model sch-i535 asked me to root his phone just the other day. I rooted his phone following all the same steps I have written above with no problems. His phone rooted perfectly, however his bootloader would not unlock. I believe that his bootloader would not unlock because he had an updated version. While his android version was the same as mine 4.1.2 he had a different baseband version.
His baseband version was "I535VRBMF1" the important part -> "VRBMF1"
Now i have been told that you can use the bootchain file VRBMB1 to unlock the bootloader for verizon SGS3 running android 4.1.2 baseband version "VRBMF1" but when i tried it, the bootloader staid locked. So i had to use an application to unlock his bootloader.
The application i used was "EZ-Unlock" which you can get here: http://rootzwiki.com/topic/32456-app-920-ez-unlock-14-easiest-way-to-unlock-your-bootloader/
Now this application is SO EASY to use it is amazing. Just download the file, the author recommend version 1.2 as the most stable and that is version i used. To download this file make sure you have the option "Unknown Sources" check in your Settings -> Security menu.
Okay to unlock your bootloader with EZ-Unlock follow these easy steps:
Step 10A. Download EZ-Unlock version 1.2 from the link above.
Step 10B. Install the application and open it.
Step 10C. Once open click on the giant "Unlock" button. If all goes well you will hear "That was easy" from the application.
Once you have hit the unlock button on EZ-Unlock reboot your phone to see if the Samsung in bold/block white letters disappears within 1-2 seconds, and make sure the custom lock icon has disappeared.
Now the application EZ-Unlock is designed specifically for verizon samsung galaxy s3 phones, it does not matter what baseband version you use or android version you use. So this is a very appealing and easy way to unlock your bootloader. If you don't feel like flashing a bootchain file with Odin or if you are not sure what bootchain file you should use then using this application. NOTE: you do need root access to run this application.
And that is it! Your phones bootloader should be unlocked either with Odin or EZ-Unlock the choice is all up to you!
***LAST THOUGHT ON INSTALLING CUSTOM RECOVERY***
This rooting method does not install and kind of custom recovery manager on to your phone. If you want to install a custom recovery manager such as "ClockworkMod Recovery" you can do that very easily once your phone is rooted. Once your phone is rooted go to the google play store and download "Rom Manager". Once Rom Manager is installed open it up and give it root access with SuperSU. Once that is done go into the option to flash a recovery manager and follow the steps and the application Rom Manager will take care of that for you!.
Congrats on rooting your phone! I hope this tutorial has helped you and I want to thank all of the system administrators of this forum and all of
the great guys and gals that contribute to this place. You guys/gals are what makes the open source community great!
I thank you all...
Hope it helped!
-droidshadow
Thanks might have to do this on my wife's phone
Sent from my SCH-I535 using xda premium
kgirlx said:
Thanks might have to do this on my wife's phone
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I think that the easiest way to root any Samsung Devices - Samsung Toolkit
I'm not having any luck with this. I've followed the instructions step by step and when I flash a custom ROM, I get the dreaded yellow triangle of death apon rebooting. There were some other files mentioned in the links. Do I need to unzip those at some point?
sorry i have been away
Okay i am so sorry for the late response I have been away and very busy. This tutorial is how to root your samsung galaxy s3 (verizon) model sch-i535 because you need to unlock the bootloader for that specific model.
Now you mentioned that when you try to flash a custom rom you get a yellow triangle of death....
Have you unlocked the bootloader?
Is your phone already rooted? Are you trying to flash a custom rom or are you still trying to root your phone?
I hope you have already resolved your issue but if you haven't I would be more than happy to try and help you out.
How is it any easier then the other guides for jelly bean? Here you added the cf-auto root which is one extra step . Also with auto root there is a possibility of bricking the phone since it supports a lot of devices and as you are well aware that a lot of people new to flashing tend to flash the wrong files even if you give them a step by step guide. While this guide is helpful and does work it isn't as idiot proof as the other guide you linked on your post.
This does not work on my phone. When I try this, the phone boots normally. I have tried this several times and I get the same results. I can however hold the vol up button+the home button+the power button and get to stock recovery mode. I had an older S3 that this did work on but not my new one. I have read several threads here for rooting the S3 i535 with Jelly Bean 4.1.2 and this is supposedly the method but it will not work on my phone. What am I doing wrong? What am I missing? Please advise!
benbrown said:
This does not work on my phone. When I try this, the phone boots normally. I have tried this several times and I get the same results. I can however hold the vol up button+the home button+the power button and get to stock recovery mode. I had an older S3 that this did work on but not my new one. I have read several threads here for rooting the S3 i535 with Jelly Bean 4.1.2 and this is supposedly the method but it will not work on my phone. What am I doing wrong? What am I missing? Please advise!
Click to expand...
Click to collapse
This guide is different in that it uses cf-auto root so I highly doubt you even tried this method.
I finally did get it. All rooted now.
Sent from my SCH-I535 using Tapatalk 2
The easiest way to root is odin'ing Mr. Robinson's root injected tar and the unlock the bootloader. Done
Sent from my MIUI powered S3 thanks to StrumerJohn
maybe i should have been more clear...
faehsemc said:
The easiest way to root is odin'ing Mr. Robinson's root injected tar and the unlock the bootloader. Done
Sent from my MIUI powered S3 thanks to StrumerJohn
Click to expand...
Click to collapse
Hey everyone,
Well i guess everyone has their own favorite way of rooting their phone/device. I did not mean for this small tutorial to be the *absolute easiest* way to root a verizon samsung galaxy s3 model i535 i just thought that I could do people a favor by elaborating a bit more on certain steps to make the rooting process a bit easier.
On certain tutorials i found I didn't seem them clearly state that the VRLAC BOOTCHAIN file needed to go in the boot loader section of ODIN to unlock the phone's bootloader.
On other tutorials that show you how to use CF-AUTOROOT I didn't see any that told you that you needed to install SUPERSU from the google play store manually in order to fully utilize your phones rooted status.
Yes there are other ways too root a SGS3, the Samsung Toolkit is a good option, or using a custom root such as Cyanogenmod is another great option as well...
All of those options you will have to research for yourself and ultimately decide for yourself.
However, if you want to keep your phone's stock ROM and you just want to root your Verizon SGS3 model SCH-I535 then I like using ODIN + CF-AUTOROOT exploit.
All i wanted to do was assist and do my part on this great forum which has helped me so much in the past...
I hope it helped someone...
Thanks for everyone who replied and shared your thoughts on other rooting options.
-DroidShadow
droidshadow said:
Hello everyone,
Well this is one of my first tutorials for this forum on how to root your Verizon Samsung Galaxy S3.
I just recently got my Verizon Samsung Galaxy S3 and all of the tutorials I found were quite complicated and not very detailed so I thought that
I would write this tutorial and maybe it might help others out there....
Since the Galaxy S4 is getting ready to come out, the price has dropped considerably for the S3 and i believe more and more people will be getting this phone and wanting to root it.
Oh, and if you want an alternative guide you can use this very excellent tutorial from another post on this amazing forum:
http://forum.xda-developers.com/showthread.php?t=2046439
Here is the specs for the phone I am using and the step by step process I used to root it.
Verizon Samsung Galaxy SIII model I535 running Android 4.1.2
Okay step 1 you are going to need some files...
First thing you are going to need is the Samsung Drivers so you can connect your phone to your computer and your computer can recognize it.
All of the files you are going to need I am just going to reference the link from the other tutorial that I posted above, no sense in redoing work
that has already been done especially if it has been done well!
1. You can get the samsung driver files here: http://forum.xda-developers.com/showthread.php?t=2046439
click on the link that says samsung drivers
2. You are going to need Odin you can get it from the same link, click on the Odin Link
3. You are going to need the VRALEC BOOTCHAIN you can get it from the link I posted in step 1 make sure you get this file it is very
important.
Since I am using a Verizon Samsung Galaxy S3 the bootloader comes by default locked so we need this file to unlock the bootloader
so we can root the phone. If we were using any other phone besides Verizon we would not have to worry about this but since I have
Verizon I have to do this. IMPORTANT: if you are not using a VERIZON PHONE DO NOT download this file or use it in the step
process you do not need it.
4. Next you are going to need the exploit so that you can root your phone and you can grab that from a different website, here is the address:
http://autoroot.chainfire.eu/
This is the CF-AUTOROOT file and this is what roots your phone. If you have the same phone as me scroll down to the SCH-I535 link and
download that file.
Okay now that we have all of that downloaded lets get things moving...
First thing we are going to need to do is install the Samsung USB drivers, so do that.
After the drivers are installed plug in your phone and make sure that it connects to your computer correctly, after it connects disconnect
your phone from your computer.
Next thing we are going to need to do is extract the ODIN zip file and install the Odin executable.
Now we need to get to the critical stuff...
Step 1. Make sure that [USB Debugging] is enabled in your phone, if it is not go to Settings -> Developer Options and enable it.
Step 2. Put your phone in DOWNLOAD Mode. You do that by pressing Volume Down + Home + Power button and hold it down till you see
a warning screen. When you see the warning screen hit Volume Up to allow Download mode.
Step 3. Now that your phone is in Download Mode you are going to connect your phone to your computer with ODIN RUNNING if
everything connects correctly you will see ODIN highlight yellow (older versions of ODIN) or highlight blue (newer ODIN versions)
Step 4. Now this is where previous tutorials kind of messed up in my opinion (just my opinion). Now that your phone is in download mode
you need to only have the "auto boot" option selected in ODIN and click on the bootloader button and select the VRALEC file
you downloaded earlier. Every tutorial i read said to use this file with the PDA button/option but you need to use it with the bootloader
button/option in ODIN. Now that you have the VRALEC file selected under bootloader in ODIN select START. This will reboot your
phone and if everything goes correctly your phone's bootloader will be unlocked.
After reboot make sure to disconnect your phone from your computer.
Step 5. After your phone reboots from step 4 turn off your phone and then boot it back into DOWNLOAD mode. Vol Down + Home + Power
Step 6. Now that your phone is in Download Mode again (Reconnect your phone to your computer) and make sure ODIN is still running
Step 7. With your phone connected go to the PDA option/button and when you select it choose the CF-AUTOROOT file you downloaded earlier
Step 8. With your PDA option selected hit start. When this happens your phone will reboot and your will see a CUSTOM lock icon on your
screen don't worry it is okay. Now you will see some new text on your phone and if everything is working you will see things like
"Android is UPDATING"
Your phone is now rooted! but you are not done...
This is where all of the other tutorials I found also fell short...
Your phone is rooted but it will not work correctly without SuperSU
Step 9. Go to the Google Play Store and Download SuperSU. When the download is complete run SuperSU and now your phone is fully
rooted. You can test it by downloading Android Terminal and running the terminal and typing "su" or by downloading a root required
app Titanium Backup.
Congrats on rooting your phone! I hope this tutorial has helped you and I want to thank all of the system administrators of this forum and all of
the great guys and gals that contribute to this place. You guys/gals are what makes the open source community great!
I thank you all...
Hope it helped!
-droidshadow
Click to expand...
Click to collapse
Followed all instructions, and the phone never rebooted. Not its not turning on. Tried vol up+home+power, vol down+home+power, battery pull, holding down power for 2 minutes. . .
The only thing I can think of is that I possibly unplugged the phone before the reboot after Step 4, just as soon as the phone shut down and before the actual reboot.
Anything you can help me with? I''m going crazy here.
Thanks
Rooting and installation on S3 GTI9300
I rooted my S3 2 days back (i think so), now i want to install a custom rom (mostly xperia Z) and I am new to this world, so can you plz help me??
I followed your instructions there was no such msg as Andriod is Updating, and how should i do install the rom??
I wish to install from this http://forum.xda-developers.com/showthread.php?t=2174644
droidshadow said:
Hello everyone,
Well this is one of my first tutorials for this forum on how to root your Verizon Samsung Galaxy S3.
I just recently got my Verizon Samsung Galaxy S3 and all of the tutorials I found were quite complicated and not very detailed so I thought that
I would write this tutorial and maybe it might help others out there....
Since the Galaxy S4 is getting ready to come out, the price has dropped considerably for the S3 and i believe more and more people will be getting this phone and wanting to root it.
Oh, and if you want an alternative guide you can use this very excellent tutorial from another post on this amazing forum:
http://forum.xda-developers.com/showthread.php?t=2046439
Here is the specs for the phone I am using and the step by step process I used to root it.
Verizon Samsung Galaxy SIII model I535 running Android 4.1.2
Okay step 1 you are going to need some files...
First thing you are going to need is the Samsung Drivers so you can connect your phone to your computer and your computer can recognize it.
All of the files you are going to need I am just going to reference the link from the other tutorial that I posted above, no sense in redoing work
that has already been done especially if it has been done well!
1. You can get the samsung driver files here: http://forum.xda-developers.com/showthread.php?t=2046439
click on the link that says samsung drivers
2. You are going to need Odin you can get it from the same link, click on the Odin Link
3. You are going to need the VRALEC BOOTCHAIN you can get it from the link I posted in step 1 make sure you get this file it is very
important.
Since I am using a Verizon Samsung Galaxy S3 the bootloader comes by default locked so we need this file to unlock the bootloader
so we can root the phone. If we were using any other phone besides Verizon we would not have to worry about this but since I have
Verizon I have to do this. IMPORTANT: if you are not using a VERIZON PHONE DO NOT download this file or use it in the step
process you do not need it.
4. Next you are going to need the exploit so that you can root your phone and you can grab that from a different website, here is the address:
http://autoroot.chainfire.eu/
This is the CF-AUTOROOT file and this is what roots your phone. If you have the same phone as me scroll down to the SCH-I535 link and
download that file.
Okay now that we have all of that downloaded lets get things moving...
First thing we are going to need to do is install the Samsung USB drivers, so do that.
After the drivers are installed plug in your phone and make sure that it connects to your computer correctly, after it connects disconnect
your phone from your computer.
Next thing we are going to need to do is extract the ODIN zip file and install the Odin executable.
Now we need to get to the critical stuff...
Step 1. Make sure that [USB Debugging] is enabled in your phone, if it is not go to Settings -> Developer Options and enable it.
Step 2. Put your phone in DOWNLOAD Mode. You do that by pressing Volume Down + Home + Power button and hold it down till you see
a warning screen. When you see the warning screen hit Volume Up to allow Download mode.
Step 3. Now that your phone is in Download Mode you are going to connect your phone to your computer with ODIN RUNNING if
everything connects correctly you will see ODIN highlight yellow (older versions of ODIN) or highlight blue (newer ODIN versions)
Step 4. Now this is where previous tutorials kind of messed up in my opinion (just my opinion). Now that your phone is in download mode
you need to only have the "auto boot" option selected in ODIN and click on the bootloader button and select the VRALEC file
you downloaded earlier. Every tutorial i read said to use this file with the PDA button/option but you need to use it with the bootloader
button/option in ODIN. Now that you have the VRALEC file selected under bootloader in ODIN select START. This will reboot your
phone and if everything goes correctly your phone's bootloader will be unlocked.
After reboot make sure to disconnect your phone from your computer.
Step 5. After your phone reboots from step 4 turn off your phone and then boot it back into DOWNLOAD mode. Vol Down + Home + Power
Step 6. Now that your phone is in Download Mode again (Reconnect your phone to your computer) and make sure ODIN is still running
Step 7. With your phone connected go to the PDA option/button and when you select it choose the CF-AUTOROOT file you downloaded earlier
Step 8. With your PDA option selected hit start. When this happens your phone will reboot and your will see a CUSTOM lock icon on your
screen don't worry it is okay. Now you will see some new text on your phone and if everything is working you will see things like
"Android is UPDATING"
Your phone is now rooted! but you are not done...
This is where all of the other tutorials I found also fell short...
Your phone is rooted but it will not work correctly without SuperSU
Step 9. Go to the Google Play Store and Download SuperSU. When the download is complete run SuperSU and now your phone is fully
rooted. You can test it by downloading Android Terminal and running the terminal and typing "su" or by downloading a root required
app Titanium Backup.
Congrats on rooting your phone! I hope this tutorial has helped you and I want to thank all of the system administrators of this forum and all of
the great guys and gals that contribute to this place. You guys/gals are what makes the open source community great!
I thank you all...
Hope it helped!
-droidshadow
Click to expand...
Click to collapse
I ran ODIN with the bootchain, and that worked, but when i tried running it with PDA set to CF-autoroot file, I get SECURE CHECK FAIL
hello everyone
bgenchel said:
I ran ODIN with the bootchain, and that worked, but when i tried running it with PDA set to CF-autoroot file, I get SECURE CHECK FAIL
Click to expand...
Click to collapse
bgenchel: what kind of phone do you have? Are you 100% sure that you downloaded the correct CF-autoroot file for your specific phone model?
mlev1987 said:
Followed all instructions, and the phone never rebooted. Not its not turning on. Tried vol up+home+power, vol down+home+power, battery pull, holding down power for 2 minutes. . .
The only thing I can think of is that I possibly unplugged the phone before the reboot after Step 4, just as soon as the phone shut down and before the actual reboot.
Anything you can help me with? I''m going crazy here.
Thanks
Click to expand...
Click to collapse
Did you run the Odin with the VRLAC bootchain file then you unplugged your phone before a full restart could take place? This is a very sensitive issue because that bootchain file unlocks your bootloader on your verizon phone. Your bootloader is everything to your phone. It controls how your phone starts and your phone can not work correctly if your bootloader became compromised in any way. I really hope you figured it out, and if you didn't maybe you could call your insurance company (if you have one) and get a new phone. If you are worried about rooting your phone again you could look on craigslist, there are always people/professionals willing to do it for very reasonable prices $10-$20. Again i really hope you figured this out and if you give me some more details maybe we can figure this out together.
Phone Rebel Method
This is the same method that Phone Rebel has on his YouTube channel for rooting d2vzw. This tutorial is missing one step that Phone Rebel covers, after running CF Auto Root, he flashes the corresponding bootchain file that goes with whatever firmware your phone is running. When I rooted, I was running VRBMB1, so I flashed that boot chain following the other two odin flashes. http://www.youtube.com/watch?v=K4b9hcWHrW8&feature=share&list=FL8Y3FM4mtznp0GQbwkkwaSg
What I've learned is that CF Auto Root does not unlock the bootloader and trying to flash a custom ROM with result in the dreaded triangle message every time. I was given this method: http://droidviews.com/2013/root-and...erizon-galaxy-s3-sch-i535-android-4-1-14-1-2/
to try instead. In this method you flash the VRALEC, then CWM recovery, then you can flash SuperSU with an unlocked bootloader via CWM, then flash the final bootchain file depending on the firmware you're running. Method 3 contains the casual root tool, but I've seen mixed reviews for that one.
At the suggestion of someone on the Google+ community for the SGS3, I"m gonna attempt to root VRBMF1 (JB 4.1.2 w/multiwindow) via method 1 and then flash the VRBMB1 bootchain for the previous version and see what happens.
UPDATE
ohemetophobia said:
This is the same method that Phone Rebel has on his YouTube channel for rooting d2vzw. This tutorial is missing one step that Phone Rebel covers, after running CF Auto Root, he flashes the corresponding bootchain file that goes with whatever firmware your phone is running. When I rooted, I was running VRBMB1, so I flashed that boot chain following the other two odin flashes. http://www.youtube.com/watch?v=K4b9hcWHrW8&feature=share&list=FL8Y3FM4mtznp0GQbwkkwaSg
What I've learned is that CF Auto Root does not unlock the bootloader and trying to flash a custom ROM with result in the dreaded triangle message every time. I was given this method: http://droidviews.com/2013/root-and...erizon-galaxy-s3-sch-i535-android-4-1-14-1-2/
to try instead. In this method you flash the VRALEC, then CWM recovery, then you can flash SuperSU with an unlocked bootloader via CWM, then flash the final bootchain file depending on the firmware you're running. Method 3 contains the casual root tool, but I've seen mixed reviews for that one.
At the suggestion of someone on the Google+ community for the SGS3, I"m gonna attempt to root VRBMF1 (JB 4.1.2 w/multiwindow) via method 1 and then flash the VRBMB1 bootchain for the previous version and see what happens.
Click to expand...
Click to collapse
You can use method 1 outlined in the droidviews link i posted yesterday to root the phone and when you get to the point where you're flashing the second bootchain you can flash VRBMB1 instead of needing VRBMF1 and it will work just fine! I also believe this method will truly unlock the bootloader for flashing custom roms, to avoid the yellow triangle of frustration, but I have no oversight on this as it was not my plan to do so.
VRBMF1??
I must admit that I am new to rooting.
I just bought a new S3 i535 with 4.1.2 and would like to root it. In the link provided there are files to download. One of these files are the bootchain... When I look in my settings, I see VRBMF1 and in the link provided I see.............
For VRBLK3 (Jelly Bean 4.1.1) Link
MD5: E3A1CB07DE214ED8081ED9D42C9BAF4A
For VRBMB1 (Jelly Bean 4.1.2) Link
MD5: 8C3DA18BD5DEF7E38E03DD147A0E10A1
For VRBMD3 (Jelly Bean 4.1.2) Link
MD5: 9CB65EAE8784807349EC3D4FF3A0AAEF
I am confused on what to do. I would imagine that this instructional post was created before I got my phone (07/13/2013) and thus is the reason why it might be missing from the instructions. Please advise me.
BKSinAZ said:
I must admit that I am new to rooting.
I just bought a new S3 i535 with 4.1.2 and would like to root it. In the link provided there are files to download. One of these files are the bootchain... When I look in my settings, I see VRBMF1 and in the link provided I see.............
For VRBLK3 (Jelly Bean 4.1.1) Link
MD5: E3A1CB07DE214ED8081ED9D42C9BAF4A
For VRBMB1 (Jelly Bean 4.1.2) Link
MD5: 8C3DA18BD5DEF7E38E03DD147A0E10A1
For VRBMD3 (Jelly Bean 4.1.2) Link
MD5: 9CB65EAE8784807349EC3D4FF3A0AAEF
I am confused on what to do. I would imagine that this instructional post was created before I got my phone (07/13/2013) and thus is the reason why it might be missing from the instructions. Please advise me.
Click to expand...
Click to collapse
Yes, the instructional post was created prior to you getting an S3. So, if you got into Settings> About Phone and look at your baseband version you'll probably see I535VRBMF1 and you'll probably see it again in another field just below it. This indicates that you're running the VRBMF1 firmware. That is JB 4.1.2 with multi-window. When using the root process in the droidviews article it outlines flashing VRALEC, then CWM touch, then using CWM to flash the supersu file, then flashing either VRBLK3, VRBMB1, or VRBMD3. Since none of those bootchain files match your firmware and there is no VRBMF1 bootchain on the forums, I flashed VRBMB1 since it was the the bootchain from the previous firmware. It worked. I successfully achieved root with no problems. Hope this helps.

Safestrap for galaxy s5 active g870w telus

G870W Recovery
Hello there!
I've successfully rooted my (Telus) S5 Active / G870WVLU1ANH3 / kltevlactive using CF Auto Root, blowing my knox and all that, works great.
However, I'm now trying to flash either TWRP or CWM Philz for klte (which may have not been to smart come to think about that, but I recall reading it should work just fine) using Odin, and I can't get into recovery. Whenever I attempt to boot into recovery, I end up with "cannot do normal boot".
I recall reading a SafeStrap for G900 works for the G870, but I can't find the thread again, and don't want to just try and see what happens.
I've also tried flashing a recovery using either TWRP app and RomManager, I have yet to try Rashr, but since all the recoveries I've found are for klte, instead of kltevlactive, I'm slightly worried.
I'm not all that new to rooting, but I'm quite new (and upset ) at the Samsung realm, any chance you guys would know what could get me going with a custom recovery?
I also have a Xposed Framework installed, I read it could cause issues with SafeStrap, but I don't suppose it would affect flashing a rom from Odin/whatever else?
My SELinux on the phone claims to be "Enforcing", if that matters, perhaps.
Thanks!
Am I allowed to bump? I have seen the exact same question before and it never was replied. . And I believe it is a good question. Worth an answer.
Thanks
Sent from my SM-G870W using XDA Free mobile app
marcil802 said:
Am I allowed to bump? I have seen the exact same question before and it never was replied. . And I believe it is a good question. Worth an answer.
Thanks
Sent from my SM-G870W using XDA Free mobile app
Click to expand...
Click to collapse
For installing safestrap you must remove XPOSED. Once installed SS you can reinstall xposed. BUT the only SafeStrap I found is for G900V (Verizon s5) and it has been abbonded in September 2015 as it has a heavy bug. If I was you, i won't look for adventures and flash other phone model's software to my own. And it could be usefull to check if the phone you are going to buy has a permanent locked bootloader when you're interested in modding.
Hey thanks man. Now I'm sure this is gonna a weird question to you but. As for safestrap I've read about out dated versions. But are there different versions for different devices? Could you help me get the right one for my phone or tell me where to download it.
Active g870w. Telus
Thanks alot.
Québec Canada
Sent from my SM-G870W using XDA Free mobile app
marcil802 said:
Hey thanks man. Now I'm sure this is gonna a weird question to you but. As for safestrap I've read about out dated versions. But are there different versions for different devices? Could you help me get the right one for my phone or tell me where to download it.
Active g870w. Telus
Thanks alot.
Québec Canada
Sent from my SM-G870W using XDA Free mobile app
Click to expand...
Click to collapse
Just like normal custom recoveries the safestrap recoveries also must be fitted for every single Phone. As comparison you can think about a custom recovery that works on every phone with unlocked bootlader. That was great but can never be made real. I already tried to find a matching recovery for your S5 active but haven't found anything suitable yet.
I'm still looking like crazy...
I have seen the at&t version got one also they
Now got a stock firmware and safestrap for them... Have you find anything that can suit our G870W
Im so desperate .
Sent from my SM-G870W using XDA Free mobile app
Here is the link of what I'm talking about
http://forum.xda-developers.com/showpost.php?p=56009811&postcount=1974
Sorry for my bad English.
Thanks and when ever I hear from another guy talking about the G870W it makes me feel like a baby with he's teddy bear... Lol
So left alone... Hard start for first time rooting
Dammit i guess i screwed i need help
IM , now stuck between power off and android system recovery
i try to do as i did before
-wipe data
-wipe cache
-apply update from extrnal storage/
-unity 2.1.0/
-Unity_ROM_V2.1.0_Signed.zip
it says
Install /sdcard/Unity 2.1.0...
then i reboot and it keep brigning me back to first step !
i guess thats a boot loop what now:crying:
BTW i forgot to say thanks for your time i apppreciate. in 18 month ill start enjoying my phone again
s5 active canadian
figured out how to flash custom roms to the g870w find a rom for an s5 variant that is snapdragon download it use 7zip to open the archive dont extract it (must get the telus ol1 firmware from android file host first ) once you have the ol1 telus firmware extract it with 7zip to a folder that you can remember now go back to the s5 rom you downloaded earlier look for the boot.img in 7zip and delete it then drag and drop the boot.img from the telus firmware that you downloaded........ On the phone make sure to root with cf auto root and install flashfire from the playstore as its vital for this to work as there is no custom recovery for the g870w now once you edit the custom rom you downloaded to include the telus boot.img drag and drop it to your phone open flash fire on the phone click the little plus button select the wipe fucntion then click the plus button again click the flash zip or ota option and select the modified custom rom you just transfered go back to where it shows the rom name and the wipe option hold on the wipe option and drag it to the spot above the rom name then click flash it will reboot and wipe then start flashing the modified custom rom.......if you want xposed download the sdk21 xposed and put it on your phone once it boots then go to flashfire again select just the flash option and select the xposed file click flash then phone will reboot flash xposed then boot up again...... i know its quiet a few steps but its the easiest way to get a custom rom on the canadian s5 active
link to the telus 5.0 https://www.androidfilehost.com/?w=search&s=g870w
xposed link http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3113463 choose the snapdragon one
currently using g900f phoenix rom 11.0 with no problems at all tested with popwiz and scorpion rom as well also now the tgp g900x rom
Thanks for the detailed information man. I wish I'd find as detailed information about my S6
I'm far from geek and I'm. Totally lost into this forum. And from being Canadian I feel like everything is a little more complicated. I never find anything for Canadian version. Same when I had my s3 any s5 active. Luckily someone pointed me step by step.
So take it as a help call ?.
Cheers
I've been look for a way to use diff ROM on my S5 Active. Mine is from Bell, will your procedure work on my phone?
Thanks.
S5 Active Bell
Hello jayandcourt2,
I followed your instructions but instead of using boot.img from Telus' stock ROM I used the ones from Bell (G870WVLU1BOL1_G870WOYA1BOL1_BMC.zip)
I tired using "PopWiz Edge Plus 5.1.1 for the Galaxy S5 SM-G900X Snapdragon" discussed on XDA Forum
I deleted boot.img on the Pop Wiz ROM and copied the boot.img I extracted from the stock Bell ROM as per your instruction. Ran Flashfire and added
'Wipe' and 'Flash ZIP or OTA' actions (Wipe the first action). After flashing it booted up OK. I went through the initial setup of the Phone, account name, wifi connection... etc.
I don't know if I actually installed the Pop Wiz ROM. It is still using Touch Wiz, and when I flashed the Xposed framework my phone just went into a boot loop.
Just like it would if the ROM is not deodexed. Would you mind giving me the URL's to some of the custom ROM's you have successfully use using the procedures you described?
Update: I re-did the procedure and I noticed during the flashing that I got a message, something like the ROM is for klte device and I have klteactive.
So I guess the custom ROM I have won't work with my G870W.
Thanks mate.
jayandcourt2 said:
figured out how to flash custom roms to the g870w find a rom for an s5 variant that is snapdragon download it use 7zip to open the archive dont extract it (must get the telus ol1 firmware from android file host first ) once you have the ol1 telus firmware extract it with 7zip to a folder that you can remember now go back to the s5 rom you downloaded earlier look for the boot.img in 7zip and delete it then drag and drop the boot.img from the telus firmware that you downloaded........ On the phone make sure to root with cf auto root and install flashfire from the playstore as its vital for this to work as there is no custom recovery for the g870w now once you edit the custom rom you downloaded to include the telus boot.img drag and drop it to your phone open flash fire on the phone click the little plus button select the wipe fucntion then click the plus button again click the flash zip or ota option and select the modified custom rom you just transfered go back to where it shows the rom name and the wipe option hold on the wipe option and drag it to the spot above the rom name then click flash it will reboot and wipe then start flashing the modified custom rom.......if you want xposed download the sdk21 xposed and put it on your phone once it boots then go to flashfire again select just the flash option and select the xposed file click flash then phone will reboot flash xposed then boot up again...... i know its quiet a few steps but its the easiest way to get a custom rom on the canadian s5 active
link to the telus 5.0 https://www.androidfilehost.com/?w=search&s=g870w
xposed link http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3113463 choose the snapdragon one
currently using g900f phoenix rom 11.0 with no problems at all tested with popwiz and scorpion rom as well also now the tgp g900x rom
Click to expand...
Click to collapse
m3tatr0n84 said:
Hello jayandcourt2,
I followed your instructions but instead of using boot.img from Telus' stock ROM I used the ones from Bell (G870WVLU1BOL1_G870WOYA1BOL1_BMC.zip)
I tired using "PopWiz Edge Plus 5.1.1 for the Galaxy S5 SM-G900X Snapdragon" discussed on XDA Forum
I deleted boot.img on the Pop Wiz ROM and copied the boot.img I extracted from the stock Bell ROM as per your instruction. Ran Flashfire and added
'Wipe' and 'Flash ZIP or OTA' actions (Wipe the first action). After flashing it booted up OK. I went through the initial setup of the Phone, account name, wifi connection... etc.
I don't know if I actually installed the Pop Wiz ROM. It is still using Touch Wiz, and when I flashed the Xposed framework my phone just went into a boot loop.
Just like it would if the ROM is not deodexed. Would you mind giving me the URL's to some of the custom ROM's you have successfully use using the procedures you described?
Update: I re-did the procedure and I noticed during the flashing that I got a message, something like the ROM is for klte device and I have klteactive.
So I guess the custom ROM I have won't work with my G870W.
Thanks mate.
Click to expand...
Click to collapse
Safestrap has been DEAD for years now. The SM-G870A and V versions have a locked boot-loader, W and T versions are luckier, but not to be used with Bootstrap. All we can do on A & V is to root it via Towelroot and Debloat it. Anything else will just brick it. I have tried everything and since Safestrap isn't developed any more, there is no newer Safestrap that would fit version 4 builds.
Thanks ChingghisKhan,
I don't know if owners of G870W are luckier, I tried to install both Clock Work and TWRP recovery and wasn't successful.
I believe it, like the A & V has a locked bootloader. I recently updated my Android OS to Marshmallow and lost
my root. Apparently rooting Marshmallow requires Systemless root and I haven't found any solution yet. Right now I'd
be happy just to get my root back on Android 6. I might have to just go back to Lollipop until someone find out
a way for a Systemless root on G870W.
Cheers.
ChingghisKhan said:
Safestrap has been DEAD for years now. The SM-G870A and V versions have a locked boot-loader, W and T versions are luckier, but not to be used with Bootstrap. All we can do on A & V is to root it via Towelroot and Debloat it. Anything else will just brick it. I have tried everything and since Safestrap isn't developed any more, there is no newer Safestrap that would fit version 4 builds.
Click to expand...
Click to collapse
m3tatr0n84 said:
Thanks ChingghisKhan,
I don't know if owners of G870W are luckier, I tried to install both Clock Work and TWRP recovery and wasn't successful.
I believe it, like the A & V has a locked bootloader. I recently updated my Android OS to Marshmallow and lost
my root. Apparently rooting Marshmallow requires Systemless root and I haven't found any solution yet. Right now I'd
be happy just to get my root back on Android 6. I might have to just go back to Lollipop until someone find out
a way for a Systemless root on G870W.
Cheers.
Click to expand...
Click to collapse
Hi m3tatr0n84,
Sorry to hear about your troubles.
I think the following will get you back to 5.1.1 and root: http://www.droidviews.com/update-att-galaxy-s5-active-to-lollipop-root-it-and-enable-wifi-tethering/
Install Rooted Lollipop ROM on AT&T Galaxy S5 Active
Note:
You can the following instruction of want to update to Lollipop and enjoy root access. Besides, you can install the rooted Lollipop firmware regardless of what firmware or build version your phone currently has.
Preparations
Rooted AT&T Galaxy S5 Active. If you don’t have root access, do as directed below:
Download the following firmware and extract it: G870AUCU1ANE4_Full_Odin.rar
Follow our tutorial to flash the firmware: Link
Then root your Galaxy S5 Active using Towelroot.
Enable USB Debugging on your Galaxy S5 Active. This step has nothing to do with the method given below but it could be a lifesaver if anything goes wrong.
Install Chainfire’s FireFlash app on your AT&T Galaxy S5 Active. Since this new app is only available for beta-testers currently, go to the Google+ page and join the Android-FlashFire community. You must be signed into Google+ using the same Gmail ID that you use on the Google Play Store. Having joined the community, click the Play Store link to download FireFlash.
Download the stock rooted Lollipop firmware for the AT&T Galaxy S5 Active:
G870A_OF3_Stock_Rooted_ROM.zip
G870A_OF2_Stock_Rooted_ROM.zip (older)
Also download the Odin (v3.10.6) OC5 bootloader file: G870A_OC5_Bootloader.tar.md5
Instructions
Copy the G870A_OF3_Stock_Rooted_ROM.zip to your device.
Before you do anything, open SuperSU app on your phone, tap the Settings tab, scroll to Enable su during boot option and enable it.enable-su-during-boot
Open the FlashFire app and “Agree” to the Terms and Conditions prompted by the app.
Press the rounded “+” button twice to bring up the Actions menu.fireflash-app-android
Now tap Flash Zip or OTA option and select the G870A_OF3_Stock_Rooted_ROM.zip.
Make sure that Auto-mount is unchecked under the Options menu and press the check-mark to continue.
From the main menu uncheck all options under EverRoot.
Set the Reboot settings to Download.
When all’s done, tap the Lightning bolt icon followed by OK to begin the installation.
When the installation is finished, your device will reboot automatically into the Download Mode.
Now connect your phone to the PC via USB cable and launch Odin.
Click the PDA/AP button in Odin and select the G870A_OC5_Bootloader.tar.md5 file.
Then hit the Start button to begin the installation.
Your AT&T Galaxy S5 Active will reboot automatically. Just wait patiently for a while. Done!
Enable WiFi Tethering on AT&T Galaxy S5 Active
Note: You must have root access to flash the WiFi Hotspot mod on your phone.
Install FireFlash app by Chainfire (see Method 1 for how to).
Download the Mobile Hotspot mod file and copy the zip to your phone: G870A_OC5_TetherAddOn.zip
Now launch FireFlash and tap the “+” icon twice to bring up the menu and then select Flash Zip or OTA option.
Navigate to G870A_OC5_TetherAddOn.zip file and select it.
Make sure that the Auto-mount option is not selected under Options.
Leave the default settings under EverRoot and Reboot options untouched.
Finally, tap the Lightning bolt icon and then tap OK.
Your phone’ screen will turn black for sometime so do not panic. When it turns up, install the Tether add-on zip file and reboot your device. When your phone boots up, you’ll be able to enjoy free WiFi hotspot on your AT&T Galaxy S5 Active (SM-G870A) running the new OC5 Lollipop firmware.
Thanks., but my carrier is Bell Canada. Will the AT&T ROM work on my S5 Active?
I was able to root the stock Lollipop using CF-Auto-Root-kltecanactive-kltevlactive-smg870w.zip
Cheers.
ChingghisKhan said:
Safestrap has been DEAD for years now. The SM-G870A and V versions have a locked boot-loader, W and T versions are luckier, but not to be used with Bootstrap. All we can do on A & V is to root it via Towelroot and Debloat it. Anything else will just brick it. I have tried everything and since Safestrap isn't developed any more, there is no newer Safestrap that would fit version 4 builds.
Click to expand...
Click to collapse
ChingghisKhan said:
Hi m3tatr0n84,
Sorry to hear about your troubles.
I think the following will get you back to 5.1.1 and root: http://www.droidviews.com/update-att-galaxy-s5-active-to-lollipop-root-it-and-enable-wifi-tethering/
Install Rooted Lollipop ROM on AT&T Galaxy S5 Active
Note:
You can the following instruction of want to update to Lollipop and enjoy root access. Besides, you can install the rooted Lollipop firmware regardless of what firmware or build version your phone currently has.
Preparations
Rooted AT&T Galaxy S5 Active. If you don’t have root access, do as directed below:
Download the following firmware and extract it: G870AUCU1ANE4_Full_Odin.rar
Follow our tutorial to flash the firmware: Link
Then root your Galaxy S5 Active using Towelroot.
Enable USB Debugging on your Galaxy S5 Active. This step has nothing to do with the method given below but it could be a lifesaver if anything goes wrong.
Install Chainfire’s FireFlash app on your AT&T Galaxy S5 Active. Since this new app is only available for beta-testers currently, go to the Google+ page and join the Android-FlashFire community. You must be signed into Google+ using the same Gmail ID that you use on the Google Play Store. Having joined the community, click the Play Store link to download FireFlash.
Download the stock rooted Lollipop firmware for the AT&T Galaxy S5 Active:
G870A_OF3_Stock_Rooted_ROM.zip
G870A_OF2_Stock_Rooted_ROM.zip (older)
Also download the Odin (v3.10.6) OC5 bootloader file: G870A_OC5_Bootloader.tar.md5
Instructions
Copy the G870A_OF3_Stock_Rooted_ROM.zip to your device.
Before you do anything, open SuperSU app on your phone, tap the Settings tab, scroll to Enable su during boot option and enable it.enable-su-during-boot
Open the FlashFire app and “Agree” to the Terms and Conditions prompted by the app.
Press the rounded “+” button twice to bring up the Actions menu.fireflash-app-android
Now tap Flash Zip or OTA option and select the G870A_OF3_Stock_Rooted_ROM.zip.
Make sure that Auto-mount is unchecked under the Options menu and press the check-mark to continue.
From the main menu uncheck all options under EverRoot.
Set the Reboot settings to Download.
When all’s done, tap the Lightning bolt icon followed by OK to begin the installation.
When the installation is finished, your device will reboot automatically into the Download Mode.
Now connect your phone to the PC via USB cable and launch Odin.
Click the PDA/AP button in Odin and select the G870A_OC5_Bootloader.tar.md5 file.
Then hit the Start button to begin the installation.
Your AT&T Galaxy S5 Active will reboot automatically. Just wait patiently for a while. Done!
Enable WiFi Tethering on AT&T Galaxy S5 Active
Note: You must have root access to flash the WiFi Hotspot mod on your phone.
Install FireFlash app by Chainfire (see Method 1 for how to).
Download the Mobile Hotspot mod file and copy the zip to your phone: G870A_OC5_TetherAddOn.zip
Now launch FireFlash and tap the “+” icon twice to bring up the menu and then select Flash Zip or OTA option.
Navigate to G870A_OC5_TetherAddOn.zip file and select it.
Make sure that the Auto-mount option is not selected under Options.
Leave the default settings under EverRoot and Reboot options untouched.
Finally, tap the Lightning bolt icon and then tap OK.
Your phone’ screen will turn black for sometime so do not panic. When it turns up, install the Tether add-on zip file and reboot your device. When your phone boots up, you’ll be able to enjoy free WiFi hotspot on your AT&T Galaxy S5 Active (SM-G870A) running the new OC5 Lollipop firmware.
Click to expand...
Click to collapse
m3tatr0n84 said:
Thanks., but my carrier is Bell Canada. Will the AT&T ROM work on my S5 Active?
I was able to root the stock Lollipop using CF-Auto-Root-kltecanactive-kltevlactive-smg870w.zip
Cheers.
Click to expand...
Click to collapse
Hi m3tatr0n84,
You need to substitute the version that fits your phone, i.e. "W" or which ever you have. http://www.sammobile.com/firmwares/
I am using "A" here in Mongolia with any carrier, also works in Germany, India, etc...

Already rooted Samsung J5 - general inquiry

Hello guys. I just bought a used Samsung Galaxy J5 (SM-J500FN) with android version 5.1.1. The previous owner told me that it is rooted. Nothing seems weird with the phone other than when i try to factory reset it it takes me to a "bios" kind window where i have to manually choose to delete all data (hard delete i think its called), that and when i normally turn on the phone, at the top left corner it says "set warranty bit kernel". I was just wondering how do i go about installing custom roms since its already rooted, and can i unblock the default carriers (T-mobile) block for other sim cards. When asked how he rooted it (what method was he using) he said he just used Odin. I dont know much about rooting so, whatever you can tell me as to the handling of the phone would be amazing. Any other guides to installing some custom roms and making the phone easier and faster ( i only want functionality, don't care much about the UI) would be greatly appreciated. Thanks in advance.
luan96 said:
Hello guys. I just bought a used Samsung Galaxy J5 (SM-J500FN) with android version 5.1.1. The previous owner told me that it is rooted. Nothing seems weird with the phone other than when i try to factory reset it it takes me to a "bios" kind window where i have to manually choose to delete all data (hard delete i think its called), that and when i normally turn on the phone, at the top left corner it says "set warranty bit kernel". I was just wondering how do i go about installing custom roms since its already rooted, and can i unblock the default carriers (T-mobile) block for other sim cards. When asked how he rooted it (what method was he using) he said he just used Odin. I dont know much about rooting so, whatever you can tell me as to the handling of the phone would be amazing. Any other guides to installing some custom roms and making the phone easier and faster ( i only want functionality, don't care much about the UI) would be greatly appreciated. Thanks in advance.
Click to expand...
Click to collapse
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
ShaDisNX255 said:
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
Click to expand...
Click to collapse
That's what I love about Samsung, as long as you have your ducks in a row, the files and tools are extremely easy to use, a 4 year old could do it.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
ShaDisNX255 said:
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
Click to expand...
Click to collapse
Thank you, ill be sure to check them out. Although, i would like to do the entire process from the beginning (root it again myself since i have no idea what the previous owner has done) and then try to install custom roms and other cool features rooting offers. I read that the KNOX security on samsung phones can pose some problems, any thoughts on that ?
Thank you again for your response.
ShaDisNX255 said:
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
Click to expand...
Click to collapse
Also, i use Linux so i hear the alternative to Odin is Heimdall, anyone have any experience with it, or should i just do it on a Windows PC?
luan96 said:
Also, i use Linux so i hear the alternative to Odin is Heimdall, anyone have any experience with it, or should i just do it on a Windows PC?
Click to expand...
Click to collapse
I've got no experience with Linux, sorry. SuperSU disables knox so there's nothing to worry about.
luan96 said:
Also, i use Linux so i hear the alternative to Odin is Heimdall, anyone have any experience with it, or should i just do it on a Windows PC?
Click to expand...
Click to collapse
If you're a Linux user and you have knowledge of using terminal commands then you should have no trouble setting up Hiemdall. Getting full USB functionality set up for the device in Hiemdall can be a pain if you aren't familiar with that kind of thing.
But, having a Windows PC will make a lot of things very simplified for you. A Windows/Linux dual boot system would be very handy to you if you can set that up. Then you could also use Kies/SmartSwitch if it ever comes to a point that you need it.
There are some handy rarely used instances with Linux when it comes to Samsung. They have no fastboot like other devices so only adb is usable. I think they primarily centered around Windows being the preferred OS to interact with their devices.
Droidriven said:
If you're a Linux user and you have knowledge of using terminal commands then you should have no trouble setting up Hiemdall. Getting full USB functionality set up for the device in Hiemdall can be a pain if you aren't familiar with that kind of thing.
But, having a Windows PC will make a lot of things very simplified for you. A Windows/Linux dual boot system would be very handy to you if you can set that up. Then you could also use Kies/SmartSwitch if it ever comes to a point that you need it.
There are some handy rarely used instances with Linux when it comes to Samsung. They have no fastboot like other devices so only adb is usable. I think they primarily centered around Windows being the preferred OS to interact with their devices.
Click to expand...
Click to collapse
Thank you for the info. I already have a dual boot on my pc with windows. I am an experienced Linux user and setting up Hiemdall should not pose a problem, but i opted to go for Windows since as you said makes things simpler.
Still looking for guides and tutorials on how exactly the root process goes. Doing research, so i guess its going to be a late night. If you have any links or pages you can guide me to for my Samsung J5 it would be amazing. Right now am looking around this forum and wherever the links lead me.
Thank you again.
luan96 said:
Thank you for the info. I already have a dual boot on my pc with windows. I am an experienced Linux user and setting up Hiemdall should not pose a problem, but i opted to go for Windows since as you said makes things simpler.
Still looking for guides and tutorials on how exactly the root process goes. Doing research, so i guess its going to be a late night. If you have any links or pages you can guide me to for my Samsung J5 it would be amazing. Right now am looking around this forum and wherever the links lead me.
Thank you again.
Click to expand...
Click to collapse
First, just to make sure that you are not walking blindly into some potential traps.
1) download the root checker app from Playstore, use it to verify whether the device is actually rooted.
2) power the device off, wait 5 seconds, hold volume up+home+power, when it boots past the logo, let go. It should boot to recovery, tell me what you see. Does it say TWRP with grey buttons on a black screen? Or does it have an android lying on his back and have options listed?
3) verify whether or not the bootloader is unlocked or not on your specific device model number with your specific build number/android version, if it's locked it will create problems if you try to flash custom recovery. Though you can flash CF autoroot with locked bootloader.
Then I'll help find what you need to do what you are looking to do. It may be simpler than you think.
If he in fact used Odin and the device is rooted, he did one of three things.
1) flashed custom recovery(TWRP) via Odin then flashed SuperSU.zip to root, not possible with locked bootloader.
2) flashed CF auto root via Odin, potentially leaving stock recovery if your bootloader is locked.
3) flashed a pre-rooted stock firmware via Odin, not likely though.
The first 2 being more likely than the last one, the second one being the most likely if your bootloader is locked.
Edit: @luan96, edited for more information.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
@Droidriven Thank you for the info. After a rough night of research i realized what i need to do. According to root checker, my phone is not rooted, and the recovery seems to be stock. This is very weird, since the phone is obviously not just the stock version that came from T Mobile. Im guessing its probably a badly done root or one that was removed. Anyways, this is how i am planing to proceed:
1. Turn on OEM Unlocking and USB Debugging from developer versions
2. Download CM Autoroot for my specific phone ( i do not know what is the difference between "normal" root and autoroot, but autoroot seems to be simpler and offers the same thing. Please correct me if i am wrong, i would love to know how to do a manual root as well if it has more benefits).
3. Volume down+home+power to get to the download screen
4. Launch Odin that comes with the autoroot package
5. Plug my phone into the USB and wait for Odin to add it.
6. Select the autoroot md5 file from the folder and begin the flashing process
7. Hope for the best and that my phone is still functional when it auto reboots.
After this i should check with Root Checker weather its properly installed or not. If it is, and i see the SuperSU application i continue to installing the custom recovery ( through some research i found out that TWRP is the best choice for me). Installing the custom recovery should be as easy as auto rooting the device. I should download the files from an official website, and flash them using the same process i did for AutoRoot.
After that its mod heaven. With my understanding so far, TWRP lets me install custom roms, and other things i might need.
This is what i plan on doing as soon as im done with a little more research. If anyone has any tips, corrections or general information on what to expect or do please share.
Many thanks to every contributor on this thread.
luan96 said:
@Droidriven Thank you for the info. After a rough night of research i realized what i need to do. According to root checker, my phone is not rooted, and the recovery seems to be stock. This is very weird, since the phone is obviously not just the stock version that came from T Mobile. Im guessing its probably a badly done root or one that was removed. Anyways, this is how i am planing to proceed:
2. Download CM Autoroot for my specific phone ( i do not know what is the difference between "normal" root and autoroot, but autoroot seems to be simpler and offers the same thing. Please correct me if i am wrong, i would love to know how to do a manual root as well if it has more benefits).
3. Volume down+home+power to get to the download screen
4. Launch Odin that comes with the autoroot package
5. Plug my phone into the USB and wait for Odin to add it.
6. Select the autoroot md5 file from the folder and begin the flashing process
7. Hope for the best and that my phone is still functional when it auto reboots.
After this i should check with Root Checker weather its properly installed or not. If it is, and i see the SuperSU application i continue to installing the custom recovery ( through some research i found out that TWRP is the best choice for me). Installing the custom recovery should be as easy as auto rooting the device. I should download the files from an official website, and flash them using the same process i did for AutoRoot.
After that its mod heaven. With my understanding so far, TWRP lets me install custom roms, and other things i might need.
This is what i plan on doing as soon as im done with a little more research. If anyone has any tips, corrections or general information on what to expect or do please share.
Many thanks to every contributor on this thread.
Click to expand...
Click to collapse
I would recommend using the command line to flash the twrp instead of the GUI if you want a simple process in linux
Run a terminal as a superuser (sudo)
heimdall flash –RECOVERY filename.img
Do step 1 and 3 you gave before before doing this
Or just flash the twrp image using Odin
J500FN twrp
https://dl.twrp.me/j5nltexx/
-Hope- said:
I would recommend using the command line to flash the twrp instead of the GUI if you want a simple process in linux
Run a terminal as a superuser (sudo)
heimdall flash –RECOVERY filename.img
Do step 1 and 3 you gave before before doing this
Or just flash the twrp image using Odin
J500FN twrp
https://dl.twrp.me/j5nltexx/
Click to expand...
Click to collapse
I'm going to use Odin for this. Since I'm quite new to the rooting community I dont want to mess things up on the first try. I'd rather get comfortable with some standard stuff before I proceed to try different variations. Thank you for your input. Though I would still like to know if I should use cm auto root or do a manual root. The difference is not quite clear to me yet. Again, thank you for your input, it is appreciated.
luan96 said:
@Droidriven Thank you for the info. After a rough night of research i realized what i need to do. According to root checker, my phone is not rooted, and the recovery seems to be stock. This is very weird, since the phone is obviously not just the stock version that came from T Mobile. Im guessing its probably a badly done root or one that was removed. Anyways, this is how i am planing to proceed:
1. Turn on OEM Unlocking and USB Debugging from developer versions
2. Download CM Autoroot for my specific phone ( i do not know what is the difference between "normal" root and autoroot, but autoroot seems to be simpler and offers the same thing. Please correct me if i am wrong, i would love to know how to do a manual root as well if it has more benefits).
3. Volume down+home+power to get to the download screen
4. Launch Odin that comes with the autoroot package
5. Plug my phone into the USB and wait for Odin to add it.
6. Select the autoroot md5 file from the folder and begin the flashing process
7. Hope for the best and that my phone is still functional when it auto reboots.
After this i should check with Root Checker weather its properly installed or not. If it is, and i see the SuperSU application i continue to installing the custom recovery ( through some research i found out that TWRP is the best choice for me). Installing the custom recovery should be as easy as auto rooting the device. I should download the files from an official website, and flash them using the same process i did for AutoRoot.
After that its mod heaven. With my understanding so far, TWRP lets me install custom roms, and other things i might need.
This is what i plan on doing as soon as im done with a little more research. If anyone has any tips, corrections or general information on what to expect or do please share.
Many thanks to every contributor on this thread.
Click to expand...
Click to collapse
Flashing CF autoroot will simplify rooting, again, just make sure you have the correct autoroot for your specific model number and firmware, flashing the wrong one can softbrick or hardbrick your device, this would require flashing stock firmware via Odin to repair if softbricked and more serious methods to restore if hardbricked. There isn't much difference in effect with the different rooting methods. They all get the job done about equally.
Just make sure that you verify that your bootloader is in fact unlocked BEFORE you flash TWRP. As stated earlier, if it is locked, it will certainly cause issues and you'll have to restore stock recovery and/or stock firmware.
As long as your bootloader is unlocked then your outlined plan should be good to go.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Flashing CF autoroot will simplify rooting, afain, just make sure you have the correct autoroot for your specific model number and firmware, flashing the wrong one can softbrick or hardbrick your device, this would require flashing stock firmware via Odin to repair if softbricked and more serious methods to restore if hardbricked. There isn't much difference in effect with the different rooting methods. They all get the job done about equally.
Just make sure that you verify that your bootloader is in fact unlocked BEFORE you flash TWRP. As stated earlier, if it is locked, it will certainly cause issues and you'll have to restore stock recovery and/or stock firmware.
As long as you're bootloader is unlocked then your outlined plan should be good to go.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Well, looks like i messed up somehow. I was fiddling around the recovery mode and Odin mode. Those were the only two screens i could view besides normal booting, so i was looking for any info.
Recovery Mode https://ibb.co/hotYZ5
Odin mode 1 https://ibb.co/nFfVE5
Once on the recovery mode, i selected "reboot to bootloader" hoping to find info if its locked or not. I got redirected to this screen
Odin Mode 2 https://ibb.co/kqhtZ5
And then i did what i think is the dumbest thing this year....i removed the batery and now when i try to turn on my phone -
Blocked https://ibb.co/kkOd1k
Please tell me i did not brick my phone without even trying to root it first. My understanding is that i accidentally wiped the current OS (softbrick?) and now i have to flash a new one and then continue with what i had planned. Or is this a small problem that can be fixed easier? Or a more serious one ? Good news tho maybe, i think that the bootloader is unlocked ?
Thank you @Droidriven for your info so far, you have been extremely helpful.
*EDIT* - Pictures didnt link correctly.
luan96 said:
Well, looks like i messed up somehow. I was fiddling around the recovery mode and Odin mode. Those were the only two screens i could view besides normal booting, so i was looking for any info.
Recovery Mode https://ibb.co/hotYZ5
Odin mode 1 https://ibb.co/nFfVE5
Once on the recovery mode, i selected "reboot to bootloader" hoping to find info if its locked or not. I got redirected to this screen
Odin Mode 2 https://ibb.co/kqhtZ5
And then i did what i think is the dumbest thing this year....i removed the batery and now when i try to turn on my phone -
Blocked https://ibb.co/kkOd1k
Please tell me i did not brick my phone without even trying to root it first. My understanding is that i accidentally wiped the current OS (softbrick?) and now i have to flash a new one and then continue with what i had planned. Or is this a small problem that can be fixed easier? Or a more serious one ? Good news tho maybe, i think that the bootloader is unlocked ?
Thank you @Droidriven for your info so far, you have been extremely helpful.
*EDIT* - Pictures didnt link correctly.
Click to expand...
Click to collapse
It looks to me like they attempted to root the device but didn't do it correctly.
FRP can be a pain to deal with. Some can be bypassed easily, those that have trouble bypassing must sign in with the original owner's original Gmail and password used to activate the device.
The method of bypassing FRP varies from device to device.
Did you factory reset in recovery? If so, that's why you FRP blocked you.
If you have stock recovery then you should not have been able to wipe out the OS using stock recovery, typically, only custom recovery can do that, unless you did something accidentally that somehow corrupted/wiped your OS.
If the OS is gone, you'll have to flash your stock firmware via Odin and start over from the beginning.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
It looks to me like they attempted to root the device but didn't do it correctly.
FRP can be a pain to deal with. Some can be bypassed easily, those that have trouble bypassing must sign in with the original owner's original Gmail and password used to activate the device.
The method of bypassing FRP varies from device to device.
Did you factory reset in recovery? If so, that's why you FRP blocked you.
If you have stock recovery then you should not have been able to wipe out the OS using stock recovery, typically, only custom recovery can do that, unless you did something accidentally that somehow corrupted/wiped your OS.
If the OS is gone, you'll have to flash your stock firmware via Odin and start over from the beginning.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Thank you. At least its not just a paperweight. I'm installing new software on it with Kiesk 3 right now. Hope that works so i can do the rooting and TWRP install soon. I pressed "reboot to bootlader" to try and find out if its locked or not, but then it got me in download mode (without having to press up volume to contionue). After i turned off my phone by removing the battery, the OS was gone.
luan96 said:
Thank you. At least its not just a paperweight. I'm installing new software on it with Kiesk 3 right now. Hope that works so i can do the rooting and TWRP install soon. I pressed "reboot to bootlader" to try and find out if its locked or not, but then it got me in download mode (without having to press up volume to contionue). After i turned off my phone by removing the battery, the OS was gone.
Click to expand...
Click to collapse
Did you get this restored with Kies?
Droidriven said:
Did you get this restored with Kies?
Click to expand...
Click to collapse
Yes, i did. Worked like a charm, and even got the new 6.0.1 android on it. Also installed TWRP, and just finished installing Xposed Framework, now waiting for it to boot up ( i hear it takes some time). Seems all well so far. If any problems pop out ill be sure to post about it. Also thinking about making a new thread just to help newbies like me who really just want to remove some bloatware, and install some nice modules and not heavily mod the phone. You have been very helpful during this process. Many thanks to you ^-^ .
luan96 said:
Yes, i did. Worked like a charm, and even got the new 6.0.1 android on it. Also installed TWRP, and just finished installing Xposed Framework, now waiting for it to boot up ( i hear it takes some time). Seems all well so far. If any problems pop out ill be sure to post about it. Also thinking about making a new thread just to help newbies like me who really just want to remove some bloatware, and install some nice modules and not heavily mod the phone. You have been very helpful during this process. Many thanks to you ^-^ .
Click to expand...
Click to collapse
If you have issues with Xposed causing a bootloop, you can flash the Xposed uninstaller zip in TWRP to remove it, then troubleshoot why it bootlooped and try again.
Are you using the Touch wiz marshmallow Xposed framework?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Categories

Resources