Related
This how you unlock bootloader.
Read all before doing anything!
Yes.
Backup all your ect unlocking bootloader will erase all your data.
1 first you will need to USB drivers including adb usb driver.
After that download minimal adb and fastboot.
Make sure you enable debuging and oem unlock in developer's settings.
Download inteladroiddrv.setup.
After you set this up test run "adb devices"
2. Download the twrp that I link in thread.
3.extract recovery .img to minimal directory.
4.open minimal app and run adb reboot bootloader.
5. Run fastboot oem unlock.
6.follow instructions and unlock bootloader.
7.next wait until process is over then it will reboot.
8. After reboot go settings about device go to build tap a bunch of times to reable
Developer's setting enable debugging.
9. Next go to minimal app run adb reboot bootloader your know in fastboot run fastboot boot recovery.img.
10 this will boot recovery then flash root.zip.
11. After that I recommend you do backup and yes it is big after done you can move it to your PC.
Do flash recovery permit touch doesn't work.
https://www.mediafire.com/file/d3h8cnouw8fih6s/android_cdc_driver.zip
Sent from my Studio XL 2 using xda premium
https://www.mediafire.com/file/s4aidnkyacpidjq/latest_usb_driver_windows.zip
https://www.mediafire.com/file/q7nt7xko0f653o4/IntelAndroidDrvSetup1.10.0.zip
skritch said:
I am very interested in rooting the Blu Studio XL2. Can you let me know how you accomplished it?
Click to expand...
Click to collapse
You need to get adb drivers.
Go to settings about device then tap many times on build then go to development settings enable debugging.
You need to unlock bootloader.
Make sure you backup your apps etc.
Unlocking bootloader will wipe user data.
After all USB stuff is in installed.
Adb reboot bootloader this will take you to fastboot next put fastboot oem unlock.
On your phone it will give a choice to unlock bootloader volume up unlocks volume down will keep it locked.
Just pressure you this is not hard to do.
I have two work able recoveries at the time they can bootloop you if you install I was told so here is my solution to this.
Adb reboot bootloader then do this fastboot boot recovery img.
Works like a charm after recovery boots up do a backup.
I will try to drop some links to recoveries for you.
You will likely need to install USB drivers manually local disc c/ programs go into like Intel Android Device USB driver.
This should take care of adb and fastboot problems.
https://www.mediafire.com/file/zy47tm55qr76fc4/SR3-SuperSU-v2.79-SR3-20170114223742.zip
https://www.mediafire.com/file/0ckf...XL+2+-+S0270UU_V08+-+MT6737+-+by+lopestom.zip
https://www.mediafire.com/file/jgpx...XL+2+-+S0270UU_V08+-+MT6737+-+by+lopestom.zip
https://www.mediafire.com/file/do0v472pgcxu3s0/minimal_adb_fastboot_v1.4_setup.exe
I f you need help pm me
I will being posting proof of root also.
Update twrp can be flashed on but no touch.
The garlic touch recovery can be flashed and it works.
Twrp can used only temporary by fastboot boot recovery.img.
Update the other recovery can't find SD card don't use it.
Sent from my Studio XL 2 using xda premium
Sent from my Studio XL 2 using xda premium
This works and is easy as hell. You can also install Magisk 14 install zip if so inclined. Instead of the SR3 SuperSU zip. I did because I wanted a properly working for all modules (mainly luckypatcher) Xposed. Normal Xposed v87 SDK 23 doesn't work. All modules report they are not activated when they are. I, after a couple hours dining and trying many things found out that the SR3 SuperSU zip I flashed coupled with BusyBox install on this phone, which has toybox caused and will cause many apps needing root and BusyBox to not work, re, adaway, Xposed official, Rom Toolbox, Luckypatcher and more. So I used my untouched, Ie, non rooted nandroid backup to restore too, rebooted and installed the Xposed Installer that the Magisk module recommend (been through the Magisk/Xposed rodeo many times) and back to fastboot for the cmd "fastboot boot recovery.img"
Flashed the downloaded Magisk v14 zip, reboot again and fastboot twrp boot to lastly install Xposed.v87.3_Sdk23_sytemless.zip.......
Every time I tried installing within Magisk Manager. I could not get it to work even though Magisk Manager reported all was ok and no errors. But zip Flash Xposed via TWRP does. Safteynet will fail but the Xposed Installer has a toggle for on off as well as a recovery disabler zip so one can toggle reboot and it passes or flash the disabler zip instead of uninstalling the framework.
im reading all this info but im still confused. is it possible for someone to make a video tutorial on how this is all done please??
Things are not going real great with this install. First of all I used a package called MTK USB Driver2014 which had an exe file named DPInst64.exe which I assumed was a good idea for my Win 7 64 bit. I got a message screen saying Google and two different groups of Media Tek usbser drivers with various ports defined are ready to use. I went through the routine then as was outlined in the first post. First I got USB debugging enabled on the phone after going through the initial user setup (this is a new phone). Then I set on the unlock option to on as well as usbdebuggin. Then I ran "adb devices" and got nothing. A couple of unplugs and replugs of the USB to the phone showed a USB driver installing. One stated it installed OK and the Media Tek failed. I ran another "adb devices" and saw the device listed, so I decided to continue.
The "fastboot oem unlock" went well and finished in a few seconds. Then the XL 2 screen showed text in tiny, tiny white on black with 3 options to choose. the default was on the reboot option and said to push volume up to select another or volume down to select the one defaulted. I pushed volume down and nothing happened. The device appeared locked. Would not respond to volume + power button or any other controls. I waited a half hour. So I looked online and it said this happens but to reboot it. I couldn't figure out how. So after more research I found that entering "fastboot reboot-bootloader" followed by "fastboot continue" would cause the phone to go back into normal mode where I once again reconfigured the phone from scratch and enabled Developer tool USB debugging.
Now I finished configuring again and the USB drivers started auto installing again and I got the MTK error on the driver install. I had to unplug the USB and replug and enter "adb devices" and at this point the phone asked for approval and I selected always from this computer. All is well so with the TWRP renamed to recovery.img in the adb program directory I entered "fastboot boot recovery.img" and the TWRP menu came up. I didn't back up because I don't have a SD card large enough and since I can't see any files from when I connect the USB cable, I wasn't sure how to download the backup image once it is stored on the phone. So at this point I selected the TWRP menu option to acomplete the install where future use of TWRP would not be read-only (forgot the exact wording, there was a slide to the right on the bottom of the screen to accept write mode).
Now I rebooted the phone by pressing the up button of the volume and the power button at once and I am still taken to the same green on black text that I saw before on the BLU "recovery menu" (without an obvious method to select TWRP). Is this something to be expected, that the TWRP menu is only available to boot via the PC using adb and fastboot or should the TWRP image somehow remained on my phone?
Thanks!
---------- Post added at 08:21 PM ---------- Previous post was at 08:07 PM ----------
Flex_or_fleece said:
This works and is easy as hell. .
Click to expand...
Click to collapse
Not so much for me LOL.
Can you tell me just how to install root, xposed and xprivacyLua on my phone? Would really be appreciative.
See above for how far I have gotten into the process. Not looking for a different image. This is only the second time I have working on this depth of changes. Again, thank you.
I have been working on this now for 2 full days. I managed to install Magisk 16.0 using TWRP, then without understanding or thinking this was old information, I selected Xposed from Magisk (installed from Magisk before I ready about needing to install it from TWRP) and all appeared to be well. I enabled Xposed and added XprivacyLua and enabled it via the Xposed module page. Everything appeared to be setup properly but Xprivacy said it wasn't installed and a log sent to the developer proved that it was not installed (even though the check box in Xposed said so.)
So after reading the posts above, I elected to remove Xposed via Magisk and install the Magisk version of Xposed (xposed-v89.2-sdk23-topjohnwu.zip) via TWRP. Got everything installed again and same results, everything showed the check boxes marked and therefore active but XprivacyLua would not work).
Now reading above about problems with Busybox, I decided to install Busybox and then the busybox binaries via TWRP, downloaded from this location. https://forum.xda-developers.com/an...zip-busybox-v1-26-2-flashable-binary-t3581875
Now after doing that, I am hung up when trying to open Magisk. It is a solid green screen now. Tired re-installing both the zip via TWRP and the apk and have the same results. I assume I am going to have to restore. This is all new to me and I did not make a backup image because I don't have a SD card where I am working on this. All I can find is a factrory image on Needrom website: BLU_S0270UU_V6.0.04.02_GENERIC_20180203.rar
Can anyone point me to a guide that explains in elementary (as possible) terms how to get this ROM onto my phone and with it restored with the factory image? THANK YOU!!!!!
Flex_or_fleece;73955523 my untouched said:
Hi, is there anyway you would be willing to share this backup? Thank you!. I live in a small town with no computer shops and I did not have a SD card to back up to. Thank you.
Click to expand...
Click to collapse
I am struggling with everything including lack of mini SD card while residing at the moment far away from a computer store, a USB cord that is flaky as the snow, and a bricked phone because I wrongly read in a prior post that installing Busybox was a way to resolve the issue of Xposed showing it was installed and working when it was not.
Now can anyone suggest a link that shows how to flash the ROM I found online at NeedROM: BLU_S0270UU_V6.0.04.02_GENERIC_20180203.rar to this phone? I am not an expert at this, having rooted only a few phones over the years where I wanted Xprivacy and mostly just entered a few commands to make it happen. Today its getting too complicated.
I don't know if this phone even works with the SP flash tool, and if it does the drivers I have found to attempt it are not working.
Any help would be appreciated. THANKS!
Donphillipe said:
I am struggling with everything including lack of mini SD card while residing at the moment far away from a computer store, a USB cord that is flaky as the snow, and a bricked phone because I wrongly read in a prior post that installing Busybox was a way to resolve the issue of Xposed showing it was installed and working when it was not.
Now can anyone suggest a link that shows how to flash the ROM I found online at NeedROM: BLU_S0270UU_V6.0.04.02_GENERIC_20180203.rar to this phone? I am not an expert at this, having rooted only a few phones over the years where I wanted Xprivacy and mostly just entered a few commands to make it happen. Today its getting too complicated.
I don't know if this phone even works with the SP flash tool, and if it does the drivers I have found to attempt it are not working.
Any help would be appreciated. THANKS!
Click to expand...
Click to collapse
Hello! Been through the same thing.
It is compatible with SP flash tool. Think about it: in the factory all phones come empty so there must be something to flash them. In case of Mediatek-based devices, it's SP Flash Tool.
And yeah, your drivers are broken. First of all, uninstall them. Can't tell exactly how because I don't know what you installed but you can try the programs list and the device manager.
After removing them, download mediatek-drivers.zip and extract it.
Now follow this carefully:
1) Go to device manager and click on Universal Serial Bus controllers.
2) Then go to Action >> Add legacy hardware.
3) Select Install the hardware that I manually select from a list (Advanced).
4) In the hardware types, select Show All Devices.
5) Click on Have Disk... >> Browse, browse to where you extracted the drivers, go to mediatek-drivers/Win7/ and select usb2ser_Win764.inf or usb2ser_Win7.inf if your system is 64 or 32 bits arch respectivelly.
6) Click Open and OK.
7) Select MediaTek DA USB VCOM PORT, then just Next everything.
Now repeat every step above but in step 7 select MediaTek PreLoader USB VCOM Port.
Your drivers should be installed by now.
Now if you haven't done it yet, download it here. Run it, go to Download and in Scatter-loading File, choose the MT6737M_Android_scatter.txt file that (hopefully) came with your ROM. If it didn't download it here and place it in the same folder as the .img files that came with your ROM.
If it shows all checkboxes marked, just mark system, boot and recovery. It's a soft brick, you don't need a full reflash. If it doesn't but has system boot and recovery it's fine too. Hit download. Now, with your phone turned off, hold the VolDown key and plug it in. It will start flashing.
A popup will appear when it's done. That's it! Unplug and restart it. Should be back from the dead now.
The TWRP build you are using can only be booted via fastboot but not installed. If you flash it, the touchscreen will not work nor power buttons so you can't select anything. However I found a working flashable TWRP build: TWRP 3.1.1 built by Vampirefo
This one has the touchscreen working so you can permanently flash it on your device. It's very important to have a working recovery on your device that can reboot to bootloader because Power+VolDown actually boots in some kind of hardware test mode on this phone. Basically, if you softbricked your system, no working recovery=no bootloader=no temp recovery. And it's way easier to just restore your backup if you brick your phone.
Also, you can flash it througt SP Flash Tool. Rename it to recovery.img and go for it.
Can you reply or PM me with the rom you found? Mine is really old and I always have to wait for OTA...
Also, if you have any progress with Xposed, please share couldn't get it working properly here. Not a single module works...
Tried installing it the regular way with SuperSU and Magisk and tried the systemless install within and out of Magisk. None worked so far.
Thank you!
Mark42XLII said:
Hello! Been through the same thing.
Can you reply or PM me with the rom you found? Mine is really old and I always have to wait for OTA...
Also, if you have any progress with Xposed, please share couldn't get it working properly here. Not a single module works...
Tried installing it the regular way with SuperSU and Magisk and tried the systemless install within and out of Magisk. None worked so far.
Thank you!
Click to expand...
Click to collapse
I got the ROM from needrom.com you have to create an account, then just search on Blu studio xl and scroll down to pull the 2 version. Restored using SP Flash tool with non problem.
This whole thing is really frustrating. Get Magisk installed via TWRP, then to load Xposed Framework, you have to load Xposed via TWRP and then if you follow comments here from Flex_or_fleeceand his mini guide for downloading from Magisk with download only and not an install, you get the universal Xposed Systemless zip that is supposed to be able to choose which OS version you need during the install but that doesn't work installing via TWRM installing the universal version of Xpozed seamless zip so you have to download from the XDA site the latest Xposed with the SDK of your OS, in my case SDK23 latest version for Android 6.0. Now once you get Xposed installed via TWRP, then everything appears to work but trying to load XprivacyLua says it is not installed when the Xposed Module list says it is installed and the module is checked as being active. Yet the XprivacyLua menu still says you need to fix the issue.
Flex_or_fleece who claimed to get this working in a prior post said he resolved his problem by going to the link for BusyBox XDA pages for a solution, well I tried that, first installing BusyBox free from playstore, made sure that it said it was installed, then I loaded the libraries they talk about that is supposed to fix the BusyBox with toybox and after installing and testing the free version of BusyBox, then booting to TWRP and installing the Busybox library zip, once you boot up, the Magisk Manager will never open up again, just a blank green screen.
Time for a restore and try something else next time but unfortunately (unless the guy I asked about what exactly he did regarding BusyBox will respond, which he hasn't yet, ) then it's anyone's guess and I am all fresh out of guesses
Donphillipe said:
This whole thing is really frustrating. Get Magisk installed via TWRP, then to load Xposed Framework, you have to load Xposed via TWRP and then if you follow comments here from Flex_or_fleeceand his mini guide for downloading from Magisk with download only and not an install, you get the universal Xposed Systemless zip that is supposed to be able to choose which OS version you need during the install but that doesn't work installing via TWRM installing the universal version of Xpozed seamless zip so you have to download from the XDA site the latest Xposed with the SDK of your OS, in my case SDK23 latest version for Android 6.0. Now once you get Xposed installed via TWRP, then everything appears to work but trying to load XprivacyLua says it is not installed when the Xposed Module list says it is installed and the module is checked as being active. Yet the XprivacyLua menu still says you need to fix the issue.
Click to expand...
Click to collapse
I already did the BusyBox thing you talked about before and it went the same way. The difference is that my first attempt was by downloading from XDA so I didn't went through the universal zip problem. Actually there is now inside Magisk both the universal zip and the targeted sdk version numbers ones. Also I installed GravityBox and it said that couldn't communicate to the framework or something like that. Basically same problem. But I noticed something: when you install Xposed and reboot for the first time, it says that the Xposed framework is installed but not active and tells you to check the logs. If you go there you can see that the log file apparently doesn't even exist. In the second reboot it tells you it's active and running but if you check the logs it still couldn't open it because it doesn't exist. So maybe the problem is that Xposed isn't even starting up.
Mark42XLII said:
I already did the BusyBox thing you talked about before and it went the same way. The difference is that my first attempt was by downloading from XDA so I didn't went through the universal zip problem. Actually there is now inside Magisk both the universal zip and the targeted sdk version numbers ones. Also I installed GravityBox and it said that couldn't communicate to the framework or something like that. Basically same problem. But I noticed something: when you install Xposed and reboot for the first time, it says that the Xposed framework is installed but not active and tells you to check the logs. If you go there you can see that the log file apparently doesn't even exist. In the second reboot it tells you it's active and running but if you check the logs it still couldn't open it because it doesn't exist. So maybe the problem is that Xposed isn't even starting up.
Click to expand...
Click to collapse
On one of my iterations I installed a playstore app Marshmellow SD fix which fixed my problem with Xposed saying it couldn't read the log file. https://forum.xda-developers.com/xposed/modules/xposed-marshmallow-sd-fix-write-t3403263 But then once I installed this, slide the slider for Xposed to "authorize to sdcard" and then Xposed no longer had the error saying it couldn't read the log file but then simply always said "log file empty".
I'm just trying for Xposed and XprivacyLua only. When if I don't install BusyBox or the follow up install of the BusyBox binary zip file (that locks up the Magisk screen) and when I only start with a full ROM restore, install Magisk with TWRP, bring up Magisk and install Magisk Manager, install Xposed Systemless via TWRP, bring it up then it says Xposed is active. In Xposed I download and install the latest XprivacyLua and click the box in the Xposed module listo enable XprivacyLua, the check box remain checked and show active but the XprivacyLua menu says it is not installed. I sent a trace to the developer of XPrivacyLua and he said that Xposed was never loading it, and this is to repeat with all the respective check box checked and everything but the actual app saying all are active.
Adding "BLU STUDIO XL 2" so maybe Google can find this thread when people don't append the 2 to the XL"
Xposed still not working
I won't use a phone without these tools so at the moment I am still using my old Blu Studio with Android 5 that has the cracked screen and it is getting more and more cracked and harder to read. From time to time I pull my new unused BLU STUDIO XL 2 out of the closet and go a few more rounds with it. I've searched high and dry for the FlexorFliece fellow who claims to have it working and can't find him on any other blog or forum and he doesn't respond to messages but I just don't see how he got the Xposed suite working on this phone. I just spent three 14 hour days working on it as of today and got so frustrated that I reflashed the stock ROM on it and set it back in the closet again to try again another day, perhaps waiting like last time for a few more releases of the respective apps and modules to try again.
Now with several iterations of installing Xposed I've gotten the "green light" from Xposed Installer menu saying that it's installed and working and with the latest release which I think I recall is Magisk 17.1 and Xposed seamless SKD23 at release 89.3. This is actually quite funny that the light is green with Xposed Framework indicated as active from the Xposed Installer menu. You can then start searching for and downloading modules from the Xposed Manager and eventually the "green light" will go red while none of the Xposed modules will ever work, green or red light. At least the red light finally gives you a real indication.
I've loaded versions of Magisk all the way back to V14 and Xposed seamless (SDK23) back to 87.3 and the results are always the same. I'm either in a boot loop on a bad try or on a good try I'm showing the green light on Xposed but with no module working and reaching a threshold of about 6 Xposed modules loaded, then the light finally turns to a red one saying it's not installed or working.
I tried Flex or Fleece's technique of adding the Magisk version (from its repository of Magisk modules), the busybox and the ADB/Flashboot modules as a prerequisite but that didn't do a thing.
Now here's some odd things about this phone and even getting it to a good point to experiment with it.
I've found if I start with a fresh flash of the stock ROM or the phone in any condition without USB Debugging on, for example if I start with a powered down phone and hold the VOL-UP and POWER button at the same time, I can go to the stock recovery to select boot to bootloader option. (Release the POWER button slightly before the VOL UP or you'll boot the phone instead.)
Next I move to the PC and begin fastboot commands:
- get the ADB command window up by bringing up Windows file explorer with the name of the ADB folder visible and while holding SHIFT I then right click on the ADB folder and select "Open command window here" which opens a "DOS prompt" with the adb files in the directory. It's assumed I have pre-copied the new recovery image recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img to the same directory (folder) as hosts the adb.exe and fastboot.exe. Here I go back up to Windows File Explorer open the folder containing ADB/fastboot and rename this image to a shorter name. (Could use the DOS rename command but the syntax is too long and too easy to make a mistake.) Here I have renamed it to simply recoveryTWRP.img
Now then on the PC command window I enter ....
fastboot devices (to check that my USB is working OK)
fastboot oem unlock (to unlock the bootloader)
fastboot flash recovery recoveryTWRP.img (recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img that's been renamed)
fastboot reboot (to reboot the phone)
The phone may not boot after a flash or after and adb/fastboot interaction if the USB cable is not unplugged when done, so be aware of that.
Now if you are fast, you can go ahead and hold VOL UP at the moment the phone begins to boot and at the moment you have completed the fastboot series of commands. As soon as you see the TWRP recover manager you can release the VOL UP and be patient while the TWRP Menu appears.
Note now that you won't be able to use the SD card you may have randomly installedwith TWRP unless you have initialized it via Settings on the phone where you have under Storage option, set the SD card type to be "portable storage". If it's not formated and initialized by this phone, TWRP won't let you select it.
Quirks seen here include a failed install with unable to mount errors on the TWRP console trying to root, that is unless you have actually initialized the phone and set on Developer Tools and turned on USB debugging. (Sounds crazy but that's what I am seeing.) So basically that's what you'll find. ALso this verion of TWRP on this phone will not mount USB storage as with TWRP on other BLU devices I've tested, so copy all l your potential zip files to install as well as your apks you plan to side load (e.g. Xposed Installer and Magisk Installer apk files to the SD card prior to loading TWRP and finding that the files are not on the card or in the phone storage yet.
Other caveats are, with USB debugging off, each time you plug in the USB cable and want to upload files to the phone, when you go looking for the files in Windows device manager you will see a blank white screen appearing like there are no files on the deivce. What you have to do is slide the phone messages up and down a few times (perhaps dragging down from the top if it's not on the main screen) and finally the small window will appear on the phone where it asks for USB Charging only which you can tap and change it to USB Media and at that point you can see the SD card and Internal Storage for the phone in the respective Pc window where you can drag files into the phone's folders from the Windows PC. Otherwise with the phone having USB Debugging on you are supposed to be able to set it permanently to USB Media but you actually can't set it permanently. If you do research you will see online articles claiming that with Developer Options enabled and USB Debugging on, that setting the option just above the green "input" word on the Developer options screen allows you to set USB Charging to USB Media and it should stay permanently. Well stay it does on the menu but the function itself does not stay. Here each time you plug the phone in with the USB cable you will be curious why you cannot access the phone's storage because you believe the menu in Developer options that says it has been set to USB Media. Yes, it shows that way but you still can't see the storage on the PC. What you have to do each time you attache the phone with a USB cable then is go to Developer Options (shortcut would be to click on the info bar stating USB Debugging is enabled and when you arrive at Developer options, page down to just above the green "input" word and then temporarily set the option from USB Media to one of the other options, then set it back again to USB Media and you once again can see the phone's storage on your Windows computer.
And all this work and dealing with quirks is required before you even try to root by using SU or Magisk zip files and attempting to install then via the new TWRP recovery image you installed and gain access to by rebooting and holding in the VOL UP button to access the TWRP menu.
Otherwise the best performing ROM I have found is BLU_S0270UU_V6.0.04.02_GENERIC but when I went looking for it just now, the only place I can find it is now with the new toll-booth controlled need.rom repository. Yes I now see that needrom.com has now started charging to download the zip recovery modules we all uploaded there for free. What a sneaky bunch of #$#R)!!! Also, the spamming of Google has made searching for ROMs and any information about rooting a phone all but worthless. For example when I searched for BLU_S0270UU_V6.0.04.02_GENERIC which I believe is the latest ROM. I know there is a V8 floating around out there that I loaded but just in setting it up, the layout of the screen first went crazy and then the wireless log-in gave problems and then and finally the turning point was that the camera or video wouldn't work, so I gave up that version of the ROM. Anyway, searching for the ROM resulted in 5 full pages of search results with every website on every page saying they had the rom to download but in fact none of them did. I got directed from everything from purchasing female teen clothes, to sports gambling sites to unending surveys to you name it. What a vast wasteland it is out there these days. Unless Google does something to stop this technique where every website says they have a hit on your phone model when all they do is to stuff your search argument into a page of generic randomly generic diatribe, one day we will no longer be able to use the Internet to find things, or certainly it will take more time while weeding through all the disinformation.
Now
Yes, but that is not the challenging part. The challenging part is to get Xposed installed and the Xposed apps working with your root that you can obtain by several methods.
TWRP and this phone is easy, as you said and as I agreed. You will not be able to get Xposed apps running if that is the goal - even with root.
What is the main interest in this phone rooted? No one has gotten Xposed working so far or if they do get the green banner saying it is installed, it doesn't work with any of the apps. (Reported as due to toybox.) The phone has been rootable for nearly a year now, it's just that you can't do much with the root once you get it.
I have had my phone rooted for over a year now. Every few months I try again installing the latest version of Xposed via SuperSU or Magisk. Xposed apps will not work with either.
I have been derailing the internet trying to figure out some way to root my device with and without usb connecting it to my mac. Frankly, as far as I can tell my mac and my phone won't support mass storage of android so odin etc seems out of the question. I just want to find a way to get my phone rooted (tried kingroot and it asked for computer and I've a mac so there you have it). Please if anyone could help me find a simple, maybe even complicated way to root my s6 (it's updated fully).
Define without USB? Like no OTG USB Storage or no USB cable? If that's the case then you're asking how to root the device without a computer which afaik with Samsung isn't an easy deed (perhaps not possible).
-------------------------------------------------------------------------------------------------
Firstly, you do this at your own risk. Js.
However.. If you can get it up and going on your Mac then try out Heimdall (the Mac/Linux Odin alternative some whiz managed to reverse engineer).
P.S. I have Linux but I've seen Heimdall is available on Mac, unfortunately I can't step you through installation.
https://forum.xda-developers.com/showthread.php?t=2118100
Go to the TWRP.ME site and locate your device and download the latest TWRP image (should be 3.1.1.0)
https://dl.twrp.me/zerofltetmo/
Download dm-verity encryption disabler (without this, it's likely things won't go as planned, it ensures you haven't modified system files etc)
https://androidfilebox.com/miscellaneous/dm-verity-and-forced-encryption-disabler/
Choose a Root method (personally I prefer Magisk but for a first time superuser provider I would recommend SuperSu:
https://download.chainfire.eu/1114/SuperSU/SR1-SuperSU-v2.82-SR1-20170608224931.zip
[ PLACE PHONE IN DOWNLOAD MODE: Hold VOL-DOWN + HOME + LOCK, then press VOL-UP ]
1. Go to Utilities Tab
2. Click Detect Device; if it is not detected you have a problem (find fix then go to Step 3)
3. Output reads Device detected; beneath Download PIT save the file somewhere (e.g. Documents/s6.pit)
4. Go to Flash Tab
5. Beneath Options > PIT, browse for the .pit file you saved in Step 3
6. On the right hand side, beneath Partitions (Files) click > Add, on the left change the partition name to Recovery (where it will ask for a recovery.img file)
--- READ STEPS 7-9 BEFORE YOU DO THEM ---
7. Select the TWRP.img you downloaded earlier
8. Click Start, pick your phone up (be careful not to disconnect it)
9. AS SOON AS THE SCREEN GOES BLACK, HOLD: VOL-UP + HOME + LOCK
--- READ STEPS 7-9 BEFORE YOU DO THEM ---
10. If done correctly (and your bootloader is unlocked, and your RA lock is disabled) you will be in TWRP Recovery. Swipe to allow system modifications (you can always come back here later, you asked for Root so this will suffice).
11. Use Finder (File Browser) to navigate onto the phone from your Mac and copy SuperSU and no-verity onto the Internal Storage
12. From TWRP (on the phone) tap on the Install tab and if you aren't able to see the two .zip files you copied over, you're probably in the / directory; navigate to /sdcard
13. Tap on the no-verity.zip first, continue through, don't worry about using multiple .zips just install and go back when it is complete
14. Tap on the SuperSU.zip. Continue through, same as previous step, this time backing out to the TWRP menu and tap on the Reboot Tab > Choose System
15. If prompted to install anything (TWRP) untick the boxes and tap do not install.
16. Your device should be rooted. Don't turn the phone off, don't panic. SuperSU can cause the first one or so boots to end prematurely and the device will reboot (don't be alarmed if it cuts out).
Note:
On the odd chance that your device is stuck in a bootloop or you are worried about 'bricking' the phone, the only way that can happen (afaik) is if you disconnect during important installations such as during the Odin/Heimdall flash process or TWRP (under certain circumstances, even during Odin/Heimdall you can normally pull through). Otherwise, you'll just end up with a soft-brick (99.9% of the time this is the only thing that happens)
glgl
i am making this post because i have an lg v20 running 20h. there was no root guides available, so i decided to root mine using an older guide. it succeeded, but was very hard and time consuming. Being a noob at the time, i was also extremely nervous that i could possibly brick my phone or screw something up. i didn't, and no part of this should brick yours either. ***However - if you do somehow break your device in any way, that is on you. by completing these steps, you assume full responsibility. now that we have that out of the way, lets continue. at the end of this guide, you should have a rooted device with your choice of os (7 or 8 - or even a custom rom if you choose!). you should also have twrp. this guide would not have been possible without users runningnak3d and clsA
**** Also, during this Proccess, Your Phone WILL be wiped clean!!! don't forget to back up photos, videos, etc...*****
don't download any other files than from this guide.
1. download these files (required) https://lg-firmwares.com/downloads-file/4578/H91510e_00_VTR_CA_OP_1205.kdz (for a rootable os that we can flash, - get this also (required) https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222 this program is called lg up and has been patched to work with this phone. you will also need this. https://androidfilehost.com/?fid=1322778262903990218. these are the root files and need to be all in the same folder as where lg up is installed. you will also need to have access to fastboot and need to have adb installed. that is pretty easy, give it a google search if you still need help.
if you are running 32 bit, get this https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads
this is the OS. get nougat, which has like three less steps (you can't upgrade to oreo on this os once rooted) or scroll down and get the oreo file. nougat (really old version) https://drive.google.com/file/d/1S82HVNt2rAtXgBY499IBJnoCVFnpCf_X/view
Oreo - get this first file, and the ones under it. https://www.androidfilehost.com/?fid=1322778262904015326
***https://androidfilehost.com/?w=files&flid=283977*** You have to have this file if getting oreo. if you chose nougat, then don't get this.
2. Now that you have everything downloaded and installed, put your phone into download mode. (power it off, hold the volume down button and plug in a usb c cable attached to your pc. don't stop holding volume down until you see download mode.)
3. once it is in download mode, open up lg up. select your device, (it should be in standby mode, according to lg up) and click dump (this is a total backup of the phone, you are lucky you know this right now, I didn't when i rooted mine) . it will bring up a file explorer, select where you want it to save to. (I chose my desktop). once you have a folder selected., it will bring up a bunch of options for partitions. click select all and uncheck user data. ****Make SURE that you don't unplug your phone during any part of this process or any other process in this guide, it will permanently brick it. ***** ow that you have selected everything but userdata, click start.
4. once that finishes, you will have made a full backup of your phone in case something goes wrong.
then click the partition DL button and select the h915 v10e kdz file (the file that i said was the rootable os we can flash) (the first file you downloaded). make sure bin file stays checked. then click start. once that finishes, your phone should automatically reboot into an old nougat operating system. then go to settings, enable developer options, and turn on usb debugging. that is easy, if you can't figure it out, google is your friend. now you should have no cellular signal. this is not the permanent ROM.
5. go to the play store and download terminal emulator for android. (once usb debugging has been enabled
then go ahead and go to the folder where you extracted the root files/package. hold shift and right click to open a command windows there or powershell, whatever your pc says. open 2 of those windows. then, in the first one, type, adb logcat -s dirtysanta
****don't close this window.*****
then in the other window, type STEP1.BAT
*****don't close this window.***** It may take a minute, but after a while it will let you type again. once you can, type run-as con
chmod 0777 /storage/emulated/0/*
6. then, pull up the window you used the logcat command in. leave it there so you can watch it
then, on your phone, go to the terminal emulator and type applypatch /system/bin/atd /storage/emulated/0/dirtysanta
once you do that, glance at the logcat window. once it says to run step 2, go to the window where you typed step1.bat. type STEP2.BAT
at this point, your phone should go ahead and reboot and say fastboot mode up at the top. now, go to your window where you typed all the .bats and type STEP3.BAT. wait until your phone reboots and you will see a screen saying that you can;'t use your phone. this is bogus, just ignore it and wait like 10-15 seconds for it to get past that screen. then it will boot that android and you should get a green screen.
Now, quickly, pull the battery from your phone. leave it out for a little while while we prepare the next steps.
If you want oreo, scroll to where it says OREO in capital letters. if you want nougat, scroll to where it says NOUGAT.
NOUGAT
use the file that you downloaded if you selected nougat - it should be a zip. it will be called h910-10r. DO NOT, I REPEAT, DO NOT UNZIP THE FILE. place it on a pre formatted micro sd card. then, place the battery and sd card back in your phone. also, unplug the phone. then, hold down the volume down key and hold hold the power key. once you see the lg logo, release the power key and immediately hold the power key again. then, you should get a screen that asks if you want to reset your phone. use your volume keys to navigate and select yes, then again confirm it. then, after letting it reboot, it should go into twrp. once there, go to wipe\and select format data. then type yes to confirm. then, go back to the main screen and click wipe again. go ahead and click advanced and wipe your dalvik cache. once done, go to home screen and click install. select the select storage option down at the bottom and change to sd card. then find the h910 zip file and install it. then go ahead and reboot your phone, you will have a rooted android 7 rom. you will also have signal. then download supersu from the play store and open it to have root.
OREO
use the file that you downloaded if you selected oreo - it should be a zip. it will be called something along the lines of full stock oreo rooted. DO NOT, I REPEAT, DO NOT UNZIP THE FILE. place it on a pre formatted micro sd card. also, go to your root package folder and find the twrp image file and put that on your sd card. then go get the mk200 zip file and also place that on your sd card. then, place the battery and sd card back in your phone. also, unplug the phone. then, hold down the volume down key and hold hold the power key. once you see the lg logo, release the power key and immediately hold the power key again. then, you should get a screen that asks if you want to reset your phone. use your volume keys to navigate and select yes, then again confirm it. then, after letting it reboot, it should go into twrp. once there, go to wipe\and select format data. then type yes to confirm. then, go back to the main screen and click wipe again. go ahead and click advanced and wipe your dalvik cache. once done, go to home screen and click install. select the select storage option down at the bottom and change to sd card. then find the oreo full rooted zip and install it then, install the mk2000 file. after you have done this, click install image and select the twrp. the reason you need to re flash this is because that oreo file re installs the stock recovery. then install the twrp. now reboot your phone. you will have a rooted android 8 rom. you will also have signal. then download a magisk 6.0 manager apk from chrome browser to have root.
IF this worked and your enjoying root give me a thanks.
This is redundant to the existing h910 root guide, all you did was copy their work and re-post it
Sent from my LG-H910 using XDA Labs
cnjax said:
This is redundant to the existing h910 root guide, all you did was copy their work and re-post it
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
Yes, that is why i gave them credit. However, It is more noob friendly and takes the time to explain what they are doing to their own phones as well as give them the option for nougat or oreo, something that none of the other guides have.
Ok, so I did it sucessfully, it's was still very complicated for me as some info is vague for a beginner. But after searching and retrying, and retrying, it worked. but go to runningnak3d post to get more info, and he wanted me to use sd card to root, but that did not work for me.. Your method worked for me. Thanks
the_R00ter said:
i am making this post because i have an lg v20 running 20h. there was no root guides available, so i decided to root mine using an older guide. it succeeded, but was very hard and time consuming....
Click to expand...
Click to collapse
your guide is good
+1 for for linking to the missing files from the old guide
+1 for mentioning me and @runningnak3d
you could break up the long paragraphs and bullet style the steps in order so it's easy to follow
theirs a video here of the steps and how the command windows should look > https://www.youtube.com/watch?v=jnRWnSHLGSc
this is where allot get confused in the guide.
I also don't remember you mentioning doing the battery pull after STEP1 when the phone sometimes hangs then run STEP2
I would also change the link to the H915 kdz to the android file host file in case LG changes it.
Their was a guy recently that could not get LGUP working you could make note that you may need the 32 bit VS 2010 > https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads
Any how, the guide is OK and the steps are not that bad, after a few tries most anyone can learn it.
clsA said:
your guide is good
+1 for for linking to the missing files from the old guide
+1 for mentioning me and @runningnak3d
you could break up the long paragraphs and bullet style the steps in order so it's easy to follow
theirs a video here of the steps and how the command windows should look > https://www.youtube.com/watch?v=jnRWnSHLGSc
this is where allot get confused in the guide.
I also don't remember you mentioning doing the battery pull after STEP1 when the phone sometimes hangs then run STEP2
I would also change the link to the H915 kdz to the android file host file in case LG changes it.
Their was a guy recently that could not get LGUP working you could make note that you may need the 32 bit VS 2010 > https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads
Any how, the guide is OK and the steps are not that bad, after a few tries most anyone can learn it.
Click to expand...
Click to collapse
alright, thank you so much for the advice! 1. i don't want to switch to bullets because when i was trying runningnak3d's guide, it seemed overwhelming. also people can comment on the step number that they were lost at. 2. i will change the kdz to something else if the file does change. i did in fact mention the battery pull step, if you ever need to find something in a page, hit control and f and then search the page.. i will add the 32 bit file. Thanks!
the_R00ter said:
i am making this post because i have an lg v20 running 20h. there was no root guides available
. . .
this guide would not have been possible without users runningnak3d and clsA
IF this worked and your enjoying root give me a thanks.
Click to expand...
Click to collapse
W O W . . .
What a way to rip-off runningnak3d's guide.
I mean, I can understand rewriting it... I did the same. But, just to parse it out for me to follow better.
But your statement "...there was no root guides available..." is just BS.
Below is my guide... for me to do the process.
Creation date on the text file was November 7, 2017. Just over a week after runningnak3d made the original post.
Difference is, I didn't feel the need to post someone else's work, in an attempt to try claiming credit for it, due to nothing more than a "rewrite".
What you meant to do is this: (FIFY)
Cool guide for rooting your LG V20. Works for 20h, too!
--------------------------------------------------------------------------------------------------------------------
Materials:
8+GB microSD Card - formatted exFAT or ext4
LG Up (patched)
C:\Program Files (x86)\LG Electronics\LGUP <- install here, or it won't read DLL correctly
ADB
DirtySanta root package - (No working Link)
H91510e_00_VTR_CA_OP_1205.kdz - http://lg-firmwares.com/downloads-file/4578/H91510e_00_VTR_CA_OP_1205.kdz
h910-10r.zip - https://drive.google.com/open?id=1S82HVNt2rAtXgBY499IBJnoCVFnpCf_X
- Check the SHA hash: 5451146030393e490dcfba3558b620badefe75cd
Terminal Emulator APK
Root Checker APK
Settings Database Editor APK
1) Copy h910-10r.zip, SuperSU-v2.82.ZIP, SuperSU.Pro.APK, Terminal Emulator, Root Checker, and Settings Database Editor to microSD Card and insert into phone.
2) Put phone into download mode (power off / hold vol. up & plug in USB cable)
Use LG UP to dump phone. When you run it, there will be additional radio buttons.
- Pick the one that says DUMP and click Start. You will be asked what partitions to dump, click the "select all" checkbox, and then you can uncheck "userdata".
3) When finished with the Dump, click the PARTITION DL radio button, pick the H915 v10e KDZ, and click start. Make sure all partitions are checked.
- Select H91510e_00_VTR_CA_OP_1205.kdz, Tick box to set as input file.
- Select all partitions
- Confirm all partition changes
- Once it is complete, phone will reboot into old Freedom Mobile ROM
- Disconnect USB Cable
- Complete Android setup, and you may not have signal (this is normal).
- Enable developer mode, and enable USB debugging.
- Enable Unknown Sources
- Connect USB Cable
- Make sure that your PC is authorized (tick always allow, and then OK).
4) Install Terminal Emulator for Android -- NOT Termux.
5) Extract root kit somewhere that you can run adb and fastboot from.
6) Open [2] Command Prompts in the directory containing ADB.EXE.
A) In first window, execute: adb logcat -s dirtysanta
B) In the secxond window, excute: STEP1.BAT
- Wait until prompt returns (several minutes)
C) Window 2: run-as con
D) Window 2: chmod 0777 /storage/emulated/0/*
E) Open Terminal Emulator on phone, enter: applypatch /system/bin/atd /storage/emulated/0/dirtysanta
- Watch window 1. Wait for "Finished. Please run Step 2 now."
F) Window 2: "exit"
- Window 2. "exit" again.
- STEP2.BAT (adb reboot bootloader)
- Phone now shows FASTBOOT MODE
G) STEP3.BAT
- This flashes TWRP and WW 2.0 kernal
- Phone will reboot on completion
7) If phone reboots to Android, in Window 2 execute: adb reboot recovery
- If phone is stuck at secure start-up, pull battery and boot into TWRP (same as factory reset)
8) In TWRP:
A) Settings: UN-Check Enable Screen timeout
B) Format Data (type "yes" to proceed)
C) Wipe Cache & Dalvic Cache
D) Install (flash) h910-10r.zip
E) Install (flash) SuperSU-v2.82.zip
F) Format Data
G) Reboot Phone
Problem Occured:
I seem to have a problem at running this, "run-as con chmod 0777 /storage/emulated/0/*" command.
the error i get is,
xelsa:/ $run-as con
chmod 0777 /storage/emulated/0/*run-as con
run-as: Package 'con' is unknown
Help?
SheMi363 said:
I seem to have a problem at running this, "run-as con chmod 0777 /storage/emulated/0/*" command.
the error i get is,
xelsa:/ $run-as con
chmod 0777 /storage/emulated/0/*run-as con
run-as: Package 'con' is unknown
Help?
Click to expand...
Click to collapse
This "run-as con chmod 0777 /storage/emulated/0/*" actually is a two commands:
- first type "run-as con" and press ENTER
- second type "chmod 0777 /storage/emulated/0/*" and press ENTER
Search in You Tube for "How to Root install TWRP for LG V20 H910 Edition!" from user NewTechBegins. This is very good video tutorial, step by step.
Hello, so nothing happens for me after I enter the code into terminal emulator, what am I missing?
After all these done I'm rebooted to secure start-up where I need to enter password. Tried my 4 digit VIN and didn't work. As suggested earlier in this thread I pulled battery and wipe everything and install Oreo_full_rooted.zip, mk2000, and TWRP 3.3.1-0. It boots up the same to the secure start-up.
I might have done differently in process.
1. H91510e_00_VTR_CA_OP_1205.kdz I downloaded did NOT match MD5 on its download page. Tried twice and it was the same. I went ahead and used it.
2. I ran into "adb server is out of date, killing.." message but was able to download an adbfix and somehow got through
3. STEP1.BAT and the rest of BAT were not accepted in Win10 powershell so I had to enter them by hand and it went smoothly with no error
4. I used twrp 3.3.1-0 as suggested in NewTechBegins' youtube clip
5. Phone boots into scramble messages like shattered warning sign before LG logo appeals. It will eventually enter twrp or secure start-up after some wait. Takes longer than it should, 5 minutes or so.
Wish to stay on Oreo but might try the 10R Rom if I have no other choice.
Please help.
(Secure start-up appeared the first time after step 3 where it was supposedly be a green screen and I can pull battery. It didn't. It went to secure start-up. I pulled battery anyways and rebooted into TWRP, I was asked to enter password again. After a few wrong attempts I was able to bypass it and enter TWRP to proceed with install)
edit: Eventually succeed by not installing TWRP after flashing OREO and MK2000. Rebooted into Secured Start-up again, pull battery and rebooted into FACTORY Recovery and deleted all user data from there. Rebooted and Android setup began.
Note: BE SURE TO FORMAT DATA AGAIN in TWRP after flashing OREO and MK2000 to have a clean start. Would be nice if it was mentioned in this tutorial.
the_R00ter said:
i am making this post because i have an lg v20 running 20h. there was no root guides available, so i decided to root mine using an older guide. it succeeded, but was very hard and time consuming. Being a noob at the time, i was also extremely nervous that i could possibly brick my phone or screw something up. i didn't, and no part of this should brick yours either. ***However - if you do somehow break your device in any way, that is on you. by completing these steps, you assume full responsibility. now that we have that out of the way, lets continue. at the end of this guide, you should have a rooted device with your choice of os (7 or 8 - or even a custom rom if you choose!). you should also have twrp. this guide would not have been possible without users runningnak3d and clsA
**** Also, during this Proccess, Your Phone WILL be wiped clean!!! don't forget to back up photos, videos, etc...*****
don't download any other files than from this guide.
1. download these files (required) https://lg-firmwares.com/downloads-file/4578/H91510e_00_VTR_CA_OP_1205.kdz (for a rootable os that we can flash, - get this also (required) https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222 this program is called lg up and has been patched to work with this phone. you will also need this. https://androidfilehost.com/?fid=1322778262903990218. these are the root files and need to be all in the same folder as where lg up is installed. you will also need to have access to fastboot and need to have adb installed. that is pretty easy, give it a google search if you still need help.
if you are running 32 bit, get this https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads
this is the OS. get nougat, which has like three less steps (you can't upgrade to oreo on this os once rooted) or scroll down and get the oreo file. nougat (really old version) https://drive.google.com/file/d/1S82HVNt2rAtXgBY499IBJnoCVFnpCf_X/view
Oreo - get this first file, and the ones under it. https://www.androidfilehost.com/?fid=1322778262904015326
***https://androidfilehost.com/?w=files&flid=283977*** You have to have this file if getting oreo. if you chose nougat, then don't get this.
2. Now that you have everything downloaded and installed, put your phone into download mode. (power it off, hold the volume down button and plug in a usb c cable attached to your pc. don't stop holding volume down until you see download mode.)
3. once it is in download mode, open up lg up. select your device, (it should be in standby mode, according to lg up) and click dump (this is a total backup of the phone, you are lucky you know this right now, I didn't when i rooted mine) . it will bring up a file explorer, select where you want it to save to. (I chose my desktop). once you have a folder selected., it will bring up a bunch of options for partitions. click select all and uncheck user data. ****Make SURE that you don't unplug your phone during any part of this process or any other process in this guide, it will permanently brick it. ***** ow that you have selected everything but userdata, click start.
4. once that finishes, you will have made a full backup of your phone in case something goes wrong.
then click the partition DL button and select the h915 v10e kdz file (the file that i said was the rootable os we can flash) (the first file you downloaded). make sure bin file stays checked. then click start. once that finishes, your phone should automatically reboot into an old nougat operating system. then go to settings, enable developer options, and turn on usb debugging. that is easy, if you can't figure it out, google is your friend. now you should have no cellular signal. this is not the permanent ROM.
5. go to the play store and download terminal emulator for android. (once usb debugging has been enabled
then go ahead and go to the folder where you extracted the root files/package. hold shift and right click to open a command windows there or powershell, whatever your pc says. open 2 of those windows. then, in the first one, type, adb logcat -s dirtysanta
****don't close this window.*****
then in the other window, type STEP1.BAT
*****don't close this window.***** It may take a minute, but after a while it will let you type again. once you can, type run-as con
chmod 0777 /storage/emulated/0/*
6. then, pull up the window you used the logcat command in. leave it there so you can watch it
then, on your phone, go to the terminal emulator and type applypatch /system/bin/atd /storage/emulated/0/dirtysanta
once you do that, glance at the logcat window. once it says to run step 2, go to the window where you typed step1.bat. type STEP2.BAT
at this point, your phone should go ahead and reboot and say fastboot mode up at the top. now, go to your window where you typed all the .bats and type STEP3.BAT. wait until your phone reboots and you will see a screen saying that you can;'t use your phone. this is bogus, just ignore it and wait like 10-15 seconds for it to get past that screen. then it will boot that android and you should get a green screen.
Now, quickly, pull the battery from your phone. leave it out for a little while while we prepare the next steps.
If you want oreo, scroll to where it says OREO in capital letters. if you want nougat, scroll to where it says NOUGAT.
NOUGAT
use the file that you downloaded if you selected nougat - it should be a zip. it will be called h910-10r. DO NOT, I REPEAT, DO NOT UNZIP THE FILE. place it on a pre formatted micro sd card. then, place the battery and sd card back in your phone. also, unplug the phone. then, hold down the volume down key and hold hold the power key. once you see the lg logo, release the power key and immediately hold the power key again. then, you should get a screen that asks if you want to reset your phone. use your volume keys to navigate and select yes, then again confirm it. then, after letting it reboot, it should go into twrp. once there, go to wipe\and select format data. then type yes to confirm. then, go back to the main screen and click wipe again. go ahead and click advanced and wipe your dalvik cache. once done, go to home screen and click install. select the select storage option down at the bottom and change to sd card. then find the h910 zip file and install it. then go ahead and reboot your phone, you will have a rooted android 7 rom. you will also have signal. then download supersu from the play store and open it to have root.
OREO
use the file that you downloaded if you selected oreo - it should be a zip. it will be called something along the lines of full stock oreo rooted. DO NOT, I REPEAT, DO NOT UNZIP THE FILE. place it on a pre formatted micro sd card. also, go to your root package folder and find the twrp image file and put that on your sd card. then go get the mk200 zip file and also place that on your sd card. then, place the battery and sd card back in your phone. also, unplug the phone. then, hold down the volume down key and hold hold the power key. once you see the lg logo, release the power key and immediately hold the power key again. then, you should get a screen that asks if you want to reset your phone. use your volume keys to navigate and select yes, then again confirm it. then, after letting it reboot, it should go into twrp. once there, go to wipe\and select format data. then type yes to confirm. then, go back to the main screen and click wipe again. go ahead and click advanced and wipe your dalvik cache. once done, go to home screen and click install. select the select storage option down at the bottom and change to sd card. then find the oreo full rooted zip and install it then, install the mk2000 file. after you have done this, click install image and select the twrp. the reason you need to re flash this is because that oreo file re installs the stock recovery. then install the twrp. now reboot your phone. you will have a rooted android 8 rom. you will also have signal. then download a magisk 6.0 manager apk from chrome browser to have root.
IF this worked and your enjoying root give me a thanks.
Click to expand...
Click to collapse
hey reply to me fast is it ok to flash h915 firmware in my h910 10I cuz already hard bricked the previous h918 motherboard cuz I don't know I accidentally flashed h990 firmware plz tell me also is it necessary to flash h915 in h910 to root and TWRP.
Isn't that what it says in the OP?
pakwarrior said:
hey reply to me fast is it ok to flash h915 firmware in my h910 10I ....
Click to expand...
Click to collapse
MaverickNextDoor said:
Isn't that what it says in the OP?
Click to expand...
Click to collapse
Dont try to install h915 instead just try dirty santa method which will install temporary twrp recovery there install h910 20h pre rooted 8.0 rom and install mk2000 v2.2 kernel and install newer version of twrp and you are good to go
No bricking risk and nothing dont try to do corss flashing of h915 its not that accurate also there is model issue in crossflashing instead doing that do dirsty santa and install h910 20h simple
pakwarrior said:
Dont try to install h915 instead just try dirty santa method which will install temporary twrp recovery there install h910 20h pre rooted 8.0 rom and install mk2000 v2.2 kernel and install newer version of twrp and you are good to go
No bricking risk and nothing dont try to do corss flashing of h915 its not that accurate also there is model issue in crossflashing instead doing that do dirsty santa and install h910 20h simple
Click to expand...
Click to collapse
So how do you use dirty santa method for h910 20h? All the guides I've seen want you to crossflash.
jxsilicon9 said:
So how do you use dirty santa method for h910 20h? All the guides I've seen want you to crossflash.
Click to expand...
Click to collapse
I didn't do crossflashing i first installed twrp throught dirty santa which then you have to open from recovery then there is android 8.0 h910 stock rom pre rooted i used or you can use your custom rom to flash then there is an kernel mk2000 file also to flash from twrp after you installed new rom for fixing errors like static screen and like that thats it also if you flash android 8.0 stock of h910 rom you will get a password during booting process just attempt it wrongs for many trys wrotten on it until you see wipe the data prompt and you will factory reset your phone and its ready to go maybe you will be promoted to twrp so you have to factory reset through wipe option ok and you are good to go one thing do it only on h910 not other model there is 0% chance of hard bricking your phone if you did this and no signal problem
Also to understand more go a see my qna with author of this post in this post obviously ok or if you meed more help reply me i will text you
pakwarrior said:
I didn't do crossflashing i first installed twrp throught dirty santa which then you have to open from recovery then there is android 8.0 h910 stock rom pre rooted i used or you can use your custom rom to flash then there is an kernel mk2000 file also to flash from twrp after you installed new rom for fixing errors like static screen and like that thats it also if you flash android 8.0 stock of h910 rom you will get a password during booting process just attempt it wrongs for many trys wrotten on it until you see wipe the data prompt and you will factory reset your phone and its ready to go maybe you will be promoted to twrp so you have to factory reset through wipe option ok and you are good to go one thing do it only on h910 not other model there is 0% chance of hard bricking your phone if you did this and no signal problem
Also to understand more go a see my qna with author of this post in this post obviously ok or if you meed more help reply me i will text you
Click to expand...
Click to collapse
Ok,you know where to get the latest firmware and files? Most dirtysanta tutorials bat have the downgrade added. How do I just add the twrp without the downgrade? Any dirtysanta bat and files?
jxsilicon9 said:
Ok,you know where to get the latest firmware and files? Most dirtysanta tutorials bat have the downgrade added. How do I just add the twrp without the downgrade? Any dirtysanta bat and files?
Click to expand...
Click to collapse
no no need to downgrade anything just find any video which says TWRP installation for LG v20 h910 dirty Santa and flash it but wait I seen in all zip files of dirty Santa there will a final step in that folder called step 3 that file is a batch file just open it in notepad and you will see there is written TWRP for I think us995 just rename it all of them to that name which TWRP in that folder ok for example if the name of the TWRP in dirty Santa folder is twrph910.img
you have to rewrite the same and exact name with .img in that batch file this ting will not tell any YouTuber or in the website cuz, I find it in curiosity and founded that the TWRP name was wrong so I just renamed it in that batch file and it worked before it it wasn't working also download the exact LG v20 h910 TWRP, not any other model TWRP or you will hard brick it man it feels so bad I one time hard bricked my LG next day I bought the device now I just sold it I change the mobo to LG h910 then I did all that root things and then I sell that phone no I have sony xz3 which is way better and have snapdragon 845 octa-core which is the thing I needed in just 135$ I found that it was japan model refurbished but has all things new and original like poled panel and stuff... well if you need more help just don't reply m on XDA you will not get the answer quickly here my social media account
discord: PAKWARRIOR#6115
Facebook: https://www.facebook.com/hafiz.saad.712161/
Instagram: https://www.instagram.com/zero_saad_sixs/
reply me on that I am online all the time but not online on XDA all the time ok
Installed twrp no problem. Had installation issues (error 7) and edited the file. Tried it again and came up with error 1. Saw someone else on xda say to extract the boot img and mount to the recovery partition successfully. Welp, I guess I wasn't so lucky. I can not get into twrp recovery or any recovery and my v20 (910) boots into the Lg android splash screen. My desktop can not see any adb device but it registers a device being plugged in. What's the verdict, soft or hard bricked? Everything was cleared besides twrp prior to error 7 and 1.
Lgv20usr said:
Installed twrp no problem. Had installation issues (error 7) and edited the file. Tried it again and came up with error 1. Saw someone else on xda say to extract the boot img and mount to the recovery partition successfully. Welp, I guess I wasn't so lucky. I can not get into twrp recovery or any recovery and my v20 (910) boots into the Lg android splash screen. My desktop can not see any adb device but it registers a device being plugged in. What's the verdict, soft or hard bricked? Everything was cleared besides twrp prior to error 7 and 1.
Click to expand...
Click to collapse
Re-flash the H91510e_00_VTR_CA_OP_1205.kdz with LG UP. And again.
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
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.