For all you Indian Users, or anybody who owns a Portronics Limebox running GB; root and CWM has finally been achieved!
Disclaimer: I am not responsible if you end up bricking your device. This procedure has been known to work for my Limebox. Deviate from the procedure and you have no right to blame me....
After lots of hours of extensive searching (with absolutely no help from portronics), I found an exact match to our device: G-Box (See the Remote???). Our Device is a Rockchip Processor, specifically RK2918. Rockchip processors are known to lock down the /system partition with a filesystem called cramfs. Don't worry, that can be solved too!
Before we start, Understand the 3 modes you can set the device in:
1. Normal Power On (Self-Explanatory)
2. Recovery Mode (Stick a Pin in the Reset Hole and keep the Power Button pressed at the same time)
3. Flash Mode:
i. Disconnect the AC Power.
ii. Connect a USB Male to Male Cable in the LOWER PORT. (similar results don't come from the upper one). Connect the other end to the PC.
iii. Stick the Pin in the reset hole. Simultaneously, connect the AC Power.
iv. The device should turn on with a blue light and no display on the screen. The PC will detect the device. Use the flash mode drivers given below.
v. Flash Mode generally works in all conditions, even if it does not boot, unless you do something really stupid :fingers-crossed: !
Now onto the procedure!
Obtaining Root
1. As i mentioned earlier, our device is exactly similiar to 'G-Box'. See the thread here (on android forums) for all development pertaining to their device. Most of what I've mentioned here comes from this forum (Big thanks to all of them )
2. Download the Official Firmware here or a Modded Lite version here (credits to xzer0).
3. Download the img Unpacker (RK29xx ImageTools : big thanks to wendal!!)
4. Use the img Unpacker to unpack the Official/Modded Firmware. If you are downloading the Official, be sure to Pack the Firmware after unpacking, since it adds the root files to the image file then. You do not need to repack for the modded one, since that is pre-rooted.
5. The Firmware will be unpacked to a folder called 'Temp'. Ignore the folder 'System'.
6. Start the Flasher (RK29update.exe). Connect the device in Flash mode to your PC and install the drivers. RK29Update should detect the device (It will say 'Detected' or something like that at the bottom)
7. For Parameter, choose the parameter file inside the Temp folder. Do not touch the offset values AT ALL.
8. For Loader, choose the .bin file that has 'loader' in the file name (in the Temp folder). Let its offset be blank, if it is.
9. For all the remaining (except backup), point them to their respective files in the 'image' folder inside 'temp'.
10. Tick Mark all except Backup. Before Pressing Update, click Format. Let it finish and wait for the device to be re-detected.
11. Press Update and wait until it finishes and the device disconnects from your computer. (It may disconnect once or twice in between. Be patient. Look at the Log on the right side to be absolutely sure when to unplug it.)
12. Your device should immediately reboot into recovery. It will format /DATA, /CACHE and /uDisk. When it is done, it will reboot into Andoid. (Though the interface looks different, it is more or less an exact copy of the Portronics).
13. Enjoy your rooted Limebox!
Known Issues:
1. Moody at boot. Takes some time to show the 'ANDROID' text on the screen. Be patient.
2. Cant get into recovery on the modded firmware. The Recovery Mode trick causes it to simply switch off. No hassle, with Flash Mode, you have the best kind of recovery!
Optional Stuff (Be Careful. You have been warned. )
CWM Recovery
I technically do not encourage using CWM on this device because i've had bad experiences with it. But its nothing that can't be fixed with a re-flash. So.....the technique is simple. Obtain a recovery.img file (specifically for any RK2918 device) from here or here or anywhere you like. When you flash the new rom, in place of the recovery.img file in the \temp\image\ folder, choose this one. If additional files are given to flash, you can flash those too. However, like i said, there are complications, it may not always work. But if you face any issues, simply reflash with the official recovery.
Removing Apps
If you wish to remove apps from the Official or Modded firmware (which is difficult, since its locked down with cramfs), after unpacking the image, go into \system\app\, delete the apps you dont want and then repack (Important!). For some reason, I've never been able to add an app. You don't need to do it this way if you use the Ext3 Image (Read on!!!)
Ext3 FileSystem
So, as i mentioned earlier, you can get a system.img that is of ext3 filesystem instead of cramfs. Simply download the image file from here and use that for the same flashing procedure. (Credits to Finless (Bob) and Paincake)
Need someone for small testing!
Can somebody find the /backup folder in the root directory? What are the contents?
unable to detect limebox on my win7 64bit laptop
3. Flash Mode:
i. Disconnect the AC Power.
ii. Connect a USB Male to Male Cable in the LOWER PORT. (similar results don't come from the upper one). Connect the other end to the PC.
iii. Stick the Pin in the reset hole. Simultaneously, connect the AC Power.
iv. The device should turn on with a blue light and no display on the screen. The PC will detect the device. Use the flash mode drivers given below.
v. Flash Mode generally works in all conditions, even if it does not boot, unless you do something really stupid :fingers-crossed: !
Now onto the procedure!
Obtaining Root
1. As i mentioned earlier, our device is exactly similiar to 'G-Box'. See the thread here (on android forums) for all development pertaining to their device. Most of what I've mentioned here comes from this forum (Big thanks to all of them )
2. Download the Official Firmware here or a Modded Lite version here (credits to xzer0).
3. Download the img Unpacker (RK29xx ImageTools : big thanks to wendal!!)
4. Use the img Unpacker to unpack the Official/Modded Firmware. If you are downloading the Official, be sure to Pack the Firmware after unpacking, since it adds the root files to the image file then. You do not need to repack for the modded one, since that is pre-rooted.
5. The Firmware will be unpacked to a folder called 'Temp'. Ignore the folder 'System'.
6. Start the Flasher (RK29update.exe). Connect the device in Flash mode to your PC and install the drivers. RK29Update should detect the device (It will say 'Detected' or something like that at the bottom)
7. For Parameter, choose the parameter file inside the Temp folder. Do not touch the offset values AT ALL.
8. For Loader, choose the .bin file that has 'loader' in the file name (in the Temp folder). Let its offset be blank, if it is.
9. For all the remaining (except backup), point them to their respective files in the 'image' folder inside 'temp'.
10. Tick Mark all except Backup. Before Pressing Update, click Format. Let it finish and wait for the device to be re-detected.
11. Press Update and wait until it finishes and the device disconnects from your computer. (It may disconnect once or twice in between. Be patient. Look at the Log on the right side to be absolutely sure when to unplug it.)
12. Your device should immediately reboot into recovery. It will format /DATA, /CACHE and /uDisk. When it is done, it will reboot into Andoid. (Though the interface looks different, it is more or less an exact copy of the Portronics).
13. Enjoy your rooted Limebox!
Known Issues:
1. Moody at boot. Takes some time to show the 'ANDROID' text on the screen. Be patient.
2. Cant get into recovery on the modded firmware. The Recovery Mode trick causes it to simply switch off. No hassle, with Flash Mode, you have the best kind of recovery!
Optional Stuff (Be Careful. You have been warned. )
CWM Recovery
I technically do not encourage using CWM on this device because i've had bad experiences with it. But its nothing that can't be fixed with a re-flash. So.....the technique is simple. Obtain a recovery.img file (specifically for any RK2918 device) from here or here or anywhere you like. When you flash the new rom, in place of the recovery.img file in the \temp\image\ folder, choose this one. If additional files are given to flash, you can flash those too. However, like i said, there are complications, it may not always work. But if you face any issues, simply reflash with the official recovery.
Removing Apps
If you wish to remove apps from the Official or Modded firmware (which is difficult, since its locked down with cramfs), after unpacking the image, go into \system\app\, delete the apps you dont want and then repack (Important!). For some reason, I've never been able to add an app. You don't need to do it this way if you use the Ext3 Image (Read on!!!)
Ext3 FileSystem
So, as i mentioned earlier, you can get a system.img that is of ext3 filesystem instead of cramfs. Simply download the image file from here and use that for the same flashing procedure. (Credits to Finless (Bob) and Paincake)
Need someone for small testing!
Can somebody find the /backup folder in the root directory? What are the contents?[/QUOTE]
My apologies for the very late reply. As I recall, the drivers are for 32bit, have you repeated the steps on a 32bit machine? Did the pc attempt to recognize it?
huzefaid said:
3. Flash Mode:
i. Disconnect the AC Power.
ii. Connect a USB Male to Male Cable in the LOWER PORT. (similar results don't come from the upper one). Connect the other end to the PC.
iii. Stick the Pin in the reset hole. Simultaneously, connect the AC Power.
iv. The device should turn on with a blue light and no display on the screen. The PC will detect the device. Use the flash mode drivers given below.
v. Flash Mode generally works in all conditions, even if it does not boot, unless you do something really stupid :fingers-crossed: !
Now onto the procedure!
Obtaining Root
1. As i mentioned earlier, our device is exactly similiar to 'G-Box'. See the thread here (on android forums) for all development pertaining to their device. Most of what I've mentioned here comes from this forum (Big thanks to all of them )
2. Download the Official Firmware here or a Modded Lite version here (credits to xzer0).
3. Download the img Unpacker (RK29xx ImageTools : big thanks to wendal!!)
4. Use the img Unpacker to unpack the Official/Modded Firmware. If you are downloading the Official, be sure to Pack the Firmware after unpacking, since it adds the root files to the image file then. You do not need to repack for the modded one, since that is pre-rooted.
5. The Firmware will be unpacked to a folder called 'Temp'. Ignore the folder 'System'.
6. Start the Flasher (RK29update.exe). Connect the device in Flash mode to your PC and install the drivers. RK29Update should detect the device (It will say 'Detected' or something like that at the bottom)
7. For Parameter, choose the parameter file inside the Temp folder. Do not touch the offset values AT ALL.
8. For Loader, choose the .bin file that has 'loader' in the file name (in the Temp folder). Let its offset be blank, if it is.
9. For all the remaining (except backup), point them to their respective files in the 'image' folder inside 'temp'.
10. Tick Mark all except Backup. Before Pressing Update, click Format. Let it finish and wait for the device to be re-detected.
11. Press Update and wait until it finishes and the device disconnects from your computer. (It may disconnect once or twice in between. Be patient. Look at the Log on the right side to be absolutely sure when to unplug it.)
12. Your device should immediately reboot into recovery. It will format /DATA, /CACHE and /uDisk. When it is done, it will reboot into Andoid. (Though the interface looks different, it is more or less an exact copy of the Portronics).
13. Enjoy your rooted Limebox!
Known Issues:
1. Moody at boot. Takes some time to show the 'ANDROID' text on the screen. Be patient.
2. Cant get into recovery on the modded firmware. The Recovery Mode trick causes it to simply switch off. No hassle, with Flash Mode, you have the best kind of recovery!
Optional Stuff (Be Careful. You have been warned. )
CWM Recovery
I technically do not encourage using CWM on this device because i've had bad experiences with it. But its nothing that can't be fixed with a re-flash. So.....the technique is simple. Obtain a recovery.img file (specifically for any RK2918 device) from here or here or anywhere you like. When you flash the new rom, in place of the recovery.img file in the \temp\image\ folder, choose this one. If additional files are given to flash, you can flash those too. However, like i said, there are complications, it may not always work. But if you face any issues, simply reflash with the official recovery.
Removing Apps
If you wish to remove apps from the Official or Modded firmware (which is difficult, since its locked down with cramfs), after unpacking the image, go into \system\app\, delete the apps you dont want and then repack (Important!). For some reason, I've never been able to add an app. You don't need to do it this way if you use the Ext3 Image (Read on!!!)
Ext3 FileSystem
So, as i mentioned earlier, you can get a system.img that is of ext3 filesystem instead of cramfs. Simply download the image file from here and use that for the same flashing procedure. (Credits to Finless (Bob) and Paincake)
Need someone for small testing!
Can somebody find the /backup folder in the root directory? What are the contents?
Click to expand...
Click to collapse
tried on 32bit machine, the pc did'nt recognize it
please help
do i need to connect monitor with hdmi port to view flash mode.?
i have press reset pin and also powered on the device at same time, but my pc did'nt recognize it.i have also started rk29androidtool to check it it detects the device but no luck.
I finally found a way to root the myPhone Hammer AXE M LTE!!! You can use Magisk to patch the boot.img from the 1.0.3 OTA! See the attached thumbnails at the bottom.
My steps:
1) Upgrade to the latest OTA from myPhone (1.0.3). In the event that you can’t download it through your phone, I’ve uploaded it to MEGA: https://mega.nz/#!Ndw3TYrR!nozVRHC1M4ugn-_PKzC7tn1fAAV6w7bB7Iq2uRr8FHA
1a) I had to manually reboot into recovery to install the update. Power off the phone, hold power + PTT until you see the myPhone logo. Once you see the dilapidated robot, tap and hold power then vol + (in that order!!!).
2) The update should be on your external SDcard. Select it and wait for the install to finish.
3) After the install completes, reboot to your system and install the Magisk Manager: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
3a) If you want to use my patched boot and scatter, skip steps 4, 5, and 6 and go to step 7. Patched boot, Scatter, Magisk.apk and Stock Recovery: https://mega.nz/#!YAQ3BQyS!dJjw-O9pyB7ra2q3qrheo7VFXeyUc4MmW1aqbBqTi6I
4) From within the Magisk Manager, go to settings, enable BETA. Go back to the main Magisk screen and select install. Select patch boot. Patch the boot.img from the 1.0.3 OTA.
5) Once that’s done, Magisk will spit a patched_boot.img to your Magisk forlder on your internal drive. Copy that over to your PC (or email it to yourself, my PC couldn't see it for some reason).
6) If you don’t already have a working SCATTER file, you’ll need to download one. The only one I’ve found that works is in this ROM: https://www.needrom.com/download/myphone-hammer-axe-m-lte/
7) Grab SP Flash Tool: https://spflashtool.com/ , launch it, load the SCATTER file, either the one from the .zip I provided or the one from the ROM on needrom.com (they’re the same), uncheck all the boxes in the lower half of the SP Flash Tool window except for the boxes to the left of the boot and recovery rows. Click in the “location” field on the right-hand side of the window, a dialog will pop up, choose the your patched boot image, if you’re using the one I provided it will be called “magisk_boot.img”. See attached thumbnail for reference.
8) Make sure that the field above the area with the content to flash is on DOWNLOAD ONLY. Make sure you don’t have and Android devices attached to your PC and upon successful inspection, click “Download”.
9) Turn off your myPhone AXE M LTE. Wait for it to fully power down (there will be an additional vibration after the screen goes blank). Attach the phone to the computer via the USB cable that shipped with it. If the SP Flash Tool is in a good mood, it should start flashing immediately (the bottom strip on the window will turn red, then yellow, then you’ll get a pop-up saying “OK!”). If SP Flash Tool is being an @$$, you may have to unplug the USB cable, hit “Download” again, plug the cable back in and repeat until SP Flash Tool correctly sees your phone.
10) Once you get the “OK!” box, reboot the phone. Go to Magisk Manager. Hit install. Choose the direct install (the third option, bezposrednie). Reboot the phone.
11) You should now be able to install XPOSED, VIPER, etc through the Magisk Manager. For XPOSED, make sure you’re using the MAGISK SPECIFIC APK (downloaded from with the Magisk Downloader, just click on the text describing the module and you’ll get a changelog): https://mega.nz/#!UYwExLjC!AAZi-qho0PHWNjXMzAikbTHmTjaEtYfLlqYeDbeJM14
Note: Everything I've tried except for the DOLBY modules has been working splendidly. If you brick yourself, just reflash the ROM from needrom.com and start over.
Thanks and credit:
topjohnwu for Magisk, hanuma50 for his ROM at needrom.com
what if OTA 1.2.0
K A M E N said:
what if OTA 1.2.0
Click to expand...
Click to collapse
I had no idea OTA 1.2.0 existed. Is it Nougat? If so, could you upload it to Mega?
I do not know how. I got my phone back from service (new display), before it was android 4, now it is android 6, working ver:AXE_M_LTE_EN_20170410_1.2.0 core 3.10.72 [email protected] #2
K A M E N said:
I do not know how. I got my phone back from service (new display), before it was android 4, now it is android 6, working ver:AXE_M_LTE_EN_20170410_1.2.0 core 3.10.72 [email protected] #2
Click to expand...
Click to collapse
Ok. Mine is still running 1.0.3. I bought it from Biedronka less than a year ago and it already had Marshmallow on it.
Well, I do not know if your procedure works on 1.2.0 and do not want to brick it.
K A M E N said:
Well, I do not know if your procedure works on 1.2.0 and do not want to brick it.
Click to expand...
Click to collapse
Don't blame you. Hopefully they'll release the OTA you have for the rest of us and then we'll be able to see if the Magisk method works for it too. At the moment my aktualizacja program says that 1.0.3 is the latest OTA.
Files lacking in your upload?
Hello,
thank you for this tutorial. I encountered a few problems:
1) needrom.com requires not only an account, but also a premium one to download the file you linked.
2) Your scatter file was not accepted by my SP flash tool. I used the one I found somewhere else (searching by the CPU model) and it was accepted.
3) After I did this, I couldn't find magisk_boot.img which was supposed to be in your .zip archive. There is no such file there. There is only boot.img, but judging by the size this is an unpatched one you attached in point 4) of your tutorial.
4) I tried generating my own patched_boot.img and succeeded, but it is rejected by SP flash tool (wrong format or sth).
5) Only pair of boot and recovery files that was accepted is in "sig" folder of ur archive. But I have no idea what files are theese and I don't have the guts to try this.
I have no idea what to do now. Could you give me some clues?
mosiowaty said:
Hello,
thank you for this tutorial. I encountered a few problems:
1) needrom.com requires not only an account, but also a premium one to download the file you linked.
2) Your scatter file was not accepted by my SP flash tool. I used the one I found somewhere else (searching by the CPU model) and it was accepted.
3) After I did this, I couldn't find magisk_boot.img which was supposed to be in your .zip archive. There is no such file there. There is only boot.img, but judging by the size this is an unpatched one you attached in point 4) of your tutorial.
4) I tried generating my own patched_boot.img and succeeded, but it is rejected by SP flash tool (wrong format or sth).
5) Only pair of boot and recovery files that was accepted is in "sig" folder of ur archive. But I have no idea what files are theese and I don't have the guts to try this.
I have no idea what to do now. Could you give me some clues?
Click to expand...
Click to collapse
Hey.
I'd tried contacting the original uploader of the needrom file but couldn't get through to him, so I've uploaded his rom to mega:
https://mega.nz/#!9UQh3CBK!LqmVOAxfoIstSVAPeypVzsi7G8PGWQWB_j9qcZB_-RI (this is the same rom from step 6)
As for points 2 through 5, sorry for any confusion, I went back and updated my links. This should resolve your difficulties (initial files I used at the time I wrote the guide): https://mega.nz/#!9UQh3CBK!LqmVOAxfoIstSVAPeypVzsi7G8PGWQWB_j9qcZB_-RI There should be three files inside, the scatter I used, the stock recovery and the modded boot image entitled "magisk-boot.img"
Alternate upload (this contains a modded boot for Magisk 16.6 plus the APK for Magisk Manager): https://mega.nz/#!YAQ3BQyS!dJjw-O9pyB7ra2q3qrheo7VFXeyUc4MmW1aqbBqTi6I
Note 1: on Linux I had to flash both the recovery and the modded boot at the same time because it kept hanging when I was only flashing the modded boot. I don't know why, I just troubleshot till it worked and that's why the stock recovery is included in the .ZIP I linked.
Note 2: I have a Hammer Axe M LTE (if you're in Poland, they were sold for 700zl at Biedronka). I don't know if this process will work on any other variant.
This is my MEGA folder for the Hammer: https://mega.nz/#F!hNAxAQBC!B0el82vXo1sKsEdIskoW1g
Successfully rooted Simbans 10" Excello Tab using Magisk Manager & SP Flash Tool
Rooting the Simbans 10' Excello Tab. Please note the usual warnings before you attempt rooting an Android device. You're probably voiding your warranty. You risk bricking your device. Neither I, nor the website where you found my words, assumes responsibility for your actions
I bought a 10" Simbans Excello Tab running Android Pie (9) for $130 USD in March 2020. I've rooted all of the ~20 Android devices I've owned. It seemed to me that $130 was a bargain price, but rooting it would be difficult. I found no reports of other owners successfully rooting the Excello Tab. I couldn't even find the OEM firmware for it on the mfr website, so I emailed them on the 4th of July asking for the firmware.
At my request, Simbans added the Excello firmware to its website (https://www.simbans.com/restore.html) on 5 July 2020, along with an SP flash tool, and both PDF and video flashing instructions. Prior to my request, Simbans only listed firmware for its Tango and Picasso tablets. N.B. Although I refer to the Excello firmware by different names, it's ExcelloTab 9.0 Base V1.rar on the official Simbans download site. Similarly, what I call the SP Flash Tool is the Reinstall Tool for Android 9.zip on Simbans' website.
The SP flash tool was a clue to how to root the Excello. SP flash tool is for flashing firmware onto Mediatek chips, which are used in several different phone and tablet brands, including the Excello Tab.
PREPARE YOUR PC. Download the Excello firmware rar file, SP Flash Tools zip, and Extract your SP Flash Tools zip file into a folder, and the Excello firmware rar file into another folder. Although most of you will be using Windows, n.b. there are Linux versions of the SP Flash Tool, and the 64 bit Linux version saved me from a hard brick situation. While you're doing that, download the Windows 10 MTK VCOM USB preloader drivers for your desktop computer.. Thoroughly vet your Windows drivers, following online guides. When you connect your powered off Excello Tab to your PC with SP Flash Tool running, you want to see the VCOM driver recognized (check with Device Manager). When you connect it with MTK Droid and Root Tool (which doesn't support Android >4.5) running, you want to see a different MTK USB driver recognized.
PREPARE YOUR EXCELLO TAB. Enable Developer Options and turn USB debugging on. You do not need to unlock the bootloader (so leave OEM unlocking off in Developer Options) to root the Excello Tab. Download and install root checker and Magisk Manager apps onto your Excello Tab.
In order to root the Excello, you need to hack the Excello's boot.img boot partition. But, we didn't get that file in the Excello firmware archive from Simbans. We will have to capture the Excello's boot partition. We do it by reading back the boot.img partition from RAM. There doesn't appear to be a simple boot.img file loaded onto the Excello. It'builds the boot partition from other files, like a boot-sign.img file.
Change the SP Flash Tool to allow capturing partitions, like the boot.img boot partition. Go to your SP Flash Tools folder, and edit the option.ini file in the SP Flash Tools archive. It's a text file, so use a text editor like Windows' Notepad or Ubuntu's Gedit. Find the [ReadBack] section of the file, and change ShowByScatter=false to ShowByScatter=true. Save your changes.
Run the SP Flash Tool as administrator by running the (Windows) flash_tool.exe with shift-right click on the file, or (Linux) sudo ./flash_tool.sh program. Set it up by selecting the Download tab near the top of the window. Choose your Download agent from the extracted firmware folder. Use the MTK_AllInOne_DA.bin choice. The correct Scatter-loading file for our Excello Tabs is the MT8163_Android_scatter.txt file. If you placed all of the extracted files from your Excello firmware rar file in the same location as the scatter file, the SP Flash tool will populate the fields for boot, recovery, etc. Correct any errors now, before you try to flash or use something that's so out of place that it bricks your device. You can click on any erroneous files and correct their path or name.
When you're ready to capture/readback your boot partition, select the Readback tab, and select only the boot partition. Make sure your Excello Tab is powered down and unplugged from the computer that's running the SP FLash tool. Choose the Read Back action. The tool will wait for you to connect your device. Hold the Volume Down button on your Excello Tab, connect the device, and release the volume down button when the red bar appears at the bottom of the tool window. The boot partition gets written as ROM_10 in your SP Flash tool folder. The boot partition will differ on different MT chip architectures, and different partitions. If your next action was to readback your Excello's (MT8163's) recovery partition, it would be saved as ROM_11, and so on.
If the readback succeeds, a green check mark icon appears on the tool screen, and your boot partition has been captured in a 10.8 MB ROM_10 file located in the SP Flash Tool folder..
Disconnect your Excello, power it up, copy the ROM_10 file to your Excello in a location you will remember, and rename it boot.img. I put mine in my Excello's internal memory's Downloads folder.
Run the Magisk Manager app on your Excello, It will tell you Magisk is not up to date. Click the INSTALL choice, confirm with yes, and choose Select and Patch a file as your method, Navigate to your just-saved boot.img file, and let Magisk do its thing. When it finishes, you will have a rooting magisk_patched.img to replace your stock boot.img. Copy the magisk_patched.img to your Excello firmware folder.
Before you flash your modified boot.img file (magisk_patched.img) to root your Excello, you have to modify your MT8163_Android_scatter.txt file (it's in your firmware folder) to only flash up to and including the boot partition. Load that scatter file in your text editor, and find the partition_name: boot. For the MT8163 chip, it's in the section starting with partition_index: SYS10. As you read about partition_index SYS10, you realize that SYS10 is where ROM_10 gets its name from. Different MT chips have different architectures. An MT6753 chip's boot partition will be in SYS8. After you've deleted all the sections following our 8163's SYS10, save the modded file with another name, like MT8163_Android_scatteredmoddedBOOTONLY.txt.
To root your Excello Tab, run the SP Flash Tool as administrator. Change the scatter file to the one you just modified. Choose the Download tab. The scatter file should only give you the boot partition as a familiar target. Check that partition, and select the magisk_patched.img. Power down your Excelo. Press the Download action on the SP Flash Tool. Hold the Excello's Volume Down button and connect the Excello to your PC running the SP Flash Tool. Release the button when the red bar appears on the flash tool. When the flashing completes with a green check mark icon, unplug the Excello. Boot it up, run Magisk Manager and your root checker. You should have a rooted tablet.
At one point, I hard bricked my Excello. It was my fault, but my Excello wouldn't respond to its power button There was an apparent Windows driver problem, as my Excello Tab wasn't recognized by my Windows PC when bricked, so the SP flash tool errored out with an unrecognized device. Luckily, there's a 64 bit Linux version of the SP Flash tool, and the Linux kernel read the MediaTec chip, allowing the Linux version of the SP flash tool to successfully flash the OEM firmware to unbrick the Excello, readback/create the boot.img, and flash the Magisk_patched.img to root the Excello Tab tablet.
If any of these instructions are confusing or contradictory, ask for clarification before you turn your beautiful $130 10" bargain tablet into the most expensive paperweight you ever bought.
i did all the steps up to the readback part it gives me error i try to readback the boot part and that i have done so far to the tablet
exglynco said:
Before you flash your modified boot.img file (magisk_patched.img) to root your Excello, you have to modify your MT8163_Android_scatter.txt file (it's in your firmware folder) to only flash up to and including the boot partition. Load that scatter file in your text editor, and find the partition_name: boot. For the MT8163 chip, it's in the section starting with partition_index: SYS10. As you read about partition_index SYS10, you realize that SYS10 is where ROM_10 gets its name from. Different MT chips have different architectures. An MT6753 chip's boot partition will be in SYS8. After you've deleted all the sections following our 8163's SYS10, save the modded file with another name, like MT8163_Android_scatteredmoddedBOOTONLY.txt.
Click to expand...
Click to collapse
Hey man, awesome work here. I am trying this myself but I am having trouble going through the part I quoted above. Can you help clarify this? Thanks in advance!
I'm sorry, guys, for not checking in more often. I dropped my Excello and cracked its screen some time ago.
Anyway, I found my old working directory for my rooting Excello project, and attached a couple of screen captures to show you what the OEM scatter.txt file looks like. I used Ubuntu's gedit to open/edit the file. The old CTRL-F command opened up a search box, which found SYS10 around line 179. Chop the file after the SYS10 section/discussion, after line 192, and save the altered file as discussed. See the second screen capture file.
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.