Rooting the G900A
*Note for Mods: if you could sticky this thread that would be great, I think its really helpful
NO THIS DOES NOT WORK ON THE G870A
Updated with even newer-er method on 03/04/2017
DISCLAIMER:
Code:
Your warranty is now void. I nor XDA is responsible for the effects this may have on your device or your life, whether that be bricking, loss of data, combustion, nuclear war, or the election of businessmen as President (wait what).
Remember, its not root that puts your device in danger, its how you use it.
If you don't know what a locked bootloader is, or think that Chainfire is a new video game, you shouldn't be here, go read a little about Android and the Galaxy S5 before continuing
So let's begin:
What You'll Need:
This *experimental* firmware: https://androidfilehost.com/?fid=745425885120704448 (Thanks @NavSad !)
The SuperSU APK, Towelroot, and FlashFire, all available from this zip: https://www.androidfilehost.com/?fid=673368273298935990 Mirror
This modified "from-noship" pre-rooted OF3: https://www.androidfilehost.com/?fid=673368273298933039
What To Do:
Step 1: Goin' Wayy Down
Use ODIN to flash the experimental firmware.
MASTER CAUTION: This will wipe ALL data on the device!! Backup your stuff before proceeding. I nor XDA is responsible for loss of your memes!
Simply flash the .TAR.MD5 file in the zip using the AP slot in ODIN, and then wait for the phone to boot (which is literally all of 10 seconds).
Step 2: Our Old Friend
After the OS is installed, go to the file manager and install Flashfire, SuperSU, and TowelRoot.
Run towelroot. Simply hit "make it ra1n" and 3 seconds later you'll have the root binaries installed.
Now open the SuperSU app and hit "new user", let it do its thing and then update the SU binaries (don't worry, its safe to reboot!)
At this point you've got root! Now, let's get back to the present!
Step 3: Back to the Future!
Open FlashFire, grant it root access, and flash the modified OF3 with these settings:
Mount /system read/write
A wipe isn't required, but it is recommended (if you do wipe, make sure to put that card B E F O R E the flash zip/ota card!)
Hit "flash", let it flash, reboot, and load.
Guess what? You're done! That's right, you've done all the steps!! Simpler than before, right?
The OLD Method:
This method is not recommended and is only here for historical purposes.
--TESTED WORKING ON BASEBAND G900AUCU4COI5, if ya don't have it, go get it!--
WARNING: THIS ROOT METHOD ONLY WORKS ON BASEBAND VERSION G900AUCU4COI5, IF YOU DON'T HAVE IT, GET IT IN POST #2!
ANOTHER WARNING: THIS IS A TEMP ROOT ONLY, REBOOTING WITHOUT FLASHING THE PREROOTED OF3 WILL RESULT IN A BOOTLOOP!!
Bootlooped? Flash the AP file in the OI5 repair ZIP to get going again. Flashing the AP slot ONLY will save your data
Here's some instructions to get you going:
STEP 1.
Install:
- Kingo ROOT v4.1.9
- KingRoot v4.8.1
- SuperSU
- SuperSUme v6.0
- FlashFire
- Any Root Checker app
STEP 2.
Disable these:
- WiFi
- Location
- NFC
- Sync
- Powersave mode of any kind
STEP 3.
- Open KingRoot
- It will say "root method available", click the blue root button, the process will fail ***THAT IS OKAY***
- Root using Kingo ROOT v4.1.9
It will also fail **THIS IS OKAY**, what this is doing is installing the binaries for KingRoot to hijack.
NOTE: Kingo ROOT must not show Install Recommended App below Android version.
If it does, you didn't disable the above toggles. Clear from Multi-Task and start this step over.
STEP 4.
- Open KingRoot v4.8.1
It should show you the Security Index page where you see the big blue numbers. Press the button saying Fix Now/Continue.
Let it run its course...
STEP 5.
- Uninstall SuperUser (installed by Kingo ROOT)
Just press and hold the app in the app drawer and drag to uninstall. Simple step.
STEP 6.
- Open Super-Sume
KingRoot should ask you for permissions. Allow it.
Tap the big blue button and let it run.
Congratulations, you've got temp root!
STEP 7.
- Use FlashFire to get on the PreRooted OF3 ROM (zip is in Post 3)
Flash Order:
- Wipe All (Wiping internal storage is recommended but not required).
- Select the pre-rooted OF3 zip
Upon selecting, an options screen pops up. Toggle Mount /system read/write.. Important..
Begin the flashing process.
* Why do I have to use KingRoot 4.81? KingRoot 4.82 and above blocks the use of Supersume.
Thanks @NavSad, @DejaVuAgain, and everyone else for their help and hard work!
COI5 Rollback Zip
Now that we have root, we're obviously gonna attempt a ROMing of the phone. But, sometimes (most of the time) this can go awry and leave you with a $4-600 paperweight.
Get the ODIN-flashable zip for G900AUCU4COI5 here: https://www.androidfilehost.com/?fid=24438995911970945
BOF3 Rollback Zip
Thanks @NavSad for finding and uploading an ODIN-flashable copy of STOCK OF3!
Get the ODIN-flashable zip for G900AUCU4BOF3 here: https://www.androidfilehost.com/?fid=529152257862696776
How to Roll Back
Step 0: Make sure you have the Samsung USB Drivers installed on your PC, if they are not installed get them here: http://org.downloadcenter.samsung.c...G_USB_Driver_for_Mobile_Phones_v1.5.45.00.exe
Step 1: Get ODIN 3.11.1 using this link: http://forum.xda-developers.com/attachment.php?attachmentid=3813736&d=1468609625
Step 2: Get the ODIN-flashable zip for G900AUCU4COI5 using the link above.
Step 3: Extract both zip files to a temporary location.
Step 4: Make sure your phone is at least 75% charged, then power it off and boot it into download mode with these steps:
Step 4a: Hold down the VOLUME DOWN, HOME, and POWER buttons.
Step 4b: The phone will boot with a warning that says "A custom OS can cause critical problems... blah blah blah", press the VOLUME UP button.
Step 5: Connect the phone to your PC and launch ODIN
Step 6: Put the appropriate .md5 files in their slots (the one beginning with BL goes in the BL slot, AP in AP, etc). When putting the AP and CP files in their slots the program will hang while it checks the md5 hash. DO NOT PANIC!! This is normal, give it a minute or two and it'll move along.
Step 7: Ensure all the right files are in their slots and click "Start" to begin flashing. WARNING: DO NOT unplug the USB cable during flashing. This can potentially result in a hardbrick! Ensure that your computer has an adequate power supply to prevent errors!Do NOT mess with the "Options" tab. These are for expert developers only and inappropriate use of them can result in a hardbrick!
Step 8: The phone will restart after the flash is complete, and the ODIN screen will light up green with "PASS" in bold lettering. It is now safe to unplug the USB cable. Just let the phone reboot and do its thing. It will hang at the AT&T logo for a bit. This is normal, but if it stays there for 30 minutes or more, pull the battery out and restart the device.
Do NOT attempt to flash a custom OS or earlier releases of Android! You will get an auth error (if flashing a custom OS) or and aboot fused 4 > binary X error (if flashing a previous version of Android).
Flashing ROMs
I have stayed up over 8 hours experimenting, bricked my device about 3 times, and probably lost a couple panoramas from New York to bring you guys this guide!
It is now possible to flash G900A ROMs from ANY BASEBAND VERSION!!!
This is a 2-step process, your phone will be flashed and wiped twice, so back up all of your data before proceeding. I'm not responsible for the loss of your memes because you didn't back up!
Part 1: Going back to good ol' 5.0
Guys, this step is MANDATORY!! If you don't do this step you could lose your root and/or SOFTBRICK!
In this part we'll be flashing your OS down to G900AUCU4BOF3, pre-rooted stock, using FlashFire by Chainfire.
Prerequisites:
Rooted using the guide above.
Download FlashFire from the Play Store
Download the G900A_OF3 pre-rooted stock ROM from here: https://www.androidfilehost.com/?fid=24052804347788226
Put said OF3 zip on your phone's external SD or internal storage.
Okay, time to flash!
Go to FlashFire, tap the "+", select "Flash Zip or OTA", find and select the OF3 zip, leave "auto-mount" unchecked.
Uncheck ALL EverRoot functions. The ROM is pre-rooted.
Set reboot setting to "Normal"
Tap the lightning bolt, tap OK
The device will flash and reboot, go to AT&T Splash for 1-2 minutes, and then completely reboot.
That's all of Part 1, pretty simple lol.
Part 2: Custom ROM time!
Prerequisites:
Install FlashFire from the Play Store
Download your custom, G900A ROM (in this example we are using Alliance 8, https://www.androidfilehost.com/?fid=23991606952596246
Put said ROM in your phone's storage (Internal Storage or External SD)
Time to flash!
Go to FlashFire, tap the "+", select "Flash Zip or OTA", find and select the ROM zip, leave "auto-mount" unchecked.
Uncheck ALL EverRoot functions.
**CRUCIAL** Tap the "+" again, select "Wipe", and check every box EXCEPT "Internal Storage", then tap OK.
Arrange the "Flash Zip" and "Wipe" cards so that "Wipe" is before "Flash", FlashFire likes to put it the other way around, and if you let it do so, you've got yourself a softbrick and have to ODIN back to OI5 and start all over.
Set reboot setting to "Normal"
Tap the lightning bolt, tap OK
The device will flash and reboot, it will stick at the splash screen anywhere from 2-8 minutes (mine stuck around 4).
That's it! You've got yourself a nice, shiny new ROM to use!
Please remember to leave a thanks if you found this guide useful! Enjoy being able to ROM like all the other S5 variants!
ROM Index
These ROMs should work using the guide above. To be put on this guide, the ROM must meet these requirements:
Be on the OC4/OF2/OF3 Kernel or Above
Be tested on an AT&T S5 by an xda user with screenshots of the About/Software Version, Home, Lock, and Notification screens.
Be flashable with Chainfire's FlashFire
To request that a ROM be added to this index, please post a reply in this thread and mention @AptLogic. Links to screenshots are required or you will be ignored (not trying to be mean, its part of the requirements)
ROMs Tested Working:
AllianceROM v8 G900A Port (OC7/OF2/OF3 Kernel, Android 5.0): http://forum.xda-developers.com/att.../rom-allianceromv8-lite-available-18-t3098527
TMS5 3.0 (OC7/OF2/OF3 Kernel, Android 5.0): http://forum.xda-developers.com/att-galaxy-s5/development/5-0-oc7-tms5-1-0-4-29-15-t3095987
Twi5ted Lollipop v7: http://forum.xda-developers.com/att-galaxy-s5/development/twi5ted-lollipop-v6-8-15-15-t3103694
Phoenix V11: https://www.androidfilehost.com/?fid=24421527759883972
Attention:
After you flash a ROM for another G900 variant, you have to replace the kernel via Odin. This is because the kernels that these ROMs come with don't work with our locked-down versions of Android. To replace the kernel, put your phone in download mode (Vol. Down + Home + Power) and flash the OC4 kernel in the AP slot in Odin.
In most of unofficial ROMs, you will have to manually install the Google Play services 10.0.84 and Google Play Store 7.3.07.K-all [0] [PR] 139935798. For that, download the .apk, transfer to your phone or SD card memory and install it via some file manager. Remember that you have to go into "Security" and enable "Unknown Sources" in your settings.
ROMs That SHOULD Work
These ROMs most likely work with the G900A, but are pending screenshots from a user to verify. Feel free to give em a try if you feel adventurous!
Again, if you would like to request that a ROM be added to the index, please post in this thread with appropriate links and screenshots, and mention @AptLogic in the post.
Glad you got kingroot working on yours to
---------- Post added at 10:44 PM ---------- Previous post was at 10:43 PM ----------
I ran kingroot 5 then super sume 6.0 afterwards no problems
---------- Post added at 10:46 PM ---------- Previous post was at 10:44 PM
---------- Post added at 10:52 PM ---------- Previous post was at 10:46 PM ----------
Not sure if i should but im an going to use flashfire to install phoenix rom, ill post and let you know how it goes.
lingo2012 said:
Glad you got kingroot working on yours to
---------- Post added at 10:44 PM ---------- Previous post was at 10:43 PM ----------
I ran kingroot 5 then super sume 6.0 afterwards no problems
---------- Post added at 10:46 PM ---------- Previous post was at 10:44 PM
Click to expand...
Click to collapse
Well it seems that with Kingroot 5 it doesn't let super sume run on most devices. I had a problem with using it with KR 5, so I had to do the whole downgrade thing.
I'm also gonna try Phoenix, just moving files off my device and I'll flash it
I heard they blocked super sume on the new kingroot
Will this method work on G900AUCS4CPA4?
No only OI5
brezulja said:
Will this method work on G900AUCS4CPA4?
Click to expand...
Click to collapse
You can try it on CPA4, we really don't know yet but if you can get as far as root you should be fine.
Go ahead and try it and tell us
Woow it worked but i cant install super user any help ?? work for my g900aucu4cpa2 after 5 tries thank you
hardwellmouad said:
Woow it worjed but i cant install super user any help ?? work for my g900aucu4cpa2 after 5 tries thank you
Click to expand...
Click to collapse
You need to use SuperSume to get SuperSU. You can get it from the Play Store for $3.99 (I think), or you can look for an APK on xda somewhere. You need to make sure you have Kingroot 4.81 or it will reject SuperSume and it won't run.
AptLogic said:
Kingroot now works on the Galaxy S5 Running OI5
DISCLAIMER:
Code:
I nor XDA is responsible for the effects this may have on your device or your life, whether that be bricking, loss of data, combustion, nuclear war, or the election of businessmen as President (wait what).
Remember, its not root that puts your device in danger, its how you use it.
--TESTED WORKING ON BASEBAND G900AUCU4COI5 AND BELOW--
Here's some instructions to get you going:
Install KingRoot 5 from http://kingroot.net
Now, this is where it gets weird: You have to keep running KingRoot until it works. It took someone 2 tries, took me 10 or 11. The phone will keep restarting but eventually you will have root!
After you are rooted: REMOVE KingRoot 5, and replace it with KingRoot 4.81 (found here: http://forum.xda-developers.com/devdb/project/dl/?id=17153
You have to do this to run Super-Sume without it hanging at the "Processing, please wait" part.
After installation, run the root again. Your phone should restart once and you will be rooted again (if it takes more than one try that's okay).
Get Super-Sume from the Play Store.
Run Super-Sume and bask in the joy of having SuperSU on your G900A
I hope to see an uptick in the development for this variant now. Maybe we'll finally get Nougat on it XD
Another Disclaimer: I did not personally find this out first. I'm just putting it in an easy to use guide so you don't have to go through about 12 pages of a different thread to find these instructions. Thanks to @lingo2012 for figuring out that Kingroot works.
Post replies saying which ROMs work with the ATT S5 so we can get a list going!
Click to expand...
Click to collapse
Can we get Safestrap working?
NavSad said:
Can we get Safestrap working?
Click to expand...
Click to collapse
I was just testing that. I managed to get Safestrap to work by just installing busybox and then safestrap. Unfortunately I bricked my device soon after trying to install Phoenix ROM and I'm waiting for it to restart XD (Update: Debricked successfully, PM me if you need the OI5 restore files )
If I do find a way to install a ROM, the instructions (as well as a list of compatible ROMs) will be put into Reply #3 in this thread.
If we could get one of those Nougat ROMs to work that would be AMAZING.
I stopped updating OF3 back when @muniz_ri was the one leading the charge. Is there a preferred method to OI5 (or PA2?) that will allow for trying out this root method while preserving the ability to get back to rooted OF3?
LuckyNumberHat said:
I stopped updating OF3 back when @muniz_ri was the one leading the charge. Is there a preferred method to OI5 (or PA2?) that will allow for trying out this root method while preserving the ability to get back to rooted OF3?
Click to expand...
Click to collapse
No, sorry. But if you're already rooted on OF3 you may as well just stay on it until we can figure out ROMing on phones with newer basebands.
Okay SO after THREE bricks (count em), I have come to the conclusion that ROMing this phone on Lollipop with Safestrap is NOT POSSIBLE.
At this point I'm going to invite @Chainfire to the party, maybe he can give us a helping hand. There is a possibility that we can use Flashfire. I'll probably try that next. I plan to be up pretty late working on this.
If anyone else wants to share input please do. Right now I'm trying to flash the Resurrection Remix 7.1 ROM.
Yeah i tried with flashfire but it just sat at the Galaxy S5 screen.
AptLogic said:
You can try it on CPA4, we really don't know yet but if you can get as far as root you should be fine.
Go ahead and try it and tell us
Click to expand...
Click to collapse
Is there any chance of bricking the phone if i try to root CPA4?
Can anyone help me with this? I am currently on CPA2 and I can run kingroot 5.0 and then uninstall it to run 4.8 and re root which works fine. Then I run Super-Sume and that works fine too it installs SuperSU but then SuperSU asks me to update which I do and it reboots after a successful attempt and I am no longer rooted. Has anyone had this issue?
Related
Hello everyone!
I am making this thread to explain how to achieve ROOT on G900F devices with "the famous May update" aka Base OE5.
DO NOT USE ON OTHER DEVICES THAN G900F (THE F MODEL, QUALCOMM 4G EUROPEAN DEVICE).
I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR PHONE, DATA, LOSS OF JOB BECAUSE OF FAILED ALARM APP AND SO ON!
YOUR WARRANTY IS NOW VOID AND YOUR KNOX COUNTER IS 0x1 FOREVER!
Many users are having issues getting it rooted and even I was trying many methods to root it and always ended up with bricked phone and corrupt data.
1) Back the hell up your device, this is extremely important as sometimes your data partition and apps will get corrupt. SmartSwitch is great tool for backing up made by Samsung.
* Disable reactivation lock in settings (I also disabled lockscreen fingerprints and account fingerprints just to be safe)
* Unlock Developer options by goint to About phone and dapping Build number 7 times.
* In Developer options turn on USB Debugging.
* Download latest SuperSU zip and put it in your phones storage (mandatory) - https://download.chainfire.eu/693/SuperSU/BETA-SuperSU-v2.44.zip
2) Go to https://dl.twrp.me/klte/ and download THE LATEST recovery - twrp-2.8.7.0-klte.img.tar (11.9MB in size). DO NOT EXTRACT IT AND MAKE SURE IT IS TAR FILE NOT IMG FILE!
3) Download ODIN 3.10.6 from trusted source, like this one - http://odin3.en.lo4d.com/download and extract it to desktop.
4) Start ODIN with admin rights, in AP section select downloaded recovery TAR file and make sure to un-check the AUTO REBOOT option (it will be in different tab in this new looking ODIN, look for it carefuly).
5) Reboot your phone in Download mode by holding VOLUME DOWN, HOME and POWER keys, press VOLUME UP when prompted to.
6) Connect your phone to computer and wait for drivers to be installed or install them manually. USE ORIGINAL USB CABLE.
7) When ODIN shows that your device is added, click START and wait untill it shows PASS.
8) When PASSed, hold VOLUME UP, HOME and POWER keys until it reboots to recovery and TWRP splash screen should appear.
9) When recovery booted, make a full backup of all partitions. (THIS IS EXTREMELY IMPORTANT)
10) Now choose INSTALL option and find the SuperSU package you put in the storage at sub-steps previously. Install it.
11) When zip with SuperSU is installed, click WIPE CACHE, DALVIK and confirm (MANDATORY, MAY CAUSE PROBLEMS WITHOUT)
12) Reboot your phone, wait for Android to optimise your apps and check ROOT status.
13) Start modding your phone and please hit the thansk button and report back if this method worked.
BOE5 roots with CF Auto Root just like all the other ROMs for me with the G900F
I think people narrowed it down to certain revisions of newer S5s, rather than just the ROM being the problem
*Detection* said:
BOE5 roots with CF Auto Root just like all the other ROMs for me with the G900F
I think people narrowed it down to certain revisions of newer S5s, rather than just the ROM being the problem
Click to expand...
Click to collapse
CF Auto ROOT bricked my device and also thousands of others, as I have seen in comments on this forum and other forums/sites.
My phones revision is new, its made in middle of this summer.
Most of the comments I've read about BOE5 not working with CF AR, are just that it fails, not that it bricked anything, but possible I suppose
But BOE5 is not the only issue, as the ROM you're running is the exact same one I was running, and I could root it fine - if it was BOE5, I'd have the same problem
Maybe a combination of BOE5 and new revision hardware
Hi,
for me this post was very useful. I tried several ways to root or install recovery but I was always stuck at the point where it tried to boot into recovery. I have this exact firmware (DBT as CSC) and unchecking reboot and then reboot without removing the battery into recovery using the 3 keys was the missing part.
I still got the error message when booting into recovery, but it passed through it and entered recovery (it did not get stuck into dark screen). After that I rooted with Chainfires ZIP.
Thanks Alot!...............rooted like breeze.........The most important part is Uncheck Auto Reboot and DONT PULL OFF battery insetad go recovery by using 3 buttons right after download completes.
thanks man!! It works for me
After i try a many methods, this worked!
:good::good::good:
TasEsmuEs said:
Hello everyone!
I am making this thread to explain how to achieve ROOT on G900F devices with "the famous May update" aka Base OE5.
DO NOT USE ON OTHER DEVICES THAN G900F (THE F MODEL, QUALCOMM 4G EUROPEAN DEVICE).
I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR PHONE, DATA, LOSS OF JOB BECAUSE OF FAILED ALARM APP AND SO ON!
YOUR WARRANTY IS NOW VOID AND YOUR KNOX COUNTER IS 0x1 FOREVER!
Many users are having issues getting it rooted and even I was trying many methods to root it and always ended up with bricked phone and corrupt data.
1) Back the hell up your device, this is extremely important as sometimes your data partition and apps will get corrupt. SmartSwitch is great tool for backing up made by Samsung.
* Disable reactivation lock in settings (I also disabled lockscreen fingerprints and account fingerprints just to be safe)
* Unlock Developer options by goint to About phone and dapping Build number 7 times.
* In Developer options turn on USB Debugging.
* Download latest SuperSU zip and put it in your phones storage (mandatory) - https://download.chainfire.eu/693/SuperSU/BETA-SuperSU-v2.44.zip
2) Go to https://dl.twrp.me/klte/ and download THE LATEST recovery - twrp-2.8.7.0-klte.img.tar (11.9MB in size). DO NOT EXTRACT IT AND MAKE SURE IT IS TAR FILE NOT IMG FILE!
3) Download ODIN 3.10.6 from trusted source, like this one - http://odin3.en.lo4d.com/download and extract it to desktop.
4) Start ODIN with admin rights, in AP section select downloaded recovery TAR file and make sure to un-check the AUTO REBOOT option (it will be in different tab in this new looking ODIN, look for it carefuly).
5) Reboot your phone in Download mode by holding VOLUME DOWN, HOME and POWER keys, press VOLUME UP when prompted to.
6) Connect your phone to computer and wait for drivers to be installed or install them manually. USE ORIGINAL USB CABLE.
7) When ODIN shows that your device is added, click START and wait untill it shows PASS.
8) When PASSed, hold VOLUME UP, HOME and POWER keys until it reboots to recovery and TWRP splash screen should appear.
9) When recovery booted, make a full backup of all partitions. (THIS IS EXTREMELY IMPORTANT)
10) Now choose INSTALL option and find the SuperSU package you put in the storage at sub-steps previously. Install it.
11) When zip with SuperSU is installed, click WIPE CACHE, DALVIK and confirm (MANDATORY, MAY CAUSE PROBLEMS WITHOUT)
12) Reboot your phone, wait for Android to optimise your apps and check ROOT status.
13) Start modding your phone and please hit the thansk button and report back if this method worked.
Click to expand...
Click to collapse
Thanks for the easiest way to root sg5
Works well for the first time on g900f BOE5
Hi
Just a post to thank you so much.
I was on my way to throw my phone on the wall cos simply flashing the CF AutoRoot was not enough.
You made my day, bro'
Hi,
Just rooted my Galaxy S5..... What a method...... Congrats to YOU BOSS..... I tried different methods available on the net but failed every time. Had to reinstall the rom as mobile got bricked, but today is my luckiest day..... THNX ONCE AGAIN
Thank you so much!
Have unbrick the G900F base BOI3 firmware afrer faulty rooted with CF-Auto and install SU. :good:
im so confused.... i have baseband version G900FXXU1BOH4 & Build number LRX21T.G900FXXU1BOH6 ? On a S5 SMG900F Uk Android 5.0, is this the correct version to use this guide & build (twrp 2.8.7.0 klte.img.tar, & this Tut with root G900F with OE5 base) im not a noob but dont like messing when it come to root, need to check all the boxes & double check again just incase. Anyone with experiance help please Thanks in advance people
Nevermind after waiting 10mins I just flashed now I'm fully rooted & running a custom rom
Sent from my SM-G900F using Tapatalk
deanr1977 said:
Nevermind after waiting 10mins I just flashed now I'm fully rooted & running a custom rom
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
Did you trip Knox? I have Baseband Ver. G900FXXU1BOH4, CP Ver. G900FXXU1BOH4 and CSC: G900FXFV1BOEH4 This is a South African unit but I'm in Australia and want to root and change my CSC.
cloneme said:
Did you trip Knox? I have Baseband Ver. G900FXXU1BOH4, CP Ver. G900FXXU1BOH4 and CSC: G900FXFV1BOEH4 This is a South African unit but I'm in Australia and want to root and change my CSC.
Click to expand...
Click to collapse
Yeah I think so, but I already tripped Knox I while back so I don't know & didn't check sorry mate
Sent from my SM-G900F using Tapatalk
Thanks for the reply, someone out there might know if knox is tripped or not.
Thanks a lot, after weeks of search and bricking the phone then unbricking I finally found this working guide. Worked like a charm!
install ok
Thx for this tuto
After a struggle to root again (update to OE5 base bande)
my GS5 i managed at least wih your tuto.
Galaxy S5 SM-G900F (french version)
I used:
twrp-2.8.7.0-klte.img.tar
odin 3.10.7
Super SU : BETA-SuperSU-v2.44.zip
after a rebbot Super SU has update through TWRP (my choice)
I installed Root Checker everything is OK
Thanks for this tuto, it's worked perfectly with BOJ1 base in my Galaxy S5 SM-G900F (spanish version)
I used:
twrp-2.8.7.0-klte.img.tar
odin 3.10.7
Super SU : STABLE-SuperSU-v2.46.zip
Work this on G900FXXU1POH1
Would this work on the SM-G900F??
Baseband = G900FXXU1POH1
Building = LRX21T.G900FXXU1POI1
Any Chance for Root on SM-N920R4?
I emailed Samsung for the kernel source code release and they sent me the link. If anyone can develop a root access it would be very much appreciated!!
Samsung has a link in their open source page
Check this link
i would ask upintheair for help on this one. once i get mine as well i will be requesting help as well.
i badly need root too
Totally. Sm-n920r4 is a great device though. Currently using it with a verizon sim. Wish i could get lte though, cant wait until theur lte roaming agreement takes hold
r00t
I got mine rooted.. It's not an official way, but I did manage to have root access..
Forgot to add device information screen..
I am curious to know how you managed to obtain root? Does it break things since it isn't an official way?
<Re-edit>
datoad said:
I got mine rooted.. It's not an official way, but I did manage to have root access..
Forgot to add device information screen..
Click to expand...
Click to collapse
Can you send the links for the recovery and the kernel? I'd like to test it out as well. Please and thank you!
Sent from my SM-N920R4 using Tapatalk
I'm working on the guide right now..
---------- Post added at 09:12 PM ---------- Previous post was at 09:11 PM ----------
Swyzzlestickz said:
I am curious to know how you managed to obtain root? Does it break things since it isn't an official way?
Click to expand...
Click to collapse
So far nothing is broken but I can't guarantee anything.. LOL
datoad said:
I'm working on the guide right now..
---------- Post added at 09:12 PM ---------- Previous post was at 09:11 PM ----------
So far nothing is broken but I can't guarantee anything.. LOL
Click to expand...
Click to collapse
Wouldn't boot if it had broken hardware or ruined the flash. Depending on the recovery until an official root is out we just can't flash ROMS. I just want to get root for now!
Sent from my SM-N920R4 using Tapatalk
How to Root US Cellular Note 5 (N920R4).
Disclaimer: I am not responsible for bricked devices, dead SD cards, or black holes. Your warranty is now VOID.
1. Gather your needed files.
Samsung Drivers -----> http://www.samsung.com/us/support/owners/product/SM-N920RZKEUSC
Beta SuperSU 2.49 -----> http://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
Odin V3.10.7 -----> http://dl.sammobile.com/Odin3_v3.10.7.zip
PhilZ Recovery -----> http://www.arter97.com/browse/exynos7420/kernel/5.0/n920tw8/arter97-recovery-n920tw8-5.0-philz_touch_6.59.0.tar.md5
SpaceX Kernel -----> https://www.androidfilehost.com/?fid=24052804347822657
EFS Backup Tool -----> http://forum.xda-developers.com/note5/orig-development/imei-efs-backup-tool-note-5-t3196256
2. Install the Samsung Drivers.
3. Unlock Flashing Capability ***IMPORTANT***
If you do not enable the following setting, you will brick your device!!!
Go to settings - About Device - Software Info - You will see "Build Number" - Tap repeatedly on build number to unlock developer options. You will now see Developer options in settings (just above about device).
Open Developer options and Enable OEM Unlock. Go ahead and enable USB Debugging as well.
4. Flash custom recovery.
TWRP has not been ported over as of yet to our model. The only option is PhilZ by arter97.
Use Odin V3.10.7 to flash the downloaded recovery.
Switch off your Note.
Get into download mode by pressing Vol Down+Power+Home until the download window pops up. Press Volume Up to continue to download mode. Connect your phone to the computer. Press the AP button in Odin and browse to the downloaded PhilZ Recovery.
MAKE SURE YOU DO NOT CHANGE ANY OPTIONS IN THE OPTION TAB! I have included a screenshot of how it looks unchanged.
Press the Start button and it will flash the recovery to your phone. After completion, Odin will automatically restart the phone. To get into recovery press Volume Up+Home+Power for a few seconds and you will get to the new recovery.
5. Flash Custom Kernel
Use the same instructions as step 3 but instead of the recovery you will now be selecting the SpaceX Kernel. Once again, do not change any settings in the options tab.
6. Now flash Beta SuperSU 2.49 from recovery.
7. MAKE AN EFS (IMEI) BACKUP.
Please take the time to thank the following people:
@dr.ketan for his original guide HERE.
@arter97 for his port of the PhilZ Touch Recovery HERE.
@mahn_IT for his SpaceX Kernel HERE.
datoad said:
How to Root US Cellular Note 5 (N920R4).
Disclaimer: I am not responsible for bricked devices, dead SD cards, or black holes. Your warranty is now VOID.
1. Gather your needed files.
Samsung Drivers -----> http://www.samsung.com/us/support/owners/product/SM-N920RZKEUSC
Beta SuperSU 2.49 -----> http://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
Odin V3.10.7 -----> http://dl.sammobile.com/Odin3_v3.10.7.zip
PhilZ Recovery -----> http://www.arter97.com/browse/exynos7420/kernel/5.0/n920tw8/arter97-recovery-n920tw8-5.0-philz_touch_6.59.0.tar.md5
SpaceX Kernel -----> https://www.androidfilehost.com/?fid=24052804347822657
EFS Backup Tool -----> http://forum.xda-developers.com/note5/orig-development/imei-efs-backup-tool-note-5-t3196256
2. Install the Samsung Drivers.
3. Unlock Flashing Capability ***IMPORTANT***
If you do not enable the following setting, you will brick your device!!!
Go to settings - About Device - Software Info - You will see "Build Number" - Tap repeatedly on build number to unlock developer options. You will now see Developer options in settings (just above about device).
Open Developer options and Enable OEM Unlock. Go ahead and enable USB Debugging as well.
4. Flash custom recovery.
TWRP has not been ported over as of yet to our model. The only option is PhilZ by arter97.
Use Odin V3.10.7 to flash the downloaded recovery.
Switch off your Note.
Get into download mode by pressing Vol Down+Power+Home until the download window pops up. Press Volume Up to continue to download mode. Connect your phone to the computer. Press the AP button in Odin and browse to the downloaded PhilZ Recovery.
MAKE SURE YOU DO NOT CHANGE ANY OPTIONS IN THE OPTION TAB! I have included a screenshot of how it looks unchanged.
Press the Start button and it will flash the recovery to your phone. After completion, Odin will automatically restart the phone. To get into recovery press Volume Up+Home+Power for a few seconds and you will get to the new recovery.
5. Flash Custom Kernel
Use the same instructions as step 3 but instead of the recovery you will now be selecting the SpaceX Kernel. Once again, do not change any settings in the options tab.
6. Now flash Beta SuperSU 2.49 from recovery.
7. MAKE AN EFS (IMEI) BACKUP.
Please take the time to thank the following people:
@dr.ketan for his original guide HERE.
@arter97 for his port of the PhilZ Touch Recovery HERE.
@mahn_IT for his SpaceX Kernel HERE.
Click to expand...
Click to collapse
Disregard - I was using odin 9 - went to 10 and it worked! Didnt think that would matter
Thanks guys, this worked for me as well! I was having some random reboots with the SpaceX N920P v0.1 kernel, but when I tried SpaceX N920R4 v0.1 it would hang on the US Cellular boot screen, and SpaceX N920R4 v.02 would boot but not detect the SIM card.
Last night I flashed Freeza's Beastmode Kernel for SM-N920P and so far I haven't had any reboots or stability issues. It seems to have better performance and battery life as well, but it might just be in my head.
I don't know if there are any negative side effects of using SM-N920P kernels on our SM-N920R4 phones so flash it at your own risk, but it's working great for me. I just wanted to share my experience since there doesn't seem to be a good place to find information on our devices yet.
mixedlemon said:
Thanks guys, this worked for me as well! I was having some random reboots with the SpaceX N920P v0.1 kernel, but when I tried SpaceX N920R4 v0.1 it would hang on the US Cellular boot screen, and SpaceX N920R4 v.02 would boot but not detect the SIM card.
Last night I flashed Freeza's Beastmode Kernel for SM-N920P and so far I haven't had any reboots or stability issues. It seems to have better performance and battery life as well, but it might just be in my head.
I don't know if there are any negative side effects of using SM-N920P kernels on our SM-N920R4 phones so flash it at your own risk, but it's working great for me. I just wanted to share my experience since there doesn't seem to be a good place to find information on our devices yet.
Click to expand...
Click to collapse
hay guys i just got mine sm-n920r4.. i am having a hard time finding phil recovery for this model. need help please need root asap
Rooted.
everything you need to root this device is at a site but i am new and cant post linkshttp://cdn2.xda-developers.com/images/smilies/frown.gif
Here's the steps I went through, I can tell it's a lot more steps than necessary but this is how I was able to get root + custom recovery on the latest update:
Okay guys, after a lot of hesitation I decided to attempt root and recovery, and was successful without any visual knox warnings.. There's not many clean guides here on this site so I'm posting the steps I went through.. first and foremost, enable usb debugging and OEM unlock.
For root, follow the guide here (note you'll get a sammy notification that your/you're device is rooted, turn that off. You'll also get a few odd reboots directly after odin resets your/you're phone, that's normal):
https://androidmtk.com/root-samsung-galaxy-note-5-sm-n920r4
After root you can use Skipsoft's Android Toolkit to install TWRP. *Make sure you follow the toolkits instructions closely.*
Link:*http://forum.xda-developers.com/not...lkit-skipsoft-android-toolkit-galaxy-t3399829
And for Xposed to work on our stock rom we obviously need the custom version that can be found here (ARM64 version):
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960**
**You can begin the following process from any Build/ROM but you must already have Root Access**
The 5.1 kernel's selinux hard enforcing prevents this build from booting when rooted. This means this build cannot be rooted! I created this ROM for those on previous, rooted builds that would like to try 5.1 while maintaining the ability to downgrade back to 4.4 and re-root at anytime. Enjoy!
**Required** FlashFire - Play BETA - PREVIEW
Download:
- G900A_PA2_Stock_ROMwTethering.zip
Previous Build:
- G900A_PA1_Stock_ROM.zip
1. Place the ROM onto your device (use either internal or ext-sdcard).
2. Open the FlashFire app and "Agree" to the Terms and Conditions.
3. Press "(+)" twice to bring up the "Actions" menu.
4. Press "Flash Zip or OTA" and locate and select the ROM. Leave "Auto-mount" unchecked under the "Options" menu and press the checkmark to continue.
5. From the main menu Uncheck all options under "EverRoot" and set "Reboot" setting to *"Download."
6. Press the lightning bolt then "Ok" to begin the **flash .
7. Once the flash is complete and the device reboots into "Download" mode, flash the G900A_OA1_Bootloader using Odin's PDA/AP slot.
*If you are already on the OA1 bootloader, set "Reboot" setting to "Normal" and skip Step 7.
**The screen will turn black then display the contents of your system before beginning the flash. FlashFire will pause for about 1 minute while flashing the "system" partition.
Once complete your device will reboot and pause on the AT&T splash screen for about 1 - 2 minutes before completely rebooting. Done!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Recommended: Package Disabler Pro for disabling unwanted bloatware (root access is not required).
Known Issues:
- None!
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery. The bootloader will not be updated to allow for downgrading to previous firmware versions.
3. No need to wipe prior to flashing! The ROM will automatically wipe UserData.
4. If you do not already have root access (or to unbrick) you must flash the G900A_Downgrade_to_NCE.tar using Odin's PDA/AP slot (Caution! Do not flash if you have taken the OC4, OF2, OF3, OI5, PA1, or PA2 ota updates!) and root with TowelRoot, before continuing with the above process.
5. To learn more about FlashFire's capabilities on locked bootloader devices see here: http://forum.xda-developers.com/showpost.php?p=60070810&postcount=2
Thank you so much @muniz_ri boss.
Hopefully we will see some 870A instructions lol
Well done muniz_ri. Ditto on the Active!
Sent from my Samsung 870a
Will this work on oc5 bootloader @muniz_ri ?
since I'm on 4.4.4 still can I make a slot in ss and install it there
Now installing
Thank you for this, running well so far with root. Will try xposed in 36h or so.
Edit: Su removed on reboot. Guess it was never rooted.
leoishwor10 said:
Now installing
Click to expand...
Click to collapse
Very fast and fell much better now .thanks again to muniz ...
Can't install su or busy box hope I didn't loose my root there been no updates on my phone should I try to go back to 4.4.4 my baseband is oi5 does this mean I lost root
stickman1981 said:
Can't install su or busy box hope I didn't loose my root there been no updates on my phone should I try to go back to 4.4.4 my baseband is oi5 does this mean I lost root
Click to expand...
Click to collapse
If u install this version then yes u lose the root ...if u want root feature then go back to NCE and root again.
leoishwor10 said:
If u install this version then yes u lose the root ...if u want root feature then go back to NCE and root again.
Click to expand...
Click to collapse
I was on 4.4.4 root the use ff to this Rom
Even if my base band is ol5 it not oa1
stickman1981 said:
Even if my base band is ol5 it not oa1
Click to expand...
Click to collapse
I think only 4.4.2 NCE version is rootable ..other then that no.
I didn't do any over the air update just use the forum here
So now u used this process to get 5.1.1
Yes when I first got the phone I used this link to root http://forum.xda-developers.com/showthread.php?t=3021120 been on 4.4.4 with ss and ff then used ff to flash 5.1.1
And muniz mentioned there this is unrooted version of 5.1.1 becase it is unrootable we dont have root on this 5.1.1 if u need root u have to go back to 4.4.2 and root
leoishwor10 said:
And muniz mentioned there this is unrooted version of 5.1.1 becase it is unrootable we dont have root on this 5.1.1 if u need root u have to go back to 4.4.2 and root
Click to expand...
Click to collapse
OK did u do the update if u did what's your base band my change to ol5
stickman1981 said:
OK did u do the update if u did what's your base band my change to ol5
Click to expand...
Click to collapse
See same
I forgot about phone info my boot loader is oa1 so I can use the file to downgrade sorry about the problems I miss understand
Latest T-Mobile QF6 Nougat FirmwareGive this guy @umaro some thanks he worked on this until it became reality even when I gave up
T-Mobile S7 Edge Can Be Found Here
This rom will give you a modded nonrooted rom that will pass safetynet checks with working samsung pay. No lag because stock boot.img is used
Files To Download
TMO_G930_Odin_Firmware.zip
FlashFire_Flashable_G930T_Firmware.zip
TMO_FLAT_HYBRID_PLAYSTORE_BS_FREE_NoNaMe_QF6_V4.zip
ADB_Root_Flat_Files.zip
This will wipe your phone
1. Unzip TMO_G930_Odin_Firmware.zip use odin and flash these files
2. Go through setup unzip ADB_Root_Flat_Files.zip flash eng boot.img with odin then root
3. Unzip FlashFire_Flashable_G930T_Firmware.zip and copy the AP_FlashFire_Only_G930_QF6_Firmware.tar.md5 file to your phone
4. Copy TMO_FLAT_HYBRID_PLAYSTORE_BS_FREE_NoNaMe_QF6_V4.zip to your phone
5. Use flashfire choose add zip and choose TMO_FLAT_HYBRID_PLAYSTORE_BS_FREE_NoNaMe_QF6_V4.zip make sure to mount system
6. Then click add firmware and choose the AP_FlashFire_Only_G930_QF6_Firmware.tar.md5 file you copied to your phone. Select all partitions
7. Do not inject SuperSU
The flash order should be AP firmware then the rom zip
8. Click Flash
9. In aroma choose full wipe
First boot will take 10+ minutes too boot
Playstore Mods fixed
MODS- (NoNaMeRomControl)
3minitbattery
Speed meter
Status bar mods
Center clock
Wifi/signal bar mods
Color change icon mod
Custom backgrounds
Notification drop-down
Incallui background
Gif in notification drop-down
Change/remove carrier names
And much more...
Bugs:
Do Not Use Package Disabler Or AdHell If You Choose NoNaMe Mods
Volume Panel Sliders Have A Bug With NoNaMe Mods
THANKS AND CREDITS
@jds3118 for testing and providing files and bootlooping his phone countless times for me
Gharrington for his awesome 3minitbattery mod...
NoNaMe rom development team for their incredible mods and rom control app...
@malbert16442 for his black themes
Xda for all the great guides to accomplish this...
RomControl Source
I recommend everyone put the Flashfire AP zip and Rom Zip on your internal storage as the AP file is so large that it may not be read properly do too limitations of some SD Cards. When you select AP file in Firmware there should be 4 partitions that are selected. If not then you have a bad download or need to have AP file on internal storage
Outstanding work. Thank you for this amazing rom.
jrkruse said:
This rom will give you a modded nonrooted rom that will pass safetynet checks with working samsung pay. No lag because stock boot.img is used
Click to expand...
Click to collapse
Thanks jrkruse for this , very much appreciated!
I just noticed your 930t post just now so I am very grateful and about to flash it.
I am currently on the previous ROM that you posted which is for the edge.
I had heavy lag after rooting due to the eng boot.img flashed on odin but after tinkering with L Speed, it's been much faster .
I'm going to do it over again using the 930t files you posted but I have a question if possible you can answer...
When you mention above thar there is no lag because stock boot.img is used... Does that only refer to the rom being flashed and not rooted ? Because of course the eng boot.img I need to flash on odin is necessary to be able to acquire root and this would leave me in the end with lag due to having to flash that eng boot img. ..
im hoping I'm wrong..
is there a way to flash in odin the eng boot, acquire root , and then flash back the stock boot.img and perhaps leaving me rooted and on a stock lag free boot.img ?
I read through the entire edge thread and other places and was hoping a solution but It may not be possible or I'm just missing something obvious? I'd rather not deal with tweaking using lspeed or kernel auditor etc. But if rooting only possible way is to be stuck with the eng boot img i guess I'll take the risk..
Thanks again !:good:
suddene said:
Thanks jrkruse for this , very much appreciated!
I just noticed your 930t post just now so I am very grateful and about to flash it.
I am currently on the previous ROM that you posted which is for the edge.
I had heavy lag after rooting due to the eng boot.img flashed on odin but after tinkering with L Speed, it's been much faster .
I'm going to do it over again using the 930t files you posted but I have a question if possible you can answer...
When you mention above thar there is no lag because stock boot.img is used... Does that only refer to the rom being flashed and not rooted ? Because of course the eng boot.img I need to flash on odin is necessary to be able to acquire root and this would leave me in the end with lag due to having to flash that eng boot img. ..
im hoping I'm wrong..
is there a way to flash in odin the eng boot, acquire root , and then flash back the stock boot.img and perhaps leaving me rooted and on a stock lag free boot.img ?
I read through the entire edge thread and other places and was hoping a solution but It may not be possible or I'm just missing something obvious? I'd rather not deal with tweaking using lspeed or kernel auditor etc. But if rooting only possible way is to be stuck with the eng boot img i guess I'll take the risk..
Thanks again !:good:
Click to expand...
Click to collapse
Following The directions will get you a nonrooted custom rom that can be manipulated by adb such as deleting stuff or pushing files to system and will pass safetynet checks. If you want a rooted rom it means you have to have the eng boot.img. If you root the rom and and only flash back stock boot.img you will not have root but as soon as you flash back eng boot.img you will have root again. but doing this breaks safetynet
Is it possible to delete the TMO boot sound with adb?
sabresfan said:
Is it possible to delete the TMO boot sound with adb?
Click to expand...
Click to collapse
See this post
Modded systemui volume panel fixed. Must flash AP file with rom
TMO_FLAT_HYBRID_PLAYSTORE_BS_FREE_NoNaMe_QF6_V4.zip
jrkruse said:
Modded systemui volume panel fixed. Must flash AP file with rom
TMO_FLAT_HYBRID_PLAYSTORE_BS_FREE_NoNaMe_QF6_V4.zip
Click to expand...
Click to collapse
Thank you for your continued support for us on the S7 flat.
I'm having issue playing video through flash player. For example, I can play youtube video through youtube app fine however if I play it through chrome or samsung browser is does this weird loop at any position in time of the video. Let me know if anyone else is having this issue. I installed rom but didn't install any of the mod of the mods. Wanted as close as stock possible. PS I did tried with mod and didn't like it and reflashed without mods.
Thanks in advance.
gundamdx said:
I'm having issue playing video through flash player. For example, I can play youtube video through youtube app fine however if I play it through chrome or samsung browser is does this weird loop at any position in time of the video. Let me know if anyone else is having this issue. I installed rom but didn't install any of the mod of the mods. Wanted as close as stock possible. PS I did tried with mod and didn't like it and reflashed without mods.
Thanks in advance.
Click to expand...
Click to collapse
It's the dual speaker mod try without that and all will work
@jrkruse,
Thanks. That is indeed the culprit. Reinstall rom without mods and remove system app through adb. Liking it. Thanks for all your efforts.
I am stuck in a bootloop when I install the stock kernel, but with the eng kernel it runs fine. Any ideas?
playingbball20 said:
I am stuck in a bootloop when I install the stock kernel, but with the eng kernel it runs fine. Any ideas?
Click to expand...
Click to collapse
Reread OP and post 2 you skipped something
Hi, nice work!, I have a quick question, can I install the rom without the mods? I just want to have root. If its possible, what steps I need to skip?
Thanks
ManuEZ said:
Hi, nice work!, I have a quick question, can I install the rom without the mods? I just want to have root. If its possible, what steps I need to skip?
Thanks
Click to expand...
Click to collapse
You can root but why not just root a stock Rom if you want no mods
Which file is the engboot.image?
DHackley said:
Which file is the engboot.image?
Click to expand...
Click to collapse
It's in the adb zip
Geizerjin said:
so this Rom has Modded Playstore? can i push modded apk thru adb with this rom?
Click to expand...
Click to collapse
The whole Rom is a customized stock nonrooted Rom. PlayStore and BSFree were my signature roms back in the day.
Playstore= almost all Samsung apps replaced with google apps that are found on the play store
BSFree= Highly debloated Rom with Samsung apps
NoNaMe= Systemui mods from that Rom.
You can choose whatever you want on install
My walkthrough
For amateurs like me, I put together some more detailed instructions. I hope this provides help for some users. Following the below steps I had no issues, it works great, and is very speedy. If there are any issues with my steps PLEASE correct me! I'm doing my best to contribute, not the opposite!
Thanks jrkruse, @umaro, and all others for this! So far I'm loving it!
My Steps:
1) ODIN (PC program) https://www.androidfilehost.com/?fid=24591023225177749
a. Setup:
-Make sure you have latest device drivers setup on your PC
-Enable USB Debugging on phone
-Boot phone into Download/Odin Mode: Turn off your device and press and hold Power button + Volume Down + Home. When you see the warning screen press Vol UP. Phone should say "Downloading..."
-Connect USB from PC to phone. ID:COM in Odin should turn Blue with a COM port
b. Unzip TMO_G930_Odin_Firmware.zip & select the (4) files from this zip (BL,AP,CP,CSC) in ODIN. Make sure all (4) get populated & selected
c. Options: Only these should be selected: Auto Reboot and F.Reset Time
d. Select START
e. When you get a green PASS! message in Odin, that means firmware has successfully been installed. Be patient as first boot may take a while
f. Exit ODIN
2) Phone Setup: After phone restarts for 1st time, go through setup as normal. (Ignore different carriers logos and SIM warnings)
3) ODIN: Restart phone back into Download/ODIN mode. Unzip ADB_Root_Flat_Files.zip, select ONLY AP_Nougat_S7_Flat_EngBoot.tar.md5, select START & wait for it to finish & restart phone
4) Gain Root:
a. Once phone comes back up, unzip ADB_Root_Flat_Files\Nougat_S7_Root_2_82_All_Carriers_V2.zip & Run root.bat. This will restart phone
b. After phone restarts, press key to continue install. I used options 2 & 1. Wait for phone to restart again. Should have root now.
5) FLASHFIRE/AROMA (App is now installed on phone via root script)
a. Unzip FlashFire_Flashable_G930T_Firmware.zip & copy unzipped file to your phone. Copy TMO_FLAT_HYBRID_PLAYSTORE_BS_FREE_NoNaMe_QF6_V4.zip to your phone. NOTE: Copy to internal memory NOT SD card.
b. Open FlashFire app on phone.
c. Choose + button, Flash ZIP, select TMO_FLAT_HYBRID_PLAYSTORE_BS_FREE_NoNaMe_QF6_V4.zip, select Mount /system option, touch checkmark button
d. Choose + button, Click add firmware & select AP_FlashFire_Only_G930_QF6_Firmware.tar.md5. Select all partitions, touch checkmark button
e. The flash order should be: Flash firmware package, then Flash ZIP. Everroot disabled. FLASH! Phone will restart into Aroma installer.
f. When phone comes up after script, select WIPE ALL DATA. (First boot will take 10+ minutes too boot)
---------- Post added at 07:45 PM ---------- Previous post was at 07:38 PM ----------
Curious (and looking to identify different tweak options), would I need to go through ALL the steps again in order to access the Flashfire/Aroma setup to pick different setups, like PlayStore or NoNaMe? Or is there a shortcut I could take?
Welcome to the root guide thread for the SAMSUNG J327T/T1 GALAXY J3 PRIME
This guide will show you how to root the J3 prime 2017, Exynos 7570 released by Tmobile and MetroPCS.
If you choose to follow the steps below, you should be aware of the risks.
While minimal, neither myself or thepcwiz101 accept any responsibily for broken devices.
Unfortunately this device has a locked bootloader and root so far has been elusive for this device. Many have tried different methods to no avail.
Finally it is here.
Through much research by @thepcwiz101 we came by a method that uses an ENG firmware to gain root. Basically this firmware is an engineering firmware with the su binary already installed which can be used to leverage some scripts to gain proper root with Supersu.
I went on the hunt for this firmware and found it.
Then we needed a method to push Supersu to the ENG firmware.
The Samsung S8/S8+ already used a similar method to root that device, so I took the script they used called SamPWNED and modified it to work for this device. We'll call this SamPWNED32.
Please see credits below for more info.
@thepcwiz101 did most of the testing along with a few others and finally we had success.
To see how we got here you can refer to the thread below:
https://forum.xda-developers.com/galaxy-j3-2017/help/samsung-galaxy-j3-prime-sm-j327t1-t3604860
Follow the steps below and at the end of it you should have a rooted device.
I strongly advise backing up all your settings and personal data before continuing. YOU HAVE BEEN WARNED!
Smartswitchmobile can be used to back up apps and settings to an SDCARD.
https://play.google.com/store/apps/details?id=com.sec.android.easyMover&hl=en_GB
************** INSTALLATION STEPS **************
Step 1.
Download the required files:
http://www.mediafire.com/file/s6hn38hb5wkiqsw/J327T_J327T_J327TUVU1AQC3_ROOT.zip
Step 2.
Unpack the package you downloaded above.
Put your device in DOWNLOAD mode (POWER + HOME + VOL DOWN)
Run Prince Comsey ODIN
Click the AP button then locate the ODIN flashable file you downloaded in the package named:
J327T_J327T1_J327TUVU1AQC3-eng.tar
Tick NAND Erase All
Leave all other ODIN options at default then click START.
Wait for the files to finish flashing and your device reboots. Disconnect the USB cable then remove the battery.
Force boot to recovery by holding POWER + HOME + VOL UP.
In recovery select Factory Reset then reboot the device.
Put the device to one side, have a coffee and wait a good ten minutes or so for the device to boot.
Step 3.
Once your device has fully rebooted you will be running the engineering firmware. This firmware isn't really good for a daily driver, so we're only using it to gain root.
Plug in the USB cable.
Your device should have USB debugging already enabled and a pop up should ask you to accept the connection to your PC. Accept the pop up to enable USB debugging for your PC.
Step 4.
Now to begin the root process.
Locate the root.bat file in the SamPWND32_Root folder and double click it to run it.
You should see a bunch of stuff on the screen as it does it thing and then your device should reboot.
When your device reboots you should now be rooted with SuperSU!
Step 5.
As mentioned in Step 3, this firmware isn't really good as a daily driver, so we're going to replace it with the stock firmware using Flashfire.
Download the stock firmware for your device from https://updato.com
Download Flashfire from the Play store: https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=en_GB
Download the Supersu system mode root package: https://forum.xda-developers.com/attachment.php?attachmentid=4289379&d=1506893064
Step 6.
Run Flashfire and agree when it asks for root permission.
In the main screen tap the + button then select Flash firmware Package and locate the stock firmware package you downloaded.
IMPORTANT: Uncheck the BOOT partition. Leave the rest enabled. Tap the tick top right when done. in the next screen tap EverRoot and uncheck Inject SuperSU and Preserve recovery. Tap the tick top right when done.
In the main screen again tap the + and then select Flash zip or OTA and locate the SR5-SuperSU-v2.82-SYSTEMMODE.zip
Check Mount /system read/write and leave everything else unchecked and then tap the tick when done.
Check you have the following selected on the main screen:
Flash Firmware package - The stock firmware with BOOT disabled.
Flash zip or OTA - System mode Supersu
EverRoot - disabled
Reboot - Normal
Ensure that System mode supersu is last on the list after the firmware or it won't root the new firmware.
Now tap FLASH and let Flashfire do it's thing.
When your device reboots you should be rooted and running the stock firmware.
If your devices suffers a kernel panic at any point take the battery out and reboot. Give it time and your device should stabilise.
I suggest factory resetting after performing the above procedure as this may make your device more stable if it's clean and fresh.
There is also an updated eng boot binary posted below which may help.
Hopefully you now have a fully rooted device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
IMPORTANT NOTE:
THE DEVICE STILL HAS A LOCKED BOOTLOADER. DO NOT ATTEMPT TO FLASH A CUSTOM RECOVERY OR ANYTHING THAT MODIFIES THE BOOT PARTITION. DO NOT REPLACE THE BOOT IMAGE EITHER.
DOING ANY OF THE ABOVE WILL SOFT BRICK THE DEVICE.
CREDITS:
ME(ashyx)
@thepcwiz101
@elliwigy and the SamPWNED devs (To donate or see who was involved in creating SamPWNED see this link, they deserve the credit for creating it.)
https://forum.xda-developers.com/ga...root-g955u-g955u1-snapdragon-sampwnd-t3658911
@Chainfire
@mauam for System mode Supersu
Anyone that tested.
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
DONATE ME HERE IF YOU WANT TO BUY ME A BEER/COFFEE OR HIT THE THANKS BUTTON IF I HELPED YOU
UPDATE 15/3/2018
Below is an updated eng binary(boot image) which may help with instability problems and kernel panics
This can be flashed with ODIN or Flashfire.
https://www.mediafire.com/file/q8j4b4ozvmwfrz7/J327TUVU1AQI1_eng_boot.tar
.
Just wanna say thanks to all that have put in the countless hours and hard work to finally give this device a root method. Will be testing this out as soon as I get home. Will post any issues or recommendations after flashing. Great work guys.
Samsung FAILS again!
ashyx said:
Please note this thread is still under construction and subject to change.
Click to expand...
Click to collapse
I think you hit the thread spot on. Also for anyone who would like to do further testing. here is my build.prop i edited. All it does is disable samsung's security features which i think is still enabled even when making supersu disable knox. Feel free to test out my build.prop. Warning do not use adb to transfer it. for some reason even when system is R/W it doesnt transfer and overwrite the original file it. when i did this i tried to transfer it using a root file manager and i was too late and a kernel panic caught me at the wrong time and when it rebooted it refused to load as build.prop was missing. After this (the 5th time rooting) i decided just to go back to stock as my phone is the only internet source i got.
thepcwiz101 said:
I think you hit the thread spot on. Also for anyone who would like to do further testing. here is my build.prop i edited. All it does is disable samsung's security features which i think is still enabled even when making supersu disable knox. Feel free to test out my build.prop. Warning do not use adb to transfer it. for some reason even when system is R/W it doesnt transfer and overwrite the original file it. when i did this i tried to transfer it using a root file manager and i was too late and a kernel panic caught me at the wrong time and when it rebooted it refused to load as build.prop was missing. After this (the 5th time rooting) i decided just to go back to stock as my phone is the only internet source i got.
Click to expand...
Click to collapse
Knox was already disabled on the firmware I've provided in the other thread, just saying.
MiiJack said:
Knox was already disabled on the firmware I've provided in the other thread, just saying.
Click to expand...
Click to collapse
Knox isn't just one thing, it's a number of services running in the background.
So got a noob question. Since we don't have the ability to have a custom recovery cuz of the locked bootloader any zips that we want to flash have to be done using abd correct? Or would it be possible to use the stock recovery using the install update from sd card option?
hatchet13rydin69 said:
So got a noob question. Since we don't have the ability to have a custom recovery cuz of the locked bootloader any zips that we want to flash have to be done using abd correct? Or would it be possible to use the stock recovery using the install update from sd card option?
Click to expand...
Click to collapse
the update from sd card option doesnt work. all it does is check signatures and anything that doesnt got samsungs signature will fail to flash.
---------- Post added at 12:32 PM ---------- Previous post was at 12:32 PM ----------
ashyx said:
Knox isn't just one thing, it's a number of services running in the background.
Click to expand...
Click to collapse
i know.
thepcwiz101 said:
the update from sd card option doesnt work. all it does is check signatures and anything that doesnt got samsungs signature will fail to flash.
That's what I thought. So basically I'll have to use adb to install any zips correct?
Edit.. nevermind my smart self forgot all about flashfire as the guide tells me to use for the root method.
Click to expand...
Click to collapse
hatchet13rydin69 said:
That's what I thought. So basically I'll have to use adb to install any zips correct?
Click to expand...
Click to collapse
No, you use Flashfire which pretty much does the same as any custom recovery and then some.
ashyx said:
hatchet13rydin69 said:
No, you use Flashfire which is pretty much does the same as any custom recovery and then some.
Click to expand...
Click to collapse
I feel like a complete noob right now. It's been a long day lol
Click to expand...
Click to collapse
thepcwiz101 said:
i know.
Click to expand...
Click to collapse
That was in response to MiiJack.
ashyx said:
That was in response to MiiJack.
Click to expand...
Click to collapse
my bad i must have misread your post.
Hey everyone i literally found a way to make a custom rom for this device. Take a look on the tmobile s8 thread. They have a locked bootloader just like us and yet they got a custom stock rom that has alot of optimizations they use flashfire to flash the rom. If anyone knows enough to build a heavily modified stock rom please start a thread. I can provide the kernel files if needed as samsung released the kernel soon after releasing this phone. We need a more stable kernel to stop these kernel panics.
thepcwiz101 said:
Hey everyone i literally found a way to make a custom rom for this device. Take a look on the tmobile s8 thread. They have a locked bootloader just like us and yet they got a custom stock rom that has alot of optimizations they use flashfire to flash the rom. If anyone knows enough to build a heavily modified stock rom please start a thread. I can provide the kernel files if needed as samsung released the kernel soon after releasing this phone. We need a more stable kernel to stop these kernel panics.
Click to expand...
Click to collapse
Modified ROM is no problem to flash, it's no different to the stock rom after rooting/installing xposed etc, but a custom kernel is a no go I'm afraid.
ashyx said:
Modified ROM is no problem to flash, it's no different to the stock rom after rooting/installing xposed etc, but a custom kernel is a no go I'm afraid.
Click to expand...
Click to collapse
Well i think we could flash the updated kernel that is stock as its more stable. It shouldnt be blocked by the bootloader. And also the kernel is inside of fota.zip but im afraid it may cause root to be lost. Only testing will show for sure. I would only flash the stock kernel after reflashing the stock system.img using flashfire. Then attempt to obtain root with supersu and try to use terminal emulator. If you get root attempt to run the root script again to repatch the kernel if at all possible. As the root script patches uevent_helper inside /sys/kernel
thepcwiz101 said:
Well i think we could flash the updated kernel that is stock as its more stable. It shouldnt be blocked by the bootloader. And also the kernel is inside of fota.zip but im afraid it may cause root to be lost. Only testing will show for sure. I would only flash the stock kernel after reflashing the stock system.img using flashfire. Then attempt to obtain root with supersu and try to use terminal emulator. If you get root attempt to run the root script again to repatch the kernel if at all possible. As the root script patches uevent_helper inside /sys/kernel
Click to expand...
Click to collapse
You can't use a stock kernel nor can it be patched. We don't need to go down this road again here. It's all been covered in the previous thread.
To gain root an eng boot image is needed otherwise the device will simply soft brick due to integrity check failure.
The images I have provided here contain the latest eng boot from the combo firmware which should in theory be more compatible with later stock firmwares.
On another note, no info whatsoever in the form of logs has been provided regarding the kernel panics.
ashyx said:
You can't use a stock kernel nor can it be patched. We don't need to go down this road again here. It's all been covered in the previous thread.
To gain root an eng boot image is needed otherwise the device will simply soft brick due to integrity check failure.
The images I have provided here contains the latest eng boot from the combo firmware which should in theory be more compatible with later stock firmwares.
On another note, no info whatsoever in the form of logs has been provided regarding the kernel panics.
Click to expand...
Click to collapse
Ok i must have had a brain fart there. Well and thats because i have been literally unable to get them as the crashes happen before i can get a logcat going. I personally wouldnt do anything unless the crashes havent happend after 30 mins of the phone being on bc if your in a file transfer or changing a system file like build.prop you would go into a soft brick if you get a kernel panic during it. It happend to me and i wasnt happy about it which made me decide to go back to full stock. But just saying as soon as i am able to start a catlog the panics stop.
thepcwiz101 said:
Ok i must have had a brain fart there. Well and thats because i have been literally unable to get them as the crashes happen before i can get a logcat going. I personally wouldnt do anything unless the crashes havent happend after 30 mins of the phone being on bc if your in a file transfer or changing a system file like build.prop you would go into a soft brick if you get a kernel panic during it. It happend to me and i wasnt happy about it which made me decide to go back to full stock. But just saying as soon as i am able to start a catlog the panics stop.
Click to expand...
Click to collapse
Logging starts as soon as the device is booted, so last_kmsg should contain info up to the crash.
Logcat won't be of any use as it'll only be for the currently booted system.
However it can be piped to a file or via adb to windows up until it crashes.