Database Info

[Guide / Tool][10/15/12] - Update to Official Jellybean Then Root or Custom ROM!

I wrote this guide do to the general lack of information for users about the Jellybean update. This guide is basic in nature and will provide you with all the tools and links you need to update from an ICS based ROM to the official JB ROM then re-root or prepare for custom ROM.
If you already have the Official JB Update simply unlock it and proceed to Section #2. This guide was intially intended for those who cannot update because of Asus stupid lock out program once you unlock.
Warning
I have tested this guide on my device multiple times and never have one single issue. I cannot say it will work perfect for you! I am not responsible for anything that goes wrong including but not limited to; A $500 brick! The economy imploding worse, Nuclear war, End of the world on 12/12/12!
Pre-requisites
Unlocked bootloader
Custom Recovery
Any version of TF700T
Windows 7 or Windows 8 PC
General Overview
Flash Asus JB update
Flash TWRP 2.2.3
Flash SuperSU or Custom ROM
Profit!
Please do not be afraid to ask for help!
This guide was written for people who need help. I didint write it for myself because I already know how to do it, lol
Donations gratefully accepted but never expected!
Please hit Thanks and Rate the thread 5 Stars
Click to expand...
Click to collapse
-Scott

Section 1 - Flash Asus JB update
Obtain the appropriate Jellybean update from the Asus Support Site HERE
Go to Downloads and pick the local / region specific update file for your device. For the intent of this guide I will focus on the US Based variant but all other devices will follow the exact same steps.
{
"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"
}
After you download the Jellybean update you must extract the zip file in the zip (I dont know why they did this!). The name of the first zip file will be "US_epad_user_10_4_4_16_UpdateLauncher.zip"
The zip file inside of that will be "US_epad-user-10.4.4.16.zip" This is the file we will flash to update to JB!
To do this open the first zip file with your zip [rogram of choice, (as you can see I use 7zip) and pull out the only other zip file in there (US_epad-user-10.4.4.16.zip).
Once you have that file copy it to you internal SD card. Although, untested, external SD should work too.
Now.... Reboot to recovery. To do this power down the device, and then Hold Volume Down and then press power untill you get a menu that says press XX key to boot to recvoery.
Once in recovery you MUST wipe data before you continue!
Now flash the ROM file you just copied like it was a plain old fashioned custom ROM or Root.zip. Just select it and flash!
Once the flash is done reboot. Dont be scared... This will take a LONG time... Maybe in upwards of 3 to 5 minutes. This is normal. Its completely rebuilding the device!
Once the device is all booted up and you are at your desktop we can proceed to Section 2.

Section 2 - Flash TWRP 2.2.2.3
First we need to obtain TWRPREcovery. You are free to use any version you want, including ClockworkMod (although I highly discourage CWM and recomend TWRP).
You can find TWRP HERE. Remember I recommend the 2.2.2.3 version. 2.3.0.0 gave me some issues.
Now that you have the file download you need to rename it to "recovery.blob" for use with my tool!
Now download the attached tool and unzip it. It contains the fastboot and ADB files you will need to flash the recovery.
Next place the recovery.blob in the folder
Turn on USB Degging in the developer menu of the device. This is very important otherwise you will be just sitting there forever, lol
Now initiate the "Recovery Install Tool.bat" file. This will reboot you to bootloader and flash the recovery for you ;c)
Done!

Section 3 - Flash SuperSU or Custom ROM
Needless to say I am partial to custom ROMS ;c) But I know some may be content with just flashing root so I will show you how to obtain the correct root file and or ROM and give a brief over view on how to flash them. This section will be pretty routine and will not contain a lot of new info for most of you!
Obtain my favorite root app, SuperSU, from HERE
Copy to storage
Reboot to recovery
Flash and Be rooted!
Same steps for a custom ROM. The best Custom ROM can be found HERE! ;c)

Section 4 - Thanks!
Thanks to Dess_troy for making TWRP for our devices!
Thanks to Chainfire for the root app!
Thanks to all the Developers on XDA that have taught me (in one way or another) everything I know!
Special Thanks to all the CleanROM users who have inspired me to push CleanROM to be the premier custom ROM for your Android Device!

Please feel free to rebuild this for the Linux or Mac platform and re-distrubute!

So, the very first step is unlocking the bootloader, correct?
Sent from my S2 Skyrocket using XDA app

scrosler said:
Pre-requisites
Unlocked bootloader
Custom Recovery
Any version of TF700T
-Scott
Click to expand...
Click to collapse
A number of people have asked and I have usually replied that it is possible to use the Asus provided UnLock tool - the one on the website that says is only compatible with ICS - with a tablet that has been updated to JB.
In short the Unlock tool works in Jellybean!
You might want to add this as an addendum to your original post.
Cheers,
Eric

i apologize for my beligerant question but if i want to try the new cwm touch recovery, do i just rename it to recovery.blob? when i downloaded it it was the usual iso. when renamed it didnt change anything so i dont wanna brick my tab. figured id ask first. thanks for the awesome walk through tho man. i really apreciate it. loving your roms. have 2.0 downloaded already. also can you pm the link to your tf300 kernel you used? i need to show off some high quadrant numbers lol

Confused...
How do I get a custom recovery on my tablet before this whole process? I've read thru some threads, do I need to be rooted first on ICS before starting this process of updating to JB? I'm not getting the official ASUS JB OTA...I've checked for the update about 500 times, I'm just not getting it.
At this point, I have an unlocked but unrooted, and wiped stock TF700T on ICS. Whats my next step?

BlastTyrantKM said:
So, the very first step is unlocking the bootloader, correct?
Sent from my S2 Skyrocket using XDA app
Click to expand...
Click to collapse
BlastTyrantKM said:
How do I get a custom recovery on my tablet before this whole process? I've read thru some threads, do I need to be rooted first on ICS before starting this process of updating to JB? I'm not getting the official ASUS JB OTA...I've checked for the update about 500 times, I'm just not getting it.
At this point, I have an unlocked but unrooted, and wiped stock TF700T on ICS. Whats my next step?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
This guide is for people who have already unlocked there device any may have had a custom ROM installed pre-JB.
You fall into a unique and rather off situation. I have never heard of some one not getting the OTA.
You could follow these steps but as a pre-step...
Download and unlock with the Asus unlock tool. Its on the same download page.
Download an ICS based recovery and use that in in place of the one noted for now. And then just start at Section 2. Then start back over at Section 1.
Basically we will put a recovery on your device in Section 2. Then start over at step 1 by applying the JB build then put a recovery back on, as it gets wiped off by Asus builds and your all set.

So I got the OTA JB update from Asus. I unlocked the boot loader using the Asus app. I downloaded and extracted US_epad-user-10.4.4.16.zip then threw it on the insternal SD card ( /storage/sdcard0 ). I rebooted with the volume key press and selected recovery. It gave me a message saying "booting recovery kernel". The next thing I see is an android on his back with a red exclamation sign.
What am I doing wrong?

beowolfschaefer said:
So I got the OTA JB update from Asus. I unlocked the boot loader using the Asus app. I downloaded and extracted US_epad-user-10.4.4.16.zip then threw it on the insternal SD card ( /storage/sdcard0 ). I rebooted with the volume key press and selected recovery. It gave me a message saying "booting recovery kernel". The next thing I see is an android on his back with a red exclamation sign.
What am I doing wrong?
Click to expand...
Click to collapse
The stock recovery will only flash firmware zips with a certain name. Rename the zip to EP201_768_SDUPDATE.ZIP and try again.

I upgraded to jb firmware and lost root. My 700T is unlocked. I thought I followed the procedure correctly but I did not get the message correct message when I ran the program. My device is not rooted. Can you tell me what I might be doing wrong.

yes you lose root. this will make your tf700 like the factory jellybean firmware which is not rooted. go back to op and keep reading. each section builds on the previous. first get the jellybean firmware. im still playing with mine stock its so damn smooth. then you flash a custom recovery using his tool. then you flash the zip which gives you root. then i would make a back up so you can always get back to that point. then you can look into custom roms like scotts sweet clean rom for tf700 series
joseph473 said:
I upgraded to jb firmware and lost root. My 700T is unlocked. I thought I followed the procedure correctly but I did not get the message correct message when I ran the program. My device is not rooted. Can you tell me what I might be doing wrong.
Click to expand...
Click to collapse

beowolfschaefer said:
So I got the OTA JB update from Asus. I unlocked the boot loader using the Asus app. I downloaded and extracted US_epad-user-10.4.4.16.zip then threw it on the insternal SD card ( /storage/sdcard0 ). I rebooted with the volume key press and selected recovery. It gave me a message saying "booting recovery kernel". The next thing I see is an android on his back with a red exclamation sign.
What am I doing wrong?
Click to expand...
Click to collapse
If you have the JB Update why ware you trying to install it again? Proceed to section #2. You just need the Recovery and the Root portion. Skip step 1.
joseph473 said:
I upgraded to jb firmware and lost root. My 700T is unlocked. I thought I followed the procedure correctly but I did not get the message correct message when I ran the program. My device is not rooted. Can you tell me what I might be doing wrong.
Click to expand...
Click to collapse
To me it looks like you are trying to run the batch file without extracting the contents.

Thank you for this guide! Although it took me some time to understand it as I was on non-rooted/locked JB stock rom.
---------- Post added at 01:34 PM ---------- Previous post was at 01:29 PM ----------
scrosler said:
If you have the JB Update why ware you trying to install it again? Proceed to section #2. You just need the Recovery and the Root portion. Skip step 1.
Click to expand...
Click to collapse
I actually had similar problem as this guy. I was already on JB and the guide is made for people that are on ICS.

scrosler said:
To me it looks like you are trying to run the batch file without extracting the contents.
Click to expand...
Click to collapse
I am using a borrowed PC. I am a Mac user so forgive my ignorance. But when I look at the folder with Scott's Tool in it it looks like everything is extracted.

scrosler said:
If you have the JB Update why ware you trying to install it again? Proceed to section #2. You just need the Recovery and the Root portion. Skip step 1.
Click to expand...
Click to collapse
I actually tried this last night with no luck. I guess it was something funny with my desktop in that it couldn't connect using fast boot. Anyway I brought it in to work and ran it here and everything is fine. I am going to throw your stock/root rom on it now. Thanks for your help!

CWM-SuperSU-v0.96.zip
Hello,
thanks a lot for the guide, it is really clear and detailed.
My question is something I did not find on the previous question and it is more a double check to be sure I am not doing something I should not.
You say to install SU with the package copied on the internal SD, and you added a link to the SU thread. in this thread, the only SU as a package you can find is CWM-SuperSU-v0.96.zip, as it is CWM, will it work if I install it with TWRP? or there is special settings in this package that will not be recognised by TWRP?
Thanks in advance for your help
Regards

[GUIDE]Newbie Guide for Root/Recovery/Stock Restore etc. ATT LG G2 (LG D800)

If you have KK or LP there are two ways to get back root and custom recovery:
1) THIS IS THE EASIEST WAY.
Use stumproot app from playstore or their thread to root and then cloudyfa's Autorec app to flash twrp. You can also get autorecd800[/URL from play store (easier)
OR the harder way
2) Go back to JB d80010d (see section 4) and then follow the guide for rooting and recovery (section 2 and 3)
If you are on JB and need to upgrade to ATT kitkat use garyd9's [URL="http://forum.xda-developers.com/showthread.php?p=50882393"]method
or AndroidUser00110001's method.
These methods are almost as easy as flashing ROM and keep root and recovery intact
While the information on rooting, flashing recovery, going to stock exists in LG G2 forum, I found them scattered all over and overwhelming. The different models and different ATT firmware makes it even more confusing for newbies and so I thought we should have a ATT G2 guide. This guide is a combination of various threads in G2 forums and my rooting experience.
I will try to keep this guide up to date. Please let me know if you find something wrong or missing
THANKS: autoprime, hyelton,djrbliss, WACOMalt, PhilZ, TWRP team( DeesTroy et al), Koush, CWM, thecubed,vincom, Judge Joseph Dredd, SuperSport,bigfau. If I missed someone please let me know
Content:
1) Introduction
2) How to root
3) How to flash recovery
4) How to go back to stock (ATT Firmware)
- How to flash Official ATT KitKat
5) FAQs (ADB, Loki, Download Mode, Go to Recovery etc.)
6) Troubleshooting (unbricking)
1) Introduction:
There are many variants of LG G2. The ATT version is called LG D800. This guide is specifically for LG D800.
LG D800 ships with a custom Android Firmware that has been “enhanced” by LG and ATT.
The firmware is unrooted and has its bootloader locked meaning they designed it so that you cannot flash custom ROMS.
Fortunately, XDA’ers are very smart people and ways have been found to circumvent these “security” locks.
Before we begin we need to take care of few things.
Make sure you have drivers for your phone (http://www.lg.com/us/support-mobile/lg-D800)
Enable Developer option (General Settings -> About Phone -> Software Information and tap “Build Number” repeatedly(7-10 times) till you see a toast notification )
Enable USB debugging in developer option
2) ROOTING:
You need root privileges in your phone to run various useful apps like Titanium Backup, AdAway and install custom ROMs. Fortunately, rooting is very easy. Head over to autoprime’s thread) to download the IOroot .I have tested it (on KK). It works perfectly (LP not so sure).
thecubed also has an excellent guide on rooting with a video that you should check out.
Extract the zip into a folder. (I prefer C:\LG\ioroot). Remember this location.
Turn on USB debugging on LG D800 and connect it to your computer
Windows user double click root.bat and you will see a command screen pop up. Linux and Mac user should run the shell script ./root.sh(make sure they have proper permissions- chmod 777 should do it)
Follow the instructions on that screen. They are pretty simple.
It may ask you to disconnect the phone and turn off and then on the usb debug option and then reconnect the phone. Do so if prompted
Also keep an eye on your phone. It may prompt you with a warning. Go ahead and hit continue.
Once your phone is rooted it will give you an option of backing up EFS partition. PLEASE DO SO AND KEEP IT SOMEWHERE SAFE(dropbox etc.)
The screenshots in the "Click to Show Content" below show how ioroot process will progress
{
"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"
}
Another advantage of ioroot is that it has adb.exe in it. So if you need to do anything adb you can do that by going to ioroot folder through your command prompt.
***THIS METHOD WILL TRIP THE LG ROOT CHECK AND VOID WARRANTY. YOU HAVE BEEN WARNED*****.
If you encounter any problem head over to FAQs and Troubleshooting section
3) RECOVERY:
To install ROM’s and Kernels you need a custom recovery. Installing custom recovery is discouraged by ATT and hence the bootloader is locked. Fortunately djrbliss has released a tool called lokithat circumvents this lock and lets us flash recoveries, ROMs etc.
WACOMalt’s guide on installing TWRP is a must read for Newbies.
Before we go ahead please make sure that your firmware version is D80010d. If you have D80010o I would recommend going back to D80010d (see “How to go back to Stock” section). While you can flash recovery on D80010o, it does not behave well and you will not be able to flash some ROMs properly.
Things needed before flashing:
Proper drivers (see section 1)
ADB. There are various ways to get it but if you used ioroot you already have it
Go to windows command prompt (cmd) and go to your ioroot folder. which in my case was C:\LG\ioroot. From there you can type adb commands
For more info on ADD and how to get it see FAQs below
To flash recovery:
Get recovery of your choice. TWRP or PhilZ CWM . As of this writing TWRP by Blastagatoris preferable.
Copy the recovery image(.img file) to your adb folder (C:\LG\ioroot in my case). The twrp file is openrecovery-twrp-2.7.6.1-g2att.img. I would rename it to recovery.img just so that it is easier to type later on.NOTE: If you have a terp zip file extract the img file from the archive to use with loki
Download loki from github(https://github.com/djrbliss/loki). Select download zip on the right side on github page.The only file you need from the zip is loki_flash from bin folder.
Copy loki_flash to your adb location (C:\LG\ioroot in my case)
Run the following commands one at a time
Code:
adb push loki_tool /data/local/tmp/loki_tool
adb push recovery.img /data/local/tmp/recovery.img
adb shell
su
cd /data/local/tmp
chmod 777 loki_tool
./loki_tool flash recovery /data/local/tmp/recovery.img
exit
adb reboot recovery
**NOTE: loki_flash HAS BEEN REPLACED WITH loki_tool. JUST A NAME CHANGE. IF YOU HAVE OLDER VERSION OF ZIP REPLACE loki_tool with loki_flash**
The final command will reboot your phone and take you to your recovery
The screenshots in the "Click to Show Content" below show how the process will look like and what would happen if you try to flash non-loki image
4) How to go back to stock (ATT Firmware)
There are many reasons to go back to stock. Restoring warranty, reverting to 80100d firmware, soft bricks or plain old nostalgia. Fortunately, LG has a tool similar to odin called LGFlashTools for D800. Unfortunately, it is not as simple as odin and you have to jump through some hoops.
SuperSport has made restoring to Stock much easier with an installer.
Go to SuperSport thread and get the installer. Install the exe file and you are good to go.
An important thing to keep in mind: There is another better tool called LG Mobile Support Tool but it is for other G2 variants and not for ATT (or Sprint)
hyelton has written an excellent guide on reverting to stock. The tools in this section are from hyelton’s guide. Please read it for more information.
Before we start:
Make sure you have the drivers (section 1)
Download the LG Flash Tool
Download the firmware LGD800AT-01-V10d-310-410-AUG-14-2013.zip and LGD800_20130904_LGFLASHv160.dll files
Extract .tot file from V10d zip
To go back to stock:
Put your phone to download mode (power off. Then press the up volume button and connect it to computer without releasing the vol up button )
Once in download mode it may install stuff. Let it do so
Then change the COM port of your phone to 41 by going to devices and selecting LG G2 (see images below). Then unplug the phone and power it off
Find a key for LG Flash Tool (google search for it) and keep it with you
Now change date of your computer to 2012 January and disconnect internet
Install LG flash tool. It will ask for key. Enter it
You will see a place for loading dll file and tot file. Go ahead load files and click OK.
DO NOT CHANGE ANY OTHER SETTING
Then click on Yellow arrow
Then put you phone on download mode again (vol up and connect to computer)
You will see activity in LG Flash Tool. Let it run. It will automatically boot your phone.
Once your phone is booted and you see your all apps etc. disconnect the phone from comp.
The screenshots in the "Click to Show Content" below show how to change port to 41 and how LG FlashTool will look like when things are going OK.
Congratulations: You are all done
5) FAQs:
Tomsgt has a thread with videos on how to root, flash roms etc. that you should check out.
a) Boot to recovery:
If you have installed recovery you will need to go to it to flash stuff. Most custom ROMs have option in power menu to go to recovery. ATT Stock does not and so there are two ways to do so.
From adb type adb reboot recovery
Power off the phone. Then press volume down+power key. Do not release till you see LG logo. Then release and again press Vol down and power button. You will see a “Factory hard reset” screen that will say press power key to confirm. Do so. It will ask again. Go ahead and press power button again. Then you will boot into recovery.
b) Boot to download Mode:
If you are on custom ROM you should see this option under Power menu.
The other way to do it is Power off phone. Then while pressing volume up button plug the phone into computer. That should bring up the download mode in the phone
c) ADB (Android Debug Bridge):
ADB lets you communicate with your phone through a command line from your computer. You can upload file, flash zips, get logs etc. through adb. For the complete guide go to http://developer.android.com/tools/help/adb.html.
To get ADB you should get the Android SDK (http://developer.android.com/sdk/index.html). It is available for Windows, Linux and Mac. Once you have installed this get the Android SDK Platform Tools (ADB is in this Tools).
Windows users can just use the adb.exe in the ioroot folder (see Introduction Section). Just go to ioroot folder location from your DOS command prompt and type adb commands.
ADB drivers should have installed once you installed the drivers I had suggested in Introduction section.
Koush has a iniversal ADB driver for windows(http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi, https://github.com/koush/UniversalAdbDriver). You can try that if you experience driver issues.
d) LOKI:
Loki is a tool/hack made by Dan Rosenberg(djrbliss) to work around the Galaxy S4 bootloader. The tool does not unlock the bootloader but tricks it into running custom kernel. There is an excellent article explaining the hack and I encourage you to read it once. Loki was ported over to G2 and gives us the ability to flash recoveries and ROMs.
As end users you really do not need to worry too much about loki. It is the ROM developers job .
Note than any OTA by ATT may well contain fix for Loki. So DO NOT TAKE OTA.
e) Flash ROM:
PhilZ CWM: Go to “Wipe Data/ Factory Reset” and select “Clean to Install a new Rom”. Once done go back to “Install Zip” and then “choose zip from sd card”
TWRP: Similar but after factory reset you will have to do a “format system” under “mounts and storage”. I have not used twrp in a while so if this is old info please let me know
6) Troubleshooting
a)Unbricking
If you are reading this you have a problem. Your phone has become a brick. But do not despair yet as there are a few ways to unbrick your phone. Let us first determine whether it is a soft brick or a hard one.
Soft Brick: Basically it means your phone is bootlooping or showing a blank screen but you can still go to recovery/download mode. The easiest way to fix this (and determine if you have a soft vs hard brick) is turn off the phone and then press the volume up button and connect to the computer (keeping vol up pressed). If you see your phone enter download mode you are fine. Just restore to stock (see section 4 of this guide). Make sure you flash 80100d firmware.
Hard Brick: If you cannot enter download or recovery mode then you may have a hard-brick. This is not a fun situation to be in but there is a fix that may work. It involves lots of linux commands and is not for newbies but then if you are hard-bricked what have you got to lose. Head over to Partager.info's thread where he explains how @Shelnutt2 helped him unbrick his phone.

reserved
reserved

Good info here for the ATT LG G2 (LG D800), Stickied. Thank you.

Judge Joseph Dredd said:
Good info here for the ATT LG G2 (LG D800), Stickied. Thank you.
Click to expand...
Click to collapse
awesome guide! thank you for taking the time to make this. a couple things suggestions i would make in the guide. first is dont use twrp 2.6.3.2. use 2.6.3.3. it is much better. also dont use the latest philz recovery as of today. it is causing alot of issues so i would change the recommendation for recoveries to twrp 2.6.3.3.
thanks again.
edit: here is a link to 2.6.3.3. no need to loki it because it has already been loki'fied.
http://techerrata.com/browse/twrp2/g2att

freebee269 said:
awesome guide! thank you for taking the time to make this. a couple things suggestions i would make in the guide. first is dont use twrp 2.6.3.2. use 2.6.3.3. it is much better. also dont use the latest philz recovery as of today. it is causing alot of issues so i would change the recommendation for recoveries to twrp 2.6.3.3.
thanks again.
edit: here is a link to 2.6.3.3. no need to loki it because it has already been loki'fied.
http://techerrata.com/browse/twrp2/g2att
Click to expand...
Click to collapse
Thanks
The issue I had was that 2.6.3.3 was a zip and not a loki image. When I tried loki_flash I encountered issue. Hence I recommended using 2.6.3.2 and then flash whatever recovery one wants(2.6.3.3 or PhilZ). But then I was on 80100o when I did that so it could have been firmware's error and not twrp's. If you were able to loki_flash the recovery.img from 2.6.3.3 please let me know.
The PhilZ recovery I recommend above is older one (with no issues )

epapsiou said:
Thanks
The issue I had was that 2.6.3.3 was a zip and not a loki image. When I tried loki_flash I encountered issue. Hence I recommended using 2.6.3.2 and then flash whatever recovery one wants(2.6.3.3 or PhilZ). But then I was on 80100o when I did that so it could have been firmware's error and not twrp's. If you were able to loki_flash the recovery.img from 2.6.3.3 please let me know.
The PhilZ recovery I recommend above is older one (with no issues )
Click to expand...
Click to collapse
yes 10o ota update gives recoveries problems. that's why it is recommended not to do the ota. twrp 2.6.3.2 is the version that takes forever to do wipes. 2.6.3.3 is the version that fixed that and now the wipes are fast.
here is a twrp 2.6.3.3 loki'd recovery. it's for d800 though and i dont think it'd work on other models. that's why the zip files have loki inside of it with a script that loki's specifically for that device. the reason loki_flash wouldnt work for you is because you were trying to use it on a zip file and not an image file. if you would have taken the image file out of the zip file and used that then it would have worked for you. like it just did for me when i just loki'd this attached image.
at&t d800 twrp 2.6.3.3 loki'd recovery = http://d-h.st/Wmg

freebee269 said:
yes 10o ota update gives recoveries problems. that's why it is recommended not to do the ota. twrp 2.6.3.2 is the version that takes forever to do wipes. 2.6.3.3 is the version that fixed that and now the wipes are fast.
here is a twrp 2.6.3.3 loki'd recovery. it's for d800 though and i dont think it'd work on other models. that's why the zip files have loki inside of it with a script that loki's specifically for that device. the reason loki_flash wouldnt work for you is because you were trying to use it on a zip file and not an image file. if you would have taken the image file out of the zip file and used that then it would have worked for you. like it just did for me when i just loki'd this attached image.
at&t d800 twrp 2.6.3.3 loki'd recovery = http://d-h.st/Wmg
Click to expand...
Click to collapse
Thanks. OP updated

I would suggest you add that users who already have the 11o update to "downgrade" to the 11d firmware.
I had lots of problems when I restored my phone back to stock using the 11o update so started fresh from the 11d firmware.

I have 10o with the lateset twrp 2.6.3.3. are you saying that I can not flash rooms with this set up, or if i do it will not work.

irokgalaxy said:
I have 10o with the lateset twrp 2.6.3.3. are you saying that I can not flash rooms with this set up, or if i do it will not work.
Click to expand...
Click to collapse
you can. but you might have complications with the rom after you boot into it.

AndroidUser00110001 said:
I would suggest you add that users who already have the 11o update to "downgrade" to the 11d firmware.
I had lots of problems when I restored my phone back to stock using the 11o update so started fresh from the 11d firmware.
Click to expand...
Click to collapse
I had mentioned that in Introduction section. Have emphasized it now- red and bold
Thanks

epapsiou said:
I had mentioned that in Introduction section. Have emphasized it now- red and bold
Thanks
Click to expand...
Click to collapse
Ha I guess I missed it. Never did learn that lesson about reading and skimming
Nice guide!

experiencing an odd problem when restoring back to factory. of course it still fails but its not that. now when i click on software update it says phone is not registered????? wth is that? now i cant update?

Excellent Work
Thanks for this information.
I was looking for this kind of information at one place, for the new comers like me.

podagee said:
experiencing an odd problem when restoring back to factory. of course it still fails but its not that. now when i click on software update it says phone is not registered????? wth is that? now i cant update?
Click to expand...
Click to collapse
can you provide with detailed steps you followed with screenshots

epapsiou said:
can you provide with detailed steps you followed with screenshots
Click to expand...
Click to collapse
http://forum.xda-developers.com/member.php?u=5182870&tab=quotes

OP updated. Added info on un-bricking (both soft and hard)

I'm trying to return to stock... But when I go into download mode It is stuck at "Firmware Update - 0%". Any tips?

Thanks for this incredible write-up.
I'm sorry, but some of the information about twrp and ota's is out of date and confusing. I just bought a D800 2 weeks ago, and it came with the 10o firmware. I did not have to downgrade, nor do I have any issues flashing or running any roms. I followed autoprime's thread and used ioroot21, and as it is repeated over and over again in that thread, downloaded freegee from the play store and flashed the proper recovery. Simple as that.
Sent from my Dark Chocolate 4.4 G2

aaronDroid80 said:
Thanks for this incredible write-up.
I'm sorry, but some of the information about twrp and ota's is out of date and confusing. I just bought a D800 2 weeks ago, and it came with the 10o firmware. I did not have to downgrade, nor do I have any issues flashing or running any roms. I followed autoprime's thread and used ioroot21, and as it is repeated over and over again in that thread, downloaded freegee from the play store and flashed the proper recovery. Simple as that.
Sent from my Dark Chocolate 4.4 G2
Click to expand...
Click to collapse
I too have 10o firmware. Please let me know if I've to really downgrade it to 10d and then root (just trying to avoid the extra step!). Also please provide that link for rooting as well. Thanks! .

HOW TO ROOT OJ6/OI6/OGD ruturn to stock tar n920pvpu2aoi6

EDIT: 11/01/2015...This root method will work for OGD...OI6...OJ6... TRIED TESTED AND PROVEN ! ! !
WARNING: Once you USE THIS OI6 TAR OR take the OI6 OTA UPDATE . . . .
You will NOT be able to revert back down to OGD​
EDIT: 11/01/2015...If you take OJ6 OTA Update, YOU CAN USE OI6 TAR FILE TO REVERT BACK TO OI6 / STOCK
With this TAR, you will be able to ODIN back to 100% FULL SPRINT STOCK. in the event you develop bootloops or just want to unroot
ROOTING will trip knox and tripping knox WILL kill Samsung pay FOREVER...even if you flash back the stock tar
I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOU PHONE. ... IT IS YOUR DECISION TO TAKE THE PLUNGE.
Anyone that tries this and gets bootloops and cannot recover here is a link to the OI6 stock tar file... flash in Odin AP slot from download mode you should recover very easily DOWNLOAD THE SPRINT N920P OI6 STOCK TARBALL HERE TO RECOVER AND/OR TO RETURN TO OI6 STOCK
WORD OF WARNING>>> AGAIN Once you take the update to OI6 or use the OI6 TAR (get OI6 HERE ) .. YOU CAN NOT GO BACK TO OGD.....
TO ROOT:
Download ODIN 3.10.7
Download FREEZA's BEASTMODE KERNEL HERE
Download TWRP-2.8.7.0-N920P.tar
Download BETA-SuperSU-v2.49.zip
PREP THE PHONE FIRST ...
go to settings>>>about device>>> scroll to bottom and build number 8 times
now press back button once and tap developer options...
make sure USB debugging is on AND OEM UNLOCK NEEDS TO BE ON ALSO .....
{
"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"
}
Place phone in ODIN / Download mode ( press and hold vol down+home+power for a few seconds...then release and press vol up)
plug the phone to the pc....Watch for ID:COM in top left corner to give an ID.......if none is given then check the data cable or try a different one.... NOTE: once you try a flash and "IF" it fails... you will need to disconnect and power off the phone ( to power off press and hold Vol down + power for 10 sec ) and go back into download mode again or you will get "Setup Connection" hangup error when re-trying to flash
Now Click the "AP" button and in the pop up window, migrate to the KERNEL and double click it. Wait for it to verify md5 checksum. If bad, re-download the file.
Now check in the OPTIONS TAB.... make sure ONLY Auto Reboot & F. Reset Time are checked...
uncheck Re-Partition ! ! !
Once these steps are followed, click start and wait till you see PASS in the ID:COM Field
After re-boot, follow same steps and flash TWRP
Then either install SuperSU in TWRP by going into recovery by powering off the phone then press and hold vol up+home+power until you see the TWRP splash .... or just install from the market( the market install "may" give update binaries issues... flash in TWRP )
I have a SPECIAL HANGOUTS thread for SPRINT NOTE 5 OWNERS.
I would like to add ALL of you to it.
PLEASE PM ME YOUR GMAIL EMAIL ADDRESS SO I CAN ADD YOU
So you have rooted, NOW WHAT? . . . You need to flash the best custom rom > > > >
Galaxy Note 5 OI6 & OGD Deodexed Rom
@tdunham has built the best deodexed rom.... CLICK HERE FOR HIS THREAD or CLICK this button
tdunham said:
Galaxy Note 5 OGD/OI6 Stock Deodexed Rom2
This build is based on the stock OGD & OI6 5.1.1 Lollipop builds.
This is a first release. Even though it has been tested, please report any issues.
Features:
- Rooted
- Busybox
- SQLite
- Hotspot enabled
- Knox Removed
- ItsOn Removed
Download Link ---> N920P_OGD.5.1.1.De-Odexed.Ver1.0.zip
Download Link ---> N920P_OI6.5.1.1.De-Odexed.Ver1.0.zip
Changelog:
OI6 Release
- OI6 brings some security enhancements and fixes nothing specific.
- Fixed access to hiddenment dialer codes
- stagefright vulnerability fully patched (for now)
- Beastmode v1.2 kernel already included.
Rom Installation
Preparing the stock rom
• In the stock rom, turn on developer mode, enable USB debugging and OEM Unlock
- Settings>>>about device>>> scroll to bottom and tap build number 8 times
now press back button once and tap developer options...
- Toggle on both USB debugging and OEM Unlock.
• Copy the downloaded rom.zip file to internal storage
Install Custom Recovery with Odin
• Download Odin & custom recovery tar
Odin3_v3.10.6.zip
TWRP-2.8.7.1-Alpha_N920P.tar.md5
or
philz_touch_6.59.0-820876114.tar.md5
• Extract Odin zip-file
• Power down the phone
• Open Odin on pc
• Boot phone in Download Mode (press and hold Home + Power + Volume Down buttons)
• Connect phone and wait until you get a blue sign in Odin
• Add the recovery file to AP / PDA (depending on version of Odin)
• Make sure re-partition & Auto Reboot are NOT ticked
• Click the start button and let the Odin flash complete
• Unplug & Reboot phone directly into Recovery Mode (press and hold Home + Power + Volume Up buttons)
• BACKUP YOUR CURRENT SETUP WITH TWRP
• Do a FULL wipe but do not reboot yet
A full wipe includes:
Dalvik Cache
System
Data
Cache
• Flash rom and reboot.
Going back to the Stock Rom
• Use the same Odin instructions to flash TWRP above but using the stock tar
Credits to my beta testers: @Chaz187 @fsunoles101 @JoeyDuran @GAPO @rlmiller @sml2004
Special Credits to: @tx_dbs_tx
For help with development, the csc & personal mode fixes.
Click to expand...
Click to collapse
to read about it​.
.
.
.
.
.
.
.

reserved for later 1

reserved for later 2

reserved for later 3

nice bro, thanks. a lot of people have been waiting for this!

Is there by chance a flashable zip that doesn't affect the bootloader so you can go back to ogd if you want? I know in the past it has been done before, not sure what it takes to accomplish this. Thanks for all your hard work.

Thank you sooooo much, but this definitely should not be in the general section for sure. A mod needs to move this to its proper place, this is a lifesaver.

So I got a replacement Note 5. I updated to OJ6 and then followed this tutorial to root. I managed to get root and installed twrp. However, try to flash certain zips in twrp the phone just reboots. This only happens with certain zip files like xposed installer and the volume mod zip. The interesting thing is these zips flashed fine on my old Note 5.
Anyone have any ideas?
Edit: Nevermind, I reflashed stock via odin and went through update and root again. NOw it seems like it's working.

Can I flash twrp first and then flash the kernel zip? Because when I try to flash the kernel through Odin it gets stuck before it even starts.

melendez214 said:
Can I flash twrp first and then flash the kernel zip? Because when I try to flash the kernel through Odin it gets stuck before it even starts.
Click to expand...
Click to collapse
Yes, that shouldn't be a problem

rlmiller said:
Yes, that shouldn't be a problem
Click to expand...
Click to collapse
Ok thank you

DarkManX4lf said:
So I got a replacement Note 5. I updated to OJ6 and then followed this tutorial to root. I managed to get root and installed twrp. However, try to flash certain zips in twrp the phone just reboots. This only happens with certain zip files like xposed installer and the volume mod zip. The interesting thing is these zips flashed fine on my old Note 5.
Anyone have any ideas?
Edit: Nevermind, I reflashed stock via odin and went through update and root again. NOw it seems like it's working.
Click to expand...
Click to collapse
Can u get xposed working with OJ6? Stock rom?

drewiskee said:
Can u get xposed working with OJ6? Stock rom?
Click to expand...
Click to collapse
Yeah it works with stock rooted.

DarkManX4lf said:
Yeah it works with stock rooted.
Click to expand...
Click to collapse
I tried and got reboots and had to flash stock rom from lower build.
using twrp recovery

I have the edge + .....can I revert back to oi6 as well? Sorry I'm new at all this! Lol thank you

So, I was a master at rooting/manipulating my phone, but as it was a Note 2 until yesterday, I'm a bit rusty.
My son and I both got new Note 5s yesterday (a 32G and a 64G) and they've got OJ6 on them. I'm not completely sure I understand the instructions in post 1 - do I have to take the phone back to OI6 to be able to root using this method? Is there no root exploit for OJ6?
If I do have to revert, could you post clearly how to do it, please? Once I get past that I should be okay...
I have all these things I want to get done on the new one (getting rid of all the Sprint apps, backing up my messages, moving some program data over, more...) but realized everything I know about manipulating a cell phone is in Root, so I have to do it...
Thanks, in advance, for the help!!!

wackydroid said:
So, I was a master at rooting/manipulating my phone, but as it was a Note 2 until yesterday, I'm a bit rusty.
My son and I both got new Note 5s yesterday (a 32G and a 64G) and they've got OJ6 on them. I'm not completely sure I understand the instructions in post 1 - do I have to take the phone back to OI6 to be able to root using this method? Is there no root exploit for OJ6?
If I do have to revert, could you post clearly how to do it, please? Once I get past that I should be okay...
I have all these things I want to get done on the new one (getting rid of all the Sprint apps, backing up my messages, moving some program data over, more...) but realized everything I know about manipulating a cell phone is in Root, so I have to do it...
Thanks, in advance, for the help!!!
Click to expand...
Click to collapse
Yes, you can root OJ6 the same exact way as all the current builds.
I'm sure you're familiar with Odin by now so just download the OI6 factory tar (there isn't one available for OJ6 so far, its only available as an OTA update) and have that handy should you wish or need to go back to stock.
Also, if you see the OGD tar, don't bother with that one, you wont be able to flash that factory tar anyway as it will fail checks in odin when it recognizes you're on a newer build.
Additionally:
Since you're going to trip knox anyway by flashing TWRP custom recovery, you might want to keep in mind about wiping your internal storage too if you're having any issues along the way. It probably doesn't apply quite yet for you at this point but you know how it collects tons of extra stuff the longer you run android. There are a couple of deodexed stock builds and a custom rom too should you want additional features not available on stock.

All seemed to go well, BUT
When I boot, in tiny red type at top left, I get a "KERNEL IS NOT SEANDROID ENFORCING", or if booting into recovery "RECOVERY IS NOT SEANDROID ENFORCING".
What is that, and how do I fix it?
[EDIT] - I also just tried flashing the 1.2 version of the kernel and am still getting those messages...HELP...

wackydroid said:
All seemed to go well, BUT
When I boot, in tiny red type at top left, I get a "KERNEL IS NOT SEANDROID ENFORCING", or if booting into recovery "RECOVERY IS NOT SEANDROID ENFORCING".
What is that, and how do I fix it?
[EDIT] - I also just tried flashing the 1.2 version of the kernel and am still getting those messages...HELP...
Click to expand...
Click to collapse
That is normal you can't fix it!!!!!

SkyHigh auto-root kernel
OP.
Another auto root kernel. I've now added support for N920P
[KERNEL] [ROOT] [SM-N920P Exynos 7420] [02 Dec] SkyHigh TW 5.1.1 Kernel [v2.4]
I don't have the device, but I created it to share with users after receiving good feedback on Note5 :good:
Please make no direct download link, but add thread link to your OP (if your desire).
Also, loads of features with Synapse
Cheers,
UITA

Starting from stock 4.2.2 UK Tab 2 p5110

Hi guys,
Apologies first of all as I'm sure this has been asked over and over again but I'm still struggling to find a concrete route/guide to running custom roms starting from a stock device (Tab 2 10" P5110 JB 4.2.2).
As far as I understood I should do the following:
1. Install CF-Autoroot - However on CF website I read:
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !
Do I need to worry about the above or can I proceed to install the CF-autoroot via Odin?
2. Install custom recovery as above method leaves with stock recovery - Question here is what is the best way to proceed at this point? Install recovery via rom manager or another method (PC Odin etc) ?
3. Install custom rom and enjoy and improved device
Please if someone could clarify the steps I need to take (exact file versions etc) from a fully stock 10" Tab 2 running 4.2.2 it would be greatly appreciated. Or link me to what I'm after in case I've missed this!
All the best,
GalaxyDude
(Happy Christmas all!)

Galaxydude1 said:
Hi guys,
Apologies first of all as I'm sure this has been asked over and over again but I'm still struggling to find a concrete route/guide to running custom roms starting from a stock device (Tab 2 10" P5110 JB 4.2.2).
As far as I understood I should do the following:
1. Install CF-Autoroot - However on CF website I read:
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !
Do I need to worry about the above or can I proceed to install the CF-autoroot via Odin?
2. Install custom recovery as above method leaves with stock recovery - Question here is what is the best way to proceed at this point? Install recovery via rom manager or another method (PC Odin etc) ?
3. Install custom rom and enjoy and improved device
Click to expand...
Click to collapse
1st, it will only root your mobile, if your purpose is to stay on stock and just delete the bloat wares. and run modded apps. you're good to go
http://forum.xda-developers.com/showthread.php?t=1957165
http://forum.xda-developers.com/showthread.php?t=2203309
just check you're using the file meant for your device only. this thread has a detailed view. and no, its safe as long as you're using the files meant exactly for your device.
2nd installing a custom recovery is the first choice and the best and smartest thing to do, cause if after rooting you did something stupid with the system files, then all your data might be lost, custom recovery helps you keep complete nandroid backup of your device which means almost everything is backed up (except media and external memory card), lets you flash custom rom and in case anything goes wrong, you access the custom recovery and bam, restore your backup, and you're back at the original state. or flash your new custom rom
3. yes install a custom rom after you backup your stock factory rom.
remember taking backup at every step from here on onward is the first rule.
good luck and have fun on xda

Hi Billysam,
Thanks for the speedy reply
I'm aiming to eventually run a nice custom rom but just want to get the rooting and custom firmware down first so as you mention I can do a full nandroid backup before moving on.
I had a look at the link you posted but you're right that leaves you with stock recovery which would be fine if I wasn't going to install a custom rom.
I found http://forum.xda-developers.com/showthread.php?t=1722745
So now I've got:
Odin 3.0.7
philz_touch_5.03.7-p5110.tar.md5
Superuser-3.1.3-arm-signed.zip
Was going to install the above via Odin and then do a full backup, does that sound about right?
Cheers again!
Galaxydude1

Galaxydude1 said:
Hi Billysam,
Thanks for the speedy reply
I'm aiming to eventually run a nice custom rom but just want to get the rooting and custom firmware down first so as you mention I can do a full nandroid backup before moving on.
I had a look at the link you posted but you're right that leaves you with stock recovery which would be fine if I wasn't going to install a custom rom.
I found http://forum.xda-developers.com/showthread.php?t=1722745
So now I've got:
Odin 3.0.7
philz_touch_5.03.7-p5110.tar.md5
Superuser-3.1.3-arm-signed.zip
Was going to install the above via Odin and then do a full backup, does that sound about right?
Cheers again!
Galaxydude1
Click to expand...
Click to collapse
Philz recovery is fine, but some custom roms requires twrp recovery, both are good. check which rom you're going to try and see if it says needs twrp, download that, if not philz is safe too and it's not much hard to switch.
Superuser app, you won't need unless the custom rom you're going to install doesn't have one already. most do. just get custom recovery installed, find a good custom rom, for your device, read instructions and other members who already tried it. don't rush. backup first.
small note- please click reply and then type your msg, it will quote and send me a notification as well. if you don't quote or don't hit thinks, I might not even get notified and see your msg. cheers

billysam said:
Philz recovery is fine, but some custom roms requires twrp recovery, both are good. check which rom you're going to try and see if it says needs twrp, download that, if not philz is safe too and it's not much hard to switch.
Superuser app, you won't need unless the custom rom you're going to install doesn't have one already. most do. just get custom recovery installed, find a good custom rom, for your device, read instructions and other members who already tried it. don't rush. backup first.
small note- please click reply and then type your msg, it will quote and send me a notification as well. if you don't quote or don't hit thinks, I might not even get notified and see your msg. cheers
Click to expand...
Click to collapse
No problem at all, I'd actually deleted the requote to save spam as I assumed you'd be notified auto as you'd contributed
Thanks for the info, on the back of what you've said I think I'll put on PhilsRecovery as I've got it downloaded for my specific model, do a full backup and then can I use Rom manager to install TWRP via the app?
Kind regards,
Galaxydude1

Galaxydude1 said:
Thanks for the info, on the back of what you've said I think I'll put on PhilsRecovery as I've got it downloaded for my specific model, do a full backup and then can I use Rom manager to install TWRP via the app?
Click to expand...
Click to collapse
Yes, go with that. and you can change to twrp with rom manager. but most of the custom rom threads have the recoveries mentioned there and most of the time you will find updated once here on the page. check this page
http://forum.xda-developers.com/galaxy-tab-2/10-inch-development
this is the place you will find all custom roms for your device and updated information. wherever you see P51xx , that rom works for your device as well.

billysam said:
Yes, go with that. and you can change to twrp with rom manager. but most of the custom rom threads have the recoveries mentioned there and most of the time you will find updated once here on the page. check this page
http://forum.xda-developers.com/galaxy-tab-2/10-inch-development
this is the place you will find all custom roms for your device and updated information. wherever you see P51xx , that rom works for your device as well.
Click to expand...
Click to collapse
Thanks for your advice :good:
One thing I just realised though is if you have to be rooted in order to do a full nandroid backup I'll need to flash the recovery with Odin and then install the superuser file zip from recovery before the backup will work.
Am I right in thinking the above?
Cheers again.

Galaxydude1 said:
Thanks for your advice :good:
One thing I just realised though is if you have to be rooted in order to do a full nandroid backup I'll need to flash the recovery with Odin and then install the superuser file zip from recovery before the backup will work.
Am I right in thinking the above?
Cheers again.
Click to expand...
Click to collapse
Get into recovery first and try to backup if it does, you're fine, if it doesn't you can flash superuser zip inside recovery and try then backup.
it's not that risky.

billysam said:
Get into recovery first and try to backup if it does, you're fine, if it doesn't you can flash superuser zip inside recovery and try then backup.
it's not that risky.
Click to expand...
Click to collapse
I just gave it a try but looks like some driver issue going on with PC (Windows 10):
http://imgur.com/5RKLSp6
Just hangs when trying to install drivers (have latest Samsung USB drivers installed) and I've checked and Kies wasn't running, going to try on my Windows 7 PC and see if it's any better. Is there anything else I need installed I'm missing? Should have ADB stuff installed as recently used this laptop to connect to Fire TV.
Will keep thread updated.
Thanks again,
Galaxydude.

Galaxydude1 said:
I just gave it a try but looks like some driver issue going on with PC (Windows 10):
http://imgur.com/5RKLSp6
Just hangs when trying to install drivers (have latest Samsung USB drivers installed) and I've checked and Kies wasn't running, going to try on my Windows 7 PC and see if it's any better. Is there anything else I need installed I'm missing? Should have ADB stuff installed as recently used this laptop to connect to Fire TV.
Will keep thread updated.
Thanks again,
Galaxydude.
Click to expand...
Click to collapse
it shows device connected at com3 in odin. if its blue and shows com3 or any other com, you're connected so the drivers are good, have you enabled usb debugging in settings? if not enable it.
it's getting hanged at installing drivers or is it trying to get update from the internet? might be issue with windows 10. check on windows 7

billysam said:
it shows device connected at com3 in odin. if its blue and shows com3 or any other com, you're connected so the drivers are good, have you enabled usb debugging in settings? if not enable it.
it's getting hanged at installing drivers or is it trying to get update from the internet? might be issue with windows 10. check on windows 7
Click to expand...
Click to collapse
Yeah I managed to get the drivers to install out of download mode but I'm still getting a blue com with it connected and usb debugging enabled.
Going to try on W7 later and post what happens.
All the best.

billysam said:
it shows device connected at com3 in odin. if its blue and shows com3 or any other com, you're connected so the drivers are good, have you enabled usb debugging in settings? if not enable it.
it's getting hanged at installing drivers or is it trying to get update from the internet? might be issue with windows 10. check on windows 7
Click to expand...
Click to collapse
So after reading multiple posts of people saying the blue com status was the same as yellow (different due to software version) I decided to go ahead and try CF-Autoroot with my Tab 2 4.2.2 JB stock and this was SUCCESSFUL:
{
"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"
}
http://imgur.com/VQxjInS
So for those of you wondering if it will work on latest stock firmware it does
Now I'm going to try get a custom recovery installed so I can do a full nandroid backup before I play with any roms.
Thanks all!
Galaxydude1

[GUIDE][EASY METHOD]Update To Official Nougat Firmware and Reroot With SuperSu

UPDATE: Hey guys! Easiest way to update to the new Nougat firmware & reroot with SuperSU currently is to install this debloated rom I just made. It does it all in one flash.
https://forum.xda-developers.com/showthread.php?p=72098300
----------
No doubt, there's already a ton of posts about this, but I decided to make this guide anyway for those who maybe prefer SuperSU over Magisk and just want to update Android and reroot quickly and easily. This method will get you rooted before you even boot up the Nougat firmware for the first time. Just be sure, of course, to BACKUP ALL YOUR DEVICE DATA BEFORE DOING THIS.
NOTE: If you use the Samsung Health app then be sure to read this post through to the end.
DOWNLOADS:(click to open links)
Odin
Nougat stock firmware
TWRP
SuperSU Nougat Fix Zip(Do not use the official SuperSU zip. It will result in "stuck at creating image" error.)
no-verity-opt-encrypt(Attached below.)
1) Install & open Odin. Uncheck "Auto Reboot" in the Options tab. Then follow the instructions pictured below to flash the firmware package to your device.
{
"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"
}
2) Once it's finished recheck "Auto Reboot" and flash TWRP the same way. IMMEDIATELY AFTER IT REBOOTS and the screen goes blank, hold Volume Up, Home key and power buttons to boot into TWRP. (Otherwise it will launch Android setup.)
NOTE: If for whatever reason the firmware and TWRP won't flash back to back then just reboot into Download mode again and finish with flashing TWRP. It seems that will happen on occasion on more recent versions of Odin.
3) Once TWRP loads, connect your device and drag and drop the "no-verity" and "supersu" files(from above) to the root of your sdcard.
4) Go to "Install" and select the "no-verity-opt-encrypt" file. Then click the "Add more Zips" button and add the SuperSU file as well and swipe to flash.
5) Reboot into Android and complete device setup.
You should now be rooted with Nougat and SuperSU!
BONUS:
Easy way to fix the Samsung Health "device has been compromised" or "can't be opened on a rooted device" errors.
1) Download an app from the Play Store called "BuildProp Editor".
2) Search for "ro.config.tima".
3) Click on it and change the "1" to a "O".
4) Reboot device.
If this helped you, then please consider hitting the "Thanks" or Donate button. Thank you!

bogarty said:
No doubt, there's already a ton of posts about this, but I decided to make this guide anyway for those who maybe prefer SuperSU over Magisk and just want to update Android and reroot quickly and easily. This method will get you rooted before you even boot up the Nougat firmware for the first time. Just be sure, of course, to BACKUP ALL YOUR DEVICE DATA BEFORE DOING THIS.
NOTE: If you use the Samsung Health app then be sure to read this post through to the end.
DOWNLOADSclick to open links)
Odin
Nougat stock firmware
TWRP
SuperSU Nougat Fix Zip(Do not use the official SuperSU zip. It will result in "stuck at creating image" error.)
no-verity-opt-encrypt(Attached below.)
1) Install & open Odin. Uncheck "Auto Reboot" in the Options tab. Then follow the instructions pictured below to flash the firmware package to your device.



2) Once it's finished recheck "Auto Reboot" and flash TWRP the same way. IMMEDIATELY AFTER IT REBOOTS and the screen goes blank, hold Volume Up, Home key and power buttons to boot into TWRP. (Otherwise it will launch Android setup.)
3) Once TWRP loads, you should do a full "advanced wipe" of everything(except the internal and usb storages) before moving forward. Afterwards, connect your device and drag and drop the "no-verity" and "supersu" files(from above) to the root of your sdcard.
4) Go to "Install" and select the "no-verity-opt-encrypt" file. Then click the "Add more Zips" button and add the SuperSU file as well and swipe to flash.
5) Reboot into Android and complete device setup.
You should now be rooted with Nougat and SuperSU!
BONUS:
Easy way to fix the Samsung Health"device has been compromised" or "can't be opened on a rooted device" errors.


1) Download an app from the Play Store called "BuildProp Editor".
2) Search for "ro.config.tima".
3) Click on it and change the "1" to a "O".

4) Reboot device.
If I've helped you, then please consider hitting the "Thanks" button. Thank you!

[/HIDE]
2) Once it's finished recheck "Auto Reboot" and flash TWRP the same way. IMMEDIATELY AFTER IT REBOOTS and the screen goes blank, hold Volume Up, Home key and power buttons to boot into TWRP. (Otherwise it will launch Android setup.)
3) Once TWRP loads, you should do a full "advanced wipe" of everything(except the internal and usb storages) before moving forward. Afterwards, connect your device and drag and drop the "no-verity" and "supersu" files(from above) to the root of your sdcard.
4) Go to "Install" and select the "no-verity-opt-encrypt" file. Then click the "Add more Zips" button and add the SuperSU file as well and swipe to flash.
5) Reboot into Android and complete device setup.
You should now be rooted with Nougat and SuperSU!
BONUS:
Easy way to fix the Samsung Health"device has been compromised" or "can't be opened on a rooted device" errors.
2) Once it's finished recheck "Auto Reboot" and flash TWRP the same way. IMMEDIATELY AFTER IT REBOOTS and the screen goes blank, hold Volume Up, Home key and power buttons to boot into TWRP. (Otherwise it will launch Android setup.)
3) Once TWRP loads, you should do a full "advanced wipe" of everything(except the internal and usb storages) before moving forward. Afterwards, connect your device and drag and drop the "no-verity" and "supersu" files(from above) to the root of your sdcard.
4) Go to "Install" and select the "no-verity-opt-encrypt" file. Then click the "Add more Zips" button and add the SuperSU file as well and swipe to flash.
5) Reboot into Android and complete device setup.
You should now be rooted with Nougat and SuperSU!
BONUS:
Easy way to fix the Samsung Health"device has been compromised" or "can't be opened on a rooted device" errors.

1) Download an app from the Play Store called "BuildProp Editor".
2) Search for "ro.config.tima".
3) Click on it and change the "1" to a "O".
4) Reboot device.
If I've helped you, then please consider hitting the "Thanks" button. Thank you!

Click to expand...
Click to collapse
Nice guide!
Sent from my SM-N920T using XDA Labs

rmarinella said:
Nice guide!
Click to expand...
Click to collapse
Thank you! Holy OP quote though. Haha!

Any problems with Samsung Account after root? Mine works fine unrooted but won't stay logged in after. Curiosity and what not....

DrRootso said:
Any problems with Samsung Account after root? Mine works fine unrooted but won't stay logged in after. Curiosity and what not....
Click to expand...
Click to collapse
I had same problem but it fixed....i am deodexed rooted with magisk clean installed and setup with mobile data thats all i did and works fine for now
Sent from my T-Mobile Samsung Galaxy Note5 using XDA Labs

odin
when I try to connect my phone to odin its not reading the phone where it says added. anyone else experience this in this version of odin? I have usb debugging checked, plus oem checked. I have also tried different usb cables and other odin applications.......weird.

skills2015 said:
when I try to connect my phone to odin its not reading the phone where it says added. anyone else experience this in this version of odin? I have usb debugging checked, plus oem checked. I have also tried different usb cables and other odin applications.......weird.
Click to expand...
Click to collapse
Try to download the drivers here:
http://org.downloadcenter.samsung.c...G_USB_Driver_for_Mobile_Phones_v1.5.45.00.exe

DrRootso said:
Any problems with Samsung Account after root? Mine works fine unrooted but won't stay logged in after. Curiosity and what not....
Click to expand...
Click to collapse
I have not experienced any issues myself. Everything should work fine on stock firmware. The only problem I found was with Samsung Health not working with root, but I provided the fix for that in the OP. Maybe try removing the account in Settings and adding it back manually.

bogarty said:
I have not experienced any issues myself. Everything should work fine on stock firmware. The only problem I found was with Samsung Health not working with root, but I provided the fix for that in the OP. Maybe try removing the account in Settings and adding it back manually.
Click to expand...
Click to collapse
I dont think it will let him added it will say session expired even after entering it again....he might have to factory reset and setup again or setup via mobile data
Sent from my T-Mobile Samsung Galaxy Note5 using XDA Labs

JonathanRAZ said:
I dont think it will let him added it will say session expired even after entering it again....he might have to factory reset and setup again or setup via mobile data
Click to expand...
Click to collapse
Strange I haven't seen this issue. Is it a Magisk problem? I signed into Samsung Account during initial device setup and its been working fine.

bogarty said:
Strange I haven't seen this issue. Is it a Magisk problem? I signed into Samsung Account during initial device setup and its been working fine.
Click to expand...
Click to collapse
No is not magisk i have it installed and all is fine on this side.....it can be on setup the problem the first time i had i setup with wifi and after changing to mobile dta had session expired....i dont know if is that or not but since i have setup via mobile data it works fine no problems
Sent from my T-Mobile Samsung Galaxy Note5 using XDA Labs

JonathanRAZ said:
No is not magisk i have it installed and all is fine on this side.....it can be on setup the problem the first time i had i setup with wifi and after changing to mobile dta had session expired....i dont know if is that or not but since i have setup via mobile data it works fine no problems
Click to expand...
Click to collapse
Weren't you using that unrooted rom from the other thread? Maybe there was a problem there.

bogarty said:
Weren't you using that unrooted rom from the other thread? Maybe there was a problem there.
Click to expand...
Click to collapse
No i was stock rooted with magisk......then was on my own deodexed rom.....then now i am on that unrooted rom.....and later on will be on a new one i will make after installing windows 10
Sent from my T-Mobile Samsung Galaxy Note5 using XDA Labs

thanks for this. sadly volte isnt working for me so ill be using the stock tweaked rom, hopefully it works. but using this root method. thanks again!

justin94 said:
thanks for this. sadly volte isnt working for me so ill be using the stock tweaked rom, hopefully it works. but using this root method. thanks again!
Click to expand...
Click to collapse
Still don't get how anyone could be having any issues with any Android features. If you're flashing the stock firmware, everything should work. VoLTE seems to be working fine for me.

bad flash probably. but this root method worked on that stock tweaked rom. everything is working.

Anyone know the differences between magisk and supersu? Pros and cons for both.. I was thinking about doing the magisk root but I've always rooted with supersu.
Sent from my SM-N920T using Tapatalk

I followed the steps but it doesn't seem to be working well for me. I can flash the stock FW fine but when I try to flash TWRP odin doesn't go through the process. I shut down the phone and went back into download mode and that allowed me to flash TWRP. I booted immediately into TWRP and flashed the two files (no-verity & Nougat Root SU - no Kernel ) from the links provided. I performed the wipe as suggested before flashing the two files in TWRP. When I reboot the phone I'm greeted with the message Kernel not seandriod enforcing. Is it because I'm using the wrong Root SU file?

Maximus2102 said:
I followed the steps but it doesn't seem to be working well for me. I can flash the stock FW fine but when I try to flash TWRP odin doesn't go through the process. I shut down the phone and went back into download mode and that allowed me to flash TWRP. I booted immediately into TWRP and flashed the two files (no-verity & Nougat Root SU - no Kernel ) from the links provided. I performed the wipe as suggested before flashing the two files in TWRP. When I reboot the phone I'm greeted with the message Kernel not seandriod enforcing. Is it because I'm using the wrong Root SU file?
Click to expand...
Click to collapse
Nevermind. I was able to get passed it but I flashed Magisk instead. I'm up and running with Rooted Nougat.

geeshiet said:
Anyone know the differences between magisk and supersu? Pros and cons for both.. I was thinking about doing the magisk root but I've always rooted with supersu.
Click to expand...
Click to collapse
I made this tutorial because I've always felt SuperSU to be more reliable personally. The last rom I had forced you to use Magisk and I didn't like it. Magisk just kind of seems like too bulky of a package for me. Too much extra stuff, going on and sometimes(a couple versions back) the package updates can be faulty and even cause device reboots. SuperSU, to me, just seems lighter and more reliable and concise.
Maximus2102 said:
when I try to flash TWRP odin doesn't go through the process.* I shut down the phone and went back into download mode and that allowed me to* flash TWRP.
Click to expand...
Click to collapse
Rebooting is fine, though there shouldn't be a problem flashing both in a row. It does take about 10-20 seconds or so sometimes before it will let you load the next one.
Maximus2102 said:
When I reboot the phone I'm greeted with the message Kernel not seandriod enforcing.* Is it because I'm using the wrong Root SU file?
Click to expand...
Click to collapse
The kernel not seandroid enforcing message has never been anything to worry about. It's just Samsung's of way of telling you that the kernel has been modified to allow for root. You shouldn't have that message though with SuperSU, as SuperSU uses a systemless root method. So if you're seeing that, then you've done something additional that's modified the kernel. What "Root SU file" did you mean? Flashing the SuperSU zip roots the device. No extra files are needed.
Maximus2102 said:
Nevermind. I was able to get passed it but I flashed Magisk instead. I'm up and running with Rooted Nougat.
Click to expand...
Click to collapse
You got rid of SuperSU because you saw "kernel not seandroid enforcing" message? Again that message is nothing to be concerned about. You'll see the same thing if you install a custom kernel, but again, if you were seeing that message during this process, then you did something wrong or did an extra step.