Database Users

Asus Transformer EPIC NOOB GUIDE.

In the process of updating information for ICS update and custom ROMs, please hold tight!
A lot of folks have been coming in with newly purchased TF101's lately, which is AWESOME, it means the community will go on longer than the expected life of the device probably, since the TF201 and TF700 have come out and are seeking to replace our beloved TF, this is good news that people still buy the OG Transformer.
That said, there have been the same problems posted by new users, over and over, and sure there are guides for just about everything. But why not one on..just...EVERYTHING?
Here we go, troubleshoot problems and learn your device, the noob way! The EPIC TF101 THREAD BEGINS!
All the typical disclaimers apply, if you mess your stuff up, it is your fault not mine. I did not discover any of these methods, develop any of these tools, or do anything else but compile it all in one epic post. This should be everything you need to know as a noob, I do not take credit for anything, except for making it all easily accessible to those who are unwilling/unable to spend the hours searching that I did. In other words, I did a lot of work for you, but others had done the work for me first. Full credit to them.
What is ROOTING? And why do it?
So you bought a new TF, and you want to root it? Or you want to know what rooting is, for that matter? Rooting is a method of obtaining what is called 'Root Access' to your device, giving you control of it. The 'Root' is the parent directory of your device's internal memory, where the system files are stored. Generally this is kept from your access, you will need to get your device 'rooted' in order to change the system. Once rooted, you will have an app installed called 'Superuser' which will selectively grant applications permission to alter or access your root directory. This method differs on every device, but don't worry- we have a very easy device to root.
VERY IMPORTANT! Do NOT use any of the tools here WHILE YOUR DOCK IS PLUGGED IN!! All these are for use with the TF101 unit BY ITSELF! Please don't brick your device or mess something up by trying it with the dock plugged in!
There have traditionally been several ways to accomplish this for our device, as new applications and tools are developed to make it easier it has gotten to be a very simple process. Which method you use will depend on what SBK version (Secure Boot Key) Transformer you have, and also that model's firmware version. Your firmware version can be located by going to Settings>About Tablet. Current version is 8.6.5.21 (TF101) or 8.6.6.23 (TF101G). When either firmware version (also referred to as the 'stock ROM' sometimes) can be used, it will be listed similar to '8.6.x.19', where x can be 5 or 6 for TF101 or TF101G, respectively.
KNOW YOUR SBK VERSION
As a TF owner looking to mod your device, you need to know that there are multiple SBK versions, primarily SBK1 and SBK2. There may possibly be other versions to come even. All you need to know is, that as of right now, SBK1 is the only model that can utilize a tool called NVFlash to UNBRICK your device if you mess it up too badly, and it is difficult to tell which SBK version you have. In order to find out, there are a few tools out there- one of them is for mac only, called SBKDetect found here
http://forum.xda-developers.com/showthread.php?t=1232612
Another is primarily for Linux, but saavy Windows users can always boot from a Linux live CD on their machines to use it, called SBKDetect v2, here;
http://forum.xda-developers.com/showthread.php?t=1290503
The other way, if you are like me, and don't have Linux-abilities at the time of this writing (I'm working on that), you can always just GO FOR IT and try to flash a modded ROM via NVFlash. If you are SBK1 it will succeed. If not, it will fail. No harm done. Of course that means skipping ahead of a lot of learning first, so it is not advised IMO. It also means that if you DO have an SBK1 tablet, you just wiped all your data. It is not absolutely necessary to determine which SBK you have in order to root and mod your device.
A hit-or-miss way of detecting your SBK version is by looking at your device's serial number, located on the bottom of the device on a sticker. It will take the form of:
B70KAS638075
The ONLY digits you need to know are the FIRST THREE. Older models are SBK1. Manufacturing started at Bxx, and has gone to Cxx this year. All Cxx serial numbers will be SBK2. In fact it was in the middle of the B70 manufacturing that they changed the SBK version, so if you are B60, B50, B40 etc..you are sure to be SBK1. If you are B80, B90, C10, etc, you are sure to be SBK2. B70 owners, it's a coin toss. You must use one of the other methods to determine it.
The only thing that differs between SBK1 tablets and SBK2 tablets is the use of NVFlash. SBK2 cannot use NVFlash, so if you end up botching both your recovery and your ROM, and cannot boot into either, then you are SCREWED, so I would suggest reading everything before attempting to mod your device if you are an SBK2 owner.
NVFlash and APX mode
This was an early method used to root and flash recovery/roms, and is still a very useful application to have saved on a disk somewhere in the event that you own an SBK1, as it renders your tablet practically unbrickable. It can be found here;
http://forum.xda-developers.com/showthread.php?t=1123429
To use it you must enter APX mode on your TF101. This is tricky and confuses many users. The procedure is;
1. Press and hold volume UP and POWER buttons at the same time (it doesn't matter if the TF101 is on or off, if it is on, simply wait until it shuts off before proceding).
2. HOLD these buttons for approximately SIX SECONDS.
3. Plug TF101 into PC and listen for it to chime that it has detected it, it should load drivers and device will be listed in Right Cick>Computer/Properties/Device Manager/USB Universal Serial Bus Controller (or similar) as NVIDIA, not as ASUS.
4. If it does not, power on the TF and try again until it does.
NOTE: This is the only way to know if it is in APX mode as the screen remains powered off completely.
Once in APX mode now you can use NVFlash tool, place the system, boot, and recovery .img files into the root of the folder you extract NVFlash into and execute the download.bat file. If at any point the flash fails, this likely means you are SBK2.
ADB Mode
This stands for Android Debugging Bridge. This is not to be confused with APX mode, which is a separate thing entirely. To learn more about your device's ADB mode, see this excellent thread here;
http://forum.xda-developers.com/showthread.php?t=1071584
Another quick guide for ADB can be found here:
http://www.droidforums.net/forum/droid-hacks/6865-how-use-adb-all-commands-options.html
(sorry for the off-site link, trying to keep it as xda pure as possible!)
Razorclaw Root Tool
Razorclaw is by far my favorite method of rooting for the TF, it can be found here;
http://androidroot.mobi/2011/11/14/introducing-razorclaw-v1/
It does not matter what SBK version you have to use Razorclaw, that is why I prefer this method of rooting.. HOWEVER, it does require you to be using an older firmware version though. If you are on version 8.6.x.21 or above, you cannot use razorclaw. It works best on firmware 8.6.x.19. You simply install the app and follow the instructions (Root me nao!). It is a one click, native rooting tool.
If you are not on this firmware version and razorclaw will not work, there are options. You can either roll back your firmware version, the method is located here;
http://forum.xda-developers.com/showthread.php?t=1417006
If you are unsuccessful or want to try another way, you can use Nachoroot or ViperMOD.
Nachoroot Root Tool
This is one of the newer root tools, it is for all firmwares and all SBK versions, and can be found here;
http://forum.xda-developers.com/showthread.php?t=1427838
Nachoroot uses the ADB (Android Debugging Bridge) via a command prompt or terminal, all necessary drivers must be installed.
I cannot personally get this method to work because my PC will not install the drivers properly, and since I don't need the tool any longer, I must admit I've never used it, thus my bias towards Razorclaw. So, if you are having similar driver issues, rolling back firmware and using RC might be quicker and more painless.
ViperMOD Root Tool
ViperMOD is another method, similar to and related to Nachoroot, in that it uses the PC to root your TF101 and will need the appropriate drivers installed. The main difference being that this method will install Superuser as well. The other major difference is that while Nachoroot is done with a command dialogue, ViperMOD is done with a much simpler command interface (choose a number from a list of options rather than typing out commands). Interestingly enough, both of these methods work on both the TF101 and the TF201, and both methods appeared about the same time (posted on January 4th 2012). ViperMOD and Nachoroot represent the most recent methods for gaining root on the TF101. ViperMOD is unique that it has a feature to unroot your device as well, though you will need to have the stock ROM and recovery files available to completely return to stock. Find out more about ViperMOD here;
http://forum.xda-developers.com/showthread.php?t=1427125
I also cannot attest to the use of ViperMOD personally, I have used other methods, but many users have reported it quite simple to root with.
A quick breakdown;
Razorclaw, Nachoroot and ViperMOD will ONLY ROOT your device. No data will be wiped and you will have to install recovery later. In the case of Nachoroot, you will have to download superuser from the market, Razorclaw and ViperMOD installs it for you.
NVFlash WILL WIPE EVERYTHING! So understand that it will rewrite your TF101 internal memory competely and install a rooted ROM (or whatever you tell it to) on your device, as well as a boot and recovery image.
REGARDLESS OF THE ROOTING METHOD YOU CHOOSE, PLEASE READ THAT METHOD'S INSTRUCTIONS VERY CAREFULLY!!!
[Q]How do I know if I am rooted?
[A] Simply check within your app drawer for the superuser application (or download it from the market if using Nachoroot), to verify it works, download titanium backup and begin a batch backup and see if it asks permission, and if the batch completes. If you are not rooted, either try your first method again or try an alternate method.
Tip: Immediately after rooting you should back up your system with Titanium Backup, skip ahead to that section to learn how before moving on.
Recovery Mode
The stock recovery mode on the TF101 shows one of two screens; a green android in the middle of the screen with gears turning inside it, or the same android with a yellow triangle with an (!) inside it instead. The gears obviously mean it is working (flashing firmware), the (!) means something has gone wrong (no file found, flash failed). To enter recovery mode, you need to press and HOLD Volume DOWN and POWER when the device is powered OFF. As soon as the screen comes on, RELEASE THE POWER BUT HOLD THE VOLUME STILL. You will see white letters appear in the upper left corner of the screen, it is now okay to release the Volume DOWN button and quickly (within 5 seconds) press the Volume UP button to enter recovery mode. There are also applications, such as Reboot to Recovery, available on the market, that will allow you to reboot your device with one click into recovery mode without having to toggle your power/volume buttons.
About Stock Recovery Mode
The stock recovery mode is absolutely required to install official Asus OTA (Over The Air) updates. Unless your device is unrooted with a stock recovery mode, you will not be able to install any OTA updates, this includes ICS!! It can also be used to install (or RE-install if it were) your STOCK ROM (only official, digitally signed files will be accepted by the stock recovery to flash over the firmware, no modded roms will work). The method for doing this is outlined in the link for rolling back your firmware version above but I will summarize;
Recovery mode searches your external SD card ROOT DIRECTORY(and the internal memory's cache directory, but this is not useful for any practical reason for you) for these Asus files. The files must be named either;
EP101_SDUPDATE.zip
or
XX_user-epad-Z.Z.Z.ZZ.zip (X = firmware region stamp, WW, US, DE, etc, and Z - firmware version, 8.6.5.19, 8.6.6.21 etc)
I personally find the second configuration to work best. If stock recovery finds a file named appropriately and signed with the proper digital signature it will install it, and you will see gears turning. Otherwise; (!). Remember, it has to be on the SD card in the ROOT, not in a folder or it won't find it.
CWM Recovery Mode
ClockWorkMod Recovery mode replaces your stock android recovery mode, and gives you control of;
Flashing (installing) ROMs, recovery, themes and app packs, patches, kernels and more
Wiping cache, dalvik cache, system, data, etc
Backup and Restore features
Advanced features you probably won't need like fixing permissions and mounting partitions etc.
The important thing to know is if you want to be able to change ROMs right from your device, you need this. In order to install it on the TF, you can use an app called RecoveryInstaller, located here;
http://forum.xda-developers.com/showthread.php?t=1346180
It is a one-click app just like Razorclaw, download and a single click will install CWM for you, though it may be an older version it will work fine to install the most recent version, directly from CWM once you enter it the first time. You will need to give it superuser permission as well. The newest CWM for the TF101 is called ROGUE XM and it is available here;
http://forum.xda-developers.com/showthread.php?t=1446019
Simply place the newest version on your SD card where you can find it, and use the 'install from SD card' option to navigate to the new version file and select it, which will flash the recovery..then you will need to reboot.
CWM Recovery can also be installed when flashing your device from NVFlash, and the NVFlash versions of ROMs almost always contain the most recent versions of the CWM recovery as well, thus making an NVFlash a one-step procedure (flashes both ROM and recovery at same time). The risk of the one-step procedure is if you are using corrupted images or something unexpected occurs you may end up BOTCHING both recovery and ROM at the same time..of course- if you are SBK1 anyways, just reflash it with a different ROM and it will be fixed.
Once you have installed the latest CWM recovery now you will want to start flashing ROMs and Kernels. I will not be posting links to the custom ROMs and Kernels because there are too many of them, that will be your homework.
Custom ROMs
We are blessed to have some great devs working on our humble TF101. That said, the procedure to flash a ROM through CWM is simple;
1: Download desired ROM and place into your external SD card somewhere you will be able to find it, it doesn't matter.
2: Boot into recovery and go to Backup and Restore and make a backup file. This is commonly referred to as a 'Nandroid' backup, and will backup everything from your ROM to your Kernel to user files.
3: Once backed up, proceed to factory reset and wipe cache partition and dalvik cache, located in the 'advanced' menu.
4: Install from SD card, navigate to your directory and find your ROM (ONLY FLASH THINGS THAT ARE MADE SPECIFICALLY FOR THE TF101! Be sure it is compatible with your device!) and select it, scroll to yes...read and follow instructions. Tapdance and sing ABC's while making some breakfast- and you are done!
5: Reboot device
Please be sure to flash only files that are meant to be flashed via CWM, as some ROMs will also have an NVFlash version, which will not work in CWM.
The Stock ROM currently provided with the TF101 is Android 3.2.1, which is called Honeycomb (HC) which is exclusively for tablets, we are all awaiting the release of Android 4.0 commonly known as Ice Cream Sandwich (ICS) which will merge the operating systems used on phones and tablets. Asus has said it will be out soon, so don't ask when it is coming! To learn more about the different Android versions, read this;
http://en.wikipedia.org/wiki/Android_version_history
I would suggest also to anyone wanting to modify their Android device to understand the history of Android itself and what it is, here;
http://en.wikipedia.org/wiki/Android_(operating_system)
Kernels
The kernel is the underbelly, the brain of the ROM. The kernel is what tells the hardware what to do when you interact with the software of the ROM. Most ROMs, I dare say almost every ROM unless specifically noted, does NOT come with it's own kernel but uses the kernel you have installed now on the device, unless it is a stock ROM, in which case most of them DO have kernels included. You want to be sure if what you are flashing has a kernel included or not, and you can always go back to another kernel version if you like, but understand that the OS will behave differently with different kernels. For example, if you wish to enable certain functions at the kernel-level, like overclocking, voodoo sound, etc, then you have to flash a customized kernel.
If you flash a custom kernel, then report your bugs to the developer of the kernel, not the ROM, as most bugs are produced by the kernel.
The procedure to flash a kernel is the same as with flashing a ROM, though you need not factory restore your device before installing, although every developer will agree that it is probably best to have what is called a 'clean install', where you would factory reset the device, flash your ROM, and flash your Kernel, and then restore your apps and information. How do you do that you say?
Titanium Backup
Titanium Backup is an app that is pretty self explainitory- it backs up all system files, data (this includes contacts, settings, call logs, etc) user apps, basically saves your state ON TOP of your ROM, where as the CWM Backup (commonly called a 'Nandroid') is the FULL ROM, Titanium Backup will only restore your settings and apps ON TOP of the ROM once installed. Therefore, you can backup all apps, safely factory reset. Install a clean ROM and Kernel together and then restore your data on top of them. This keeps your user files from either being accidentally overwritten or otherwise interfering with the installation of the ROM/Kernel whatever else you wish to flash.
IF YOU SKIPPED AHEAD READ THIS
Titanium Backup can be found on the market for free, if you like it, buy the paid version.
To backup and restore, simply press the settings softkey and choose 'batch' and select the appropriate action with caution. Press the 'RUN' button for the action of your choice and you will be prompted with a checklist of apps and data to run the batch on. Select which files you want or select all if it is your first time using the app and confirm the action. You will need to give Titanium Backup Superuser permission and make sure you have 'Unknown Sources' checked as well as 'Debugging Mode' checked in your settings/applications menu.
Ok, now go back to 'Recovery Mode' section and keep reading..
Also understand that if you are moving from a version that you have backed up in which apps will not be useable in the version you are moving to, the will not work either. For example, if you flash an ICS ROM and then save the ICS-only apps with titanium backup, and then try to move back to honeycomb or gingerbread (if you have a phone like I do) these apps will likely not install or if they do will FC (force close) constantly. Similar things can happen with user data, call logs from one dailer might not be compatible with an older version etc, so expect there to be instances where you have to selectively install apps one at a time to see if it causes bugs, testing the device for buggs, and uninstalling the app/data before proceding with your restore if it does.
Return to Stock
EDIT: While the below represents a review of how we used to unroot, I have now learned that merely flashing the stock ROM provided by Asus on their website will flash the recovery as well, and that there is a minor difference between the recovery img that came on the device stock versus the recovery img that comes loaded in the Asus firmware packages. If nothing else, the graphics are different, but I suspect that there could be other changes as well. To best unroot the device, simply watch and follow the video in the link.
Outdated info;
So, you played around, and you decided it was time to go back stock for that update, or maybe you just liked it better, or you wanted to give it to your grandma but knew Revolver was above her head- whatever the reason, you want to start fresh. The procedure requires you to get the Stock recovery image and a stock ROM. Luckily the stock ROMs are available on Asus' website, the recovery image isn't as easy to find, it is located here;
http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/
(Note: The recovery file is not region-specific, therefore it does not matter what version TF101 you have, it is one of the few 'universal' files for this device.
CAUTION: Unrooting with this procedure will only rewrite your system files on the system partition, if you have files located in your root directory that are user-created files that are not part of the system, these files will remain after unrooting, though you will not be able to view them as they are in the root directory, if you root the device again they will be visible. If selling your device or returning for an exchange and you are unrooting it, make sure to manually delete any files/folders that you created in your root directory and do a factory restore with CWM before flashing over your recovery.
Click to expand...
Click to collapse
Procedure:
Click HERE to watch my UNROOTING How-to video.
There should also be a distinction made here between unrooting and breaking root access, while breaking root access will prevent you from having root access to your device, it does not return your device to stock. For example, deleting your superuser application and su binary files can 'break your root' as it is referred to. Yet, in order to effectively unroot your device, you should return the device to it's 100% stock configuration. If you are giving the tab to your grandma or little sister, breaking root is probably enough. If you want to return the device or sell it on XDA, you should probably return to stock completely.
Now that you have read all of this (hopefully) here is the shortcut you wished you had;
My HOW TO ROOT video (Part one)

So, now you are a BUTTFLIPPIN' PRO, you can root, you can flash recovery mode, ROMs, even Kernels, and you can flash stock files from your SD card so you can unroot and return to stock if you want. What if something goes wrong? What if you want to expand your knowledge?
Well this is what we all fear, this section will attempt to address possible outcomes of bad flashes, corrupt ROM images, bad recovery images, etc. as well as help you diagnose your problem and determine whether you need an RMA or to ask for help in the forum.
[Q] My screen won't come on! Help!
[A] In order to determine what the problem is, first try to power on normally, if that does not work try to power on with the USB device plugged into a PC, if you hear it connect you unfortuntely likely have a screen malfunction. If not, try to enter APX mode and listen for notification of connecting to your PC, if still no notification, try charging your tablet overnight and see if it is over-discharged, mine did this once and scared the CRAP out of me, I thought it was bricked, after 10 minutes of fooing with it a battery warning finally popped onto the screen for 1 second before shutting off again. Repeat the previous steps after 24 hours of charging (if TF does not power on on its' own). If none of these solutions work, try powering on and listening for the camera to 'click', if you do not hear this, then it is very likely you have a brick or malfunctioning device.
[Q] My dock drains very fast..why?
[A] This is a problem with old firmware and certain docks. The docks themselves were manufactured with hardware that prevents the updated firmware from being installed in the dock itself, which results in being unable to change the battery consumption configuration. The dock was originally designed to keep the TF awake so that a quick key press would wake it easily, but this resulted in battery drain, when Asus updated the firmware they realized some docks simply needed to be RMA'd. To test yours;
1. Make sure you are updated to the latest firmware for the dock (in Settings?About Tablet), latest firmware is EP101-0213.
2. In Settings>Screen make sure "MobileDock Battery saving mode" is checked.
3. Press the power button on the TF101 to turn the screen off, then press a key on the keyboard (not the mouse buttons).
If any key wakes the TF, then you have the defective dock and must be RMA'd. However if it does not wake, and you still have severe drain, try to resolve it by shutting off background services and checking to see if drain is bad without the dock as well. If it is still draining, as mine has done previously, contact Asus for an RMA.
[Q] My dock is making a strange squealing sound??
[A] Yes, I received one that did this myself, and returned it to the store I purchased it. As far as I could tell it only presented an annoyance, but others reported the issue and suspected that it might have been connected with some people's battery drain issue, so I returned mine as you probably should as well.
[Q] My screen has light bleeding around the edges..is this common?
[A] Unfortunately, yes, light bleed on these devices is far too common. You can try to return the device and get a better one, depending on the severity of the light bleed, and unfortunately it seems every device has it's quirks, you may end up with one that doesn't have much light bleed but has another problem..
[Q] My case creaks, is this normal?
[A] Yes, unfortunately, the plastic backplate has notches that are supposed to affix into the bezel, and sometimes these come loose. However, some people have reported being able to 'snap' it into place again within the bezel, others had to remove the bezel and backplate partially to resolve the issue- others just ignore it as it is only cosmetic.
[Q] My Transformer won't charge! Help!
[A] There could be a few reasons for this experience- the connector is a proprietary connector, and the wires inside can be easily tangled and snapped according to user experience- to verify that the cable works try plugging the device while powered on into the PC and listen for audio confirmation. If your cable is working, but the tablet doesn't seem to charge, you can try to plug in the dock to see if the led on it lights up (unfortunately the TF unit has no charging indicator except for when powered on). The charging adapter itself sometimes has connection problems inside it, and some users have reported success in simply enclosing the charger in a ziplock bag and placing it in the freezer for several hours. I don't know why this works for some, but it does. If it doesn't for you, however, you may need to order a new power adapter from Asus, or you can make your own here;
http://forum.xda-developers.com/showthread.php?t=1087321
[Q] My TF keeps booting and booting but never loads into my ROM..
[A] This is called a 'bootloop', and depending on how far it loads can tell you the severity of the boot loop. First thing to do, is to attempt to boot into recovery. Unless you have an SBK1 tab, this is going to be the only way you will be able to stop this. If not, you have a soft-brick. Eee Pad logo loads and reboots after this, then you have a problem with the ROM itself not wanting to boot (corrupt image, files missing, etc), and usually reflashing your previous ROM without wiping will cure the issue. Sometimes the issue is within the ROM, settings that lock up your device while initializing. If it makes it to the boot animation and reloads, there is a possibility that it is a setting within a kernel if you have a custom kernel installed, try another one, if you aren't running a custom kernel it could be user settings and a factory restore may resolve the issue, and if that fails try another ROM. If the TF will not go into recovery mode and reboots within 5-10 seconds from powering on, you might have a major problem with your system in which case only NVFlash is likely to help.
[Q] I keep getting FC's and bugs..(OR) Do I need to wipe to install...?
[A] Making sure you wipe the correct partitions before you flash new software is vital to making sure it functions properly. This is your necessary wiping procedure, although always best to have a clean install as previously stated;
Nature of the flash| Wipe cache? Wipe Dalvik? Factory Reset?
Clean ROM Flash = YES YES YES
Kernel Flash = YES YES NO
App Pack Flash = YES YES NO
Theme Flash = YES NO NO
ROM Re-flash = NO NO NO
Recovery Flash = NO NO NO
Nandroid Restore = NO NO NO
(Will work on getting this more graphlike after dinner )
Of course always better safe than sorry, and unless you are trying to preserve user apps and data while flashing a kernel or theme then it is always best to reinstall everything after a clean wipe to avoid orphan files and other messy possible errors.
[Q] I can't get into recovery! Help!
[A] The only time you really need to start worrying about not being able to get into recovery is if your ROM also will not load, and vice versa. Since you can simply use the RecoveryInstaller app to fix your broken recovery, similarly if your TF will boot into recovery mode but NOT into the ROM you simply flash (or re-flash) your previous ROM to restore your OS. For this reason, when wishing to update BOTH ROM and recovery, DO NOT FLASH BOTH AT ONCE WITHOUT CONFIRMING THE FIRST FLASH WORKED!
My general rule is to flash my recovery mode first, and then flash my ROM, this is true whether going forward in versions or rolling back to older versions. This way, as soon as you are done flashing and restart (simply holding Volume DOWN as it reboots on its own is enough to initiate recovery mode, be sure to then press Volume UP), you will know if your flash was a success and can rest easy as you flash your ROM, if done the other way around you have to boot into your OS to confirm the flash worked and then reboot back into recovery. If your recovery flash fails, simply allow the OS to load, load recovery installer again and try again.
In the case in which your ROM or recovery will not load, again, your only hope is that you are an SBK1 device and can restore your device via NVFlash.
[Q] Help! My buttons (volume, power) don't work!
[A] Unfortunately this has been discussed quite a bit, sometimes it is related to poor manufacturing, or user damage, or even a poor RMA service. In this case you have only two options- you can try to RMA it, or you can try to tear down the TF101 yourself to try and repair it. It isn't advisable if you can get it repaired under warranty, but if not, you can find discussion with photos of a teardown of the unit here;
http://forum.xda-developers.com/showthread.php?t=1109928
[Q] How do I edit the files in my root directory?
[A] The File Explorer app provided by Asus by design will not allow you to access the root directory, you must use an app, like Root Explorer. In order to change or delete files directly from this app, you will need to make sure the root is mounted as R/W (readable/writeable) as opposed to R/O (Read Only), there will be an option to 'mount R/W' if it is mounted currently as R/O, and vice versa.
[Q] How do I remove Asus' Pre-Installed apps (Bloatware)?
[A]While you can simply delete the app file with your Root Explorer, this may not delete all user data. You could download a tool called Root Uninstaller from the Android Market, or you can use the functions in Titanium Backup to run batch uninstalls, or just 'deselect all' and delete one at a time.
[Q] How do I get back my Asus or Google apps after flashing a modded ROM?
[A]GApps and Asus apps generally are not included with many custom ROMs for copyright reasons, but GApps can be found here;
http://goo-inside.me/gapps/
Asus apps can be found in Gnufabios' package 'Asus Removed Apps' that can be acquired through his Revolver Parts package if you are running that ROM, or can be downloaded here if not;
http://www.gnufabio.com/revolver/dls/
Or you can always make a Titanum Backup of your valued system apps before you flash your ROM. You can then do what I do, find the Titanium Backup folder on your internal and rename it 'TitaniumBackupStockApps' and move it to your SD card, then backup your user apps, rename THAT folder 'TitaniumBackupUserApps' (you may even want to date it or name which ROM it came from, this is your choice), and remove that from your internal memory. You could then do the same with user data, if you decide to do that separately. To flash them back, simply replace the folder and rename it to the 'TitaniumBackup' as it was originally, or, if the folder already exists you can simply copy over the contents, run the batch, then delete the contents and copy the user data contents over as well. This is a great way to keep your apps and data organized and backed up safely. You should make sure this stays up to date and delete old backups after 2 to 3 iterations.
[Q] Can I run Linux?
[A] Yes, look here;
http://forum.xda-developers.com/showthread.php?t=1364095
[Q] How do I install themes?
[A] Depending on the ROM and Launcher you are using, some of the theming options can be built in and accessed in settings menus inside the Android UI (User Interface). However, there are other themes that change files within your root directories and these files will generally need to be installed either via CWM or via ADB. The themes' developer should have clear instructions on installing it.

One more reserved.. This one is for my thank-yous and anything else I miss guys
Roach2010, mike1986, gnufabio, xboxfanj, blades, Clemsyn, baseballfaz, danzano, paulburton, kaijura, daoist, supercurio, MrNago, jcarrz1, rayman84, lilstevie, rburrow, solarnz, fonix232, daxtsu, dipje, frankc123, Sharpe351, chatch15117 ,K900 ,earthbound, AproSamurai, TOO MANY TO REMEMBER YOU ALL!!
You guys are why I am able to do what I do now..

Mods: Stickie this!!!!

This is great! Have my tf a month and had to search all over to root/rom/etc.wish I'd had this info
Great help for us tf noobs.
Sent from my Transformer TF101 using xda premium

Thanks for taking the time to write this up!
Absolute champ!

nice one..thanks mate

Get work this is a must have guide
Sent from my EVO Titan 3D

Fantastic! Having current info all in one place is rare, especially on "older" devices.
Edit: Maybe add a section or note about ViperMOD

Nice job Luna.
+1 on the vipermod. That is what I used and it was extremy simple.

ViperMOD..the one thing I have no experience in on this device it seems; I did a crash course, seems it was actually based right off of Nachoroot, just a cleaned up command prompt interface, and interestingly works on TF101 and TF201. Perhaps that is why I never used it- the post is located in the Prime forum section
Added to OP, guys help me check for accuracy, and correct me if I get anything confused.
Next have some few things to polish up in my thank-yous and try not to leave anyone slighted. Also, thinking of a few more common problems to add to post two. Anything not addressed here just comment or PM me about it I will amend these posts.
THANKS!

Hi Luna
I tried to follow the Return to Stock instructions you listed but there seems to be some problems.
I know these problems are not your fault but maybe you know of another alternative which is as easy to follow as well?
I need a WW Version of the packed stock Rom but neither US nor WW are available due to the mediafire problem.
And the recovery is called 8239USrecovery so I assume I can't use it with my WW version?
Return to Stock
So, you played around, and you decided it was time to go back stock for that update, or maybe you just liked it better, or you wanted to give it to your grandma but knew Revolver was above her head- whatever the reason, you want to start fresh. The procedure requires you to get the Stock recovery image and a stock ROM. Luckily the stock ROMs are available on Asus' website, the recovery image isn't as easy to find, it i located here;
http://theunlockr.com/2011/11/28/how...s-transformer/
Place both files on your SD, but make sure the ROM file is in root (they can both be in the root it doesn't matter) and then use CWM to flash the recovery image, then WIPE EVERYTHING before rebooting into recovery mode again to confirm you have stock recovery in place, and allow it to flash stock ROM. Double check that you are unrooted by downloading superuser and installing it and seeing if it allows you root access (it should not).
Click to expand...
Click to collapse

luna_c666 said:
About Stock Recovery Mode
The stock recovery mode is absolutely required to install official Asus OTA (Over The Air) updates. It can also be used to install (or RE-install if it were) your STOCK ROM (only official, digitally signed files will be accepted by the stock recovery to flash over the firmware, no modded roms will work). The method for doing this is outlined in the link for rolling back your firmware version above but I will summarize;
Click to expand...
Click to collapse
So theoretically this stock recovery mode will allow us to recover to a stock Asus signed ROM in case the main ROM get damaged? for example if rooting goes wrong or any other reason?
I have an SBK2 TF101, and I don't want to install CWM for the moment but want to have root, and don't want to brick my pad.

Outstanding post. Thanks a lot...
Sent from my Transformer TF101 using Tapatalk

Malandro2011 said:
Hi Luna
I tried to follow the Return to Stock instructions you listed but there seems to be some problems.
I know these problems are not your fault but maybe you know of another alternative which is as easy to follow as well?
I need a WW Version of the packed stock Rom but neither US nor WW are available due to the mediafire problem.
And the recovery is called 8239USrecovery so I assume I can't use it with my WW version?
Click to expand...
Click to collapse
The recovery mode can be used regardless of region or firmware version, and if you are unable to locate the firmware files due to mediafire and megaupload etc. being down, simply retrieve them from Asus' website here;
http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#download
I'll update the OP to make this more clear

mcbyte_it said:
So theoretically this stock recovery mode will allow us to recover to a stock Asus signed ROM in case the main ROM get damaged? for example if rooting goes wrong or any other reason?
I have an SBK2 TF101, and I don't want to install CWM for the moment but want to have root, and don't want to brick my pad.
Click to expand...
Click to collapse
Yes, if you retain your stock recovery mode then it will be able to flash your firmware in the event that your ROM gets messed up for whatever reason, so long as you use the Stock signed copies of your firmware from Asus (i.e. the official files), recovery mode as stated will only flash official Asus files, they are digitally signed by Asus and without the signature recovery mode will fail.
And to put you at ease, the likelihood of anything going wrong while rooting is much smaller than flashing custom ROMs or recovery mode. Rooting is fairly fail-safe if you follow directions well.

luna_c666 said:
Yes, if you retain your stock recovery mode then it will be able to flash your firmware in the event that your ROM gets messed up for whatever reason, so long as you use the Stock signed copies of your firmware from Asus (i.e. the official files), recovery mode as stated will only flash official Asus files, they are digitally signed by Asus and without the signature recovery mode will fail.
And to put you at ease, the likelihood of anything going wrong while rooting is much smaller than flashing custom ROMs or recovery mode. Rooting is fairly fail-safe if you follow directions well.
Click to expand...
Click to collapse
I am asking because, as mentioned earlier, I only need to root for now without going the whole mod thing, because at the moment I am still not convinced that an android tablet suits me, so in case I still don't like it I want to be able to restore the stock ROM without going more into modding CWM and risking a brick.
So, in the case I root then later decide that I want to unroot, it is enough to put the signed stock Asus firmware on the SD card and boot into recovery mode, and it will be unrooted? why is it then that most unrooting guides does this with a special repacked zip file? why not just stock asus zip?

sticky!

mcbyte_it said:
I am asking because, as mentioned earlier, I only need to root for now without going the whole mod thing, because at the moment I am still not convinced that an android tablet suits me, so in case I still don't like it I want to be able to restore the stock ROM without going more into modding CWM and risking a brick.
So, in the case I root then later decide that I want to unroot, it is enough to put the signed stock Asus firmware on the SD card and boot into recovery mode, and it will be unrooted? why is it then that most unrooting guides does this with a special repacked zip file? why not just stock asus zip?
Click to expand...
Click to collapse
First, you should know that if you do not install CWM and flash a custom ROM, you will never actually know what you can do with an android tablet
But to answer about why others use special zips, unrooting with the Asus file actually does not delete anything on your system partition, it will simply rewrite all the system files, if there are other files that are unrelated to the rooting process leftover in your system partition those files will remain after unrooting. That is what the unroot zip files do usually, is they delete everything and reformat the system partition before installing (instead of just overwrite installing) to avoid leaving orphan files. But these orphan files usually do not impact your system (the entire system has been rewritten anyway) and for sake of argument your TF is unrooted, as you no longer have root access. To avoid leaving anything in your system after unrooting you should factory restore and delete all user apps/data with something like titanium backup before installing the stock firmware over your old rooted ROM. I will think of how to add this to the OP to make it more clear.
Basically though, if you unroot you will want to manually remove any files that are in your system partition (root directory) that were not there when you first rooted your TF or flashing the stock ROM will simply leave those and overwrite the other folders/files.

Just to throw something in here about that. Vipermod does have an unroot setting in it's commands.
Or using terminal emulator or adb
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
reboot

[HOWTO] Rooting + Wiping + Flashing : For the ultimate noob.

Note from rootsu:
XDA staff have transferred ownership of this thread to me so that I can update the rooting methods. The reason for this is because the rooting method contained within is outdated and since identified as unsafe.
I have PM'd the original OP @Stormlister to update the thread but unfortunately have received no response.
I aim to keep the structure of the thread in tact. I am only here to edit out / replace outdated and unsafe methods contained within this thread. The work below is not my own.
Disclaimer:
This guide is for total noobs (I am one myself). Until the information here can be confirmed by an experienced person please don't bet on the fact that this information is 100% accurate. I studied and put together bits and pieces of information that I found everywhere, tried it and it worked. I will mention the sources. Even though its probably not a good idea for a noob to write any sort of guide, these were taken from working sources, I have tried it myself and all works flawlessly.
About me:
I write open source software and also write documentation.
Why:
I wrote this tutorial as I found the scattered information all over kinda confusing on the subject of flashing, wiping and ROMS.
Who's it for?
You already know what you want to do, but don't know where to start.
THIS IS A WORK IN PROGRESS.
--------------------------------------------------------------------------------------------
Getting Started - Rooting
--------------------------------------------------------------------------------------------
Root means you are opening the operating system to allow a user or application full read and write access. This is needed by some special applications to change operating system files. For example the "Adfree" application changes system files to block certain domains which completely stops ads from showing up on your phone. Unlike other systems like in the iOS, all the root applications are available in the Google Play store, I think Google is great for allowing this.
The main thing I root first even though it is not needed to flash a rom is the fact that you ALWAYS need to make a backup, if something goes wrong you have a something to fall back on and the friendly xda community can help us get things running again.
The easiest way I found to quickly and safely root was by using the following software:
ODIN (Desktop software) (Incorrect usage may make your phone unusable.)
Before you start using Odin, make sure all the Kies* services on your desktop is stopped. (On Windows, you can press Ctrl+Alt+Delete, go to task manager, services and stop it from there). Infact you should consider uninstalling Kies altogether as it is really not needed if you are going to root. There are more than enough backup software that does not add the bloatware.
This piece of genius is a tool to flash among other things a new ROM to your phone.
We will be using this piece of software twice, first to root it, and then to flash your S3 with a new ROM.
------------------------------------------------------------------------------
<rootsu insert>
Recommended methods to "root" depending on your requirements...
1) You want root only. No custom ROMs, kernels etc. Just root, just to use root apps.
CF Auto Root Via Odin
Why? Tried and tested method, simple to use. No need to choose what exploit you want to use as it's tailored for your device.
What does it do? It gives you a stock recovery (so can't flash things) and roots the Android OS
The Steps:
1) Download the Latest Odin
2) Download CF-Auto-Root for your model
3) Follow These steps to root
2) You want to flash custom ROMs / Kernels
If you want root on your existing Android ROM, you can do 1) first. Then flash a recovery of your choice (CWM, Philz, TWRP) via Odin
However, if you immediately plan on flashing a ROM, there's no need to root your existing ROM. Simply skip straight to installing a recovery. Backup then flash what you like.
The Steps:
1) Download the Latest Odin
2) Download recovery of your choice CWM, Philz, TWRP
3) Follow The steps to Flash Philz recovery (But for the recovery of your choice)
These steps can also be followed to update recovery to newer versions
</rootsu insert>
------------------------------------------------------------------------------
Difficulty: Easy
After you have completed the tutorial your phone should be rooted and ready to go to the next step.
--------------------------------------------------------------------------------------------
Backing up
--------------------------------------------------------------------------------------------
The next thing we will need to do is backup our current apps, settings and even ROM. Now that the phone is rooted we can install a few applications to help with this process. Lets do this now.
In Google Play Store, search and install:
Titanium Backup (Google Play)
With this tool, you will be able to backup application and settings of your current installation.
To do so;
Open Titanium Backup
At some point it will ask for root access, you will need to allow it root access.
Click on Backup/Restore.
It will show you a list of software.
Click the ok tick top right.
It will now show a list of actions you can take.
You will now [ RUN ] Backup all user apps+ system data.
It will flip to a new screen, click top right ok tick again.
The backup process will take a few minutes.
After the backup completes, we will need to copy it to a safe place, just in case something else goes wrong.
With above explained, there are more optimized Titanium Backup methods, this is a must read:
http://checkrom.com/threads/titanium-backup-explained.433/
You could also backup your whole system from the boot menu of ClockWorkMod / custom recovery - which you will already have if you used the rooting method above. Have a look at this short yet very informative video to do just that:
http://www.youtube.com/watch?v=sPvNr7LqP30&feature=related
Difficulty: Easy
Bear in mind that custom recoveries vary, they all work pretty much the same. The backup is referred to as a "nandroid" backup, but in the recovery menus, it may well be referred to as simply "backup and restore".
To boot into whichever custom recovery you have installed, power off the phone. From off, hold Volume Up + Home then press and hold Power until the S3 splash screen shows. Release power. Once in recovery, find the backup and restore menu and take a backup.
There is one more place you need to manually write down some settings, the APN for your data and MMS, this is the only area besides the branding when another countries stock rom might affect you if you chose to use it. So head over to;
Settings->More Settings->Mobile Networks->Access Point Names.
Click on each and write down its settings.
Backing up EFS folder
---------------------------------------------------------------------------------------------------------------------
The EFS is a filesystem folder which contains important information like for instance your IMEI (International Mobile Equipment Identity) number, even though I cant find any evidence that anyone lost their EFS folder yet, I think it is probably important enough to back it up. First open your favorite file browser like ASTRO and click on your internal build in sdcard0 and see if you have a efs_Backup folder. If you have such a folder its is probably backup up inside already. To be honest, I dont know what backed mine up, but it was there, and it will be likely there if you followed the procedures listed in the collection of this tutorial.
However, the folder is only 6mb, if you don't have such a backed up folder, using an application like KTOOL, gives you the ability to backup the whole "/efs" folder to wherever you like. The external SSD and also your PC would be a good idea to back it up to.
----------------------------------------------------------------------------------------------------------------------
Difficulty: Easy
--------------------------------------------------------------------------------------------
ROM - Hunting for a new rom
--------------------------------------------------------------------------------------------
************************************************************************************************************
My ROM is not YOUR ROM
But I have an S3, wtf is this? Note that when hunting for a ROM that you make sure it is either based on your models ROM or supports your models ROM. The reason this should be noted is because the models are so profoundly different, from Dual Core to Quad Core, from 1GB memory to 2GB memory etc. This means each ROM is optimized of based on a specific model. If you have the GT-I9300, you have the most popular model which has a lot of custom ROMS.
Read more about the differences here:
http://forum.xda-developers.com/showthread.php?t=1870827
************************************************************************************************************
This is where I got confused, I did not know if I had to match the code base of my factory stock rom to the rom I wanted. I was afraid that it might flash my modems software making my phone unusable with my service provider. It seems that the rom file is only to flash the actual OS and wont include the modem flash too.
So what ROM to pick, there seems to be very good ROMS out there, but know, the further you go away from the stock rom, the more difficult things become. You might just want to upgrade to the latest Jelly Bean and not worry about an improve stock Samsung rom. Or you might want to take it to a whole new level and perhaps install a pure Android rom (however, I noted a few people having trouble with the pure android rom, you really need to know what you are doing). But as I say, it seems things gets kinda tricky the further you move away from the Stock Rom.
Lets look at a few examples of solid roms:
At this stage we only have one stock rom available in Jelly Bean, this is most probably the safest bet when you only want to upgrade to Jelly Bean (If you do decide to just go with the safest rom, you can just root again after the rom was successfully flashed) [INTERNATIONAL GALAXY S3 ONLY] [DONT USE THIS ROM ON ANYTHING ELSE THAN INTERNATIONAL VERSION (IT WONT WORK)]:
http://forum.xda-developers.com/showthread.php?t=1646610
Now we can start looking at roms based on stock roms that was improved by a linux guru, very good example of such a rom which is very solid is Android Revolution HD, if you have other Samsung devices I would recommend sticking to this one as it comes stock with Allshare Play:
http://forum.xda-developers.com/showthread.php?t=1797334
The most popular OMEGA rom for the S3 international, pure awesomeness:
http://forum.xda-developers.com/showthread.php?t=1663656
Then you get completely customized roms like Cyanogenmod, this is next level roms and should probably only be tried once you are more confident with flashing ( . Y . )
Note that Cyanogenmod is very controversial for the international version of the S3, there are technical issues, and newer stable version is always behind, I would NOT go for Cyanogenmod at the moment..
http://www.cyanogenmod.com/
For a very nice list of roms and some explanations have a look at:
http://forum.xda-developers.com/showthread.php?t=1674286
Now that you have your rom, lets continue.
Difficulty: Easy
--------------------------------------------------------------------------------------------
Wiping & Flashing - Cleaner Flashing Method
--------------------------------------------------------------------------------------------
[I will try and confirm all my findings below]
When people refer to the term wipe, it is my understanding that it means to delete the old ROM from various locations. This ensures a more clean installation, almost like its better to install Windows afresh instead of an upgrade. However, this is not Windows, its Linux, I am sure the logic behind this is because the way Linux works, it has certain files in certain directories, that if the file is there, the service is loaded automatically. Now if you had to replace a stock rom with something completely different, some of those auto loaded files will be left behind and you will be stuck with loaded services that should not be there. But this is just my experience, I am not sure if this completely accurate.
This is where things might start becoming slightly confusing. Many people seem to argue that when upgrading from a stock version to another stock version that you don't need to wipe, I completely agree with this, as this will almost be the same upgrade process the default upgrade will follow.
However, if you upgrade to a very different ROM, start paying attention, as things might just get slightly more complicated. This I have not tried myself yet, but it seems that for this to work you wont need Odin.
Some people also recommend formatting and not just deleting, I will even advice against this, this is the EXT4 filesystem, not some NTFS filesystem. I cannot see the real benefit of formatting.
At this stage I don't know how to wipe the phone if you are going to use the alternative Odin flashing method explained below, this I have done, tried and tested, working fine:
[Below method I use to flash my own international S3]
This is what you will be doing to install a custom rom while wiping it for a fresh install (make sure you have your titanium backups handy ):
Copy your ROM inside an easy locatable phone folder by browsing to it, from your PC and copying it to your phones folder using your micro USB cable. I strongly recommend using your External SD card as some roms may wipe your internal SD card leaving you without any ROM to update.. that will be very sad. :crying:
Boot into recovery (Vol up + Home + power from off)
You will see a new Unix like screen appear, use volume + and - to navigate up and down, home button is enter, and soft touch back button back is back.
Next we will wipe the phone (if your ROM does not have special instructions on wiping this is a standard method).
Goto Wipe Data/Factory Reset -> Yes
Goto Wipe Cache Partition -> Yes
Goto Advance -> Wipe Dalvik Cache -> Yes
Next Select Install Zip from SD Card (You may also mount External SD card and load ROMS from external SD card (I can recommend this))
It will take a while...
Reboot, and hope to god all is good.
I can confirm above works perfectly, I have flashed HD Revolution ROM successfully using above method.
BUT PLEASE BE WARNED: HD Revolution recommends using Super Wipe, the instructions are unclear, it says you must copy it to the your sd card, if you do this and copy it to your internal sd card all will be wiped including your images, I think you are screwed then. Rather copy them to your EXTERNAL SD card and choose zip from EXTERNAL SD card.
Or you can see a very clear example video of how to wipe data from your phone in preparation of a new rom;
Be aware, this video shows that you should UNLOCK your bootloader, some phones wont boot after this, don't do it except if you know you have to.
http://www.youtube.com/watch?v=EJUCOtX1cUk
Difficulty: Medium
--------------------------------------------------------------------------------------------
ALTERNATIVE Flashing - With Odin
--------------------------------------------------------------------------------------------
If you have not followed the wiping method and you will just be going for the stock updated rom, you should not be needing any wiping, you can just download the stock rom as linked and follow this great guide:
STOCK ROM:
http://forum.xda-developers.com/showthread.php?t=1646610
ODIN GUIDE
http://forum.xda-developers.com/showthread.php?t=1671969
Difficulty: Medium
--------------------------------------------------------------------------------------------
Restoring your data
--------------------------------------------------------------------------------------------
After you have are done with a successful flash, we want to recover our apps, but its not just a matter of recovering everything, it will be a mess if you do that.
Many people carry out a backup before installing a custom rom and didnt really understand what kind of backup they should of carried out and have just gone with what they have seen, WRONG!!! when it comes to custom roms there is only one type of backup you can do.
Custom roms have their own system files and dont like other system files being installed over it, you will definitely have rom problems if you carry out this kind of restore from a backup over a custom rom.
When using Titanium Backup its important not to use the settings - backup all system data and backup all user apps + system data, you cant use these with a custom rom, so dont try this kind of backup, this kind of backup is to restore your phone back to its previous state, should something go wrong with the rom installation.
Click to expand...
Click to collapse
Read more detail here:
http://checkrom.com/threads/titanium-backup-explained.433/
Difficulty: Easy
--------------------------------------------------------------------------------------------
Getting rid of bloatware
--------------------------------------------------------------------------------------------
If you went for a stock based ROM, you might want to get rid of all the SAMSUNG bloatware that sits in memory and really never gets used.
This is mostly all the "S" software like "S Suggest", I believe not a lot of people is going to use this for instance. And one can't simply uninstall it as it is hiden from uninstalling.
There is a very easy way if you are rooted though (another reason to root). Simply install the little greatness called "Nobloat Free" from the Play store.
Now select those bloatware you dont want and simply uninstall. But make sure it might not be useful for yourself. To give you an idea, "AllShare Play" might sound useless, however, if you have a XBMC media pc, by simply enabling "PNP" in the configuration, you can display photos and videos instantly from your G3, does not matter where you are in XBMC.
Difficulty: Very Easy
--------------------------------------------------------------------------------------------
Unrooting and getting back your Warranty!
--------------------------------------------------------------------------------------------
At some stage you might want to sell your phone or it is giving you hardware issues that has nothing to do with software. At this stage you want to reset the phone to it 100% factory state and status. It is completely possible, unfortunately it wont work to just update the rom to the stock factory rom as there are built in counters and status writes who flags the phone as modified. However, by following these tutorials, you can quickly reset your phone.
You will need the factory rom for your country, this can be downloaded here:
http://www.sammobile.com/firmware/
Then watch both of these tutorials and decide which one you feel the most comfortable with:
http://www.youtube.com/watch?v=ZEI_c1R0_nQ&feature=related
And another approach to regaining your warranty:
http://www.youtube.com/watch?v=TEsBwtqY2xE&feature=related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Oops, if you are stuck on a crossroad and you think you might have bricked (term used to define the fact that you made your phone unusable) your phone, following this tutorial will help you out:
http://www.youtube.com/watch?v=ypmqJbZqOaU&feature=related
Difficulty: Easy
--------------------------------------------------------------------------------------------
Thanks to everyone
--------------------------------------------------------------------------------------------
I just want to say thanks to the wonderfully smart people who makes rooting possible. It is amazing how much more fun some people can make the life for other. I truly appreciate every bit of it.
Also special thanks to xdadevelopers who keeps an awesome community together.
Odin Greatness!
CF-Root
SuperSu
CWM
CWMManager
ClockworkMod (WTF, this is omg awesome!)
Titanium Backup
Adfree
--------------------------------------------------------------------------------------------
Congrats on your new firmare!
--------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------
FAQ
--------------------------------------------------------------------------------------------
JiiNDER said:
Hey I want to thank you so much for your guide! It actually makes rooting a lot easier. I had one question though, if I root and a new official firmware comes out, can I still update to the latest stock rom with Kies even though I will lose my root.
Click to expand...
Click to collapse
It all depends what ROM you loaded, if its not the default factory ROM or based on it, you will have to follow the instructions of the CUSTOM rom provider on how an upgrade should be achieve. Else simply use the newest default rom and simply re-root, should be a very quick to do. Also, dont use KIES if you have already rooted, rather use ODIN and follow the instructions. NOTE: KIES, if left running will make ODIN behave incorrectly.

just a slight correction/heads up.... if you root with cf root then cwm recovery is installed, hence no need to use Rom manager, it's kinda outdated now imho
---------- Post added at 05:51 PM ---------- Previous post was at 05:49 PM ----------
further to that you may want to provide instructions after the rooting process on how to get into recovery and download mode

slaphead20 said:
just a slight correction/heads up.... if you root with cf root then cwm recovery is installed, hence no need to use Rom manager, it's kinda outdated now imho
---------- Post added at 05:51 PM ---------- Previous post was at 05:49 PM ----------
further to that you may want to provide instructions after the rooting process on how to get into recovery and download mode
Click to expand...
Click to collapse
Thanks, I will note that above.

The stock rom at the bottom goes to the international version rom. I found this thread in the Sprint version so u might want to note that. If someone were to flash that they wouldn't boot up.
Sent from Galaxy SIII

Added many corrections.

musclehead84 said:
The stock rom at the bottom goes to the international version rom. I found this thread in the Sprint version so u might want to note that. If someone were to flash that they wouldn't boot up.
Sent from Galaxy SIII
Click to expand...
Click to collapse
Could you please explain why you think it wont boot, what exactly would be different that wont make it boot. I believe it will?

Great tutorial for the noobs. Would be really useful for them. :thumbup:
Sent from my GT-I9300 using xda app-developers app

Stormlister said:
Could you please explain why you think it wont boot, what exactly would be different that wont make it boot. I believe it will?
Click to expand...
Click to collapse
Different CPU's, different kernels, different drivers, different partitions, different radios and tech (one being GSM the other being CDMA) and the list goes on...

graffixnyc said:
Different CPU's, different kernels, different drivers, different partitions, different radios and tech (one being GSM the other being CDMA) and the list goes on...
Click to expand...
Click to collapse
Thanks for the feedback man... will mark it as International Only.

I had question regarding Odin behaving strangely, make sure KIES is stopped in your services. I have added it in the tutorial.

Stormlister said:
I had question regarding Odin behaving strangely, make sure Kiss is stopped in your services. I have added it in the tutorial.
Click to expand...
Click to collapse
Do you mean Kies ? (Samsung) good tut for super noobs btw
Sent from my GT-I9300 using xda app-developers app

i would recommend you to recommend not installing Kies at all, or uninstall it if installed.
any backup that you can do with it, can be done by 3rd party apps. it has a lot of security issues. and worst, its slow as hell.
i think a person that want to root his phone and flash a custom rom, will have no need of it anyway.
Edit: thumbs up for the effort! i could have really used such guide when i just started, instead i learned it the hard way!

OverRipeBananas said:
Do you mean Kies ? (Samsung) good tut for super noobs btw
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Yes, yes Kies, thanks for spotting it

Thanks, I'll try this soon! Glad I found this, voiding warranty still sounds scary. I have other rooted devices and sometimes they can blow me away, so I think I'll go for it anyway.
Cheers.

MrEdgar said:
Thanks, I'll try this soon! Glad I found this, voiding warranty still sounds scary. I have other rooted devices and sometimes they can blow me away, so I think I'll go for it anyway.
Cheers.
Click to expand...
Click to collapse
I personally think it is well worth-it, it is almost as if the phones turns into mini super computer when rooted. It is so much fun to have a ROM installed and setup that you are completely happy with, removing bloatware, no intrusive ads. Just stay away from overclocking, I think that is taking it too far if you are a scary pants like myself.
Also, you know how the retailers are, they almost never deliver on their warranty anyway.

No offence, but given this guide is designed 'for the ultimate noob' AND it has been stickied, there are some glaringly obvious things missing, that should be cover at the beginning of your post/guide before hitting the processes of
In the first post, you do not cover information pertaining to the flash counter and triangle away, and most importantly by far, BACKING UP THE EFS. Also, possible risks from installing potentially malicious apks from 'other sources' to a rooted device.
Sent from my GT-I9300 using xda app-developers app

Good job! :good:

bootx1 said:
No offence, but given this guide is designed 'for the ultimate noob' AND it has been stickied, there are some glaringly obvious things missing, that should be cover at the beginning of your post/guide before hitting the processes of
In the first post, you do not cover information pertaining to the flash counter and triangle away, and most importantly by far, BACKING UP THE EFS. Also, possible risks from installing potentially malicious apks from 'other sources' to a rooted device.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
None taken, but in a community it works like this. We build a tutorial together. Instead of taking the time pointing out what you think is missing. Why did you not just write the part so I could add it? This tutorial is based on the international version, I am not sure if the triangle notification does not affect this version but I could not test it as I did not ran into this problem.
Regarding the EFS, I will do some research regarding this and add it to the tutorial.

I have added detail on backing up EFS folder and also triangle away.

CF-Root 6.4 - SuperSU+CWM5.5+CWMManager does not work on stock JellyBean Firmware right?

[HOWTO]Downgrade From COD6 to NK4 or Upgrade from NK4 to COD6

I just successfully downgraded from COD6 back to NK4 in order to alleviate concerns that downgrading back to Kit-Kat was going to be an issue. Reference post found: HERE. I am outlining the method I used to downgrade below, but this can also be a guide on how to upgrade to later firmwares.
I don't recommend trying to downgrade past NK4 and only downgrade if your dev says you need to! downgrading is risky and can brick your device! You've been warned!
Downgrade to NK4 or Upgrade to COD6
1.) Download Odin v3.09
2.) Download full Odin NK4 (Found HERE) or COD6 found, almost everywhere
3.) Unzip the file and there should be a file called "N910TUVU1ANK4_N910TTMB1ANK4_N910TUVU1ANK4_HOME.tar.md5" or your COD6 tar called, "N910TUVU1COD6_N910TTMB1COD6_N910TUVU1COD6_HOME.tar.md5"
4.) Open Odin v3.09 and click the button labeled "AP" and locate the tar file you unzipped
5.) Let it load, it will freeze for some time while checking the MD5 and then be ready to go
6.) Turn off your phone completely; after it is powered off hold vol down+ home + power until you see a warning message
7.) Hit Volume up to continue
8.) Plug in your device and and the it should light up blue under "ID:COM" and say something like "COM:1"
9.) Check to make sure your tar is loaded into the AP slot.
10.) Ensure that they only two boxes that are checked are: "Auto Reboot" and "F. Reset Time"
SHOULD LOOK LIKE THIS PHOTO: http://cdn.droidviews.com/wp-content/uploads/2013/05/galaxy-s4-odin-flash.jpg
11.) If you've verified that your Odin looks like the picture then click "Start" and be patient
*****************************************************************************************************************************
***If Downgrading You MUST wipe USER DATA following the steps below or your phone will boot loop on restart!***
***If Upgrading I Strongly Suggest wiping USER DATA to avoid potential issues from upgrading!***
*****************************************************************************************************************************
12.) Wipe User Data as outlined below by booting into recovery as soon as the download completes by holding power + volume up + home until it says, "Recovery booting" in blue in the upper left corner.
13.) After doing the factory reset and rebooting it will you can setup your phone like normal
These are the same steps if you want to upgrade with Odin, you just use the full tar of the upgraded firmware (COD6 in our case)
To Wipe User Data
1.) After you've clicked start and the file completely loads on your phone it will reboot and immediately enter recovery
2.) It will show and Android and a blue bar scrolling across setting up your system. It will reboot again after this
3.) As soon as the screen turns black hold vol up+ home + power to enter recovery again
4.) It will boot to the Android again and you should see THIS before the menu loads
5.) Scroll down to "factory reset/data wipe" with the Vol Down button and then hit the power button to select it
6.) Scroll down again and hit "Yes" so that it completes
7.) After it is done reboot and allow your phone to boot normally
8.) Setup your phone like normal
Done!

I vote for this to be a "Sticky".
Good job :good:

Thank you, I've been with 5.0.1 for the day and the battery was better on 4.4 and it looked better. I was going to try as soon as I got home but now I know.

I was googling how to downgrade and ran in to this. A lot of report saying it worked. I'm surprised this is possible with Odin. Thanks for the additional confirmation.

Just wanted to add. Downgrading to NK4 will require a factory reset, otherwise you go into a boot loop.

aznmode said:
Just wanted to add. Downgrading to NK4 will require a factory reset, otherwise you go into a boot loop.
Click to expand...
Click to collapse
I know it was a long time ago when you posted this, but it just now sank in that boot loop = bad
I will update the OP, thanks for pointing this out :good:

Makes no sense. It says must wipe user data....why on earth would you need to wipe / factory reset just to UPGRADE to COD6?
Guide needs proper writing...

CtJackHarkness said:
Makes no sense. It says must wipe user data....why on earth would you need to wipe / factory reset just to UPGRADE to COD6?
Guide needs proper writing...
Click to expand...
Click to collapse
Because doing an Odin upgrade or downgrade on your device does not wipe the data partition which is necessary when changing a letter versions of Android. For example, let's say you are going from Kit-Kat to Lollipop or perhaps Lollipop to Kit-Kat in a way similar to that presented in this "How to".
However, I get that new members need help sometimes so let me help you research your criticism.
Welcome to XDA.

Forgive my ignorance, but I am curious. When upgrading to a new letter version via OTA or a program like Kies, there is no factory reset done by default. The fact that a factory reset solved problems for many this go around aside, why is it a must when using Odin? I have upgraded ma few devices over the years to new letter versions without resetting so I am just trying to get a better understanding.

KingBeef said:
Forgive my ignorance, but I am curious. When upgrading to a new letter version via OTA or a program like Kies, there is no factory reset done by default. The fact that a factory reset solved problems for many this go around aside, why is it a must when using Odin? I have upgraded ma few devices over the years to new letter versions without resetting so I am just trying to get a better understanding.
Click to expand...
Click to collapse
The reason OTA and Kies don't do the reset themselves is because they aren't capable of backing up the data you've accumulated on your phone since you've owned it. The average user only get an icon in the upper left-hand corner that tells them to update and they do it because T-Mobile says so. Imagine that same user installed the update and then they were looking at the Lollipop welcome screen like they had just taken the device out of the box. It would lead to an outcry from consumers because they lost months of data from the upgrade. However, we here on XDA are not average users and some of us know exactly what happens during these updates. You probably don't remember this, but there was a time when Odin wiped your phone automatically even on incremental updates. Because just like flashing a ROM, clean is the only way to truly ensure that residual files are not causing problems. But they eventually removed this behavior in later releases of Android. I don't know why this was done, I am only able to tell you the history of Odin as I know it. However, because Android changes have been so drastic lately (locked SD cards, addition of preload partition, removal of preload partition, SELinux policy updates, institution of Knox and protected files, etc etc etc.) not starting with a clean slate led to a myriad of problems for users. If you need specific examples just look at the Galaxy S5 Wi-Fi issues from taking the Lollipop OTA without doing a factory reset. If you format your hard drive before installing a new version of Windows then you should be capable of understanding why clean partitions for an OS upgrade makes sense. But you don't have to take my word for it, click the link I left with CtSomethingOrAnother up there. People almost unanimously support a factory reset for major upgrades. So you can take my advice or follow your own, but I promise that I'm going to get plenty of sleep tonight regardless of what you decide to do with your phone. You have to realize that I am giving advice as a senior member of a respected development community where new members come for answers. I make sure that I am giving them the best advice that I could possibly give them with my experience on these forums and with Samsung devices. If users decide to cut corners after knowing the proper way to do it, that is on them.
tl;dr -- I wrote this Howto so that I could help people; not waste their time. You don't have to believe anything I wrote above. In fact I encourage you to research this information yourself and come to your own conclusions about why factory resets are necessary. Until Google goes on record saying, "No more factory resets for upgrades" I'm going to keep my advice just the way it is written.

I appreciate you taking the time to explain this. I have been flashing and what not for a few years, but I am by no means completely aware of why I do things a certain way in all cases. It is nice to know the "why" behind things sometimes.

I think resetting the phone and having everything wiped should only be done if experiencing problems. Everywhere online this is the case. It is NOT required to wipe a phone. And again if you wipe / factory reset a CDMA phone - don't they have you call in to reactivate it? (little offtopic but just curious regarding verizon)

KingBeef said:
I appreciate you taking the time to explain this. I have been flashing and what not for a few years, but I am by no means completely aware of why I do things a certain way in all cases. It is nice to know the "why" behind things sometimes.
Click to expand...
Click to collapse
To me, the why is always the most important part. When someone posts a flashable file to fix a problem I open it up to see what it is doing. It took a lot of reading and some prior experience with Linux to be able to grasp a lot of what Android developers are doing when they change the files
CtJackHarkness said:
I think resetting the phone and having everything wiped should only be done if experiencing problems. Everywhere online this is the case. It is NOT required to wipe a phone. And again if you wipe / factory reset a CDMA phone - don't they have you call in to reactivate it? (little offtopic but just curious regarding verizon)
Click to expand...
Click to collapse
I truly don't understand how you could acknowledge that skipping the factory resetting could lead to problems for people but that you don't recommend it because people should just use it until they have a problem and then wipe all their data at that point. And as far as "everywhere online this is the case", I literally Googled for you tons of links with people saying to factory reset for Android upgrades and you're choosing to ignore the information. That's on you. As far as CDMA phones having to be re-activated? It's been years since I used a device on Sprint and doing a factory reset on Android led to the device activating itself. It isn't an issue, it's just part of the setup process. It's no different than updating the PRL and Profile on Sprint (CDMA) once a month to ensure roaming capabilities are working at peak efficiency. Verizon customers used to have to dial a number to update the PRL but now on Android it happens in the background just like it would during setup.
However, changing your mind isn't my job nor is it how I intend to spend my time on here. You can do whatever you wish with your phone and what I wrote is exactly how I handle my phone. I'm leaving your criticism and my responses in this thread for people who want to hear both sides and hopefully that will accomplish what you set out to do by posting here in the first place. If you still aren't satisfied, please take it to PM.
EDIT: Nevermind, I went back and edited the post to clarify that boot loop happens on downgrading and encouraged people to wipe user data while upgrading.

This method worked for me..
This was my solution to completely downgrade the N910T back to KitKat after a full Lollipop stock upgrade or rom.
Please do a nan droid back up before attempting this first?
*** I am not responsible nor accountable if you damage your android device when done incorrectly or attempting this***
Please understand doing this will and is going to trigger the knox count if attempted.
When I did this it worked for me to test Lollipop or roms and back to KitKat stock for example:
DARTHSTALKER_NOTE4_V2
InfamousROM_Note4_COD6_v1.8.1.
Just to name some good KitKat and Lollipop ROMs for the N910T that I use.
Four things your gonna need before you start:
1. The actual KitKat N910TUVU1ANK4 Firmware.
2. Odin3 v3.07
3. N910TUVU1ANK4_N910TTMB1ANK4_TMB-files-modem.bin-boot.img-recovery.img (This contains 4 files: boot.img, modem.bin, NON-HLOS.bin, recovery.img).
4. WinRar or 7zip software.
What I found is that the baseband changes and does not allow to downgrade from stock N910TUVU1COD6 Lollipop back to stock N910TUVU1ANK4 KitKat with Odin it just wouldn't allow it. I've done this so I know this works since I wasn't ready for Lollipop bugs and battery consumption. From what I heard this couldn't be done.. Anyway after your nan droid backup Wipe every thing in your recovery TWRP: Advance wipe, Wipe the dalvik cach, System, Data, Internal storage, cache reboot back download mode. Now take the TMB-files-modem.bin-boot.img-recovery.img extract it with winrar or 7zip. Now go back into Odin Click Phone and search for the files you just extracted. They are 2 files needed and that's the NON-HLOS and the modem file. This needs to be installed one at a time on the Phone tab using Odin. Flash the NON-HLOS and reboot back into download mode. Now flash the modem file in the Phone tab using Odin and boot back into download mode. Now flash N910TUVU1ANK4 KitKat Firmware using Odin and let it finish and reboot completely. Check and make sure that Odin completes the flash and reboot completely to Tmobile setup screen. Done..
If the firmware feels weird at first just do a factory reset and cache in the stock recovery. Hope this helps out the XDA community. Don't forget to thanks please?
Here: N910TUVU1ANK4_N910TTMB1ANK4_TMB-files-modem.bin-boot.img-recovery.img
h t t p://w w w 10. zippyshareDOTcom /v/5feSbGgX/file .html

hacker904 said:
This was my solution to completely downgrade the N910T back to KitKat after a full Lollipop stock upgrade or rom.
Please do a nan droid back up before attempting this first?
*** I am not responsible nor accountable if you damage your android device when done incorrectly or attempting this***
Please understand doing this will and is going to trigger the knox count if attempted.
When I did this it worked for me to test Lollipop or roms and back to KitKat stock for example:
DARTHSTALKER_NOTE4_V2
InfamousROM_Note4_COD6_v1.8.1.
Just to name some good KitKat and Lollipop ROMs for the N910T that I use.
Four things your gonna need before you start:
1. The actual KitKat N910TUVU1ANK4 Firmware.
2. Odin3 v3.07
3. N910TUVU1ANK4_N910TTMB1ANK4_TMB-files-modem.bin-boot.img-recovery.img (This contains 4 files: boot.img, modem.bin, NON-HLOS.bin, recovery.img).
4. WinRar or 7zip software.
What I found is that the baseband changes and does not allow to downgrade from stock N910TUVU1COD6 Lollipop back to stock N910TUVU1ANK4 KitKat with Odin it just wouldn't allow it. I've done this so I know this works since I wasn't ready for Lollipop bugs and battery consumption. From what I heard this couldn't be done.. Anyway after your nan droid backup Wipe every thing in your recovery TWRP: Advance wipe, Wipe the dalvik cach, System, Data, Internal storage, cache reboot back download mode. Now take the TMB-files-modem.bin-boot.img-recovery.img extract it with winrar or 7zip. Now go back into Odin Click Phone and search for the files you just extracted. They are 2 files needed and that's the NON-HLOS and the modem file. This needs to be installed one at a time on the Phone tab using Odin. Flash the NON-HLOS and reboot back into download mode. Now flash the modem file in the Phone tab using Odin and boot back into download mode. Now flash N910TUVU1ANK4 KitKat Firmware using Odin and let it finish and reboot completely. Check and make sure that Odin completes the flash and reboot completely to Tmobile setup screen. Done..
If the firmware feels weird at first just do a factory reset and cache in the stock recovery. Hope this helps out the XDA community. Don't forget to thanks please?
Here: N910TUVU1ANK4_N910TTMB1ANK4_TMB-files-modem.bin-boot.img-recovery.img
h t t p://w w w 10. zippyshareDOTcom /v/5feSbGgX/file .html
Click to expand...
Click to collapse
I'm going to wait on some testers for this one lol but if confirmed...I'm on it! Lol although I'm a little confused why I would nan and then immediately wipe internal data? I don't have a SD card yet though (just got phone today) so any nan I make goes right to internal :/

Internal data
v2.2v said:
I'm going to wait on some testers for this one lol but if confirmed...I'm on it! Lol although I'm a little confused why I would nan and then immediately wipe internal data? I don't have a SD card yet though (just got phone today) so any nan I make goes right to internal :/
Click to expand...
Click to collapse
I wouldn't recommend doing any type of internal data wipe unless you have a SD card. Now take note of this when using custom (TWRP) recovery that you have to manually go into storage during the back up. Now go to the drive/storage and change the option in oder to back up on the Ext.SD card. I would be careful in the recovery when advance wiping the phone to reinstall another rom. It has the option to wipe the Ext.Sdcard...Do not do that take it from me I've done it rushing and it sucks. TWRP backs the nandroid on the Ext. in a TWRP file.
Hope this helps every one out.
Please thank?

hacker904 said:
I wouldn't recommend doing any type of internal data wipe unless you have a SD card. Now take note of this when using custom (TWRP) recovery that you have to manually go into storage during the back up. Now go to the drive/storage and change the option in oder to back up on the Ext.SD card. I would be careful in the recovery when advance wiping the phone to reinstall another rom. It has the option to wipe the Ext.Sdcard...Do not do that take it from me I've done it rushing and it sucks. TWRP backs the nandroid on the Ext. in a TWRP file.
Hope this helps every one out.
Please thank?
Click to expand...
Click to collapse
Hey bud. and this by no means is trying discredit you, but the OP works just fine. Just did it. Odin 4.4.4 and wipe data after.

@hacker904 did you do this from 5.0.1 or 5.1.1 because I am on 5.1.1 and have tried to return to Kit Kat and it will not allow me to. Also waiting for testers on this one

Santos89 said:
@hacker904 did you do this from 5.0.1 or 5.1.1 because I am on 5.1.1 and have tried to return to Kit Kat and it will not allow me to. Also waiting for testers on this one
Click to expand...
Click to collapse
I guess tmobile changed some security policy that blocks phone users from downgrading.
Source:
http://forum.xda-developers.com/showpost.php?p=64548030&postcount=5

downgrading from cod6
Has anyone confirmed that you cant downgrade from Cog6? I am on one of the 5.1.1 ROMs I tried downgrading to 4.4.4 using ODIN but it keeps failing. Has anybody had any success with this?

Would someone mind looking over my plan to root my Note 4? I just want to be sure

I have experience rooting a Xoom, an Atrix, and an S3, but at the same time I usually just follow instructions to the bullet point while only vaguely understanding what I'm doing.
I got my cracked screen replaced at a non-samsung outlet yesterday which I'm pretty sure voids my warranty, and if so, I want to take advantage of that by rooting. But a lot has changed since the last time I rooted a phone - they're talking about "systemless root" and flashing an SELinux Permissive Kernel and then "Oh no wait you don't have to flash such a kernel in this new version" and I have no idea what any of that is referring to, all that stuff is new to me.
I have a Canadian Note 4 SM-N910W8 running the latest COK3 OTA update on 5.1.1. I found this rooted ROM which I'm pretty sure is the one I want, but then, it's the only one I found, if there are more or better rooted ROMs please let me know:
http://forum.xda-developers.com/note-4/snapdragon-dev/trltecan-n910w8-aoa1-stock-rooted-t3025538
The instructions for how to install it keep changing for every version though. It also says I need to start by flashing TWRP via ODIN - Okay, I've done that before, but I want to make sure I get the right one. I found a couple of sources:
http://forum.xda-developers.com/note-4/general/ref-stock-firmware-kernel-modem-recovery-t2920452 - twrp-2.8.7.0-trltecan.img.tar
and:
http://galaxynote4root.com/cwmtwrp-recovery/ - openrecovery-twrp-2.8.1.0-trltecan.img.tar
Not sure which one I should use.
All I want is to be able to edit the keyconfig files to get my USB controller working, to be able to edit system files to change the Touchwiz aggressive background app closing and allow apps to remain in memory for much longer to make it more like Windows memory management, and to be able to install Xposed modules like statusbar volume.
But I want to make sure that I'm doing everything *exactly* right, and that's why I like to ask real human beings to confirm my plan before starting. So I download one of those TWRP files, download ODIN, plug my phone into my PC, use ODIN to flash TWRP, boot into TWRP, use TWRP to wipe data, cache, dalvik, and system, and then install the rooted ROM I linked above. Have I got all that right? What's all this SELinux and systemless root stuff I keep hearing about, and why don't I need to do that anymore with the latest version of this rooted rom? Will this break any key features on my Note 4 like my spen or my external USB or my blood oxygen meter or all the cool novelty **** that Samsung Note 4 comes with?

Right here goes the rom u have is the right one for ur phone. There will be others around byt u can try that ome to start with. The twrp recovery u need is the 6th one on the list down the model numner is at the end of the file name, its the .tar file u want zip can be used also but thats using recovery to flash the rom. Using odin 3.09 latest one i think. U need to hold down volume down, home and the power to boot into download mode open idon with kies closed and end task with task manager in window.
Now whem oden starts u need to select the phone tab and choose the twrp recovery and flash that leaving everything unchecked apart from restart and reset time all others should be blank, i flashed with erase nand and nearly bricked my phone, thats one to leave for the experts lol.
Once u flashed recovery i think u need to root even though the rom is rooted rom i think it needs to be rooted before u flash the rom, not sure but its what was on the instructions i followed. If u try find a root file off here for ur phone u do same as u did flashing the recovery file and tjats it wait for phone to restart and reboot fully after flashing each recovery and root, i always do from knowimg its best ti imstall wimdows apps ome at a ti, e and reboot between the installs as less syste, errors can happen that way , well not system errors but linked dll files not been copied right and the like.
Thanks
Steve
Still need help them post back and will do my nest nut i a newb, i have an understandimg of how things work but by no means am i an expert i do what u do, i follow imstructions and learn as i go along what thimgs are and what they do, best way then u kmow what ur messing or dealing with.
U also, well i did for my 910f need to use a specific twrp or at least the latest release.
The walk throughs on most sites are all the right way to do it, just others are explained better than others and imclude other stuff if it goes wrong which believe me it can go wrong, easy as not seeimg a check box tocked or not ticked and boom paper weight lol

Digipro said:
The twrp recovery u need is the 6th one on the list down the model numner is at the end of the file name, its the .tar file u want zip can be used also but thats using recovery to flash the rom.
Click to expand...
Click to collapse
Okay but what about the other site I found, the XDA forum with TWRP recovery files? They seem like newer versions, but then that left me wondering if the reason the other site has older versions is because it's just outdated, or because only the older versions will work.
Thanks for all your help btw!

Your welcom, the rom you want is fine, u want to go for either of the roms version 3.21 de bloated or regula,, de bloated is where they take slot of apps by google and also carrier apps that sometimes come installed.
Steve.

ROOT Galaxy J700t1 (TWRP)(ODIN)

**CREDIT GOES TO messi2050 FOR THE WORKING RECOVERY AND TO paco_1 FOR HIS GUIDE TOO
ASHYX FOR THE DECRYPTION BREAKER AND Walkerblue2030 (??) FOR AT LEAST HAVING A STABLE ENOUGH ROM TO FLASH THAT'S ACTUALLY WORTH YOUR TIME. AND ALSO CREDIT TO fullofhell (??) FOR WHO EVER HE DESIDES TO ENROL FOR THE BETA FOR THE MOST BATTERY EFFICIENT ROM ON THE DEVICE**
--Make sure y'all slap a thanks to these people because without them, unfortunately, any excitement on the J700T devices wouldn't be possible.--
<<DISCLAIMER>>
I NOR ANY OF THE CREDITED PEOPLE ARE RESPONSIBLE FOR ANY DAMAGE DONE TO YOUR DEVICE AFTER FOLLOWING THIS GUIDE. YOU'RE ON XDA SO YOU SHOULD ALREADY KNOW WE LIKE TO SH*T ON OUR WARRANTIES LIKE THERE'S NO TOMORROW. IF YOUR DEVICE BECOMES A BAKED POTATOE OR BLOWS UP YOUR HOUSE FOLLOWING THIS GUIDE OR FLASHING ANY OF THE CREDITED PEOPLE'S WORK, DO KEEP IN MIND THAT YOU HAVE ACCEPTED THIS WARNING AND EVERYTHING AFTER FOLLOWING THIS GUIDE IS BECAUSE OF YOUR ACTIONS.
-------YOU HAVE BEEN WARNED-----
(as scary as I made it sound, I've done this COUNTLESS times and it has worked for me just fine, so nothing to be scared of here if you do this step by step! If you do mess up, try finding the stock firmware and flash back to stock with Odin! Though do take note that Odin has never worked for me unless it was flashing a recovery. I will be making a post on how to flash back to stock soon, so definitely keep an eye out for that!)
Okay so many people are asking how to root the J7 and I wanted to post this small simple guide on how I did it successfully. Without further delay, let's begin.
1- You get yourself them Samsung drivers
2- Get Odin. Duuh.
3- download TWRP (this is messi2050's TWRP, so go give 'em a thanks won't ya?)
4- have a micro SD ready because once you're in TWRP, internal storage won't be mountable.
Okay, so after you've got those things ready, start by enabling OEM unlock. And then USB debugging.
Then you want to move the SU ZIP to your SD card.
(Link for the one I used down below)
Then, power your phone down. Boot into download mode (volume down+home button+power button)
Have that TWRP on your computer, you'll need it on there
Then you'll want to open Odin, select the TWRP.img
(or .tar, I forgot which it is but if .img doesn't show get the .tar from messi2050's post) THROUGH THE AP SLOT
Open the back cover of your device
Plug in your device. When your Odin displays "Added!' you'll know you're ready.
Then click "start" or whatever the button is to begin the flashing process. It should flash and end with a "PASS!" on the top left box and it should be green.
Now, on your device, when you see the Samsung Galaxy J7 logo, IMMIDIATELY unplug the device and remove the battery. I don't know if there is a setting to disable auto reboot, but this is how I personally got it to work.
Then put the battery back in, hold the volume up, power and home buttons untill you boot into TWRP.
Select "install" and then you'll have to select your external storage. Then find the SU zip you should have and then flash it. If it doesn't work you might need to format your internal memory through the WIPE category, then you'll reboot into TWRP again and try again. But make sure you back up before that. And if you do end up formatting, flash SU and the encryption breaker down below.
You should be done! You should be rooted and ready to go! Ahead lies a huge mass of S8/N7 ROMs you should try (they're kinda the same but one in particular has amazing battery life, you'll need to ask " fullofhell" for it, though .-.) a somewhat S5 ROM you can try, just DONT expect any AOSP ROMS to come because from the looks of it they end up broken. And don't try to flash any of the other J7 ROMS (J7 2015-2016, etc.) Because they don't work. Trust me, I've tried.
LINKS
TWRP.IMG: http://www.mediafire.com/file/ehygrybdq7a2j8e/
TWRP. TAR. MD5 (Odin format. To flash this one, you'll need to select it from your PC in the AP slot on odin)
http://www.mediafire.com/file/4f5sz13cz5gy466/
SU ZIP:
https://www.androidfilehost.com/?fid=24591000424939898
DECRYPTION BREAKER:
https://www.androidfilehost.com/?fid=24591000424951049
Use this after you format your data, flash SU or another ROM. Flash it every time you after you flash a ROM so that you can mount internal storage so that you can flash internal zips and images or so that you can create backups and be able to restore. You know, in case you wanna play dirty and all ?)
A ROM TO BEGIN WITH:
https://forum.xda-developers.com/ga...lkerblue-v1-notexperienceromv3-t3575377/page2
(even though the people of this ROM LOVE to bash opinions, this is definitely the ROM to start with. Most stable of all the N7/S8 clones and is kinda battery efficient though id still ask @fullofhell for a beta tryout. Also keep in mind that VIDEO CALLING and WIFI CALLS along with NFC are only a FEW OF THE THINGS YOU WILL BE SACRIFICING TO FLASH ANY ROM ON THIS DEVICE!!!!! DONT ASK ME WHY, ASK ANY OF THE CREATORS OF THE ROM YOU CHOOSE)
I don't use this phone but I can still help out who ever needs it and who ever isn't willing to bash my balls out for my opinions so if you ever need help with things like this, do PM me as I love talking about Android!

I went through the process shown but when finished my phone said "verification failed. unable to restart device" so I would like to know how to fix this.

I don't have oem unlock in developer option

Is this currently(8/13/2019) still working?? Can you point me in direction to list of Compatible Custom Roms or a Stock Debloated Rom and a zip to most current SU archive file?? Would be great since it was took off store. I use to own SU Pro