[TUTORIAL] on Root/Recovery/Custom ROM Galaxy S4 (I337z) Cricket Wireless/Aio - AT&T Samsung Galaxy S 4 General

Hey guys,
After working on my Cricket/Aio Galaxy S4 for days and finding very little development tips, I decided to write my own full guide on how to root, install a custom recovery (TWRP) and flash a custom ROM for the SGH-I337z.
Before we begin, I am not responsible for any damage, including physical damage due to frustration, that you may inflict on your device. If at the end of this, your phone is nothing but an expensive paperweight, I must apologize, but assume no responsibility. If you are not comfortable using Odin or flashing ROMs, I suggest reading a little more on the subject before moving forward. This is a detailed guide for a specific device that is difficult to find help for. This isn't a step by step guide for a first time flasher. You have been warned.
First, download and install the Kingroot apk. Do a quick Google search for this. It is a Chinese root method that I know for a fact works, where Kingoroot and Towelroot fail. Trust me, I tried Kingo and Towelroot just as many times as you. It also installs it's own sub-par version of Superuser called Kinguser. Nothing great, but it gets the job done. If you only want root, you are done. Install the app, run the app, run Root Checker. From here you can uninstall system apps, overclock, etc. Keep in mind, if you uninstall either of these, you lose root access.
If you want a custom recovery/ROM, here's how:
First thing I did was flash the recovery. But it has locked bootloader right? Right. So we are going to Odin flash the recovery. Although it is a custom recovery, flashing through Odin will allow you to bypass the bootloader lock. First, you will want to download the recovery image. http://www.mediafire.com/download/j6ml64w1ldixklq/jflteaio_twrp.img
Now put this somewhere you can find it.
Next you will need to download the .tar converter tool and convert this .img file you just downloaded into a .tar.md5 file so that Odin can flash it. There are instructions in the link and it is very simple.
http://forum.xda-developers.com/showthread.php?t=2446269
Once you have converted the img, Open Odin, and boot your phone into download mode by holding Volume down and power, and plug it in. Odin should notify you it has been "Added!" Select PDA, and navigate to the recovery img that you just converted to the tar file. Select this file, then make sure Auto Reboot is the only other box checked, and hit start. It should only take a few seconds, and you should be greeted with a "Success" message. Allow the phone to reboot into recovery. It should do it manually, but if not, boot into recovery by holding Volume Up+Home+Power. It should load the TWRP splash screen. If this happens, it was all successful.
That is the hard part honestly. Once you're recovery is installed, you're golden, Pony Boy. Download a compatible ROM and install the zip via TWRP recovery. Unfortunately, from what I understand, Touchwiz based ROMs are the only ones compatible with this method. I am using Skyfall as suggested in another thread I saw, and it is great. Looks just like stock, but enables Wifi Tethering (which Cricket currently blocks) and comes with a couple other cool features. It also uses Aroma installer which allows you to customize the installation, meaning you can choose to have Xposed Modules and Wanam Xposed installed by default, and NONE of the Samsung apps from default.
Here is the link for a ROM that I know for a fact works flawlessly: http://forum.xda-developers.com/showpost.php?p=55524201&postcount=4
KEEP IN MIND---Cricket/Aio must install the AT&T variant from Aroma installer. Others may work, but this is the only one I can confirm. Internally, they are the same phone. LTE, Wifi, Bluetooth all confirmed working.

Following the steps provided everything worked up until I reached odin. I downloaded and converted the jflteaio_twrp.img to jflteait_twrp.tar.md5 and my phone has root access provided by kingroot.
I tried using Odin3 v3.04 3.07 and 3.10.7 no matter the version always following "<ID:0/005> NAND Write Start!!" I see "<OSM> All threads completed. (succeed 0 / failed 1)".
I know this post was last updated June 30th 2015 so my versions of Odin should be working. Please help, Thanks

Try using Heimdall Suite to flash recovery. Once downloaded unzip file to desktop. Follow these instructions next.
- Boot the Galaxy S4 into download mode (Vol Dwn + Pwr Up).
- Run zadig.exe from the Drivers folder of the Heimdall Suite.
- Choose Options > List All Devices from the menu.
- Select MSM8x60.
- Click Install Driver.
- If prompted with a warning the installer is unable to verify the publisher of the driver, select Install this driver anyway. Further prompts about security may pop-up, select the options which allow the installation to continue.
- Place recovery image in heimdall folder(rename the img to recovery.img) Do not covert img to tar it needs to stay as a img file.
-Next open command window inside the Heimdall folder you unzipped by holding shift and right clicking. Then select open command window here. In the command window type the following.
(heimdall flash --RECOVERY*recovery.img) .Once it's finished the phone should reboot. Let it reboot if it doesn't just do a battery pull and reboot into recovery mode by pressing volume up+home+power .Once it's finished the phone should reboot. Let it reboot if it doesn't just do a battery pull and reboot into recovery mode by pressing volume up+home+power. That should work.

Related

[Q] Re: THE ULTIMATE NEWB GUIDE. I'm too noob for to noob guide, help.

. I don't even want a custom ROM. I just want to be rooted and run stock with rooted google play store apps. Am I there?
I just want to run rooted apps with no ROM flashing...oh god why...where is the guide to root and only root?
You'd think this http://forum.xda-developers.com/show....php?t=1652398 would be where to go to do that, but evidently it's sending me down the road to custom ROM flashing. AGHGHGhjkdashbdas. Do not want.
Ok, so here's where I am, I have finished step 8:
1. Download Odin 1.85 .
2. Download(USE FIREFOX!) ClockworkMod TOUCH 5.5.0.4 OR TWRP 2.2.2.0, they are both named "recovery.tar.md5" and will be downloaded as "recovery.tar.md5", DO NOT CHANGE the filename or else it wont install.
3. Extract the contents of odin-185.zip to a folder.
4. Run Odin 1.85.exe from the folder you extracted it to.
5. Prepare Odin: Check "auto-reboot" and UNCHECK ALL OTHER OPTIONS. SEE COMPUTER SREEN PICS BELOW.
6. Only Click "PDA" and select the recovery.tar.md5 file you downloaded. SEE COMPUTER SREEN PICS BELOW.
7. How To Put your device into Download Mode: DO NOT TOUCH THE POWER BUTTON FOR THIS PROCEDURE. - download mode is NOT the same as recovery mode
a. Connect the USB cable to your PC, but NOT to your phone.
b. Remove the battery.
c. Reinsert the battery.
d. ATT PHONES - Press and keep down both Volume Up and Volume Down keys simultaneously.
ROGERS PHONES - Press and keep down only the Volume Down key.
DO NOT RELEASE THE VOLUME KEY(S) UNTIL INSTRUCTED TO DO SO IN STEP (f)
e. Insert the USB cable into your device. The phone will turn itself on when usb cable is inserted - DO NOT TOUCH THE POWER BUTTON.
f. You will now see a screen w/a yellow triangle warning you about installing a rom . Now release the volume key(s) - SEE PHONE PICS BELOW
g. Press and release the "Volume Up" key to enter into download mode - SEE PHONE PICS BELOW
h. You should now be at the Download Mode screen w/odin recognizing your phone. SEE COMPUTER SREEN PICS BELOW.
8. Click Start in Odin. It will flash the new recovery and will reboot the phone when completed. Your device will autoreboot into android. You are done using ODIN.
9. UPDATING CWM OR TWRP:
Now you need to udate CWM, download and copy cwm6027touch_v14.4.6_skyrocket.zip file to your sdcard, boot into recovery and choose "INSTALL FROM SDCARD" from recovery, install the file and reboot back into recovery to see if it installed correctly.
sk8erwitskil's CWM thread is here HERE , check to see if above file is the latest or dl the "Flashable zip" CWM file from there.
If upgrading TWRP go here HERE and follow the dev's instructions on using goo app, or you can use the flashable TWRP 2.4.1.0 file HERE and copy that file to your sdcard, boot into recovery and pick "INSTALL" from recovery, install the file and reboot back into recovery to see if it installed correctly.
How to enter recovery read section #2 below.
How to use cwm read THIS, also read Q&A on recoveries
You can upgrade to either CWM OR TWRP from which ever recovery TAR file you used in ODIN in step #2 from above.
10. You're done newbie and soon to be a power user, read and educate yourself as much as you can before flashing, happy flashing.
Click to expand...
Click to collapse
I don't know how to do step 9. Do I even need it? I have no desire to run a custom ROM.
yargdpirate said:
OK so here's the list of instructions I'm using to root my Skyrocket:
I have completed everything through step 4. I completely do not understand what to do after that. So, like I'm a 40 year old soccer mom, can you explain what I'm supposed to do to fulfill step 5? Is it through the odin app on my pc? Is this completed on my phone? The link provided that ostensibly explains to noobs how to do this (http://forum.xda-developers.com/showthread.php?t=1777970) doesn't adequately explain to me what I'm doing and where.
Help, please!
Click to expand...
Click to collapse
Assuming that you have successfully installed your custom recovery you then need to know which recovery you installed before you update it. If you used CWM you can get the updated version from the Skyrocket development thread. Put the updated CWM file on your SD card and flash that zip while in recovery. If you used TWRP you can update it through the app that it installed if it did install one. GooManager (someone correct me if I am wrong on the name) I think GooManager needs suoeruser privileges. So which recovery did you flash?
CodeNameRedNeck said:
Assuming that you have successfully installed your custom recovery you then need to know which recovery you installed before you update it. If you used CWM you can get the updated version from the Skyrocket development thread. Put the updated CWM file on your SD card and flash that zip while in recovery. If you used TWRP you can update it through the app that it installed if it did install one. GooManager (someone correct me if I am wrong on the name) I think GooManager needs suoeruser privileges. So which recovery did you flash?
Click to expand...
Click to collapse
Put the updated CWM file on your SD card and flash that zip while in recovery?
Click to expand...
Click to collapse
It's CWM. How do I
A. Put the updated CWM file on my SD card and
B. Flash that zip while in recovery? Is that through Odin, or what?
Thanks
yargdpirate said:
It's CWM. How do I
A. Put the updated CWM file on my SD card and
B. Flash that zip while in recovery? Is that through Odin, or what?
Thanks
Click to expand...
Click to collapse
i think you should stay on stock, read more b4 you brick your phone, no sense in rooting/installing custom roms when you dont know how to install a file on your scard, im not putting you down but trying to give you friendly advice
Vincom has a point. I taught myself through these forums and Google how to do it back in October of 2011. I flashed many a ROM and many files since then until I bricked mine Thursday. Now I have to pay 60 dollars to get it fixed. But on the upside I now have a Note II to play with.
Edit: She is asking for help though and she did ask in the right thread. Some people need more help than others.
vincom said:
i think you should stay on stock, read more b4 you brick your phone, no sense in rooting/installing custom roms when you dont know how to install a file on your scard, im not putting you down but trying to give you friendly advice
Click to expand...
Click to collapse
Oh. ****. I don't even want a custom ROM. I just want to be rooted and run stock with rooted google play store apps. Am I there?
I just want to run rooted apps with no ROM flashing...oh god why...where is the guide to root and only root?
You'd think this http://forum.xda-developers.com/showthread.php?t=1652398 would be where to go to do that, but evidently it's sending me down the road to custom ROM flashing. AGHGHGhjkdashbdas. Do not want.
Ok, so here's where I am, I have finished step 8:
1. Download Odin 1.85 .
2. Download(USE FIREFOX!) ClockworkMod TOUCH 5.5.0.4 OR TWRP 2.2.2.0, they are both named "recovery.tar.md5" and will be downloaded as "recovery.tar.md5", DO NOT CHANGE the filename or else it wont install.
3. Extract the contents of odin-185.zip to a folder.
4. Run Odin 1.85.exe from the folder you extracted it to.
5. Prepare Odin: Check "auto-reboot" and UNCHECK ALL OTHER OPTIONS. SEE COMPUTER SREEN PICS BELOW.
6. Only Click "PDA" and select the recovery.tar.md5 file you downloaded. SEE COMPUTER SREEN PICS BELOW.
7. How To Put your device into Download Mode: DO NOT TOUCH THE POWER BUTTON FOR THIS PROCEDURE. - download mode is NOT the same as recovery mode
a. Connect the USB cable to your PC, but NOT to your phone.
b. Remove the battery.
c. Reinsert the battery.
d. ATT PHONES - Press and keep down both Volume Up and Volume Down keys simultaneously.
ROGERS PHONES - Press and keep down only the Volume Down key.
DO NOT RELEASE THE VOLUME KEY(S) UNTIL INSTRUCTED TO DO SO IN STEP (f)
e. Insert the USB cable into your device. The phone will turn itself on when usb cable is inserted - DO NOT TOUCH THE POWER BUTTON.
f. You will now see a screen w/a yellow triangle warning you about installing a rom . Now release the volume key(s) - SEE PHONE PICS BELOW
g. Press and release the "Volume Up" key to enter into download mode - SEE PHONE PICS BELOW
h. You should now be at the Download Mode screen w/odin recognizing your phone. SEE COMPUTER SREEN PICS BELOW.
8. Click Start in Odin. It will flash the new recovery and will reboot the phone when completed. Your device will autoreboot into android. You are done using ODIN.
9. UPDATING CWM OR TWRP:
Now you need to udate CWM, download and copy cwm6027touch_v14.4.6_skyrocket.zip file to your sdcard, boot into recovery and choose "INSTALL FROM SDCARD" from recovery, install the file and reboot back into recovery to see if it installed correctly.
sk8erwitskil's CWM thread is here HERE , check to see if above file is the latest or dl the "Flashable zip" CWM file from there.
If upgrading TWRP go here HERE and follow the dev's instructions on using goo app, or you can use the flashable TWRP 2.4.1.0 file HERE and copy that file to your sdcard, boot into recovery and pick "INSTALL" from recovery, install the file and reboot back into recovery to see if it installed correctly.
How to enter recovery read section #2 below.
How to use cwm read THIS, also read Q&A on recoveries
You can upgrade to either CWM OR TWRP from which ever recovery TAR file you used in ODIN in step #2 from above.
10. You're done newbie and soon to be a power user, read and educate yourself as much as you can before flashing, happy flashing.
Click to expand...
Click to collapse
I don't know how to do step 9. Do I even need it? I have no desire to run a custom ROM.
For just rooting u have to run the superuser zip through your recovery
Oh and if you are not understanding what the stickies are saying to do then look it up on youtube because there are a lot of step by step instructions there.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
a. put updated file in your micro sd card.... plug ur micro sd card to pc... drag file and drop it in your micro sd card. put the micro sd card back in phone.
b. to go to recovery press power button + vol+ + vol- all at once and hold.
why do u need to unlock play store app? playstore is accessible completely even without root. you can also sideload Amazon appstore and other apps without root. no need to get all bricked up just to run playstore. i'm confused what are you trying to do again?
droidbabyxda said:
a. put updated file in your micro sd card.... plug ur micro sd card to pc... drag file and drop it in your micro sd card. put the micro sd card back in phone.
b. to go to recovery press power button + vol+ + vol- all at once and hold.
why do u need to unlock play store app? playstore is accessible completely even without root. you can also sideload Amazon appstore and other apps without root. no need to get all bricked up just to run playstore. i'm confused what are you trying to do again?
Click to expand...
Click to collapse
im guessing he wants to run apps from play that require root, eg titanuim backup, but he doesnt know how to put a file on his sdcard, but then he has to learn how to install zips from recovery which someones got to teach him since he doesnt want to read/learn/search for the answers. he seems to be impatient and wants it done "now", its a brick waiting to happen, my advice to him was to slowdown and learn
vincom said:
im guessing he wants to run apps from play that require root, eg titanuim backup, but he doesnt know how to put a file on his sdcard, but then he has to learn how to install zips from recovery which someones got to teach him since he doesnt want to read/learn/search for the answers. he seems to be impatient and wants it done "now", its a brick waiting to happen, my advice to him was to slowdown and learn
Click to expand...
Click to collapse
agree and such bad attituted too. i wouldn't want to help anybody who cusses in every conversation geez little respect goes a long way
It you just want to root and not want to flash any custom ROMs or anything related to it,I will tell you how to from total beginning
ALL DATA WILL BE LOST , BACKUP EVERYTHING
In order to root Android 4.2 the following three requirements must be satisfied beforehand:
The Android SDK, which you can download from Google Developers
A custom recovery like ClockworkMod (CWM) or Team Win Recovery Project (TWRP)
SuperSU, which you can download from CF-Root
There are no major differences between the two, but TWRP is more touch-oriented thanks to larger buttons. CWM is also available in a touch-compatible variant, but it has much smaller buttons. It's a matter of personal preference between the two though, but you have to choose one.
Before starting the process I urge you to perform a backup, as all data might be lost afterwards. You can copy the contents of the SD card to a safe external location such as cloud storage service or computer hard drive.
The first step that needs to be performed after all the files are downloaded is to install the Android SDK. Afterwards open the Android SDK Manager and select the following two items:
Android SDK Platform-tools -- it contains the required programs to install Android 4.2 Jelly Bean
Google USB Driver -- it contains the necessary drivers for the Nexus device
Then you should create a folder in an easily accessible location within the command line. In this example I will use a folder named "Root" in my C:\ drive in Windows. The path name will therefore be: "C:\Root".
From the folder where Android SDK Platform-tools is installed (in my case it is "C:\Program Files x86)\Android\android-sdk\platform-tools" copy the following files to the previously created "Root" folder:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
The following files must also be copied to the "Root" folder:
CWM-SuperSU-v0.97.zip -- SuperSU file
The custom recovery that you previously downloaded for your specific device (please see below)
For my 8 GB nexus 7 wifi(codename "grouper" I will use TWRP with the name "openrecovery-twrp-2.3.1.0-grouper.img".
You can easily find the codename for your devoice by looking into Google
The custom recovery file differs for each device, please make sure you download the correct file
In order to make the process smoother for instance the SuperSU file can be renamed to "root.zip" and the custom recovery to "customrecovery.zip". It's a matter of convenience, but for accuracy I will stick to the original naming for this guide.
If the previous steps are completed you must have the following six files in your "Root" folder:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
CWM-SuperSU-v0.97.zip -- SuperSU file
The custom recovery. In my case it is "openrecovery-twrp-2.3.1.0-grouper.img"
From there, you can proceed to install the drivers for "fastboot mode". To install them, follow these steps:
Power off your Nexus device.
Press and hold Volume Up and Volume Down then press and hold the Power button; the device will now enter "fastboot mode".
Go to Device Manager (Computer -> Properties -> Device Manager in Windows 7/8) and identify the device; for me it shows up as Android 1.0.
Right click Android 1.0 and select "Update Driver Software," then select "Browse my computer for driver software".
Select "Let me pick from a list of device drivers on my computer," then click "Next".
From "Have Disk..." option go to the folder where you have Google USB Driver installed (for me it's "C:\Program Files .(x86)\Android\android-sdk\extras\google\usb_driver" and select "android_winusb.inf".
Out of the three options select "Android ADB Interface" and validate any future warning window to install the driver.
Final preparations
Everything is prepared in order to start the installation process, but in order to do so a command window must be opened. Windows Key + R opens "Run"; type in "cmd" and the command window appears. Typing "cd C:\Root" and pressing Enter sets the "Root" folder as the working directory. Pressing the Shift key and right clicking inside the "Root" folder will also deliver the same result.
The device must be turned on in "fastboot mode" which I have explained at step no.2 during the driver installation process, and obviously plugged-in to the computer. You then have to type in the following commands while in "fastboot mode":
fastboot devices -- this is just for verification purposes; if there is no listed device then the drivers have been improperly installed and steps 1 through 7 must be redone.
fastboot oem unlock -> you have to accept the prompt in order to continue -- this command will unlock the bootloader, but it will also erase the data on the device which is why a backup is necessary.
fastboot reboot-bootloader -- this will reboot the bootloader.
fastboot flash recovery openrecovery-twrp-2.3.1.0-grouper.img -- this will flash the custom recovery --please use the specific file and name for your particular Nexus device!
fastboot erase cache -- this will erase the cache -- might not be necessary but it's just as a precaution.
fastboot reboot -- this will reboot the device.
After Android 4.2 is loaded and running the SuperSU file must be copied from the "Root" folder to the internal storage (shows up in Windows Explorer as a Nexus device). A simple copy and paste will do the trick here.
Then you have to power off the Nexus device and enter "fastboot mode" again. Use the Volume Up and Volume Down keys to navigate until you can select "Recovery Mode". After the power button is pressed the device will reboot in the new custom recovery.
Rooting your Nexus device
If you have ClockworkMod installed, you have to perform the following steps:
Select "install zip from sdcard"
Select "choose zip from sdcard"
Select "0" (zero) folder
Select "CWM-SuperSU-v0.97.zip"
Select "Yes - Install CWM-SuperSU-v0.97.zip"
Select "Go Back"
Select "reboot system now"
If you have Team Win Recovery Project installed, you have to perform the following steps:
Press "Install".\
Select "CWM-SuperSU-v0.97.zip" -- for me it's in the "0" (zero) folder
Swipe to confirm flash
Press "Wipe cache/dalvik" (just as a precaution)
Swipe to wipe
Press "Reboot System"
After Android 4.2 loads your device can run apps with elevated privileges (meaning it's rooted). A SuperSU app is installed in order to allow root requests, so please use your judgement on which apps you grant access.
If you experiences any problem, please reply and I will look into it.
Sent from my Nexus 7 using xda app-developers app
Sent from my Nexus 7 using xda app-developers app
^^you want him todo that, lmao, he doesnt even know how to put a file on his sdcard to flash it in recovery, theres no way a computer newb is going to be able to follow what you posted
That's why I have not used the word flash anywhere, I know that he does not know how to flash , I have posted the right thing for a total noob,( at least if he knows how to use command in windows or install drivers)
I helped him in the way I could and what he requested
Sent from my Nexus 7 using xda app-developers app
You think that helped. LOL. Your telling him to do things that aren't even required to gain root with this device. Not everything is a nexus bro. Next time you wanna help study up on the phone your giving advice about. lol
Well , thanks for telling me that every android isn't rooted in same manner, I was thinking that all devices are rooted in same ways like for my nexus
Sent from my Nexus 7 using xda app-developers app
naman14, im not putting you down, your step by step howto is admirable, good work, but the problem is that the op is clueless on tech stuff, its not the word "flash" he has a problem with, i could of said "install" and it would lead to same conclusion, he doesnt know how to copy a file to his sdcard, if he cant do that he has no business in modding his phone until he learns more. anyhow the op is long gone by now
I upgraded my samsung skyrocket s2 version 2.3.6 to 4.0.4 through the Kies. Then I tried to install TWRP 2.2.0 and Odin 1.85. I saw COM 14 ; COM 17 when I hit start button .It said
FAILED. Now it showed a yellow triangle in the middle of phone & monitor pictures. ( including : Firmware upgrade encountered an issue . please select recovery mode in Kies & try again). Please help . Thank you very much.
I just tried other laptop . I saw COM 3 but it said it couldn't open the serial (COM )port . All thread completed (success 0/ failed 1)

[Q] Bootloader question.

I follwed these instructions to root my phone:
Guides
Mar 29, 2013 Ξ57 CommentsRoot and Install CWM Recovery on Verizon Galaxy S3 SCH-I535 Android 4.1.1/4.1.2
posted by Rakesh Shukla
Rooting an Android device has many privileges. Having rooted your phone once, you are able to use third-party custom ROMs and mods that require a custom recovery to be installed. Besides, there are hundreds,or say thousands, of app that are capable of doing wondrous things and enhance your phones performance and usability. But this humble eulogy of rooting cannot undermine the hazards associated with it.
Rooting a Samsung Galaxy device is much easier than rooting any device manufactured by other OEMs but when it comes to rooting a Samsung phone from Verizon, things get a little more complicated and rounded. However, complicated it might be, it cannot stop our great Devs to crack the nut. All props and credit for the method described here goes to XDA member open1your1eyes0.
Disclaimer:
Please note that the procedure of unlocking the bootloader, rooting and installing a custom recovery on your Verizon Galaxy S3 SCH-I535 is considered risky. Moreover, it will also void the warranty of your phone. Proceed only when you are sure what you are going to do and understand the seriousness of things. More than anything, be careful while following the steps.
Looking for Rooting Tutorial for Some Other S3 Variant?
Take a look all Galaxy S3 rooting tutorials here.
Prerequisites:
•Charge your phone to have at least 60% of battery juice.
•Rooting does not wipe any data from your phone but we would strongly recommend that you backup all your contacts, messages, call-log, apps, etc. Here are some good free apps to help you with backing up your data.
•Put your device in USB Debugging mode from Settings> Developer Options>
Required Downloads:
Since this tutorial is for Galaxy S3 I535 on Android 4.1.1 and 4.1.2 both, download the files accordingly- only different being the stock bootchain file. For the sake of convenience put all the downloaded files in one folder.
These are important but mandatory files. If you have them, just skip:
•Download the Odin tool and extract the zip on your desktop: Odin3-v3.07.zip – Mirror
•Download Samsung USB Drivers and install on your computer. Skip if you already have it: Download
These two files are meant to be downloaded by all:
•Download the custom Bootchain file: VRALEC.bootchain.tar.md5 – Mirror
•Download CWM Recovery: CWM6023TouchVZW.tar.md5 — Mirror
Download one of the following files depending on what you want:
•Download SuperSU file (for Root Only): CWM-SuperSU-v0.99.zip
•Download SuperUser file to (Root and Unlock Bootloader both): SuperSU_Bootloader_FIXED.zip — Mirror
Download one of the following bootchain files depending on firmware version of your Galaxy S3 SCH-I535:
•Bootchain file for VRBLK3 (Jelly Bean 4.1.1): VRBLK3_Bootchain.tar.md5 — Mirror
•Bootchain file for VRBMB1 (Jelly Bean 4.1.2): VRBMB1_Bootchain.tar.md5 — Mirror
Root, Unlock Bootloader and Install CWM:
Already made the preparations and downloaded the required stuff? It’s action time now. Be careful and proceed.
1.Copy the “SuperSU_Bootloader_FIXED.zip” file to your phone’s internal or external SD card.
2.Turn off your Galaxy S3 and boot it into Download mode: hold the Volume Down + Home + Power buttons simultaneously for a few seconds till you see a warning screen asking you to press Volume Up key to continue. Pressing this key will take you to Download or Odin mode.
3.Open the Odin folder and run the .exe file present there and then connect your Galaxy S3 to PC via USB cable. Wait till Odin detects your device and you see ID:COM port turning Blue and “Added!!” text at the message box below.
4.Now we will flash the custom bootchain file so make sure that “Auto Reboot” and “F Reset Time” are selected on Odin. Then click the PDA button and select the “VRALEC.bootchain.tar.md5″ file and click on “Start” button on Odin.
5.The bootchain file will be flashed in a few seconds and you will see “RESET!!” message with blue signal. Your phone will reboot automatically. Close the Odin window and disconnect the USB cable.
6.Now you need to install the ClockworkMod touch recovery. To install it, boot the phone into Download mode again (as you did in Step #2 above).
7.Relaunch the Odin, connect the phone using the cable and uncheck the “Auto Reboot” option on Odin.
8.Click on the PDA button, select the “CWM6023TouchVZW.tar.md5″ file and hit the “Start” button.
9.CWM Recovery will be flashed to your phone followed by “PASS!!”. This time your phone will not reboot automatically. Close the Odin window.
10.Now pull out the back cover of the phone and remove the battery. Place the battery to its place after about 30 seconds.
11.Then boot the phone into ClockworkMod recovery mode. To do this, hold the Volume Up + Home + Power buttons simultaneously. Keep the 3 keys pressed till your phone vibrates and when it does, release the Power button but keep the other 2 keys pressed till you a gray background with blue text the clockworkmod recovery written on the top of the screen.
12.Since it’s touch recovery, you can either select options by tapping, or using the volume and power keys.
13.Okay, now go to “install zip from sdcard> choose zip from sdcard” and select the “SuperSU_Bootloader_FIXED.zip” file.
14.Confirm your choice by selecting “yes’ and let the installation finish.
15.When it’s done, go back and select “reboot system now”. But before your phone boots, pull out the battery and place it back after a few seconds.
16.Once again, and for the third time. you will have to boot the device in Download Mode. You know well how to do it.
17.Relaunch Odin, connect the phone to PC, click on PDA button and select the stock bootchain file (either VRBLK3 or VRBMB1) depending on what file you have downloaded.
18.Click the “Start” button to initiate the installation. When it is finished, the phone will reboot automatically.
So, now you have a fully rooted Verizon Galaxy S3 SCH-I535 with unlocked bootloader and ClockworkMod recovery installed. To verify the root, download any app that requires root permissions. However, there is a specific app for the purpose and you can find it at the Play Store
Everything went sucessfully and my phone was rooted. I did encounter one problem and that was I couldn't get the CWM Touch Recovery to stick. I found out with the help of a few forum members that I needed to select "yes" on the propmt to overwrite the stock recovery. (the warnign I got stated ROM will flash back to stock. Would you like to fix this? YES= This can not be undone/ NO or Go Back. I was selecting go back because I was not sure on what to select and CWM would never stick it would always reboot back to stock. Last night I did select yes, and it worked fine.) I went back and fixed the issue, and now CWM Touch Recovery is flashed on my phone. I also used Terminal Emulater to back up my IMEI.
My question is, because I initailly did'nt flash the CWM Touch Recovery the right way (right way meaning selecting yes) does this mean I didn't unlock my bootloader? I'm a complete noob and just want to make sure I have things in order.
Thanks,
Take a look at this thread to determine if you bootloader is unlocked.
http://forum.xda-developers.com/showthread.php?t=2265291

[Q] GT-P5113 Root problems, SuperSu binary issue. Could sure use help.

Tablet: Samsung Galaxy Tab 2 10.1 (GT-P5113) Wifi only.
OS: Android 4.2.2 Jellybean
Build#: P5113UEUCMK3
So here is what I have done:
Ran Odin v3 1.85 and pushed CF-Auto-Root-expresso10wifi-expresso10wifibby-gtp5113.tar.md5
I followed the instructions to the letter. The Odin process runs, red Android screen....tablet process runs...neither process reports errors...No Root.
When I try SuperSU I get "There is no SU binary installed...." blah blah see it all over the forums but nothing I have tried has fixed either problem. I even put the SuperSU.apk on a micro SD and it won't install over to replace the binary. SuperSU does not show up in my Applications list so I cannot remove it.
So I did hard resets, wiped cache etc..
No change.
Next I downloaded the factory ROM P5113UEUCMK3_P5113XACCND2_HOME.tar.md5 from Samsung and pushed it over successfully.
No change.
I cannot get root to take so I cannot manually remove SuperSU using a file manager (requires root)
I would really like to get my tablet rooted so i can install other apps.
Any one with information that will help me solve this will be my new hero...briefly...
Thanks in advance!
Did you check "unknown sources" in security/developer section?
Pp.
PanchoPlanet said:
Did you check "unknown sources" in security/developer section?
Pp.
Click to expand...
Click to collapse
Yes I did.
I'm having the exact same problem with my P5110.
Is anyone really gonna help here?
I have the same issue with GT-P3113.
To root or not to root?
Which one is it people? If you can't file explore because you don't have root you just delete SU from your apps (Manage apps) drawer.
Then you just go about your typical rooting, following the Op instructions and your done.
Pp.
I can only turn on and off supersu, can't delete or uninstall it.
Also despite turning it off and checking the appstore, there's no uninstall button, even when I did update it with a new apk it still won't do anything. Still says the same thing. no Binary and can't even install one.
PanchoPlanet said:
To root or not to root?
Which one is it people? If you can't file explore because you don't have root you just delete SU from your apps (Manage apps) drawer.
Then you just go about your typical rooting, following the Op instructions and your done.
Pp.
Click to expand...
Click to collapse
As I mentioned SU is not in my App manager and therefore cannot be removed. I attempted to download and install the SU apk from micro SD and it failed.
So I am stuck with no root and unable to get a file manager running to manually remove SU.
I have the same problem with my P3113
Do you have a custom recovery (CWM or TWRP) installed? If so you can download and flash the latest SuperSU.zip
Sent from my Nexus 4 using XDA Premium HD app
Well I had the exact same problem, and I think that the SuperSU included on the CF-Auto-Root file is outdated or something.
I was on android 4.2.2 but I have the Galaxy Tab 2 10.1 P5110.
I searched the forums and came up with a solution for our problem. I think that SuperSU is outdated on that CF-Auto-Root file or it was the custom recovery that it installs thats outdated or messed up for android 4.2.2, because right after it does its thing, we get the tablet default recovery again.
Since I dont know how to make a new CF-Auto-Root file, I tried to install an updated custom recovery through Odin3 instead of the CF-Auto-Root file, and it worked. Then I entered on the TWRP recovery and installed an updated SuperSU, restarted the tablet, and it worked too. I had now a rooted tablet with a permanent custom recovery, So i followed to install a custom rom, etc.
So now the steps I did:
(I am not responsible if it doesnt work for your tablet and messes something up or brick it, so please follow on your own risk, or maybe wait for some expert on this things to say if its safe or not. All i know is that it worked for me.)
Step 1: Download Stuff
Download and install samsung usb drivers
Go to Samsung website and search for your device. Go to downloads and download the USB Driver and install it.
Download Odin3 1.85_3
Go to this topic and download Odin3 3.85_3 from the "What you need:" section. Extract it on your computer.
Download TWRP recovery
Go to TWRP website, click "Get TWRP for your device", search for 5110 (doesn't have the 5113 version, and I think that the 5110 is the same and works too), scroll down to "Download - Odin Flashable Tar:" and click the "5110 only" version. It will open another page, scroll down for the most recent version and download the .tar file. Extract it on your computer.
Download SuperSU for TWRP
Go to Chainfire website and download that SuperSU version for TWRP. Dont extract, just put it on your SD card for the tablet.
Step 2: Doing stuff.
Install samsung drivers, extract Odin to your computer and put the SuperSU file on your SD card for the tablet.
(To avoid confusion about using the Volume rocker switch, I'll refer to side closest to POWER button as LEFT/Volume DOWN and side away from power switch as RIGHT/VolumeUP. )
1: Turn off the tablet and restart it on download mode. To enter download mode, press Power Button + Volume Right. When the warning appears press Volume Left to enter download mode.
2: Now open Odin3 1.85, click PDA, select the TWRP .tar file you downloaded.
3: Make sure to uncheck the "Auto Reboot" option. The only checked thing must be "F. Reset Time".
4: Connect usb cable to tablet. Press start. When it finishes, the box will turn green and says "pass!" you can remove the cable.
5: Now press Power button + Volume Left. Keep pressing it, the tablet should restart and when the samsung galaxy tab 2 screen appears, let go of the power button, but keep pressing Volume Left until the TWRP recovery screen appears.
6: Now inside TWRP recovery menu, press Install. On the top part of the screen press Storage and and change to external storage or SD card. Now select the SuperSU file and install it by swiping that thing. After it install and says successful, press reboot.
Congratulations ! Now you have successfully rooted your tablet and you have a permanent custom recovery ! You can now install a custom rom, etc.
Some notes:
I used TWRP recovery because i used it on my smartphone. So thats what I learned to use, so I used it on the tablet too. Feel free to use other custom recovery and adapt the tutorial for it.
It worked for me. If it doesn't work for you, or something is failing on some step, try to read everything again and re-do.
Credits:
* I based this on this topic and its replys (the last comment on this page.)
* Also credits for the Odin3 creator, SuperSU creator and TWRP team.
I just put together things from here and there, but without this persons, creators and stuff, we would not be able to make this happen.

[Guide]How to root Samsung Galaxy C9 pro (SM-C9000)

Hi! After struggling in rooting my C9 pro (SM-C9000, TGY) due to the lack of a proper guide, I decided to provide my guide to the community.
Of course, I don't take responsibility for damages etc. etc. Read the entirety of the guide before doing anything.
Useful shortcuts: Holding down power+volume down for a couple seconds force reboots from almost anywhere. Vol up+home+power while booting boots into recovery. Vol down+home+power boots into download (odin) mode.
Step 1) Fetch the required files(sorry I can't post direct links):
Nougat 7.1.1 firmware from sammobile
Oreo 8.0 firmware from sammobile
Odin https://www.xda-developers.com/update-firmware-any-samsung-phone/
Magisk Manager https://www.xda-developers.com/how-to-install-magisk/ (The link that says "Download the latest Magisk Manager APK here")
ADB https://www.xda-developers.com/install-adb-windows-macos-linux/
CROM Service apk from apkmirror
Step 2) Prepare the files
Unlock developer options on your phone by spamming Build Number in Settings> About Phone> Software Information. Enable USB debugging from developer options. Connect your phone to your PC via cable. Extract ADB (platform-tools) on your desktop (or other location). Extract Oreo firmware. There should be 5 files. Copy the one that starts with AP into platform-tools folder. Open the platform-tools folder. Hold down shift and right click inside the folder. Choose "Open PowerShell window here" from the context menu. Type or copy-paste
Code:
.\adb devices
to start ADB. On your phone, check "always allow on this PC" and click OK when prompted. Enter the code again and check if a device appears on the list. Then type
Code:
.\adb push AP_C9000ZHU1CSC1_CL14667562_QB22709761_REV00_user_low_ship_MULTI_CERT_meta.tar.md5 /sdcard/
.(Change the name of the file corresponding to yours. You can change the destination to another folder in your phone. Ex. /sdcard/download/) This will transfer the file from your PC to your phone. Do not drag and drop the file. This might corrupt it, causing a bootloop upon installiation. (Happened to me initially. Recovered & used the push command to get it to work.). Transfer Magisk Manager's apk to your phone or download it directly from your phone(you can drag and drop this one, as it won't install if corrupted(it won't corrupt)). Install Magisk Manager on the phone(Enable sideloading if asked). In the app, touch the topmost install button and touch install again in the next screen. You will have two options: "Download zip only" and "Select and patch a file". Choose "Select and patch a file", then locate the AP file you transferred to the device. Magisk manager will patch the file and generate magisk_patched.tar in /sdcard/download/. In ADB, type
Code:
.\adb pull /sdcard/download/magisk_patched.tar
This will transfer it to the platform-tools folder. Again, don't use windows explorer to transfer. That will most certainly corrupt the file.
Step 2.5) Backup
Backup your data (you can use smart switch desktop program paired with mobile app to backup most of the stuff). Remove your google account from the device.
Step 3) Install Nougat 7.1.1
Extract Nougat 7.1.1 firmware. Extract odin. Run Odin.exe (might have version in name). Click OK. Factory reset your phone (You can do so from settings or recovery mode.). After the reset, reboot into download mode. It will ask if you're sure you want to install unofficial software, choose continue (If I don't recall incorrectly, the button for that was vol up). Plug your phone into your PC. Odin log should say "added!!" and you should see your device in one of the rectangles above. Now select the tar.md5 files extracted from the 7.1.1 firmware. Click the BL button, locate the BL_etcetc.tar.md5 file, click open. It will check the md5 for a second then let you click the next button. After choosing the BL(bootloader), AP(system), CP(radio) and CSC(localization) files (USERDATA button should remain empty, HOME_CSC file has no use) make sure only F.reset time and auto reboot are selected in options. Click start to begin. After flashing, it will do another factory reset and show you the setup.
Step 4) Unlock Bootloader
Skip everything in setup, then unlock develper options and you should see "OEM Unlocking" option that was removed in OREO firmware in there. Enable it. Next transfer the CROM service apk to your device (or download it directly). Install the app. Open it. Unlock the bootloader. (This step is required because C9000 is a Chinese phone)
Step 5) Install Oreo again
Boot into download and connect to odin. You can use the reset button to empty the buttons. Now select BL, CP and CSC files from the extracted oreo firmware. For AP, choose magisk_patched.tar . Start. If the installiation fails, you didn't unlock the Bootloader properly. The phone will reboot and factory reset a couple times. When it boots up, you'll have magisk installed.
Step 6) Things to do after rooting(optional)
First of all, magisk can hide root from Google, but not Samsung. Samsung Health, Knox secure container, Maximum power saving mode and Samsung pay won't work after you root. NFC will keep turning on on its own unless you uninstall Samsung pay. A samsung package (I'm not sure about the name but I think it was security log agent) will keep sending an unblockable notification offering to unroot. Uninstall that too, and you'll have a stable experience.
Recovering from fails:
If download mode refuses to install because of unofficial binaries, the bootloader isn't properly unlocked. Wait a couple seconds and force reboot with the key combination. Since it couldn't flash the system, that should reboot back to download mode (or recovery. in that case, choose "reboot to bootloader"). Install the official firmware, unlock bootloader and try again.
If the magisk_patched.tar file gets corruped and you flash the corrupted file successfully, your device will get into a bootloop. After the install, odin orders the phone to reboot into recovery to factory reset, but since the system image is corrupted, it won't be able to boot and produce a kernel panic. This will cause the phone to reboot, which will fail and cause it to try to reboot again. Since the phone doesn't get past the splash screen, this bootloop cannot be interrupted by button shortcuts. You should wait for the battery to die out for the bootloop to end. (It should take a day at max. Wrap a towel around it to block the vibration sounds if you want) After battery gets depleted, you need to perform a quick maneuver. You should plug the phone into a power supply (preferably your computer) while holding down volume down+home+power buttons. If you do it right, it will boot into download mode. (Otherwise, it will bootloop again. Simply unplug, wait for it to stop and try again) Flash the official firmware and repatch the AP file. Just in case you run into this issue, I recommend having less than 10% charge in your phone while flashing, just to make the wait time shorter.
Important: Check your firmware's baseband version from settings before flashing. In C9000ZHU1CSC1, CSC1 is the system and U1 is the bootloader version. Compare the bootloader version to the firmware you're going to flash and make sure they match. You can't downgrade bootloader versions. Flashing a previous version will brick your phone. (Probably permanently) This shouldn't be an issue since sm-C9000 has only one bootloader version, but check it anyways just to be sure.
Lojcs said:
Hi! After struggling in rooting my C9 pro (SM-C9000, TGY) due to the lack of a proper guide, I decided to provide my guide to the community.
Of course, I don't take responsibility for damages etc. etc. Read the entirety of the guide before doing anything.
Useful shortcuts: Holding down power+volume down for a couple seconds force reboots from almost anywhere. Vol up+home+power while booting boots into recovery. Vol down+home+power boots into download (odin) mode.
Step 1) Fetch the required files(sorry I can't post direct links):
Nougat 7.1.1 firmware from sammobile
Oreo 8.0 firmware from sammobile
Odin https://www.xda-developers.com/update-firmware-any-samsung-phone/
Magisk Manager https://www.xda-developers.com/how-to-install-magisk/ (The link that says "Download the latest Magisk Manager APK here")
ADB https://www.xda-developers.com/install-adb-windows-macos-linux/
CROM Service apk from apkmirror
Step 2) Prepare the files
Unlock developer options on your phone by spamming Build Number in Settings> About Phone> Software Information. Enable USB debugging from developer options. Connect your phone to your PC via cable. Extract ADB (platform-tools) on your desktop (or other location). Extract Oreo firmware. There should be 5 files. Copy the one that starts with AP into platform-tools folder. Open the platform-tools folder. Hold down shift and right click inside the folder. Choose "Open PowerShell window here" from the context menu. Type or copy-paste to start ADB. On your phone, check "always allow on this PC" and click OK when prompted. Enter the code again and check if a device appears on the list. Then type .(Change the name of the file corresponding to yours. You can change the destination to another folder in your phone. Ex. /sdcard/download/) This will transfer the file from your PC to your phone. Do not drag and drop the file. This might corrupt it, causing a bootloop upon installiation. (Happened to me initially. Recovered & used the push command to get it to work.). Transfer Magisk Manager's apk to your phone or download it directly from your phone(you can drag and drop this one, as it won't install if corrupted(it won't corrupt)). Install Magisk Manager on the phone(Enable sideloading if asked). In the app, touch the topmost install button and touch install again in the next screen. You will have two options: "Download zip only" and "Select and patch a file". Choose "Select and patch a file", then locate the AP file you transferred to the device. Magisk manager will patch the file and generate magisk_patched.tar in /sdcard/download/. In ADB, type This will transfer it to the platform-tools folder. Again, don't use windows explorer to transfer. That will most certainly corrupt the file.
Step 2.5) Backup
Backup your data (you can use smart switch desktop program paired with mobile app to backup most of the stuff). Remove your google account from the device.
Step 3) Install Nougat 7.1.1
Extract Nougat 7.1.1 firmware. Extract odin. Run Odin.exe (might have version in name). Click OK. Factory reset your phone (You can do so from settings or recovery mode.). After the reset, reboot into download mode. It will ask if you're sure you want to install unofficial software, choose continue (If I don't recall incorrectly, the button for that was vol up). Plug your phone into your PC. Odin log should say "added!!" and you should see your device in one of the rectangles above. Now select the tar.md5 files extracted from the 7.1.1 firmware. Click the BL button, locate the BL_etcetc.tar.md5 file, click open. It will check the md5 for a second then let you click the next button. After choosing the BL(bootloader), AP(system), CP(radio) and CSC(localization) files (USERDATA button should remain empty, HOME_CSC file has no use) make sure only F.reset time and auto reboot are selected in options. Click start to begin. After flashing, it will do another factory reset and show you the setup.
Step 4) Unlock Bootloader
Skip everything in setup, then unlock develper options and you should see "OEM Unlocking" option that was removed in OREO firmware in there. Enable it. Next transfer the CROM service apk to your device (or download it directly). Install the app. Open it. Unlock the bootloader. (This step is required because C9000 is a Chinese phone)
Step 5) Install Oreo again
Boot into download and connect to odin. You can use the reset button to empty the buttons. Now select BL, CP and CSC files from the extracted oreo firmware. For AP, choose magisk_patched.tar . Start. If the installiation fails, you didn't unlock the Bootloader properly. The phone will reboot and factory reset a couple times. When it boots up, you'll have magisk installed.
Step 6) Things to do after rooting(optional)
First of all, magisk can hide root from Google, but not Samsung. Samsung Health, Knox secure container, Maximum power saving mode and Samsung pay won't work after you root. NFC will keep turning on on its own unless you uninstall Samsung pay. A samsung package (I'm not sure about the name but I think it was security log agent) will keep sending an unblockable notification offering to unroot. Uninstall that too, and you'll have a stable experience.
Recovering from fails:
If download mode refuses to install because of unofficial binaries, the bootloader isn't properly unlocked. Wait a couple seconds and force reboot with the key combination. Since it couldn't flash the system, that should reboot back to download mode (or recovery. in that case, choose "reboot to bootloader"). Install the official firmware, unlock bootloader and try again.
If the magisk_patched.tar file gets corruped and you flash the corrupted file successfully, your device will get into a bootloop. After the install, odin orders the phone to reboot into recovery to factory reset, but since the system image is corrupted, it won't be able to boot and produce a kernel panic. This will cause the phone to reboot, which will fail and cause it to try to reboot again. Since the phone doesn't get past the splash screen, this bootloop cannot be interrupted by button shortcuts. You should wait for the battery to die out for the bootloop to end. (It should take a day at max. Wrap a towel around it to block the vibration sounds if you want) After battery gets depleted, you need to perform a quick maneuver. You should plug the phone into a power supply (preferably your computer) while holding down volume down+home+power buttons. If you do it right, it will boot into download mode. (Otherwise, it will bootloop again. Simply unplug, wait for it to stop and try again) Flash the official firmware and repatch the AP file. Just in case you run into this issue, I recommend having less than 10% charge in your phone while flashing, just to make the wait time shorter.
Important: Check your firmware's baseband version from settings before flashing. In C9000ZHU1CSC1, CSC1 is the system and U1 is the bootloader version. Compare the bootloader version to the firmware you're going to flash and make sure they match. You can't downgrade bootloader versions. Flashing a previous version will brick your phone. (Probably permanently) This shouldn't be an issue since sm-C9000 has only one bootloader version, but check it anyways just to be sure.
Click to expand...
Click to collapse
Have you tried this method and phone working fine will there will be any problem if i use this method for rooting c9000?
khankk42 said:
Have you tried this method and phone working fine will there will be any problem if i use this method for rooting c9000?
Click to expand...
Click to collapse
Yes, I did root my SM-C9000 using this method, and it is working nicely. Obviously I lost access to Secure Folder and Samsung Pay. You should be able to install the Play Store version of Samsung Health. Maximum Power Saving froze the phone the first two times I enabled it, but it's working fine now. One unexpected caveat is that mobile hotspot started to turn itself off if mobile data is enabled even though my carrier has no restrictions on using hotspot. You can't share your data connection using Bluetooth or usb cable neither. You can still use the hotspot for creating a local network. Other than those, I didn't experience any problems after rooting. While I was rooting, I did the mistake of using MTP to transfer the image and as a result my phone bootlooped for half a day but if you follow the instructions, that won't be a problem.
Of course, I don't guarantee anything and don't take responsibility, but there is no reason anything should go wrong.
My base band R16NW.C9000ZHU1CSC1, model number SM-C9000, android 8.0.0...
I have never rooted any phones in my life. What should i do? I search on internet but i didnt found any spesific things about "R16NW.C9000ZHU1CSC1" can you help me? Those options will work for me to ?
otocu said:
My base band R16NW.C9000ZHU1CSC1, model number SM-C9000, android 8.0.0...
I have never rooted any phones in my life. What should i do? I search on internet but i didnt found any spesific things about "R16NW.C9000ZHU1CSC1" can you help me? Those options will work for me to ?
Click to expand...
Click to collapse
Sorry for responding late. Yes, that is the exact model that I have and rooted using the method in the post. If you feel confident, you can follow trough it and root your phone. You can grab the required firmware from Sammobile. Keep in mind that after rooting some features might stop working (like hotspot and knox-related features). Good luck!
I got the same model of Samsung phone. I follow the steps but till step five, when i press open the files in odin and press start button, the odin will disappear in my computer. Then i try again and it failed. My phone shows: unsuppoted dev types. Here are my photos. Do you have any ideas? And i dunno how can i redo it again to root my phone. Would love to see helps from you, thanks!
cherrio128 said:
I got the same model of Samsung phone. I follow the steps but till step five, when i press open the files in odin and press start button, the odin will disappear in my computer. Then i try again and it failed. My phone shows: unsuppoted dev types. Here are my photos. Do you have any ideas? And i dunno how can i redo it again to root my phone. Would love to see helps from you, thanks!
Click to expand...
Click to collapse
Sorry for the late response. Searching that on the internet, it seems you might be using an old version of Odin. Please make sure you're using 3.13.1 and try again

SM-X200 (Galaxy Tab A8) Root Guide

New to this community I hope this post is welcome here. Thanks to many of you I got a successful first time root and thought I would make a decent guide for others that stumble across this eventually.
This guide is for Windows only. I'm sure it would work similarly on Linux, but this is specific to Windows.
I AM NOT RESPONSABLE FOR ANY DAMAGE OR BRICKED DEVICE. That is always a risk you take with rooting, altering any software/firmware. This method did work for me, and if followed correctly it should work for you. Make sure you are using the same device this guide is for. That all being said, if anything goes wrong, this device is very easy to fix bootloops, soft bricks etc. Carry on.
YOU WILL LOSE ALL YOUR DATA AND YOUR TABLET WILL BE RESET TO FACTORY DEFAULT!! BACKUP ANYTHING YOU DONT WANT TO LOSE BEFORE STARTING THIS ROOT.
YOU WILL NEED A COMPUTER. This is NOT a hardware only root, in this guide, again, we will be using Windows 10.
Before starting anything, this will be the software list you need to download and install before moving forward...
The latest release of Magisk: GitHub - topjohnwu/Magisk: The Magic Mask for Android v.25.2 was the latest release at the time of this post, it might be updated when you are reading this. It should still work the same.
Odin: https://forum.xda-developers.com/attachments/odin3-v3-14-1-zip.5158505/ this should be a direct download link. If you dont like that, here is a link to the XDA fourm itself, make sure to download the Odin3 3.14.1.zip, ( 3.13.1.zip is not a link, reddit just highlights it because of the .zip, you just need to scroll down and find it in the forum, should be 1st or second in the list) NOT THE PATCHED VERSION.
The Firmware for your device (SM-X200) This is where I got mine, mind you it's the USA version: https://samfw.com/firmware/SM-X200/XAR/X200XXU1AVC1 If you are out of the states, there is many other sources for your exact firmware version, just type the second half of your build number (starting with "X200...etc.' into the browser followed by firmware then "download". The build number can be found in the software information inside of the "About tablet" section at the bottom of your settings.
The Samsung USB drivers: Samsung Android USB Driver | Samsung Developers You will need these to ensure a proper connection between your PC and tablet
And finally, this is optional, this already patched boot.img file already converted to .tar: https://drive.google.com/file/d/1Rm4BPaIVXWClhjKFencRnheJlDB3RRVm/view This is a working boot file, at least for me and many others on XDA, feel free to make your own if you wish, it will be explained in the guide below.
P.S Using the boot file above will save you some time and may help you avoid errors or crashes inside of odin or on your tablet. Also, better for those not as experienced.
The Guide now starts below.
Enable Dev options. (This is done by going into the "About Tablet" section at the very bottom of your settings, clicking "Software information", then clicking build number multiple times until a prompt shows up saying you are now a developer, or have unlocked dev settings.)
Enable OEM unlock inside of Developer settings.
Power off device, then hold both volume up and down buttons and plug your tablet into your PC to boot into download menu
Hold volume up once in download menu, to start OEM unlock prosses
When unlocked, the device with automatically factory reset
Set up device, Enable Wi-Fi either during or after setup prosses.
Re-Enable dev settings (as we did in step #1), and make sure "Enable OEM unlock" Is on and or grayed out.
Download latest firmware for your device and extract it using 7zip, (Link for firmware is at the begining of this guide) there should now be a list of 4 files starting with BL_, AP_, CSC_OMC, and HOME_CSC. (We won't be using HOME_CSC, more on that later).
Using Odin, install the AP BL and CSC . In the BL slot, click the BL, then go to the extracted firmware from earlier and select the file the file that starts with "BL_X200". Then give it a second to load in, move to the AP section. Click AP, then select the file from the extracted file again, that starts with "AP". And for CSC, select the file "CSC_OMC..." Not the "CSC_HOME..." After all the files are in the correct slots, click Start at the bottom of the Odin3 application.
Once odin is finished, you need to boot back into stock OS by holding down volume and power button to get out of download menu, if prompted to push power button during boot, do so.
Go through the setup again, enable Wi-Fi and check and make sure OEM unlock is still grayed out and enabled.
Download Magisk From there official GitHub on to your tablet (Link above)
Install Magisk
IMPORTANT!!
This is where you have two options, either skip these steps, and use the provided boot.img file, or make your own (this is harder, you may run into errors and issues, but most of you have been doing this much longer than me, this is just a guide from someone new to this, so I thought my incite may be easier to understand) SKIP STEPS #14-#21 if you chose to download the provided boot.tar file at the beginning of this guide. (I would recommend reading them still, because understanding the prosses will help with a successful root, whether or not you choose to make your own boot.img file, this advice is from experience. Knowledge is power, right?
14. If you choose to make your own patched boot file with magisk, go back to your PC, extract the "AP_X200..." file inside of the firmware file you already extracted, send that file to your Tab A8 (again this is for the SM-X200 ONLY!) via plugging your tablet into your laptop (MAKE SURE ITS POWERED ON AND UNLOCKED)
14.5. You will be prompted to allow data transfer between your tablet and the PC something like " allow this PC to access...etc". Allow it. Open your tablets root storage from the file manager on your windows computer. This PC, then select your tablet. You should see the root files.
15. Return back to the folder of the extracted AP_X200... file you extracted previously; it should be in a standard file format now, not a .tar file
16. Find the "Boot.img" file, copy it and return to your tablets root file
17. Paste the boot.img file you copied from the extracted AP_X200... file, into the root directory of your tablet. Then unplug your tablet and return to your tablet for the next step.
18. Open magisk, click install on the top option, to the right of "Magisk" NOT THE ONE THAT SAYS "App". Then click "Select and patch file" find your "boot.img" file you previously copied over to your tablet in step #16/#17, its often in recent files, but should always be in the tab "Galaxy tab A8" You can find that tab by tapping the hamburger icon (three horizontal lines) in the top left corner. Once there, select the "boot.img" file.
19. Once you find your file, click "Let's go" back in the main Magisk screen
20. Once completed, it should show that it installed the patched boot.img file in your tablets download directory. You have now successfully patched the boot file. If you get an error or a crash, try again. If you keep running into errors, make sure your file is the correct "boot.img" file. Don't be shy, re-read the guide, start over, if necessary, we haven't gone too far yet to try again.
21. Plug your tablet back into your PC, go back to your tablets root directory via your computers file manager, open whichever file Magisk installed its patched "boot.img" file (it should be in the downloads folder of your tablets root directory) copy it to your computer. You can move it anywhere but if you move it back to where the other firmware files that we downloaded and extracted are, you will need to right click the file, hover over 7zip, then click "Add to archive". Then, in the section of the options where it says "archive format" change the file type to tar. You will need to do this step either way, but make sure it's done BEFORE moving it to the other files we extracted earlier, because it will prompt you to replace the file, we don't want to do that.
22. Now take your tablet, unplug it if it's still plugged in, and power off. Once it's powered down completely, hold both the volume up and down buttons like earlier to get into download mode when unlocking the OEM, and plug it into the PC (WHILE STILL HOLDING THE VOLUME BUTTONS UNTIL THE MENU APPEARS). Once the download menu appears, (should be familiar by now) click once on the up-volume button, and you will now be ready to download your files to root your device! Yayy!
23. Open Odin3, and it should have on the left a, "Log" info box, "<ID: somthing/somthing> Added! ("something/something will be numbers, just make sure it says added, that means it sees your Tablet is in download mode and ready for your patched files"
24. You will see 4 slots to the right of the Log page inside of Odin. They will read (top to bottom) "BL", "AP", "CP", "CSC, and "USER DATA". Only BL, AP, and CSC will be used in this prosses, and should be the only ones with check marks to the left of them. If the check marks are not checked, check them.
25. Now, (don't worry almost done!) In the BL slot, click the BL box, go to the extracted firmware from earlier (Step 8) and select the file the file that starts with "BL_X200". Then give it a second to load in, move to the AP section. Select it, then find your boot.img file you made using magisk, or downloaded via the link at the top of this post. Select it, and now move on to CSC. Click it, find your "CSC_OMC" file (you might get away with using the CSC_HOME..." file, but at this point your tablet shouldn't have anything you want to save, as it should have been wiped when unlocking the bootloader, so just take my advice and use the stock CSC_OMC file.
26. Now, you should have files in the BL slot, the AP slot, and the CSC slot. Double check and make sure there are nothing in the "CP" slot, nor the "USERDATA" slot. Once you are ready, and all files are in the correct slots, and your tablet is ready to start downloading, (should have an empty progress bar under the "cancel" instructions on your tablet screen) go ahead and click " Start" at the bottom of the Odin application.
27. This prosses should be relatively quick, less than a minute, but in my many tries, sometimes it was quick, other times it took a minute or two. Once done, the Odin app on your PC should read "Pass" in a green box towards the top right corner of the app, under the Odin logo.
28. Proceed to shut down the device, by holding down on the Power and Volume Down keys, once the screen goes black, lift off the power AND volume down key, and immediately press down on the Power key (again) and the Volume UP this time. (Some guides have said it's not necessary to release from the power key when the black screen starts, and to only change from the volume down key to the volume up key, but in my experience, this may lead to a bootloop *Don't worry, it's fixable*. So, I recommend you lift off both and then immediately start clicking the power *again* and volume up) This should bring you into the system recovery menu. Use the volume down key to scroll down, and the volume up key for up, the power button is to select the option in the menu. Scroll down to "Wipe data/factory reset" and select it. Confirm when prompted, and it will reset your device using the firmware you just installed.
29. Setup as usual, enable the Wi-Fi, double check that OEM unlock is still enabled and grayed out in the developer menu (you will have to re enable the dev menu). Then go to Chrome, type in "Root checker apk" and download the apk, should be available in the first or second result of Google. MAKE sure to allow Chrome downloads, it will prompt you when the apk is downloaded. Open it, and check for Root. This is when I got a pop-up from Magisk, but it may happen at any time. Whenever it happens, just follow its instructions, it will reboot your tablet, then when it's powered back on, go back to root checker. When you check for root, wait a couple seconds, a pop up should show up with a count down, allow it, and it will show that you...are now...ROOTED!
YAY, you did it congratulations. This took me probably 12 hours and many different forums, because there has been a great debate on how to do this properly, but from what I've experienced this is all the right info and guides shoved into one. Many thanks to the XDA forums, and especially user "tofor" on the XDA forums, for the patched boot file when people where still having issues making their own.
I may make a YouTube video explaining all this, but I'm not super into the idea. We will see, depends how this post does and if people still need help. Again, I'm not a pro when it comes to rooting. I'm a nerd, I know my way around tech, but I was an iPhone kid, so I grew up with jailbreaking, which was 100% easier cause most the work was done for you. That all being said, I'm sure I missed some terms, or dint explain something perfectly, so please, to all of you who are much more experienced with this, FEEL FREE TO CORRECT ME!! Have any questions, I'll try to get to them, but I'm not super active. If I don't get to you, I'm sure somebody will. I really hope this helps; this was hell for me.
Great job on the guide! Worked perfectly for me on the 1st try!
Thanks for the guide, also there is TWRP out there now for this tablet
[RECOVERY][UNOFFICIAL] TWRP 3.7.0 for 2021 Galaxy Tab A8 10.5 [SM-X200]
Notes: What's posted below is a work in progress, but it should suffice to unblock efforts to build custom ROMs for this impressive tablet. This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you...
forum.xda-developers.com
On step 25 for "Then give it a second to load in, move to the AP section. Select it, then find your boot.img" when I try to add the boot.img in the AP section it does not show the boot.img for me to select like it does with the other files.
Edit: I found out I needed to select the .tar and not extract and select the boot.img
Edit: Rooted doing what I need now! Thank you for such an awesome tutorial!
Sorry new to rooting here, for Step 8 do I need to go to the blue download screen for Odin to work? My odin is stuck on setupconnection
I only want to change the ''tap'' sounds when the display is touched. Do I really need to do all of this (root access) or is there an easier way to do that? This seems like a lot of work and I use this tablet regularly.
Hello and Thank you for your work.
Do you think your guide works for android 12? knowing that I found my version on samfw.com, namely the X200XXU1BVI6 version (CSC European Union). Thank you.
SerielRipou said:
Hello and Thank you for your work.
Do you think your guide works for android 12? knowing that I found my version on samfw.com, namely the X200XXU1BVI6 version (CSC European Union). Thank you.
Click to expand...
Click to collapse
yes the only thing i did was
extract the boot.img from the tar
put it on my phone patched it with magisk
put the new patched file on my pc.
created a new ap tar using all the old files it had except i added the new patched boot.img
after all files are in i created the .tar
used the same BL_X200XXU1BVI6_X200XXU1B
used the new ar has all original files except the modified boot.img
used the same CSC_XAR_X200XAR1BVI6
it worked super su says its rooted. been at it all morning coudl not have done it without this guide
Got as far as step 28, where things went a bit off.
After the download from odin was complete, the device immediately shut down and starting going through a bootloop without me having touched power or volume at all.
Then after getting into the system recovery menu and doing a factory reset, it didn't reset the device with the firmware and when trying to power it on it just remained in the same bootloop as before doing the factory reset.
I'm using the boot.img file with firmware EUX - SMX200XXS1BVJ1 which I'm pretty confident is the correct version as it matches the build number on the device.
This is what I get on the system recovery after doing a factory reset.
at step 28 your supposed to
"Wipe data/factory reset" and select it. Confirm when prompted, and it will reset your device using the firmware you just installed.
it reinstalls the tablets new firmware
edit - it wont just start up the tablet like everything is brand new out of the box. thats why you need to "Wipe data/factory reset
I did factory reset. That's what produced the lines after -- Wiping data...
After factory resetting it doesn't seem to install anything and just goes right back to the system recovery menu. Rebooting the device at that point just has it going back into a bootloop.
Got it working.
Had to redownload the firmware from step 8 onto the device and then use magisk to make my own boot.img
Things to note in case anyone needs them is that the file magisk makes might not be called boot.img, in which case you do need to rename it to boot.img for it to work and also if you get stuck with being unable to access the download mode on your device, you can use FRP HiJacker to fix it.
I'm also stuck on "SetupConnection" in Odin. I enabled USB debugging, but that didn't seem to help.
Worked, thanks for this tutorial and your work with it.
regards
mkpcxxl
Hello, I conjured up the Android 13 on the A8 today. But unfortunately I can't get it rooted. The root checker says it's not rooted. What do I have to do to make it count as rooted again?
I got it solved myself and now have Android 13 on Samsung A8 (x200) and rooted :-D
Worked for me.
I initially had issues and thought I had bricked it, but a combination of Odin issues and possibly cable/bad firmware issues caused the problems and not this guide.
Nice one.
Sync999 said:
New to this community I hope this post is welcome here. Thanks to many of you I got a successful first time root and thought I would make a decent guide for others that stumble across this eventually.
This guide is for Windows only. I'm sure it would work similarly on Linux, but this is specific to Windows.
I AM NOT RESPONSABLE FOR ANY DAMAGE OR BRICKED DEVICE. That is always a risk you take with rooting, altering any software/firmware. This method did work for me, and if followed correctly it should work for you. Make sure you are using the same device this guide is for. That all being said, if anything goes wrong, this device is very easy to fix bootloops, soft bricks etc. Carry on.
YOU WILL LOSE ALL YOUR DATA AND YOUR TABLET WILL BE RESET TO FACTORY DEFAULT!! BACKUP ANYTHING YOU DONT WANT TO LOSE BEFORE STARTING THIS ROOT.
YOU WILL NEED A COMPUTER. This is NOT a hardware only root, in this guide, again, we will be using Windows 10.
Before starting anything, this will be the software list you need to download and install before moving forward...
The latest release of Magisk: GitHub - topjohnwu/Magisk: The Magic Mask for Android v.25.2 was the latest release at the time of this post, it might be updated when you are reading this. It should still work the same.
Odin: https://forum.xda-developers.com/attachments/odin3-v3-14-1-zip.5158505/ this should be a direct download link. If you dont like that, here is a link to the XDA fourm itself, make sure to download the Odin3 3.14.1.zip, ( 3.13.1.zip is not a link, reddit just highlights it because of the .zip, you just need to scroll down and find it in the forum, should be 1st or second in the list) NOT THE PATCHED VERSION.
The Firmware for your device (SM-X200) This is where I got mine, mind you it's the USA version: https://samfw.com/firmware/SM-X200/XAR/X200XXU1AVC1 If you are out of the states, there is many other sources for your exact firmware version, just type the second half of your build number (starting with "X200...etc.' into the browser followed by firmware then "download". The build number can be found in the software information inside of the "About tablet" section at the bottom of your settings.
The Samsung USB drivers: Samsung Android USB Driver | Samsung Developers You will need these to ensure a proper connection between your PC and tablet
And finally, this is optional, this already patched boot.img file already converted to .tar: https://drive.google.com/file/d/1Rm4BPaIVXWClhjKFencRnheJlDB3RRVm/view This is a working boot file, at least for me and many others on XDA, feel free to make your own if you wish, it will be explained in the guide below.
P.S Using the boot file above will save you some time and may help you avoid errors or crashes inside of odin or on your tablet. Also, better for those not as experienced.
The Guide now starts below.
Enable Dev options. (This is done by going into the "About Tablet" section at the very bottom of your settings, clicking "Software information", then clicking build number multiple times until a prompt shows up saying you are now a developer, or have unlocked dev settings.)
Enable OEM unlock inside of Developer settings.
Power off device, then hold both volume up and down buttons and plug your tablet into your PC to boot into download menu
Hold volume up once in download menu, to start OEM unlock prosses
When unlocked, the device with automatically factory reset
Set up device, Enable Wi-Fi either during or after setup prosses.
Re-Enable dev settings (as we did in step #1), and make sure "Enable OEM unlock" Is on and or grayed out.
Download latest firmware for your device and extract it using 7zip, (Link for firmware is at the begining of this guide) there should now be a list of 4 files starting with BL_, AP_, CSC_OMC, and HOME_CSC. (We won't be using HOME_CSC, more on that later).
Using Odin, install the AP BL and CSC . In the BL slot, click the BL, then go to the extracted firmware from earlier and select the file the file that starts with "BL_X200". Then give it a second to load in, move to the AP section. Click AP, then select the file from the extracted file again, that starts with "AP". And for CSC, select the file "CSC_OMC..." Not the "CSC_HOME..." After all the files are in the correct slots, click Start at the bottom of the Odin3 application.
Once odin is finished, you need to boot back into stock OS by holding down volume and power button to get out of download menu, if prompted to push power button during boot, do so.
Go through the setup again, enable Wi-Fi and check and make sure OEM unlock is still grayed out and enabled.
Download Magisk From there official GitHub on to your tablet (Link above)
Install Magisk
IMPORTANT!!
This is where you have two options, either skip these steps, and use the provided boot.img file, or make your own (this is harder, you may run into errors and issues, but most of you have been doing this much longer than me, this is just a guide from someone new to this, so I thought my incite may be easier to understand) SKIP STEPS #14-#21 if you chose to download the provided boot.tar file at the beginning of this guide. (I would recommend reading them still, because understanding the prosses will help with a successful root, whether or not you choose to make your own boot.img file, this advice is from experience. Knowledge is power, right?
14. If you choose to make your own patched boot file with magisk, go back to your PC, extract the "AP_X200..." file inside of the firmware file you already extracted, send that file to your Tab A8 (again this is for the SM-X200 ONLY!) via plugging your tablet into your laptop (MAKE SURE ITS POWERED ON AND UNLOCKED)
14.5. You will be prompted to allow data transfer between your tablet and the PC something like " allow this PC to access...etc". Allow it. Open your tablets root storage from the file manager on your windows computer. This PC, then select your tablet. You should see the root files.
15. Return back to the folder of the extracted AP_X200... file you extracted previously; it should be in a standard file format now, not a .tar file
16. Find the "Boot.img" file, copy it and return to your tablets root file
17. Paste the boot.img file you copied from the extracted AP_X200... file, into the root directory of your tablet. Then unplug your tablet and return to your tablet for the next step.
18. Open magisk, click install on the top option, to the right of "Magisk" NOT THE ONE THAT SAYS "App". Then click "Select and patch file" find your "boot.img" file you previously copied over to your tablet in step #16/#17, its often in recent files, but should always be in the tab "Galaxy tab A8" You can find that tab by tapping the hamburger icon (three horizontal lines) in the top left corner. Once there, select the "boot.img" file.
19. Once you find your file, click "Let's go" back in the main Magisk screen
20. Once completed, it should show that it installed the patched boot.img file in your tablets download directory. You have now successfully patched the boot file. If you get an error or a crash, try again. If you keep running into errors, make sure your file is the correct "boot.img" file. Don't be shy, re-read the guide, start over, if necessary, we haven't gone too far yet to try again.
21. Plug your tablet back into your PC, go back to your tablets root directory via your computers file manager, open whichever file Magisk installed its patched "boot.img" file (it should be in the downloads folder of your tablets root directory) copy it to your computer. You can move it anywhere but if you move it back to where the other firmware files that we downloaded and extracted are, you will need to right click the file, hover over 7zip, then click "Add to archive". Then, in the section of the options where it says "archive format" change the file type to tar. You will need to do this step either way, but make sure it's done BEFORE moving it to the other files we extracted earlier, because it will prompt you to replace the file, we don't want to do that.
22. Now take your tablet, unplug it if it's still plugged in, and power off. Once it's powered down completely, hold both the volume up and down buttons like earlier to get into download mode when unlocking the OEM, and plug it into the PC (WHILE STILL HOLDING THE VOLUME BUTTONS UNTIL THE MENU APPEARS). Once the download menu appears, (should be familiar by now) click once on the up-volume button, and you will now be ready to download your files to root your device! Yayy!
23. Open Odin3, and it should have on the left a, "Log" info box, "<ID: somthing/somthing> Added! ("something/something will be numbers, just make sure it says added, that means it sees your Tablet is in download mode and ready for your patched files"
24. You will see 4 slots to the right of the Log page inside of Odin. They will read (top to bottom) "BL", "AP", "CP", "CSC, and "USER DATA". Only BL, AP, and CSC will be used in this prosses, and should be the only ones with check marks to the left of them. If the check marks are not checked, check them.
25. Now, (don't worry almost done!) In the BL slot, click the BL box, go to the extracted firmware from earlier (Step 8) and select the file the file that starts with "BL_X200". Then give it a second to load in, move to the AP section. Select it, then find your boot.img file you made using magisk, or downloaded via the link at the top of this post. Select it, and now move on to CSC. Click it, find your "CSC_OMC" file (you might get away with using the CSC_HOME..." file, but at this point your tablet shouldn't have anything you want to save, as it should have been wiped when unlocking the bootloader, so just take my advice and use the stock CSC_OMC file.
26. Now, you should have files in the BL slot, the AP slot, and the CSC slot. Double check and make sure there are nothing in the "CP" slot, nor the "USERDATA" slot. Once you are ready, and all files are in the correct slots, and your tablet is ready to start downloading, (should have an empty progress bar under the "cancel" instructions on your tablet screen) go ahead and click " Start" at the bottom of the Odin application.
27. This prosses should be relatively quick, less than a minute, but in my many tries, sometimes it was quick, other times it took a minute or two. Once done, the Odin app on your PC should read "Pass" in a green box towards the top right corner of the app, under the Odin logo.
28. Proceed to shut down the device, by holding down on the Power and Volume Down keys, once the screen goes black, lift off the power AND volume down key, and immediately press down on the Power key (again) and the Volume UP this time. (Some guides have said it's not necessary to release from the power key when the black screen starts, and to only change from the volume down key to the volume up key, but in my experience, this may lead to a bootloop *Don't worry, it's fixable*. So, I recommend you lift off both and then immediately start clicking the power *again* and volume up) This should bring you into the system recovery menu. Use the volume down key to scroll down, and the volume up key for up, the power button is to select the option in the menu. Scroll down to "Wipe data/factory reset" and select it. Confirm when prompted, and it will reset your device using the firmware you just installed.
29. Setup as usual, enable the Wi-Fi, double check that OEM unlock is still enabled and grayed out in the developer menu (you will have to re enable the dev menu). Then go to Chrome, type in "Root checker apk" and download the apk, should be available in the first or second result of Google. MAKE sure to allow Chrome downloads, it will prompt you when the apk is downloaded. Open it, and check for Root. This is when I got a pop-up from Magisk, but it may happen at any time. Whenever it happens, just follow its instructions, it will reboot your tablet, then when it's powered back on, go back to root checker. When you check for root, wait a couple seconds, a pop up should show up with a count down, allow it, and it will show that you...are now...ROOTED!
YAY, you did it congratulations. This took me probably 12 hours and many different forums, because there has been a great debate on how to do this properly, but from what I've experienced this is all the right info and guides shoved into one. Many thanks to the XDA forums, and especially user "tofor" on the XDA forums, for the patched boot file when people where still having issues making their own.
I may make a YouTube video explaining all this, but I'm not super into the idea. We will see, depends how this post does and if people still need help. Again, I'm not a pro when it comes to rooting. I'm a nerd, I know my way around tech, but I was an iPhone kid, so I grew up with jailbreaking, which was 100% easier cause most the work was done for you. That all being said, I'm sure I missed some terms, or dint explain something perfectly, so please, to all of you who are much more experienced with this, FEEL FREE TO CORRECT ME!! Have any questions, I'll try to get to them, but I'm not super active. If I don't get to you, I'm sure somebody will. I really hope this helps; this was hell for me.
Click to expand...
Click to collapse
what about android 13 on on sm-x200 is it same as these steps just use the tar for the android 13 build u r on? or no?
ignore this post.
So no root for android 13 ? if u find root could u share n ill do same if i fine a way.

Categories

Resources