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.
Related
Hi All,
1. Will unlock the bootloader wipe out the phone? If so how to root 2.3.6 without losing data?
I want to backup my data in the N1, then do flash the CM7 mod onto that.
It's in retail 2.3.6, I want to backup my data first.
sms, did with sms backup and restore.
call logs and bookmarks, how I backup them?
apps, want to backup with titanium backup, but hasn't root the phone yet.
I found the root guide for 2.3.6 here
https://bexton.net/2011/10/12/bexboot-root-nexus-one-passion-grk39f/
But it wants me to unlock the bootloader first, unlock the bootloader will wipe the phone so I will lost my data right?
apps can be redownloaded, so how I backup my call logs and bookmarks without root (yet)?
--
another question is I see the note for the latest N1 CM7 build is
'The latest radio is needed to run CyanogenMod 7'.
I can see my phone already has baseband of 5.08.00.04, do I need to do anything related to the radio while I flashing CM7?
Regards,
Sorry, there is NO way to back up your data if you are on 2.3.6 with a locked bootloader and without root.
I'm on stock 2.3.6.
Tried using the bexboot method, but it goes through all the steps and does nothing.
The bat file at the end doesn't reboot my phone or root.
I have also tried downgrading my device, but every time i go into fastboot, it says I have the wrong img file, or the file can't be found. I have properly renamed the file and put it on my sd card. no luck.
please help
patelkartik27 said:
I'm on stock 2.3.6.
Tried using the bexboot method, but it goes through all the steps and does nothing.
The bat file at the end doesn't reboot my phone or root.
I have also tried downgrading my device, but every time i go into fastboot, it says I have the wrong img file, or the file can't be found. I have properly renamed the file and put it on my sd card. no luck.
please help
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=18527514&postcount=1853
patelkartik27 said:
I'm on stock 2.3.6.
Tried using the bexboot method, but it goes through all the steps and does nothing.
The bat file at the end doesn't reboot my phone or root.
I have also tried downgrading my device, but every time i go into fastboot, it says I have the wrong img file, or the file can't be found. I have properly renamed the file and put it on my sd card. no luck.
please help
Click to expand...
Click to collapse
Sry for the late response, but i've been on a business trip. The issue with my first version of bexboot was, that it was compiled from a heavily "prestressed" system with lots of modifications. Thus i rebuilt the boot image from a complete clean source.
So if somebody is still looking for an "idiot-proof" way to root a Nexus One on stock GRK39F, check out the updated version release of Bexboot v2.0 what have been confirmed working from people who had issues with v1:
https://bexton.net/2011/11/07/bexboot-for-passion-version-2-root-for-nexus-one-with-android-grk39f/
Greets!
Bexton said:
Sry for the late response, but i've been on a business trip. The issue with my first version of bexboot was, that it was compiled from a heavily "prestressed" system with lots of modifications. Thus i rebuilt the boot image from a complete clean source.
So if somebody is still looking for an "idiot-proof" way to root a Nexus One on stock GRK39F, check out the updated version release of Bexboot v2.0 what have been confirmed working from people who had issues with v1:
https://bexton.net/2011/11/07/bexboot-for-passion-version-2-root-for-nexus-one-with-android-grk39f/
Greets!
Click to expand...
Click to collapse
What is the advantage of doing this, if all you have to do is flash a custom recovery and flash this from recovery??
efrant said:
What is the advantage of doing this, if all you have to do is flash a custom recovery and flash this from recovery??
Click to expand...
Click to collapse
Hey Efrant,
well, actually there is no big difference. But if i should find some, maybe:
A) ALL-IN-ONE
* It comes packed with all you need.
* There is no need to have the SDK installed before using it.
* You don't need to flash a custom recovery before using it.
B) STOCK
* As you don't need a custom recovery to flash it, you also don't need to overwrite any of the original stock ROM files. So actually your system stays completely untouched.
C) UP-TO-DATE
* It installs the latest versions of Superuser APK / su binary, rather than the linked ones.
The bottom line: Actually it was built for "beginners", to provide a simple to use method to root a stock ROM. You can download a zip archive, connect an untouched, never used/modified stock phone to a computer, type two/three commands in a terminal window, the phone reboots, you have root and the system is still pure stock. That's what it's all about..
Cheers!
Bexton said:
Hey Efrant,
well, actually there is no big difference. But if i should find some, maybe:
A) ALL-IN-ONE
* It comes packed with all you need.
* There is no need to have the SDK installed before using it.
* You don't need to flash a custom recovery before using it.
B) STOCK
* As you don't need a custom recovery to flash it, you also don't need to overwrite any of the original stock ROM files. So actually your system stays completely untouched.
C) UP-TO-DATE
* It installs the latest versions of Superuser APK / su binary, rather than the linked ones.
The bottom line: Actually it was built for "beginners", to provide a simple to use method to root a stock ROM. You can download a zip archive, connect an untouched, never used/modified stock phone to a computer, type two/three commands in a terminal window, the phone reboots, you have root and the system is still pure stock. That's what it's all about..
Cheers!
Click to expand...
Click to collapse
Thanks for the explanation. Good work.
But just to address some of your points:
A) ALL-IN-ONE:
if you don't install the SDK, you still need to install the fastboot and ADB drivers anyway - there is no difference between using this method or any other method, i.e., either the SDK or the drivers themselves have to be installed for your device to be recognized by the computer.
B) STOCK:
flashing a custom recovery on a stock ROM does not really overwrite anything, because once you boot your device, the stock recovery is automatically flashed back by the ROM.
no ROM files are touched by flashing a custom recovery.
C) UP-TO-DATE
I linked to the wrong thread in my post.. oops I meant to link here: http://androidsu.com/superuser/
efrant said:
Thanks for the explanation. Good work.
But just to address some of your points:
A) ALL-IN-ONE:
if you don't install the SDK, you still need to install the fastboot and ADB drivers anyway - there is no difference between using this method or any other method, i.e., either the SDK or the drivers themselves have to be installed for your device to be recognized by the computer.
B) STOCK:
flashing a custom recovery on a stock ROM does not really overwrite anything, because once you boot your device, the stock recovery is automatically flashed back by the ROM.
no ROM files are touched by flashing a custom recovery.
C) UP-TO-DATE
I linked to the wrong thread in my post.. oops I meant to link here: http://androidsu.com/superuser/
Click to expand...
Click to collapse
Well, as said: actually there's no big difference. And yeah, indeed you're right about the recoveries. But to address one of your (/my) points:
The SDK is an application package that needs to be installed.
Fastboot, as well as the ADB are standalone executables; there is nothing to be installed. These executables are just a tiny part of the whole SDK Package. There's no need to download and install all the SDK Package, if you'd need just the adb, the fastboot and the drivers. Thus you'd save at least some time (and bandwith).
Also, when i'll include the install script tomorrow (as it has been with v1), it will reduce the number of commands you have to type in the terminal to two.
So the bottom line: eventhough you're right about (almost all of) your contras, if you'd need to start with an untouched phone and computer it's definitely faster - and i think, also just simpler - to do it "my way".
But.. anyway.. it's the same way.
---------- Post added at 10:46 PM ---------- Previous post was at 10:34 PM ----------
PS: And therefore - to re-answer your initial question:
efrant said:
What is the advantage of doing this, if all you have to do is flash a custom recovery and flash this from recovery??
Click to expand...
Click to collapse
Depending on your working environment, it simply can save some time.
This method has been taken from the following threads and some what modified :
http://forum.xda-developers.com/verizon-galaxy-s5/general/how-to-root-g900vvru1ane9-t2836201
http://forum.xda-developers.com/showthread.php?t=2840150
Rooting method has been tested only on G900F, G900M, G900I and G900FD. Theoretically it should work on all the variants of S5 that were SUPPORTED by towelroot before updating . test and let me know ; )
FOR ANDROID LOLIPOP 5, LOOK BELOW THE ROOTING INSTRUCTIONS ON HOW TO UPGRADE FROM 4.4.2 TO 5.0 WITHOUT TRIGGERING KNOX. The Rom has been compiled/cooked by @_alexndr
Hence credits go out to:
@muniz_ri
@open1your1eyes0
@Misterxtc
@FlairDevil
@Chainfire
@_alexndr
@geohot
@aguarello
@lufeig
@mkh.mourad
@faraaz @Lonski
Missed any1?? shoot me a PM
For G900M please look at post #13 or click here
http://forum.xda-developers.com/showthread.php?p=54745709
Requirements:
1. Have ANG2 or latest 4.4.2 Rom installed
2. Require PC Odin 3.09
3. Kernal for NE2 (Old Rom Kernel for G900F ONLY, use F6 KERNEL FOR G900FD), get G900F kernels from here: https://www.dropbox.com/s/cun1uainm2h07em/KERNEL_G900FXXU1ANE2.tar.md5
4. Your current Rom Kernel prior to flashing the old kernel. Here the kernel for FOR H900F ONLY: https://www.androidfilehost.com/?w=files&flid=18027 (kudus to @_alexndr) (if your Kernel is not there and/or you have a different variant like 900I, look below the instructions on how to create flashable kernel)
5. DISABLE REACTIVATION LOCK
6. IF YOUR DEVICE IS ENCRYPTED, DECRYPT IT
7. Towelroot and SuperSU downloaded and installed prior to flashing NE2 kernel
For SM-900I Australian:
Look >>>>here<<<<
Root instructions:
1. Get to download mode, and flash ANE2 kernel or relevant kernel that supports towelroot
2. Once done, reboot and open towelroot and click make it rain. (NOTE: wifi and s health will not work after flashing ANE2 kernel and you will face numerous FCs)
3. After this, reboot again into download mode and flash your current rom kernel. everything will start to work and all FC will be gone.
4. Open SuperSU and update binary and viola!!
For any Questions FAQ first before posting: >>>Here<<<<
===============================
Flashing android 5.0 WITHOUT TRIGERRING KNOX:
After rooting with the above method, flash using Mobile Odin Pro @_alexndr rom from this thread >>>>here <<<<
How to downgrade from Android 5 to 4.4.2??
1. Download ANE2 Firmware
2. Flash it via PC Odin.
3. Boot your phone into recovery mode and factory/data reset
4. Reboot and Viola
Congratulations You've been faster
★ [ROOT][N9005] ★ Rooting 4.4.2 XXUFNF4 & NEWER stock firmwares ★ (KNOX 0x0) ★
I've planned to create a similar thread for G900F, but no problem good work :good:
everything well explained below but i´ve got one question: Will it work with SM-G900f?
julianski said:
everything well explained below but i´ve got one question: Will it work with SM-G900f?
Click to expand...
Click to collapse
Yes, of course it has been well tested by OP, me and my friends
I followed the instructions and everything went well. When i flashed NE2 kernel S Health Service was force closing all the time
When i flashed back to NG2 kernel phone was running again like a champ!
Thank you very much for this guide! worked flawlessly
BTW Knox 0X0
Lol you will cost chainfire quite a bit in lost revenue on mobile Odin
wajiman said:
Again, THIS DOES NOT TRIGGER KNOX
Click to expand...
Click to collapse
Work fine!
CIC: ATO (Austria)
Knox: 0x0
Status: Custom
Thanks for you job!
Jogi_CH said:
Work fine!
CIC: ATO (Austria)
Knox: 0x0
Status: Custom
Thanks for you job!
Click to expand...
Click to collapse
There is a way to keep status official and also keep root. It worked on rom NE2.
Did not try it yet on this Method. Will c and update tonight
I'm not used to these procedures so I didn't really know what I was doing but it worked for me as well:
As above, S Health was FC constantly and it was pretty difficult to get into towelroot or SuperSU in between.
I already had SuperSU installed and I did not uninstall it before starting the procedure (may be I should have?). SuperSU wouldn't start because of no binaries installed so there was no way to install them (or I don't know how to do it). I could uninstall and reinstall SuperSU but it would not restart at all afterwards. I gave up.
During this time, I had also warning messages about unauthorized operations taking place and asking me to reboot to undo these changes. I ignored these messages.
I finally rebooted, flashed ANG2 kernel and rebooted. It seems everything is fine. I have root access and KNOX 0x0. SuperSU also works normally.
WiFi did not work either, as written in the guide. It looks like it removed the connexion settings. I had to re configure WiFi after last reboot.
Thank you very much for this procedure!
I updated my phone through OTA and want to root again using TowelRoot. I have the following ROM; G900FXXU1ANG9, is the ANG2 kernel the same or do I need to find the ANG9 kernel? If not, can I extract the ANG9 kernel without root? Because I can't find a download link for ANG9...
See screenshot for details:
{
"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"
}
Thanks in advance! Great tutorial btw!
Verstuurd vanaf mijn SM-G900F met Tapatalk
Hi, i know this is for the lte version (sm-g900f) but do you know of a working method for the sm-g900h? Thanks for sharing.
faraaz said:
I updated my phone through OTA and want to root again using TowelRoot. I have the following ROM; G900FXXU1ANG9, is the ANG2 kernel the same or do I need to find the ANG9 kernel? If not, can I extract the ANG9 kernel without root? Because I can't find a download link for ANG9...
See screenshot for details:
Thanks in advance! Great tutorial btw!
Verstuurd vanaf mijn SM-G900F met Tapatalk
Click to expand...
Click to collapse
Mate as per your screen, kernel version number is same but date and dpi are different. i dont know what do they stand for but to be on the safe side i wont recommend you as of now to root. you will need to wait until your firmware is out on sammobile so to extract the kernel file from it.
tisazalay said:
Hi, i know this is for the lte version (sm-g900f) but do you know of a working method for the sm-g900h? Thanks for sharing.
Click to expand...
Click to collapse
Sorry towelroot does not support G900H so this method wont work on yours
i want to thank the OP and everybody involved somehow for making this method successful for me.
thanks for this method, now i have a SGS5 SM-G900M, on firmware G900MUBU1ANG3, rooted, knox 0x0.
i was already on stock (non-rooted) G900MUBU1ANG3. find below my steps to accomplish this:
1. install towelroot apk on device
2. downloaded ODIN 3.09 on PC
3. downloaded G900MUBU1ANE2 firmware on PC
4. downloaded G900MUBU1ANG3 firmware on PC
5. using WINRAR, i extracted G900MUBU1ANE2 kernel (boot.img)
6. using this script (kudos to mkh.mourad), i created boot.tar.md5
7. put device in download mode (turn off, press POWER + VOLUME DOWN + HOME buttons, connect to PC using USB cable
8. run ODIN 3.09, click AP button, select "boot.img" just created, and flashed it. then deleted "boot.img"
9. upon device reboot, you will receive lots of FCs. don't worry, run towelroot, click make it ra1n
10. put device in download mode (turn off, press POWER + VOLUME DOWN + HOME buttons, connect to PC using USB cable
11. using WINRAR, i extracted G900MUBU1ANG3 kernel (boot.img)
12. using this script (kudos to mkh.mourad), i created boot.tar.md5
13. put device in download mode (turn off, press POWER + VOLUME DOWN + HOME buttons, connect to PC using USB cable
14. run ODIN 3.09, click AP button, select "boot.img" just created, and flashed it. then deleted "boot.img"
now i have latest official firmware, rooted, knox 0x0!!!
thanks!!!
Hi!
I have a rooted G900F with ANE2. ANG2 is not available yet fro me. My question is if the update will be available and I want to update with root, I have to do the steps from the beginning or can I skip them and continue from 7?
Markee89 said:
Hi!
I have a rooted G900F with ANE2. ANG2 is not available yet fro me. My question is if the update will be available and I want to update with root, I have to do the steps from the beginning or can I skip them and continue from 7?
Click to expand...
Click to collapse
If i`am rooted i always disable the whole OTA procedure, just add .bak to FW Upgrade.apk and its odex file so it will not be active after reboot and you don`t get notifications anymore. Instead i flash the whole updated rom with Mobile Odin Pro and i check wipe data and cache, enable Everroot and the other 2 options and flash it. Make a app/data backup with Helium or Titanium Backup first of your apps and personal files.
gee2012 said:
If i`am rooted i always disable the whole OTA procedure, just add .bak to FW Upgrade.apk and its odex file so it will not be active after reboot and you don`t get notifications anymore. Instead i flash the whole updated rom with Mobile Odin Pro and i check wipe data and cache, enable Everroot and the other 2 options and flash it. Make a app/data backup with Helium or Titanium Backup first of your apps and personal files.
Click to expand...
Click to collapse
Do you replace the .apk for .bak or do you add it at the end of the .apk?
Thanks
aguarello said:
Do you replace the .apk for .bak or do you add it at the end of the .apk?
Thanks
Click to expand...
Click to collapse
In /systems/app FWUpgrade.apk.bak and in system/priv-app FotaClient.apk.bak, the same for the odex files
faraaz said:
I updated my phone through OTA and want to root again using TowelRoot. I have the following ROM; G900FXXU1ANG9, is the ANG2 kernel the same or do I need to find the ANG9 kernel? If not, can I extract the ANG9 kernel without root? Because I can't find a download link for ANG9...
See screenshot for details:
Thanks in advance! Great tutorial btw!
Verstuurd vanaf mijn SM-G900F met Tapatalk
Click to expand...
Click to collapse
you can download G900FXXU1ANG9 now sammobile has uploaded it!
I'll try to root G900FXXU1ANG9 tonight
http://www.sammobile.com/firmwares/3/?download=33474
Hey guyz, do you think this work with "G900FQJVU1ANG4" installed S5? Thanks.
akdenizx said:
Hey guyz, do you think this work with "G900FQJVU1ANG4" installed S5? Thanks.
Click to expand...
Click to collapse
It should work on any firmware but make sure you have ANG4 kernel with you
Hi all,
i would like to ask how to install a custom rom onto my samsung galaxy s3 mini. I know there are many guides but i am a complete starter, i just made a switch from apple and i have no idea what they mean, even the clearest one.. I just want to update these devices to lollipop since they are still on 4.1.2 jelly bean. Omnirom or cyanogen or others, i dont mind, i just want an updated device. Step by step instructions on everything would be perfect thank you!! By the way, i dont have windows, only mac.
this would help me a lot in the future.
thanks
Leonardo Yip said:
Hi all,
i would like to ask how to install a custom rom onto my samsung galaxy s3 mini. I know there are many guides but i am a complete starter, i just made a switch from apple and i have no idea what they mean, even the clearest one.. I just want to update these devices to lollipop since they are still on 4.1.2 jelly bean. Omnirom or cyanogen or others, i dont mind, i just want an updated device. Step by step instructions on everything would be perfect thank you!! By the way, i dont have windows, only mac.
this would help me a lot in the future.
thanks
Click to expand...
Click to collapse
Hi, at first I suggest to you to choose between two roms: The Omnirom and the CM. Your choice depend only about what you want from your phone. The Omni one is pretty nice and it looks like more a stock rom. The CM is very customisable in a lot of stuff. If you are not very expert, I suggest to you the CM, because it's more easy to install. But decide at first what you need from your phone!
Stefano Cappelletti said:
Hi, at first I suggest to you to choose between two roms: The Omnirom and the CM. Your choice depend only about what you want from your phone. The Omni one is pretty nice and it looks like more a stock rom. The CM is very customisable in a lot of stuff. If you are not very expert, I suggest to you the CM, because it's more easy to install. But decide at first what you need from your phone!
Click to expand...
Click to collapse
I’ll choose Cyanogen then. Thanks for the reply.
What you need to flash is:
- the original firmware
- Odin
- USB drivers
- CM (Odin version)
- gApps (Google Apps)
You can find the original firmware on sammobile.com, and you can find other sottware on novafusion.pl in the section . When you have everything we can start!
Stefano Cappelletti said:
What you need to flash is:
- the original firmware
- Odin
- USB drivers
- CM (Odin version)
- gApps (Google Apps)
You can find the original firmware on sammobile.com, and you can find other sottware on novafusion.pl in the section . When you have everything we can start!
Click to expand...
Click to collapse
Is it ok if i get odin for mac? Because i'm a mac user. I'm not sure if this is official
techbeasts . com/2015/04/13/download-odin-jdoin3-mac/
I added two spaces between on the left and write of the dot because I'm not allowed to post links, idk why. Just remove the other two spaces thanks.
Two more things, I can't find the USB drivers or original firmware on novafusion. And please be patient as it will take a while to download these things. My internet has a whopping 200 kilobytes per second, yeah it's slower than a snail...
It seems that Odin for Mac doesn't exist, the software that you can find is only similar but not the original Odin. Maybe they are good software as well but I don't want to risk to brick the phone for a not fully compatible software... Don't worry: we do everything also without Odin, is just a little bit longer but it works.
At first reboot your phone in recovery mode (menu button, volume up, power botton than wait) and do the wipe of cache and than reboot it and wait.
When the Phone is ready go here and download the SuperSu (to root the device) https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
and copy the zip file in your phone, than, reboot again the device in recovery mode and select "instal ZIP" (or something like that, I don't remember exactly honesty and choose the zip that you downloaded. Reboot the phone and now if everything worked you should find an app called "SuperSU" in your drawer. After you got the root access, we can go to the next step
Oh i actually already rooted it with KingRoot, is it bad?
Leonardo Yip said:
Oh i actually already rooted it with KingRoot, is it bad?
Click to expand...
Click to collapse
KingoRoot is also fine.
Regarding "Odin on Mac":
jOdin uses "Heimdall" which works fine with S3 Mini - so unless they messed up the UI completely (giving wrong commands to Heimdall) the tool works fine, too.
KingRoot is should be fine at the same. You just need the root access to flash the device from the recovery. I sugget to you to install the TWRP recvery if you don't have it yet. You can download it and flash it from the recovery (you have root access now) or you can download an app on Google Play store like rom manager or TWRP manager and install the recovery from the app. Then we can go to the next step
KaffeeKiffer thanks but i'll stick with Stefano's method . Ok i got TWRP, but i still can't find the USB drivers or the original firmware (it's not on SamMobile). And for cyanogen mod 12.1, do i now get the normal version, like not the odin one?
Yes, you have to download not the Odin version but the other one "recovery version". At the same you have to download and flash the TWRP recovery first (always "recovery version" of the download). It should be the same also if you flash the CM with other recovery but I read online that flashing CM via recovery, by the TWRP recovery is better.
1) Download and flash TWRP recovery
2) Wipe cache and clean everything
3) Download and flash
Now the next step will be installing gApps
MAJOR PROBLEM!!! PLEASE HELP NOW. It failed to install the zip, and when i try to reboot it, it goes automatically to twrp.. please see attached picture, please please help. it says E: Error executing updater binary in zip
{
"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"
}
http://postimg.org/image/j4invhd0v/
Leonardo Yip said:
MAJOR PROBLEM!!! PLEASE HELP NOW. It failed to install the zip, and when i try to reboot it, it goes automatically to twrp.. please see attached picture, please please help. it says E: Error executing updater binary in zip
http://postimg.org/image/j4invhd0v/
Click to expand...
Click to collapse
sei italiano?
KaffeeKiffer said:
KingoRoot is also fine.
Regarding "Odin on Mac":
jOdin uses "Heimdall" which works fine with S3 Mini - so unless they messed up the UI completely (giving wrong commands to Heimdall) the tool works fine, too.
Click to expand...
Click to collapse
I'll jump in long enough to point out that Heimdall/Odin is not functional under current Mac environments. SInce Mobile Odin is effectively obsolete for current devices/ROMs, Mac users often rely on fastboot and similar tools instead for what can't be accomplished via a good custom recovery such as TWRP.
Leonardo Yip said:
Hi all,
i would like to ask how to install a custom rom onto my samsung galaxy s3 mini. I know there are many guides but i am a complete starter, i just made a switch from apple and i have no idea what they mean, even the clearest one.. I just want to update these devices to lollipop since they are still on 4.1.2 jelly bean. Omnirom or cyanogen or others, i dont mind, i just want an updated device. Step by step instructions on everything would be perfect thank you!! By the way, i dont have windows, only mac.
this would help me a lot in the future.
thanks
Click to expand...
Click to collapse
install odin on windows pc: http://depositfiles.com/files/m2n77b1vc
install samsung drivers on windows pc: http://developer.samsung.com/technical-doc/view.do?v=T000000117#none
get cyanogenmod 12.1: http://novafusion.pl/
get the odin version
when mobile powered off, hold volume down, home and power button. You get the downloadmode option on your screen, let go all buttons and press volume up button.
Now connect the phone to your pc with the usb cable and let odin find it.
Load the tar file in the downloaded zip file as pda and flash it.
If you want clockwork mod, install this as tar, also in pda flash option: https://www.androidfilehost.com/?fid=95887005526789241
If your samsung doesn't work but you can still get into download mode, view next page: http://forum.xda-developers.com/showthread.php?t=2122548
and install a fail safe firmware according to your type of phone.
Leonardo Yip said:
MAJOR PROBLEM!!! PLEASE HELP NOW. It failed to install the zip, and when i try to reboot it, it goes automatically to twrp.. please see attached picture, please please help. it says E: Error executing updater binary in zip
http://postimg.org/image/j4invhd0v/
Click to expand...
Click to collapse
I don't have 12.1 running, but isn't TRWP 2.6.3 a bit low? I hope somebody with experience in that regard can help you.
But on Novafusion's site (which I assume you're flashing), the current version is 2.8.
Androidandy's version also worked great for me.
Mike B. said:
I'll jump in long enough to point out that Heimdall/Odin is not functional under current Mac environments. SInce Mobile Odin is effectively obsolete for current devices/ROMs, Mac users often rely on fastboot and similar tools instead for what can't be accomplished via a good custom recovery such as TWRP.
Click to expand...
Click to collapse
Thanks for the info - I tested it some time ago and have a windows PC, so no need to run it ever after.
I was just relying on my past experience.
What i don't understand is why the flashing went wrong, I did everything right, at least I think. Wipe everything and flash the rom, why didn't it work?
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?
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?