Database Info

[Q] Where to start the root process?

I have a GT-N8013 Galaxy Note 10.1 Wireless 16G. It has been updated to Jelly Bean and has been updated to JB through the Keis OTA and has also just recently received one or two other updates, for what reason I am not sure.
I just recently rooted my Droid Razr Maxx and so far, I am happy that I did that. Now I want to go ahead and root my Note 10.1, however I am thoroughly confused as to where to start. Through all of my Google searches and message board searches, I keep coming across what seems to be older instructions for updating to JB, which I already have, or rooting based upon apps that were in existence as far back as say August, 2012.
Well now it is the end of March, and I do not know if I should be pursuing this using Odin (which version and where is the best place from which to download it) or is there an alternative or better approach using CM 10, etc. As I typed the question, the last similar threads that popped up were from November 30, 2012 and prior.
I wanted to avoid having to ask what to many of you seems to be such a basic question, but there just doesn't seem to be anything that I see out there that has a recommended method, post OTA JB.
Any advise will be greatly appreciated.

bookbean said:
I have a GT-N8013 Galaxy Note 10.1 Wireless 16G. It has been updated to Jelly Bean and has been updated to JB through the Keis OTA and has also just recently received one or two other updates, for what reason I am not sure.
I just recently rooted my Droid Razr Maxx and so far, I am happy that I did that. Now I want to go ahead and root my Note 10.1, however I am thoroughly confused as to where to start. Through all of my Google searches and message board searches, I keep coming across what seems to be older instructions for updating to JB, which I already have, or rooting based upon apps that were in existence as far back as say August, 2012.
Well now it is the end of March, and I do not know if I should be pursuing this using Odin (which version and where is the best place from which to download it) or is there an alternative or better approach using CM 10, etc. As I typed the question, the last similar threads that popped up were from November 30, 2012 and prior.
I wanted to avoid having to ask what to many of you seems to be such a basic question, but there just doesn't seem to be anything that I see out there that has a recommended method, post OTA JB.
Any advise will be greatly appreciated.
Click to expand...
Click to collapse
Some of the rooting methods have been defeated by Samsung with the last 2 updates.
Zedomax has a root method that does work will the most current firmware updates and his version of CWM that is installed with his root method seems to be more compatible with a few of the custom ROM's out there.
You should visit these links, they are very informative.
http://forum.xda-developers.com/showthread.php?t=1831152
http://rootgalaxynote.com/galaxy-note-10-1-root/how-to-root-galaxy-note-10-1-easiest-methodcwmmethod-2/
Root Video Link
http://www.youtube.com/watch?feature=player_embedded&v=nIYiXzcW7xs
Un-Root directions
http://rootgalaxynote.com/galaxy-note-10-1-2/how-to-unrootunbrick-galaxy-note-10-1-factory-firmware/

Did not succeed with root
kkretch said:
Some of the rooting methods have been defeated by Samsung with the last 2 updates.
Zedomax has a root method that does work will the most current firmware updates and his version of CWM that is installed with his root method seems to be more compatible with a few of the custom ROM's out there.
You should visit these links, they are very informative.
http://forum.xda-developers.com/showthread.php?t=1831152
http://rootgalaxynote.com/galaxy-note-10-1-root/how-to-root-galaxy-note-10-1-easiest-methodcwmmethod-2/
Root Video Link
http://www.youtube.com/watch?feature=player_embedded&v=nIYiXzcW7xs
Un-Root directions
http://rootgalaxynote.com/galaxy-note-10-1-2/how-to-unrootunbrick-galaxy-note-10-1-factory-firmware/
Click to expand...
Click to collapse
I carefully watched the video. After the CWM-SuperSU-v0.94.zip file was transferred onto my external drive, I ran odin3 v1.85exe and got to the green pass screen. After the reboot, I held down the power and volume up buttons until I saw the screen go off. When the logo came up, I let go of the power button and I kept holding onto the power up button, but I did not get to the ClockworkMod Recovery screen. Instead, I was brought to the Android Recovery Screen. I tried clicking on the file on the external SD from that screen, but all that I got were failures.
What other options are there?
Thank you, btw, for trying to assist me.

bookbean said:
I carefully watched the video. After the CWM-SuperSU-v0.94.zip file was transferred onto my external drive, I ran odin3 v1.85exe and got to the green pass screen. After the reboot, I held down the power and volume up buttons until I saw the screen go off. When the logo came up, I let go of the power button and I kept holding onto the power up button, but I did not get to the ClockworkMod Recovery screen. Instead, I was brought to the Android Recovery Screen. I tried clicking on the file on the external SD from that screen, but all that I got were failures.
What other options are there?
Thank you, btw, for trying to assist me.
Click to expand...
Click to collapse
You did something wrong....... Did you do power and vol down at the same time first 1:40 of video after that run odin again.
It maybe better to download video in1080p to your computer so you can watch easier.

Resolved with an alternative process
kkretch said:
You did something wrong....... Did you do power and vol down at the same time first 1:40 of video after that run odin again.
It maybe better to download video in1080p to your computer so you can watch easier.
Click to expand...
Click to collapse
I used Odin, but found another root method called CF-Auto-Root-p4notewifi-p4notewifiue-gtn8013.zip. That worked like a charm. I then installed Root Checker to ensure that it worked, which it did.
So now I need to know what applications I need to install next as a follow-up.

I don't believe Auto root installs CWM. You may need to get Mobile ODIN, there's a free version on XDA or a paid version in the play store... I prefer to get the licenced version as there's more things you can do.
After installing this, you can then put the CWM file on your sd card or internal memory and flash it or just flash a custom rom...
Flashing a custom rom should put a custom recovery on too...
You might want to download and run an app called triangleaway to reset your flash counter too...

Moving right along
ultramag69 said:
I don't believe Auto root installs CWM. You may need to get Mobile ODIN, there's a free version on XDA or a paid version in the play store... I prefer to get the licenced version as there's more things you can do.
After installing this, you can then put the CWM file on your sd card or internal memory and flash it or just flash a custom rom...
Flashing a custom rom should put a custom recovery on too...
You might want to download and run an app called triangleaway to reset your flash counter too...
Click to expand...
Click to collapse
Thank you all for helping this root noobie. So I am running CWM Recovery v6.0.0.1.1 right now and doing a full backup to my external card. Seems like it should be done pretty soon. The blue widget in Andy's belly doesn't seem to move too much, if at all, however I do see that the progress bar is moving along and the file names keep changing below "backup up data...".
On top of Andy's head are three little guys with the words "High on Android" across his head. Oops, now I'm getting messages about skipping backup of apps and the fact that No sd-ext found. I don't understand that as there is most certainly an ext SD card.
Assuming that this completes OK, I will next proceed for CM10 and Triangleaway, unless there are other recommendations. Now back to the main Backup and Restore screen. Sorry for the blow by blow, but this is all new to me. Would my Titanium license provide the same benefits?

Here are a few good must haves for me.
Triangle Away
https://play.google.com/store/apps/details?id=eu.chainfire.triangleaway&feature=search_result#?t=W251bGwsMSwxLDEsImV1LmNoYWluZmlyZS50cmlhbmdsZWF3YXkiXQ..
Carbon - App Sync and Backup
https://play.google.com/store/apps/details?id=com.koushikdutta.backup
AirDroid (better than Kies for wireless file transfer)
https://play.google.com/store/apps/details?id=com.sand.airdroid
MyScript Calculator
https://play.google.com/store/apps/details?id=com.visionobjects.calculator
.

Triangle Away
kkretch said:
Here are a few good must haves for me.
Triangle Away
https://play.google.com/store/apps/details?id=eu.chainfire.triangleaway&feature=search_result#?t=W251bGwsMSwxLDEsImV1LmNoYWluZmlyZS50cmlhbmdsZWF3YXkiXQ..
Carbon - App Sync and Backup
https://play.google.com/store/apps/details?id=com.koushikdutta.backup
AirDroid (better than Kies for wireless file transfer)
https://play.google.com/store/apps/details?id=com.sand.airdroid
MyScript Calculator
https://play.google.com/store/apps/details?id=com.visionobjects.calculator
.
Click to expand...
Click to collapse
I went ahead and downloaded Triangle Away. When I start in download mode, I receive the warning along with the big yellow triangle. After pressing volume up to continue, it goes into Odin Mode (in Red) and shows that the Custom Binary Download: Yes (5 counts), followed by Current Binary: Custom and then System Status: Custom. To get out of that screen, I have just held down the power button to turn off the device.
When I start up the Triangle Away app, the current status (under Flash Counter) says that Status cannot be determined, need to reboot into a special bootmode - tap "Reset flash counter".
In the Overview section on Play Store, it shows this warning:
On a number of devices, TriangleAway can work, but your firmware may not be supported directly. In that case, the app will tell you it needs to reboot into a special boot mode, which will be happen if you select "Reset flash counter". The device will reboot into a special mode which will allow you to review the current status and reset the binary and flash counter values (or abort and do nothing). On some devices this will actually trigger the counter to 1 if its 0 - so if you're "just checking", do that in download mode!
!!! THIS IS A DANGEROUS OPERATION AND COULD POTENTIALLY BRICK YOUR DEVICE. PROCEED AT YOUR OWN RISK. A USB JIG IS PREFERRED IF YOU HAVE A WORKING ONE !!! ( and by brick I mean brick - only a board replacement or a JTAG unit will be able to save you, don't mess with boot(loader) stuff unless you *really* mean it! )
Note#1: using Triangle Away may unmount your SD card. Reboot or manually remount it from Android settings.
Note#2: on new devices like the SGS3/SGNote2/SGNote10.1, status can only be reset on some firmwares - they must be stock firmwares!
I am not clear on how to interpret the warning, other than it makes me a bit nervous about bricking the device. I did a quick search of USB JIG for the SGN10 and I didn't see anything come up in the first few Google pages. One placed discussed making your own JIG which involves soldering. Not my thing!
So my question is has any other GT-N8013 user performed the step of selecting the reboot into the special mode, and if so, what happens after that? More importantly, did anyone experience having their SGN10/GT-N8013 bricked from this step?
Again, sorry if this is basic to most, but it is new to me, and we all have to start somewhere.
Thanks,
'Bean

bookbean said:
I went ahead and downloaded Triangle Away. When I start in download mode, I receive the warning along with the big yellow triangle. After pressing volume up to continue, it goes into Odin Mode (in Red) and shows that the Custom Binary Download: Yes (5 counts), followed by Current Binary: Custom and then System Status: Custom. To get out of that screen, I have just held down the power button to turn off the device.
When I start up the Triangle Away app, the current status (under Flash Counter) says that Status cannot be determined, need to reboot into a special bootmode - tap "Reset flash counter".
In the Overview section on Play Store, it shows this warning:
On a number of devices, TriangleAway can work, but your firmware may not be supported directly. In that case, the app will tell you it needs to reboot into a special boot mode, which will be happen if you select "Reset flash counter". The device will reboot into a special mode which will allow you to review the current status and reset the binary and flash counter values (or abort and do nothing). On some devices this will actually trigger the counter to 1 if its 0 - so if you're "just checking", do that in download mode!
!!! THIS IS A DANGEROUS OPERATION AND COULD POTENTIALLY BRICK YOUR DEVICE. PROCEED AT YOUR OWN RISK. A USB JIG IS PREFERRED IF YOU HAVE A WORKING ONE !!! ( and by brick I mean brick - only a board replacement or a JTAG unit will be able to save you, don't mess with boot(loader) stuff unless you *really* mean it! )
Note#1: using Triangle Away may unmount your SD card. Reboot or manually remount it from Android settings.
Note#2: on new devices like the SGS3/SGNote2/SGNote10.1, status can only be reset on some firmwares - they must be stock firmwares!
I am not clear on how to interpret the warning, other than it makes me a bit nervous about bricking the device. I did a quick search of USB JIG for the SGN10 and I didn't see anything come up in the first few Google pages. One placed discussed making your own JIG which involves soldering. Not my thing!
So my question is has any other GT-N8013 user performed the step of selecting the reboot into the special mode, and if so, what happens after that? More importantly, did anyone experience having their SGN10/GT-N8013 bricked from this step?
Again, sorry if this is basic to most, but it is new to me, and we all have to start somewhere.
Thanks,
'Bean
Click to expand...
Click to collapse
I think there's no USB jig to Note 10.1. I have used TriangleAway for my I9100 few times and N8010 (same that your device but european) once and both worked fine, no bricks. After you boot in "special mode", you'll be shown your counter, and it will confirm are you sure, you can cancel it there if you want and it does nothing to your device. Just check that your download mode's counters match TriangleAway's counters.

After Special Mode
niko0o said:
I think there's no USB jig to Note 10.1. I have used TriangleAway for my I9100 few times and N8010 (same that your device but european) once and both worked fine, no bricks. After you boot in "special mode", you'll be shown your counter, and it will confirm are you sure, you can cancel it there if you want and it does nothing to your device. Just check that your download mode's counters match TriangleAway's counters.
Click to expand...
Click to collapse
Thanks for giving me the courage to give it a shot, which I have now done. The counter in the special mode matched what Odin was showing, so I went ahead with it.
Now when I start up holding down the volume down button along with the power button, I am still getting the Triangle. However this time, below the Odin Mode (written in red), it shows Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
I take it that because there is still root on the device, that the System Status will continue to show "Custom" and I will continue to have the triangle? I thought that the idea was to get everything to "look" official stock. Please let me know if I am missing anything else.
Thanks,
'Bean

I Got All Things Official By Flashing A Stock Rom Through Mobile ODIN Onto The Note At This Point BUT You Will Need To Factory Reset. You Will Also Go Back To Stock Recovery. If You Want All These Things To Display Official Status.
I Haven't Got It Back To Not Show Official While Running A Custom Rom As Current Binary Changes To Custom When You Install Cwm Or System Status Does.
Theres Also A Status In Settings> About> Status That Will Also Say Custom Too. Shouldnt Be A Problem Unless You Try To Use The Allshare Cast Hub...

ultramag69 said:
I Got All Things Official By Flashing A Stock Rom Through Mobile ODIN Onto The Note At This Point BUT You Will Need To Factory Reset. You Will Also Go Back To Stock Recovery. If You Want All These Things To Display Official Status.
I Haven't Got It Back To Not Show Official While Running A Custom Rom As Current Binary Changes To Custom When You Install Cwm Or System Status Does.
Theres Also A Status In Settings> About> Status That Will Also Say Custom Too. Shouldnt Be A Problem Unless You Try To Use The Allshare Cast Hub...
Click to expand...
Click to collapse
My understanding is that Allshare is useful only if you have other Samsung devices. So first, please advise if my understanding on that is correct. Assuming that this is the case, then I suppose that I do not need to immediately concern myself with getting all three settings to be "official", as I am in no immediate need (hopefully) to go back to full factory settings with official software since I do not own any other Samsung Android device. I am only beginning the root journey. I guess that it is good to have the bread crumbs to find my way back home at first, but I also want to be adventurous and try out some of these really interesting things which root is supposed to lead me to.
Is it fair to say then, that the counter thing shouldn't be a concern for now?

bookbean said:
My understanding is that Allshare is useful only if you have other Samsung devices. So first, please advise if my understanding on that is correct. Assuming that this is the case, then I suppose that I do not need to immediately concern myself with getting all three settings to be "official", as I am in no immediate need (hopefully) to go back to full factory settings with official software since I do not own any other Samsung Android device. I am only beginning the root journey. I guess that it is good to have the bread crumbs to find my way back home at first, but I also want to be adventurous and try out some of these really interesting things which root is supposed to lead me to.
Is it fair to say then, that the counter thing shouldn't be a concern for now?
Click to expand...
Click to collapse
To zero that last you need to flash stock firmware with Odin, but thats not necessary except if you need to return your Note to warranty or something.

bookbean said:
My understanding is that Allshare is useful only if you have other Samsung devices.
Click to expand...
Click to collapse
I own an allsharecast hub and I use it at school to lecture.I project the tablet screen to an hdmi LED TV which is not a Samsung brand.So no;you have a misunderstanding at this.And since I have a GT-N8005 device and triangle away doesn't support this device I can't use the 'reset flash counter' method:crying:

Allshare
ordeniz said:
I own an allsharecast hub and I use it at school to lecture.I project the tablet screen to an hdmi LED TV which is not a Samsung brand.So no;you have a misunderstanding at this.And since I have a GT-N8005 device and triangle away doesn't support this device I can't use the 'reset flash counter' method:crying:
Click to expand...
Click to collapse
Thank you for clarifying the allsharecast hub use and I am sorry that you cannot change your flash counter. Is it possible for the author of the program to modify it for your device? Perhaps you can contact them about it.

bookbean said:
Thank you for clarifying the allsharecast hub use and I am sorry that you cannot change your flash counter. Is it possible for the author of the program to modify it for your device? Perhaps you can contact them about it.
Click to expand...
Click to collapse
Thanks.I posted a comment on google play store,and I will contact them soon.

A: Having Problems Rooting the Note Pro 12.2 SM-P900/905? TRY THIS!

**NOTE** For the SM-P900! However steps should be the same for SM-P905 EXCLUDING THE FILE TYPES (THEY ARE DIFFERENT DO NOT ATTEMPT TO USE THE FILES FOR THE SM-P900 OR BYE BYE TO YOUR NOTE 12.2 Pro because now you have a problem that may or may not be repairable/reversible). You just have to make sure you have the coordinating files for the process!
If anyone else has issues try this and these steps to complete the Root/Custom ROM/TWRP Recovery installations successfully for a "First time go":
1. Remove Kies and Kies3 files, related files, folders, and everything that has anything to do with the primary installation of either the two programs on your PC and your devices. When/if prompted, select the checkable box and elect not save any type of files... if you want to keep them save them OFF your main PC on a flash or removable storage device.
2. REMOVE ALL SAMSUNG DRIVERS AND REPLACE WITH ONLY OFFICIAL SAMSUNG DRIVES!!! THIS IS A BIG MUST!
3. Using your USB 2.0 cable and ports Install the Custom Rom "P900XXUANB3-RecoveryImg.tar" FIRST and flash it via ODIN 3.07 under the PDA checkbox that is "fixed" (so you noobs don’t make any soft bricks if this is your first attempt at rooting), and only use the ODIN 3.07 THAT COMES W/ CHAINFIRES AUTO ROOT .zip file and then unzip the folder to open ODIN 3.07 ONLY! This is only because I have read that there have been issues installing the SU via Chain Fires Auto Root Process... the file is called (currently as of 25 JUNE 2014) "P900XXUANB3-RecoveryImg.tar" PDA select it and then start when in DOWNLOAD MODE on your device. Manually select DOWNLOAD MODE if you have to BEFORE PRESSING START! Otherwise, one is just going to sit there and not accomplish anything.
http://forum.xda-developers.com/attachment.php?attachmentid=2591013&d=1392923580
http://forum.xda-developers.com/attachment.php?attachmentid=2591159&d=1392930654
http://forum.xda-developers.com/attachment.php?attachmentid=2775098&d=1401644348
4 Reboot back into DOWNLOAD MODE. Flash in ODIN 3.07 with the PDA section and select this file next to install: "openrecovery-twrp-2.7.1.0-v1awifi.img.tar"
5. In DOWNLOAD MODE and flash the file under the PDA box TWRP (OR CURRENT RECOVERY OF YOUR CHOICE THAT IS AVAILABLE)
6. AGAIN... Restart your device into DOWNLOAD MODE via ODIN 3.07 and select PDA and then finally root this: "CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5" Then you can backup, restore, flash anything, and be happy! YOU SHOULD FINALLY HAVE A SUCCESSFUL ROOT! Turn off and REBOOT into RECOVERY to see if TWRP stuck and then reboot to see if the SU stuck. IF everything stuck reboot back into TWRP to flash whatever rom is available MAKE SURE TO BACK UP EVERY FILE BEFORE YOU FLASH ANY NON-STOCK ROMS. If not successful rinse wash and repeat until it does!
http://download.chainfire.eu/384/CF-Root/CF-Auto-Root/CF-Auto-Root-v1awifi-v1awifixx-smp900.zip
7. That’s it you should have root and a custom rom and recovery if you followed these instructions for flashing via ODIN 3.07 and Chainfires AutoRoot files. If you still have an issue repeat until root/recovery/Rom sticks. If you have to update the Binary for the SU just go to the Google Play Store and install the app and then try it again till it works. GOOD LUCK it worked for me this way!
**IMPORTANT**
BACK UP BACK UP BACK UP BACK UP after every flash that is possible to back up. If you can, back up the NON-SU stock ROM BEFORE installing SU, after installing the recovery and/or back up.
***IF I HELPED YOU OUT THANK ME***
DISCLAIMER - all research was observed via comments on the thread according to issues people have been having during ROOTING the device I simply have compiled the data and made a check list!

Need a link to the files you mentioned.

Thanks. Very helpful.
I have a P900. Is there a way to unroot and bring a unit back to stock? My main concern is if Samsung sends out a software/firmware update, and a device is already rooted, can the update be applied?

sstea said:
Thanks. Very helpful.
I have a P900. Is there a way to unroot and bring a unit back to stock? My main concern is if Samsung sends out a software/firmware update, and a device is already rooted, can the update be applied?
Click to expand...
Click to collapse
Read THIS
But still one quiestion, why the heck you root your device if you are going to update it via Samsung's official ways. Ah and one more question.. why the heck would you want to update your device if it's rooted?
A new update from Samsung can patch all known security holes and make your device unrootable, and since you are rooted now, one would think that you don't want to loose it. Or where do I know if you rooted because it sounded nice and cool, without knowing what you did and most importantly WHY you did.

Spere said:
Read THIS
But still one quiestion, why the heck you root your device if you are going to update it via Samsung's official ways. Ah and one more question.. why the heck would you want to update your device if it's rooted?
A new update from Samsung can patch all known security holes and make your device unrootable, and since you are rooted now, one would think that you don't want to loose it. Or where do I know if you rooted because it sounded nice and cool, without knowing what you did and most importantly WHY you did.
Click to expand...
Click to collapse
Thanks. I appreciate the reply. I have rooted many devices before. I have to admit that it was more of following posted instructions and not fully understanding the details. What gives me pause is how extremely limited the support is for this tablet. I want to root my note if I can make it more responsive, get rid of bloatware, enable more apps for multi-window, titanium backup, etc. I want to make sure that if I root that I don't get stuck with on an old release. So will previously rooted Notes be able to get the necessary files to easily update and maintain root, or does rooting now mean that a tablet may be stuck at the current release? Thanks

sstea said:
Thanks. I appreciate the reply. I have rooted many devices before. I have to admit that it was more of following posted instructions and not fully understanding the details. What gives me pause is how extremely limited the support is for this tablet. I want to root my note if I can make it more responsive, get rid of bloatware, enable more apps for multi-window, titanium backup, etc. I want to make sure that if I root that I don't get stuck with on an old release. So will previously rooted Notes be able to get the necessary files to easily update and maintain root, or does rooting now mean that a tablet may be stuck at the current release? Thanks
Click to expand...
Click to collapse
You can always flash stock firmware via odin

I was just wondering if everyone was having a much easier time with achieving root now? Kies caused me to "Hang" a lot during the Root and custom rom to stick w root... as of right now i can not get the only ONE custom ROM that looks promising, i have found by GWatts (correct me if i am wrong and i apologize if i have typed the wrong screen name handle) i believe his handle is... at this point im not sure what i am doing wrong as of yet but im sure i am missing a step or i just need to start back at unroot back to stock firmware and try and try again lol. not saying anything is wrong with his work at all by any means because people other than me with the same device have gotten it to stick and im just wishing i could as well because its sweet looking ROM! NOT TO MENTION THE ONLY ONE THAT IS OUT (that is which i know about. i haven't been on in a few months idk), SO KUDOS TO WATTS i just haven't been successful at installing his custom rom just yet... Im hoping that its just going to need to be erased again and then reformatted after a factory reset and what not, i pray it sticks because his incorporation of the aroma installer was a nice touch and his ROM really looks good... Now if i can just get it not to stick at samsung boot logo and freeze id be good lol!

sanvara said:
Need a link to the files you mentioned.
Click to expand...
Click to collapse
ok

I followed your instructions but while flashing the cf-auto-root file my screen got all distorted (speckled grains of color), and nothing else happened for about 15 minutes, until I just unplugged it and shut it off.
Now when I power it on it gives me the error "Firmware upgrade uncountered an issue. Please select recovery mode in Kies & try again."
I wonder what I did wrong.

pnuker said:
I followed your instructions but while flashing the cf-auto-root file my screen got all distorted (speckled grains of color), and nothing else happened for about 15 minutes, until I just unplugged it and shut it off.
Now when I power it on it gives me the error "Firmware upgrade uncountered an issue. Please select recovery mode in Kies & try again."
I wonder what I did wrong.
Click to expand...
Click to collapse
**Edit**
I went back and reflashed the twrp file and it got me out of the error screen. I installed supersu, and then re-flashed the cf-auto-root file, and it worked like a charm. I'm not sure if it was the installation of supersu, or just repeating the process that fixed it, but I'm happy either way...

Thank you! I succesfully rooted my SM-P900 after all mentioned problems ( hanging in the cache.img and after a while a disturbed screen etc.) with your guide. I am a very happy rooter now.

Thanks,
Thanks to the poster. I tried rooting with the instructions from a few other sites and thought I bricked it,
Followed your instructions, and presto.. Rooted! :good:

Rooted!
Thanks for your post. This is my first time ever rooting a device. Your method worked perfectly!

your welcome!
frankiecxyz said:
Thanks for your post. This is my first time ever rooting a device. Your method worked perfectly!
Click to expand...
Click to collapse
your very welcome! it took me a bit to get it down but i eventually figured it out and at the time information on rooting the device was hard to find with this specific model. then i discovered what the issues where and felt the need to post it! im glad i could help!:laugh:

Flash SU with TWRP not ODIN
Here's my story...
Received my new UK spec SM-P900 Note Pro 12.2, ran through the initial setup, performed two OTA upgrades to KOT49H.P900XXUANI1, then attempted to flash SU using Odin 3.07 using the various instructions on this forum. Result: failed cache flash and soft brick!
Used Keis 3 to recover the tablet which took two hours! After more reading I discovered the quick boot recovery flash method, so re-attempted on a different PC, with exactly the same result. Re-flashed the boot, tried again, fail, again, fail, etc, etc. Various permutations of PCs, Odin versions and USB ports were tried.
Concluded that the Odin method was NEVER going to work, so had a rethink. Used Odin to flash TWRP v2.8. Downloaded the latest SU-BETA v2.7 flash for TWRP (not Odin), copied it to the root of the tablet SD and then flashed it with TWRP. Worked first time with no messing about!!!
Booted, ran SU and upgraded to Premium, disabled KNOX from within SU. Tablet locked up. Booted, re-ran SU, disabled KNOX again, this time successfully. Ran Titanium, filtered with KNOX and froze all occurrences, then de-installed KNOX completely. :good:
Lesson learnt... DO NOT use Odin to flash SU on a P900 !

soft bricked
Hello!
First of all let me say that I'm a complete newbie, this is my first android device. I tried to root my SM-P900 (P900XXUANI1) using an online guide (image with URL attached, as I am not allowed to paste URLs)
Unfortunately at Step 10 (flashing with Odin) the operation failed and now I ended up with a soft bricked device (I assume this is the correct definition). It will only show the message asking me to connect it to KIES to recover it.
I know i can try to use KIES 3 and restore it, but before that i would like to ask if there is any alternative which will allow me to unbrick the device without losing all my data... (yeah i know...).
If i follow this guide will this help? I'm not sure if I can even put the device in download mode again as it shows the error message about connecting it to KIES...
At this point I don't care about rooting, I just want to unbrick the device.... I understand the guide up to (and including) step 3. But for the rest of the steps I'm lost Could anyone please explain them in a bit more detail? I don't want to install any custom firmware, just to unbrick it...
Any help would be very appreciated!
Thank you

Yemble said:
Here's my story...
Received my new UK spec SM-P900 Note Pro 12.2, ran through the initial setup, performed two OTA upgrades to KOT49H.P900XXUANI1, then attempted to flash SU using Odin 3.07 using the various instructions on this forum. Result: failed cache flash and soft brick!
Used Keis 3 to recover the tablet which took two hours! After more reading I discovered the quick boot recovery flash method, so re-attempted on a different PC, with exactly the same result. Re-flashed the boot, tried again, fail, again, fail, etc, etc. Various permutations of PCs, Odin versions and USB ports were tried.
Concluded that the Odin method was NEVER going to work, so had a rethink. Used Odin to flash TWRP v2.8. Downloaded the latest SU-BETA v2.7 flash for TWRP (not Odin), copied it to the root of the tablet SD and then flashed it with TWRP. Worked first time with no messing about!!!
Booted, ran SU and upgraded to Premium, disabled KNOX from within SU. Tablet locked up. Booted, re-ran SU, disabled KNOX again, this time successfully. Ran Titanium, filtered with KNOX and froze all occurrences, then de-installed KNOX completely. :good:
Lesson learnt... DO NOT use Odin to flash SU on a P900 !
Click to expand...
Click to collapse
Have you got a link to the odin rwrp 2.7 you used and the su 2.7 flash for twrp please?

VenomousViper said:
**NOTE** For the SM-P900! However steps should be the same for SM-P905 EXCLUDING THE FILE TYPES (THEY ARE DIFFERENT DO NOT ATTEMPT TO USE THE FILES FOR THE SM-P900 OR BYE BYE TO YOUR NOTE 12.2 Pro because now you have a problem that may or may not be repairable/reversible). You just have to make sure you have the coordinating files for the process!
If anyone else has issues try this and these steps to complete the Root/Custom ROM/TWRP Recovery installations successfully for a "First time go":
1. Remove Kies and Kies3 files, related files, folders, and everything that has anything to do with the primary installation of either the two programs on your PC and your devices. When/if prompted, select the checkable box and elect not save any type of files... if you want to keep them save them OFF your main PC on a flash or removable storage device.
2. REMOVE ALL SAMSUNG DRIVERS AND REPLACE WITH ONLY OFFICIAL SAMSUNG DRIVES!!! THIS IS A BIG MUST!.......
Click to expand...
Click to collapse
When i trying root, my SGN freeze in "cache". Odin show error and tablet goes to Emergency Firmware Recovery. Аnd it does not matter what program I use and how I do it.

Mine Reboots Constantly
I rooted my SM-900 about two weeks ago.
It worked great for a week until the device started rebooting by itself.
The first time a couple times a day, now it does it whenever as often as twice in 5 minutes.
Is there a way to see which app is causing this or does anyone know why this might be happening?
Though I rooted I haven't been poking around. I figured it'd be like using Linux but now I see it's not quite like that.
Thanks in advance.

sunnykhs said:
I rooted my SM-900 about two weeks ago.
It worked great for a week until the device started rebooting by itself.
The first time a couple times a day, now it does it whenever as often as twice in 5 minutes.
Is there a way to see which app is causing this or does anyone know why this might be happening?
Though I rooted I haven't been poking around. I figured it'd be like using Linux but now I see it's not quite like that.
Thanks in advance.
Click to expand...
Click to collapse
Have you cleared dalvic cache and cache in TWRP recovery? Be forewarned the process takes a while for cache wipe.
Sent from my SM-P900 using Tapatalk

TWRP Screen unresponsive; China version

Hey
Disclosure: I haven't played around much with rooting but I got a Samsung S6 SM-G9200 Model from China and wanted it get it up to speed with google services and such so I tried to follow instructions from rooting videos, downloading Odin 3.10 and the right software for TWRP.
I was able to get it to work but when I tried to work with google services, nothing ran. So I tried to unroot and reroot after realizing there were two different types of .tar or md5 files I had to use Odin to (flash?) onto my phone. Now I've tripped KNOX, tried to unroot and reroot, but TWRP is still there but SuperSU isn't. When I try to select the booting options (or any options) from TWRP screen, nothing responds. The power button locks, but I can't unlock the screen or anything.
I've tried looking around for answers, but I don't know how I can operate TWRP from my computer without having the softwares on my phone, nor do I know how to remove TWRP and try to re-install it to see if it will respond. Still don't have google anything.
I mainly want the phone to function like it would an American/Canadian phone so I can access the apps i want and remove a bunch of the installed apps from China (everything base, even the download window is chinese).
Any advice on how to proceed? I've been searching for a while now but I'm getting lost in a lot of general answers. I'll need a step by step for things related to the phone since I haven't programmed anything substantial before.
Thanks in advance!

honeybadger1121 said:
Hey
Disclosure: I haven't played around much with rooting but I got a Samsung S6 SM-G9200 Model from China and wanted it get it up to speed with google services and such so I tried to follow instructions from rooting videos, downloading Odin 3.10 and the right software for TWRP.
I was able to get it to work but when I tried to work with google services, nothing ran. So I tried to unroot and reroot after realizing there were two different types of .tar or md5 files I had to use Odin to (flash?) onto my phone. Now I've tripped KNOX, tried to unroot and reroot, but TWRP is still there but SuperSU isn't. When I try to select the booting options (or any options) from TWRP screen, nothing responds. The power button locks, but I can't unlock the screen or anything.
I've tried looking around for answers, but I don't know how I can operate TWRP from my computer without having the softwares on my phone, nor do I know how to remove TWRP and try to re-install it to see if it will respond. Still don't have google anything.
I mainly want the phone to function like it would an American/Canadian phone so I can access the apps i want and remove a bunch of the installed apps from China (everything base, even the download window is chinese).
Any advice on how to proceed? I've been searching for a while now but I'm getting lost in a lot of general answers. I'll need a step by step for things related to the phone since I haven't programmed anything substantial before.
Thanks in advance!
Click to expand...
Click to collapse
TWRP has the touchscreen drivers built in, so probably the one you flashed does not have them for the SM-G9200.
Also, you can try Philz Recovery, where the hardware buttons also work.

davebugyi said:
TWRP has the touchscreen drivers built in, so probably the one you flashed does not have them for the SM-G9200.
Click to expand...
Click to collapse
Thanks for the reply! Would I have to unroot first or can I directly flash that and proceed to see if TWRP works?
Thing is the first time I went around with the TWRP, it worked but afterwards it stopped working.

honeybadger1121 said:
Thanks for the reply! Would I have to unroot first or can I directly flash that and proceed to see if TWRP works?
Thing is the first time I went around with the TWRP, it worked but afterwards it stopped working.
Click to expand...
Click to collapse
Root has nothing to do with recovery (unless you want to flash it from a booted phone) So you can flash it straight away.

davebugyi said:
TWRP has the touchscreen drivers built in, so probably the one you flashed does not have them for the SM-G9200.
Also, you can try Philz Recovery where the hardware buttons also work.
Click to expand...
Click to collapse
Hey again... I'm so lost as to what I'm supposed to download from there. I downloaded each of the three links but none can be opened in Odin to flash (???)
At this point I just want a way to put google apps onto my phone - is there a step by step to do that? So far I haven't been able to directly download apk files and have them work. I keep getting the message, " Google Services stopped working" or If I try to log in with my account, it says " cannot communicate with google servers"
Any pointers?
Thanks in advance!

Change your phone .... with mine [emoji14] . I want 9200 for tdd bands
Sent from my Note 5 Duos S6

I got my touch screen in recovery working on my SM-G9200 by flashing the sprint version (I am using an a different international carrier and not sprint, but for whatever reason, it works)... Works perfect, I even backed up my phone and restored all working 100%... I cannot find the download link i used but the file is inside the zip attached below... Extract the zip file and flash the .tar file in odin... However this won't fix your "Google Services stopped working" problem, which is a different problem entirely and not something I am facing on my SM-9200

criszz said:
Change your phone .... with mine [emoji14] . I want 9200 for tdd bands
Sent from my Note 5 Duos S6
Click to expand...
Click to collapse
This will be my backup plan.... coming to canada soon?!!??
davewils55 said:
I got my touch screen in recovery working on my SM-G9200 by flashing the sprint version (I am using an a different international carrier and not sprint, but for whatever reason, it works)... Works perfect, I even backed up my phone and restored all working 100%... I cannot find the download link i used but the file is inside the zip attached below... Extract the zip file and flash the .tar file in odin... However this won't fix your "Google Services stopped working" problem, which is a different problem entirely and not something I am facing on my SM-9200
Click to expand...
Click to collapse
I'll try this and see if TWRP responds.
I"m about to break something here...

GT-N8000 downgrade and no update.

I've been using Gnabo v_7 version for quite a long time, and a very simple and beautiful day when I woke up my Samsung GT-N8000 was stuck on bootscreen. I wasn't able to do much so I got this "Brazil stock rom" that I found in a website, and it flashed all right, except for the detail that there is something at the screen that I haven't got a bloody clue how to remove. hahaha
And still, whenever I try to install another room, I got stuck at bootlogo and so on. I'm kinda lost here, mind a little help?
I traveled around the forum but well, I'm a little dumb so I couldn't find any proper information about, how to solve this. I would like to know if there is a way to remove this thing from the main screen, and post here the image for you guys to see it please.
I tried to post the image here to make it easier understanding, but since I got this login recently I can't =\
Thanks

Install custom recovery (if you haven't already. If you already have it installed, make sure to update to latest version), root device, wipe everything and flash custom ROM.

DroidTwe4kz said:
Install custom recovery (if you haven't already. If you already have it installed, make sure to update to latest version), root device, wipe everything and flash custom ROM.
Click to expand...
Click to collapse
So far I've tried the rom = N8000XXUDNE4 [still bootloop], then another 4.1 android version of other German rom XXALGA and nothing. Downloaded 3 Brazilian versions, and nothing. [I am from Brazil]. The only one that worked flashing using Odin was one called "KIES_HOME_N8000UBALGA_N8000ZTOALG3_N8000UBLG5.tar". And still, not recognizing my cellphone chip, and with some big watermark at the middle of the screen showing some information about the ROM and the version is 4.0. Even though this one worked fine, I was able to root and when I tried to flash another room, BANG! Bootloop again! =\
I was looking at the forum topics and I read some about ADB or something like that can fix this and "break" this bootloop making the device work normally again with the roms. But i haven't got a clue how to use it. Please help me! =\

vitortakeda said:
So far I've tried the rom = N8000XXUDNE4 [still bootloop], then another 4.1 android version of other German rom XXALGA and nothing. Downloaded 3 Brazilian versions, and nothing. [I am from Brazil]. The only one that worked flashing using Odin was one called "KIES_HOME_N8000UBALGA_N8000ZTOALG3_N8000UBLG5.tar". And still, not recognizing my cellphone chip, and with some big watermark at the middle of the screen showing some information about the ROM and the version is 4.0. Even though this one worked fine, I was able to root and when I tried to flash another room, BANG! Bootloop again! =\
I was looking at the forum topics and I read some about ADB or something like that can fix this and "break" this bootloop making the device work normally again with the roms. But i haven't got a clue how to use it. Please help me! =\
Click to expand...
Click to collapse
You can use ADB to push/pull files to Android. I don't know if you can use it to fix bootloop. With it, you can also reboot to recovery and sideload zip

DroidTwe4kz said:
You can use ADB to push/pull files to Android. I don't know if you can use it to fix bootloop. With it, you can also reboot to recovery and sideload zip
Click to expand...
Click to collapse
Well, after 2 days of research and paying attention on things here, I found out that my problem is "/EFS error". Meaning to use ADB to recover or fix it? But I don't know how to use this. I've downloaded 3GB of it but I was lost about using, and uninstalled. Is is there any short or better version and some good tutorial about using to retrieve my EFS so I can install another roms? I'm using original stock rom now, Brazilian android 4.0 and that's the only only the device is working fine but of course missing things as my cellphone card and the yellow message at the top of the screen. Please guide me through ADB.
P.s Is there a way to create /efs or something like so the device work properly? Cause I've deleted when I installed some rom, and I have no backup here. =\
Thanks!

vitortakeda said:
Well, after 2 days of research and paying attention on things here, I found out that my problem is "/EFS error". Meaning to use ADB to recover or fix it? But I don't know how to use this. I've downloaded 3GB of it but I was lost about using, and uninstalled. Is is there any short or better version and some good tutorial about using to retrieve my EFS so I can install another roms? I'm using original stock rom now, Brazilian android 4.0 and that's the only only the device is working fine but of course missing things as my cellphone card and the yellow message at the top of the screen. Please guide me through ADB.
P.s Is there a way to create /efs or something like so the device work properly? Cause I've deleted when I installed some rom, and I have no backup here. =\
Thanks!
Click to expand...
Click to collapse
Here is tutorial about how to install ADB and Fastboot drivers and use them. Unfortunately, I don't know how to use it to restore efs. Sorry.

Already rooted Samsung J5 - general inquiry

Hello guys. I just bought a used Samsung Galaxy J5 (SM-J500FN) with android version 5.1.1. The previous owner told me that it is rooted. Nothing seems weird with the phone other than when i try to factory reset it it takes me to a "bios" kind window where i have to manually choose to delete all data (hard delete i think its called), that and when i normally turn on the phone, at the top left corner it says "set warranty bit kernel". I was just wondering how do i go about installing custom roms since its already rooted, and can i unblock the default carriers (T-mobile) block for other sim cards. When asked how he rooted it (what method was he using) he said he just used Odin. I dont know much about rooting so, whatever you can tell me as to the handling of the phone would be amazing. Any other guides to installing some custom roms and making the phone easier and faster ( i only want functionality, don't care much about the UI) would be greatly appreciated. Thanks in advance.

luan96 said:
Hello guys. I just bought a used Samsung Galaxy J5 (SM-J500FN) with android version 5.1.1. The previous owner told me that it is rooted. Nothing seems weird with the phone other than when i try to factory reset it it takes me to a "bios" kind window where i have to manually choose to delete all data (hard delete i think its called), that and when i normally turn on the phone, at the top left corner it says "set warranty bit kernel". I was just wondering how do i go about installing custom roms since its already rooted, and can i unblock the default carriers (T-mobile) block for other sim cards. When asked how he rooted it (what method was he using) he said he just used Odin. I dont know much about rooting so, whatever you can tell me as to the handling of the phone would be amazing. Any other guides to installing some custom roms and making the phone easier and faster ( i only want functionality, don't care much about the UI) would be greatly appreciated. Thanks in advance.
Click to expand...
Click to collapse
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn

ShaDisNX255 said:
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
Click to expand...
Click to collapse
That's what I love about Samsung, as long as you have your ducks in a row, the files and tools are extremely easy to use, a 4 year old could do it.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

ShaDisNX255 said:
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
Click to expand...
Click to collapse
Thank you, ill be sure to check them out. Although, i would like to do the entire process from the beginning (root it again myself since i have no idea what the previous owner has done) and then try to install custom roms and other cool features rooting offers. I read that the KNOX security on samsung phones can pose some problems, any thoughts on that ?
Thank you again for your response.

ShaDisNX255 said:
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
Click to expand...
Click to collapse
Also, i use Linux so i hear the alternative to Odin is Heimdall, anyone have any experience with it, or should i just do it on a Windows PC?

luan96 said:
Also, i use Linux so i hear the alternative to Odin is Heimdall, anyone have any experience with it, or should i just do it on a Windows PC?
Click to expand...
Click to collapse
I've got no experience with Linux, sorry. SuperSU disables knox so there's nothing to worry about.

luan96 said:
Also, i use Linux so i hear the alternative to Odin is Heimdall, anyone have any experience with it, or should i just do it on a Windows PC?
Click to expand...
Click to collapse
If you're a Linux user and you have knowledge of using terminal commands then you should have no trouble setting up Hiemdall. Getting full USB functionality set up for the device in Hiemdall can be a pain if you aren't familiar with that kind of thing.
But, having a Windows PC will make a lot of things very simplified for you. A Windows/Linux dual boot system would be very handy to you if you can set that up. Then you could also use Kies/SmartSwitch if it ever comes to a point that you need it.
There are some handy rarely used instances with Linux when it comes to Samsung. They have no fastboot like other devices so only adb is usable. I think they primarily centered around Windows being the preferred OS to interact with their devices.

Droidriven said:
If you're a Linux user and you have knowledge of using terminal commands then you should have no trouble setting up Hiemdall. Getting full USB functionality set up for the device in Hiemdall can be a pain if you aren't familiar with that kind of thing.
But, having a Windows PC will make a lot of things very simplified for you. A Windows/Linux dual boot system would be very handy to you if you can set that up. Then you could also use Kies/SmartSwitch if it ever comes to a point that you need it.
There are some handy rarely used instances with Linux when it comes to Samsung. They have no fastboot like other devices so only adb is usable. I think they primarily centered around Windows being the preferred OS to interact with their devices.
Click to expand...
Click to collapse
Thank you for the info. I already have a dual boot on my pc with windows. I am an experienced Linux user and setting up Hiemdall should not pose a problem, but i opted to go for Windows since as you said makes things simpler.
Still looking for guides and tutorials on how exactly the root process goes. Doing research, so i guess its going to be a late night. If you have any links or pages you can guide me to for my Samsung J5 it would be amazing. Right now am looking around this forum and wherever the links lead me.
Thank you again.

luan96 said:
Thank you for the info. I already have a dual boot on my pc with windows. I am an experienced Linux user and setting up Hiemdall should not pose a problem, but i opted to go for Windows since as you said makes things simpler.
Still looking for guides and tutorials on how exactly the root process goes. Doing research, so i guess its going to be a late night. If you have any links or pages you can guide me to for my Samsung J5 it would be amazing. Right now am looking around this forum and wherever the links lead me.
Thank you again.
Click to expand...
Click to collapse
First, just to make sure that you are not walking blindly into some potential traps.
1) download the root checker app from Playstore, use it to verify whether the device is actually rooted.
2) power the device off, wait 5 seconds, hold volume up+home+power, when it boots past the logo, let go. It should boot to recovery, tell me what you see. Does it say TWRP with grey buttons on a black screen? Or does it have an android lying on his back and have options listed?
3) verify whether or not the bootloader is unlocked or not on your specific device model number with your specific build number/android version, if it's locked it will create problems if you try to flash custom recovery. Though you can flash CF autoroot with locked bootloader.
Then I'll help find what you need to do what you are looking to do. It may be simpler than you think.
If he in fact used Odin and the device is rooted, he did one of three things.
1) flashed custom recovery(TWRP) via Odin then flashed SuperSU.zip to root, not possible with locked bootloader.
2) flashed CF auto root via Odin, potentially leaving stock recovery if your bootloader is locked.
3) flashed a pre-rooted stock firmware via Odin, not likely though.
The first 2 being more likely than the last one, the second one being the most likely if your bootloader is locked.
Edit: @luan96, edited for more information.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

@Droidriven Thank you for the info. After a rough night of research i realized what i need to do. According to root checker, my phone is not rooted, and the recovery seems to be stock. This is very weird, since the phone is obviously not just the stock version that came from T Mobile. Im guessing its probably a badly done root or one that was removed. Anyways, this is how i am planing to proceed:
1. Turn on OEM Unlocking and USB Debugging from developer versions
2. Download CM Autoroot for my specific phone ( i do not know what is the difference between "normal" root and autoroot, but autoroot seems to be simpler and offers the same thing. Please correct me if i am wrong, i would love to know how to do a manual root as well if it has more benefits).
3. Volume down+home+power to get to the download screen
4. Launch Odin that comes with the autoroot package
5. Plug my phone into the USB and wait for Odin to add it.
6. Select the autoroot md5 file from the folder and begin the flashing process
7. Hope for the best and that my phone is still functional when it auto reboots.
After this i should check with Root Checker weather its properly installed or not. If it is, and i see the SuperSU application i continue to installing the custom recovery ( through some research i found out that TWRP is the best choice for me). Installing the custom recovery should be as easy as auto rooting the device. I should download the files from an official website, and flash them using the same process i did for AutoRoot.
After that its mod heaven. With my understanding so far, TWRP lets me install custom roms, and other things i might need.
This is what i plan on doing as soon as im done with a little more research. If anyone has any tips, corrections or general information on what to expect or do please share.
Many thanks to every contributor on this thread.

luan96 said:
@Droidriven Thank you for the info. After a rough night of research i realized what i need to do. According to root checker, my phone is not rooted, and the recovery seems to be stock. This is very weird, since the phone is obviously not just the stock version that came from T Mobile. Im guessing its probably a badly done root or one that was removed. Anyways, this is how i am planing to proceed:
2. Download CM Autoroot for my specific phone ( i do not know what is the difference between "normal" root and autoroot, but autoroot seems to be simpler and offers the same thing. Please correct me if i am wrong, i would love to know how to do a manual root as well if it has more benefits).
3. Volume down+home+power to get to the download screen
4. Launch Odin that comes with the autoroot package
5. Plug my phone into the USB and wait for Odin to add it.
6. Select the autoroot md5 file from the folder and begin the flashing process
7. Hope for the best and that my phone is still functional when it auto reboots.
After this i should check with Root Checker weather its properly installed or not. If it is, and i see the SuperSU application i continue to installing the custom recovery ( through some research i found out that TWRP is the best choice for me). Installing the custom recovery should be as easy as auto rooting the device. I should download the files from an official website, and flash them using the same process i did for AutoRoot.
After that its mod heaven. With my understanding so far, TWRP lets me install custom roms, and other things i might need.
This is what i plan on doing as soon as im done with a little more research. If anyone has any tips, corrections or general information on what to expect or do please share.
Many thanks to every contributor on this thread.
Click to expand...
Click to collapse
I would recommend using the command line to flash the twrp instead of the GUI if you want a simple process in linux
Run a terminal as a superuser (sudo)
heimdall flash –RECOVERY filename.img
Do step 1 and 3 you gave before before doing this
Or just flash the twrp image using Odin
J500FN twrp
https://dl.twrp.me/j5nltexx/

-Hope- said:
I would recommend using the command line to flash the twrp instead of the GUI if you want a simple process in linux
Run a terminal as a superuser (sudo)
heimdall flash –RECOVERY filename.img
Do step 1 and 3 you gave before before doing this
Or just flash the twrp image using Odin
J500FN twrp
https://dl.twrp.me/j5nltexx/
Click to expand...
Click to collapse
I'm going to use Odin for this. Since I'm quite new to the rooting community I dont want to mess things up on the first try. I'd rather get comfortable with some standard stuff before I proceed to try different variations. Thank you for your input. Though I would still like to know if I should use cm auto root or do a manual root. The difference is not quite clear to me yet. Again, thank you for your input, it is appreciated.

luan96 said:
@Droidriven Thank you for the info. After a rough night of research i realized what i need to do. According to root checker, my phone is not rooted, and the recovery seems to be stock. This is very weird, since the phone is obviously not just the stock version that came from T Mobile. Im guessing its probably a badly done root or one that was removed. Anyways, this is how i am planing to proceed:
1. Turn on OEM Unlocking and USB Debugging from developer versions
2. Download CM Autoroot for my specific phone ( i do not know what is the difference between "normal" root and autoroot, but autoroot seems to be simpler and offers the same thing. Please correct me if i am wrong, i would love to know how to do a manual root as well if it has more benefits).
3. Volume down+home+power to get to the download screen
4. Launch Odin that comes with the autoroot package
5. Plug my phone into the USB and wait for Odin to add it.
6. Select the autoroot md5 file from the folder and begin the flashing process
7. Hope for the best and that my phone is still functional when it auto reboots.
After this i should check with Root Checker weather its properly installed or not. If it is, and i see the SuperSU application i continue to installing the custom recovery ( through some research i found out that TWRP is the best choice for me). Installing the custom recovery should be as easy as auto rooting the device. I should download the files from an official website, and flash them using the same process i did for AutoRoot.
After that its mod heaven. With my understanding so far, TWRP lets me install custom roms, and other things i might need.
This is what i plan on doing as soon as im done with a little more research. If anyone has any tips, corrections or general information on what to expect or do please share.
Many thanks to every contributor on this thread.
Click to expand...
Click to collapse
Flashing CF autoroot will simplify rooting, again, just make sure you have the correct autoroot for your specific model number and firmware, flashing the wrong one can softbrick or hardbrick your device, this would require flashing stock firmware via Odin to repair if softbricked and more serious methods to restore if hardbricked. There isn't much difference in effect with the different rooting methods. They all get the job done about equally.
Just make sure that you verify that your bootloader is in fact unlocked BEFORE you flash TWRP. As stated earlier, if it is locked, it will certainly cause issues and you'll have to restore stock recovery and/or stock firmware.
As long as your bootloader is unlocked then your outlined plan should be good to go.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Droidriven said:
Flashing CF autoroot will simplify rooting, afain, just make sure you have the correct autoroot for your specific model number and firmware, flashing the wrong one can softbrick or hardbrick your device, this would require flashing stock firmware via Odin to repair if softbricked and more serious methods to restore if hardbricked. There isn't much difference in effect with the different rooting methods. They all get the job done about equally.
Just make sure that you verify that your bootloader is in fact unlocked BEFORE you flash TWRP. As stated earlier, if it is locked, it will certainly cause issues and you'll have to restore stock recovery and/or stock firmware.
As long as you're bootloader is unlocked then your outlined plan should be good to go.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Well, looks like i messed up somehow. I was fiddling around the recovery mode and Odin mode. Those were the only two screens i could view besides normal booting, so i was looking for any info.
Recovery Mode https://ibb.co/hotYZ5
Odin mode 1 https://ibb.co/nFfVE5
Once on the recovery mode, i selected "reboot to bootloader" hoping to find info if its locked or not. I got redirected to this screen
Odin Mode 2 https://ibb.co/kqhtZ5
And then i did what i think is the dumbest thing this year....i removed the batery and now when i try to turn on my phone -
Blocked https://ibb.co/kkOd1k
Please tell me i did not brick my phone without even trying to root it first. My understanding is that i accidentally wiped the current OS (softbrick?) and now i have to flash a new one and then continue with what i had planned. Or is this a small problem that can be fixed easier? Or a more serious one ? Good news tho maybe, i think that the bootloader is unlocked ?
Thank you @Droidriven for your info so far, you have been extremely helpful.
*EDIT* - Pictures didnt link correctly.

luan96 said:
Well, looks like i messed up somehow. I was fiddling around the recovery mode and Odin mode. Those were the only two screens i could view besides normal booting, so i was looking for any info.
Recovery Mode https://ibb.co/hotYZ5
Odin mode 1 https://ibb.co/nFfVE5
Once on the recovery mode, i selected "reboot to bootloader" hoping to find info if its locked or not. I got redirected to this screen
Odin Mode 2 https://ibb.co/kqhtZ5
And then i did what i think is the dumbest thing this year....i removed the batery and now when i try to turn on my phone -
Blocked https://ibb.co/kkOd1k
Please tell me i did not brick my phone without even trying to root it first. My understanding is that i accidentally wiped the current OS (softbrick?) and now i have to flash a new one and then continue with what i had planned. Or is this a small problem that can be fixed easier? Or a more serious one ? Good news tho maybe, i think that the bootloader is unlocked ?
Thank you @Droidriven for your info so far, you have been extremely helpful.
*EDIT* - Pictures didnt link correctly.
Click to expand...
Click to collapse
It looks to me like they attempted to root the device but didn't do it correctly.
FRP can be a pain to deal with. Some can be bypassed easily, those that have trouble bypassing must sign in with the original owner's original Gmail and password used to activate the device.
The method of bypassing FRP varies from device to device.
Did you factory reset in recovery? If so, that's why you FRP blocked you.
If you have stock recovery then you should not have been able to wipe out the OS using stock recovery, typically, only custom recovery can do that, unless you did something accidentally that somehow corrupted/wiped your OS.
If the OS is gone, you'll have to flash your stock firmware via Odin and start over from the beginning.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Droidriven said:
It looks to me like they attempted to root the device but didn't do it correctly.
FRP can be a pain to deal with. Some can be bypassed easily, those that have trouble bypassing must sign in with the original owner's original Gmail and password used to activate the device.
The method of bypassing FRP varies from device to device.
Did you factory reset in recovery? If so, that's why you FRP blocked you.
If you have stock recovery then you should not have been able to wipe out the OS using stock recovery, typically, only custom recovery can do that, unless you did something accidentally that somehow corrupted/wiped your OS.
If the OS is gone, you'll have to flash your stock firmware via Odin and start over from the beginning.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Thank you. At least its not just a paperweight. I'm installing new software on it with Kiesk 3 right now. Hope that works so i can do the rooting and TWRP install soon. I pressed "reboot to bootlader" to try and find out if its locked or not, but then it got me in download mode (without having to press up volume to contionue). After i turned off my phone by removing the battery, the OS was gone.

luan96 said:
Thank you. At least its not just a paperweight. I'm installing new software on it with Kiesk 3 right now. Hope that works so i can do the rooting and TWRP install soon. I pressed "reboot to bootlader" to try and find out if its locked or not, but then it got me in download mode (without having to press up volume to contionue). After i turned off my phone by removing the battery, the OS was gone.
Click to expand...
Click to collapse
Did you get this restored with Kies?

Droidriven said:
Did you get this restored with Kies?
Click to expand...
Click to collapse
Yes, i did. Worked like a charm, and even got the new 6.0.1 android on it. Also installed TWRP, and just finished installing Xposed Framework, now waiting for it to boot up ( i hear it takes some time). Seems all well so far. If any problems pop out ill be sure to post about it. Also thinking about making a new thread just to help newbies like me who really just want to remove some bloatware, and install some nice modules and not heavily mod the phone. You have been very helpful during this process. Many thanks to you ^-^ .

luan96 said:
Yes, i did. Worked like a charm, and even got the new 6.0.1 android on it. Also installed TWRP, and just finished installing Xposed Framework, now waiting for it to boot up ( i hear it takes some time). Seems all well so far. If any problems pop out ill be sure to post about it. Also thinking about making a new thread just to help newbies like me who really just want to remove some bloatware, and install some nice modules and not heavily mod the phone. You have been very helpful during this process. Many thanks to you ^-^ .
Click to expand...
Click to collapse
If you have issues with Xposed causing a bootloop, you can flash the Xposed uninstaller zip in TWRP to remove it, then troubleshoot why it bootlooped and try again.
Are you using the Touch wiz marshmallow Xposed framework?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE