Database Info

[Galaxy Note2 TOOLKIT V6 GSM] Drivers, Backup, Root, Recovery, Flash Stock Image

[TOOLKIT] UNIFIED ANDROID TOOLKIT - SAMSUNG GALAXY NOTE 2 - Drivers, Root, Recovery + MORE
GSM (GT-N7100) and LTE (GT-N7105) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=1923956
AUSTRALIAN GSM (GT-N7100T) and LTE (GT-N7105T) SUPPORTED. USE GSM THREAD
SPRINT (SPH-L900) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=1957155
TMOBILE (SGH-T889) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=1957720
MOBILICITY, VIDEOTRON, WIND [SGH-T889V] SUPPORTED. NO THREAD YET. USE TMOBILE THREAD
AT&T (SGH-L317) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=2052779
BELL, ROGERS, SASKTEL, TELUS [SGH-I317M] SUPPORTED. NO THREAD YET. USE AT&T THREAD
VERIZON ([SCH-I605]) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=2052788
US CELLULAR (SCH-R950) SUPPORTED. NO THREAD YET. USE ANY
KOREAN SK TELECOM [SHV-E250S] SUPPORTED. NO THREAD YET. USE ANY
The Unified Android Toolkit brings together all the Nexus and Samsung Toolkits and supports many Nexus and Samsung devices. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.
FUNCTIONS OF UNIFIED ANDROID TOOLKIT
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit/Windows 10
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
* Unlock/Re-Lock your Bootloader [Nexus]
* Root Stock builds
* Various Root options using insecure boot image or custom recovery
* ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
* ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
* [NEW] use SkipRoot boot image to Auto Root device, install Busybox Binaries and rename Recovery Restore files [selected devices]
* Install BusyBox on your device
* Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
* Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
* Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
* Extras, Tips and Tricks section
* Auto Update ToolKit to latest available version at startup (professional only feature)
* Program up to 10 Quickpick slots and run them very quickly (professional only feature)
* Mods section to automatically perform certain tasks on your device
* Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
* Check md5 of stock image to make sure downloaded file isn’t corrupted before flashing [Nexus]
* Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
* Flash Custom Recovery or Google Stock Image to Device
* Flash any part of a stock Nexus image to device [boot, system, recovery] – Great for fixing broken parts of firmware
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
* Flash Custom Recovery to Device
* Boot [Nexus] or Flash .img Files directly from your PC
* Install a single apk or multiple apk’s to your device
* Push Files from your PC to your device
* Pull Files from your device to your PC
* Disable forced encryption on Nexus6 and Nexus9 devices
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
* Install EFS/Partition Backup/Restore app by Wanam
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Set Files Permissions on your device
* Open new Command Prompt for manual input
* Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
* Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
* Display Important Information about 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"
}
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.
Credits: ChainsDD for Superuser, Chainfire for SuperSU and kernel patches, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels, Viperboy for the Knox Disabler app, Stephen Erickson for the BusyBox installer app, BurrowsApps for the Root Checker app, NextApp for the SD Fix app, fOmey for TWRP for the Galaxy Gear.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE AND ROOT YOUR DEVICE.
ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR ‘AUTO UPDATES’ DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE ‘QUICK PICKS’ SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE “ANY BUILD” OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD AS LONG AS THE VERSION IS SUPPORTED (USEFUL IF YOUR BUILD IS NOT LISTED).
MORE IMPORTANTLY DONATING SHOWS YOUR APPRECIATION AND ALLOWS THE TOOLKIT TO CONTINUE TO EVOLVE AND GROW.
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
--------------------------------------------------------------
1. INSTALLING ADB/FASTBOOT DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.
--------------------------------------------------------------
2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
USEFUL INFORMATION
How to get into Recovery Mode
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
How to get into Download Mode (For Odin)
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.

**FAQ**
Q. What is ADB Shell?
Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF (e.g removing system apps).
From Google:
Android Debug Bridge (adb) is a versatile tool lets you manage the state of an emulator instance or Android-powered device. It is a client-server program that includes three components:
A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device.
A daemon, which runs as a background process on each emulator or device instance.
----------------------------------------------------------------------------
Q. I flashed CWM but each time I reboot the Stock Recovery is back
There is an auto recovery restore system on Android that will reflash the Stock Recovery if you flash CWM on a Stock Rom.
Use Root Explorer to Mount the system folder as R/W (or use a free app from the Market). Delete the file recovery-from-boot.p from /system. Now when you flash CWM Recovery it will NOT be overwritten after a reboot. You can also use the Toolkit to rename the files if you wish.
----------------------------------------------------------------------------
Q. What is the difference between Nandroid and Titanium backup?
A NANDROID will backup the whole system including boot, system, data and recovery partitions so you can restore a complete rom and all data and settings.
Essentially Titanium Backup is used to backup apps and associated user data. These could be restored AFTER a full wipe and a new Rom had been flashed on your phone.
The other option now which google added into the new adb command list is the adb backup which is in the ToolKit and can do the same job as Titanium Backup but will store the data on your PC rather than on the phone (where it takes up space and could be deleted).
----------------------------------------------------------------------------
Q. When would i perform a nandroid vs a titanium backup?
You would perform a nandroid backup to back up your entire system including boot image and data and system partitions so you can restore your entire system back to that particular point in the future.
You would use Titanium Backup mainly to back up your installed apps and settings so they could be reinstalled easily and quickly on any future roms. You can also choose individual apps to backup or restore on Titanium Backup whereas if you restore your boot partition via CWM Recovery you are stuck with the whole lot.
----------------------------------------------------------------------------
Q. When I try to open the ToolKit I get a box pop up for a split second and then it goes away. My AntiVirus program says the file may be harmful.
The exe files I compiled are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton and AVG Free) will pick it up as potentially harmful when it is not. They pick up ANY file that doesnt contain a purchased Microsoft certificate in the same way. Restore the deleted file and exclude it from further scans and it will be fine.
----------------------------------------------------------------------------
Q. I donated but where do I get my activation code from?
Donation Codes are sent out manually to your PayPal email address [unless otherwise stated] after a confirmation email from PayPal has been receive. The Code can then be entered in the ToolKit Settings, Activate Donators Features Screen. This will enable The Auto Updates, Quick Picks and Extras Features in the ToolKit. Please be patient when waiting for the Code to be sent as it depends very much on what I am doing and whether I am at my PC when the donation is made. Please do not post in the ToolKit's thread or pm me asking for the activation code as it clogs up the thread and my messages. If you haven't received your code after 24 hours then feel free to email me via the skipsoft.net contact page.
Don't worry that you have been forgotten about, I check all emails personally and will deal with it as soon as I can.
----------------------------------------------------------------------------
Q. I have Windows 8 and cannot install the drivers
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
When your computer restarts, select ‘Disable driver signature enforcement‘ from the list. You can now load your modified driver. Reboot again once the driver is installed and all will be well.
----------------------------------------------------------------------------
Q. I flashed the Stock Firmware Image. Odin flashes the file successfully and the phone reboots but it stays stuck on the samsung logo
If the firmware tar file does not include a userdata image (which most Samsung firmware do not) then your userdata partition will be left from your previous setup. If this is incompatible with the new firmware because of build or something else then your system will freeze on boot up.
This is easily fixable by holding the Volume UP, Home and Power buttons all at the same time for about 10 seconds until the device reboots to the Stock Recovery screen. Use the Volume Down button to scroll down to 'wipe data/factory reset' and press the Home button to select it. Go down to yes to confirm and your userdata partition will be wiped. Your device should now boot fine.

*reserved if needed*

How To Videos on the Samsung Galaxy Note II ToolKit
This post belongs to wwjoshdew I am just mirroring his posts from the other Note2 threads.
Reserved for how to videos on this incredible toolkit!
http://www.youtube.com/playlist?list=PLwCVKEYxr_z7FBQYT32dbYw_kdSJmSDH2
How To Root
How To Manually Boot to Custom (or Stock) Recovery

mskips magic
Another one in the series of TOOLKITS from Mskip ( here since the early xdays ) and im v-happy to see this here.
im already rooted but this will make root a safer process for so many Note-2 owners.
here we go

Appreciate your big work Mskip !!!
This is a wonderful and complete tool

Mskip, the legend! !!!!!
Sent from my GT-N7100 using Tapatalk 2

Great news. Thank you so much for this. I'm sure it will come in very handy :good:

Released!!
Download link in first post.
Please let me know of any errors or bugs so I can get them fixed ASAP.
Mark.

hi mskip
Thanks for this great tool, i was using it on my GS3 to and was very useful.
I have a little issue I'm not able to flash the "boot-insecure-xxalj1-n7100.tar" after i hit start it doesn't goes on, i waited more than 15 min and nothing, see attached picture:
Any advise?

Can this be used for Note 2 LTE?
Sent from my GT-N7000 using Tapatalk 2

M3xital said:
hi mskip
Thanks for this great tool, i was using it on my GS3 to and was very useful.
I have a little issue I'm not able to flash the "boot-insecure-xxalj1-n7100.tar" after i hit start it doesn't goes on, i waited more than 15 min and nothing, see attached picture:
Any advise?
Click to expand...
Click to collapse
Its a driver problem with Odin.
Try rebooting your phone and pc and use a different usb port. I had that problem in the past and it usually fixed it. Also make sure you dont have samsung kies on your pc as Odin doesnt play nicely with it at all.
Mark.

zard said:
Can this be used for Note 2 LTE?
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
As far as I know the gsm and lte lodels are exactly the same hardware so in theory it should work fine. The only difference would be radios. This is what im hoping so I can keep everything under a single Toolkit. Do you have a link to a Note 2 LTE forum so I can check it?
Mark.

I've used these mskip all in one tools for various Android devices and can thoroughly recommend them. Whilst I have already rooted and modded my 7100 I will be downloading this tool and buying him yet another beer!
Sent from my GT-N7100 using Tapatalk 2

mskip said:
Its a driver problem with Odin.
Try rebooting your phone and pc and use a different usb port. I had that problem in the past and it usually fixed it. Also make sure you dont have samsung kies on your pc as Odin doesnt play nicely with it at all.
Mark.
Click to expand...
Click to collapse
Gonna try to reboot phone and PC and try another USB port. Don't have Kies installed. Will let you know.

hey
Is it a chance for mac version ?
Cheers
P

mskip said:
As far as I know the gsm and lte lodels are exactly the same hardware so in theory it should work fine. The only difference would be radios. This is what im hoping so I can keep everything under a single Toolkit. Do you have a link to a Note 2 LTE forum so I can check it?
Mark.
Click to expand...
Click to collapse
Thanks Mark! That did the trick.
Just another question, after making a Nandroid backup I end up (on my PC) with a 16 mb folder like on a incremental backup but without the blobs folder.

Don't know why not able to download from MediaFire.
Try to get it later again. Thanks anyway.

Ive used it, works like a charm!!!! Thanks so much mate, i wil be making a donation tomorrow.
Sent from my GT-N7100 using Tapatalk 2

mskip said:
As far as I know the gsm and lte lodels are exactly the same hardware so in theory it should work fine. The only difference would be radios. This is what im hoping so I can keep everything under a single Toolkit. Do you have a link to a Note 2 LTE forum so I can check it?
Mark.
Click to expand...
Click to collapse
Sorry, no links as yet. I'm waiting for the Note 2 LTE to launch here (that's the only model to be launched here) this month, thus I had started to read Note 2 threads to get myself ready. I'll pm you if I find any link useful. So far, from the threads in Xda Note 2, there's no good information on LTE.
Sent from my GT-N7000 using Tapatalk 2

[SC-01F/SCL22] Galaxy Note 3 (Japanese) (NTT Docomo) (au KDDI)

[SC-01F] Galaxy Note 3 (Japanese) (NTT Docomo)
Rooting information is in the second post.
Debloating and tweaking information is in the third post.
Available Firmwares:
Android 4.3 (SC01FOMUBMIF) - original firmware
Android 4.3 (SC01FOMUBNA8) - released on 2014/02/12 - patch notes
Android 4.3 (SC01FOMUBNB3) - released on 2014/03/04
Android 4.3 (SC01FOMUBNC3) - released on 2014/03/31
Android 4.4.2 (SC01FOMUBNF6) - released on 2014/07/08 patch notes
Android 4.4.2 (SC01FOMUBNI3) - released on 2014/10/16
Android 5.0 (SC01FOMUGOI4) - released on 2015/10/05 - patch notes
Download firmwares here.
Latest patch notes.
[SCL22] Galaxy Note 3 (Japanese) (au KDDI)
Original and rooted firmwares are available from Dev-Host.
Rooting information is in the second post.
Available Firmwares:
Android 4.3 (SCL22KDUBML1) - original firmware - patch notes
Android 4.3 (SCL22KDUBNB1) - released on 2014/03/04 - patch notes
Android 4.3 (SCL22KDUBND3) - released on 2014/05/15 - patch notes
Android 4.4.2 (SCL22KDU2FNF7) - released on 2014/07/09 - patch notes
Android 5.0 (SCL22KDU2GOH7) - released on 2014/09/01 - patch notes
Download firmwares here.

Rooting Information
This root method shows custom status, but FeliCa works.
Instructions - Device Rooting
There are guides on xda on how to do every step, so please don't ask how to do any particular step in this post.
If you can't get the Download Mode to show Samsung Official, keep reflashing the recovery image and rebooting. It may take a few tries.
If it doesn't work. Try making a tar file with the official recovery.img in. Guide here.
You must install the cwm in the last step using the dd command. You can't use Odin or it will disable NFC again.
Download these things:
The latest KitKat firnware (link in the first post)
The KitKat CWM recovery (attached)
Odin and Samsung Mobile Drivers
SuperSU CWM Installer
7zip
Extract the firmware so you have a tar.md5 file.
If you don't have KitKat yet, do this:
Reboot to download mode
Run Odin press AP and select the firmware tar.md5
Press Start and wait 5 minutes for your firmware to update
Reboot to download mode
Run Odin press AP and select your recovery tar file
Press Start and wait for the reboot.
Copy the SuperSU insstaller zip to your sdcard.
Reboot to recovery mode.
Install SuperSU by selecting the zip.
Reboot.
Install BusyBox Installer.
Install BusyBox. If it doesn't work, you don't have root.
Install Android Terminal Emulator
Extract recovery.img from the firmware tar.md5
Copy to /sdcard
Run this command (you can copy/paste it):
su
dd if=/sdcard/recovery.img of=dev/block/platform/msm_sdcc.1/by-name/recovery​
Reboot the phone, reboot into recovery, then reboot into download mode, check that it says "Current binary: Samsung Official"
Repeat these 3 reboots until it shows official. (NFC will work then)
Extract the recovery.img from your recovery tar file to /sdcard
Run this command (you can copy/paste it):
su
dd if=/sdcard/recovery.img of=dev/block/platform/msm_sdcc.1/by-name/recovery​Reboot to recovery to test that it installed.
You should now be rooted with NFC and custom recovery.
Notes:
To get to download mode: hold power+home+vol down, while the phone reboots, then at the screen with Japanese text, press vol up.
To get to recovery mode: hold power+home+vol up, while the phone rebootsp.
When using Odin, ensure re-partition is unchecked.​
Instructions - TWRP
You can find an alternate recovery in this post.​
Instructions - Install Xposed
Follow the rooting instructions above.
Install the Xposed Installer.
Open Xposed Installer, click Framework, click Install, reboot.
Recommended Modules:
Wanam Xposed​
Instructions - Enable Bluetooth Tethering
Follow the rooting instructions above.
Follow the Xposed Installation instructions above.
Install the Xposed-Bluetooth-Tethering-Enabler module.
Open Xposed Installer, clock Modules, enable Xposed-Bluetooth-Tethering-Enabler, reboot.

Lollipop Deodex Rom
I have created a deodexed Lollipop rom for the SC-01F.
It is pre-rooted, deodexed and Busybox is installed.
You don't have to wipe and you can go back to stock easily.
NFC is working.
Please download all the files in the SC-01F folder.
Guide: (This will trip knox)
Download all the files in the SC-01F folder.
Copy "SC-01F_Part2_System.zip" to your phone's SD card.
Optional: Copy "XposedInstaller_3.0_alpha4.apk" and "xposed-v75-sdk21-arm-arter97-snapdragon_requestConcurrentGC.zip" too if you want Xposed Framework.
Reboot your phone into download mode and connect the USB cable.
Extract "Odin3_v3.10.7.zip" and run the program.
Press the "AP" button and select "SC-01F_Part1.tar"
Reboot into recovery mode.
Flash the "SC-01F_Part2_System.zip" from the SD card.
Optional: Flash "xposed-v75-sdk21-arm-arter97-snapdragon_requestConcurrentGC.zip" if you want Xposed.
Optional: Skip this step if you prefer a custom recovery over NFC.
Reboot to download mode. Flash "SC-01F_Part3_OfficialRecovery.tar"
Repeat this step until download mode shows official binary.
You may have to pull the battery and cable mid flash to trigger the official check.
You won't brick your phone from a bad recovery.img flash.
Done.

I'm a SEA Note 3 SM-N9005 user. Is there any way I can use Japanese language pack from DoCoMo version? I just switched from Xperia Z and noticed the missing language.

what are the supported bandwidth of the SC-02C model?
hmm... according to this
Code:
連続待受時間注意1注意2
（静止時） 3G：約 470時間／LTE：約 410時間／GSM：約 380時間注意6注意7
連続通話時間注意2
（音声通話時） 3G：約 1000分／GSM：約 860分
seems like only Japan frequencies

SimmoF,
Are you upgrading from the Note 2 (SC-02E)?
I still have a year to go on the SC-02E contract, I wonder if NTT Docomo offer an upgrade path?

Fulvian said:
I'm a SEA Note 3 SM-N9005 user. Is there any way I can use Japanese language pack from DoCoMo version? I just switched from Xperia Z and noticed the missing language.
Click to expand...
Click to collapse
I don't think its possible, without a huge amount of effort.
Sent from my L-06C using Tapatalk 4

AllGamer said:
what are the supported bandwidth of the SC-02C model?
hmm... according to this
Code:
連続待受時間注意1注意2
（静止時） 3G：約 470時間／LTE：約 410時間／GSM：約 380時間注意6注意7
連続通話時間注意2
（音声通話時） 3G：約 1000分／GSM：約 860分
seems like only Japan frequencies
Click to expand...
Click to collapse
SC-02C is the Galaxy S2. Did you mean SC-01F?
Docomo uses its own frequencies, but their devices support a few standard frequencies when roaming, but you won't get to full speed.
Sent from my L-06C using Tapatalk 4

Grant Barker said:
SimmoF,
Are you upgrading from the Note 2 (SC-02E)?
I still have a year to go on the SC-02E contract, I wonder if NTT Docomo offer an upgrade path?
Click to expand...
Click to collapse
I'm upgrading from the Galaxy S2.
I wouldn't upgrade, the way Docomo subsidize is by giving you a discount off your bill, every month, for 2 years. This works out to about 44000yen, if you stick the 2 years out.
Also differences aren't that great between the note 2 and 3, and they'll likely filter all the new touchwiz features into the new note 2 firmware.
Sent from my L-06C using Tapatalk 4

SimmoF said:
I'm upgrading from the Galaxy S2.
I wouldn't upgrade, the way Docomo subsidize is by giving you a discount off your bill, every month, for 2 years. This works out to about 44000yen, if you stick the 2 years out.
Also differences aren't that great between the note 2 and 3, and they'll likely filter all the new touchwiz features into the new note 2 firmware.
Sent from my L-06C using Tapatalk 4
Click to expand...
Click to collapse
Yeah. Cheers. I'll be sticking with the Note 2 which I'm very happy with.

I just upgraded from my American Note 2 (Verizon) I was using with a Docomo SIM. I'm loving it so far, but I know it could be much better if I had root (to remove bloatware, change a few things, add a few things, etc). I will post links in here if I confirm root methods and recoveries that work with this device.
Sent from my SC-01F using xda app-developers app

gaxiolafm said:
I just upgraded from my American Note 2 (Verizon) I was using with a Docomo SIM. I'm loving it so far, but I know it could be much better if I had root (to remove bloatware, change a few things, add a few things, etc). I will post links in here if I confirm root methods and recoveries that work with this device.
Sent from my SC-01F using xda app-developers app
Click to expand...
Click to collapse
Great. So the De la Vega method requires the firmware dump to be available for the hacker to make it for our firmware.
So I wouldn't use that until one is available for our device. I will tell him as soon as I can.

SimmoF said:
Note: Do NOT do any updates until we know how to root this thing. Updating may block your chances of rooting.
Edit: I just saw that the Root de la Vega requires a custom version for our AP and CSC, so I will go down to the Docomo shop today and get the details, and request a custom root for us. I will post the details here when done.
Click to expand...
Click to collapse
I will be watching this page constantly waiting for an update! I just picked up my note an hour ago. Thanks for making the effort!

AllGamer said:
hmm... according to this
Code:
連続待受時間注意1注意2
（静止時） 3G：約 470時間／LTE：約 410時間／GSM：約 380時間注意6注意7
連続通話時間注意2
（音声通話時） 3G：約 1000分／GSM：約 860分
seems like only Japan frequencies
Click to expand...
Click to collapse
What you are quoting here are not frequencies, but standby and talk time ratings.
Standby 470 hours on 3G and so on.
Talk time 1000 minutes on 3G and so on.
But it seems that you are right about the fequencies either way.
look here: http://www.samsung.com/jp/consumer/mobilephone/galaxy-note/docomo/SM-N900DZKEDCM-spec

SimmoF said:
Hello everyone,
Some of you may know me for my work in the SC-02C thread.
I am starting this device thread for the users of the Japanese Galaxy Note 3.
I intend to pick up one of these on release day, October 17, so I'll post as much advice and information as I can about rooting/modding.
I will try rooting using the Root de la Vega method, as soon as I get the device.
Note: Do NOT do any updates until we know how to root this thing. Updating may block your chances of rooting.
Edit: I just saw that the Root de la Vega requires a custom version for our AP and CSC, so I will go down to the Docomo shop today and get the details, and request a custom root for us. I will post the details here when done.
You can visit the Official Docomo Page for this 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"
}
Click to expand...
Click to collapse
Just got my Galaxy Note 3 from Docomo Shinyokohama branch last night.
This page is great and thank you to you sir for your technical knowledge and continued support for Samsung device owners here in Japan.
My previous phone was a Galaxy S2 (SC-02c) and I used your previous methods on rooting and now, my phone is still perfectly working
Though I'm still hesitant to tinker with my (20 hour-old) Galaxy Note 3...but I will continue to monitor this thread.
Thanks again in advance!

no one buying the galaxy J? :laugh::laugh:

docomo Note 3 owner now. Sweet root method please....(Onegaishimas)
tried ODIN with CF-Auto-Root-hlte-hltexx-smn9005 end status said PASS but on root check - failed.
Any pointers. Need CHAINFIRE to run.

n9005
I've purchased N9005 version off of hong kong based website. With my galaxy s3 from docomo sim card, i don't get any 3G/4G.... nothing but makeing and receiving phone calls.... i can't even send text!!!! but i can receive one... what is going on!
any help?

soul870518 said:
I've purchased N9005 version off of hong kong based website. With my galaxy s3 from docomo sim card, i don't get any 3G/4G.... nothing but makeing and receiving phone calls.... i can't even send text!!!! but i can receive one... what is going on!
any help?
Click to expand...
Click to collapse
Firstly, you need to set up the APN.
Secondly, DoCoMo has IMEI filtering on sp-mode, so you must be using a DoCoMo branded device.
You will need to switch your data plan from sp-mode to mopera to use your own device.
http://www.mopera.net/service/about/fit.html
Sent from my SC-01F using Tapatalk

I'm new to Japan and my original Note is getting long in the tooth so I'm considering buying a DoCoMo Note, hence I'm curious about bloatware. My understanding is that Japanese operators jam their phones with cute but useless apps, I also believe they only come with support for Japanese and English languages and you are not able to download support for other languages, is that true?
Is there any advantage to getting a DoCoMo device over Au?
Sent from my GT-N5110 using Tapatalk 4

Stock KitKat XXUEND6 Multi-CSC N9005 [GUIDE, ROOT, FIXES, MIRROR - ALL IN ONE PLACE]

Hi
Here is the way i used to flash the firmware, i advise to backup all your data before the flash.
All the files here are provided without any waranty.
Flash at your own risks.
Remember that go back to 4.3 is impossible after this procedure.
You may too void your knox counter when you attempt to root your device...
Click the pictures to open the root of the Mirror and find others goodies.
- Flash The Firmware :
First: Set the reactivation lock setting of your phone to OFF.
Be sure the battery of the phone is full.
- Uninstall Kies if you have it on your computer to avoid conflicts.
- Download PC Odin and Install / update the drivers from Samsung[/URL], that's all you need.
- Best and safe way is to use the original stock usb3 cable and make the job on a portable computer with his own power supply (battery connected).
1 - Download the latest repacked rom in this folder and extract it.
This is pure stock rom with only Multi-CSC OXXEND2 added.
Currently, this rom contain 19 Country Codes:
BGL, CYO, ERO, MSR, ORX, PHE, ROM, SEB, SEE, SIO, TEB, TOP, TPH, TRA, TSR, TWO, XEF, XEH, XSK
As it have a small sized hidden partition there is no need of any PIT File. More safe in my opinion.
If you need another CSC, maybe one of then is yours:
The Multi-CSC VFGENA4, 19 Country Codes:
ATL, CNX, CYV, MOB, MTL, OMN, PRO, SIM, SWC, TCL, TOP, VD2, VDC, VDF, VDH, VDI, VGR, VOD, XFV
As it have a small sized hidden partition there is no need of any PIT File.
The Multi-CSC OLBEND1, 10 Country Codes:
GLB, MM1, SIN, SMA, STH, THL, XME, XSP, XTC, XTE (Asia)
As it have a small sized hidden partition there is no need of any PIT File.
The Multi-CSC OXAEND1, 5 Country Codes:
BTU, DBT, ITV, XEF, XEO
As it have a small sized hidden partition there is no need of any PIT File.
The Multi-CSC OJVENB2, 3 Country Codes:
KSA, XFM, XSI
As it have a small sized hidden partition there is no need of any PIT File.
The CSC ITVEND1, 1 Country Code:
ITV (Italy)
As it have a small sized hidden partition there is no need of any PIT File.
The CSC ZZHENE3, 1 Country Code:
TGY (Hong Kong) - The attached modem ZHUENE2 is here.
As it have a small sized hidden partition there is no need of any PIT File.
The CSC VNZDMJ4, 1 Country Code:
VNZ (New Zealand)
The csc parts are from 4.3 rom but are confirmed working fine.
As it have a small sized hidden partition there is no need of any PIT File.
Three others CSC for specifics operators in France.
As they have a small sized hidden partition there is no need of any PIT File.
Check at the bottom of this post for French thread.
​
Just grab the one you want and put it in CSC in PC ODIN during the same flash process and it first flash the CSC inclued in the firmware, and then overwrite the CSC with the one you added.
2 - Download CF Auto Root for KitKat from Chainfire ODIN version.
Extract the tar.md5 file inside the zip to use with pc odin.
3 - Download the custom recovery PhilZ Touch ODIN version.
I advise to apply this unlock procedure before anything to avoid flash errors:
-> You need Triangle Away from Chainfire with a root acces granted.
Free version is avaible but consider to support the dev for his great job...
a/ Install the app on your phone.
b/ Run Triangle Away and Reset Flash Counter - Follow exactly what the program ask.
At the time to choose the way to reboot after the reset is done in recovery, choose reboot in download mode and then start the flash process immediatly.​
4 - In download mode flash the file that you had previously downloaded N9005-hlte_PDA-xxxxxxx_CSC-xxxxxxx_MODEMS-xxxxxxx_REPACK.tar.md5 with PC Odin in AP.
Do not forget to check/enable the Phone Bootloader Update option in pc odin. (seems working nevertheless without this option ticked)
Leave all others one by default.
Make sure re-partition is NOT ticked.
If you have an error (size error - Your phone may mismatch with this rom, another Samsung lock...) as odin fail at the end of the flash process.
- Shutdown the phone, disconnect the battery, disconnect the phone from your computer and wait a minute, return to download mode.
- Download and flash the file wich contain the CSC that you want.
5 - Auto self-reboot, let the stock recovery do his work completly (the green android man).
If you don't want to install root and a custom recovery, you can stop here.
6 - Go back download mode, flash the PhilZ Touch recovery with pc odin in AP.
7 - Again, in download flash, CF Auto Root with pc odin in AP, let the installation process terminate.
Note: If you were previously rooted, jump this step and download, If not yet done, SuperSu to update by flashing the file in custom recovery..
In this case, re-flash CF Auto Root will loose all your settings of SuperSu...​
8 - Download the fix for the ExtSdCard issue and flash it in custom recovery.
This is a Google security restriction, unnecessary to wait for a fix from Google, just from developpers of apps. Quick way is to apply this fix.
9 - Don't forget BusyBox which should be usefull too.
- About Mobile Odin :
As Mobile Odin seems to be unable to update the bootloader, don't use this one to avoid brick issues when operate with a different rom version than you have.
If you are already on the same firmware, you can use Mobile Odin to re-flash the rom or any other single part:
- Copy the file on your phone.
- Open this file in Mobile Odin.
- Enable EverRoot and Inject Superuser (SuperSu) in case of a system flashing.
- Choose to reboot in Recovery when you flash System and Cache partitions. If not, you may have problems regarding the CSC.
- Start Flashing.
- Do not skip md5 check to gain a little time. (For the life of your phone...)
- Issues :
All theses solutions were tested by me and worked for me, but without any other warranty.
The CSC region code or version are invisibles, the CSC folder is missing in system/.
The stock samsung keyboard crash often once booted.
You need another CSC (warning, you wil loose all your datas and settings, change for another CSC perform a wipe of the phone)
- Check here for the file you need, download and extract it.
-> Apply the Unlock Procedure.
- Flash the file N9005-hlte_CSC_xxxxxxx_RECOVERY-xxxxxxx_REPACK.tar.md5 with pc odin in CSC.
The Modem is not updated.
Download and extract the .tar.md5 modem file.
-> Apply the Unlock Procedure.
- Flash the file that you had previously downloaded N9005-hlte_MODEMS_xxxxxxx_REPACK.tar.md5 with pc odin in CP.
- Reboot normally.
The Bootloader is not updated.
You can check by using this app.
-> Download and extract the .tar.md5 bootloader file.
-> Apply the Unlock Procedure.
- Flash the file N9005-hlte_BL_xxxxxxx_REPACK.tar.md5 with pc odin in BL and check/enable the Phone Bootloader Update option.
- Reboot normally.
Flash player doesn't work anymore.
-> Install Firefox last up to date version and the original latest apk from adobe, nothing else to do.
-> If you prefer Dolphin, download the special version of adobe flash player, more here.
Maybe someone make an xposed module later, it should be a dream...
This fix seems working with this rom (bootloop efs corrupted related).
Not personally affected, just tested the flash.
Download here too.
After all this procedure, you should be fine, upgraded and with all yours datas and settings...
At this state, i just made a wipe of the cache and dalvik cache with phil'z recovery.
- Tune :
- Enable Init.d Support.
- To simply restore the sound at the (de)connection of the charger, you can install this app.
- If you want an imaged battery, you can use RECOVERY - SystemUI N9005 xxxxxxx MOD tkari4-Version by tkari4 based on the guide from parkhyb.
Basically revert to the old 4.3 style for battery and network icons.
{
"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"
}
Just Flash the mod with any custom recovery.
To revert back to the original situation, just flash in custom recovery the file RECOVERY - SystemUI xxxxxxx ODEX STOCK. (STOCK ODEX version)
You can use my blue battery mod. (I reworked a little the graphics for a better scale.) Just extract the .rar archive and install normally the apk Inside, you need too a working Xposed Framework installed.
You can find other Xposed compatibles battery Mods here.
Just reboot once installed.
Many Thanks to tkari4 for keeping alive his mod. :good:
- The repacks i made still works fine.
The rom repacks are made by me with this tool.
Many thanks and credits to all the persons who made this possible.
Notes:
As i do not have the time to download/extract all the roms, if someone needs another CSC repack for him or just to share, please post here with a link for the extracted CSC files only (cache.img.ext4 - hidden.img.ext4) related and with all the details (region, full code name, original rom it come from ... )
To unpack a .tar.md5 file, simply rename it as .tar and extract the content with any good archive software.
I will centralize here.
All others requests in any another form will be ignored, thanks for understanding.
To keep as simply and clear as possible, i will maintain on the Mirror and on thread only the latest updated rom, so if you put elsewhere any link from here, it may be broken in the time, the only ones which would be permanent is the one of the folder and the one of this thread. If you Mirror any file, thanks to keep credits.
Keep a local copy of the downloaded files if you think you will need then later as the content should be updated here.
I maintain the updates only for multi-csc repacks and keep others ones in the mirror, if you need one of theses mono-csc wich is not updated with the latest recovery avaible, simply ask here...
French users, clone thread is here.
Just press thanks if i helped.

Did you search the forum before posting? because if you did, you'd see that there are 500 thread about this already.

polish_pat said:
Did you search the forum before posting? because if you did, you'd see that there are 500 thread about this already.
Click to expand...
Click to collapse
Yes, every day i do.
And i saw no thread that talk about merging two différents roms to make a new one for a specific country, centralize all the majors tools with direct download links for correct versions to avoid confusions between JB & KK, that i often saw, and attached xda threads, and too provide others files needed at the same place for my device (n9005)
Maybe i had read the forum more often than you think...
Sincerly.

Perhaps you should look again
http://forum.xda-developers.com/showthread.php?t=2617932
http://forum.xda-developers.com/showthread.php?t=2631395
http://forum.xda-developers.com/showthread.php?t=2614787
http://forum.xda-developers.com/showthread.php?t=2618633
these are just thread in general section, hit in the past 24 hours, i didnt even get the ones in FAQ nor in dev section, i'm sure i could add about 10 more just by looking at the first page of each. If your thread is not getting hits from anybody, must be for a reason. Just sayin'

I made also my Rom N9005XXUENA7_OXXENA5_XXUENA2_ NoBootloader whit this TOOL from A.S._id Dev. Thanks @A.S._id
Only this files:
boot.img
cache.img.ext4 -->from NA6 (OXX)
hidden.img.ext4 -->from NA6 (OXX)
modem.bin
NON-HLOS.bin
recovery.img
system.img.ext4
Whitout Bootloader (5 files). Work well whit BL XXUENA6 and no Knox appl's.
At first boot, after enter whit my language, I have my csc TPH automatic, alright.
It's very good this [TOOL] TAR.MD5 PACKAGER and easy to make changes whit.
Anyway, thanks by Your work.
Best Regards
Valente
=======================================================================================
polish_pat said:
Did you search the forum before posting?
Click to expand...
Click to collapse
polish_pat said:
Perhaps you should look again
Click to expand...
Click to collapse
Hi Dear @polish_pat
Please, we have a MODERATION to see all Member's work. Not censure this Member. He have rights like You.
Thank You

polish_pat said:
Perhaps you should look again
....................
these are just thread in general section, hit in the past 24 hours, i didnt even get the ones in FAQ nor in dev section, i'm sure i could add about 10 more just by looking at the first page of each. If your thread is not getting hits from anybody, must be for a reason. Just sayin'
Click to expand...
Click to collapse
You made a thread, Others made a thread, i made a thread too, i just wanted to simply share my experience in another form, without any other pretention.
You seems to have a problem about that, not me.
You have time to waste, not me.
I'm not interested to play to the one that has the biggest.
Sincerly

Le [email protected] said:
You made a thread, Others made a thread, i made a thread too, i just wanted to simply share my experience in another form, without any other pretention.
You seems to have a problem about that, not me.
You have time to waste, not me.
I'm not interested to play to the one that has the biggest.
Sincerly
Click to expand...
Click to collapse
i made a thread a month ago, when it was relevant and nobody else did it.

Le [email protected] said:
Hi,
Set the reactivation lock setting of your phone to OFF.:
Click to expand...
Click to collapse
How do you do that on 4.3? (It's not on security setting).
Samsung Galaxy Note 3 T-Mobile USA.

johnvicencio said:
How do you do that on 4.3? (It's not on security setting).
Samsung Galaxy Note 3 T-Mobile USA.
Click to expand...
Click to collapse
I found it easly in security settings.
Maybe because you are on a Galaxy Note 3 T-Mobile USA, i have the HLTE international one.
In any case, check this video at about 2.30 mn

Le [email protected] said:
I found it easly in security settings.
Maybe because you are on a Galaxy Note 3 T-Mobile USA, i have the HLTE international one.
In any case, check this video at about 2.30 mn
Click to expand...
Click to collapse
I see thank you. That doesn't exist on T-Mobile USA at least not on 4.3.

1 - Download the official Poland rom...
2 - Download any NA7 rom...
To this step's We have here a MIRROR on MEGA Host.

Updated the op with a link to the repacked rom and refreshed the guide.
So it is more easy and simple, i think.

Good and informative First Post. Thanks!
Maybe you can do the same with the update that came out today

Pierre118 said:
Good and informative First Post. Thanks!
Maybe you can do the same with the update that came out today
Click to expand...
Click to collapse
Op Updated
No need to repack the whole firmware as all which is needed is Inside.
I am currently upload the rom to mirror it ...
Just made a new repack for the multi-csc.
Just flashed over the NA7 rom by following my guide and all went fine.
No full wipes.
Just made a wipe in dalvik cache and cache in recovery once done.

Great and complete Guide. Useful this ALL IN ONE PLACE. Bookmarked.
Thanks

I QUOTE from my THREAD next useful posts by @letama and @Le [email protected]
After this question to a member that not managed to flash the Bootloader NB3:
ValenteL said:
What Rom have You installed? If You have flashed the XXUENB3 why You are in NA6 BL?
Click to expand...
Click to collapse
letama said:
There is a catch in going from NA6 to NB3, it seems bootloader flashing is ignored now in NA6 BL if your rom status is custom. Solution is triangle away, reflash na6 stock, then make sure that you status is official before flashing NB3.
Click to expand...
Click to collapse
Le [email protected] said:
I was on NA7 BL previously flashed over NA6 BL without any problem.
Followed your trick and flashed my own made NB3 flashable file.
I did not any reflash, just reseted with triangle away.
And it worked, i am now on NB3 BL.
Updated my thread too..
Thanks.
Click to expand...
Click to collapse
letama said:
Thanks, good to know that reflashing pure stock is not mandatory, so the bootloader checks custom status flag only and not the whole firmware. Great, will save time for next one .
Click to expand...
Click to collapse

Updated the OP with a new version of Flash Player i found on xda wich work with Firefox too now.

Hi @Le [email protected]
Only for this time: Do not forget to check/enable the Phone Bootloader Update option in pc odin.
I don't understand why, if we flash a complete Rom whit a new bootloader. We not update the bootloader installed. Why You have this opinion now?
Thank You

Hi ValenteL
I saw (here or on other frenchs forums, no links to provide, forgot then) twice posts of somes personnes who don't have checked the option and have updated their bootloader and others one who don't had bootloader update and got soft brick issues as the rest was updated (JellyBean to Kitkat essentially)
It is usually advised here to check this option.
I not personnally took the risk to bypass this option in pc odin and always used it, so i can not confirm if it is important, effective or not.
There is this option in pc odin, i think too this is not for nothing at all.
For all this reasons, i prefer advise to enable this option when flashing a new rom, and it cost nothing to do.
Personnaly, i think it is important to do when using multi-files roms as the first Poland Leaked KitKat, but the bootloader update must be done automatically when flashing a single file rom which contain Inside all the needed parts.
Of course we can have problems when the knox is trigerred or the status of the rom is to custom, then somes parts seems to be 'jumped' when flashing. I feel this fact is increasing in the time.
When i bought my note 3, Under JellyBean, in France, i updated the rom with the latest version of JellyBean avaible on sam mobile for my country (XEF) and had no issue after the flash.
I got problem when i starded to flashed KitKat from others countries as the XEF one is not yet avaible and as i am a little an impatient flash-addict.
I wonder sometimes if i could have all this problems if were more patient and waiting for an upated version for my country.
At this time i identified three parts wich seems locked (not a secret).
CSC -> Ok, Samsung do not want i flash from another country, new policy from Samsung to lock by geographics sectors.
Modem -> Ok, region lock again.
Bootloader -> Why ? Does samsung want to block customs rom such CM, roots and others sames things? And knox related certainly too.
Samsung want to control and limit me a lot, to make more money with me.
Me, i want to be able to do ALL what i want with the device i bought, this is mine, as i can do with my Note 1.
There is a lot of chances that samsung never see again my money...
Time to bed here.
Sincerly

@ Le [email protected], Mega gives me a error when trying to download BOOTLOADER_N9005XXUENB3_REPACK.rar. Is there something wrong with the file?
---------- Post added at 09:22 PM ---------- Previous post was at 08:36 PM ----------
Pierre118 said:
@ Le [email protected], Mega gives me a error when trying to download BOOTLOADER_N9005XXUENB3_REPACK.rar. Is there something wrong with the file?
Click to expand...
Click to collapse
Never mind, Mega had a problem. Download is ok now.

Here's how I ROOTED Nougat on my S7 Edge G935T

Root Android 7.0 Nougat on Galaxy S7 & S7 Edge devices. YES! Supports all USA Qualcomm variants. T-mobile, AT&T, Verizon and *Sprint (*Note: Some people have reported problems with the Sprint device after root, while others have had success. As always, read the thread for detail and use at your own risk)
** THIS IS NOT FOR THE EXYNOS VERSION OF THE S7! **
A few answers to common questions:
YES - this breaks Samsung Pay and probably Android Pay (you will NOT be able to use Samsung Pay after root)
YES - this process is reversible by several methods, one of which would be simply doing a factory reset and re-flashing the complete Nougat Android 7.0 Firmware files in Odin, More details on this below.
NO - this process does NOT trip the KNOX counter
NO - there is no TWRP or custom recovery for this method of rooting
NO - there is no XPOSED framwork for Android 7.0 currently (as of today's date)
YES - There is a Android 7.0 custom rom! Thanks to @jrkruse https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3572739
Many thanks to the people who released the files! I am only posting the file's in a single easy to find post along with my experience and instructions which may or may not work for you! these instructions may or may not be right. these instruction may or may not be missing crucial steps. USE AND PROCEED AT YOUR OWN RISK! No one is responsible if you damage your device. CERTAINLY NOT ME!
PLEASE GIVE THANKS WHERE ITS DESERVED! Thank you :good:
MANY THANKS TO
@JUSMEJOSE https://forum.xda-developers.com/member.php?u=1113488
@princecomsy https://forum.xda-developers.com/member.php?u=5028474
@jrkruse https://forum.xda-developers.com/member.php?u=1949695
@jrkruse for his awesome job for making a custom flashable Android 7.0 Nougat ROM https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3572739
@Chainfire for creating SuperSU and other great android utilities.
I'm sure there are many others, but I don't know who all created what, so I'm only listing those who I know - if I messed this up, I'm sorry in advance.
ENG (AP) files for S7 and S7E (from this post https://forum.xda-developers.com/showpost.php?p=71271898&postcount=28 )
https://www.androidfilehost.com/?fid=457095661767141717
(This is the ENGINEER boot kernel boot.tar file you'll be flashing in the special modified Odin software from your PC)
*edit: newer method available!* SuperSU 2.79 root.bat file (from this post https://forum.xda-developers.com/showpost.php?p=71281527&postcount=50 )
https://www.androidfilehost.com/?fid=817550096634750763
(This is the command prompt script you'll execute from a CMD prompt from a windows PC that installs the needed files for root access like SuperSU)
**EDIT: @jrkruse on 5/29/17 has created a new ROOT.BAT including SuperSU v2.82, it has been outlined in this post #480 of his custom rom thread. As always, please take a moment to hit the thanks button! Without the work of these amazing dev's we would NOT have root PERIOD! It is free for you, and mean's a lot to everyone involved in bringing these releases to you the public!!!
Here is latest root zip with SuperSU 2.82 (5/29/2017)
Nougat_S7_Root_2_82_All_Carriers_V1.zip
jrkruse said:
This root method will reset your fingerprints and lockscreen security it will also fix fingerprint issue this should help with issues of not recognizing your fingerprint after you root. I had to modify the latest SuperSu to get root to stick on SuperSU 2.82.
Here is a what I did:
The new supolicy from 2.82 Version was causing root not to stick. So I used the supolicy from 2.81 Version. I modded the SuperSu.apk to ingnore the supolicy not being 2.82 Version So you wont get asked to update the SuperSU binaries.
The SU binary is updated to 2.82 and all other files.
If you delete SuperSU apk dont reinstall it from playstore use the one in Above zip
Click to expand...
Click to collapse
**Alternative** Many thanks to active contributor of this thread @Quickvic30 for the info in post #688
https://forum.xda-developers.com/showpost.php?p=71700562&postcount=688
Who offer's another root.bat alternative which gave him better performance. Please check out that post for the file, and click the thanks button.
PLEASE REMEMBER: Results for rooting vary on each and every device. Lag, Performance, Heat - These things vary from device to device. YOUR MILEAGE WILL VARY!
** You will use either the originally posted SuperSU 2.79 root.bat, or the ALTERNATE version posted by Quickvic30 - DO NOT USE BOTH - CHOOSE ONE METHOD OR THE OTHER ** OR TRY EACH INDIVIDUALLY AND SEE WHICH GIVES YOU ACCEPTABLE RESULTS **
VoLTE VMM - IMservice hurricane icon fix thanks to jrkruse post #453
https://www.androidfilehost.com/?fid=457095661767144116
jrkruse said:
Sorry about all the VOLTE Icon problems
If your having FC issues your going to have to copy the original imsservice folder with imsservice.apk and oat folder to system/priv-app before you can flash this fix
This new zip should fix fc problems as no apk is replaced no more just the icons are replaced inside the apk
Volte Icon Fix Is now one zip for all S7 Variants. No more flashing wrong zip and getting FC. The zip only replaces Icons in imsservice apk. This zip will work on odex or deodex roms
S7_VOLTE_ICON_FIX_ALL_VARIANTS.zip
YOU MUST MOUNT SYSTEM IN FLASHFIRE WHEN FLASHING!!!
Click to expand...
Click to collapse
ALTERNATIVE SOLUTION from Post #413: Thanks to @sabresfan post #413
You will need to download and use only the PrinceComsy modified Odin which I got from https://www.androidfilehost.com/?fid=24591023225177749
Kernel Adiutor can be downloaded from Play Store
https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor
Original stock firmware files can be found on these sites or searching XDA
https://www.sammobile.com/firmwares/
http://updato.com/
** Edit: More information about returning to STOCK below on this first post **
**EDIT: Samsung USB driver's direct from Samsung web site http://org.downloadcenter.samsung.c...G_USB_Driver_for_Mobile_Phones_v1.5.45.00.exe
I'm not sure if you need the ADB files installed system wide or not? But you can also download and install the 15 minute ADB drivers. (use google or search XDA)
AGAIN: I did this to my Samsung Galaxy S7 Edge on T-mobile G935T RUNNING ANDROID 7.0 NOUGAT I believe this will work with other USA released carrier variants using Qualcomm chipset (T-mobile, AT&T, Verizon and Sprint)... BUT YOU DO THIS AT YOUR OWN RISK.
EDIT: MAKE SURE YOU ARE ON ANDROID 7.0 NOUGAT - OBVIOUSLY. (Baseband Version: G935TUVU4BQB1 in the case of a G935T S7 Edge) :fingers-crossed:
This process did NOT cause any data or application loss for me. I did this procedure from an OTA upgrade to N from MM.
Obviously, Download all needed files in advance and unzip accordingly.
Put your phone in download mode (Volume Down, Home and Power) then click home again to continue to download mode
Launch the modified ODIN on your PC
Unzip ENG BOOT file and get the boot.tar for your device (in my case it was the S7edge_qualcomm.tar was the file I needed for the S7 Edge) DO NOT UNZIP THE TAR FILE.
Put that .tar file in AP section of ODIN
Connect your phone, you should see a lighted COM port selected in ODIN meaning your good to go.
CLICK START in Odin. You Phone will flash the file quickly and restart.
Let it boot up fully and wait until you can unlock the phone (go to desktop of the phone)
Now open a CMD prompt on the computer and navigate to where you downloaded and unzipped the SuperSU 2.79 earlier
in the CMD prompt type root.bat this will push the required files to the phone and it will be rooted when its completed.
After a few minutes your phone will restart, and you will have SuperSU and root access on Android 7.0 Nougat.
This is how I rooted my SM-G935T Samsung Galaxy S7 Edge on Android 7.0 Nougat. Yes this is a bootloader locked T-mobile branded device.
Please feel free to add or correct anything here in the posts below!
EDIT: You'll want to install Kernel Auditor from the Play store, grant it supersu permission, and set both cpu govenors to ONDEMAND and set apply on boot. (core 1&2 default to performance and core 3&4 default to interactive - set both to ondemand and apply on boot)
EDIT2: You may want to experiment with the CPU governors in Kernel Adiutor (that's actually the correct spelling according to the author). It's been suggested CONSERVATIVE will give you better battery life than ONDEMAND. So you'll want to try the available options and see which results in acceptable balance of performance and battery life for you.
GOOD LUCK! AND THANK YOU!
I HOPE THIS HELPS PEOPLE GET ROOT ON THEIR USA QUALCOMM DEVICES
PLEASE TAKE A MOMENT TO THANK THE PEOPLE WHO BROUGHT THIS INFORMATION TO YOU.
Returning to STOCK Android 7.0 Nougat
You will need to have Odin installed (same modified Odin linked above should work fine)
You can download stock Android 7.0 Nougat firmware from
https://www.sammobile.com/firmwares/
http://updato.com/
For the T-mobile S7 Edge G935T ONLY
File: SM-G935T_G935TUVU4BQB1.zip
Google Drive Link: https://drive.google.com/file/d/0B9QvmNs9dpD-LTdwQUgzejk5ZGM/view
From thread (thanks to it's OP): https://forum.xda-developers.com/tmobile-s7-edge/how-to/odin-stock-nougat-firmware-s7-edge-t3558242
Thanks to @Krog18 for linking to Verizon firmware files in post https://forum.xda-developers.com/showpost.php?p=71383942&postcount=359
G930V QA2 Stock fw: https://www.androidfilehost.com/?fid=529152257862709174
G935V QA2 Stock fw: https://www.androidfilehost.com/?fid=817550096634752305
Thanks to @Quickvic30 for linking to the AT&T firmware files in post https://forum.xda-developers.com/showpost.php?p=71601821&postcount=608
G935A QA6 https://www.androidfilehost.com/?fid=745425885120713605
When you extract the .zip file for your device, you have 2 options for the CSC section. One file will erase all existing data and apps, reverting your phone to a like new state. The other will preserve your currently installed apps and data.
CSC_TMB_G935TTMB4BQB1_CL10376601_QB12449118_REV02_user_low_ship_MULTI_CERT.tar USING THIS FILE WILL ERASE ALL EXISTING DATA ON THE DEVICE
HOME_CSC_TMB_G935TTMB4BQB1_CL10376601_QB12449118_REV02_user_low_ship_MULTI_CERT.tar USING THIS FILE WILL PRESERVE (*NOT ERASE) ANY EXISTING DATA FROM THE DEVICE
Obviously you can only choose 1 of the CSC files. Using the HOME_CSC keeps your existing data, and the other CSC formats your phone.
Thanks to @billa (https://forum.xda-developers.com/member.php?u=293193) for taking taking the time to put these tips together for everyone.
Slightly edited by me
billa said:
Note (and suggestions)
----
Before and after rooting wipe the cache.
For tweak settings to stick, must reboot multiple times.
Security Updates OFF
--------------------
Settings > Lock Screen > Security > Other Security > Security Policy Updates > OFF and Wi-Fi only
Disable (things to disable after root - Use Titanium Backup or Package Disabler Pro for Samsung, both available from the Play Store - Worth the price to buy!)
-------
Samsung DM Phone Interface
Samsung DM Service
SecurityLogAgent
com.sec.android.soagent
com.wssyncmldm
tethering.automation
tethering.provisions
After Eng-Boot (root is complete)
--------------
Install Kernel Auditor, and set both CPU govenors to "OnDemand" and set apply on boot.
Set cores 1&2/3&4 to "OnDemand" and apply on boot.
EDIT: Experiment with governor settings until a balance of power and performance is reached. Kernel Adiutor is available from the Play Store
Performance tweaks
------------------
GovTuner - set to interactive and performance
Kernel Auditor
Kernel Toolkit
LSpeeds
SSD Boost
SHealth fix
-----------
Set ro.config.tima to 0 in build.prop
WiFi passwords fix
------------------
Set ro.securestorage.support to false in build.prop
VOLTE/RCS icons OFF
-------------------
Copy the imsservice.apk from the root zip to
/system/priv-app/imsservice/
and set permissions to -rw-r--r--
Data toggle
-----------
Use SQLite editor and add MobileData to a string in settings.db
Busybox fix
-----------
Install busybox to /system/xbin instead of /su/xbin
Sprint LTE fix
--------------
In Build.Prop change the following:
ro.cdma.default_numeric=310000 to 310120
ro.cdma.default_alpha=Chameleon to Sprint
ro.build.characteristics=Chameleon to Sprint
OR
Go into settings
Click Connections
Click Wi-Fi Calling
Click Cellular Network Preferred
Go back two times and click on Mobile networks
Select Network mode and select 3G/2G (auto connect)
Restart your phone and call 611 just to make sure the call goes through
Hangup and go back to Network mode and switch back to LTE mode
Click to expand...
Click to collapse
As always THANKS to all the users who continue to contribute to this thread, and to all the people involved in bringing you this information so you can ROOT your Samsung Galaxy S7 or Samsung Galaxy S7 Edge on Android 7.0 Nougat!
I will continue to update this first page with relevant links, details and information in an attempt to keep the information easier to find for everyone.
Take a moment to press the THANKS button!

So how's the lag for you compared to the eng boot on marshmallow?

As stated in the OP, what you do at this point is at your own risk. I did it, and worked smoothly. Not sure if you need CMD drivers installed before hand, probably do, but I clicked on the Root.bat, and it did it's thing. So far, so good. Thanks to the above contributors without a doubt. Snappy so far.

nitroevo said:
So how's the lag for you compared to the eng boot on marshmallow?
Click to expand...
Click to collapse
I never did the ENG root on MM, so I can't compare. The lag right now is absolutely there. I'm trying to tweak and reboot as I go. Trying to get it better.
I installed Kernel Auditor and set both of the CPU gov's to ONDEMAND - but it won't stick on reboot, one defaults back to performance and the other (core 3&4) defaults to interactive.

vazquezcmp said:
As stated in the OP, what you do at this point is at your own risk. I did it, and worked smoothly. Not sure if you need CMD drivers installed before hand, probably do, but I clicked on the Root.bat, and it did it's thing. So far, so good. Thanks to the above contributors without a doubt. Snappy so far.
Click to expand...
Click to collapse
I think the SuperSU root file has the needed ADB files, so once you navigate to that folder in CMD (command prompt on the pc for those a little lost), I assume those files are whats used to push the root.bat script to the phone? I think we are both right? but I'm not 100% that's why I mention the ADB drivers, which were already installed on this PC I used. This information was scattered in several threads, I was hoping to put all the links in 1 place so we can maybe get this working smoothly for EVERYBODY.:good:
Since you did it too, and you're getting smooth results what steps did I miss? if any.:fingers-crossed:

I did exactly as you said and worked nicely. The only thing I would add is to already be on Nougat but that might be obvious. I didn't do that earlier, and ended up in a boot loop. Thanks for putting it together. Tomorrow I'll post any lag issues.

vazquezcmp said:
I did exactly as you said and worked nicely. The only thing I would add is to already be on Nougat but that might be obvious. I didn't do that earlier, and ended up in a boot loop. Thanks for putting it together. Tomorrow I'll post any lag issues.
Click to expand...
Click to collapse
Excellent.. Glad it worked.

I just installed it, seems to be running pretty good. Definitely a lot smoother than the MM eng root. I mainly installed because I wanted to get Google assistant lol.
To enable Google assistant you have to use a root explorer app or ADB and change + add a line to the system/build.prop
Change first line to
ro.product.model=Pixel XL
Copy and paste this into system/build.prop
ro.opa.eligible_device=true
Reboot and you have Google assistant!

Quickvic30 said:
I just installed it, seems to be running pretty good. Definitely a lot smoother than the MM eng root. I mainly installed because I wanted to get Google assistant lol.
To enable Google assistant you have to use a root explorer and change + add a line to the system/build.prop
Change first line to
ro.product.model=Pixel XL
Copy and paste this into system/build.prop
ro.opa.eligible_device=true
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
LMAO... That's funny, we should be getting in legit soon... :good:
(but, I'm gonna enable it too! :silly: )

Will this work for Sprint? Thanks

Regnuf said:
Will this work for Sprint? Thanks
Click to expand...
Click to collapse
I believe so... but since I don't have a sprint device to test, I have no idea. (but I think YES)

Thank you sir! Going to be doing this to my S7 standard right now.

Araltd said:
I never did the ENG root on MM, so I can't compare. The lag right now is absolutely there. I'm trying to tweak and reboot as I go. Trying to get it better.
I installed Kernel Auditor and set both of the CPU gov's to ONDEMAND - but it won't stick on reboot, one defaults back to performance and the other (core 3&4) defaults to interactive.
Click to expand...
Click to collapse
to make it stick on reboot i think there should be a setting there that says apply on boot

Have you tried flashing the fixes from the popular root thread? Or is it not needed?

Araltd said:
VoLTE VMM icon fix (from this post https://forum.xda-developers.com/showpost.php?p=71281527&postcount=50 )
https://www.androidfilehost.com/?fid=673368273298935963
You will need to download the PrinceComsy odin which I got from https://www.androidfilehost.com/?fid=24591023225177749
Click to expand...
Click to collapse
Give this a try and see if it gets rid of that stupid icon
TMO_VOLTE_ICON_FIX.zip

jrkruse said:
Give this a try and see if it gets rid of that stupid icon
TMO_VOLTE_ICON_FIX.zip
Click to expand...
Click to collapse
Hey thanks for coming over here...
As I mentioned, I don't care about the big hurricane looking icon, but the com.sec.vmimservice icon notification (looks like a red face) pops up multiple times in my status bar whenever there is texting activity. Send or receive. That's what I want to get rid of.
Edit: here's the notification pulled down so you can see.. I have that little red icon in my status bar several times right now... I am using Android messages, and I use Tmobile digits on my other phone (note 4) just fyi... Not sure if everybody is seeing that or if it's unique to either Android messages (formerly Google messenger) or digits service by Tmobile?
{
"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"
}

nitroevo said:
to make it stick on reboot i think there should be a setting there that says apply on boot
Click to expand...
Click to collapse
Somewhere between reboots (of which there have been many tonight) the setting finally stuck. I also set kernel auditor (adiutor) to set the settings immediately on reboot with no delays.
To me, there is still significant lagging, even with on demand Governor set. I read somewhere about setting the min/max also, those values are always fluctuating in the kernel adiutor program, I'm not sure how to properly set those.... But I also tried kernel tool and had similar results. Just fyi.

cjlopez213 said:
Have you tried flashing the fixes from the popular root thread? Or is it not needed?
Click to expand...
Click to collapse
Honestly I don't think most of those fixes are still relevant even for MM 6.0.1, so I doubt any flash able version mod would be suitable for N 7.0 [emoji6]
So far, what I've done is wiping cache in recovery (volume up, home and power)
Set the governors to on demand... Beyond that we will need some experts to chime in with suggestions, tips and advice.

cjlopez213 said:
Have you tried flashing the fixes from the popular root thread? Or is it not needed?
Click to expand...
Click to collapse
They are installed when you root
---------- Post added at 02:20 AM ---------- Previous post was at 02:19 AM ----------
Araltd said:
Honestly I don't think most of those fixes are still relevant even for MM 6.0.1, so I doubt any flash able version mod would be suitable for N 7.0 [emoji6]
So far, what I've done is wiping cache in recovery (volume up, home and power)
Set the governors to on demand... Beyond that we will need some experts to chime in with suggestions, tips and advice.
Click to expand...
Click to collapse
If you set govenors to conservative you will get way better battery life.

jrkruse said:
They are installed when you root
---------- Post added at 02:20 AM ---------- Previous post was at 02:19 AM ----------
If you set govenors to conservative you will get way better battery life.
Click to expand...
Click to collapse
Please refresh, I posted a picture of the imservice notification I'm getting. Thanks!

[SOLVED] Thinking of upgrading my Galaxy Tab S T800 - double check help please

Hello all,
I am thinking of upgrading my T800 to android 7 or 8 and need to start somewhere.
The main reason so many apps are either v7 or 8 min recently and I still use this tablet surprisingly lol
I have read a few threads to help me but I keep seeing that old ones I need to be careful and some say ok and some say no - so I need help.
I checked this thread to start rooting my device:
[Root][Port] Cf-Autoroot T800 [Tab S 10.5 ]
CF-AUTO Root By Chainfire Ported To the Tab S 10.5 By:@BeansTown106 First off, Huge Thanks to Chainfire for coming up with AutoRoot & for his SuperSU App Warning: I cannot be held responsible...
forum.xda-developers.com
Now - with my research I need:
Odin 3.13.1 the latest
Download Cf-Autoroot T800 from the link above
load the file to AP Odin and install to tablet
Then do the same again with TWRP with the latest file I found called: twrp-3.5.0_9-0-chagallwifi.img.tar
Reboot and should be rooted with TWRP as far as I have read
Now - do these files still work and is it ok for me to use the above to start? Am I missing anything? I guess SuperUser gets install with the rooting?
I am on Android 6.0.1 currently.
Then I need to choose an Android 7 or 8 or 9 or 10 - but seems only 7 OFFICIAL I can see - would want as close to stock as possible and the most stable I guess - can anyone recommend which ROM to flash, please?
Thank you in advance
Ben

bumping an old question - I guess may be difficult to get an answer for such an old device.
if anyone can help pls reply or PM me.

you are planning to install custom rom right? most custom rom have built in root included just follow the custom rom installation and your pretty much good to go
LineageOS seems the most popular and active custom rom for your device

No you shouldnt use cf auto root as it might brick your device reportedly.
Use magisk v21 instead (again v22 is bricking devices).

ineedroot69 said:
you are planning to install custom rom right? most custom rom have built in root included just follow the custom rom installation and your pretty much good to go
LineageOS seems the most popular and active custom rom for your device
Click to expand...
Click to collapse
Thank you - will follow them instead.

jjgvv said:
No you shouldnt use cf auto root as it might brick your device reportedly.
Use magisk v21 instead (again v22 is bricking devices).
Click to expand...
Click to collapse
Wow - thank you - glad I asked and was patient lol

SUCCESS Went through set up and seems working fine first impressions.
How I did it in 2021:
I have a Samsung Tab S - SM-T800 - on android 6.0.1 not rooted
1: These are the files that I have used
Odin3_v3.14.1
lineage-14.1-20210122-UNOFFICIAL-chagallwifi.zip
addonsu-14.1-arm-signed.zip
open_gapps-arm-7.1-nano-20210224.zip
twrp-3.5.0_9-0-chagallwifi.img.tar
2: I installed the Samsung USB drivers - and checked that I could transfer files to and from the PC - in this step I added the files into my external SD Card:
lineage-14.1-20210122-UNOFFICIAL-chagallwifi
addonsu-14.1-arm-signed
open_gapps-arm-7.1-nano-20210224
3: Once they were copied over - I unplugged the tablet and powered it off.
4: I opened ODIN on my win10 machine
5: I booted the tablet into download mode - by pressing the HOME-VOL:downOWER at the same time
6: I added the twrp-3.5.0_9-0-chagallwifi.img.tar file into the AP of Odin. Go to options, and deselect "auto-reboot"
7: Pressed START in Odin and waited for the Green PASS! to show.
8: Unplugged cable from the tablet
9: This is important -
You need to power off and power on back to the recovery you just flashed - if you miss this you may have to start again from the top here.
When done press HOME-VOL:downOWER for about 5 to 8 seconds - the screen will change and as soon as it changes let go and repress HOME-VOL:upOWER at the same time - the only change is the volume to UP. This will then boot to TWRP.
10: when TWRP first comes on - just swipe right
11: On the home screen of TWRP - I decided to make a backup - so I went to back up - and backed up to my SD Card. This takes a long time
12: when this was done - I went WIPE - and selected Format Data
13: when done go back and select INSTALL - here choose:
lineage-14.1-20210122-UNOFFICIAL-chagallwifi - then add zip and choose
addonsu-14.1-arm-signed - then add zip and choose
open_gapps-arm-7.1-nano-20210224
14: Start flashing. this is quite quick except for the Gapps.
15: When done - you will be asked to format cache and davlik partitions click it and when done - REBOOT
16: Wait a while, you should see the Samsung Logo - then the blue arc of LineageOS and go through the set up. The first boot can take 4 to 6 minutes - in my case, it was about 6 minutes.
17: Optional ROOT
Go to Settings > About Tablet > tap the build number seven times to enable developer options
Then go back and go to > Developer Options > Root Access. and choose what you want - I selected Apps Only.
I hope this helps anyone looking to do the same and wanted to say THANK YOU TO ALL WHO HAS HELPED ME.
Done.

Hi, I'm thinking of doing the same (for security reasons since updates are no longer provided for Android v6).
What version of Android did you end up with?
And have you had any issues since your upgrade?
Thanks

tuvinor said:
Hi, I'm thinking of doing the same (for security reasons since updates are no longer provided for Android v6).
What version of Android did you end up with?
And have you had any issues since your upgrade?
Thanks
Click to expand...
Click to collapse
Ended with Android 7 - and works nice ever since double-check the links though as its been a while now

also check this forum and many replied
[ROM][7.1.2][UNOFFICIAL] LineageOS 14.1 - SM-T800
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1.2 (Nougat), which is designed to increase performance and reliability over stock Android for your device. #include /* * Your...
forum.xda-developers.com

_XSnPX_ said:
Ended with Android 7 - and works nice ever since double-check the links though as its been a while now
Click to expand...
Click to collapse
And do you get ongoing automatic updates for android 7 or does that need you to go through the manual upgrade process again?
(sorry, newb questions)
Thanks

tuvinor said:
And do you get ongoing automatic updates for android 7 or does that need you to go through the manual upgrade process again?
(sorry, newb questions)
Thanks
Click to expand...
Click to collapse
That is ok,
Once you are in Lineage - you will get updates as they release them - and just upgrade from the app - you will have to go to TWRP to upgrade after you download the update but it is an easy and quick process
ill try get some screen prints now for you

The last updates

_XSnPX_ said:
The last updates
Click to expand...
Click to collapse
Perfect, thank you