Related
Background:
I had my Galaxy S3 rooted on 4.0.4 ICS with no problems for several months, however when I wanted to upgrade to 4.1 Jellybean via OTA I quickly learned that the OTA update won't work on a rooted OS. I installed an called Voodoo OTA which claimed to be able to temporarily unroot you device so you can get the OTA Jellybean update. It failed, did not accomplish what it claimed to be able to do, however what it did do was patially unroot my phone to a state that it can neither be unrooted fully or re-rooted back to a full rooted state. I did a full clean wipe and factory reset and I am still in the same position. I have used the Android Toolkit for S3 to flash it back to factory state it just hangs in ODIN at the boot.img, I have attempted to root and un-root with the Android Toolkit multiple methods and .tar files, nothing, just hangs when it gets to the imaging part.
The phone is fully functional, but I feel imprisoned by the phone now as it operates like an unrooted phone, but I can't upgrade it.
Can anyone help me out of this, even to just get back to a rooted phone.
Thank you to anyone and everyone for your advice!
I will donate to any developer that can get my phone back to working order!
bigmtnskier said:
Background:
I had my Galaxy S3 rooted on 4.0.4 ICS with no problems for several months, however when I wanted to upgrade to 4.1 Jellybean via OTA I quickly learned that the OTA update won't work on a rooted OS. I installed an called Voodoo OTA which claimed to be able to temporarily unroot you device so you can get the OTA Jellybean update. It failed, did not accomplish what it claimed to be able to do, however what it did do was patially unroot my phone to a state that it can neither be unrooted fully or re-rooted back to a full rooted state. I did a full clean wipe and factory reset and I am still in the same position. I have used the Android Toolkit for S3 to flash it back to factory state it just hangs in ODIN at the boot.img, I have attempted to root and un-root with the Android Toolkit multiple methods and .tar files, nothing, just hangs when it gets to the imaging part.
The phone is fully functional, but I feel imprisoned by the phone now as it operates like an unrooted phone, but I can't upgrade it.
Can anyone help me out of this, even to just get back to a rooted phone.
Thank you to anyone and everyone for your advice!
Click to expand...
Click to collapse
I am desperate at this point , I have spent 2 almost 3 days trying to get my phone back to stock or rooted state. I have scoured Google, XDA and other Android phones. If anyone wants to volunteer and help me on or offline I will gladly donate generously.
I'd recommend forgetting about that tool kit for now. You should download the latest version of Odin v3.07, twrp recovery (tar file), and supersu.zip, and try doing everything manually; flash twrp through PDA from Odin, and supersu.zip through Twrp recovery if you get that far. The files are easy to find, so I'm not going to post links just yet.
Sent from my SAMSUNG-SGH-I747 using xda premium
shortydoggg said:
I'd recommend forgetting about that tool kit for now. You should download the latest version of Odin v3.07, twrp recovery (tar file), and supersu.zip, and try doing everything manually; flash twrp through PDA from Odin, and supersu.zip through Twrp recovery if you get that far. The files are easy to find, so I'm not going to post links just yet.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
:good:thank you, I will give it a go and try it as you describe.
Fixed after almost 3 days!!!!
shortydoggg said:
I'd recommend forgetting about that tool kit for now. You should download the latest version of Odin v3.07, twrp recovery (tar file), and supersu.zip, and try doing everything manually; flash twrp through PDA from Odin, and supersu.zip through Twrp recovery if you get that far. The files are easy to find, so I'm not going to post links just yet.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
:laugh:FIXED!!!!!!!!!!!!!!!!!!!!!!!
I did what you said, but only after I figured out that I was using the wrong driver, correct device, wrong model. I used a USB driver cleaner, cleaned them all off, wiped the device, installed the driver and reconnected then I followed your instructions!:good:
I found these instructions on the AT&T Samsung forum for how to clean your drivers:
http://forums.att.com/t5/Android-Di...ix-for-Windows-7-at-least-for-me/td-p/3369515
Samsung Galaxy S3 MTP USB Fix for Windows 7(at least for me)!!
Post Options
11-30-2012 02:55:21 PM
Here's what worked for me after literally trying everything under the sun (compiled steps from various sources):
Steps to Safely Cleanup and Remove old USB Mass Storage Drivers on your PC
Shut down your computer. Unplug your USB storage devices: USB Disks, flash, cams, CD/DVD, etc.
==> Other USB devices like keyboards, mice and LAN adapters can stay plugged in
Boot computer back up. Click for how to determine whether you are running 32 or 64 bit Windows
Download drivecleanup.zip, unzip and save to your desktop. Move the 32 or 64 bit version of DriveCleanup.exe toC:\Windows\System32
Open a command prompt window as follows:
==> For XP only: You must have Admin privileges. Click Start->Run, enter cmd
==> For Vista and Windows 7: You must open an elevated command prompt window!
After the command prompt enter: drivecleanup.exe
==> Your command prompt window should be similar to my example below.
==> If, instead, you get an error message like Command not recognized it means you didn't move Drivecleanup.exe to the right directory
Reboot.
Download the latest USB drivers here:http://www.samsung.com/us/support/owners/product/SGH-I747MBBATT Click the tab at the bottom that says "Manuals & Downloads" then Software then the link for the Device(Install),USB Driver (Software) (ver.v1.5.14.0)
Intstall Drivers
Reboot
Unplugged or disable your internet connection ***CRITICAL***
On your S3 go to Settings>About device>Check for updates and install the update (eventhough we next do a hard reset the new firmware is worth it if only for the brightness feature added to the notification drop down).
Do a hard reset on your Galaxy S3 instructions for that here: http://www.hard-reset.com/samsung-galaxy-s3-hard-reset.html
Turn on S3 (without USB plugged in) and don't login to your Android account ***CRITICAL***
Plug in USB and it should install all the drivers at long last ***SIGH***
Login to your Android account with the USB plugged in and you should be good to go!
Thanks again for helping me out!
my android is partially rooted or partially unrooted
Before three days I was think to update my android.so I done to unroot my android.after update my device is not root again.it says failed again and again.i also try to unroot again but this is also says that root required first.how can I do.i want to root again.please help me.:crying:
Problem: Stuck on white/black screen, can't boot into recovery, able to boot into download mode
I recently returned my phone to stock following the return to stock tread (4.1.1), however, my first OTA update from ATT (4.1.2), after the install finished it stuck at boot up screen. And I can't get into recovery screen at all no matter what I try.
Tried to flash TW recovery
Tried to flash CWM recovery
no success, any help?
Edit, I noted whenever my phone is off, when plug in the charger/usb cable, my phone automatically goes into the black/white letter screen. WITHOUT touching any button what so ever.
On download screen
Current Binary: Custom
Systems Status: Custom
Use Kies to emergency recover back to stock 4.1.1.
Steps. (READ ALL BEFORE STARTING)
1.) Downloads Kies onto your pc
2.) Install drivers to pic
3.) Open Kies and go to TOOLS > instal/upgrade firmware.
4.) Kies will ask you for you device model. AT&T = SHE I317. And your serial number. Located behind the battery.
5.) Hit start in Kies it will down load the stock firmware to your PC. Follow the instructions.
6.) It will eventually ask you to put your phone in download mode and connect it to the pc. Do this.
7.) Don't touch it. It is going to take about 10-20 min depending on your Internet speed and your computer.
When it is complete your phone will be back to stock. The same it was the day you pulled it out of the box.
***I would also make sure you back up any data on your phone because it will delete the sd card. It is also wise to remove any external storage sd.
****when finished you can re root using cf auto root or take the OTA update to get you back to 4.3.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
kelpqq said:
Problem: Stuck on white/black screen, can't boot into recovery, able to boot into download mode
I recently returned my phone to stock following the return to stock tread (4.1.1), however, my first OTA update from ATT (4.1.2), after the install finished it stuck at boot up screen. And I can't get into recovery screen at all no matter what I try.
Tried to flash TW recovery
Tried to flash CWM recovery
no success, any help?
Edit, I noted whenever my phone is off, when plug in the charger/usb cable, my phone automatically goes into the black/white letter screen. WITHOUT touching any button what so ever.
On download screen
Current Binary: Custom
Systems Status: Custom
Click to expand...
Click to collapse
Did you get it working? Mine has the same issue. Sucks...
Kies does not work with a Note II.
hey! any solution, ???
KIes 3
I downloaded the newest version of Kies, it is called Kies 3. My note 2 connects to it easily. I have not had to try the emergency repair. Here is the link for it. Hope it helps.
http://www.samsung.com/sg/support/usefulsoftware/KIES/JSP
I used the above mention Kies procedure to return my phone to working condition. I was also stuck on the Samsung logo for hours. I tried flashing several backups in Clockwork mod several times for several hours. My sd card would not mount as well. I could use wifi but no phone service. During the Kies process it prompted me to do an emergency repair which I did but this was only after doing a factory reset, and cache wipe, and dalvik cache wipe. I followed the steps by ShrekOpher and my phone was returned to 4.1.2 stock. My new problem is that I made the mistake of updating to 4.3 OTA and now have a locked bootloader. Everything works perfectly except now I'm not rooted. Screen Mirroring works perfect which was the main reason for my misadventure. I'm wondering if I root manually will my screen mirroring be disabled like it was when I was on the unofficial 4.3?
Screen mirroring checks for rooted status and won't run if detected.
See bottom of post #2 here for a link to a solution to that...
http://forum.xda-developers.com/showthread.php?t=2589891
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
reply
cameron213 said:
Did you get it working? Mine has the same issue. Sucks...
Click to expand...
Click to collapse
I had the same issue. I pulled my sd card and battery for 30 seconds. Then it went into recovery with vol + home and power. Hope this helps someone.
hatgirl223 said:
I downloaded the newest version of Kies, it is called Kies 3. My note 2 connects to it easily. I have not had to try the emergency repair. Here is the link for it. Hope it helps.
Good morning friend, how I stay KIES fixed the error? as I try to do the tutorial provided here in the forum, but by placing the model and S / N, Kies indicated that I had no copy to restore. Just yesterday I stay in this mode.
Can you help me?
Click to expand...
Click to collapse
I have an i747 and after a week of research and trail and error I was able to get back to a factory working phone. I wanted to share my findings so that the next person may get up and running a bit quicker. First off, my phone was never rooted. I was getting it ready to sell and was going to factory reset it when I realized I forgot the system password. So I installed Kies and proceeded to factor rest it there. For whatever reason the reset did not take and after several failed attempts with kies the phone began to boot in ODIN mode. I built a USB jig and was able to get back into download mode but nothing would bring it back to life. Downloading the official rom from sammobile and flashing with ODIN3.07 would fail every time. Emergency recovery in kies also failed. So here was my final approach that worked. Maybe the wrong way to do this, maybe the long way to do it.. IDK.. but it worked for me..
1) get the official Samsung files from kies (google -"does kies store firmware")
2) boot do download mode
3) flash CSC file with auto reboot and F. reset time checked
4) boot do download mode
5) flash PDA file with auto reboot and F. reset time checked
6) boot do download mode
7) flash Modem file with auto reboot and F. reset time checked
* I closed ODIN between each step, might be overkill.
** I did not flash the bootloader file
I have read that it takes a long time the first boot, and I have been waiting 15 minutes at the SAMSUNG screen but it is still pulsing so i think it is still processing. If it is still at this screen in the morning, I will let you all know but this is further than I have been in over a week.
On a side note, when it crashed I took this into AT&T they told me over the past month or so they have seen numerous people with the same issue. All from doing a factor rest in Kies. My phone was out of warranty and they barely looked at it before asking me to upgrade. I took it to BestBuy and they fixed it from booting to ODIN mode but it still locked up on the AT&T logo, so I was back to square one.
Food for thought. How about waiting to see if your instructions actually work on your phone before posting them here for people with similar issues to use. Kind of useless if it doesn't end up working, huh?
lordblue969 said:
I have an i747 and after a week of research and trail and error I was able to get back to a factory working phone. I wanted to share my findings so that the next person may get up and running a bit quicker. First off, my phone was never rooted. I was getting it ready to sell and was going to factory reset it when I realized I forgot the system password. So I installed Kies and proceeded to factor rest it there. For whatever reason the reset did not take and after several failed attempts with kies the phone began to boot in ODIN mode. I built a USB jig and was able to get back into download mode but nothing would bring it back to life. Downloading the official rom from sammobile and flashing with ODIN3.07 would fail every time. Emergency recovery in kies also failed. So here was my final approach that worked. Maybe the wrong way to do this, maybe the long way to do it.. IDK.. but it worked for me..
1) get the official Samsung files from kies (google -"does kies store firmware")
2) boot do download mode
3) flash CSC file with auto reboot and F. reset time checked
4) boot do download mode
5) flash PDA file with auto reboot and F. reset time checked
6) boot do download mode
7) flash Modem file with auto reboot and F. reset time checked
* I closed ODIN between each step, might be overkill.
** I did not flash the bootloader file
I have read that it takes a long time the first boot, and I have been waiting 15 minutes at the SAMSUNG screen but it is still pulsing so i think it is still processing. If it is still at this screen in the morning, I will let you all know but this is further than I have been in over a week.
On a side note, when it crashed I took this into AT&T they told me over the past month or so they have seen numerous people with the same issue. All from doing a factor rest in Kies. My phone was out of warranty and they barely looked at it before asking me to upgrade. I took it to BestBuy and they fixed it from booting to ODIN mode but it still locked up on the AT&T logo, so I was back to square one.
Click to expand...
Click to collapse
Seems a pretty long route to take. If you are on an Odin flashable firmware version (e.g. 4.1.1), you only need to flash one partition - PDA. This updates all partitions to stock including bootloader, modem, recovery, kernel. The newer firmware versions - 4.1.2 & 4.3 are, however, not Odin flashable. Also, if you couldn't do a factory reset from settings because of password issues, you could have booted into recovery mode and done a factory reset there. This wouldn't require a password and would still have the same effect of wiping data and returning to factory settings.
If your phone is stuck at the Samsung screen for 15 minutes, then it's stuck. Reboot into recovery mode and try a reset there. If this doesn't work, then it means you have a soft brick you need to restore your firmware via custom recovery. Your phone is never hard bricked when you can get to download and recovery modes. Flash custom recovery via Odin in download mode. Reboot to custom recovery and flash a clean, complete stock image for 4.3. That's your best option now since you are selling
Larry2999 said:
Seems a pretty long route to take. If you are on an Odin flashable firmware version (e.g. 4.1.1), you only need to flash one partition - PDA. This updates all partitions to stock including bootloader, modem, recovery, kernel. The newer firmware versions - 4.1.2 & 4.3 are, however, not Odin flashable. Also, if you couldn't do a factory reset from settings because of password issues, you could have booted into recovery mode and done a factory reset there. This wouldn't require a password and would still have the same effect of wiping data and returning to factory settings.
If your phone is stuck at the Samsung screen for 15 minutes, then it's stuck. Reboot into recovery mode and try a reset there. If this doesn't work, then it means you have a soft brick you need to restore your firmware via custom recovery. Your phone is never hard bricked when you can get to download and recovery modes. Flash custom recovery via Odin in download mode. Reboot to custom recovery and flash a clean, complete stock image for 4.3. That's your best option now since you are selling
Click to expand...
Click to collapse
So like the true repository of knowledge we have here, Larry you are correct.. After about 30 minutes I decided it was really stuck.. So this time I watched the process I described above a bit more closely and as you stated the PDA file is all i needed.. but I had tried several from different sources including the office from sammobile and they always crashed. So what eventually worked for me was after being stuck at the samsung logo...
I booted into recovery mode
wiped the cache
factory reset it
then flashed with the Kies PDA file that I obtained in Kies in emergency recover mode.
This finally worked.
and as stated was a shorter route to take. The PDA that i used had 4.1.1 on it.
Thanks for the clarification in the fact that flashing with the PDA takes care of the bootloader, cache, file system, etc.
DMF1977 said:
Food for thought. How about waiting to see if your instructions actually work on your phone before posting them here for people with similar issues to use. Kind of useless if it doesn't end up working, huh?
Click to expand...
Click to collapse
excitement over came me.
Still having issues
Ok, keepers of knowledge.. I have a phone that will boot up but I have no baseband version. It shows unknown.. I have tried just flashing the modem file but i still do not get it back.. if I try to flash anything other than the official files from kies, ODIN fails. My phone is now at 4.1.1, build JR003L.I747UCDLK3.
If I try to update via wifi with the software updater, it says I am up to date. If I try to update with Kies, it fails..
I am at a loss...
Please help..
Thanks in advance..
I might have posted this on the wrong thread sorry:
Hello everyone,
Welcome to a series of unfortunate noob events;
All I wanted was to set my default storage to SD, since my Samsung Note 8 GT-N5120 only had 16 gb of internal memory.
I am aware that with my device, I can move apps to SD, but only a part of it gets moved, a huge chunk still stays in the internal memory (i.e 60 mb of an app goes to sd and 100mb of an app stays in memory).
So I searched online and all signs lead to rooting, in order to tweak my device to its fullest ;therefore, making the feature I want available at my disposal. And so I did, I followed tutorials correctly, from usb debugging mode to using odin. SuperSU was there and I downloaded Root Checker just to verify.
My device was working perfectly, but during bootup instead of a screen that shows the android with a pirate patch, it shows a static white screen before going into the samsung logo screen. I've searched through the forums and found out that other GT-N5120 owners had the same problem as well. It was no big deal and I didn't mind.
After that I searched online on things to do after rooting my device. It says install a CWM for better recovery options than what the stock recovery offers, so I did I used this tutorial: droidviews.com/root-and-install-cwm-on-samsung-galaxy-note-8-0-gt-n5100-gt-n5110-gt-n5120-all-models/
Everything was fine and I thought I was getting the hang of this thing, so I moved on to the next step and downloaded ROM Manager, to use a Custom ROM, I used this tutorial: androidtipsz.com/how-to-install-a-custom-rom-on-your-android-phone-using-rom-manager
This part got hazy,
ROM Manager asked me what version of CWM I am using and the options were: 2.0 or 5.x+, I picked the latter
and I was all set,I just needed a Custom ROM to use I picked Paranoid Android. Went to their site downloaded the .zip file that corresponds to my device and used ROM Manager to flash Paranoid Android, but it got to a screen that says my .zip file is for GT-N5120 your device is GT-N5110, which was weird because anywhere I checked on the device (including ROM manager, except when it gets to the said screen) says my device is GT-N5120.
This where the unorthodox noob of myself comes in:
Without hesitation I downloaded the Paranoid Android .zip for GT-N5110 and flashed it with ROM Manager. It worked, the tab still boots and Paranoid Android is running, but the tab got laggy and Google Store stopped running and Email stopped running and because of that, no games would work. SuperSU and ROM Manger didn't open too, I forgot the message tho. Keep in mind I did all this WITHOUT BACKING UP MY FILES igotrektnub
I looked everywhere for a solution to revert without deleting all my files, Ive decided to download the Stock Rom for GT-N5120, the only problem was there were GT-N5120 Stock Roms from different regions, I think that my tablet was from the Sweden Region so I went ahead and downloaded that.
Question#1
Should the Stock Rom I use be region specific? If so how would I check which region my device came from?
So I went to Odin Mode again and flashed this MD5 file:N5120XXDNE4_N5120AUTDNF1_N5120XXDNE4_HOME.tar
it was ok but it got stuck on system.img for a good 2 hours or so? So I did the unthinkable, turn off the device...
After that every time I turn on my device it just boots to the white static screen and never gets past it, I can still go to download mode and recovery mode, but thats about it. I think my recovery mode went back to stock. I tried flashing the root files CF_Auto but it didnt do anything, the same for the CWM, I went into recovery mode factory reset and data wipe and cache wipe, but it still wont get pass the static white screen.
Please help, Ive read somewhere that as long as it still boots download mode, it can still be fixed.
Sincerely,
Nubdatgotrektbyhimself
Please help, I think I made an unusual mistake, all I want is to be able to use the tab again
Could I flash something to make this work again?
Ok so I got it fixed
1. I downloaded a stock rom 4.4.2 from sammobile, its region is unknown and the .md5 file has this name: N5120XWDNE3_N5120OJVDNE3_N5120XXDNE4_HOME.tar
2. Went into download mode flashed it with odin and got stuck at cache.img (passes the cruel system.img)
3. Turned off my device and went into download mode again, flashed this file: CF-Auto-Root-konalte-konaltexx-gtn5120.tar
And now its working again.
*Note: while extracting the .rar file from sammobile make sure you extract .md5 and .dll into the same folder before proceeding with odin.
the noob managed to revert
gtn5120getrektnub said:
Ok so I got it fixed
1. I downloaded a stock rom 4.4.2 from sammobile, its region is unknown and the .md5 file has this name: N5120XWDNE3_N5120OJVDNE3_N5120XXDNE4_HOME.tar
2. Went into download mode flashed it with odin and got stuck at cache.img (passes the cruel system.img)
3. Turned off my device and went into download mode again, flashed this file: CF-Auto-Root-konalte-konaltexx-gtn5120.tar
And now its working again.
*Note: while extracting the .rar file from sammobile make sure you extract .md5 and .dll into the same folder before proceeding with odin.
the noob managed to revert
Click to expand...
Click to collapse
Hey man, glad you got it sorted out. Just saw this now, otherwise I would have tried to help you sooner. Anyways, yes as long as you can get to download mode then you can always Odin flash the proper official firmware for your specific device from sammobile.com. That gets you back to normal every time. Now that you're up and running, you can root, install CWM recovery, then boot to recovery and make a backup. Now wipe cache and dalvik (note: if you want to "clean" flash instead of "dirty" flash, then also wipe system and data), and then flash a compatible custom rom (that you've previously downloaded to your device) through recovery. Reboot once it's done installing.
If something goes wrong then you can simply reboot to recovery and restore your backup. Always make a fresh backup before flashing a new rom, mod, etc, because restoring a backup is easier than having to Odin official firmware and start over from scratch.
Cheers
I have a galaxy note 3 which is stuck on the Tmobile splash screen.
I am not sure if this phone is rooted or not.
I don't want to wipe the phone because there is contacts and things which need to be recovered.
We can get into recovery mode, but not into Safe mode.
Can someone provide some tips?
If your contacts are synced with a Google account, they should appear if you sign in on another phone.
Flashing a ROM to a phone will carry risks; therefore, no matter what you do, you may wind up losing all of the data. That being said, you could try reflashing the stock ROM with Odin and it may boot without wiping.
You could also flash TWRP to the phone, boot into TWRP, mount the data partition, connect it to a computer, and copy off the data. Alternatively, you could try and copy information from the phone to a micro SD card in TWRP.
Did you fix your issue? I had this problem when....
Flash Fix said:
I have a galaxy note 3 which is stuck on the Tmobile splash screen.
I am not sure if this phone is rooted or not.
I don't want to wipe the phone because there is contacts and things which need to be recovered.
We can get into recovery mode, but not into Safe mode.
Can someone provide some tips?
Click to expand...
Click to collapse
I hope you have fixed your issue by now however if not then please try this.
1. Remove your battery from the phone
2. Hold your phone (volume down button + home button) then slide the battery in and power the phone. *Note you must hold the (volume down button + home button) until you get the warning about installing custom OS.
+Once you reach Warning OS page, at this point Oden should see your phone so you can download a custom recovery like CWM / TWRP
3. Download (Oden + Device Drivers & TWRP) --- I just found out that I need to post 10 times before I can link to outside files so I hope you get the links. If not then PM me and I will try to send directly to you.
HTML:
https://download.chainfire.eu/354/CF-Root/CF-Auto-Root/CF-Auto-Root-hltetmo-hltetmo-smn900t.zip
CF-Auto-Root which includes your phones correct Oden version
https://dl.twrp.me/hlte/twrp-2.8.7.0-hlte-4.4.img.tar"]TWRP.
4. Extract the CF-Root folder you downloaded using 7zip and you will see Oden. Install Oden on your PC.
5. Connect your phone to your computer and look for a so your connected to Oden and then flash TWRP .tar file to your phone. Once it flashes then your phone should reboot automatically and you should have access to your old data.
This happen to my Note 3 T-Mobile phone when I was trying to flash the wrong versions. If you are confused about the directions then I will do my best to make a video for you. It might take me a day or two to respond with the video. Hope this helps! Let me know how it works out or if you have any questions.
Also, once you gain access to your phone again I recommend taking a look at some of the ROM's on this website! There are some developers who have put quality time into making their ROM's SOLID working systems.
Always remember to give support as this is what makes this community attract real talent!
I do not recommend CWM as it is very outdated.
Rooting is not required to flash TWRP, only Odin and the tar version of TWRP.
The phone can be rooted by flashing supersu from TWRP too.