Database Users

[GUIDE] The Beginner's Guide to Rooting Galaxy S3 and installing your first ROM

The Galaxy S3 being my first android (or smartphone for that matter), I had a tough time trying to figure out how to root my phone, which methods to use and which ROM to install. So I've compiled this from other threads here on xda after 2 days of heavy reading, for other noobs like me
FOLLOW THIS GUIDE TO THE LETTER. DO NOT TOUCH ANYTHING, PRESS ANYTHING, CHECK ANY BOXES UNLESS TOLD TO DO SO OR YOU WILL END UP WITH A 600$ BRICK
[/COLOR]Rooting
So what is rooting? Rooting basically gives you administrator privileges on your phone, allowing you to install a host of programs that allow you to, for e.g. use firewalls, remove bloatware, change themes, install improved kernels, install custom roms with improved boot and memory performance, the list is really endless.
ROOTING VOIDS YOUR WARRANTY
However, it IS possible to reverse the process and cover your tracks, should you need to claim warranty. Read on to find out how.
Here is some good prereading to help you understand the basic flashing process and apps involved, even if it was written for the S2:
http://forum.xda-developers.com/showthread.php?t=1125282
Before we begin, its a good idea to note down the details under Settings -> About Phone, for future reference. Also note that under Status, if you root your phone, it changes to 'Modified'. This is, as stated before, reversible.
This guide is for the GT-I9300 Model. If your model number has a suffix (other than T) this may not work.
Step 1: Flashing CF-Root with Odin
This is an easy method to root your phone and I haven't needed to use any other. It comes with the added benefit of also installing Clockwork Mod and CWManager which we will use to make backups, flash our first ROM and cover our tracks. For those of you who want to install the newer clockworkmod touch look here:
http://forum.xda-developers.com/showthread.php?t=1719744
Guide compiled from here:
http://forum.xda-developers.com/showthread.php?t=1695238
1. Install Samsung Kies and plug your phone into your PC via USB so that all the appropriate phone drivers are installed
2. Download and extract Odin3-vX.X.zip from the download link below
3. Download and extract CF-Root-SGS3-vX.X.zip ONCE (you will end up with CF-Root-SGS3-vX.X.tar
CF-Root for SGS3 v6.4:
http://download.chainfire.eu/196/CF-Root/SGS3/CF-Root-SGS3-v6.4.zip
4. Disconnect your phone from your computer, close Samsung Kies and any antivirus/firewall that may interrupt the flashing process
5. Run Odin, click PDA and navigate to your CF-Root-SGS3-vX.X.tar file
6. Power off your phone and then boot it into download mode (Hold Volume Down + Home + Power button until the screen fires up)
7. Note the warning and continue.
8. Connect the phone to your PC via USB and allow drivers to install.
9. Make sure 'Re-partition' is NOT checked in Odin
10. Click Start button and wait for android to boot
11. If you see a green 'PASS' message in Odin, everything went as intended. Done!
Step 2: Make a NANDroid Backup
This is a precautionary measure that backs up your phone's current state, should you have any problems with custom Roms. It is also a step in reversing the root process, should you need to claim warranty.
1. Power off your phone and boot into recovery mode (Hold Volume Up + Home + Power button untill the screen fires up). This starts up ClockworkMod.
2. Use Volume Up/Down to navigate and the Power button to select
3. Navigate to Backup/Restore->Backup and wait for backup to finish
4. Go back and select 'Reboot System Now'
5. Connect your phone to your computer and copy the backup folder from /sdcard/clockworkmod/backups/
6. Done! Now you can restore this backup by booting into recovery mode and hitting Restore!
Step 3: Installing your first ROM
After hunting for a good ROM that was fast and bloatware free, I ended up with the nightly build of the popular CyanogenMod 9 and I don't intend to go back!! I haven't had any problems with it whatsoever but if you prefer, you could instead install the RC version.
Note: The camera's flash feature cannot and will not work on any version of cyanogenmod until samsung releases source code for their camera.
Here's how to flash the ROM. This is also the basic method of installing any other ROM or kernel, though the ROM/kernel developer would give you more tailored instructions.
1. Download the desired version of CyanogenMod 9 from here:
http://get.cm/?device=i9300
2. Download Gapps from here. I used the 20120429 version. This may not be necessary for other roms.
http://goo.im/gapps
3. Copy both files to your phone's internal sd card
4. Boot into recovery mode
5. Select 'wipe/factory reset' and confirm
6. Select 'wipe cache partition' and confirm
7. Go to Advanced -> wipe dalvik cache and confirm.
Now we're ready to flash the ROM!
8. Select 'install zip from sd card'
9. Select 'install zip from internal sd card and navigate to the cyanogenmod file and confirm
10. When done, use the same method to install the gapps file
11. Do a wipe/factory reset again (needed for google calendar sync to work)
12. Go back and select 'Reboot system now'
13. The boot screen of the new ROM will show up. Wait about 10 seconds, remove the battery and put it back in.
14. Power on and setup your phone. Done!
More on CyanogenMod:
http://forum.xda-developers.com/showthread.php?t=1714354
Step 4: Installing your modem
With CyanogenMod 9, people report that the first call made doesn't work, but every subsequent call will. If, however, you are still unable to make calls, you may have to install your phone's specific modem driver which you should have noted under Baseband version before we began (under Settings->About Phone).
1. Go here to download your specific modem and copy it to your phone's internal sd card:
http://forum.xda-developers.com/showthread.php?t=1740061
In my case, it was XXLFB.
2. Boot into Recovery Mode
3. Install .zip from internal sdcard and navigate to your modem.zip file
4. Done!
Step 5: Covering your tracks
So your phone is broken and you need to claim warranty? Not with your rooted phone you don't! The S3 uses a flash counter that tells it how many times the phone has been flashed, and your rooted phone appears as 'modified' under status information. Here's how to cover your tracks.
1. Download your phone's stock firmware for your region from here and copy it to your phone
http://www.sammobile.com/firmware/?page=3
2. Download TriangleAway from the download link below or consider buying it from googleplay to support the hardworking developers, extract it and copy it to your phone:
http://forum.xda-developers.com/showthread.php?t=1494114
3. Install TriangleAway by opening the .apk your phone's file explorer (Mine's ES File Explorer)
4. Run TriangleAway and select 'Reset Flash Counter'. Your phone will Reboot into a special mode. Reset the flash counter here and pull the battery immediately after reboot.
5. Boot into Recovery Mode and do a factory reset, cache wipe and dalvik cache wipe.
6. Flash the stock Firmware, reboot and setup the phone without any logins.
7. Check that Settings -> About Device -> Status is not 'Modified'
8. Done!
[
More on TriangleAway:
http://forum.xda-developers.com/showthread.php?t=1494114
Optional: Upgrade to CM10
1. Make a Nandroid backup so you can restore if you dont like cm10/if its too buggy.
2. Download CyanogenMod 10, Gapps and your modem from here and copy it to your internal sd card:
http://www.clockworkmod.com/rommanager/device/i9300/developer/daniel.hillenbrand%40codeworkx.de?manifest=http%3A%2F%2Fdeveloper.clockworkmod.com%2Fdeveloper%2Fdaniel.hillenbrand%40codeworkx.de%2Fmanifest&name=codeworkx&deviceName=Samsung%20Galaxy%20S3
3. Boot into Recovery Mode and install cm10 then gapps then modem using 'install zip from sd card -> choose zip from internal sd card'
4. Do a factory reset/wipe then reboot
5. Done!
More on CyanogenMod 10:
http://forum.xda-developers.com/showthread.php?t=1779578
Please point out any errors/suggestions so I can make the appropriate changes. Also report any issues for the benefit of other noobs out there
Admins: If my formatting is inappropriate I apologize but I'm by no means an expert at this
Credits:
Chainfire
Teamhacksung
willk22
UpInTheAir
and All contributors without whom none of this would be possible
Download

I'm afraid to root mine in case something goes wrong.

Thus is the best root guide I have read thank you so much , will do thus when cm10 is more everyday user friendly. Can not thank you enough.
Sent from my GT-I9300 using xda premium

Awesome guide mate.
I'm too big a wuss to flash a custom rom at the moment but this is pushing me to try it!

good thread man just moved from sgs2 to this and what an improvement! Cheers

I spent an entire day researching heavily before I was comfortable doing this and since everything is compiled here, I'm glad to see it having the same effect on you guys

Triangle Away is a payed app. Offered for free by chainfire on his thread for xda members. He specifically asked not to post it elsewhere. I think you are not permitted to attach it on other thread. At least ask for permission to do it.
Sent from my GT-I9100 using Tapatalk 2

Phil3759 said:
Triangle Away is a payed app. Offered for free by chainfire on his thread for xda members. He specifically asked not to post it elsewhere. I think you are not permitted to attach it on other thread. At least ask for permission to do it.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
I have posted this thread only on xda and like chainfire believe it should be available for free. People won't buy the app unless theyve tried it and know it works. But since you complained I've removed the attachment and people will have to visit chainfire's thread in order to download it.
Thanks for feedback!

Use Clockworks Touch
http://forum.xda-developers.com/showthread.php?t=1719744
Can be found here

Updated to include clockwork touch option.

Awesome stuff jbonetwo :good:
Question though? Rooted & installed Cyanogen 9 as above, followed all steps all rebooted and set up phone as if 1st time user. Now I've lost all apps, contacts, messages etc and nothing has synced?
How can I get all contacts back? Not sure why it hasn't synced as I've linked my Gmail account and sync is on?
Please excuse an Android noob....

Updated with CM10 Instructions

FinGerS o FuDgE said:
Awesome stuff jbonetwo :good:
Question though? Rooted & installed Cyanogen 9 as above, followed all steps all rebooted and set up phone as if 1st time user. Now I've lost all apps, contacts, messages etc and nothing has synced?
How can I get all contacts back? Not sure why it hasn't synced as I've linked my Gmail account and sync is on?
Please excuse an Android noob....
Click to expand...
Click to collapse
You will lose your apps when switching to a new rom. One good way to reinstall apps is with titanium backup pro (batch reinstall).
If you had your contacts sync;d with google, syncing with your google account on your new rom should (supposedly) restore your contacts. I didnt have to do this though since i added contacts after installing cm9.

Thank you for the guide, worked first time for me

Help! Marshmallow 6.0.1 ROM has been flashing for hours!

Over the weekend my Nexus 4 decided not to start. Saturday night it was working, and I hooked it up to charge. By Sunday morning it had turned off. When I restarted it, it got as far as asking for my password (encryption key), and then the four circles just danced around for hours. After letting it sit for a few days, the phone started again. But the experience made me decide it was time to update the system from Kit Kat.
So, more or less, I followed the instructions on the Team Android site. (As a new member of this forum, I'm not allowed to include the link. But Google "Update Nexus 4 to Android 6.0.1 Pure Nexus Project Marshmallow Custom ROM.") The main differences were (1) I only copied the ROM file over and (2) I used TWRP instead of CWM for the recovery. I was having trouble copying the Gapps file, so I thought it would be easier to install Marshmallow first and do the apps later.
Everything was backed up and copied around 7 PM yesterday, when I then wiped the data, did a factory reset, wiped the cache, wiped the dalvik cache, and finally started the installation. It's now almost 1 AM, and the ROM is still being flashed.
What should I do next?

Well it seems like the ROM you downloaded is a corrupt zip file.
I would like you to go to Original Development and download one of the ROMS from there, and then google opengapps, choose, ARM>6.0.1>Pico package (or any other package of your choice). I recommend Pico for your first install which is barebones google play services and Google Play store.
TWRP is perfectly compatible with most recent roms.
And for 6.0.1 , Flash the ROM and then flash GAPPS right away. After flashing, wipe dalvik/cache and then reboot.
If you have any questions, do not hesitate to post them here. good luck
EDIT: If you want Vanilla android with zero modifications, get this one:
http://forum.xda-developers.com/nexus-4/development/rom-6-0-android-marshmallow-pure-aosp-t3220900
Also, if it helps, I got 4 hours of Screen On Time on this ROM, I never got it on any other ROM so it is very light and is exactly what you would be getting on a nexus device.

mohsinkhan35 said:
Well it seems like the ROM you downloaded is a corrupt zip file.
I would like you to go to Original Development and download one of the ROMS from there, and then google opengapps, choose, ARM>6.0.1>Pico package (or any other package of your choice). I recommend Pico for your first install which is barebones google play services and Google Play store.
TWRP is perfectly compatible with most recent roms.
And for 6.0.1 , Flash the ROM and then flash GAPPS right away. After flashing, wipe dalvik/cache and then reboot.
If you have any questions, do not hesitate to post them here. good luck
EDIT: If you want Vanilla android with zero modifications, get this one:
http://forum.xda-developers.com/nexus-4/development/rom-6-0-android-marshmallow-pure-aosp-t3220900
Also, if it helps, I got 4 hours of Screen On Time on this ROM, I never got it on any other ROM so it is very light and is exactly what you would be getting on a nexus device.
Click to expand...
Click to collapse
Thanks, Mohsinkhan35. I followed the link you included and downloaded the ROM and TWRP 3.0.0-0, as the site requires. (I currently have TWRP 2.7.1.0 installed.) I was unable to download the Pico Gapp from that site, since the link seems to be broken. No problem. It's available from lots of locations.
So, as I understand it, my first step should be updating TWRP. I found instructions on how to do this at PhoneArena.com. Although written for Windows users, basically one starts the phone in bootloader mode and then uses adp commands to flash the new recovery (TWRP file).
But now Android File Transfer is not connecting to the phone. I wouldn't expect it to connect if the phone wasn't booted, as the file system is encrypted. Nonetheless, I tried this way without success. Then I tried using bootloader mode, with similar results. I then booted up in RM and got into TWRP, but AFT still doesn't see the phone. This is not altogether unexpected. If the new OS has settings and drivers to connect to my computer (a Yosemite iMac), and I've wiped the old one to make way for the new install, then how can the phone communicate with the PC?
For each of these cases (normal start, bootloader, and RM), I also tried issuing "adb devices" from a command prompt, but it's also returning nothing.
So any suggestions for the next step?

Von Neumann said:
Thanks, Mohsinkhan35. I followed the link you included and downloaded the ROM and TWRP 3.0.0-0, as the site requires. (I currently have TWRP 2.7.1.0 installed.) I was unable to download the Pico Gapp from that site, since the link seems to be broken. No problem. It's available from lots of locations.
So, as I understand it, my first step should be updating TWRP. I found instructions on how to do this at PhoneArena.com. Although written for Windows users, basically one starts the phone in bootloader mode and then uses adp commands to flash the new recovery (TWRP file).
But now Android File Transfer is not connecting to the phone. I wouldn't expect it to connect if the phone wasn't booted, as the file system is encrypted. Nonetheless, I tried this way without success. Then I tried using bootloader mode, with similar results. I then booted up in RM and got into TWRP, but AFT still doesn't see the phone. This is not altogether unexpected. If the new OS has settings and drivers to connect to my computer (a Yosemite iMac), and I've wiped the old one to make way for the new install, then how can the phone communicate with the PC?
For each of these cases (normal start, bootloader, and RM), I also tried issuing "adb devices" from a command prompt, but it's also returning nothing.
So any suggestions for the next step?
Click to expand...
Click to collapse
NEVERMIND!!!!
Experimenting with several different USB cords and ports finally yielded a good connection! Even a native USB port on the back of the iMac didn't work, and neither did some of the ports on my USB 3.0 (2.0 compatible) hub. But finally one worked, and I ran with it. Currently reinstalling my apps on the shiny new Marshmallow system!
THANKS Mohsinkhan35!!!!!

Von Neumann said:
NEVERMIND!!!!
Experimenting with several different USB cords and ports finally yielded a good connection! Even a native USB port on the back of the iMac didn't work, and neither did some of the ports on my USB 3.0 (2.0 compatible) hub. But finally one worked, and I ran with it. Currently reinstalling my apps on the shiny new Marshmallow system!
THANKS Mohsinkhan35!!!!!
Click to expand...
Click to collapse
Sorry about the late reply Von I just saw your replies, I am glad that you got it to work!!
For Future purposes, The easiest way to update TWRP is to download the .img from TWRP, put it on your phone, go to TWRP recovery, and instead of flashing .zip file, choose .img from dropdown list, then select the image file, select recovery option from the list.
Enjoy your new system! Which MarshMallow ROM did you end up flashing?
I found that MM breathe a new life into my Nexus, can't imagine going back to Lollipop, I don't know how you managed to stay with KitKat haha

J500FN rapidly running out of space

As a bog standard user I naively assumed that I could put apps on my SD card as and when I wanted. Instead the majority refuse to be put there or cause problems.
If I root my Samsung J500fn (Marshmallow) will I be able to chose the location for putting apps? Can I get rid totally of the stuff Google/Samsung think I need but I never use? Can I make better use of my SD card that is practically empty? Are there any drawbacks to keeping Marshmallow as installed or would rooting overwrite it? Is there a better way than to root? Is "One Click root" safe to use? Am I better of using various programs like Odin, TWRP etc. mentioned in various threads here?
Thanks to any and all who can answer my questions. :fingers-crossed:
Anne

webelan said:
As a bog standard user I naively assumed that I could put apps on my SD card as and when I wanted. Instead the majority refuse to be put there or cause problems.
If I root my Samsung J500fn (Marshmallow) will I be able to chose the location for putting apps? Can I get rid totally of the stuff Google/Samsung think I need but I never use? Can I make better use of my SD card that is practically empty? Are there any drawbacks to keeping Marshmallow as installed or would rooting overwrite it? Is there a better way than to root? Is "One Click root" safe to use? Am I better of using various programs like Odin, TWRP etc. mentioned in various threads here?
Thanks to any and all who can answer my questions. :fingers-crossed:
Anne
Click to expand...
Click to collapse
Hi Anne,
We all have the same trouble with storage on our J5.
If you chose to root your phone then yes you will be able to uninstall alot of the bloat ware that is on your phone.
You will also have the option of using adaptable storage.
There are lots of threads on here that will guide you through the process. Just make sure that you read the guides properly and download and install the CORRECT zips.
I don't know if the one click root is safe to use.
I would advice installing TWRP and then flashing super su. Again all of the guides are on here.
If you do install TWRP via Odin then you will have the option of flashing custom ROMs..
Have a good look at the guides. Ask all the questions that you need to. People in here will be happy to help.
It's really nice to see you on here
Have fun
John

Don't need root for adoptable storage.

Hi
Did u get the info that you need ?

Rooting
johnhux7 said:
Hi
Did u get the info that you need ?
Click to expand...
Click to collapse
Hi again, thanks for asking.
I downloaded TWRP from https://www.androidfilehost.com/?w=files&flid=55922, version for SM-J500FN dated May 6, 2016. Also ODIN-v3.10.7 and SU SR4-SuperSU-v2.78-SR4-20161115184928 as well as the Samsung USB drivers. All check sums were fine. Odin 3 installed fine on my PC. I used Odin 3 to install the TWRP on my phone. However, when I try to go into Volume up - home - power on - I get a screen that does not resemble at all what I thought TWRP should look like.
I get the yellow/green Android thingy which says "installing system update" follows by "no command" followed by a screen which says:
Android Recovery
MMB29M.J500FNXXU1BPH1
samsung/j5nltexx/j5nlte
6.0.1/MMB29M/J500FNXXU1BPH1
user/release-keys
Use volume up/down and power. (all in yellow)
Followed by a menu which includes "apply update from SD card" but which doesn't install the SU zip file that I put in the download section of the SD card.
--------
So I am a bit lost and bewildered. Is the menu correct for TWRP? I haven't seen anything on the web or in YouTube that looks at all like what I'm getting. Did TWRP install properly - Odin 3 seemed to think so, but I'm beginning to wonder.
Any help, comment appreciated.
Anne

webelan said:
Hi again, thanks for asking.
I downloaded TWRP from https://www.androidfilehost.com/?w=files&flid=55922, version for SM-J500FN dated May 6, 2016. Also ODIN-v3.10.7 and SU SR4-SuperSU-v2.78-SR4-20161115184928 as well as the Samsung USB drivers. All check sums were fine. Odin 3 installed fine on my PC. I used Odin 3 to install the TWRP on my phone. However, when I try to go into Volume up - home - power on - I get a screen that does not resemble at all what I thought TWRP should look like.
I get the yellow/green Android thingy which says "installing system update" follows by "no command" followed by a screen which says:
Android Recovery
MMB29M.J500FNXXU1BPH1
samsung/j5nltexx/j5nlte
6.0.1/MMB29M/J500FNXXU1BPH1
user/release-keys
Use volume up/down and power. (all in yellow)
Followed by a menu which includes "apply update from SD card" but which doesn't install the SU zip file that I put in the download section of the SD card.
--------
So I am a bit lost and bewildered. Is the menu correct for TWRP? I haven't seen anything on the web or in YouTube that looks at all like what I'm getting. Did TWRP install properly - Odin 3 seemed to think so, but I'm beginning to wonder.
Any help, comment appreciated.
Anne
Click to expand...
Click to collapse
If your phone is looking like that then you have the wrong version of TWRP for the version of android that your using.
I did the same thing.
I hadn't got the time at the mo to find you the correct version but that is the problem for sure.
You want the one by Garnesh Varma which if on the Roms & kernels thread
John

johnhux7 said:
If your phone is looking like that then you have the wrong version of TWRP for the version of android that your using.
I did the same thing.
I hadn't got the time at the mo to find you the correct version but that is the problem for sure.
You want the one by Garnesh Varma which if on the Roms & kernels thread
John
Click to expand...
Click to collapse
Hi john,
Following your suggestion I downloaded the TWRP version http://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j500f-t3416960 by searching for Garnesh Varma. It successfully installed, but the problem remains the same. I do not get the TWRP recovery page just the same as before.
I shall continue to look to see if I can find another version from Garnesh, although it seemed correct ie SM-J500FN Android version 6.0.1 Build number MMB29M.J500FNXXU1BPH1, security patch level 1 August 2016.
Will let you know how I get on.
Thanks again,
Anne

webelan said:
Hi john,
Following your suggestion I downloaded the TWRP version http://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j500f-t3416960 by searching for Garnesh Varma. It successfully installed, but the problem remains the same. I do not get the TWRP recovery page just the same as before.
I shall continue to look to see if I can find another version from Garnesh, although it seemed correct ie SM-J500FN Android version 6.0.1 Build number MMB29M.J500FNXXU1BPH1, security patch level 1 August 2016.
Will let you know how I get on.
Thanks again,
Anne
Click to expand...
Click to collapse
Ahah! The trick was to turn off the phone and not to permit ODIN to do a reboot. I didn't know how to turn off so I pulled the battery. Then went into volume up - home - power on and got the correct menu. Whew. Rooted now according to root checker. Now to get some of the stuff off the phone and make some space.#
Thanks for your help,
Anne

webelan said:
Ahah! The trick was to turn off the phone and not to permit ODIN to do a reboot. I didn't know how to turn off so I pulled the battery. Then went into volume up - home - power on and got the correct menu. Whew. Rooted now according to root checker. Now to get some of the stuff off the phone and make some space.#
Thanks for your help,
Anne
Click to expand...
Click to collapse
Nice one. I'm pleased that you got it sorted !
Next you will be on the custom roms ! If you need any help just shout !
John

@webelan
Hello Anne!
Once you are rooted you can remove any Google/Samsung app. But removing some system apps can lead to bootloop. You can recover from bootloop by re-flashing stock rom.
I can make a flashable zip which removes unnecessary system apps, including the Google/Samsung apps which you want (you flash the zip in recovery and you're done). So let me know which Google/Samsung apps you wanna remove.
You can find some more basic informations in our Q&A thread: http://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-qa-thread-galaxy-j5-series-t3382922 .
I recommend you to try cm 12.1 (5.1.1 lollipop) by Nick Verse if you don't care about Samsung Camera, Memo and Browser. I use Open Camera, Color Note and Dolphin Browser (has sound/brightness sliders in videos) as alternatives. Unlike Touchwiz, CM 12.1 is faster than Touchwiz and has more free ram. But latest release has a bug (random reboot reported by users) which can be fixed manually. I'm running latest release without any problem.
Have a nice day!
Robert.
PS: You have a nice name

more woe
johnhux7 said:
Nice one. I'm pleased that you got it sorted !
Next you will be on the custom roms ! If you need any help just shout !
John
Click to expand...
Click to collapse
Don't know if I should start another thread but...
I used Aps2SD to create a second partition on my phone after making a backup of the SD card using that program. Restored the SD card and then I linked various apps to the new partition. When everything was done, and working, I used the option "Broken ap cleaner" just in case there were any residue files with "select all"
My error may have been to do a hard shutdown afterwards because now I get "Android System There's an internal problem with your device, and it may be unstable until you factory data reset." Then several aps, including a Google app, Photos, CM security and Gmail stop, in fact all those that run automatically at startup. Gmail and Google are on the internal drive now but were previously linked; CM is on the external partition still. The first thing after that I noticed after the hard shut down was that the icons for linked aps had disappeared and the aps keep stopping if I try to run them.
I read the Aps2SD FAQ and followed the two suggestions regard SU, ie "enable su at boot" and disabled "namespace separation" option.
Any suggestions? Should I
(a) do a "factory data reset"
(b) wipe the SD card and partition and completely reinstall the aps I want? Although if Google app is not working don't know if it can be reinstalled as I'm not sure which oneis meant.
(c) Bite the bullet and install a custom rom?
(d) something else?
Any help as usual very much appreciated,
Anne

webelan said:
Don't know if I should start another thread but...
I used Aps2SD to create a second partition on my phone after making a backup of the SD card using that program. Restored the SD card and then I linked various apps to the new partition. When everything was done, and working, I used the option "Broken ap cleaner" just in case there were any residue files with "select all"
My error may have been to do a hard shutdown afterwards because now I get "Android System There's an internal problem with your device, and it may be unstable until you factory data reset." Then several aps, including a Google app, Photos, CM security and Gmail stop, in fact all those that run automatically at startup. Gmail and Google are on the internal drive now but were previously linked; CM is on the external partition still. The first thing after that I noticed after the hard shut down was that the icons for linked aps had disappeared and the aps keep stopping if I try to run them.
I read the Aps2SD FAQ and followed the two suggestions regard SU, ie "enable su at boot" and disabled "namespace separation" option.
Any suggestions? Should I
(a) do a "factory data reset"
(b) wipe the SD card and partition and completely reinstall the aps I want? Although if Google app is not working don't know if it can be reinstalled as I'm not sure which oneis meant.
(c) Bite the bullet and install a custom rom?
(d) something else?
Any help as usual very much appreciated,
Anne
Click to expand...
Click to collapse
It sounds like the app has been corrupted, don't really know how to best advice you.
It sounds like you have to do s factory reset.
I would install a custom ROM.
The only trouble with this is that all the roms have just been shut down so you will have trouble downloading any.
Why model do you have ?
If you want to use a custom ROM pm me and I will send you a link.
The custom roms are much better (in my opinion )
John
Sent from my j5nltexx using XDA Labs

#Henkate said:
@webelan
Hello Anne!
Once you are rooted you can remove any Google/Samsung app. But removing some system apps can lead to bootloop. You can recover from bootloop by re-flashing stock rom.
I can make a flashable zip which removes unnecessary system apps, including the Google/Samsung apps which you want (you flash the zip in recovery and you're done). So let me know which Google/Samsung apps you wanna remove.
You can find some more basic informations in our Q&A thread: http://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-qa-thread-galaxy-j5-series-t3382922 .
I recommend you to try cm 12.1 (5.1.1 lollipop) by Nick Verse if you don't care about Samsung Camera, Memo and Browser. I use Open Camera, Color Note and Dolphin Browser (has sound/brightness sliders in videos) as alternatives. Unlike Touchwiz, CM 12.1 is faster than Touchwiz and has more free ram. But latest release has a bug (random reboot reported by users) which can be fixed manually. I'm running latest release without any problem.
Have a nice day!
Robert.
PS: You have a nice name
Click to expand...
Click to collapse
Hi Robert,
Thanks for the offer. So far I have not deleted anything but have used software to partition my SD card and to move stuff out of internal memory onto it - or rather link it. I managed to mess up a bit but seem to have recovered - or at least got a phone with items I want to use. Next week when I've more time I'm hoping to install a Custom ROM. In the meantime I've spent what little time available trying to read as much as I can so that when I do put a Custom ROM on, it goes right first time.
Best wishes,
Anne

webelan said:
Hi Robert,
Thanks for the offer. So far I have not deleted anything but have used software to partition my SD card and to move stuff out of internal memory onto it - or rather link it. I managed to mess up a bit but seem to have recovered - or at least got a phone with items I want to use. Next week when I've more time I'm hoping to install a Custom ROM. In the meantime I've spent what little time available trying to read as much as I can so that when I do put a Custom ROM on, it goes right first time.
Best wishes,
Anne
Click to expand...
Click to collapse
Hi Anne!
Note that once you flash TWRP, Knox will become 0x1 (initially is 0x0) which means that you void the warranty. In my opinion, I don't care about the warranty because I prefer to have a better experience with my phone. I cannot live without root after I rooted a phone for first time
Regarding the ROM, if you wanna try cm12.1 (which I recommend it, best ROM which is closest to AOSP and never lagged) I'll recommend you to wait some more time because I'll download CM 12.1 sources and build a new update with the help of Nick Verse . He doesn't have enough space on his PC to have both cm12 & cm13 sources. I'm currently trying to extend my Linux partition to have enough space to build though. Is needed about 80gb in total average and I have about 20 and can't resize my partition. I might try to reinstall Linux.
If you have any other question, feel free to ask here (new thread if it's related to something else) or PM me.
Have a nice day!
Robert.

Having a similar issue, i have got my phone so it boots to TWRP 3.1.1-0 but cannot find a ROM file that will install, they all seem to be for j5nlte, even if the file name states j5nltexx. I have tried to ammend/remove the assert lines in the install package to no avail...
any advice would be good
Thanks in advance
PB

ashyx said:
Don't need root for adoptable storage.
Click to expand...
Click to collapse
Then what to do

#Henkate said:
Hi Anne!
Note that once you flash TWRP, Knox will become 0x1 (initially is 0x0) which means that you void the warranty. In my opinion, I don't care about the warranty because I prefer to have a better experience with my phone. I cannot live without root after I rooted a phone for first time
Regarding the ROM, if you wanna try cm12.1 (which I recommend it, best ROM which is closest to AOSP and never lagged) I'll recommend you to wait some more time because I'll download CM 12.1 sources and build a new update with the help of Nick Verse . He doesn't have enough space on his PC to have both cm12 & cm13 sources. I'm currently trying to extend my Linux partition to have enough space to build though. Is needed about 80gb in total average and I have about 20 and can't resize my partition. I might try to reinstall Linux.
If you have any other question, feel free to ask here (new thread if it's related to something else) or PM me.
Have a nice day!
Robert.
Click to expand...
Click to collapse
Please work on camera that is the only thing cm 12.1 lackss thank youu

Newbie-friendly: TWRP and Root for Samsung S3 Tablet

Tested SM-T820, for Android O. It is reported that it works for Android P as well, with small modification (see below).
This post is designed to gather information found across this forum to give a step-by-step guide for obtaining a custom recovery TWRP and Root (via Magisk) for the Samsung S3 tablets running Android O. This process works if you are upgrading or staying with Oreo. [If you wish to run Android N, there is a slightly different process.] This process will wipe the contents of the tablet, so make backups as appropriate.
Credit to the software authors, original post creators (especially ashxy) and all those who contributed to the discussions to clarify all the issues. Most of the specifics below were hammered out in https://forum.xda-developers.com/ga...recovery-twrp-3-1-0-1-samsung-galaxy-t3581359.
WARNING Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on. You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering. [credit: jcadduono]
The below instructions are for Android O (Oreo). User BenG7 reports (I have not verified) that the same process, with slight modification, will work for Android P (Pie). See posts #38 and #39 for those modified instructions.
1. DOWNLOAD
a. ODIN​https://samsungodin.com/ (I used 3.13.1)​b. Samsung USB Drivers​https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows​c. Original firmware​Search for SM-T820 and download latest version 8.X at http://updato.com/firmware-archive-select-model​d. TWRP​At some point, it will likely find an official version at https://twrp.me/Devices/. For now, grab the latest beta version at https://forum.xda-developers.com/ga...recovery-twrp-3-1-0-1-samsung-galaxy-t3581359​e. Magisk​Get the latest stable Magisk version from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445​f. Ashxy's oreo encryption disabler https://androidfilehost.com/?fid=890278863836288163​​
2. PREPERATION
a. While running your tablet in Android, go to Settings -> About device. Tap 7 times on Build number to enable Developer options. [credit: jcadduono]​b. Now go to Settings -> Developer options. You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on. Do not ever turn off Developer Options or OEM unlock. Doing so will cause your device to refuse to boot and require a full factory restore. [credit: jcadduono]​c. Turn off your tablet.​d. Get a micro SD card​e. Copy Magisk and oreo encryption disabler onto microSD card​f. Install microSD card into Tablet​g. Install Samsung USB Drivers on Windows machine​h. Unzip ODIN (1a) and Original firmware (1c) on your Windows computer​i. While tablet is off, plug in usb cable between tablet and Windows computer​​3. REFLASH ORIGINAL FIRMWARE (Optional if your tablet is already running Oreo)
a. Enter Download mode, press and hold Home, Down Vol, and Power until you see the Warning screen of the downloader mode. Press Vol up to continue​b. Open up ODIN, confirm that ODIN can see your tablet. We will fill in three files for flashing. Click AP button on Odin. In popup, select AP_[blah blah].tar.md5 (whatever AP file you downloaded in step 1c). After selecting the file, Odin will check the signature of the file you downloaded and appear to freeze up. Let it finish, and it will report: <OSM> Checking MD5 finished Sucessfully.. <OSM> Leave CS.. In a similar way, fill in the BL and the CSC files. As these are much smaller, the signature checks will go much faster. [Use the CSC file, not the HOME_CSC file, in the CSC slot. This will completely erase your data on the tablet, which minimizes the likelihood of future problems. You will be erasing all of the /data partition later, so there is no point in saving your data now by using the HOME_CSC file.]​c. Make sure that in the options, Auto Reboot is selected. Then click Start. The screen of the tablet should show a progress bar as your tablet is being restored to its original firmware.​d. At this point, your tablet will reboot into the default recovery mode, with a full blue screen and an android figure with the spinning arrows. The tablet will then self reboot again (perhaps more than once). After a while, you will be greeted with the Welcome screen where you can select your language. Be patient.​e. Power off the tablet using the power button​​4. FLASH TWRP
a. Enter Download mode (press and hold Home, Down Vol, and Power) until you see the Warning screen of the downloader mode. Press Vol up to continue​b. (Re) Open up ODIN, confirm that ODIN can see your tablet,​c. Important We do not want the tablet to automatically reboot after installing TWRP. If the tablet does reboot into Android before completing the steps in Section 4 and 5, there is a good chance the stock recovery will overwrite TWRP. So click the Options tab on the left and deselect Auto Reboot. After doing that, click the Log tab so you can monitor progress​d. Click AP button on Odin. In popup, select twrp-[blah blah].img.tar (downloaded in step 1d), but make sure that the BL and CSC slots are unchecked, i.e. we will only be flashing an AP file this time. Then click Start. You will see the progress bar on your tablet. Watch the log window of Odin and wait for the message "<OSM> All threads completed. (succeed 1 / failed 0)"​​5. ENTER TWRP AND CONFIGURE
a. At this point, from the last section, you should still be in Download mode on the tablet. It is important that, after flashing TWRP, to go straight to TWRP without letting the Android System reboot. To do this, Hold [Volume Down] + [Home] + [Power] to get out of Download mode and immediately swap to [Volume Up] (while still holding [Home] + [Power]) when the screen blanks. [credit: jcadduono]​b. In a few secs, you will see the TWRP first screen, you can let go of all the buttons.​c. If you don't see then TWRP boot splash try again from the start of 4. FLASH TWRP.​d. Swipe to Allow Modifications. (For some reason, TWRP has some issues with the touchscreen for some tablets. If you experience this, expect to make several swipes or taps until it properly registers. You have succeeded when you see the classic 8-button main screen of TWRP.)​e. Click Wipe then Format Data (do not just Wipe data), type yes and let it complete. Then click back until you get to the 8-button main screen of TWRP.​f. Click the Mount button. Select Storage button, and confirm that the Internal Storage shows non-zero MB. If it is, you know that the /data partition is now mounted properly. However, since we put the needed install files on the microSD, go ahead and select Micro SD Card as our storage. Click Back until you are back at the 8-button main screen.​g. Click the Install button, install the Magisk zip file you downloaded in step 1e and copied to your microSD. Once finished, click Back to get back to the install screen (do not reboot yet).​h. Install the oreo encryption disabler zip file from step 1f. When it completes, you can press the Reboot System button and let your tablet reboot into Android. You can also disconnect the usb cable connecting the tablet from the computer. The tablet may reboot itself once or twice, let it do its thing, and eventually you will see the Samsung Welcome! Screen, where you can select your language.​​6. CONFIRM DATA ACCESS IN TWRP
a. Before going into configuring your tablet, go ahead and turn off the tablet and re-enter TWRP (Home, Vol up, Power).​b. *Important* Since you will not be changing your system partition, this time, when you get to the "Keep System Read only?" screen, click the Keep Read Only button.​c. In the 8-button screen of TWRP, click Mount, click Select Storage. Confirm that the Internal Storage is greater than zero MB. If it is, congratulations, you have TWRP installed with /data mounted.​d. Reboot to System​​7. FUTURE USE OF TWRP
a. Unless you are planning to make changes to the System, continue to choose the Read Only System when you return to TWRP.​B. [NOT YET TESTED]If you need to make changes to System, e.g. flash a new ROM, go back to Step 5 and install the ROM just before Step 5g​​
8. Click the Thanks button if my guide helped you.

Good guide. In 5, a, at least for the t-820 and if assume other variants, you can hold power, vol up, and home until it boots to recovery. You don't need to hold the keys to boot the bootloader and then quickly switch to the vol up. It's a little easier for me to do it that way.
Sent from my [device_name] using XDA-Developers Legacy app

Good guide and HNY!
klaberte said:
7. FUTURE USE OF TWRP
.....
B. [NOT YET TESTED]If you need to make changes to System, e.g. flash a new ROM, go back to Step 5 and install the ROM just before Step 5h
Click to expand...
Click to collapse
I would flash magisk *after* flashing a new ROM, i.e. install the ROM just before Step 5g.
Btw, I installed TWEAKED for T820 by @rorymc928 which comes already with encryption disabler.

Great guide!
But, anyway to install SuperSU instead of Magisk?

Frunktz said:
Great guide!
But, anyway to install SuperSU instead of Magisk?
Click to expand...
Click to collapse
I'd ask over here: https://forum.xda-developers.com/ga...recovery-twrp-3-1-0-1-samsung-galaxy-t3581359

klaberte said:
I'd ask over here: https://forum.xda-developers.com/ga...recovery-twrp-3-1-0-1-samsung-galaxy-t3581359
Click to expand...
Click to collapse
Already asked but it SEEMS not possible because SuperSu was discountinued. But somebody has successfully installed it on Oreo 8.

I am new to rooting my Tab s3 so pardon me if any of my questions are redundant. I will be following the directions from post "Newbie-friendly: TWRP and Root for Samsung S3 Tablet". Can someone please confirm the following for me before I root -
1. I am running on the most recent firmware T820XXU2BRL1, do I need to complete process #3 REFLASH ORIGINAL FIRMWARE?
2. After I complete root process will my Tab s3 automatically be set to recognize SD Card as internal storage or will I need to complete another setting or process? This is my main reason to rooting.
3. Second reason is to remove bloatware. Does anyone know of a post advising which bloatware on Tab s3 to remove safely and which ones to leave alone?
4. After completing root process following directions from post "Newbie-friendly: TWRP and Root for Samsung S3 Tablet" has anyone experienced any Tab s3 functions or app not working properly? Is USB-OTG working?

my Tab S3 delivered today and followed ur guide and did in first try! send Thanks!

Great post. Im having an issue. With my tab s3. Yesterday i was updating magisk manager and after i did it stopped charging. I thought my charger came unplugged but it didnt. Now the only way i can charge it is to put it in twrp and let it charge. But its unresponsive when its powered on and when its off it just loops the charging screen. But wont charge. I jave tried to revert back to a previous back up but had no luck. I was plannig on flashing stock firmware when i get back to my computer.. but any input would be greatly appreciated..
Sent from my SM-N960U using Tapatalk

cdeitrich00 said:
Great post. Im having an issue. With my tab s3. Yesterday i was updating magisk manager and after i did it stopped charging. I thought my charger came unplugged but it didnt. Now the only way i can charge it is to put it in twrp and let it charge. But its unresponsive when its powered on and when its off it just loops the charging screen. But wont charge. I jave tried to revert back to a previous back up but had no luck. I was plannig on flashing stock firmware when i get back to my computer.. but any input would be greatly appreciated..
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
I don't know why your tab won't charge. Updating magisk should be totally unrelated to charging. Did you have any magisk modules that would have modified charging parameters?

jd1639 said:
I don't know why your tab won't charge. Updating magisk should be totally unrelated to charging. Did you have any magisk modules that would have modified charging parameters?
Click to expand...
Click to collapse
I had the sony framework module installed for ps4 remote play. But that was it. I cant figure it out.
Sent from my SM-N960U using Tapatalk

jd1639 said:
I don't know why your tab won't charge. Updating magisk should be totally unrelated to charging. Did you have any magisk modules that would have modified charging parameters?
Click to expand...
Click to collapse
https://r.tapatalk.com/shareLink?ur...share_tid=3641443&share_fid=3793&share_type=t
This was my issue. I love this forum.
Sent from my SM-N960U using Tapatalk

Quick question. I'm already on the latest firmware, my bootloader is unlocked so can I just run Odin, flash twrp and then any pre-rooted Rom? Or do I need to follow all these steps? It's been awhile since I've flashed anything and just want to make its done properly. TIA

after rooting, the secure folder works or not

jawalexander said:
after rooting, the secure folder works or not
Click to expand...
Click to collapse
That's correct.

Is that the only drawback?

On reboot I got: Verification Failed, Unable to restart your device. The Integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data.
Now what?
UPDATE: Oh I see, I totally skipped e. "Click Wipe then Format Data". Now it's fixed and working properly. Now to remove some bloatware.
David C.

I posted something silly before. Deleted.

THANKS ! Works also for Android PIE
Hi,
thanks,
I did a clean install of Android Pie for my Samsung Galaxy Tab S3, SM-T825.
Altough not yet officially available for my country, I downloaded the version for the Netherlands (PHN-T825XXU3CSH9-20190909091851) from the SamFrew-site [https://samfrew.com/nl/download/Galaxy__Tab__S3__/evss/PHN/T825XXU3CSH9/T825PHN3CSH8/[/URL] . As one can anyway customize languages, etc., no problem.
Then I followed your guide step by step.
I added BusyBox, latest version from XDA developers []https://forum.xda-developers.com/showthread.php?t=1929852 as last step, in 5. g
Altough written for OREO, all this steps work perfectly well on my Android PIE !
Including the use of the Ashxy's oreo encryption disabler of point 1.f
(I didn't find a similar disabler for Android Pie yet... Someone a better idea ?)
Rootchecker confirms that I have Root access and that BusyBox is indeed installed.
Thanks very much - great help !
baudi

baudi said:
Hi,
thanks,
I did a clean install of Android Pie for my Samsung Galaxy Tab S3, SM-T825.
Altough not yet officially available for my country, I downloaded the version for the Netherlands (PHN-T825XXU3CSH9-20190909091851) from the SamFrew-site [https://samfrew.com/nl/download/Galaxy__Tab__S3__/evss/PHN/T825XXU3CSH9/T825PHN3CSH8/[/URL] . As one can anyway customize languages, etc., no problem.
Then I followed your guide step by step.
I added BusyBox, latest version from XDA developers []https://forum.xda-developers.com/showthread.php?t=1929852 as last step, in 5. g
Altough written for OREO, all this steps work perfectly well on my Android PIE !
Including the use of the Ashxy's oreo encryption disabler of point 1.f
(I didn't find a similar disabler for Android Pie yet... Someone a better idea ?)
Rootchecker confirms that I have Root access and that BusyBox is indeed installed.
Thanks very much - great help !
baudi
Click to expand...
Click to collapse
Thanks for the update! Just wondering, why did you add busybox and XDA developers at the end of step 5g? XDA developers could have been installed as a standard app once the tablet is up and running, no?
Why manually installing BusyBox at this point of the setup?

Hi all. I'm new to rooting can any one please help and point me to the right tutorial to root a samsung s7

Hi All
Looking for a best tutorial to follow and the right one for my phone really don't want to brick it, obviously :/. as there seems to be a few versions for the S7
I have the following: S7 android 8.0.0 SM-G930F not sure what else I need to know! I'm in the UK so I assume UK phones come with Exynos cpu's
and as far as I am aware android 8 is Oreo! but when they say Stock Rom I assume they mean the same as what came with the phone the original rom?
if so is there an alternative stable rom without the crap included or is it just as simple to delete every thing you don't want now it's rooted! and does that mean if I reset the phone its back to normal with all the crap included! or is there a way to keep it rooted even after reset! and should anything be disabled I.e prepare the phone before attempting to root like any kind of auto encryption that needs disabling and just one more question
if at anytime the rooting process hangs for a ridiculous amount of time when should I throw in the towel! and what are the chances of retrieving the phone back to original state! or does a dirty shutdown brick it?.
I started the root process but failed at first hurdle!, followed instructions install Odin3_v3.13.1 but when I connected the phone nothing showed up in Odin? though I will have another go just to confirm I followed it correctly, I'll update this when it's done.
this was the tutorial I followed:
Easy 4 Newbie [Root Guide]SM-G930F, G935F, G930FD, G935FD (Samsung Galaxy S7 Edge)
Warning ! Please note that the official TWRP for Nougat on Galaxy S7/ S7 Edge is not available yet but based on my experience the Marshmallow version is working on Nougat. By installing a custom recovery on your S7 and S7 Edge and rooting it...
forum.xda-developers.com
I know alot of questions I would really appreciate any help and clarification on the above.
many thanks
Regards
Daz

Look pal, rooting the phone is just like being an adult, it means you will get rid of Samsung's "Child Care".
Yes, UK models use Exynos chip, but you have to be sure, look at your baseband version, if it is G930FXXX, then you are good.
ROMs are in two shapes:
Stock-based: These are just like the one you are using, or other Samsung phones does, like Samsung Experience, One UI, TouchWiz. Maybe MIUI and FlymeOS will come into account, as there are ROMs based on them + Samsung's.
AOSP: These are pure Android ROMs, with few modifications to the core, but keeping the UI as close to the source as possible, Google & OnePlus phones come with a near-to-pure operating systems.
Changing a ROM is not risky, as long as you follow the instructions, without any unaccounted improvising.
Before you install a ROM, read the working and bug list, to make sure you are installing something you have an idea of.
You need to install TWRP recovery (or any other one you like), and format data, in order to be able to travel among ROMs and/or root your device.
Formatting is only required because the phone is forcibly encrypted, and TWRP can not decrypt it, at least not for this device.
Rooting is simply about flashing a 5-MB file, Magisk, then rebooting to system, no need to wipe data.
No need to do any additional steps, unless you are trying to hide root from some apps and/or pass SafetyNet.

Mohamedkam000 said:
Look pal, rooting the phone is just like being an adult, it means you will get rid of Samsung's "Child Care".
Yes, UK models use Exynos chip, but you have to be sure, look at your baseband version, if it is G930FXXX, then you are good.
ROMs are in two shapes:
Stock-based: These are just like the one you are using, or other Samsung phones does, like Samsung Experience, One UI, TouchWiz. Maybe MIUI and FlymeOS will come into account, as there are ROMs based on them + Samsung's.
AOSP: These are pure Android ROMs, with few modifications to the core, but keeping the UI as close to the source as possible, Google & OnePlus phones come with a near-to-pure operating systems.
Changing a ROM is not risky, as long as you follow the instructions, without any unaccounted improvising.
Before you install a ROM, read the working and bug list, to make sure you are installing something you have an idea of.
You need to install TWRP recovery (or any other one you like), and format data, in order to be able to travel among ROMs and/or root your device.
Formatting is only required because the phone is forcibly encrypted, and TWRP can not decrypt it, at least not for this device.
Rooting is simply about flashing a 5-MB file, Magisk, then rebooting to system, no need to wipe data.
No need to do any additional steps, unless you are trying to hide root from some apps and/or pass SafetyNet.
Click to expand...
Click to collapse
Hi Mohamedkam000
Thanks for replying. I'm not confused about why I want to root the phone. I'm just trying to understand the inner workings and the risks as I'm not as clued up with phone OS's as I am windows. I don't care about warrantees or hiding the the fact it's rooted I just want a clean rooted phone free of big brother well inside at least I know you will never completely keep them out but making it hard is a start lol.
Thank you very much for all the above especially on clarifying about the roms and the reason TWRP formats due to encryption nice one
My Baseband version slightly different though it's G930FXXU8ETI3 not sure if having a U instead of a third X makes any difference!
and I posted wrong tutorial I'm actually following this one below again not sure if that matters.
Guide How to root Android 8.0 Oreo Stock ROM on Galaxy S7 ( 100% Working )
Hi . i see too many peoples have problem on rooting Android 8.0 Oreo Stock Rom on Galaxy S7 ( edge ) and they cant get passed from the verification field error ! ok its bcuz they do only 1 step wrong , here i just wanna tell you all the steps 1...
forum.xda-developers.com
Again many thanks for clarifying that lot up very informative and much appreciated.
Kind regards
Daz

CitizenSmith said:
Hi Mohamedkam000
Thanks for replying. I'm not confused about why I want to root the phone. I'm just trying to understand the inner workings and the risks as I'm not as clued up with phone OS's as I am windows. I don't care about warrantees or hiding the the fact it's rooted I just want a clean rooted phone free of big brother well inside at least I know you will never completely keep them out but making it hard is a start lol.
Thank you very much for all the above especially on clarifying about the roms and the reason TWRP formats due to encryption nice one
My Baseband version slightly different though it's G930FXXU8ETI3 not sure if having a U instead of a third X makes any difference!
and I posted wrong tutorial I'm actually following this one below again not sure if that matters.
Guide How to root Android 8.0 Oreo Stock ROM on Galaxy S7 ( 100% Working )
Hi . i see too many peoples have problem on rooting Android 8.0 Oreo Stock Rom on Galaxy S7 ( edge ) and they cant get passed from the verification field error ! ok its bcuz they do only 1 step wrong , here i just wanna tell you all the steps 1...
forum.xda-developers.com
Again many thanks for clarifying that lot up very informative and much appreciated.
Kind regards
Daz
Click to expand...
Click to collapse
It doesn't matter which version of Android you are using, root is the same.
However, on stock ROMs, it might sometimes get rough, as you may end up with Wi-Fi not working (happened to me Q1 2020).
If you really want to learn how Android OS works, then rooting the stock ROM is not your way.
Try AOSP ROMs, preferably start with Oreo ones, you can root in 3 common way, LineageOS SU Add-on, Magisk, Super SU.
But before you tickle your phone, you have to make a backup of your current device, of every partition, EFS is the most important partition, so make sure it is safe.
Baseband version doesn't matter a lot, unless you're paranoid with updates, it is sorted alphabetically, each string on its own.
The phone is more similar to a linux machine than to a Windows PC.
Edit: To root stock ROM, you have to flash dm verity, so you don't end up encrypted again.

Mohamedkam000 said:
It doesn't matter which version of Android you are using, root is the same.
However, on stock ROMs, it might sometimes get rough, as you may end up with Wi-Fi not working (happened to me Q1 2020).
If you really want to learn how Android OS works, then rooting the stock ROM is not your way.
Try AOSP ROMs, preferably start with Oreo ones, you can root in 3 common way, LineageOS SU Add-on, Magisk, Super SU.
But before you tickle your phone, you have to make a backup of your current device, of every partition, EFS is the most important partition, so make sure it is safe.
Baseband version doesn't matter a lot, unless you're paranoid with updates, it is sorted alphabetically, each string on its own.
The phone is more similar to a linux machine than to a Windows PC.
Edit: To root stock ROM, you have to flash dm verity, so you don't end up encrypted again.
Click to expand...
Click to collapse
Thanks again for clearing quite a few things up I thought rooting stock rom would have been far safer way forward wow how wrong was I! but I guess I am just trying to find any kind simile to windows in any way but as you pointed out again it's more like Linux which again I've only played around with ubuntu and mint for a short period so again not to up on Linux lol.
It's funny I was just reading up on AOSP ROMs then got your message. I see they have a stable but not complete! Android 10 not that I would consider it need as I need a stable OS so Oreo is fine for me.
I have backed up phone using Smart Switch on the PC I assume that copy's every thing that's needed, I reset the phone in anticipation all be it prematurely but at least it restored all my data so if anything that was a good test of the back up at least .
I will have look at some AOSP ROMs and see what's involved there, I'll check out their tutorial hopefully it will include the whole process including root.
I gather by your comment using a AOSP ROM you don't need to use dm-verity or will that still be needed!.

The first thing to do is to flash (install) TWRP, it's a custom recovery (think of it as a mini OS that can boot before Android), that will be the base for any of your future tinkering.
Here is the thread, read the FP carefully: [Recovery][Exynos] Official TWRP for Galaxy S7 (herolte)
Once TWRP installed, you can do many things:
Install addons like Magisk. Magisk is the tool you use to obtain root. Forget SuperSU, its outdated, and don't works in modern versions of Android.
Install a custom ROM (this subforum is the perfect place to find them).
Backup & restore an image of your current ROM (very useful).

mooms said:
The first thing to do is to flash (install) TWRP, it's a custom recovery (think of it as a mini OS that can boot before Android), that will be the base for any of your future tinkering.
Here is the thread, read the FP carefully: [Recovery][Exynos] Official TWRP for Galaxy S7 (herolte)
Once TWRP installed, you can do many things:
Install addons like Magisk. Magisk is the tool you use to obtain root. Forget SuperSU, its outdated, and don't works in modern versions of Android.
Install a custom ROM (this subforum is the perfect place to find them).
Backup & restore an image of your current ROM (very useful).
Click to expand...
Click to collapse
Thanks Mooms for the input
I tried to follow your links tutorial which he gives three options only one is any good to me and that was installing twrp using Odin but I'm having issues at every turn!. I can't even get Odin to recognise my phone it just wont pick it up I have Samsung driver installed and I have reinstalled many times I found an article claim to have a workaround but that was BS just selling some other app I even change the driver as described on there page,
7 Tips to Fix Odin Not Detecting Phone
Are you using Odin flash tool to flash your Samsung phone but it is not recognized by Odin? Here are 7 tips to fix Odin not detecting phone.
www.imyfone.com
.
but that did nothing so reinstall normal driver again.
feels like it's just not meant to be :/
Thanks again.

CitizenSmith said:
Thanks again for clearing quite a few things up I thought rooting stock rom would have been far safer way forward wow how wrong was I! but I guess I am just trying to find any kind simile to windows in any way but as you pointed out again it's more like Linux which again I've only played around with ubuntu and mint for a short period so again not to up on Linux lol.
It's funny I was just reading up on AOSP ROMs then got your message. I see they have a stable but not complete! Android 10 not that I would consider it need as I need a stable OS so Oreo is fine for me.
I have backed up phone using Smart Switch on the PC I assume that copy's every thing that's needed, I reset the phone in anticipation all be it prematurely but at least it restored all my data so if anything that was a good test of the back up at least .
I will have look at some AOSP ROMs and see what's involved there, I'll check out their tutorial hopefully it will include the whole process including root.
I gather by your comment using a AOSP ROM you don't need to use dm-verity or will that still be needed!.
Click to expand...
Click to collapse
AOSP ROMs are pure, you can't say they are not complete. They are complete, and what OEMs do, like Samsung and Xiaomi is just a customization that you can do, too.
It is preferred that when you take a backup, take it with TWRP, just to ensure you backed up phone's partitions, along with "EFS".
The root procedure on Android 6+ is done by patching the Kernel (boot.img), so unless you take backup of that, you cannot keep root.
There are stable custom ROMs, custom ROMs are meant for custom adjustments, however the stability depends on your phone, and the way you use it, you can compare AOSP vs. Stock and see the difference.
AOSP ROMs doesn't need dm verity, well, at least not if the developer did not mention the encryption part.

Mohamedkam000 said:
AOSP ROMs are pure, you can't say they are not complete. They are complete, and what OEMs do, like Samsung and Xiaomi is just a customization that you can do, too.
It is preferred that when you take a backup, take it with TWRP, just to ensure you backed up phone's partitions, along with "EFS".
The root procedure on Android 6+ is done by patching the Kernel (boot.img), so unless you take backup of that, you cannot keep root.
There are stable custom ROMs, custom ROMs are meant for custom adjustments, however the stability depends on your phone, and the way you use it, you can compare AOSP vs. Stock and see the difference.
AOSP ROMs doesn't need dm verity, well, at least not if the developer did not mention the encryption part.
Click to expand...
Click to collapse
Some of the roms I have looked at mention external touch buttons at bottom of phone do not work or something else in the phone I'm just reading their comments.
I understand about the stock & custom rom's now that's not my problem at least not at the moment as I am miles away from choosing a rom! as I can't even get out the starting gate!. I can not get TWRP on my phone as the only way I can see to get it on a unrooted! phone is to use Odin but as I said Odin doesn't work at least not for me it does not see my phone. I would love to take a back up using twrp but that won't happen until I find a way to get TWRP on a unrooted phone. what crazy paradox is this!. you can't root phone without twrp installed and twrp won't install on a unrooted phone!. that makes perfect sense.

CitizenSmith said:
Some of the roms I have looked at mention external touch buttons at bottom of phone do not work or something else in the phone I'm just reading their comments.
I understand about the stock & custom rom's now that's not my problem at least not at the moment as I am miles away from choosing a rom! as I can't even get out the starting gate!. I can not get TWRP on my phone as the only way I can see to get it on a unrooted! phone is to use Odin but as I said Odin doesn't work at least not for me it does not see my phone. I would love to take a back up using twrp but that won't happen until I find a way to get TWRP on a unrooted phone. what crazy paradox is this!. you can't root phone without twrp installed and twrp won't install on a unrooted phone!. that makes perfect sense.
Click to expand...
Click to collapse
Does your phone allow MTP communication? I mean can you transfer files when the phone is turned on?
Does the phone show any notification about a usb connection?
If not, then you have probably a bad USB cable, at least, or you have a hardware issue that can go as deep as a burned charging port.
If yes, then either your USB cable is not as fast as the phone requires, or you haven't installed the Samsung USB Drivers on your PC.
Unfortunately, you cannot root your device without PC, at least not since Lollipop.

CitizenSmith said:
Thanks Mooms for the input
I tried to follow your links tutorial which he gives three options only one is any good to me and that was installing twrp using Odin but I'm having issues at every turn!. I can't even get Odin to recognise my phone it just wont pick it up I have Samsung driver installed and I have reinstalled many times I found an article claim to have a workaround but that was BS just selling some other app I even change the driver as described on there page,
7 Tips to Fix Odin Not Detecting Phone
Are you using Odin flash tool to flash your Samsung phone but it is not recognized by Odin? Here are 7 tips to fix Odin not detecting phone.
www.imyfone.com
.
but that did nothing so reinstall normal driver again.
feels like it's just not meant to be :/
Thanks again.
Click to expand...
Click to collapse
Which version of Odin are you using ?
Use this version (latest): Odin v3.14.4
Which version of the Samsung USB drivers are you using ?
Use this version (latest): https://developer.samsung.com/mobile/android-usb-driver.html

Mohamedkam000 said:
Does your phone allow MTP communication? I mean can you transfer files when the phone is turned on?
Does the phone show any notification about a usb connection?
If not, then you have probably a bad USB cable, at least, or you have a hardware issue that can go as deep as a burned charging port.
If yes, then either your USB cable is not as fast as the phone requires, or you haven't installed the Samsung USB Drivers on your PC.
Unfortunately, you cannot root your device without PC, at least not since Lollipop.
Click to expand...
Click to collapse
Hi
Yes I can transfer files.
Yes phone asks to allow or block file transfer and it ohone shows up in Devices and Drives list and I can access the phone directory and shows up as Samsung s7 icon.
I will try another USB lead but the one I'm using is new and wasn't cheap but still a possibility I have had leads that weren't suitable for other things I was trying so it is worth a try.
Thanks

mooms said:
Which version of Odin are you using ?
Use this version (latest): Odin v3.14.4
Which version of the Samsung USB drivers are you using ?
Use this version (latest): https://developer.samsung.com/mobile/android-usb-driver.html
Click to expand...
Click to collapse
When I downloaded Odin this was latest one Odin3_v3.13.1 though I have doubts that one version update will fix this issue as I did not see many if any people having my issue so they all used Odin and I believe theirs are fine even with older versions! but as I said Mohamedkam it's worth a try I will down load that version and give it a try.
As for the Samsung usb driver I believe that is where I got mine
SAMSUNG_USB_Driver_for_Mobile_Phones no version visible under properties on file version 1.7.23.0.
The USB connection seems to be fine I have uninstalled then re-download and reinstalled a couple of times.
I can transfer files no problem it shows up as Galaxy S7 Icon with card and phone drive inside.
I'll update shortly thank you.
Update:
I just went to try new Odin and whilst checking my phone have seen I have Offical TWRP app installed? I have no clue as to how that's got in there! as Odin did not show phone so I could select nothing!.
In the phone I open app and if i select backup existing recovery it opens and Select Folder tab and under that Selected Folder: /sdcard Filename: Recovery .img and at the bottom of screen Root access required.
I just hope it's installed correctly!. it is showing in playstore my apps as well just to confirm. if this is now installed what should I do next Now not sure what tutorial to start following.
I am just going to try the new odin and see if it picks up the phone back soon.

OK Seem that it now shows up in the new Odin. at least I think it has! in the log window I see this: <ID:0/004> Added!!
I didn't see that before.
Would be grateful if you could tell me how to proceed from here!

Correct, you don't need he latst version of Odin or the Samsung drivers, bit it was just to be sure.
You need to be in download mode, but before, you must have checked OEM unlock & USB debug in developer options (mandatory).
I've written a tutorial with images here (in French):
Samsung Galaxy S7 (edge) - Mangez un Oreo! [Topic Unique] - Page : 487 - Téléphone Android - Technologies Mobiles - FORUM HardWare.fr

mooms said:
Correct, you don't need he latst version of Odin or the Samsung drivers, bit it was just to be sure.
You need to be in download mode, but before, you must have checked OEM unlock & USB debug in developer options (mandatory).
I've written a tutorial with images here (in French):
Samsung Galaxy S7 (edge) - Mangez un Oreo! [Topic Unique] - Page : 487 - Téléphone Android - Technologies Mobiles - FORUM HardWare.fr
Click to expand...
Click to collapse
As I said the older version did not show any kind of data what's so ever and the phone was in download mode. phone displayed "Downloading" which I believe it says that even if it's not doing anything! so a tutorial explained. I think it must have installed the Official TWRP app even though phone did not show up in Odin everything was blank however when I installed the new version of Odin like you suggested it then showed up as <ID:0/004> Added!!. so your suggestion work thanks for that and I did enable OEM unlock & USB debug I did long time ago.
I would check out your tutorial but unfortunately I don't speak French and translating instructions is too risky but thank you for the offer but I'll carry on look around still undecided on what custom rom to go for as I said some comments point out small issues and the developers also state certain things are not working so that is making it hard to consider one if you know what I mean.
Again Thank you for your input very much appreciated.

CitizenSmith said:
As I said the older version did not show any kind of data what's so ever and the phone was in download mode. phone displayed "Downloading" which I believe it says that even if it's not doing anything! so a tutorial explained. I think it must have installed the Official TWRP app even though phone did not show up in Odin everything was blank however when I installed the new version of Odin like you suggested it then showed up as <ID:0/004> Added!!. so your suggestion work thanks for that and I did enable OEM unlock & USB debug I did long time ago.
I would check out your tutorial but unfortunately I don't speak French and translating instructions is too risky but thank you for the offer but I'll carry on look around still undecided on what custom rom to go for as I said some comments point out small issues and the developers also state certain things are not working so that is making it hard to consider one if you know what I mean.
Again Thank you for your input very much appreciated.
Click to expand...
Click to collapse
Take a note that, when you flash TWRP, you have to boot immediately to the recovery, so as to enforce its existence, cause I remember they phone has an original recovery backed up somewhere, and gets triggered when you reboot directly to system instead of the unofficial binary.
I advise you to watch guides on YouTube, it's more .. understandable.

CitizenSmith said:
still undecided on what custom rom to go for as I said some comments point out small issues and the developers also state certain things are not working so that is making it hard to consider one if you know what I mean.
Again Thank you for your input very much appreciated.
Click to expand...
Click to collapse
I recommend to go with ALEXNDR ROM: zero bugs, everything works perfectly (it's based on stock ROM).
[ROM][G930F/FD][ALEXNDR] * U8EUE1 * DevBase v7.4 * Encryption support [Jul-10]
Important notes for Developers / Chefs !!! This ROM is NOT based on any other custom ROM. My work contains many original ideas and innovations that I introduced as the first in the ROM development (see "Changelist" in post #2). Of course, it...
forum.xda-developers.com

Mohamedkam000 said:
Take a note that, when you flash TWRP, you have to boot immediately to the recovery, so as to enforce its existence, cause I remember they phone has an original recovery backed up somewhere, and gets triggered when you reboot directly to system instead of the unofficial binary.
I advise you to watch guides on YouTube, it's more .. understandable.
Click to expand...
Click to collapse
Yer I read that but I've ended up with TWRP installed and did not do that process because I was unaware it installed until it showed up.
As I said I'll just keep looking for now I know I'll find one that works for me from start to finish.
and I've been checking youtube but wouldn't want to use any links their providing but it may help familurise myself with the whole process if i watch enough of them.
Thanks again for your help.

mooms said:
I recommend to go with ALEXNDR ROM: zero bugs, everything works perfectly (it's based on stock ROM).
[ROM][G930F/FD][ALEXNDR] * U8EUE1 * DevBase v7.4 * Encryption support [Jul-10]
Important notes for Developers / Chefs !!! This ROM is NOT based on any other custom ROM. My work contains many original ideas and innovations that I introduced as the first in the ROM development (see "Changelist" in post #2). Of course, it...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi Mooms
I will check that out many thanks. I wonder if you could help me here. I am in the middle of the rooting process but have hit a snag. again!
I have now installed TWRP successfully then no-verity-opt-encrypt-3.1 all went fine and I'm at point of flashing Magisk but have an issue when I swipe to flash is gives me a error in red saying "invalid zip file format !"
I downloaded it from github here.
GitHub - topjohnwu/Magisk: The Magic Mask for Android
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
I click on "code" tab and then "download zip" and I placed that in a download folder on my sd card when I select it I get the above error any ideas as to why I am getting this am I downloaded the correct file?
thanks for any assistance you could give.