[Q] SGH-T999 Rooting issues with KNOX - T-Mobile, Samsung Galaxy SIII

I am completely new to the whole rooting thing, but I decided to try rooting my T-Mobile Galaxy SIII (which is running Android 4.3) because I wanted to put CyanogenMod on it. I followed this guide:
Step 1: Extract CF-Auto-Root and Odin 3.07 files using winrar/7zip/winzip or any other extracting tool.
Step 2: Switch off the Galaxy S3. Then boot the device into Download Mode by pressing and holding Volume Down, Home and Power buttons together until a construction Android robot icon with a warning triangle appears on screen. Now press the Volume Up button to enter Download Mode.
Step 3: Launch Odin on the computer as an Administrator.
Step 4: Connect the Galaxy S3 to the computer using USB cable while it is in the Download Mode. Wait until Odin detects the device. When the device is connected successfully, the ID: COM box will turn to light blue with the COM port number. Additionally, the successful connected will be indicated by a message saying Added.
Step 5: In Odin, click the PDA button and select the CF-Auto-Root-d2tmo-d2tmo-sght999.tar.md5 file.
Step 6: Verify that Auto Reboot and F. Reset Time checkboxes are selected in Odin. Also, ensure the Re-Partition option is NOT selected.
Step 7: Double-check and click Start button in Odin. The installation process will now begin.
Step 8: Once the installation process is completed, your phone will restart and soon you will see a PASS message with green background in the left-most box at the very top of the Odin. You can now unplug the USB cable to disconnect your device from the computer.
There is only one thing I did differently than what the guide said was to install SuperSU before I did the root. The root completed successfully; however, SuperSU crashes whenever I try to launch it and KNOX puts a warning in my notifications tray. I never installed or launched KNOX prior to performing the root and I cannot update or remove SuperSU. I also cannot install or remove KNOX. I've been browsing forums and looking for answers but I can't understand half of the things people are saying. Does anyone have a noob-friendly solution? (By the looks of it, there are many people with similar issues due to KNOX.)
Thanks in advance.

I had been trying to figure out this same problem for days. Finally got it last night.
Just like you, I had been trying to use the CF autoroot method on my tmo s3 (4.3). Ran into the same "Unfortunately SuperSU has stopped." It seems as though CF autoroot and Knox don't play nicely. You might try using TWRP recovery instead of CF. I ended using the TWRP 2.5.0.0 to root via Odin. Success! Also, I was having troubles with my pc, so you might try to switching machines if you're still having trouble.
Here's a great guide on how to do this by @cLogic, who took @upndwn4par's method and refined it for T-Mobile. http://forum.xda-developers.com/showthread.php?t=2563955
Hope it helps!

Related

restoring Continuum to stock DL17

DOWNGRADE BEFORE I COULD UPGRADE
I had to jump through a lot of hoops to help a friend upgrade their Samsung Continuum (on Verizon) to the new Froyo 2.2.2 (EC09). I had previously rooted the phone, which was still on DL17, and that was now crashing the official upgrade. So I thought I'd document what finally worked, for anyone else who's struggling with the same. Not guaranteeing my procedure will work, of course.
Mostly, I've summarized and rewritten the other instructions I found buried in and amongst the other discussion threads. After successfully restoring 'stock' the official Froyo upgrade finally worked.
PRE-REQUISITES
- locate the thread, [DEV] Continuum DataBase [EC09][DL17][EC03][EC07]
- download the following files:
Samsung i400 USB driver
"DL17 Factory stock rom+radio+kernel (odex) all in one odin flash"
(the resulting unzipped file is 'Continuum-Stock-DL17.tar.md5')
ODIN flash-tool
- download the updated "EC07" PIT file (the "DL17" PIT didn't work for me!)
Samsung_I500_VZW_PIT.PIT
PROCEDURE
Install the Samsung i400 USB drivers
Remove battery from phone (not sure if this is necessary but some threads advised it, and after several failed attempts I was desperately trying everything. In any case, it didn't interfere with a successful imaging!)
Connect the phone on USB
Hold VOL-DOWN plus PWR buttons until the built-in 'Flashing' screen appears (should be immediate)
Confirm that the computer detected the phone over USB
If not, re-run the Samsung USB Driver install and select 'Repair')
run ODIN
Confirm that there is a yellow 'COM' status showing in the top-left.
If not, ODIN isn't connected to the phone!
Click on 'PIT' button and select the 'Samsung_I500_VZW_PIT.PIT'
UNCHECK the checkbox option for 'Re-partition'
Click on 'PDA' button and select the 'Continuum-Stock-DL17.tar.md5' file
Click START
You should see a steady stream of status updates in the bottom-left window as well as a progress bar in the top-left (labeled "factoryfs")
The update should take about 10 minutes, then the phone will reboot. The reboot takes about 2 minutes and there is nothing shown on the phone!
NOTES
I originally tried using the (DL17) 'SCH-i4000-VZW-Continuum.pit' but it didn't work.
I also tried it both with and without the re-partition option; neither worked
At one point the phone stopped being recognized on USB. I simply re-ran the Samsung USB Driver install and selected 'Repair'. Then the phone was recognized again.

SGS3 Connection Issues and Download Mode Help

There are three parts to this thread - How to get into download mode, how to get into recovery mode, and how to solve problems connecting your Android device to your computer. I think you should be able to find where each one begins without too much trouble.
----------------------------------------------------
GETTING INTO DOWNLOAD MODE
----------------------------------------------------
"Just get into download mode and..."
Ever find yourself with a phone that's misbehaving, and you can't seem to figure out how to get it to download mode?
Here's a list of things to try, sorted in a "where are you now" setup:
Note: You will need to use Vol+ to select download mode after you reach the mode selection screen.
FROM A POWERED-DOWN STATE - BATTERY REMOVED
- Insert battery, then press and hold Vol-, Home button, and Power.
- Press and hold Vol-/Home/Power, Insert Battery.
- Use a USB jig (can be manufactured jig or homemade chain of resistors)
FROM CLOCKWORKMOD RECOVERY MENU
- Position the cursor (highlighted selection) on "Restart device", hold Vol-/Home, then press power
- (Where available) Use the "Reboot Download" option in the "Advanced" menu
FROM A FULLY BOOTED PHONE STATE, WITH USB DEBUGGING ENABLED
Note: you may need to have ADB installed on your computer, and/or an Android Terminal Emulator installed on your Android device.
- Connect your Android device to your computer, navigate to your ADB directory, and type "adb reboot download"
- (Where available) Use the rom's power menu option to reboot into download mode.
- From a terminal, type "su", then "reboot download"
- Download the app "quickboot", follow the app directions to reach download mode.
----------------------------------------------------
GETTING INTO RECOVERY MODE (CWM RECOVERY)
----------------------------------------------------
FROM A POWERED-DOWN STATE - BATTERY REMOVED
- Insert battery, then press and hold Vol+, Home button, and Power.
- Press and hold Vol+/Home/Power, Insert Battery.
FROM A FULLY BOOTED PHONE STATE, WITH USB DEBUGGING ENABLED
Note: you may need to have ADB installed on your computer, and/or an Android Terminal Emulator installed on your Android device.
- Connect your Android device to your computer, navigate to your ADB directory, and type "adb reboot recovery"
- (Where available) Use the rom's advanced power menu (long press power in android OS) option to reboot into recovery.
- From a terminal emulator, type "su", then "reboot recovery"
- Download the app "quickboot", follow the app directions to reach recovery mode.
- Download the app "Rom Manager", select "Reboot to Clockwordmod Recovery"
----------------------------------------------------
UNIVERSAL FIRST STEPS FOR CONNECTION ISSUES
----------------------------------------------------
So you've got Odin up, the phone's in download mode, it's connected to the computer, but Odin is saying "What phone?". You've tried jiggling the handle, checking the blinker fluid levels, and even using the board stretcher, but the Android guy is smirking at you with that smug green face.
Although it is possible that there is something else at work that's preventing your phone from connecting, I would suggest trying these "universal first steps" to see if you can resolve the connection issues:
1. Turn off both devices (phone and PC) - and I do mean full power-down. Go ahead and pull the phone's battery, if necessary.
2. Disconnect your phone from your computer at all points - USB out of phone, USB out of computer.
3. Start up your computer. Don't touch it, don't do anything to it. Let it fully boot and completely settle.
(Obviously, log in if it's necessary, but then let it finish booting before moving on to step 4.)
4. Start up Odin. Let that get completely started and settled.
(If on Vista/Win 7, make sure to "Run as Administrator" in the right-click menu.)
5. Connect your USB cable to a different port than the one you last had it connected to.
(If you're on a Windows desktop, the ports in the back of the computer are generally more stable and should be used. If you're on a laptop, use USB port #1)
Do not connect the phone to the cable yet.
6. Start your phone in download mode. Wait until you see the Android guy with the 4-5 lines of text in the upper left corner.
7. Connect your cable to the phone. Let it sit until Odin recognizes it (which should only take a couple of seconds).
If, for some reason, Odin doesn't recognize the phone at this point, here are a few more things to check/try:
- Repeat steps 1-7 above, making sure to change USB ports. As dumb as it sounds, sometimes the phone or computer just doesn't like particular USB ports.
- With everything still up, switch USB ports.
- Try a different OS (if possible) - sometimes Ubuntu will recognize what Windows won't, and vice versa.
- Try doing this on a different computer - again, different OS, different USB ports, they're all links in a chain and sometimes you'll come across a configuration that doesn't have the weak link.
- Try a different cable. I've had a case where I couldn't do any flashing with one cable, but everything was rock-solid and smooth on the same machine with just a different cable.
- Fully uninstall your drivers, reboot the computer, reinstall the drivers, power down, and then start again from step 2. Sometimes faulty drivers are the problem.
--------------------------------------
Additional Note:
If you're moving from an AOSP-based rom (MIUI, CM10, etc) to a Touchwiz-based / Samsung Stock-based rom, remember to wipe data / factory reset prior to flashing a stock rom. You will hang on the "Samsung" logo if you don't.
Please note very carefully, though, to do the wipe in CWM recovery - not 3e recovery. If you do it in 3e recovery, you'll format the internal storage, meaning you lose all your pictures, music, etc.. (I learned this the hard way.)
--------------------------------------------
If anyone has any additional items / corrections, please reply and I'll update the OP accordingly. Thanks.
Reserved
Great guide!
I'd like to add my experiences, while using CWM 6.0.1.2 booting into Recovery is a bit tricky. It appears the default recovery boots instead of CWM. The only work around I know of is to Flash ClockworkMod Recovery first from ROM Manager v5.0.2.0 and then select Reboot into Recovery. Any other method I try seems to fail.
I'm running Stock At&t ROM, rooted.
Hey Mrhaley,
I just found your post. Wish I knew I had to wipe data and factory reset before flashing stock rom... well I followed another post to use kies and now Im stuck. Im hanging on samsung logo. Can you help me fix this?
Thanks
djtiko said:
Hey Mrhaley,
I just found your post. Wish I knew I had to wipe data and factory reset before flashing stock rom... well I followed another post to use kies and now Im stuck. Im hanging on samsung logo. Can you help me fix this?
Thanks
Click to expand...
Click to collapse
OP thanks for exelent post..I had one more problem with USB connection. Sticks in usb port did not connect correctly. Just jently squize USB male connector on samsung data cable so top of male connector will bend just enough to get good connection when you push back to PC port.
@djtiko - I answer on other post to your problem..
djtiko said:
Hey Mrhaley,
I just found your post. Wish I knew I had to wipe data and factory reset before flashing stock rom... well I followed another post to use kies and now Im stuck. Im hanging on samsung logo. Can you help me fix this?
Thanks
Click to expand...
Click to collapse
Do a factory reset again, should fix you up. If not, consider using Odin to flash a stock ROM package.
Thanks got it all fixed, just had to do a data wipe in the stock recovery and then I was golden
ondin
Hey guys when i run the bootloader file should i open it up in the pda tab on ondin or in the Bootloader tab?
Should be in the pda tab I believe.
Edit. Which bootloader file are you referring to? To know for sure, you could just flash the entire stock rooted jelly bean Rom.
If using Odin with Chainfire to auto root just to root I found that the file that you are using to root you HAVE to have in the SAME folder I made the mistake of downloading the Odin then Odin with chainfire from http://forum.xda-developers.com/showthread.php?t=1963790 then was opening the odin first downloaded then it would stall for not able to start the installation then rechecking the unzipped folder for the .tar.md5 file noticed that Odin was there too, loaded it and PRESTO rooted in less than 30 seconds... So for other that are just looking to root give chainfire a check, yes you would need to use the triangle away if you are worried about that however you don't loose anything when doing it this way so all a matter of what you are looking to do. THANK YOU so much for the help with the drivers issues!

[SOLVED] "'Firmware upgrade encountered an issue." Softbrick issue

Hello XDA!
So, idiot that I am, I decided today would be a great time to root my Galaxy S III (SGH-T999N version). It was running Jellybean 4.3, so it had fewer root options than other, older Jellybean versions, but I still found a root file on here. I put it into USB debugging mode, downloaded the driver, Odin, and the root file. I also backed the phone up on Kies, and have that on my PC., I did everything right, and... it failed. I tried again without doing anything to the phone (read: kept it in download mode), but it failed again with a different root file. So, I turned it off, sad that I wasn't able to root it, and I came upon the dreaded 'Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again' screen.
After hours of searching, I saw two different solutions: downloading the 4.3 OS from online, and using Odin to flash that to the phone, or using Kies to reformat the phone. I've been trying Kies, but Kies 3 isn't recognizing the phone, and won't allow me to restore or to reformat the phone. I'm still waiting on the download of Jellybean 4.3 to finish so that I can try that (Odin HAS been recognizing the phone). While I wait, I wanted to know if other users have had similar problems that they've solved, or where I've gone wrong, and what I can fix.
As for additional details:
- I CAN put the phone into Download mode. I CANNOT do a factory reset through Vol. Up+Home+Power
- The status screen with 'Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again' also has this information at the top:
ODIN MODE
PRODUCT NAME: SGH-T999N
CUSTOM BINARY DOWNLOAD: Yes (1 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 0
BOOTLOADER AP SWAREV: 1
- The phone is carried by Metro-PCS
Thanks in advance!
Okay, turns out the downloaded Jellybean 4.3 OS did the trick. For future people who run into this issue:
1. Have Odin 3.07 or higher downloaded (Odds are that you have this due to your phone's current state).
2. Download a copy of the OS you want from here: samsung-updates.com/device/?id=SCH-I535 Go to the dropdown menu on the left-hand side, and select your phone. Don't know/remeber your phone's identifier? Open up the back, remove the battery, and there should be a white sticker with your phone's model at the top. WARNING! Unless you plan to pay, these downloads will take a while. Do this when you can have your computer on for 4+ hours.
3. Once the download is complete, unzip the file, and place it in a location that you can easily find with Odin.
4. Open Odin, and make sure that Auto Reboot and F. Reset time are the only options checked. If there are other options selected, uncheck them and proceed.
5. Click the "PDA" button, and select your copy of the Android OS from where it was stored. Assuming everything has gone correctly, a message should appear in the Odin status box along the lines of "Check MD5... Do not unplug the cable...". Wait for the message "Leave CS..." to appear before proceeding.
6. Once "Leave CS..." has appeared, put your phone into Download mode (Turn it off, then restart by holding down the Vol. Down, Home, and Power keys until you get a screen that has informed you that you are in download mode.). Then, plug your usb cable into your PC/Laptop, and then into the USB outlet on the phone.
7. Once Odin has noted that your phone is attached, you can press "Start", and assuming all steps have been followed correctly, the new OS should download, and your phone will reboot, fully functional. If you are lucky like me, it will even have kept all of your settings!

[Q] Someone Help Me restore my phone to factory

I've been online all day trying to find a way to restore my phone after my brother installed cyanogenmod on it. It's not showing on odin and I am getting really upset. Its a note 2 from koodo and I've only had it for two days. (I got it as a birthday gift and my bro thought that cyanogen would be "cool" Can someone give me a foolproof step by step guide on restoring my phone to default.
Hey !
Are you looking for a Step by Step guide ?
I am not sure if you will find one right here ! Btw you can use search button to search for it !
However,
You can do this:
1) Go to sammobile.com, click on "firmaware", search for your phone on the right search box.
2) Download the Official Firmware. When download finished, extrat it somewhere.
3) Download ODIN
4) Install Samsung KIES (it includes USB Drivers) if Kies is already reinstalled, then uninstalled, reboot and reinstall back.
5) Go to download Mode (When powered off: press Volume UP, Home and then Power button and finally Volume Up again)
6) Flash the firmware.
Note: You may change USB Cables, USB Ports (of your Computer) or even Computer if Odin won't detect your Phone !
Alternative Way: If the Phone is switching on, then Download This great app !
When installed, just open it and will installed a flash kernel automatically. After that, just click "Open Tar/MD5/ZIP" then look for your firmware and then click "Flash Firmware".

Samsung Galaxy S4 ACTIVE shv-e470s Rooting Guide

Use this tutorial only with the Samsung Galaxy S4 ACTIVE shv-e470s smartphone.
CAUTION:THIS ROOTING METHOD IS ONLY FOR THE KOREAN VERSION SHV-E470S!!!
It was tested successfully on Samsung Galaxy S4 Active SHV-E470S Android version 4.2.2
Firmware version:E470SKSUANA1
Abstract:
Do not attempt to root any other smartphones with the files that you wil find in this articles.
This tutorial is destined to be used by advanced Android users.
I won’t be blamed in case you brick the phone or lose any data in the process!!!
Rooting the Galaxy S4 ACTIVE SHV-E470S will revoke its warranty. If you want to restore your phone's warranty then you will need to flash an official Samsung Android ROM OS.
Pre-requisites :
Download and install the Samsung USB Drivers on your computer
Disable Samsung KIES program if you have it installed on your computer
Disable any antivirus applications from running on your computer
Enable USB Debugging from Developer Options.
If Developer Options doesn’t appear in Settings, then you need to enable it.
go to Settings, then More, open About Device.
tap seven times on the Build Number.
you will now be enabling Developer Option, go back to main Settings section, scroll down and enable USB Debugging
Check your phone’s battery and make sure that there is at least 50% left before the device switches off
Read the entire post, don’t skip any steps and the guide should be completed in under ten minutes with success.
In case you have trouble completing the guide, then you are free to ask for extra help in comments
Download required files (see attachments)
Odin3 1.85
UPDATE-SuperSU-v1.93
unofficial_philz_touch_6.12.8-e470s
Process:
1. Copy the "UPDATE-SuperSU-v1.93.zip" into your phone internal or external memory
2. Extract the contents of the Odin zip file and place them on your computer’s desktop screen.
3. Power off the Galaxy S4 active shv-e470s now.
4. After that you have to boot the device in Android Download Mode (press and hold: volume down,home and power buttons}
5. Launch Odin on your PC as administrator
6. Connect the phone with your computer via USB cable.(make sure antivirus+firewall is now disabled!!)
7. Wait for ODIN to detect your device,(you should see the "added" message) then continue to the next step.
8. If the phone is not recognized by your PC, then you should re-install the Samsung USB Drivers.
9. Go to ODIN’s main window, click on PDA and then find the "unofficial_philz_touch_6.12.8-e470s.tar" Load it in ODIN.
10. Do not change any other Odin default settings
11. Make sure that the Re-Partition option is not enabled
12. When ready, hit the START button for the process to begin.
13. Don’t press any buttons until the process is complete
14. When ODIN completes the process it will show the PASS alert, then the phone will reboot in normal mode. You can unplug the device from PC when the Samsung Galaxy S4 active shv-e470s boot animation screen loads.
15. Now power off your phone again and boot in recovery mode (press and hold: volume up,home and power buttons)
16. Once in recovery mode,find and install the "UPDATE-SuperSU-v1.93.zip" .To do this,in the recovery menu choose the "install zip" option and then find the directory u have saved the zip file and choose it for installing.
17. Wait for the process to finish and then ur phone will reboot.once reboot u can download "root checker" from play store and verify that u have root access.
18. Have fun and enjoy your rooted SHV-E470s
Did anyone try with E470SKSUAND1 yet?
story said:
Did anyone try with E470SKSUAND1 yet?
Click to expand...
Click to collapse
I tried and it works.
req new download links
The download links has expired . please give me another links.thx
This phone is update to 4.4.2. Are we can't root our phone such as #1?
new files
nickserbanoiu said:
The download links has expired . please give me another links.thx
Click to expand...
Click to collapse
hello my friend....i just renewed the files.
Thanks you !
how about 4.4.2 root, can we use this tool to root?
story said:
I tried and it works.
Click to expand...
Click to collapse
Hi, I also have E470SKSUAND1, but my recovery mode only shows me 4 or 5 options, no install zip option. I looked for the cwm but the shv e470s isn´t supportet yet. How did you do it?
Hi, I need pit file for this phone or 2gb system dump. Pls help me. My phone is brick now.
shv-e470s
Thanh_GSM said:
Hi, I need pit file for this phone or 2gb system dump. Pls help me. My phone is brick now.
Click to expand...
Click to collapse
Bro!! did you repair your shv-e470s boot-loader ?
i have hard bricked my shv-e470s any help?
Does anyone try on E470SKSUCOE1? (lollipop 5.0.1)
Bump for lollipop E470SKSUCOH1 rooting...
Hi, I downgrade my Samsung Galaxy S4 Active (SHV-E470s) from Android 4.4.2 kitkat to Android 4.2.2 JellyBean, Odin says "PASS", it means i successfully flash the 4.2.2 jellybean firmware, then I try to reboot my phone, nothing happens, It won't turn on, I try to charge it but no response, no vibration, it is like completely dead, It is Hard brick? How can I unbrick and revive it? Thank you.

Categories

Resources