SPH-L520 NJ1 update question - Galaxy S 4 Mini Q&A, Help & Troubleshooting

SPH-L520 NJ1 update question - Galaxy S 4 Mini Q&A, Help & Troubleshooting

I have obtained a Sprint s4 mini. From what I can find, the current kernel is SE secure enforcing.
The exact build number is KOT49H.L520_4.4.2_0016
Build date is Oct 7 2014
I am not new here, I know that all known root methods are now bust. What other options are there?
Searching seems to be pretty difficult for this device. All searches for bootloader and recovery come up for the i9190 / i9195
If I use Kies or Odin to flash a previous recovery image, will that brick the device? Also in the settings, it says Secure Boot Status - Type: Samsung
Guess that is referring to the Knox enforcing
The particular image I had in mind to flash with Odin is SPR-L520VPUAMK2-20131115204826
Will it work? Or am I screwed?

Well no one was able to answer my question, so I had to figure it out on my own. Hopefully the following information will be of help to someone else without spending 36+ hours digging through the internet for answers.
You CAN fix your phone it you are on the NJ1 kernel. This is NOT a guide to fixing a bricked phone, although it may fix that too.
If you are on the NJ1 kernel, there are no root methods currently available. You MUST be on NE3 or lower. I also attempted to flash the custom recovery through Odin, but after a reboot it was as if I did nothing. No Knox flag, no warranty trip, no custom recovery.
Here is what I did to get custom recovery and root:
READ THIS BEFORE ATTEMPTING STEP 1.
This is only for the Sprint variant of the S4 Mini. Model number SPH-L520
Your Warranty could be voided. Proceed if you like. (More info on steps 5 and 6)
I had a horrible time getting the downloads from Sammobile. You WILL have to create an account and login to download files. I could not find any working links for the firmware below except for this site. Register a user name and password, DO NOT UNCHECK THE BOX that says receive emails from Sammobile OR YOU WILL NOT GET YOUR REGISTRATION EMAIL. On the Register page it is at the bottom. After you register, check your email and click on the link to complete the registration.
Close all your windows that are open to sammobile.
You are going to want to download Internet Download Manager in order to download files from Sammobile. After many many attempts to download the firmware from Sammobile, all tries failed. YOU ARE GOING TO NEED IDM to get a reliable download.
Download IDM ---> https://www.internetdownloadmanager.com/download.html
Install it and follow these directions to enable resume downloads in IDM ---> http://forum.xda-developers.com/showthread.php?t=2765456
If you do not do the steps above, you most likely will have failed download after failed download.
Even after setting this up, the firmware download failed on me twice. I deleted it from the download list in IDM and started it again.
IDM integrates well with Internet Explorer. Kinda buggy with Chrome. I would suggest using IE for the rest of this Tutorial.
Ok, now that you have that squared away, move on to step 1
_________________________________________________________________________________________________________________________
1) Flash your phone back to NE3. You can get that here ---> http://www.sammobile.com/firmwares/download/31482/L520VPUBNE3_L520SPTBNE3_SPR/ (click Regular Download, then on new page right-click Confirm Download and click SAVE AS. After that the IDM window should pop up. Just Start Download)
Also go ahead and download download the NJ1 in case things get rough. List of all firmwares here ---> http://www.sammobile.com/firmwares/database/SPH-L520/
2) Download and install the Samsung drivers ---> http://www.mediafire.com/download/a4hd8y0c1iakysk/Samsung-Usb-Driver-v1.5.49.0.exe
Download Odin 3.09 ---> http://androidhost.org/PVAIv
Unzip Odin to a folder or desktop. Do not run it from in the zip folder.
3) Run Odin 3.09.
Reboot your S4 Mini SPH-L520 into download mode. Turn phone off > Hold Volume Down, Home Button, and Power Button all at the same time. Wait for the phone to buzz and the pop up on the screen. Release the buttons and press Volume Up to confirm.
Now plug in your phone to your computer. It might take a few seconds for the drivers to install. Wait until Odin shows blue color in the first bar on the left side. Should say 0:[COM3] (the COM number will be different depending on your computer and the USB port you plugged it into)
VERY VERY IMPORTANT! Make sure that the AUTO-REBOOT and F. RESET TIME boxes ARE checked. Make sure that the RE-PARTITION box is NOT checked.
4) Unzip the NE3 download from earlier. Click on the AP button in Odin and navigate to where you unzipped NE3. It should be a .MD5 type of file
Give Odin a few mins to check the file. It may appear that Odin has hung up, just be patient.
After Odin has run the check, it should say ok in the little window on the bottom left. Now click START and wait.
DO NOT bump the phone, the laptop, the usb cord, and MAKE SURE THE BATTERY DOES NOT FALL OUT!!!
After Odin is done flashing, it will reboot the phone. After the initial reboot, the phone will reboot itself once more. Be patient
Now wait for the phone to completely boot up.
5) After you have got back to ME3, you can follow this guide to root it ---> http://androidxda.com/root-samsung-galaxy-s4-mini-sprint-sph-l520
You already have most of the files you need. Just follow the instructions and download what you do not have already.
By the way, in Odin the AP button and the PDA button are the same
(This method should not trip the Knox counter, but I am unsure. Mine was already tripped before all of this)
OPTIONAL (this will trip the Knox counter and lose warranty status)
6) Now you can use this guide to install the custom recovery ---> http://techbeasts.com/2014/05/04/in...-root-sprint-samsung-galaxy-s4-mini-sph-l520/
Again, you already have most of the files you need. DL what you don't have.
_________________________________________________________________________________________________________________________
I am planning on instaling CM11 ---> http://forum.xda-developers.com/showthread.php?t=2669991
This ROM apparently needs a specific recovery in order to work properly. I installed that one instead.
MAKE A BACKUP IN THE RECOVERY OF THE STOCK ROM BEFORE FLASHING ANY CUSTOM ROMS, or else be sorry later.
This is about as simplified as I could get it. Hope this helps out those of you that were as confused as I was.
I will not be providing support. Simply do not have the time. There is more than enough info here to help you figure out what to do.

fire3element said:
I have obtained a Sprint s4 mini. From what I can find, the current kernel is SE secure enforcing.
The exact build number is KOT49H.L520_4.4.2_0016
Build date is Oct 7 2014
I am not new here, I know that all known root methods are now bust. What other options are there?
Searching seems to be pretty difficult for this device. All searches for bootloader and recovery come up for the i9190 / i9195
If I use Kies or Odin to flash a previous recovery image, will that brick the device? Also in the settings, it says Secure Boot Status - Type: Samsung
Guess that is referring to the Knox enforcing
The particular image I had in mind to flash with Odin is SPR-L520VPUAMK2-20131115204826
Will it work? Or am I screwed?
Click to expand...
Click to collapse
Can you help me to backup your first partition on your phone and send to me. You can use EFS Professional on xda.

Hmm....I installed the NJ1 update through Odin. And then flashed the CF auto root (or maybe it was the recovery.tar) with no issues. I did this when NJ1 was first released.

NCTP2 said:
Hmm....I installed the NJ1 update through Odin. And then flashed the CF auto root (or maybe it was the recovery.tar) with no issues. I did this when NJ1 was first released.
Click to expand...
Click to collapse
Can you backup your phone by EFS Pro and send to me. Thanks.

NCTP2 said:
Hmm....I installed the NJ1 update through Odin. And then flashed the CF auto root (or maybe it was the recovery.tar) with no issues. I did this when NJ1 was first released.
Click to expand...
Click to collapse
I was unsure about it considering all the changes with SE Secure and Knox. Always pays to be safer than sorry. I could not find any reports of this anywhere after hours of reading and searching. Thanks for confirming though. :good:
quanqw said:
Can you backup your phone by EFS Pro and send to me. Thanks.
Click to expand...
Click to collapse
I am sorry, I have been really busy. What exactly are you trying to do? Asking someone to backup sensitive data from their phone and share it to a stranger can be alarming.
At least tell us what is going on or why you need the backup.

worked
fire3element said:
I was unsure about it considering all the changes with SE Secure and Knox. Always pays to be safer than sorry. I could not find any reports of this anywhere after hours of reading and searching. Thanks for confirming though. :good:
I am sorry, I have been really busy. What exactly are you trying to do? Asking someone to backup sensitive data from their phone and share it to a stranger can be alarming.
At least tell us what is going on or why you need the backup.
Click to expand...
Click to collapse
thanks alot
the baseband nearly killed me but i thanked my God for you. it worked for me
my question is, is there any way to get it work for domestic sim outside USA?

Related

Root access and tethering but stock?

Hello,
I know nothing about rooting so I may be using the wrong terms. I've read a number of people are having issues with their phones after they've rooted or changed to rom or something. I've also read you can run stock(?) but be rooted (or something like that) so you won't have any issues.
Is there a way to give root access without really changing anything about your phone other than enabling tethering? I really only want to enabling tethering. Oh and the sonicwall client says the phone must be rooted or have root access or something before I can run it.

Yeah that can be done, but once you're rooted, you'll end up flashing roms lol
Sent from my SPH-D710 using xda premium

Instructions on how to get root with stock kernel here: http://forum.xda-developers.com/showthread.php?t=1273730
I followed the instructions to the tee and it worked perfectly. I have wifi tethering working now.

Thanks. If anyone has been flashing or rooting on Samsung Androids for a while, what do you think the chance is that I'll be able to do the over the air update for this phone when it comes out if I do root it?

boe said:
Thanks. If anyone has been flashing or rooting on Samsung Androids for a while. What do you think the chance is that I'll be able to do the over the air update for this phone when it comes out if I do root it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=18038477&postcount=46
The other thread is long and convoluted, pm me if you need anymore details, but the original threads in development by ACS are quite clear and easy to follow.

nabbed said:
http://forum.xda-developers.com/showpost.php?p=18038477&postcount=46
The other thread is long and convoluted, pm me if you need anymore details, but the original threads in development by ACS are quite clear and easy to follow.
Click to expand...
Click to collapse
Thanks. I appreciate you taking the time to reply. To be honest I really don't know what you said though. I'm sure it is simple and obvious but I don't know squat about modifying my android phone so I'm not sure what you said really means.
Anyone know if there are any videos I can follow along to get to where I need to be. I think if someone tries to explain it to me in text I'll get lost and people will get frustrated with my lack of android knowledge.

boe said:
Thanks. I appreciate you taking the time to reply. To be honest I really don't know what you said though. I'm sure it is simple and obvious but I don't know squat about modifying my android phone so I'm not sure what you said really means.
Anyone know if there are any videos I can follow along to get to where I need to be. I think if someone tries to explain it to me in text I'll get lost and people will get frustrated with my lack of android knowledge.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1268037
http://forum.xda-developers.com/showthread.php?t=1273647
Here's what you will be doing:
1) Use "Odin" method to flash kernel+cwm recovery (.tar file) from your computer to the phone.
2) Use recovery to flash su.zip from the phone itself.
3) Same as 1 but stock kernel+recovery.
Here's how to do it:
1) Install Samsung Kies software on your computer. It installs usb drivers necessary to communicate to the phone.
2) Install odin software on your computer. Download .tar file for kernel+cwm.
3) Open odin, follow directions in the first thread to point to the .tar file you download from the same thread.
4) Shut down phone. Use key combination to reboot the phone into "download mode". Connect phone to computer with usb cable. Use odin on computer to commence flash of .tar file. Phone will reboot.
5) Download su.zip from the first thread. Place it on usb storage of the phone.
6) Shut down phone again. Hold down Volume Up and power buttons until you see orange menu. That's CWM recovery.
5) Choose install .zip from sdcard (it really installs from usb storage, not from sdcard). Choose select zip on sd card. Navigate to su.zip, confirm.
Then use the menus to go back and reboot the phone.
6) Download stock kernel+recovery from second thread. Start from step 3 above to flash the stock .tar file.
EDIT: Oh yeah, there's a video in the first thread. Not sure how useful it is though.
EDIT2: The video is old. It has conflicting information with the stuff in the first thread. Use it very cautiously, use the links to download from the first thread. You also don't need .pit file. Only .tar files.
EDIT3: these are the file links:
Kies: link
odin: http://forums.acsyndicate.net/ACS/Odin3 v1.85.zip
CWM+kernel .tar: http://forums.acsyndicate.net/ACS/acs-eb30-clockwork-epic-touch-4g-sep-20-4-00-pm.tar
su.zip: http://www.multiupload.com/TD3X6TM9O1
stock .tar: http://www.inspiringandroid.com/mirrors/devices/epic4gtouch/kernels/acs-eg30-stock-kernel-pulled.tar

Thanks! I'll give it a try.
I installed KIES it says "reconnect the device in Samsung Kies (PC Studio) mode. Current connection mode not supported by Kies. I'm not sure how to connect it in Samsung Kies mode.
Odin 1.85 shows it connected as ID0 (com5)
I only have auto reboot selected and the check for PDA as well as the acs-eb30 ewm file.
The phone says downloading but the first box in odin says fail.
Not sure if it is safe to reboot phone.

To answer a question you asked earlier, if you root and take an OTA update the chances are very good you'll lose root. If you're rooted and want to stay that way, wait until devs work with the update and come up with a "root-safe" version.
.....

boe said:
Thanks! I'll give it a try.
I installed KIES it says "reconnect the device in Samsung Kies (PC Studio) mode. Current connection mode not supported by Kies. I'm not sure how to connect it in Samsung Kies mode.
Odin 1.85 shows it connected as ID0 (com5)
I only have auto reboot selected and the check for PDA as well as the acs-eb30 ewm file.
The phone says downloading but the first box in odin says fail.
Not sure if it is safe to reboot phone.
Click to expand...
Click to collapse
You don't need to run kies to use Odin. Kies is only installed for usb drivers.
I'm not sure what would happen if you had both running at the same time.
If you want to use Kies later, you would need to uncheck USB Debugging on the phone in Settings/Applications/Development.
The phone says "downloading" regardless of whether it is flashing the kernel or not. Did you follow the instructions from the first thread?
4. Open Odin3 V1.85 and on the left side ONLY have AUTO reboot checked (VERY IMPORTANT)
6. Check the PDA slot and then press the PDA button and navigate to the Tar file and select it
7. Now power off your Epic Touch.
8. Once fully powered off, press and hold volume down, home key, and power button at the SAME time.*This will take you into Odin mode.
9. Plug your phone into your PC.
10. You should see COM# (the number doesn't matter) in the ID:COM box
11. Press start and let it run through the process!*
Click to expand...
Click to collapse
There's a step missing, but I suppose they didn't mention it since it's fairly obvious. I don't know if it matters...
The step is 8a) When you see odin prompt to continue, confirm to enter odin mode.
Also make sure that those .tar files downloaded correctly.

Thanks - you nailed it. If you have kies running you can't get odin to update the phone. My phone is all updated - ran all the steps.
Do I use a built in app on it for tethering or add an app?

boe said:
Thanks - you nailed it. If you have kies running you can't get odin to update the phone. My phone is all updated - ran all the steps.
Do I use a built in app on it for tethering or add an app?
Click to expand...
Click to collapse
I think you need Wifi Tether. Search for it, it's gonna be on code.google.com. I myself don't use it, but I heard it works pretty much out of the box w/o tweaking.

nabbed said:
I think you need Wifi Tether. Search for it, it's gonna be on code.google.com. I myself don't use it, but I heard it works pretty much out of the box w/o tweaking.
Click to expand...
Click to collapse
My sonicwall client works great with root access. I haven't been able to get the wifi tether to work yet. I can't find the device if I enable security. I can't seem to find the right BT drivers when my computer finds it via BT. If I disable security I can findi it via wifi but with our without acccess control disabled I can't actually complete the wifi connection.

Update - I did get it to connect via tether after all. I hadn't ever had an issue connecting to about 20 wireless networks with my laptop but I did notice a 5002 event churning away in the event viewer when I tried to connect. I updated my wireless drivers and I'm all set!
Thanks for all the help and patience!!!

[FACTORY STOCK] GS4 Stock Firmware Odin Package- Original Factory ROM

This will only work for Windows!
Downloads
Get the Odin Flashing Tool: http://forum.xda-developers.com/attachment.php?attachmentid=1168421&d=1341114315
Get this Firmware Package (very large): http://www.hotfile.com/dl/210140535/c7c4d28/I337UCUAMDB_I337ATTAMDB_ATT.zip.html
mirror: http://storagecow.eu/index.php?dir=Xda/AT&T+S4/Stock+Odin/
mirror: http://www.135.a.hostable.me/public/I337UCUAMDB_I337ATTAMDB_ATT.zip
Instructions
extract I337UCUAMDB_I337ATTAMDB_ATT.zip in your downloads folder
Open Odin
Click PDA
Navigate to where you extracted the firmware and select it
Hold Volume Down + Home + Power until your device enters Download(Odin) Mode, then press volume up.
Connect the device to the computer and hit Start in Odin.
Stand back from the device and the computer until its complete.
Flashing Tips
Always use a GOOD USB cable, preferably stock.
Always use a good USB port in the back of the computer.
Always set the device in a good position where it will not become disconnected or disturbed.
Above all, Always use Heimdall over Odin when it becomes available. It's not available yet.
How to make a firmware like this
I was actually uploading a copy from my own computer obtained via exploit from bfielding's device, and I decided to try kies. The official package is a much better idea. Samsung Kies requires that you put in your model and serial, then it downloads the firmware in an encrypted package, extracts it, flashes it and deletes it. There's a short window where you can get in and grab the firmware.
Kies downloads to a temporary file called (in my case) C:\Users\Adam\AppData\Local\Temp\tmp####.tmp (where # is an integer less than 10). When the firmware is extracted, it goes into a new folder called C:\Users\Adam\AppData\Local\Temp\tmp####\. Yank that and put it on hotfile .

Nice work as always sir!
Sent from my SAMSUNG-SGH-I317 using xda premium

Just checked. The download for this is available on sammobile.com/firmware. It wasn't there a couple of hours ago, well sometime this afternoon.

creepyncrawly said:
Just checked. The download for this is available on sammobile.com/firmware. It wasn't there a couple of hours ago, well sometime this afternoon.
Click to expand...
Click to collapse
There was alot going on and I had multiple windows up. I created one in Linux from bfielding's device, was uploading it to hotfile, uploading one from Kies, and was sent this link too somewhere in the mix. I guess I lost my upload link. Oh well, looks like we're using the Sammobile version.

creepyncrawly said:
Just checked. The download for this is available on sammobile.com/firmware. It wasn't there a couple of hours ago, well sometime this afternoon.
Click to expand...
Click to collapse
I was waiting for it too.
Uploading it to my Server now for Faster download

Your a beast Adam!
Deviance runs in the blood...
BMS fueled.
4.2.2

we will make it a mirror link for faster download

Does this mean if we screw up we can go back to stock

Bradl79 said:
Does this mean if we screw up we can go back to stock
Click to expand...
Click to collapse
Yes this is exactly what it means
sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum

Bradl79 said:
Does this mean if we screw up we can go back to stock
Click to expand...
Click to collapse
Yes thats the idea.

Rock on Adam, rock on! :good:

AdamOutler said:
Yes thats the idea.
Click to expand...
Click to collapse
@AdamOutler, based on your video on the other thread, the motherboard of the ATT and the TMo version of the S4 are the same, does it mean that if flash the TMo version of the ROM on the ATT it may unlock the bootloader or are those two distinctive matters ?

CarpeNoctem said:
@AdamOutler, based on your video on the other thread, the motherboard of the ATT and the TMo version of the S4 are the same, does it mean that if flash the TMo version of the ROM on the ATT it may unlock the bootloader or are those two distinctive matters ?
Click to expand...
Click to collapse
NO! the signatures are different. You'll brick your device, but I'm not sure to what extent.

Ninja'd

I was just talking to my friend who works at Koodo (Canada). They receive their S4s tomorrow, and I had make sure he places a hold on one of them for me!
Using the steps you provided in your OP, I'll upload Koodo's ROM tomorrow!

THANK YOU!!
AdamOutler said:
This will only work for Windows!
Downloads
Get the Odin Flashing Tool: http://forum.xda-developers.com/attachment.php?attachmentid=1168421&d=1341114315
Get this Firmware Package (very large): http://www.hotfile.com/dl/210140535/c7c4d28/I337UCUAMDB_I337ATTAMDB_ATT.zip.html
Instructions
extract I337UCUAMDB_I337ATTAMDB_ATT.zip in your downloads folder
Open Odin
Click PDA
Navigate to where you extracted the firmware and select it
Hold Volume Down + Home + Power until your device enters Download(Odin) Mode, then press volume up.
Connect the device to the computer and hit Start in Odin.
Stand back from the device and the computer until its complete.
Flashing Tips
Always use a GOOD USB cable, preferably stock.
Always use a good USB port in the back of the computer.
Always set the device in a good position where it will not become disconnected or disturbed.
Above all, Always use Heimdall over Odin when it becomes available. It's not available yet.
How to make a firmware like this
I was actually uploading a copy from my own computer obtained via exploit from bfielding's device, and I decided to try kies. The official package is a much better idea. Samsung Kies requires that you put in your model and serial, then it downloads the firmware in an encrypted package, extracts it, flashes it and deletes it. There's a short window where you can get in and grab the firmware.
Kies downloads to a temporary file called (in my case) C:\Users\Adam\AppData\Local\Temp\tmp####.tmp (where # is an integer less than 10). When the firmware is extracted, it goes into a new folder called C:\Users\Adam\AppData\Local\Temp\tmp####\. Yank that and put it on hotfile .
Click to expand...
Click to collapse

AdamOutler said:
NO! the signatures are different. You'll brick your device, but I'm not sure to what extent.
Click to expand...
Click to collapse
Thanks but let's take an stupid case scenario:
ATT device
TMo odin ROM
try to flash 2 onto 1
Fail or succeed
if succeeds -> bootloader unlocked ?
if fails -> can we flash back ATT odin rom now we have it?

If it flashed, which it wont, then you would now uave bootloaders with the wrong signature and would need to jtag it

You the man Adam!

jcase said:
If it flashed, which it wont, then you would now uave bootloaders with the wrong signature and would need to jtag it
Click to expand...
Click to collapse
ok, so basically the signature is check before the flash of the rom. so if my understanding is correct the solutions would be to
disable the check of the signature
have the TMo rom with the ATT signature to flash the unlocked bootloader
change the bootloader with a non-signed version
Please correct me if I am wrong, I am new at this and I am trying to understand what Adam explains in the other thread but I am sometime very confused (and not knowledgeable enough)

How to return to stock Samsung firmware

I'm completely new to rooting. I plan on rooting my Galaxy SII using the Cyanogenmod Installer. However, I want to know how to return to stock.
I found this FAQ online and want to know if it's the correct way of doing it or if there's some easier way out there.
http://www.samsung.com/us/support/faq/FAQ00052690/61265
I would also like to know if Triangle Away works with the Hercules? Thank you.

Hero746 said:
I'm completely new to rooting. I plan on rooting my Galaxy SII using the Cyanogenmod Installer. However, I want to know how to return to stock.
I found this FAQ online and want to know if it's the correct way of doing it or if there's some easier way out there.
http://www.samsung.com/us/support/faq/FAQ00052690/61265
I would also like to know if Triangle Away works with the Hercules? Thank you.
Click to expand...
Click to collapse
Well I first would do a superwipe on TWRP before anything, and download ODIN and your SAMSUNG drivers. I have included a nifty .zip file with everything you would ever need, with all of the firmwares, drivers and ODINs. After you run that superwipe, go on download mode by plugging in your USB cord on your computer, then on your phone. Hold down both volume keys and proceed to turn on your phone. Then, you should see a screen that says volume up to install custom firmware, and volume down to restart. Press volume up. Open ODIN, and click on the PDA or AP (which ever one it says) proceed to go to one of the three files, I have included either 4.0.3, 4.0.4 and 4.1.2. Pick which file you want to restore to and press start. Let it do it's thing and you're done. To root, just go back to ODIN, point it at your root folder and double click on the TWRP file. I have included the upgrade .zip as well to put it to the latest TWRP that works correctly. Enjoy! (The link is huge because it has EVERY SINGLE Stock ROM from ICS and up).
Download to everything: https://mega.co.nz/#!AJ83jQzD!PjrpkBxbFAuQucYEnVcH7yWHagcy3z9Q_3sQ8ZBK980
Also, I have not tried triangle away, but from what I know I've flashed so many times but I haven't even tripped the counter yet.

I'm bumping this with the intent of thanking you.
I followed your instructions to the dot and returned my phone to stock in preparation for the Note 3 I'm getting tomorrow. I feel like this thread should be stickied or included in some sort of master list so as to help the rest of the community.
A word of advice though. If Odin fails to recognize your SGH-T989, you must uninstall and then reinstall your Samsung Drivers. Once again, thank you!

★ |[How-To]| | ROOT NK3 | KEEP KNOX 0x0 | The EffortLess Way | Rooting | 26NOV14 ★

★ |[How-To]| | ROOT NK3 | KEEP KNOX 0x0 | The EffortLess Way | Rooting | 26NOV14 ★
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
If you do not care about KNOX and want a custom recovery or custom ROM installed in addition to root- Go to my other thread here! A custom ROM or custom recovery WILL trip your KNOX to 0x1 (this is irreversible and KNOX will cease to function on your phone forever and ever and ever) :crying:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
************************************************** ************************************************** ************************************************** ************************************************** **************************************************
Welcome to ROOT with KNOX 0x0 the EffortLess Way!!This is a quick and easy way to root the N900T T-Mobile Note 3 with the full stock N900TUVUENK3 update installed!
This guide will assist you in rooting full stock N900TUVUENK3 without tripping KNOX (preserving 0x0)
************************************************** ************************************************** ************************************************** ************************************************** **************************************************NOTE: You will need to be updated to the full stock N900TUVUENK3 firmware before proceeding!
If you need to update to N900TUVUENK3 and are on a stock firmware that has not been rooted yet:
Use the built-in Over The Air (OTA) software updater in your phone settings to check for an update then follow the instructions to update.
After booting up, check for an update again and confirm there are none and that you are on firmware N900TUVUENK3 before proceeding to the "EffortLess Rooting Guide" below.
If you are updating from any prior rooted stock firmware (basically, you've used this guide before but need to update) you will need to follow these steps:
Download EffortLess ROM Prep.zip and Full Stock NK3.zip
Unzip both files
Turn off your phone and then hold the Volume Down, Home Button, and Power Button at the same time, when the phone vibrates, let go of Power Button. Press Volume Up to continue past the "Warning!!" screen.
Open the EffortLess ROM Prep folder and double click on EffortLess Odin.exe
Connect your phone to the computer via USB cable (one of the boxes under ID:COM in Odin will fill with a com number and turn baby blue meaning it can communicate with your phone.. if it does not, unplug your phone and run EffortLess Odin USB Driver.exe from the EffortLess ROM Prep unzipped folder. Now plug your phone in again and it should load the driver and the box should turn baby blue and display a com number)
Click the PDA button and navigate to the unzipped Full Stock NK3 folder, click on N900TUVUENK3_N900TTMBENK3_N900TUVUENK3_HOME.tar.md5 and click Open
Wait for the file to load properly in Odin, it will take a minute and you'll see a check-mark to the left of the PDA button and the system path of the NK3 file to the right.
Now click start and wait, don't touch anything until after your phone restarts.
Now go to menu, settings, General tab, and click About device and verify the Baseband version AND Build Number are N900TUVUENK3
************************************************** ************************************************** ************************************************** ************************************************** **************************************************EffortLess Rooting Guide
This method will revert the kernel back to the Samsung stock NE6 kernel (that is vulnerable to the towelroot method). Then you will use towelroot to root. Finally, you will flash back the NK3 kernel and enjoy root on your stock NF3 phone!
This process should take approximately 5 minutes and will not erase any files on your phone.
First download and install towelroot on your phone]:
Navigate to towelroot on your phone (once at the site, click the main center logo) and install the downloaded app (do not open the app and click make it ra1n yet).
Then download EffortLessRootPrep.zip on your Windows computer and unzip it.
Flashing NE6 Kernel
Turn off your phone and then hold the Volume Down, Home Button, and Power Button at the same time, when the phone vibrates, let go of Power Button. Press Volume Up to continue past the "Warning!!" screen.
Open the EffortLess Root Prep folder and double click on EffortLess Odin.exe
Connect your phone to the computer via USB cable (one of the boxes under ID:COM in Odin will fill with a com number and turn baby blue meaning it can communicate with your phone.. if it does not, unplug your phone and run EffortLess Odin USB Driver.exe from the EffortLess Root Prep unzipped folder. Now plug your phone in again and it should load the driver and the box should turn baby blue and display a com number)
Click the PDA button and navigate to the unzipped EffortLess Root Prep folder, click on N900TUVUDNE6_KERNEL.tar.md5 and click Open
Wait for the file to load properly in Odin, it will take a minute and you'll see a check-mark to the left of the PDA button and the system path of the root file to the right.
Now click start and wait, don't touch anything until after your phone restarts.
Running towelroot
Once your phone boots up, open the towelroot app and click "make it ra1n".
Wait ten seconds and then reboot your phone. (I know it says reboot is not required, do it anyway)
Open SuperSU (if it's not in your app drawer, download it from the play store) and if it asks to update the binary, choose the normal method. (if it says installation failed, just try again or try again after you flash back to NK3, it's normal and it'll be updated)
When it mentions disabling KNOX, click ok (this will not trip KNOX, it will simply disable it for the time being.. If you want to use KNOX while rooted, don't disable it in SuperSU). NOTE: if it hangs disabling KNOX don't worry. Turn off your phone and proceed to the next step. After flashing the NK3 Kernel back, open SuperSU and disable KNOX and it should work within a few seconds.
Flashing NK3 Kernel back
Turn off your phone and then hold the Volume Down, Home Button, and Power Button at the same time, when the phone vibrates, let go of Power Button. Press Volume Up to continue past the "Warning!!" screen.
Open the EffortLess Root Prep folder and double click on EffortLess Odin.exe
Connect your phone to the computer via USB cable (one of the boxes under ID:COM in Odin will fill with a com number and turn baby blue meaning it can communicate with your phone.. if it does not, unplug your phone and run EffortLess Odin USB Driver.exe from the EffortLess Root Prep unzipped folder. Now plug your phone in again and it should load the driver and the box should turn baby blue and display a com number)
Click the PDA button and navigate to the unzipped EffortLess Root Prep folder, click on N900TUVUENK3_KERNEL.tar.md5 and click Open
Wait for the file to load properly in Odin, it will take a minute and you'll see a check-mark to the left of the PDA button and the system path of the root file to the right.
Now click start and wait, don't touch anything until after your phone restarts.
You can uninstall the towelroot app after you're are finished.
If this helped, please click the "Thanks" button! :good:
| Let me know you like it :highfive: Donate to show your support |
Thanks to:
@geohot for making towelroot
and special thanks @toastito for getting me the stock Odin flashable kernels!

This worked for me! Followed your steps and I now have root with Knox counter 0x0. Thank you for the guide! The only issue I had was while updating the Super SU binaries I received an "installation failed" message after updating and disabling knox, but after flashing back to the NF4 kernel I had root and Super SU works fine. You might want to add something to the guide so people know this is normal. :good:

_bhaves_ said:
This worked for me! Followed your steps and I now have root with Knox counter 0x0. Thank you for the guide! The only issue I had was while updating the Super SU binaries I received an "installation failed" message after updating and disabling knox, but after flashing back to the NF4 kernel I had root and Super SU works fine. You might want to add something to the guide so people know this is normal. :good:
Click to expand...
Click to collapse
Thanks for the feedback _bhaves_! I'll be adjusting the guide as I get more feedback. I was only able to test this twice as my phone is already KNOX 0x1 and I had limited time with the KNOX 0x0 phone. I concentrated on ensuring KNOX would stay 0x0 during my testing. I had different results than you regarding installing the binaries. Now I feel that running SuperSU and updating it and disabling KNOX should be done after flashing back to NF4 kernel. I feel the reboot clears stuff up and enables SuperSU to function more fluidly. I'll change it to that and await further feedback.

Thanks for the guide! I was on NF1 and used your guides to successfully go to NF4 with no issues and still have not tripped KNOX...thank you good sir.

effortless said:
************************************************** ************************************************** ************************************************** ************************************************** **************************************************
Welcome to ROOT with KNOX 0x0 the EffortLess Way!!This is a quick and easy way to root the N900T T-Mobile Note 3 with the full stock NF4 update installed!
This guide will assist you in rooting NF4 without tripping KNOX (preserving 0x0)
Only proceed with this guide if you want root and do not want a custom recovery or custom ROM installed!
NOTE: You will need to be updated to the full stock NF4 ROM before proceeding!
If you need to update to NF4, use the EffortLess Guide and stop after the "For full N900TUVUDNF4 stock:" section, steps 1-8. (DO NOT proceed to root or flash a custom recovery in that thread) then come back here.
This method will revert the kernel back to the Samsung stock NE6 kernel (that is vulnerable to the towelroot method). Then you will use towelroot to root. Finally, you will flash back the NF4 kernel and enjoy root on your stock NF4 phone!
This process should take approximately 5 minutes and will not erase any files on your phone.
************************************************** ************************************************** ************************************************** ************************************************** **************************************************
First download towelroot (once at the site, click the main center logo) on your phone and install the app (do not click make it ra1n yet).
Then download EffortLessRootPrep.zip on your Windows computer and unzip it.
Rooting NF4 (Flashing NE6 Kernel)
Turn off your phone and then hold the Volume Down, Home Button, and Power Button at the same time, when the phone vibrates, let go of Power Button. Press Volume Up to continue past the "Warning!!" screen.
Open the EffortLess Root Prep folder and double click on EffortLess Odin.exe
Connect your phone to the computer via USB cable (one of the boxes under ID:COM in Odin will fill with a com number and turn baby blue meaning it can communicate with your phone.. if it does not, unplug your phone and run EffortLess Odin USB Driver.exe from the EffortLess Root Prep unzipped folder. Now plug your phone in again and it should load the driver and the box should turn baby blue and display a com number)
Click the PDA button and navigate to the unzipped EffortLess Root Prep folder, click on N900TUVUDNE6_KERNEL.tar.md5 and click Open
Wait for the file to load properly in Odin, it will take a minute and you'll see a check-mark to the left of the PDA button and the system path of the root file to the right.
Now click start and wait, don't touch anything until after your phone restarts.
Rooting NF4 (Running towelroot)
Once your phone boots up, open the towelroot app and click "make it ra1n".
Wait ten seconds and then reboot your phone. (I know it says reboot is not required, do it anyway)
Open SuperSU (if it's not in your app drawer, download it from the play store) and if it asks to update the binary, choose the normal method. (if it says installation failed, just try again or try again after you flash back to NF4, it's normal and it'll be updated)
When it mentions disabling KNOX, click ok (this will not trip KNOX, it will simply disable it for the time being.. If you want to use KNOX while rooted, don't disable it in SuperSU). NOTE: if it hangs disabling KNOX don't worry. Turn off your phone and proceed to the next step. After flashing the NF4 Kernel back, open SuperSU and disable KNOX and it should work within a few seconds.
Rooting NF4 (Flashing NF4 Kernel back)
Turn off your phone and then hold the Volume Down, Home Button, and Power Button at the same time, when the phone vibrates, let go of Power Button. Press Volume Up to continue past the "Warning!!" screen.
Open the EffortLess Root Prep folder and double click on EffortLess Odin.exe
Connect your phone to the computer via USB cable (one of the boxes under ID:COM in Odin will fill with a com number and turn baby blue meaning it can communicate with your phone.. if it does not, unplug your phone and run EffortLess Odin USB Driver.exe from the EffortLess Root Prep unzipped folder. Now plug your phone in again and it should load the driver and the box should turn baby blue and display a com number)
Click the PDA button and navigate to the unzipped EffortLess Root Prep folder, click on N900TUVUDNF4_KERNEL.tar.md5 and click Open
Wait for the file to load properly in Odin, it will take a minute and you'll see a check-mark to the left of the PDA button and the system path of the root file to the right.
Now click start and wait, don't touch anything until after your phone restarts.
You can uninstall the towelroot app after you're are finished.
If this helped, please click the "Thanks" button! :good:
| Let me know you like it :highfive: Donate to show your support |
Thanks to:
@geohot for making towelroot
and special thanks @toastito for getting me the stock Odin flashable kernels at short notice while I was away from my workstation!
Click to expand...
Click to collapse
I really wish this had came out when started rooting my Note. I had to send my phone out to Samsung and had to pay to have it fixed

N900TUVUDNE6_KERNEL.tar.md5 is not present in the folder. Only a CF root file is there and a recovery file.
Towelroot states the device isn't supported.
Knox Warranty Void 0x1

conchchowder said:
N900TUVUDNE6_KERNEL.tar.md5 is not present in the folder. Only a CF root file is there and a recovery file.
Towelroot states the device isn't supported.
Click to expand...
Click to collapse
You're mixing my how-to threads and files. You didn't download the EffortLessRootPrep file... you downloaded the EffortLess ROM Prep.zip which is used to install a custom recovery and custom rom (both of which will trip your KNOX if flashed).
Also, the whole purpose of this thread is to downgrade to the NE6 kernel which supports towelroot (before running it). I specifically mention not to run it (until after you downgrade to the NE6 kernel), because it's not compatible with NF4.

[emoji15]
Sent from my SM-N900T using Tapatalk

worked perfectly for me !!!

I would like to thank OP and other developers for all their efforts, it worked like a charm.
But I do have a quick question: I stayed on 4.3 until now due to SD card access being broken and fix requiring root access, that trip Knox.
Of course this solution solved Knox worry and therefore I went ahead updating, however I don't seem to have any SD card issues yet, even before I applied the fix. I just would like to know why?
1. Is it because Google or Samsung fix it in later release?
2. Is it because all the apps I use were already updated?
3. is it because ROMs were somehow fixed either by rooting, or by the people posting the ROM.
Or maybe it's not fixed? When I use ES explorer, I see the folders, but many appear empty, like titanium backup for example.
Now this would be the most stupid thing, if all those folders showing empty weren't, since I always delete empty folders as a rule.
So are SD Card access restrictions fixed in NF4 or not and if not which fix is working well, since I came across some posts that claim broken BT, after applying the fix.
TIA

pete4k said:
I would like to thank OP and other developers for all their efforts, it worked like a charm.
But I do have a quick question: I stayed on 4.3 until now due to SD card access being broken and fix requiring root access, that trip Knox.
Of course this solution solved Knox worry and therefore I went ahead updating, however I don't seem to have any SD card issues yet, even before I applied the fix. I just would like to know why?
1. Is it because Google or Samsung fix it in later release?
2. Is it because all the apps I use were already updated?
3. is it because ROMs were somehow fixed either by rooting, or by the people posting the ROM.
Or maybe it's not fixed? When I use ES explorer, I see the folders, but many appear empty, like titanium backup for example.
Now this would be the most stupid thing, if all those folders showing empty weren't, since I always delete empty folders as a rule.
So are SD Card access restrictions fixed in NF4 or not and if not which fix is working well, since I came across some posts that claim broken BT, after applying the fix.
TIA
Click to expand...
Click to collapse
This is a copy and paste of a previous statement I've made about this topic:
A lot of people are very confused on the SD card changes. YOU DO NOT LOSE SD CARD access! The change was that if an app created a folder on your SD card to store stuff, another app cannot access and make changes to it (Which is how it should have been from the beginning). There are many reasons as to why this is the better way (many security related as well as programming related scenarios).
This means that each app can create and write changes to SD card folders it creates and no other folder. The app has to be the creator of the folder it's making changes to.. that makes sense right?! You can still put all the music and pictures and documents you want on the SD card and they will still work like in the past. A few apps had to be updated because they were doing things the old way, but that's been done and you shouldn't have any issues that people had when the change first was done.
4.4 adds a host of new features, bug fixes, network efficiency enhancements and security patches (some are very serious and if you're still on 4.3, your phone is at risk daily). I highly suggest everyone upgrade. If you have any particular issue, private message me and I will help you address it!
To address your current questions though, the change wasn't something that was broken by Google. It shouldn't have been called an SD Card Fix either (like I said, it didn't break), but there were changes in the way Android Apps interacted with the SD card. You can still do this SD Card Fix manually or just use an app in the play store to make the changes for you. There are still certain situations where the "SD Card Fix" is useful, but if it's working for you, then leave it the way it is. Most problems initially were due to needing updates for apps at the time.

effortless said:
This is a copy and paste of a previous statement I've made about this topic:
A lot of people are very confused on the SD card changes. YOU DO NOT LOSE SD CARD access! The change was that if an app created a folder on your SD card to store stuff, another app cannot access and make changes to it (Which is how it should have been from the beginning). There are many reasons as to why this is the better way (many security related as well as programming related scenarios).
This means that each app can create and write changes to SD card folders it creates and no other folder. The app has to be the creator of the folder it's making changes to.. that makes sense right?! You can still put all the music and pictures and documents you want on the SD card and they will still work like in the past. A few apps had to be updated because they were doing things the old way, but that's been done and you shouldn't have any issues that people had when the change first was done.
4.4 adds a host of new features, bug fixes, network efficiency enhancements and security patches (some are very serious and if you're still on 4.3, your phone is at risk daily). I highly suggest everyone upgrade. If you have any particular issue, private message me and I will help you address it!
To address your current questions though, the change wasn't something that was broken by Google. It shouldn't have been called an SD Card Fix either (like I said, it didn't break), but there were changes in the way Android Apps interacted with the SD card. You can still do this SD Card Fix manually or just use an app in the play store to make the changes for you. There are still certain situations where the "SD Card Fix" is useful, but if it's working for you, then leave it the way it is. Most problems initially were due to needing updates for apps at the time.
Click to expand...
Click to collapse
Thank you for response and again great job on the root.
The reason I used word "broken" was because originally it broke many programs. I would hate not to be able to access DCIM directory created by camera, to view or delete pics with my favorite third party view program, just to give an example, of why limiting access to SD card could create major issues, but it seems to be working fine so far, so I leave it alone for now.
Another quick question: phone status says official, so do I need to worry about future updates breaking the root, or is OTA updates not possible despite official status.

pete4k said:
Thank you for response and again great job on the root.
The reason I used word "broken" was because originally it broke many programs. I would hate not to be able to access DCIM directory created by camera, to view or delete pics with my favorite third party view program, just to give an example, of why limiting access to SD card could create major issues, but it seems to be working fine so far, so I leave it alone for now.
Another quick question: phone status says official, so do I need to worry about future updates breaking the root, or is OTA updates not possible despite official status.
Click to expand...
Click to collapse
Don't accept the OTA updates (you can be notified even when rooted). They will most likely result in a softbrick.
Wait for someone to test it or you might have to unroot and take the update and then perform a similar method to get root back. It depends on what they do to prevent things like this in the future (if anything).

thanks for your quick reply, on my previous root phone status was custom, so no OTA there. I guess I just freeze the update app to be on safe side, kids play my phone sometimes and could update by accident, I remember from the time before root how pesky those update reminders can be and how easy it is to press accept instead of cancel.

Quick question: I am already at NE6, rooted with TowelRoot and KNOX is NOT tripped. Which steps I need to follow to upgrade to NF4?
Or is the steps shown here is not applicable in my case?

lanwarrior said:
Quick question: I am already at NE6, rooted with TowelRoot and KNOX is NOT tripped. Which steps I need to follow to upgrade to NF4?
Or is the steps shown here is not applicable in my case?
Click to expand...
Click to collapse
This guide will work for you. However, you should start from fresh stock NF4 unrooted. Odin stock NF4 and proceed.
It's a lot harder to update a rooted NE6 to all the NF4 files then it is to root NF4 using the NE6 kernel.

effortless said:
This guide will work for you. However, you should start from fresh stock NF4 unrooted. Odin stock NF4 and proceed.
It's a lot harder to update a rooted NE6 to all the NF4 files then it is to root NF4 using the NE6 kernel.
Click to expand...
Click to collapse
I just did an upgrade from NE6 to NF4 following the thread here: http://forum.xda-developers.com/not...udnf4-extracted-stock-firmware-t2834398/page3
But my phone is now hosed - cannot use keyboard ("Unfortunately, Samsung Keyboard has stopped" error) and APN is gone from SIM card. So I am trying to salvage this.
If I Odin NF4 (add the NF4 file to "AP" in Odin), wouldn't this trip KNOX?

lanwarrior said:
I just did an upgrade from NE6 to NF4 following the thread here: http://forum.xda-developers.com/not...udnf4-extracted-stock-firmware-t2834398/page3
But my phone is now hosed - cannot use keyboard ("Unfortunately, Samsung Keyboard has stopped" error) and APN is gone from SIM card. So I am trying to salvage this.
If I Odin NF4 (add the NF4 file to "AP" in Odin), wouldn't this trip KNOX?
Click to expand...
Click to collapse
No.. Knox is only tripped with custom kernel or custom recovery. Flashing stock NF4 in Odin will not trip Knox. Just flash NF4 in Odin and reset your phone through the settings and it will be working fine again.
Don't continue to flash the recovery or root your phone through my other guide as it will trip Knox (If that is something you are avoiding).

effortless said:
Don't continue to flash the recovery or root your phone through this guide as it will trip Knox (If that is something you are avoiding).
Click to expand...
Click to collapse
Oh, I thought this guide refer to rooting NF4? I was reading through the steps and it talks about "downgrading" to NE6 kernel if one already have NF4.
If needed to, I can flash stock NE6, do a system update to NF4, then follow this guide.
Err.. I just realized that my phone still have SU and root still working, even after hard reset. That means system update won't work. I guess flashing stock will wipe out root?

lanwarrior said:
Oh, I thought this guide refer to rooting NF4? I was reading through the steps and it talks about "downgrading" to NE6 kernel if one already have NF4.
If needed to, I can flash stock NE6, do a system update to NF4, then follow this guide.
Err.. I just realized that my phone still have SU and root still working, even after hard reset. That means system update won't work. I guess flashing stock will wipe out root?
Click to expand...
Click to collapse
Sorry for the confusion. I edited it to say my other guide (my other guide is for custom recovery and custom rom).. through this guide is fine. Don't root through Odin, root using the NE6 kernel and towelroot like it says and you'll be ok with Knox.

Failed root attempt left tablet at the Samsung screen

I have been searching the forum and google and have been unable to reach a solution yet.
I am not a noob, but i am not an expert either so use small words ha.
I have a Samsung Galaxy Tab 3 10.1 5210 with the most recent OTA update.
Last night I attempted to root my device using this:
androidxda (DOT) com/root-samsung-galaxy-tab-3-10-1-gt-p5210
It claimed successful and my device started to reboot and hung up at the Samsung GALAXY TAB 3 screen. I am unable to get to recovery mode on the device. Only able to go to download mode. I have tried several options but have been unable to find a way to flash it successfully. The flashes i have tried downloading were all in .zip and that obviously isn't able to be used in Odin. I have researched how to convert the files into a .tar but I don't have linux. Can someone please help me because I need my tablet. I know it can be saved but I can't seem to locate the answers. I am also getting concerned that it is unable to charge the battery being in the condition it is in now so I am trying to conserve the battery on the tablet until it is absolutely needed. Thanks.

cameron72 said:
I have been searching the forum and google and have been unable to reach a solution yet.
I am not a noob, but i am not an expert either so use small words ha.
I have a Samsung Galaxy Tab 3 10.1 5210 with the most recent OTA update.
Last night I attempted to root my device using this:
androidxda (DOT) com/root-samsung-galaxy-tab-3-10-1-gt-p5210
It claimed successful and my device started to reboot and hung up at the Samsung GALAXY TAB 3 screen. I am unable to get to recovery mode on the device. Only able to go to download mode. I have tried several options but have been unable to find a way to flash it successfully. The flashes i have tried downloading were all in .zip and that obviously isn't able to be used in Odin. I have researched how to convert the files into a .tar but I don't have linux. Can someone please help me because I need my tablet. I know it can be saved but I can't seem to locate the answers. I am also getting concerned that it is unable to charge the battery being in the condition it is in now so I am trying to conserve the battery on the tablet until it is absolutely needed. Thanks.
Click to expand...
Click to collapse
First of all - Welcome to xda
Your tab is soft bricked, something has gone wrong with your system files... Honestly it seems like you know enough to get it done, but are struggling a bit with the file formats. You are correct in saying that Odin won't use zip files, but you shouldn't have to convert anything to tar or download linux! If you extract the zip files, you should find a .tar or .tar.md5 file (inside the zip file) that Odin can use, put it in the PDA mode box, etc etc... If your downloads don't have the correct files inside them, try THIS thread.
Let me know if you get it sorted :good:

bob23bk said:
First of all - Welcome to xda
Your tab is soft bricked, something has gone wrong with your system files... Honestly it seems like you know enough to get it done, but are struggling a bit with the file formats. You are correct in saying that Odin won't use zip files, but you shouldn't have to convert anything to tar or download linux! If you extract the zip files, you should find a .tar or .tar.md5 file (inside the zip file) that Odin can use, put it in the PDA mode box, etc etc... If your downloads don't have the correct files inside them, try THIS thread.
Let me know if you get it sorted :good:
Click to expand...
Click to collapse
I had already tried the method and file in the forum you linked me to. It failed almost instantly. That's when I turned everything off and tossed it all to the back seat of my work truck before it got thrown at the windshield. I keep seeing people saying they have trwp or whatever. I don't even know what that is haven't researched that. Is it something i need as well?
I've never successfully rooted a Samsung device. I used to do this stuff a lot back with the droid x with Linux and everything was pretty simple. Does Samsung change their bootloader with each update like Motorola did then? I was wondering that when trying to install a firmware of a previous version that maybe that was the problem.
All I wanted root for was to just tweak some things and be happy. It has turned into a nightmare.

C,
hi,
the consistent/common thread of this problem is/seems to be taking the ota and trying unverified/gimmicky
root methods.
there are recoveries for the gt-p52xx in the tab 10.1 forum
the majority of samsung devices root as follows;
if a custom recovery exist, flash it.
then download recent or latest version of chainfire's supersu update zip, reboot to recovery
backup your rom first, then flash supersu, if everything goes well, once you have set up your stock rom with root in place
make a new backup.
samsung ota's are death incarnate, reject them.
goto the tab 10 forum and get busy ! you said it yourself, you're not a noob, you know the drill. :good:
m

moonbutt74 said:
C,
hi,
the consistent/common thread of this problem is/seems to be taking the ota and trying unverified/gimmicky
root methods.
there are recoveries for the gt-p52xx in the tab 10.1 forum
the majority of samsung devices root as follows;
if a custom recovery exist, flash it.
then download recent or latest version of chainfire's supersu update zip, reboot to recovery
backup your rom first, then flash supersu, if everything goes well, once you have set up your stock rom with root in place
make a new backup.
samsung ota's are death incarnate, reject them.
goto the tab 10 forum and get busy ! you said it yourself, you're not a noob, you know the drill. :good:
m
Click to expand...
Click to collapse
I have tried the recoveries in the forum and it failed seconds after starting.
I don't do this stuff regularly as I don't hardly have the time. I haven't done anything of this nature in years so I'm well out of the loop on things..

cameron72 said:
I have tried the recoveries in the forum and it failed seconds after starting.
I don't do this stuff regularly as I don't hardly have the time. I haven't done anything of this nature in years so I'm well out of the loop on things..
Click to expand...
Click to collapse
okay, hmm, when you say it fails, do you mean odin fails to flash and if so what is the reason/ouput ?
or do you mean that you are now in a recovery bootloop ?
note- though i go the full route of packing recovery.img's for odin flashing, the md5 checksum always seems to
come up as invalid, the working "remedy" is to remove the .md5 extension from the "odin-flashable-recovery".tar.md5 file
by renaming the file to "odin-flashable-recovery".tar
odin will no longer attempt the checksum verification but the recovery file will flash.
make sure you have samsung-usb-drivers for windows installed. on the main page of my devhost archive [link is in my signature]
you will find the tools you need. the possible problem is that the ota you installed may have overwritten your bootloader, for that i don't
have a reliable fix, so if anything make sure you also have the stock recovery ready to go as well as supersu update zip
already downloaded onto your device for rooting.
after you flash the custom recovery [with auto-restart in odin disabled] run the flash and wait for the res-ok message, give it another second or two then disconnect the tab and force reboot to recovery, home,vol-up and power, once in recovery make a full backup, then flash supersu zip and reboot, if you do go into recovery loop, force reboot to odin mode, home,vol-down and power, follow the on screen instruction, now reconnect your tab to pc and use odin to flash back stock recovery.
m

Okay guys I appreciate the help. I finally got it. I tried the method on Zachisimo's post on unbricking and finally got it installed.
After it installed, it left me with a bootloop and I was actually able to go into recovery mode this time and do a factory data reset and wipe cache then everything went well. I am a happy dude now.
Going to attempt rooting it again and does anyone have any suggestions on what ROM to install? I have never used any custom ROM's before so that is a new area for me. Feeling more confident knowing how to save it from the dead. :good::good::good:

cameron72 said:
Okay guys I appreciate the help. I finally got it. I tried the method on Zachisimo's post on unbricking and finally got it installed.
After it installed, it left me with a bootloop and I was actually able to go into recovery mode this time and do a factory data reset and wipe cache then everything went well. I am a happy dude now.
Going to attempt rooting it again and does anyone have any suggestions on what ROM to install? I have never used any custom ROM's before so that is a new area for me. Feeling more confident knowing how to save it from the dead. :good::good::good:
Click to expand...
Click to collapse
Hi,
Alright !'m glad you got it working, as to roms , all available roms currently are stock modifications , I use cag-rom, there's also pimp-droid
both kitkat.
m

moonbutt74 said:
Hi,
Alright !'m glad you got it working, as to roms , all available roms currently are stock modifications , I use cag-rom, there's also pimp-droid
both kitkat.
m
Click to expand...
Click to collapse
If you use it then thats what i shall try. First i gotta find a root, then I have seen many people recommend philz recovery, and then the rom?
question why does Restl3ss say wait 10minutes after installing a rom before doing anything?

cameron72 said:
If you use it then thats what i shall try. First i gotta find a root, then I have seen many people recommend philz recovery, and then the rom?
question why does Restl3ss say wait 10minutes after installing a rom before doing anything?
Click to expand...
Click to collapse
for root look up supersu update zip
ask Restl3ss :silly:
m

cameron72 said:
Okay guys I appreciate the help. I finally got it. I tried the method on Zachisimo's post on unbricking and finally got it installed.
After it installed, it left me with a bootloop and I was actually able to go into recovery mode this time and do a factory data reset and wipe cache then everything went well. I am a happy dude now.
Going to attempt rooting it again and does anyone have any suggestions on what ROM to install? I have never used any custom ROM's before so that is a new area for me. Feeling more confident knowing how to save it from the dead. :good::good::good:
Click to expand...
Click to collapse
Glad it worked out, recovering from brick does set you free from the stress induced by the disclaimers imo :silly:

Develop Bugs

welcome