galaxy tab pro 8.4 rom

Samsung Galaxy Tab Pro 8.4 bootloader should be unlocked. A PC/Laptop and a USB cable are required for this process. Make sure to take a Full Backup of Device Data (No Root). Charge your device battery to full. Download All Required Files: Download SuperSU Zip - For root using SuperSU Download Magisk Zip - For root using Magisk How to install 4.4.2 KitKat firmware on Samsung Galaxy Tab Pro 8.4. Run the Odin3 v3.07.exe from the extracted Odin program on the PC. A Odin program window will appear. Now turn off the device and wait at least 5 seconds. Press and hold Volume Down + Home + Power buttons together until a Warning! message gets appeared over the screen. Galaxy Tab Pro 8.4 Battery . $14.99. Buy. Galaxy Tab Pro 8.4 Rear Panel . $9.99. Buy. Step 1 Battery . Begin by separating the back panel from the screen glass assembly using the plastic opening tool. Insert the plastic opening tool between the edge of the glass screen and the metal frame around the device. Buy 4 PCs/Lot 8" Screen Protector For Samsung Galaxy TAB Active 2 T395 Tablet,Protective Film For SM-T395 SM T395 Tablet And 4 Tools for 10.77 usd in the online store Shenzhen Sara Electronic Co.,Ltd. Compare specifications, photos and reviews of 2 offers from other stores at a price of 10.66 usd. (Tổng hợp) Rom stock / full cho Samsung Galaxy Tab PRO 8.4 (SM-T320 / T321 / T325) DOWNLOAD: 1. Samsung Galaxy Galaxy Tab PRO 8.4 (SM-T320) T320ZSS1BQC1_T320OZS1BQC1_TGY_4.4.2.zip / AFH / OneDrive / GDrive2 2. Samsung Galaxy Tab PRO 8.4 (SM-T320NU) T320NUUEU1AOB8_T320NUXAR1AOB8_XAR_4.4.2.zip / AFH / OneDrive / GDrive2 3. Wie Kann Ich Mehr Jungs Kennenlernen. Home » Stock ROM » Samsung Galaxy Tab Pro 3G SM-T321 Stock ROMAre you looking for the Stock ROM of your device Samsung Galaxy Tab Pro 3G SM-T321? If yes your answer, you are in the right page. We have given the direct link to download Samsung Galaxy Tab Pro 3G SM-T321 stock ROM. Download Samsung Galaxy Tab Pro 3G SM-T321 Stock ROM from here, flash it in your device and enjoy the native Android experience again. The download file contains the USB driver, flash tool and the Stock ROM file. Stock ROM File Name Stock ROM File Size 1 GB Android OS Version Download Now Stock ROM File Name Stock ROM File Size 1 GB Android OS Version Download Now Stock ROM File Name Stock ROM File Size 1 GB Android OS Version Download Now Stock ROM File Name Stock ROM File Size 1 GB Android OS Version Download Now How To Flash Stock ROM On Samsung Galaxy Tab Pro 3G SM-T321 Step 1 To get started, download Samsung Galaxy Tab Pro 3G SM-T321 USB driver and install it in your computer. Once done, download the stock ROM of your device and extract the zip file to get the ". file as shown below. Step 2 Next, switch off your smartphone. Once done, boot it into the "Download" mode by pressing and holding the Volume Down, Power and Home buttons simultaneously. Now your Samsung device will vibrate. Once you have felt it, keep pressing the Volume Down and Home buttons leave the Power button and your device will boot into the Download mode. Step 3 Now you will see a "Warning" message as shown below. Just press the "Volume Up" key to continue. Step 4 Next, download Odin and extract it to a folder in your computer. Once done, click on " to launch its window. Step 5 Now connect your smartphone to the computer using the original USB data cable. If you have installed the USB drivers of your device properly in the Windows computer, Odin will automatically identify your device and will show a "Added" message in the "Log" section. Step 6 Next, click on the "AP" button and select the ". file from Step 1. Step 7 Once the Samsung stock ROM file is added, click on "Start" button in "Odin" to launch the flashing process. Step 8 Don't do anything during the flashing process. Once it gets completed, you will see the green "PASS" message as shown in the screenshot below. Step 9 Now unplug your device from the computer. But when you try to boot your device normally, it will get into a boot loop. To fix this error, switch off your smartphone and boot into the "Recovery" mode by pressing and holding the Volume Up, Power and Home buttons simultaneously. Step 10 Once your device boots into the recovery mode, click on "Wipe data/factory reset". Once done, click on "Reboot System Now" as shown in the screenshot below. That's it. Now you have successfully flashed Stock ROM on your Samsung Galaxy Tab Pro 3G SM-T321 Android device. If you encounter any issues while following this tutorial, do let me know via comments. Rajarajacholan Kulothungan is a tech nerd and an Android enthusiast working for from 2020. He specializes in testing new stock ROMs for Android devices, and he shares his experiences Interactions Quick Info Special boot modes Recovery Hold Volume Up while booting. Download Hold Volume Down while booting. Source code Galaxy Tab Pro Specifications Codename mondrianwifi Also known as sm-t320 Vendor Samsung Type tablet Platform Qualcomm Snapdragon 800 CPU GHz quad-core Snapdragon 800 Krait 400 GPU Adreno 330 RAM 2GB Weight 331 g oz Dimensions 219 x x mm x x in Screen size 213 mm in Resolution 1600×2560 Screen density 359ppi Internal storage 16GB SD Card up to 128GB Bluetooth Wi-Fi Dual-Band Wi-Fi a/b/g/n/ac Main camera 8MP, flash LED Secondary camera 2MP CM supported 11, 12, 13 How to Install CyanogenMod on the Samsung Galaxy Tab Pro mondrianwifi Note DISCLAIMER Modifying or replacing your device’s software may void your device’s warranty, lead to data loss, hair loss, financial loss, privacy loss, security breaches, or other damage, and therefore must be done entirely at your own risk. No one affiliated with the CyanogenMod project is responsible for your actions. Good luck. Installing a custom recovery Samsung devices come with a unique boot mode called Download Mode which is very similar to Fastboot Mode on some devices with unlocked bootloaders. Heimdall is a cross-platform, open source tool for interfacing with Download Mode on Samsung devices. The preferred method of installing a custom recovery is through this boot mode. Rooting the stock firmware is neither recommended nor necessary. Download and install the Heimdall Suite Windows Extract the Heimdall suite and take note of the directory holding You can verify Heimdall is working by opening a command prompt in this directory and typing heimdall version. If you receive an error, be sure that you have the Microsoft Visual C++ 2012 Redistributable Package x86/32bit installed on your computer. Linux Pick the appropriate installation package based on your distribution. The -frontend packages are not required for this guide. After installation, heimdall should be available from the terminal; type heimdall version to verify installation succeeded. Mac Install the dmg package. After installation, heimdall should be available from the terminal; type heimdall version to verify installation succeeded. Building from source The source code for the Heimdall Suite is available on Github. For more details about how to compile the Heimdall Suite, please refer to the README file on Github under the relevant operating system directory. You can also refer to the Install and compile Heimdall instructions on this wiki. Download recovery — you can directly download a recovery image using the link below, or visit TWRP site to check for the latest version of recovery for your device if your device can be found there. For general info about recoveries click here. Recovery Download md5 52669f4642896fde99313251163cedde Power off the Galaxy Tab Pro and connect the USB adapter to the computer but not to the Galaxy Tab Pro yet. Boot the Galaxy Tab Pro into download mode. Hold Volume Down while booting. Accept the disclaimer on the device. Then, insert the USB cable into the device. Windows only driver installation – Skip this step if you are using Linux or Mac A more complete set of the following instructions can be found in the Zadig User Guide. Run from the Drivers folder of the Heimdall Suite. Choose Options » List All Devices from the menu. Select Samsung USB Composite Device or MSM8x60 or Gadget Serial or Device Name from the drop down menu. If nothing relevant appears, try uninstalling any Samsung related Windows software, like Samsung Windows drivers and/or Kies. Click Replace Driver having selecting “Install Driver” from the drop down list built into the button. If you are prompted with a warning that the installer is unable to verify the publisher of the driver, select Install this driver anyway. You may receive two more prompts about security. Select the options that allow you to carry on. At this point, familiarize yourself with the Flashing with heimdall notes below so that you are prepared for any strange behaviour if it occurs. On the computer, open a terminal or Command Prompt on Windows in the directory where the recovery image is located and type heimdall flash -RECOVERY -no-reboot Tip The file may not be named identically to what’s in this command. If the file is wrapped in a zip or tar file, extract the file first, because heimdall isn’t going to do it for you. A blue transfer bar will appear on the device showing the recovery being transferred. Unplug the USB cable from your device. NOTE Be sure to reboot into recovery immediately after having installed the custom recovery. Otherwise the custom recovery will be overwritten and the device will reboot appearing as though your custom recovery failed to install. Manually reboot the phone into recovery mode by performing the following. Hold Volume Up while booting. The Galaxy Tab Pro now has a custom recovery installed. Continue to the next section. Note Flashing with heimdall In Windows 7 UAC User Account Control may need switching off. Once Heimdall is finished it can be re-enabled. Protocol initialization can fail if the device is connected via a USB hub – connect the USB cable directly to the PC It may be necessary to run the heimdall flash command as root in Linux or Mac OS X sudo heimdall flash [...]. Typical symptoms of this are a blue bar doesn’t show up after the process has finished Failed to confirm end of file transfer sequence! It may be necessary to capitalize the name of the partition on some devices. Try -KERNEL instead of -kernel and/or -recovery instead of -RECOVERY. If on Linux 64bit you get “unable to execute ./heimdall No such file or directory”, try the 32bit version and make sure to run it with sudo reference. On Mac OS X you may see this message “ERROR Claiming interface failed!”. If so, you need to disable the default USB drivers with the following commandssudo kextunload -b kextunload -b kextunload -b you have installed Samsung Kies, you may further need to unload those USB drivers with the following commandssudo kextunload -b kextunload -b kextunload -b Using Heimdall version the latest version available for download on the Glass Echidna website you may see this message or one similar to itError Failed to confirm end of PIT file transfer!If you experience this error, follow the instructions for compiling Heimdall from source to get the latest version on GitHub with the issue patched. Helpful Tip The stock ROM may overwrite your custom recovery on boot. To prevent this, boot immediately into recovery after leaving Download Mode instead of letting the ROM boot up normally. If your recovery is overwritten, simply redo the steps you followed above and catch it before it boots next time. Note for upgrades from gingerbread to jellybean remember the recovery is changed. This means once you install do NOT restore to old-gingerbread-stock ROM from cwm-recovery. To upgrade from stock/CM7/CM9/ to you must first boot into recovery and wipe data, cache, and dalvik cache factory reset. Due to the new partition layout in failing to perform these steps will result in a bootloop. See here for details; more about repartitioning here. If you missed this step before installing, boot to recovery and factory reset, then reinstall Some users have reported connection errors if the device is connected to a USB hub. If you experience such errors it is recommended that you try connecting your device to a USB port on the motherboard. Antivirus software may prevent Heimdall from connecting properly. Disable your antivirus before proceeding. When Heimdall fails to connect, the Download mode may get stuck, making all further attempts fail too. To retry, you may need to restart the Download mode turn off the phone by holding Power for 5-10 seconds or by pulling out the battery, then boot into Download mode and run Heimdall again. If Heimdall fails to connect errors related to initializing the protocol, or transferring data if you just installed the driver, try rebooting your computer and trying again. if you still have troubles after reboot, in Zadig try installing the libusbK driver rather than the WinUSB driver. Installing CyanogenMod from recovery Make sure your computer has working adb. Download the CyanogenMod build package for your device that you’d like to install to your computer. Optional Download 3rd party applications packages, like Google Apps which are necessary to download apps from Google Play. Place the CyanogenMod .zip package, as well as any optional .zip packages, on the root of /sdcard Using adb adb push /sdcard/ Note You can copy the .zip packages to your device using any method you are familiar with. The adb method is used here because it is universal across all devices and works in both Android and recovery mode. If you are in recovery mode, you may need to ensure /sdcard sometimes called Internal Storage is mounted by checking its status in the Mounts menu. If you have booted regularly, USB debugging must be enabled. If you are not already in recovery, boot to recovery mode now. Hold Volume Up while booting. In Team Win Recovery Project, select menu choices by tapping on the appropriately labelled button. Optional Recommended Select the Backup button to create a backup. Select Wipe and then Factory Reset. Select Install. Navigate to /sdcard and select the CyanogenMod .zip package. Follow the on-screen notices to install the package. Optional Install any additional packages you wish using the same method if you are installing multiple packages, install CyanogenMod first and then install any subsequent packages on top of it. Once installation has finished, return to the main menu and select Reboot, then System. The device will now boot into CyanogenMod. How To Build CyanogenMod For Samsung Galaxy Tab Pro mondrianwifi Contents 1 Introduction What you’ll need 2 Build CyanogenMod and CyanogenMod Recovery Prepare the Build Environment Install the SDK Install the Build Packages Create the directories Install the repo command Put the ~/bin directory in your path of execution Initialize the CyanogenMod source repository Download the source code Get prebuilt apps CM11 and below Prepare the device-specific code Extract proprietary blobs Turn on caching to speed up build Start the build If the build breaks… 3 Install the build Install CyanogenMod Success! So….what’s next? Introduction These instructions will hopefully assist you to start with a stock Galaxy Tab Pro unlock the bootloader if necessary, and then download the required tools as well as the very latest source code for CyanogenMod based on Google’s Android operating system. Using these, you can build both CyanogenMod and CyanogenMod Recovery image from source code, and then install them both to your device. It is difficult to say how much experience is necessary to follow these instructions. While this guide is certainly not for the very very very uninitiated, these steps shouldn’t require a PhD in software development either. Some readers will have no difficulty and breeze through the steps easily. Others may struggle over the most basic operation. Because people’s experiences, backgrounds, and intuitions differ, it may be a good idea to read through just to ascertain whether you feel comfortable or are getting over your head. Remember, you assume all risk of trying this, but you will reap the rewards! It’s pretty satisfying to boot into a fresh operating system you baked at home And once you’re an Android-building ninja, there will be no more need to wait for “nightly” builds from anyone. You will have at your fingertips the skills to build a full operating system from code to a running device, whenever you want. Where you go from there– maybe you’ll add a feature, fix a bug, add a translation, or use what you’ve learned to build a new app or port to a new device– or maybe you’ll never build again– it’s all really up to you. What you’ll need A Galaxy Tab Pro A relatively recent computer Linux, OS X, or Windows with a reasonable amount of RAM and about 100 GB of free storage more if you enable ccache or build for multiple devices. The less RAM you have, the longer the build will take aim for 8 GB or more. Using SSDs results in considerably faster build times than traditional hard drives. A USB cable compatible with the Galaxy Tab Pro typically micro USB, but older devices may use mini USB or have a proprietary cable A decent internet connection & reliable electricity Some familiarity with basic Android operation and terminology. It would help if you’ve installed custom roms on other devices and are familiar with recovery. It may also be useful to know some basic command line concepts such as cd for “change directory”, the concept of directory hierarchies, that in Linux they are separated by /, etc. If you are not accustomed to using Linux– this is an excellent chance to learn. It’s free– just download and run a virtual machine VM such as Virtualbox, then install a Linux distribution such as Ubuntu AOSP vets Ubuntu as well. Any recent 64-bit version should work great, but the latest is recommended. Note You want to use a 64-bit version of Linux. A 32-bit Linux environment will only work if you are building CyanogenMod 6 and older. For CyanogenMod if you encounter issues with 64bit host binaries, you can set BUILD_HOST_32bit=1 in your environment. This is generally not needed, though, especially with CyanogenMod and newer. Using a VM allows Linux to run as a guest inside your host computer– a computer in a computer, if you will. If you hate Linux for whatever reason, you can always just uninstall and delete the whole thing. There are plenty of places to find instructions for setting up Virtualbox with Ubuntu, so I’ll leave it to you to do that. So let’s begin! Build CyanogenMod and CyanogenMod Recovery Prepare the Build Environment Note You only need to do these steps the first time you build. If you previously prepared your build environment and have downloaded the CyanogenMod source code for another device, skip to Prepare the device-specific code. Install the SDK If you have not previously installed adb and fastboot, install the Android SDK. “SDK” stands for Software Developer Kit, and it includes useful tools that you can use to flash software, look at the system logs in real time, grab screenshots, and more– all from your computer. Helpful Tip While the SDK contains lots of different things– the two tools you are most interested in for building Android are adb and fastboot, located in the /platform-tools directory. Install the Build Packages Several “build packages” are needed to build CyanogenMod. You can install these using the package manager of your choice. Helpful Tip A package manager in Linux is a system used to install or remove software usually originating from the Internet on your computer. With Ubuntu, you can use the Ubuntu Software Center. Even better, you may also use the apt-get install command directly in the Terminal. Learn more about the apt packaging tool system from Wikipedia. For both 32-bit & 64-bit systems, you’ll need bc bison build-essential curl flex git gnupg gperf libesd0-dev liblz4-tool libncurses5-dev libxml2 libxml2-utils lzop maven openjdk-7-jdk pngcrush schedtool squashfs-tools xsltproc zip zlib1g-dev In addition to the above, for 64-bit systems, get these g++-multilib gcc-multilib lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev For Ubuntu wily and newer, substitute lib32readline-gplv2-dev → lib32readline6-dev For Ubuntu xenial and newer, substitute additionally see java notes below → openjdk-7-jdk → openjdk-8-jdk Java versions Different versions of CyanogenMod require different versions of the JDK Java Development Kit CyanogenMod 7 – 9 Sun/Oracle Java SE CyanogenMod Sun/Oracle Java SE or CyanogenMod – Sun/Oracle Java SE or OpenJDK works fine, but the build system will display a warning CyanogenMod – OpenJDK see note about OpenJDK below CyanogenMod OpenJDK Ubuntu Xenial Xerus or newer and OpenJDK Since OpenJDK was removed from the official Ubuntu repositories, you have a couple options Obtain OpenJDK from the openjdk-r PPA Enable experimental OpenJDK support in CyanogenMod not available in earlier version. To enable OpenJDK support, add this line to your $HOME/.bashrc file export EXPERIMENTAL_USE_JAVA8=true. Also see which lists needed packages. Create the directories You will need to set up some directories in your build environment. To create them $ mkdir -p ~/bin $ mkdir -p ~/android/system Install the repo command Enter the following to download the “repo” binary and make it executable runnable $ curl > ~/bin/repo $ chmod a+x ~/bin/repo Put the ~/bin directory in your path of execution In recent versions of Ubuntu, ~/bin should already be in your PATH. You can check this by opening ~/.profile with a text editor and verifying the following code exists add it if it is missing set PATH so it includes user's private bin if it exists if [ -d "$HOME/bin" ] ; then PATH="$HOME/bin$PATH" fi Initialize the CyanogenMod source repository Enter the following to initialize the repository Note Make sure the cm branch entered here is the one you wish to build and is supported on your device. $ cd ~/android/system/ $ repo init -u -b Download the source code To start the download of all the source code to your computer $ repo sync The CM manifests include a sensible default configuration for repo, which we strongly suggest you use don’t add any options to sync. For reference, our default values are -j 4 and -c. The -j 4 part means that there will be four simultaneous threads/connections. If you experience problems syncing, you can lower this to -j 3 or -j 2. -c will ask repo to pull in only the current branch, instead of the entire CM history. Prepare to wait a long time while the source code downloads. Helpful Tip The repo sync command is used to update the latest source code from CyanogenMod and Google. Remember it, as you can do it every few days to keep your code base fresh and up-to-date. Get prebuilt apps CM11 and below Next, $ cd ~/android/system/vendor/cm then enter $ ./get-prebuilts You won’t see any confirmation- just another prompt. But this should cause some prebuilt apps to be loaded and installed into the source code. Once completed, this does not need to be done again. Prepare the device-specific code Helpful Tip – Errors during breakfast Different maintainers setup their device inheritance rules differently. Some require a vendor directory to be populated before breakfast will even succeed. If you receive an error here about vendor makefiles, then jump down to the next section Extract proprietary blobs. The first portion of breakfast should have succeeded at pulling in the device tree and the extract blobs script should be available. After completing that section, you can rerun breakfast mondrianwifi After the source downloads, ensure you are in the root of the source code cd ~/android/system, then type $ source build/ $ breakfast mondrianwifi This will download the device specific configuration and kernel source for your device. An alternative to using the breakfast command is to build your own local manifest. To do this, you will need to locate your device on CyanogenMod’s GitHub and list all of the repositories defined in in your local manifest. Helpful Tip If you want to know more about what source build/ does or simply want to know more about the breakfast, brunch and lunch commands, you can head over to the Envsetup help page. Helpful Tip Instead of typing cd ~/android/system every time you want to return back to the root of the source code, here’s a short command that will do it for you croot. To use this command, you must first run source build/ from ~/android/system. Now ensure that your Galaxy Tab Pro is connected to your computer via the USB cable and that you are in the ~/android/system/device/samsung/mondrianwifi directory you can cd ~/android/system/device/samsung/mondrianwifi if necessary. Then run the script $ ./ You should see the proprietary files aka “blobs” get pulled from the device and moved to the ~/android/system/vendor/samsung directory. If you see errors about adb being unable to pull the files, adb may not be in the path of execution. If this is the case, see the adb page for suggestions for dealing with “command not found” errors. Note Your device should already be running a build of CyanogenMod for the branch you wish to build for the script to function properly. Note It’s important that these proprietary files are extracted to the ~/android/system/vendor/samsung directory by using the script. Makefiles are generated at the same time to make sure the blobs are eventually copied to the device. Without these blobs, CyanogenMod may build without error, but you’ll be missing important functionality, such as graphics libraries that enable you to see anything! Turn on caching to speed up build You can speed up subsequent builds by adding export USE_CCACHE=1 to your ~/.bashrc file what’s a .bashrc file?. Then, specify the amount of disk space to dedicate to ccache by typing this from the top of your Android tree prebuilts/misc/linux-x86/ccache/ccache -M 50G where 50G corresponds to 50GB of cache. This only needs to be run once and the setting will be remembered. Anywhere in the range of 25GB to 100GB will result in very noticeably increased build speeds for instance, a typical 1hr build time can be reduced to 20min. If you’re only building for one device, 25GB-50GB is fine. If you plan to build for several devices that do not share the same kernel source, aim for 75GB-100GB. This space will be permanently occupied on your drive, so take this into consideration. See more information about ccache on Google’s android build environment initialization page. Helpful Tip If you are a very active developer, working on many other projects than just Android, you might prefer to keep your Android ccache independent because it’s huge and can slow down the efficiency of ccache in your other projects. Beginning with CyanogenMod you can specify environment variables for the location and size of CyanogenMod’s ccache. Some syntax examples export ANDROID_CCACHE_DIR="$HOME/android/.ccache" and export ANDROID_CCACHE_SIZE="50G". Start the build Time to start building! So now type $ croot $ brunch mondrianwifi The build should begin. Helpful Tip If the build doesn’t start, try lunch and choose your device from the menu. If that doesn’t work, try breakfast and choose from the menu. The command make mondrianwifi should then work. Helpful Tip A second, bonus tip! If you get a command not found error for croot, brunch, or lunch, be sure you’ve done the source build/ command in this Terminal session from the ~/android/system directory. Helpful Tip A third tip! If the build to fails while downloading Gello, you’ll need to import a missing certificate into Maven’s truststore. Detailed instructions on how to do that can be found here If the build breaks… If you experience this not-enough-memory-related error… ERROR failed return code 1make *** [out/target/product/mondrianwifi/ Error 1 …you may want to make the following change to ~/android/system/build/tools/releasetools/ Search for instances of -Xmx2048m it should appear either under or near usage of and replace it with -Xmx1024m or -Xmx512m. Then start the build again with brunch. If you see a message about things suddenly being “killed” for no reason, your virtual machine may have run out of memory or storage space. Assign it more resources and try again. Install the build Assuming the build completed without error it will be obvious when it finishes, type $ cd $OUT in the same terminal window that you did the build. Here you’ll find all the files that were created. The stuff that will go in /system is in a folder called system. The stuff that will become your ramdisk is in a folder called root. And your kernel is called… kernel. But that’s all just background info. The two files we are interested in are 1 which contains CyanogenMod Recovery, and 2 which is the CyanogenMod installation package. Install CyanogenMod Back to the $OUT directory on your computer– you should see a file that looks something like Note The above file name may vary depending on the version of CM you are building. Your build may not include a version number or may identify itself as a “KANG” rather than UNOFFICIAL version. Regardless, the file name will end in .zip and should be titled similarly to official builds. Now you can flash the cm...zip file above as usual via recovery mode. Before doing so, now is a good time to make a backup of whatever installation is currently running on the device in case something goes wrong with the flash attempt. While CyanogenMod Recovery doesn’t have a backup feature, there are other custom recoveries available that do. You can also use something like Titanium Backup root required as an alternative. Success! So….what’s next? You’ve done it! Welcome to the elite club of self-builders. You’ve built your operating system from scratch, from the ground up. You are the master/mistress of your domain… and hopefully you’ve learned a bit on the way and had some fun too. Now that you’ve succeeded in building CyanogenMod for your device, here are some suggestions on what to do next. Also, be sure to take a glance at the Dev Center on this wiki for all kinds of more detailed information about developer topics ranging from collecting logs, understanding what’s in the source code directories, submitting your own contributions, porting CyanogenMod to new devices, and a lot more. Congrats again! Content of this page is based on informations from under CC BY-SA licence. Released 2014, March 335g, thickness Android TouchWiz UI 16GB/32GB storage, microSDXC Samsung Galaxy Tab PRO LTE was announced at 2014, January. Released 2014, March with Android KitKat, TouchWiz UI, have chipset Qualcomm Snapdragon 800 28 nm CPU Quad-core GHz Krait 400 and GPU Adreno 330. It have 16GB 2GB RAM, 32GB 2GB RAM storage and there are colors Black, White NETWORK Technology GSM / HSPA / LTE 2G GSM 850 / 900 / 1800 / 1900 - SM-T321, SM-T325 3G HSDPA 850 / 900 / 1900 / 2100 - SM-T321, SM-T325 4G 1, 3, 5, 7, 8, 20 - SM-T325 Speed HSPA Mbps T321/ LTE Cat4 150/50 Mbps T325 TIMELINE Announced 2014, January. Released 2014, March Released Released 2014, March BODY Dimensions 219 x x mm x x in DISPLAY Size inches, cm2 ~ screen-to-body ratio Resolution 1600 x 2560 pixels, 1610 ratio ~359 ppi density PLATFORM OS Android KitKat, TouchWiz UI Chipset Qualcomm Snapdragon 800 28 nm CPU Quad-core GHz Krait 400 MEMORY Card slot microSDXC dedicated slot Internal 16GB 2GB RAM, 32GB 2GB RAM SOUND Loudspeaker Yes, with stereo speakers COMMUNICATES WLAN Wi-Fi a/b/g/n/ac, dual-band, Wi-Fi Direct, hotspot GPS Yes, with A-GPS, GLONASS USB microUSB MHL TV-out, USB On-The-Go FEATURES Sensors Accelerometer, gyro, compass BATTERY Battery Li-Ion 4800 mAh, non-removable Specs source Disclaimer. We can not guarantee that the information on this page is 100% correct 1. Extract unzip the Samsung firmware file. Recommended using WinRAR or 7-Zip 2. Download Odin Tool 3. Extract Odin ZIP file 4. Open Odin execute file 5. Reboot Samsung phone in Download Mode hold Home + Power + Volume Down buttons / hold Volume Down + Bixby buttons then plug-in cable 6. Connect you Samsung phone and wait until you get a blue sign in Odin 7. Add the 1 file Samsung firmware to AP/PDA or 4 files Samsung firmware AP/BL/CP/CSC to it's slots 8. Make sure re-partition is NOT ticked 9. Click the START button, sit back and wait few minutes Install LineageOS on mondrianwifi Basic requirements Make sure your computer has adb. Setup instructions can be found here. Enable USB debugging on your device. Preparing for installation Samsung devices come with a unique boot mode called “Download mode”, which is very similar to “Fastboot mode” on some devices with unlocked bootloaders. Heimdall is a cross-platform, open-source tool for interfacing with Download mode on Samsung devices. The preferred method of installing a custom recovery is through Download Mode – rooting the stock firmware is neither necessary nor required. Download and install the appropriate version of the Heimdall suite for your machine’s OS Windows Extract the Heimdall suite zip and take note of the new directory containing You can verify Heimdall is functioning by opening a Command Prompt or PowerShell in that directory and running heimdall version. If you receive an error, install the Microsoft Visual C++ 2015-2019 Redistributable Package x86 on your computer. Linux Extract the Heimdall suite zip and take note of the new directory containing heimdall. Now copy heimdall into a directory in $PATH, a common one on most distros will be /usr/local/bin. For example cp heimdall /usr/local/bin. You can verify Heimdall is functioning by opening a Terminal and running heimdall version. macOS Mount the Heimdall suite DMG. Now drag heimdall down into the /usr/local/bin symlink provided in the DMG. You can verify Heimdall is functioning by opening a Terminal and running heimdall version. Power off the device, and boot it into download mode With the device powered off, hold Volume Down while booting. Now, click the button that the on screen instructions correlate to “Continue”, and insert the USB cable into the device. For Windows user only install the necessary drivers. A more complete set of instructions can be found in the Zadig user guide. If nothing relevant appears, try uninstalling any Samsung related Windows software, like Samsung Windows drivers and/or Samsung Kies. Run found in your extracted Heimdall directory. Choose Options » List all devices from the menu. Select Samsung USB Composite Device or MSM8x60 or Gadget Serial or Device Name from the drop down menu. Click Replace Driver, then selecting Install Driver from the drop down list built into the button. If you are prompted with a warning that the installer is unable to verify the publisher of the driver, select Install this driver anyway. You may receive two more prompts about security. Select the options that accept the warnings and allow you to carry on. On your machine, open a Command Prompt or PowerShell Windows window, or Terminal Linux or macOS window, and type If the device reboots that indicates that Heimdall is installed and working properly. If it does not, please refollow these instructions to verify steps weren’t missed, try a different USB cable, and a different USB port. Installing a custom recovery using heimdall Download a custom recovery – you can download TWRP. Simply download the latest recovery file, named something like Power off the device, and boot it into download mode With the device powered off, hold Volume Down while booting. Now, click the button that the on screen instructions correlate to “Continue”, and insert the USB cable into the device. On your machine, open a Command Prompt or PowerShell Windows window, or Terminal Linux or macOS window, and type heimdall flash -RECOVERY .img -no-reboot A blue transfer bar will appear on the device showing the recovery image being flashed. Unplug the USB cable from your device. Manually reboot into recovery, this may require pulling the device’s battery out and putting it back in, or if you have a non-removable battery, press the Volume Down + Power buttons for 8~10 seconds until the screen turns black & release the buttons immediately when it does, then boot to recovery With the device powered off, hold Volume Up while booting. Installing LineageOS from recovery Build a LineageOS installation package. Optionally, download additional application packages such as Google Apps use the arm architecture. If you are not in recovery, reboot into recovery With the device powered off, hold Volume Up while booting. Now tap Wipe. Now tap Format Data and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage. Return to the previous menu and tap Advanced Wipe, then select the Cache and System partitions and then Swipe to Wipe. Sideload the LineageOS .zip package On the device, select “Advanced”, “ADB Sideload”, then swipe to begin sideload. On the host machine, sideload the package using adb sideload Optionally If you want to install any additional add-ons, repeat the sideload steps above for those packages in sequence. Optionally Root your device by installing LineageOS’ AddonSU, use the arm package or by using any other method you prefer. Once you have installed everything successfully, run adb reboot’. Update to a newer build of the same LineageOS version on mondrianwifi Updating your device Using the LineageOS Updater app Open Settings, navigate to “System”, then “Updater”. Click the Refresh Icon in the top right corner. Choose which update you’d like and press “Download”. When the download completes, click “Install”. Your device will reboot to recovery and install the update, then reboot to the updated installation. From your PC via the push_update script Linux/macOS only Make sure your computer has working adb. Setup instructions can be found here. Enable USB debugging on your device. Additionally, open Settings, then “System”, then “Developer Options”, and then either check “Rooted Debugging” LineageOS or above or select “Root Access Options”, then “ADB Only”. Run adb root Run wget && chmod +x Run ./ /path/to/zip Open Settings, navigate to “System”, then “Updater”. Then proceed to click “Install” on the newly pushed update to commence installation. Your device will reboot to recovery and install the update, then reboot to the updated installation. Sideloading from Recovery Make sure your computer has working adb. Setup instructions can be found here. Enable USB debugging on your device. Additionally, open Settings, then “System”, then “Developer Options”, and then either check “Rooted Debugging” LineageOS or above or select “Root Access Options”, then “ADB Only”. Run adb reboot sideload Run adb sideload /path/to/zip Run adb reboot Upgrade to a higher version of LineageOS -> on mondrianwifi Manually upgrading LineageOS The updater app does not support upgrades from one version of LineageOS to another, and will block installation to any update for a different version. Upgrading manually requires similar steps to installing LineageOS for the first time. Build a LineageOS install package. Optionally, download additional application packages such as Google Apps use the arm architecture. Make sure your computer has working adb. Setup instructions can be found here. Enable USB debugging on your device. Additionally, open Settings, then “System”, then “Developer Options”, then select “Root Access Options”, and finally “ADB Only”. Now, run adb root’ Run adb reboot sideload. Run adb sideload /path/to/zip inserting the path to your LineageOS package. Optionally If you want to install any additional add-ons, click Advanced, then ADB Sideload, then swipe to begin sideload, then adb sideload /path/to/zip those packages in sequence. Optionally Root your device by installing LineageOS’ AddonSU, use the arm package or by using any other method you prefer. Once you have installed everything successfully, run adb reboot. Build for mondrianwifi Introduction These instructions will hopefully assist you to start with a stock Samsung Galaxy Tab Pro unlock the bootloader if necessary, and then download the required tools as well as the very latest source code for LineageOS based on Google’s Android operating system for your device. Using these, you can build both a LineageOS installation zip and a LineageOS Recovery image and install them on your device. It is difficult to say how much experience is necessary to follow these instructions. While this guide is certainly not for the extremely uninitiated, these steps shouldn’t require a PhD in software development either. Some readers will have no difficulty and breeze through the steps easily. Others may struggle over the most basic operation. Because people’s experiences, backgrounds, and intuitions differ, it may be a good idea to read through just to ascertain whether you feel comfortable or are getting over your head. Remember, you assume all risk of trying this, but you will reap the rewards! It’s pretty satisfying to boot into a fresh operating system you baked at home . And once you’re an Android-building ninja, there will be no more need to wait for “nightly” builds from anyone. You will have at your fingertips the skills to build a full operating system from code and install it to a running device, whenever you want. Where you go from there– maybe you’ll add a feature, fix a bug, add a translation, or use what you’ve learned to build a new app or port to a new device– or maybe you’ll never build again– it’s all really up to you. What you’ll need A Samsung Galaxy Tab Pro A relatively recent 64-bit computer Linux, macOS, or Windows with a reasonable amount of RAM and about 200 GB of free storage more if you enable ccache or build for multiple devices. The less RAM you have, the longer the build will take. Aim for 16 GB RAM or more, enabling ZRAM can be helpful. Using SSDs results in considerably faster build times than traditional hard drives. A USB cable compatible with the Samsung Galaxy Tab Pro A decent internet connection and reliable electricity. 🙂 Some familiarity with basic Android operation and terminology. It would help if you’ve installed custom roms on other devices and are familiar with recovery. It may also be useful to know some basic command line concepts such as cd, which stands for “change directory”, the concept of directory hierarchies, and that in Linux they are separated by /, etc. Let’s begin! Build LineageOS and LineageOS Recovery Install the platform-tools If you haven’t previously installed adb and fastboot, you can download them from Google. Extract it running unzip -d ~ Now you have to add adb and fastboot to your PATH. Open ~/.profile and add the following add Android SDK platform tools to path if [ -d "$HOME/platform-tools" ] ; then PATH="$HOME/platform-tools$PATH" fi Then, run source ~/.profile to update your environment. Install the build packages Several packages are needed to build LineageOS. You can install these using your distribution’s package manager. To build LineageOS, you’ll need bc bison build-essential ccache curl flex g++-multilib gcc-multilib git gnupg gperf imagemagick lib32ncurses5-dev lib32readline-dev lib32z1-dev liblz4-tool libncurses5 libncurses5-dev libssl-dev libxml2 libxml2-utils lzop pngcrush rsync schedtool squashfs-tools xsltproc zip zlib1g-dev To build LineageOS you’ll also need maven For Ubuntu versions older than focal, install also While for Ubuntu versions older than xenial, install Java Different versions of LineageOS require different JDK Java Development Kit versions. LineageOS OpenJDK included by default LineageOS OpenJDK install openjdk-8-jdk LineageOS OpenJDK install openjdk-7-jdk* * Ubuntu and newer do not have OpenJDK in the standard package repositories. See the Ask Ubuntu question “How do I install openjdk 7 on Ubuntu or higher?”. Note that the suggestion to use PPA openjdk-r is outdated the PPA has never updated their offering of openjdk-7-jdk, so it lacks security fixes; skip that answer even if it is the most upvoted. Create the directories You’ll need to set up some directories in your build environment. To create them mkdir -p ~/bin mkdir -p ~/android/lineage The ~/bin directory will contain the git-repo tool commonly named “repo” and the ~/android/lineage directory will contain the source code of LineageOS. Install the repo command Enter the following to download the repo binary and make it executable runnable curl > ~/bin/repo chmod a+x ~/bin/repo Put the ~/bin directory in your path of execution In recent versions of Ubuntu, ~/bin should already be in your PATH. You can check this by opening ~/.profile with a text editor and verifying the following code exists add it if it is missing set PATH so it includes user's private bin if it exists if [ -d "$HOME/bin" ] ; then PATH="$HOME/bin$PATH" fi Then, run source ~/.profile to update your environment. Configure git Given that repo requires you to identify yourself to sync Android, run the following commands to configure your git identity git config -global "[email protected]" git config -global "Your Name" Initialize the LineageOS source repository The following branches can be used to build for the Samsung Galaxy Tab Pro Enter the following to initialize the repository cd ~/android/lineage repo init -u -b Download the source code To start the download of the source code to your computer, type the following The LineageOS manifests include a sensible default configuration for repo, which we strongly suggest you use don’t add any options to sync. For reference, our default values are -j 4 and -c. The -j 4 part means that there will be four simultaneous threads/connections. If you experience problems syncing, you can lower this to -j 3 or -j 2. On the other hand, -c will ask repo to pull in only the current branch instead of all branches that are available on GitHub. Prepare the device-specific code After the source downloads, ensure you’re in the root of the source code cd ~/android/lineage, then type source build/ breakfast mondrianwifi This will download your device’s device specific configuration and kernel. Now ensure your Galaxy Tab Pro is connected to your computer via the USB cable, with ADB and root enabled, and that you are in the ~/android/lineage/device/samsung/mondrianwifi folder. Then run the script The blobs should be pulled into the ~/android/lineage/vendor/samsung folder. If you see “command not found” errors, adb may need to be placed in ~/bin. Turn on caching to speed up build Make use of ccache if you want to speed up subsequent builds by running export USE_CCACHE=1 export CCACHE_EXEC=/usr/bin/ccache and adding that line to your ~/.bashrc file. Then, specify the maximum amount of disk space you want ccache to use by typing this where 50G corresponds to 50GB of cache. This needs to be run once. Anywhere from 25GB-100GB will result in very noticeably increased build speeds for instance, a typical 1hr build time can be reduced to 20min. If you’re only building for one device, 25GB-50GB is fine. If you plan to build for several devices that do not share the same kernel source, aim for 75GB-100GB. This space will be permanently occupied on your drive, so take this into consideration. You can also enable the optional ccache compression. While this may involve a slight performance slowdown, it increases the number of files that fit in the cache. To enable it, run ccache -o compression=true Start the build Time to start building! Now, type croot brunch mondrianwifi The build should begin. Install the build Assuming the build completed without errors it will be obvious when it finishes, type the following in the terminal window the build ran in There you’ll find all the files that were created. The two files of more interest are which is the LineageOS recovery image. which is the LineageOS installer package. Success! So… what’s next? You’ve done it! Welcome to the elite club of self-builders. You’ve built your operating system from scratch, from the ground up. You are the master/mistress of your domain… and hopefully you’ve learned a bit on the way and had some fun too.

galaxy tab pro 8.4 rom