Database Info

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

Tablet: Samsung Galaxy Tab 2 10.1 (GT-P5113) Wifi only.
OS: Android 4.2.2 Jellybean
Build#: P5113UEUCMK3
So here is what I have done:
Ran Odin v3 1.85 and pushed CF-Auto-Root-expresso10wifi-expresso10wifibby-gtp5113.tar.md5
I followed the instructions to the letter. The Odin process runs, red Android screen....tablet process runs...neither process reports errors...No Root.
When I try SuperSU I get "There is no SU binary installed...." blah blah see it all over the forums but nothing I have tried has fixed either problem. I even put the SuperSU.apk on a micro SD and it won't install over to replace the binary. SuperSU does not show up in my Applications list so I cannot remove it.
So I did hard resets, wiped cache etc..
No change.
Next I downloaded the factory ROM P5113UEUCMK3_P5113XACCND2_HOME.tar.md5 from Samsung and pushed it over successfully.
No change.
I cannot get root to take so I cannot manually remove SuperSU using a file manager (requires root)
I would really like to get my tablet rooted so i can install other apps.
Any one with information that will help me solve this will be my new hero...briefly...
Thanks in advance!

Did you check "unknown sources" in security/developer section?
Pp.

PanchoPlanet said:
Did you check "unknown sources" in security/developer section?
Pp.
Click to expand...
Click to collapse
Yes I did.

I'm having the exact same problem with my P5110.

Is anyone really gonna help here?
I have the same issue with GT-P3113.

To root or not to root?
Which one is it people? If you can't file explore because you don't have root you just delete SU from your apps (Manage apps) drawer.
Then you just go about your typical rooting, following the Op instructions and your done.
Pp.

I can only turn on and off supersu, can't delete or uninstall it.
Also despite turning it off and checking the appstore, there's no uninstall button, even when I did update it with a new apk it still won't do anything. Still says the same thing. no Binary and can't even install one.

PanchoPlanet said:
To root or not to root?
Which one is it people? If you can't file explore because you don't have root you just delete SU from your apps (Manage apps) drawer.
Then you just go about your typical rooting, following the Op instructions and your done.
Pp.
Click to expand...
Click to collapse
As I mentioned SU is not in my App manager and therefore cannot be removed. I attempted to download and install the SU apk from micro SD and it failed.
So I am stuck with no root and unable to get a file manager running to manually remove SU.

I have the same problem with my P3113

Do you have a custom recovery (CWM or TWRP) installed? If so you can download and flash the latest SuperSU.zip
Sent from my Nexus 4 using XDA Premium HD app

Well I had the exact same problem, and I think that the SuperSU included on the CF-Auto-Root file is outdated or something.
I was on android 4.2.2 but I have the Galaxy Tab 2 10.1 P5110.
I searched the forums and came up with a solution for our problem. I think that SuperSU is outdated on that CF-Auto-Root file or it was the custom recovery that it installs thats outdated or messed up for android 4.2.2, because right after it does its thing, we get the tablet default recovery again.
Since I dont know how to make a new CF-Auto-Root file, I tried to install an updated custom recovery through Odin3 instead of the CF-Auto-Root file, and it worked. Then I entered on the TWRP recovery and installed an updated SuperSU, restarted the tablet, and it worked too. I had now a rooted tablet with a permanent custom recovery, So i followed to install a custom rom, etc.
So now the steps I did:
(I am not responsible if it doesnt work for your tablet and messes something up or brick it, so please follow on your own risk, or maybe wait for some expert on this things to say if its safe or not. All i know is that it worked for me.)
Step 1: Download Stuff
Download and install samsung usb drivers
Go to Samsung website and search for your device. Go to downloads and download the USB Driver and install it.
Download Odin3 1.85_3
Go to this topic and download Odin3 3.85_3 from the "What you need:" section. Extract it on your computer.
Download TWRP recovery
Go to TWRP website, click "Get TWRP for your device", search for 5110 (doesn't have the 5113 version, and I think that the 5110 is the same and works too), scroll down to "Download - Odin Flashable Tar:" and click the "5110 only" version. It will open another page, scroll down for the most recent version and download the .tar file. Extract it on your computer.
Download SuperSU for TWRP
Go to Chainfire website and download that SuperSU version for TWRP. Dont extract, just put it on your SD card for the tablet.
Step 2: Doing stuff.
Install samsung drivers, extract Odin to your computer and put the SuperSU file on your SD card for the tablet.
(To avoid confusion about using the Volume rocker switch, I'll refer to side closest to POWER button as LEFT/Volume DOWN and side away from power switch as RIGHT/VolumeUP. )
1: Turn off the tablet and restart it on download mode. To enter download mode, press Power Button + Volume Right. When the warning appears press Volume Left to enter download mode.
2: Now open Odin3 1.85, click PDA, select the TWRP .tar file you downloaded.
3: Make sure to uncheck the "Auto Reboot" option. The only checked thing must be "F. Reset Time".
4: Connect usb cable to tablet. Press start. When it finishes, the box will turn green and says "pass!" you can remove the cable.
5: Now press Power button + Volume Left. Keep pressing it, the tablet should restart and when the samsung galaxy tab 2 screen appears, let go of the power button, but keep pressing Volume Left until the TWRP recovery screen appears.
6: Now inside TWRP recovery menu, press Install. On the top part of the screen press Storage and and change to external storage or SD card. Now select the SuperSU file and install it by swiping that thing. After it install and says successful, press reboot.
Congratulations ! Now you have successfully rooted your tablet and you have a permanent custom recovery ! You can now install a custom rom, etc.
Some notes:
I used TWRP recovery because i used it on my smartphone. So thats what I learned to use, so I used it on the tablet too. Feel free to use other custom recovery and adapt the tutorial for it.
It worked for me. If it doesn't work for you, or something is failing on some step, try to read everything again and re-do.
Credits:
* I based this on this topic and its replys (the last comment on this page.)
* Also credits for the Odin3 creator, SuperSU creator and TWRP team.
I just put together things from here and there, but without this persons, creators and stuff, we would not be able to make this happen.

TUTORIAL-ROOTED SM-T235 5.1.1 Lollipop Tab 4 7.0 LTE finally!

The following is an outcome of an initial post I put up in Q&A regarding achieving root on the SM-T235 for the 5.1.1 Stock Rom (and subsequent questions and dialog with other forum members on issues) I have tried to clean up the posts here but am retaining most of them as it shows the issues other users went through (and feedback perhaps useful to some) The TWRP version is key here and it is what was seen as enabling correct flashing of the SU zip to achieve root. So hope this helps!
I used the following firmware today as a demonstration (have tried now all available 5.1.1 firmwares (successfully) except the DBT which does not flash fully for some reason)
https://www.androidfilehost.com/?fid=24269982087020611
which is AUT-T235XXU1BOH7-20151217085736.zip
ROMs are available here
http://forum.xda-developers.com/tab-4/general/links-galaxy-tab-4-official-lollipop-5-t3102844
I took out external sd (so NO EXTERNAL SD..no linkstosd nothing of the sort)
(TO NOTE-I simply took out the external SD and worked with just the internal storage for THIS demonstration to weed out the issue as other members posting on my original thread were not able to achieve the root I was able to get-it is not absolutely necessary and you could have your SU zip and any other files on the external SD however it is a good idea to keep it simple initially)
SO...I went to TWRP
TWRP is the one attached here in this post (from the thread below but may be different as the OP got updated-however the one I have attached works!)
http://forum.xda-developers.com/tab-...a1-sm-t3027059
You will see in this post that has a picture of the previous OP, the file name is what I have
http://forum.xda-developers.com/show...1&postcount=52
anyway, not sure if there are any differences but am using what works for me (the attached file)
So i did the following which may contain extra or unnecessary steps-no harm though in doing them-as I was trying to demonstrate the rooting process relative to issues other forum posters were having
(EDIT-VERIFIED-you could simply start at step 4 below where you go into download mode to flash the rom (but have the SU zip on external SD card unless it is already in the internal sdcard) and also uncheck autoreboot in Odin (do NOT check repartition!) so that once the rom has been flashed you do not have to boot up the rom, but then reset odin, again go to download mode, again uncheck autoreboot, flash TWRP, then go to recovery (do not boot rom), and flash SU zip and then only boot up-thanks frenkie9999999)
Otherwise this is what I did
1) complete wipe data, cache, system, dalvik all 2 times just for good measure
2) format internal sd (note NO external sd card) (no SIM either but that is because I need my phone working during this process and my SIM is on the T705)
3) reboot to download (do NOT install SU by twrp)
4) Used odin 1.85
5) flash the rom above (or the country firmware of your choice)
6) once device boots up do not connect to anything NO google, no wireless nothing
7) just go to settings, enable development and usb debugging (just what I do normally and mock locations) and in security allow for unknown sources, in google settings I uncheck ALL options
8) do not set up anything else
9) connect device to the laptop
10) copied over the beta 2.65 latest chainfire and root explorer apk that I have (to internal storage...see pictures...I do not have anything else in the internal card, and do not have any external card)
Chainfire's SU zip is from (credits to him for his awesome work for many many years now)
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
credit goes to K94U for this post that helped me achieve root on the T235 (not my original work as such but just listing the steps here as there were no explicit instructions for the T235)
http://forum.xda-developers.com/showpost.php?p=64182938&postcount=15
11) disconnected device from the laptop
12) went to download mode
13) odin 1.85 again and this time the TWRP recovery I have attached
14) did not let it boot up.,,,forced it to recovery by first pressing power, vol down and home to get to the choice of download or continue to reboot...
15) chose continue to reboot
16) immediately switched to power, vol up and home to get to TWRP
17) flashed the SU zip
18) do not install SU as prompted by TWRP
19) let it reboot
20) found SU in the installed apps in launcher
21) opened up SU and checked the options I want
that was it...opened root explorer and sure enough have root
Google may prompt accept. decline check apps...I always decline and then go to google settings and uncheck those pesky secuirty options as well (if not done already)
the TWRP version is important as the one I have attached works for the purpose of flashing the SU zip to get root correctly
here are the screenshots and the TWRP tar

Got xposed working too wanam arm (32) v78.1 sdk22
Sent from my SM-T235 using XDA Free mobile app

@mac231us
Doesnt work for me. Did everything as your thread guides but i still can't get the SU permissions.
Enabling SuperSU gives me the note "There is no SU binary installed[...]"
Any idea what i did wrong?
1. Flashed to 5.1.1 from CM12.1 and didn't boot
2. Flashed TWRP and booted directly to recovery
3. Flashed BETA-SuperSU-v2.62-20151210170034 and reboot
4. Got SuperSU app installed but it don't let me launch it (not installed binaries)

tyktak said:
@mac231us
Doesnt work for me. Did everything as your thread guides but i still can't get the SU permissions.
Enabling SuperSU gives me the note "There is no SU binary installed[...]"
Any idea what i did wrong?
1. Flashed to 5.1.1 from CM12.1 and didn't boot
2. Flashed TWRP and booted directly to recovery
3. Flashed BETA-SuperSU-v2.62-20151210170034 and reboot
4. Got SuperSU app installed but it don't let me launch it (not installed binaries)
Click to expand...
Click to collapse
that is odd..i just did a fresh install..wiped fully formatted...went to download (do NOT install SU as twrp prompts) odin flashed the 5.1.1 (nordic)...in fact this time even rebooted and set up google account..then went back to download...installed twrp again...again rebooted but this time straight to twrp...then installed the latest su 2.62-3...rebooted (again do not check the SU install prompted by TWRP)...and the su app was there..and so was the binary
noticed chainfire now has BETA-SuperSU-v2.64-20151220185127.zip
curious did you do a 5.1.1 odin flash from cm12.1 or a twrp nandroid recovery...just wondering if it makes a difference
twrp is from here
http://forum.xda-developers.com/tab-4/general/sm-t235-lte-rooted-twrp-2-8-alpha1-sm-t3027059
again...am only speaking of the T235 (or T235Y) not any other variant
the 5.1.1 I used is from here
https://www.androidfilehost.com/?fid=24052804347821380
in order to prevent stock recovery from coming up always first go to download step (not actual download) but using the volume down, power and home to get to the choice of download and reboot..then reboot but quickly go to volume up home and power to get to the twrp recovery

@mac231us
Aww, i cant get it working..
Did exactly what you said:
1. Format everything from TWRP (5.1.1 rom)
2. Flash 5.1.1 (nordic)
3. Configure google account
4. Back to download and flash TWRP
5. Back straight from download to recovery
6. Flash 2.62-3 and reboot (didnt checked the SU install prompted by TWRP)
7. When i open SuperSU app i am getting exactly:
There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgrade to Android 5.0, you need to manually re-root - consult the revelant forums for your device!
Click to expand...
Click to collapse
Btw. i am getting red and blue text when booting - Kernel is not seandroid enforcing.
Galaxy Tab 4 7.0 LTE (SM-T235)

EDIT...also
tyktak said:
@mac231us
Aww, i cant get it working..
Did exactly what you said:
1. Format everything from TWRP (5.1.1 rom)
2. Flash 5.1.1 (nordic)
3. Configure google account
4. Back to download and flash TWRP
5. Back straight from download to recovery
6. Flash 2.62-3 and reboot (didnt checked the SU install prompted by TWRP)
7. When i open SuperSU app i am getting exactly:
Btw. i am getting red and blue text when booting - Kernel is not seandroid enforcing.
Galaxy Tab 4 7.0 LTE (SM-T235)
Click to expand...
Click to collapse
cannot think of anything else at the moment except that am using older version of odin v 1.85 (i too get the red and blue text..the recovery is not default as simply rebooting to recovery takes one to the stock unless doing the 3button to download to recovery process to get to twrp)
try it again w odin 1.85 and maybe go back to the way I 'instructed' the first time (where I did not set up the rom at all and went back to straight to twrp and flashed supersu...formatting internal storage is important but think you are doing that already)
you may want to ask some of the other folks who also got root
though imo there were no explicit instructions but enough for me to go on with..here....
http://forum.xda-developers.com/tab-4/general/sm-t235-lte-rooted-twrp-2-8-alpha1-sm-t3027059/page15
except for K94U's post here which was very informative
http://forum.xda-developers.com/showpost.php?p=64182938&postcount=15
and
http://forum.xda-developers.com/tab...laxy-tab-4-t3264281/post64216314#post64216314
EDIT another thought i may have done this at some point do not recall (but not today for example on this new installation) is to format the internal card using the stock recovery itself after installation of the odin-rom
then do the other steps of twrp etc from download mode again

@mac231us
Giving up and waiting for CM13.
I've did everything exactly how it should be done and SuperSU is showing information about mising SU binary.
Tried every SuperSU zips from Chainfire but effect was the same every time even with fresh flash of nordic rom and recovery. Ive tried cleaning data through stock recovery but it didnt helped.
Thanks for trying.

tyktak said:
@mac231us
Giving up and waiting for CM13.
I've did everything exactly how it should be done and SuperSU is showing information about mising SU binary.
Tried every SuperSU zips from Chainfire but effect was the same every time even with fresh flash of nordic rom and recovery. Ive tried cleaning data through stock recovery but it didnt helped.
Thanks for trying.
Click to expand...
Click to collapse
Apparently some users need these additional steps to fix supersu:
11. - Reboot Tablet, and from you PC extract the originally downloaded SuperSU 2.6x file on you PC, and navigate to the common directory on the extracted folder, and copy the superuser.apk file to your tablet.
12. - Make sure that you have Unknown Sources checked in the Device administration section of security settings so that you can install superuser.apk.
13. - Install superuser.apk
Also, SuperSU 2.64 fixed my kernel enforcing msg on boot...

@K94U
Still the same. I'll try flash KK then LL and try again whole process instead of CM12.1 -> LL.
I will let you know if it helped.
Btw. Chainfire published version 2.65 today

tyktak said:
@K94U
Still the same. I'll try flash KK then LL and try again whole process instead of CM12.1 -> LL.
I will let you know if it helped.
Btw. Chainfire published version 2.65 today
Click to expand...
Click to collapse
another wild guess is put all your supersu zip and apk files onto the internal storage itself
you will boot into the rom (now seeing that it does not matter if you boot into rom and then go back to download, odin the twrp, flash the supersu zip or that from odin rom directly go to download again, twrp odin and then flash supersu zip as both worked for me-not sure if there really is any technical difference)
you will need to boot to rom anyway especially after formatting and in order to put the supersu apk as K94U mentioned onto the device and then go back to download and do the recovery etc steps
after yesterday's fresh install the way of booting into rom, then going back to download etc (so this process has worked 2 ways, 4 times so no fluke understand some little differences may exist) i was doing backups only to find that when i actually went to the sd card no backup was there although i could transfer files back and forth between storage and the sdcard and computer and sdcard...so finally it was the sdcard that was bad...now all is working fine with backups after switching to different sdcard and using the ridgecrop 32formatter
http://www.ridgecrop.demon.co.uk
32bit version

@mac231us
Is that possible there is something wrong with the downloaded rom and it causes the problems?
When i get "upgrading" notice after flashing, bar goes 1/4 and then show "erasing".
I'll download germany 5.1.1 and try again. Totally no idea what's wrong. Maybe Link2SD has broke mine partitions or something.. after flashing SuperSU it didn't created any folders in /system
I've unmounted my sdcard but recovery still shows it as possible to wipe.
EDIT: After flashing Germany 5.1.1 there is still Erasing in 1/4 way of upgrading software..
EDIT2: Tried again with differrent usb cable and its the same.
EDIT3: After flashing SuperSU and reboot, device is starting and there is a samsung logo for a few secs and then there is a second reboot but with sound at samsung logo.

tyktak said:
@mac231us
Is that possible there is something wrong with the downloaded rom and it causes the problems?
When i get "upgrading" notice after flashing, bar goes 1/4 and then show "erasing".
I'll download germany 5.1.1 and try again. Totally no idea what's wrong. Maybe Link2SD has broke mine partitions or something.. after flashing SuperSU it didn't created any folders in /system
I've unmounted my sdcard but recovery still shows it as possible to wipe.
EDIT: After flashing Germany 5.1.1 there is still Erasing in 1/4 way of upgrading software..
EDIT2: Tried again with differrent usb cable and its the same.
EDIT3: After flashing SuperSU and reboot, device is starting and there is a samsung logo for a few secs and then there is a second reboot but with sound at samsung logo.
Click to expand...
Click to collapse
the DBT 5.1.1 has never worked for me (flash failed always) (am in the USA btw not that it makes a difference)
the ones that have worked are (have tried all of them at one time or the other when I was experimenting getting root type control (removing unwanted system apps, deodexing etc by flashing zips to perform certain mods/functions))
do not have any special apps like link2sd...i recommend removing external sdcard altogether and just working w the internal storage for now
LTE SM-T235 XXU1BOH7 AUT Region (Switzerland)
--LTE SM-T235 XXU1BOH7 NEE Region (Nordic Countries)
--LTE SM-T235 XXU1BOH7 SER Region (Russia)
--LTE SM-T235 XXU1BOH7 SKZ Region (Kazakhstan)

tyktak said:
@mac231us
Is that possible there is something wrong with the downloaded rom and it causes the problems?
When i get "upgrading" notice after flashing, bar goes 1/4 and then show "erasing".
I'll download germany 5.1.1 and try again. Totally no idea what's wrong. Maybe Link2SD has broke mine partitions or something.. after flashing SuperSU it didn't created any folders in /system
I've unmounted my sdcard but recovery still shows it as possible to wipe.
EDIT: After flashing Germany 5.1.1 there is still Erasing in 1/4 way of upgrading software..
EDIT2: Tried again with differrent usb cable and its the same.
EDIT3: After flashing SuperSU and reboot, device is starting and there is a samsung logo for a few secs and then there is a second reboot but with sound at samsung logo.
Click to expand...
Click to collapse
Here the same for me. Like Tyktak I ve tried every every step like him but not work for me too.
I

Will do flash, root etc from scratch once more tomorrow taking pictures along the way and post here...maybe by evening U.S time
Sent from my SM-T705 using XDA Free mobile app

deleted
mostly replicated/cleaned up in the OP now

@mac231us
Thanks mate, it worked!
The reason was probably the newer TWRP which was 2.8.7.0 Add this tutorial as new topic in general section of Galaxy Tab 4.
@frenkie9999999

tyktak said:
@mac231us
Thanks mate, it worked!
The reason was probably the newer TWRP which was 2.8.7.0 Add this tutorial as new topic in general section of Galaxy Tab 4.
@frenkie9999999
Click to expand...
Click to collapse
AWESOME!...yes was thinking about the TWRP yesterday so posted it this morning along with the other steps.
have requested moderator to move the thread to the General section.

@mac231us
Don't forget to edit first post so ppl won't have any problems

YesssSSS! Twrp 2.8.1.0 !!!!
Works great!!!
Thanks Mac231us!
Thanks tyktak!
-Flash TWRP 2.8.1.0 recovery with odin3 1.85 (without re-stocking) -dont forget UNCHECK "autoreboot" on odin.
-WIPE CACHE & DALVIK
- Flash SuperSU 2.65
enjoy!
---------- Post added at 11:38 PM ---------- Previous post was at 11:37 PM ----------
thanks mr. Chainfire!!!!!!
without you Android will never be the same

Thanks a lot !
I followed every step and I was successful . Everything worked .
My tablet is rooted again !

LEAGOO M5 - Development & Support

In order to keep this thread clean, please use this one to discuss about Development, Support or Software Updates.​
ROMs:
To avoid any possible issue, do not forget to backup your NVRAM so that you won't risk to lose your IMEI. How-to: http://www.anythingultimate.in/2015/11/how-to-backup-your-nvram-partition.html
Custom ROM
- CyanogenMod 13 Beta 2 by "smurad-05": https://mega.nz/#!kMcRwTDb!1yrNzrP_XvqGyPcXzNF9eSRKfj1DpFixkUaNz_3OPAY​
Stock (Android 6.0)
- 20161202: https://yadi.sk/d/rYoOTrUT32xDuL or http://www.leagoo.com.my/support/firmware/
DO NOT USE THE "Format All & Download" OPTION IF YOU CARE ABOUT YOUR IMEI! Choose "Download Only" instead.
Previous Releases:
- 20160909: http://leagooftp.com.my/M series/M5..._WF562G.LEAGOO.M0.HB.H.SSA.B18.0909.V3.03.zip
- 20160808 by "smurad-05": https://mega.nz/#!8V93SYaI!E4FOHWBxCFU6TKFmjguu7x3A3590Zt2W-c9KgNLgOLU
Flash Tool
- SP Flash Tool v5.1628 for Windows & Linux: https://mega.nz/#F!dYUm0TbB!SWeMLb5Wu1NbRzTPQ8-s_A​
Recovery:
- TWRP (Universal), use the Scatter that comes with the latest Stock ROM linked above: https://github.com/VRNWALLE/Android/raw/master/MT6580/Leagoo m5/TWRP/recovery.img​
Root:
Rooting Methods (if you are on Stock ROM)
- SuperSU (flashable using TWRP): http://forum.xda-developers.com/apps/supersu​
Extras (Root-Only):
Customization
- Xposed Framework: http://forum.xda-developers.com/showthread.php?t=3034811​
Useful Third-Party Apps:
Battery Life
- Amplify: https://play.google.com/store/apps/details?id=com.ryansteckler.nlpunbounce&hl=en
- Greenify: https://play.google.com/store/apps/details?id=com.oasisfeng.greenify&hl=en​

CM13 & TWRP added to first post.

dear my freind, how to install twrp?
thanks

@yamani_25 - Haven't done it myself, but first root your phone (see bottom of http://giveawaytricks.in/install-cyanogenmod-13-leagoo-m5/) then install TWRP the same way but using the recovery.img that's in the TWRP.3.0.2 zip file.

vladhed said:
@yamani_25 - Haven't done it myself, but first root your phone (see bottom of http://giveawaytricks.in/install-cyanogenmod-13-leagoo-m5/) then install TWRP the same way but using the recovery.img that's in the TWRP.3.0.2 zip file.
Click to expand...
Click to collapse
I think install TWRP first than the device can be root. CMIIW
Sent from my M5 using XDA Premium 4 mobile app

yup, first you need TWRP for root the phone with SuperSu..
waiting for tutorial too..
from my x500 on TT

tutorial for installing custom recovery (twrp) and how to root
Hi guys! Here's a tutorial for installing custom recovery (twrp) and how to root Leagoo M5 cellphone.
First turn on the cellphone, go to "Settings>About phone" and enable "Developer options" by tapping on the "Build number" multiple times. Then go one step back, enter the "Developer options" and turn it on, and also enable the "OEM unlocking" and "USB debugging" options
Now you need to install custom recovery by following these steps:
1. plug the cellphone into pc, unzip and manually install drivers by going to "control panel>device manager" (select the device which needs drivers).
drivers are located here
https://drive.google.com/file/d/0B4PwJKhC6foZZnBzY0RPQnhHX2s/view?usp=sharing
2. download to pc and unzip the twrp custom recovery zip file
https://drive.google.com/open?id=0B4PwJKhC6foZc1czcnZtRXQ4eUU
3. download to pc and unzip the Sp Flash tool zip file
https://drive.google.com/open?id=0B4PwJKhC6foZcWJQVThGTGhzaTQ
4. download to pc, but do not unzip the "super su" file needed for root
https://drive.google.com/open?id=0B4PwJKhC6foZQzA0OGtYRTVRWnc
Now copy this "supersu" zip file to cellphone (e.x. into "Download" folder). Once you're done, disconnect the cellphone from pc and turn it off.
5. go into "Sp Flash tool" folder and run "flash_tool.exe" application. Click on the "Download tab" at the top and then on the "Scatter-loading" button to select a path to Scatter file which is needed to flash custom recovery. The file is located in the "TWRP_3.0.2" folder and it is named "MT6580_Android_scatter.txt". The mode for flashing should be "Download only". When you're sure that everything is setup correctly click on the "Download" button located in the top left part of the screen.
6. Now take out a battery from cellphone, wait 5 seconds, put it back in, and just connect the cellphone. Do not turn it on.
Windows (PC) should recognize the device, and the flashing process should start.
Note: if it says that there is no driver, then manually install it by following procedure on step 1.
When the flashing is done you'll see a green checkmark. It's ok now to close the app and to disconnect the cellphone from the pc.
7. Cellphone will boot to startup menu, you should choose "Recovery" to enter TWRP custom recovery.
When you're in recovery go to "Mount" and mount (select) following partitions: protect_f, protect_s, nvdata, System, Cache and Data.
Now it's time to perform root. Go back from "Mount" screen, tap on "Install", find and select "SuperSU_PRO_v2.76_patched_Cobra1111.zip" file and flash it.
When the flashing is done click on "delete cache and dalvik cache", and then reboot cellphone.
8. Let the cellphone boot, it should take a few minutes. When it's booted you'll see the "SuperSU" app installed on your cellphone homescreen.
You're done! Enjoy!
Note:
I've collected these files on the internet. All of credits should go to their authors, so please thank to them!
One more thing. I would advise you to perform nandroid backup of your cellphone. Go into twrp recovery and perform backup (all partitions), save it to sd card and also copy that backup to pc, just in case something goes wrong.
Bye,
cuks

@cuks [emoji482]
from my x500 on TT

tutorial - how to update youtube app
as you all know, youtube app on the Leagoo m5 is an very old version. in order to update it you need to do the following:
note: you have to have a rooted phone
1. install file manager app which can access system partition (es file explorer, root explorer, etc.)
2. start file manager, go to /system/priv-app and move the folder named "Youtube" to another directory outside /system, e.g. to /sdcard/Download
3. restart the phone
4. install the youtube app from the google play
enjoy!

cuks said:
as you all know, youtube app on the Leagoo m5 is an very old version. in order to update it you need to do the following:
Click to expand...
Click to collapse
ARGH, didn't noticed this, but really, the youtube app got frozen every time on the stock rom. That's why i changed to this Cyanogen.

That's the reason why I wrote this tutorial
What are your experiences with cm rom? Are you satisfied? Is there any bugs? What's about battety life?

cuks said:
That's the reason why I wrote this tutorial
What are your experiences with cm rom? Are you satisfied? Is there any bugs? What's about battety life?
Click to expand...
Click to collapse
Not sure about battery life sorry, i'm trying to keep it charged
But i still have problems with youtube (however i'm not an experienced user): sometimes it halts, mostly in 720p/HD videos. The picture freezes, audio is working. Sometimes the video gets zoomed to the left upper corner with a black banner in the left. This could be an app-problem though.

cuks said:
That's the reason why I wrote this tutorial
What are your experiences with cm rom? Are you satisfied? Is there any bugs? What's about battety life?
Click to expand...
Click to collapse
Oops, fingerprint sensor doesn't work with CM.

Well, that's bad.
I have thought that the cm rom has the all functionality.
Better to stay on stock rom then. Only problem with it is sending images from within whatsapp, because it works on only one awkward way.

i wrote this before, without kernel source fingerprint cant work, same problem on my Leeco Le 1s..
from my x500 on TT

I cant scan the whatsapp web QR code with stock rom... (Whith third apps i can)
Today Leagoo launched a new patch LEAGOO_M5_FreemeOS_20160728_TEST with some bug fixed.

Is there a way to un-root after fixing YouTube? MobileIron refuses to work on a rooted phone, probably because it's a security hole.
Thanks!

you can unroot directly from SuperSu apk.. try it..
from my x500 on TT

Hello guys,
i have a problem with my battery ( drain out too fast - 25% in 30 min - and charge really slow - full charge in 6h+ !!! )
I suspect that this is caused due to the official update i made but the strange thing is that my mother's m5 with the same update is ok.
Is there any " official " way to go back to the original version to check it without doing all this process you analyzed ?
Ps. I checked my apps / settings, cleared chase, made factory reset, changed charger, checked my battery with apps and is in a good condition,
so i concluded that problem has to be there. Any ideas ?

divinitygr said:
Hello guys,
i have a problem with my battery ( drain out too fast - 25% in 30 min - and charge really slow - full charge in 6h+ !!! )
I suspect that this is caused due to the official update i made but the strange thing is that my mother's m5 with the same update is ok.
Is there any " official " way to go back to the original version to check it without doing all this process you analyzed ?
Ps. I checked my apps / settings, cleared chase, made factory reset, changed charger, checked my battery with apps and is in a good condition,
so i concluded that problem has to be there. Any ideas ?
Click to expand...
Click to collapse
GPS on maybe?
from my Leagoo M5 on TT

[Stock ROM][Combination][RMM state solution][GUIDE AIO] and many more for M30s

What's currently included in this thread :-
TWRP (With/without magisk)
Installing EdXposed
Root with magisk (not recommended due to bootloops, use twrp with magisk)
RMM state Prenormal solution
Stock and combination firmware and Kernal source Gdrive links
Tools for flashing and downloading latest firmware
Post 2
Hide bootloader unlocked warning message
DeGoogle & debloat M30s and install MicroG
Enable Haptic feedback on m30s (or any other samsung phone)
BACKUP YOUR EFS PARTITION BEFORE DOING ANYTHING​If EFSpartition is corrupted or lost, you would not be able to get calls and wifi and your IMEI will be permanently lost.
There is currently no way of restoring corrupted EFS partition since it is device specific, so flashing stock firmware will also be useless
Here is one guide. follow this or any other that works for you.
Here is another (droid view.com/restore-efs-imei-galaxy-s7/)
OR You can Backup all partitions using twrp (nandroid backup) and store in someplace safe (make sure to tick all partitions including EFS)
This is an excellent guide regarding EFS (thanks to @PlayingPoise). I HIGHLY RECOMMEND READING IT BEFORE PROCEEDING.
TWRP (With/without magisk) (huge thanks to @santhoosh)
Thread
there are two .tar files, flash the one you need
Pro Tip: I would recommend Smalipatcher module to reboot directly into magisk system.
Installing EdXposed
See This for installation video OR This Or This for installation guide.
This, for official website
And This for github!
NOTE: v0.4.6.0_beta from github requires custom magisk otherwise the system wont boot since github hosts alpha versions, so i advice to follow the video tutorial since it has installed the most stable EdXposed
Rooting with Magisk (Currently causing random bootloops since custom Kernal is req., i recommend flashing twrp with magisk)
From magisk official repo and This Link, Both are same, but i just wanted to make AIO thread)
thanks to @santhoosh and @topjohnwu
Unlocking Bootloader
Normally I wouldn’t provide instructions for this, but since things had changed drastically from previous Samsung devices, and there are some caveats, I figure this would be helpful.
* Allow bootloader unlocking in Developer options → OEM unlocking
* Reboot your device to download mode. Either use adb reboot download, or use turn off m30s, press vol+ and vol- simultaneously (while powered off) and connect to pc.
* Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Just when you think the bootloader is unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will reject any unofficial partitions before VaultKeeper explicitly allows it.
* Go through the initial setup. Skip through all the steps since data will be wiped again later when we are installing Magisk. Connect the device to internet in the setup!
* Enable developer options, and confirm that the OEM unlocking option exists and grayed out! The VaultKeeper service will unleash the bootloader after it confirms that the user has the OEM unlocking option enabled.
* if there is no OEM unlock option, set phone's date to 7+ days and back and now see.
* Your bootloader now accepts unofficial images in download mode.
Instructions
* Download the firmware for your device.
* Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5
* Install the latest Magisk Manager
* In Magisk Manager: Install → Install → Select and Patch a File and select the AP tar file.
* Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar
* Copy the patched file to your PC with adb pull /sdcard/Download/magisk_patched.tar. Do not use MTP as it is reported to corrupt files.
* Reboot to download mode, and flash magisk_patched.tar as AP in Odin, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
Important: Uncheck “Auto Reboot” in Options!
* Magisk is now successfully flashed to your device! But there are still several steps before you can properly use the device.
* We now want to boot into the stock recovery to factory reset our device.
* Full data wipe is mandatory! Do not skip this step.
* Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press the Vol up and power to boot to recovery . Since we want to boot into stock recovery, continue pressing the volume up button until you see the stock recovery screen.
* Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
* This time, we can finally boot to the system with Magisk. Select Reboot system now, and immediately press the combo key to recovery. After seeing the bootloader warning screen, release all buttons so it can boot to the system.
* The device will automatically reboot for the first time it boots. This is completely normal and done by design.
* After the device is booted up, do the usual initial setup. The following steps will need an internet connection.
* You shall see Magisk Manager in your app drawer; if not, manually install the APK you downloaded in step 3 and continue to the next step. The app would be a stub and it shall automatically upgrade to the full Magisk Manager when you open it.
* Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
Voila! Enjoy Magisk
Additional Info
* Magisk actually patches 3 partitions on your device:
vbmeta: replace with empty vbmeta image to disable partition verification
boot: remove the signature of the image to prevent soft bricks
recovery: this is where Magisk is actually installed
* Never, ever try to restore either of the 3 images mentioned back to stock! You can easily brick your device by doing so, and the only way out is to do full Odin restore following with factory reset. Just don’t do it.
* If you want to upgrade your device, never flash the stock AP tar file with the reasons mentioned above. Always pre-patch the firmware before flashing in Odin.
* If you don’t need to patch the full firmware, you can manually create a tar file with at least vbmeta.img, boot.img, and recovery.img to let Magisk Manager patch your images in the proper way.
Due to the fact that some devices no longer uses ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. For these devices, you will have to boot to recovery every time if you want Magisk. Since both Magisk and recovery lives in the same partition, what you actually end up getting when you choose to boot to recovery will be determined by how long you press volume up.
1. Powering up normally → System without Magisk
2. Power + Volume Up → Bootloader warning → Release all buttons → System with Magisk
3. Power + Volume Up → Bootloader warning → Keep holding volume up → Actual recovery
I would recommend Smalipatcher module to reboot directly into magisk system.
Updates: For each and every updates, either magisk or system update always patch the firmware with magisk and flash using odin(data will not be wiped if HOME_CSC
used instead of CSC)
RMM state Prenormal solution
Flash stock firmware
Boot up WITH sim inserted, CONNECT to internet during setup (or you can connect after setting up, but perform below operations only when connected to internet).
Enable developer options and go to them.
Now connect to internet and go to dev options, now set date 8 days back and check dev options for OEM unlocking
if it's still not there set date to today and again 8 days back and again check.
This worked for me and OEM unlocking was there and RMM state was changed to checking.
(what we are doing is fooling phone to believe that sim was inserted for more than 7 days)
Stock and combination firmware and Kernal source
Below are Gdrive links for Combination firmware for (M307FXXU1ASH9) and (M307FXXU2ASK2) and ROM M307FXXU1ASHI, M307FXXU2ASL2, M307FXXS2ATB3 (FOR INS ONLY, for other regions, use frija or samfirm).
I have also uploaded Kernal source for M307FXXU2ASL2 on gdrive for faster download.
Tools included
The following tools are also included in the shared folder, they are up to date as of FEB 2020, but i have attached links to original threads of xda to give credits and in case they are updated, you can download them from there. (As i said, this is AIO thread to find tools, none of them are my creation)
Frija, Samfirm continued and Samfirm are Tools for downloading Official firmware from samsung servers with high speed (so no to sammobile and other ****ty premium websites)
Frija thanks to @invmini, Github
SamFirm thanks to @zxz0O0, Github
SamFirm_continued, Github
Odin
Patched Odin by @realbbb
Frija not working ? install both vcredist_x00 for your device !
(check your windows settings to know which version to install)
(Microsoft Visual C++ 2010 Redistributable Package) and (Microsoft Visual C++ 2008 Redistributable Package)
https://www.microsoft.com/en-US/download/details.aspx?id=29 (x86) 2008
https://www.microsoft.com/en-US/download/details.aspx?id=5555 (x86) 2010
https://www.microsoft.com/en-US/download/details.aspx?id=15336 (64bit) 2008
https://www.microsoft.com/en-US/download/details.aspx?id=14632 (64bit) 2010
-Open Frija and type in your model (mine is SM-m307f) and your CSC : (mine is INS).
(All models on samfrew: https://samfrew.com/model/SM-M307F/).
Thanks to @BK
Other Tools
PIT Magic v1.3.10 - Samsung PIT Creator, Editor, Analyzer
Samsung firmware naming convention and explanation (Outdated)
SM-M307F - Galaxy M30s Samfrew
Extract Samsung PIT File from Samsung Firmware -> www.droid views.com/extract-samsung-pit-file-from-firmware (remove space b/w "droid" and "views")
NAND Erase Samsung Devices in Odin -> www.droid views.com/nand-erase-odin-samsung-firmware (remove space b/w "droid" and "views")
Latest Odin Downloader: https://odindownloader.com/category/download
Samsung USB Driver: https://samsungusbdriver.com/category/download
Samsung Firmware: https://firmwarefile.com/category/samsung
Links​LINK (Pm me if link is dead. If there is error like "try after some time", make a copy of file to your drive and then download)

Hide bootloader unlocked warning message
See Here
DeGoogle & debloat M30s and install MicroG
Here
Enable Haptic feedback on m30s (or any other samsung phone) (thanks to ak****)
1- download "Settings database Editor" from playstore.
2- scroll to bottom and find "haptic_feedback_enabled" and change it to 1

Just in case

great, im planning to buy this device and sell my a70, wouldn't have though a little bit of my thread would have been used there also combination files cannot be flashed anymore until a fix is found (nope Z3X Samsung tool don't work )

BK said:
great, im planning to buy this device and sell my a70, wouldn't have though a little bit of my thread would have been used there also combination files cannot be flashed anymore until a fix is found (nope Z3X Samsung tool don't work )
Click to expand...
Click to collapse
Are you talking about the frija and samfirm part?
I think i took it from some other thread which i cant find now. (maybe s10 or note10 ones)
Edit: Gave credits to you

How to flash Combination firmware?
I am trying to flash combination firmware [COMBINATION_FAC_FA90_M307FXXU1ASH9_FAC_CL16672589_QB25543275_REV00] with Odin v3.13.3B Patched but it doesn't work, giving this error on the phone
"Please get the approval to use factory binaries (PIT)"
Anyone know any way to make it work? It would be really nice to be able to downgrade to U1 binaries.

nobody_nowhere said:
I am trying to flash combination firmware [COMBINATION_FAC_FA90_M307FXXU1ASH9_FAC_CL16672589_QB25543275_REV00] with Odin v3.13.3B Patched but it doesn't work, giving this error on the phone
"Please get the approval to use factory binaries (PIT)"
Anyone know any way to make it work? It would be really nice to be able to downgrade to U1 binaries.
Click to expand...
Click to collapse
it's currently impossible to install a test/debugging firmware without a samsung dev account that work as an authorization to flash combination files.

Sm-m307f/ds
Hi i got OTG update and my phone didnt restart after that, i have been trying to find the right Stock firmware for my Samsung M30S SM-m307F/DS but i couldnt find the right one, can you please help me out with the link of the right firmware for my phone.
Thanks

Watch this video broo...you will get to know how to download all latest updated frimware

Managed to root but cannot update

Hi!
Xperia ZXP was running the official Firmware fine. Then, I just decided to root. I followed this video:
Got my phone properly rooted.
Now I keep getting notification of an update that I had before but cannot install it. Also, I cannot setup my company work profile as it detects root.
I mainly wanted to use Cheat Engine that why I rooted.
How do I apply latest update?
How do I hide root status?

Download Flashtool and latest version of Xperifirm. Find latest firmware with Xperifirm. Should end in .107. Download it and decrypt it with Flashtool. Download Newflasher. Unzip Newflasher into the folder you have the decrypted files. Plug your phone into your computer. Make sure you have the correct driver. Developer option and usb debugging enabled on your phone. Put phone into flash mode and hit newflasher.exe and choose "n" for the first two choices and let it run. That will give you the latest and final update for this phone.
Now use twrp to install the latest Magisk version(search online), also have Magisk manager app(Play Store) on your phone. Once that's done and you've rebooted phone open Magisk Manager and select the menu in upper left corner and go to Magisk Hide and if there's the option to hide whatever app that is detecting root and causing problems, select it and it should no longer detect root. If the problem app is not shown then I don't know. I believe there is a Magisk Module that may be less app specific and hide Magisk from everything.

bobsright said:
Download Flashtool and latest version of Xperifirm. Find latest firmware with Xperifirm. Should end in .107. Download it and decrypt it with Flashtool. Download Newflasher. Unzip Newflasher into the folder you have the decrypted files. Plug your phone into your computer. Make sure you have the correct driver. Developer option and usb debugging enabled on your phone. Put phone into flash mode and hit newflasher.exe and choose "n" for the first two choices and let it run. That will give you the latest and final update for this phone.
Now use twrp to install the latest Magisk version(search online), also have Magisk manager app(Play Store) on your phone. Once that's done and you've rebooted phone open Magisk Manager and select the menu in upper left corner and go to Magisk Hide and if there's the option to hide whatever app that is detecting root and causing problems, select it and it should no longer detect root. If the problem app is not shown then I don't know. I believe there is a Magisk Module that may be less app specific and hide Magisk from everything.
Click to expand...
Click to collapse
Is there a place/page here that lists all these tools?

Fix after root effects
bobsright said:
Download Flashtool and latest version of Xperifirm. Find latest firmware with Xperifirm. Should end in .107. Download it and decrypt it with Flashtool. Download Newflasher. Unzip Newflasher into the folder you have the decrypted files. Plug your phone into your computer. Make sure you have the correct driver. Developer option and usb debugging enabled on your phone. Put phone into flash mode and hit newflasher.exe and choose "n" for the first two choices and let it run. That will give you the latest and final update for this phone.
Now use twrp to install the latest Magisk version(search online), also have Magisk manager app(Play Store) on your phone. Once that's done and you've rebooted phone open Magisk Manager and select the menu in upper left corner and go to Magisk Hide and if there's the option to hide whatever app that is detecting root and causing problems, select it and it should no longer detect root. If the problem app is not shown then I don't know. I believe there is a Magisk Module that may be less app specific and hide Magisk from everything.
Click to expand...
Click to collapse
Here is how I'm going step by step:
Download Flashtool - Done
latest version of Xperifirm - Done
Find latest firmware with Xperifirm. Should end in .107 - Done
-- Download it - Done
-- decrypt it with Flashtool - Stuck
Download Newflasher - Done
-- Unzip Newflasher into the folder you have the decrypted files
Plug your phone into your computer
-- Make sure you have the correct driver - Done
-- Developer option and usb debugging enabled on your phone - Done
Put phone into flash mode and hit newflasher.exe
-- choose "n" for the first two choices and let it run
-- That will give you the latest and final update for this phone
I'm stuck at the decryption part... I downloaded the correct firmware for my phone and it is quite a load of files. But, the decrypt tool in Flashtool finds nothing to decrypt

Doomer D. Great said:
Here is how I'm going step by step:
• Download Flashtool - Done
• latest version of Xperifirm - Done
• Find latest firmware with Xperifirm. Should end in .107 - Done
○ Download it - Done
○ decrypt it with Flashtool - Stuck
• Download Newflasher - Done
○ Unzip Newflasher into the folder you have the decrypted files
• Plug your phone into your computer
○ Make sure you have the correct driver - Done
○ Developer option and usb debugging enabled on your phone - Done
• Put phone into flash mode and hit newflasher.exe
○ choose "n" for the first two choices and let it run
○ That will give you the latest and final update for this phone.
• Now use twrp to install the latest Magisk version(search online)
○ also have Magisk manager app(Play Store) on your phone
• Once that's done and you've rebooted phone
• open Magisk Manager and select the menu in upper left corner and go to Magisk Hide and if there's the option to hide whatever app that is detecting root and causing problems, select it and it should no longer detect root.
• If the problem app is not shown then I don't know. I believe there is a Magisk Module that may be less app specific and hide Magisk from everything.
I'm stuck at the decryption part... I downloaded the correct firmware for my phone and it is quite a load of files. But, the decrypt tool in Flashtool finds nothing to decrypt
Click to expand...
Click to collapse
You have to select the location. Click on Tools, then Bundles, then FILEset Decrypt. On the line where it says source folder there's a small box on the end. Click it and from there go to your harddrive, users(you), flashtool, firmware, downloads and there you will find the firmware that you just downloaded. Click on it and that should unpack the firmware. Then select all the files to convert. That will place the converted files in the same location as the firmware. Don't bother with removing the .ta files. Do create the partition folder. See link below.
http://www.xperiablog.net/2018/01/2...mware-for-xperia-xz-premium-xz1-and-more/amp/
The above link will take you through all the above steps. You will lose user data. You can remove the USERDATA X Flash ALL and that should save your data but no guarantees.

bobsright said:
You have to select the location. Click on Tools, then Bundles, then FILEset Decrypt. On the line where it says source folder there's a small box on the end. Click it and from there go to your harddrive, users(you), flashtool, firmware, downloads and there you will find the firmware that you just downloaded. Click on it and that should unpack the firmware. Then select all the files to convert. That will place the converted files in the same location as the firmware. Don't bother with removing the .ta files. Do create the partition folder. See link below.
http://www.xperiablog.net/2018/01/2...mware-for-xperia-xz-premium-xz1-and-more/amp/
The above link will take you through all the above steps. You will lose user data. You can remove the USERDATA X Flash ALL and that should save your data but no guarantees.
Click to expand...
Click to collapse
The latets Xperifirm also extract right after downloading so the decrypt step is not needed.
I'm flashing a I write. I'll be dealing with the next part now:
Now use twrp to install the latest Magisk version(search online)
also have Magisk manager app(Play Store) on your phone
Once that's done and you've rebooted phone
open Magisk Manager and select the menu in upper left corner and go to Magisk Hide and if there's the option to hide whatever app that is detecting root and causing problems, select it and it should no longer detect root.
If the problem app is not shown then I don't know. I believe there is a Magisk Module that may be less app specific and hide Magisk from everything
TWRP has to be flashed or installed from store?

Was going to attach the file but had upload issues. What you want is twrp 3.3.1-0-maple.img. Once you have that put phone in fastboot mode ( volume up while plugging phone into computer) then go to the place you downloaded the above ( unzip it to a folder that also contains adb and fastboot unless you have that installed system wide). Open a powershell or cmd window inside that folder and type: fastboot boot twrp-3.3.1-0-maple.img. that'll open twrp on your phone in recovery. Then you can flash Magisk and that'll root your phone. I'm typing this from memory. I believe I have that right. If you want to install twrp on the phone itself umm, I believe you flash the .IMG file to recovery partition. You'll need to have both those files in your phone. Let me know if I got that right. If it doesn't work, no worries, just start over. These phones are hard to brick; believe me, I know.

bobsright said:
Was going to attach the file but had upload issues. What you want is twrp 3.3.1-0-maple.img. Once you have that put phone in fastboot mode ( volume up while plugging phone into computer) then go to the place you downloaded the above ( unzip it to a folder that also contains adb and fastboot unless you have that installed system wide). Open a powershell or cmd window inside that folder and type: fastboot boot twrp-3.3.1-0-maple.img. that'll open twrp on your phone in recovery. Then you can flash Magisk and that'll root your phone. I'm typing this from memory. I believe I have that right. If you want to install twrp on the phone itself umm, I believe you flash the .IMG file to recovery partition. You'll need to have both those files in your phone. Let me know if I got that right. If it doesn't work, no worries, just start over. These phones are hard to brick; believe me, I know.
Click to expand...
Click to collapse
I have downloaded the TWRP image and I have the android platform tools as well. Right now, my mobile is working with the latest ROM from Xperifirm and I'm not sure about root status. It was rooted before I did the firmware update. It is latest now and no app is complaining.
Current status:
- OEM Booltloader unlocked
- USB Debugging ON
Question:
- I need to know will if I'll lose all data on the phone?
- If I use the fastboot boot twrp-3.3.1-0-maple.img command, phone wil have TWRP as recovery and will be in this recovery mode? I need to copy Magisk (apk?) already on the phones hardrive so I can install from there?

Doomer D. Great said:
I have downloaded the TWRP image and I have the android platform tools as well. Right now, my mobile is working with the latest ROM from Xperifirm and I'm not sure about root status. It was rooted before I did the firmware update. It is latest now and no app is complaining.
Current status:
- OEM Booltloader unlocked
- USB Debugging ON
Question:
- I need to know will if I'll lose all data on the phone?
- If I use the fastboot boot twrp-3.3.1-0-maple.img command, phone wil have TWRP as recovery and will be in this recovery mode? I need to copy Magisk (apk?) already on the phones hardrive so I can install from there?
Click to expand...
Click to collapse
If you didn't lose data in upgrading the firmware you won't lose it installing Magisk. Using TWRP from your computer does not install it. It only puts you into recovery using TWRP as the menu. If you want to have it installed you need to flash the .img file to the recovery partition while in TWRP. All this does is eliminate the need to use a computer every time you want to use TWRP.
You more than likely lost root when flashing the new firmware. So Magisk apk is the manager app. You also need to have Magisk 20.4 as a zip file in your phone. When in TWRP select mount and make sure the location where the zip is is selected. Then go back and select install and then go to the location of the zip, select it and slide the slider and it will install. Go back to main menu and power off. People like to wipe and reboot, I find not wiping if you don't have to works for me along with powering off and then restarting the phone.

bobsright said:
If you didn't lose data in upgrading the firmware you won't lose it installing Magisk. Using TWRP from your computer does not install it. It only puts you into recovery using TWRP as the menu. If you want to have it installed you need to flash the .img file to the recovery partition while in TWRP. All this does is eliminate the need to use a computer every time you want to use TWRP.
You more than likely lost root when flashing the new firmware. So Magisk apk is the manager app. You also need to have Magisk 20.4 as a zip file in your phone. When in TWRP select mount and make sure the location where the zip is is selected. Then go back and select install and then go to the location of the zip, select it and slide the slider and it will install. Go back to main menu and power off. People like to wipe and reboot, I find not wiping if you don't have to works for me along with powering off and then restarting the phone.
Click to expand...
Click to collapse
Mission accomplished.
I did all this so that I can use Cheat engine to chat in some silly games plus a few simple ones I made with Unity. Turns out, Cheat Engine fails to show running apps to select from... what a trip...

Doomer D. Great said:
Mission accomplished.
I did all this so that I can use Cheat engine to chat in some silly games plus a few simple ones I made with Unity. Turns out, Cheat Engine fails to show running apps to select from... what a trip...
Click to expand...
Click to collapse
So Cheat Engine doesn't detect root with Magisk?

bobsright said:
So Cheat Engine doesn't detect root with Magisk?
Click to expand...
Click to collapse
Everything works perfectly. All apps working with root and Magisk is hiding root from required apps. Cheat Engine is working with Root. After that, the issue is with Cheat Engine. It is not working as expected. I see an emty Apps list and cannot fing the game I want to cheat in even when it is running. This is off topic as the thread is now complete. Just saying I didi all this for a dissapinting app.

Doomer D. Great said:
Everything works perfectly. All apps working with root and Magisk is hiding root from required apps. Cheat Engine is working with Root. After that, the issue is with Cheat Engine. It is not working as expected. I see an emty Apps list and cannot fing the game I want to cheat in even when it is running. This is off topic as the thread is now complete. Just saying I didi all this for a dissapinting app.
Click to expand...
Click to collapse
Oh well, at least you got it updated and working. Maybe it'll take some searching somewhere else to get that other stuff worked out.
Just a side note; I used to work for Sheikh Hamdan bin Rashid Al Maktoum at his Throughbred operation in Lexington.

Excuse me, does anyone know how to root xz premium docomo ubl no ??? Now on Android 9 Pie, please help.

I believe the Japan market version can't have the bootloader unlocked, thus, no root.