Database Users

How to root my SM-A500M Android 6.0.1?

Hi!
I've just updated my android from 5.0.2 to 6.0.1 using a firmware from sammobile and lost the root I had previously (super user).
I tried installing from cf-root using the version they already have for 5.0.2 and at first it seemed to have worked, since it started to show my phone device's status as custom, and also to show kernel's status at the black start screen with the logo samsung.
Then, I tried changing an app into a system file using Link2SD and the app vanished instead of working again. When I get to install the .apk again, it shows as an update (of something that is not running anywhere) and don't ask any new permission.
I guess the problem is because of the root I used, but I'm not sure. My mobile is dual sim (brazil's trend...) and the app I'm trying to hide is Cerberus (I have the pro version, disguised, but want to make it "blended" as it was before the Android update).
I did the unroot with the SU app, but my device is still showing as a "custom" one at the system's about (the kernel's status is not appearing at initialization tho).
I want to know what to do to fix that and how to properly root the new android marshmallow. If not possible, I even consider downgrading my phone to the previous android until the root is available (security from thieves first, unfortunately!).

Same Here
Doen anyone know if there is other variant rom we can use in a500M

Wait for CF-AutoRoot
Some A5 variants have received the root file for Android 6.0.1 Marshmallow
CF-AutoRoot: https : // autoroot.chainfire. eu/

nicolaycarlos said:
Same Here
Doen anyone know if there is other variant rom we can use in a500M
Click to expand...
Click to collapse
I use the 5.0.2 root version in marshmallow and it's working fine for me with xposed and everything else

ToDream said:
Some A5 variants have received the root file for Android 6.0.1 Marshmallow
CF-AutoRoot: https : // autoroot.chainfire. eu/
Click to expand...
Click to collapse
Not the A500M, yet.

Option 1: Flash CTR o TWRP with Odin. Then, flash SuperSU.zip from recovery.
Option 2: Flash CF-AutoRoot (Lollipop version) with Odin.
PS: If you want more options antitheft, you can use Xposed and GravityBox or Advanced Power Menu modules to disable the Power-Off menu when the screen is locked.
Good Luck

So I can use your "Option 1" to root my device with 6.0.1 even if it's a 5.0.2 method? (I just want to make sure to not brick my phone).

Incomplete root on Meizu Pro 5

Hi everyone,
I have some weird root on my Meizu Pro 5 with 5.1.6.0 G. Root permissions are ON in the Settings/Fingerprint and Security/Root Permission/ . I have a list of apps with Allow permission, including SuperSU, BusyBox, Root Explorer and Terminal Emulator. When I launch any of these apps for the first time I get a prompt for permission and I choose Allow.
However, Root checker does not recognize the root and Kingroot failed to root the device. When I boot device into fastboot to unlock the bootloader to install TWRP, I see “Fastboot [locked, rooted]” message. Whenever I try to use “su” command in the Terminal it returns access denied or something similar. SuperSU app fails to update the binary, although, ES Explorer has root access to explore files.
I tried to Reset to factory settings - same issue
Tried to Factory reset + Format internal storage and test root on clean device without even restoring from a backup - same issue
Tried to flash update.zip from File Explorer and from Recovery itself - firmware corrupt and does nothing.
Not sure when and what went wrong. I updated to 5.1.6.0G via terminal commands, hence I had su access with no problems.
Do you have any ideas? Now I just want to revert to the original state of the device and repeat the rooting from scratch, but unable to do so since any firmware I tried was "corrupt" and terminal does not let to use commands.
P.S. After "Factory reset + Format internal storage" in the very first boot of the device I noticed that Root access was already ON, even though I skipped the Flyme account login step. The phone is working fine - no bootloops, not bricked. Even Xposed is installed and working fine. The only issue is with the root, which appears to be incomplete.

Something similar happened to me.
Just update Flyme and check clear data. Then root it again.

Found the problem: if you are unrooted on the bootloader (check with [power] + [vol-])
And rooted within flymeos, you experience this problem.

I've got the same issue but I'm unable to instal another version of flymeOS (got corrupted firmware).
Does someone know how to fix ?

Atarhorn said:
I've got the same issue but I'm unable to instal another version of flymeOS (got corrupted firmware).
Does someone know how to fix ?
Click to expand...
Click to collapse
I might be able to help you, do you have a locked bootloader ?

kingroot 4.9.6 problems

I rooted with newest kingroot i currently don't have access to a computer atm, it displays ads on lockscreen and lags ive tried everything to replace w supersu it doesnt delete it ive noticed the script tries to delete "com.kinguser" stuff i also noticed they changed the kingroot apk to "cafeuser.apk" inside a folder called cafeuser i dont want to just delete it because like i said i dont have access to computer i want to know if anyone knows a successful way to uninstall this new kingroot 4.9.6 and keep root status and perhaps use superuser or supersu without computer access safely thank you for your time
Be advised im using a metropcs LG K7
LG MS330 running 5.1.1

may help
When asking for help you need to provide additional information such as device info:
sdk
manufacturer
model
However I faced the same problem too!
If I understood you correctly...so first thing first.
1. install superSU first & use root to install it as a system app any root apps can do that)
2. before rebooting the phone....please install busybox utilities from an app called "Busybox" on google play
3. reboot the device
4. once successfully rebooted open SuperSU & grant it root from kingroot & try to get it to install its binary.
- if it cant, disable kingroot after you know superSU was granted root & then try again.
-if it doesnt work again...then uninstall kingroot & relaunch SuperSU & try to let it install its binary again.

I have the lgms330 with the same kingroot version, did yours also automatically convert it to a system applies? I've never seen it do that on my other phones. Also my PlayStore stopped working when the update showed up there. Lol only good thing is Google also stopped telling me it would hurt the system. I have the newest version downloaded but I'm terrified to install it until I get some opinions cuz I currently don't have a monitor for my computer in case I brick it.

How to download kingroot

Does unlocking bootloader means rooting device?

I'm using zuk z1,android 5.1.1,a normal device as it is from manufacturer.I want to root my device. As I am newbie I got a doubt, does unlocking bootloader means rooting device? After I unlocked my bootloader with help of my computer,can I directly install TWRP manager app from play store and flash TWRP recovery with that app?l don't want to flash it by PC as I don't know much about it. Can I flash supersu with smartphone itself.

No. Until you don't install KingoRoot Or SuperSU. Your phone is not permanently rooted. Rooting is the Android equivalent of jailbreaking, a means of unlocking the operating system so you can install unapproved apps, deleted unwanted bloatware, update the OS, replace the firmware, overclock (or underclock) the processor, customize anything and so on.

Anurag11 said:
I'm using zuk z1,android 5.1.1,a normal device as it is from manufacturer.I want to root my device. As I am newbie I got a doubt, does unlocking bootloader means rooting device? After I unlocked my bootloader with help of my computer,can I directly install TWRP manager app from play store and flash TWRP recovery with that app?l don't want to flash it by PC as I don't know much about it. Can I flash supersu with smartphone itself.
Click to expand...
Click to collapse
Well, I believe that using the manager won't make any difference with flashing it using a PC. And once you have flashed the recovery, reboot into it and in my case, when I was trying to reboot to system from TWRP it popped a message and told me that your phone is not rooted- Do you want to root and install SuperSU? And that's how I rooted mine. However after booting into the system you might want to update the SuperSU and the binary to the latest version!
Try it! Hope it'll solve the issue. Feel free to ask any doubts! Because that's what we do here at XDA!

[T-Mobile D6616] Updated Root Method Request

Good afternoon,
After MUCH research, I have arrived at the conclusion rooting the D6616 with T-Mobile's likely final Z3 build for 5.0.2 (Build 23.1.C.0.399 and, really anything past KK) is no longer possible without involving Kingroot.
Why does this matter? Because there may not be a feasible way to remove the most recent builds of Kingroot from the D6616 ROM. Using Kingroot's own uninstaller in the App settings fails and factory resetting using the ROM/stock recovery threw my phone into a bootloop. Other users report it successfully factory reset their ROM with kingroot installed as a system app and their device no longer rooted. I attribute the variety of outcomes to different software builds and Kingroot versions.
It seems as though the only working root method also uses ZXDualRecovery. Though I have not tried it, all procedures that show the ZXDualRecovery method of pushing recovery and superSU involved rooting the device with Kingroot first and removing it after SuperSU is installed. This appears to be the only still-working method of acquiring temporary root long enough to install recovery. The only way to remove Kingroot is to use flashtool and a new Sony TFT, which also removes root and recovery.
Has anyone successfully been able to pull off rooting a D6616 lately? I want to keep this phone but it is unfortunately useless to me without working root so I'll likely be returning it if nobody still has one that's running the last software with a locked bootloader.
I would really appreciate any help anyone can give.

I believe I have done it! I think SuperSU is ever so slightly ahead of Kingroot.
What I did:
1) Rooted via Kingroot app on Google Play. Run rootchecker after it's done its business to make sure. DO NOTHING ELSE IN THE APP. Doing so may prevent SuperSU from kicking its ass later.
2) Downloaded and upacked to desktop the file for Xperia Z3 from here:
http://nut.xperia-files.com/path/XZD...ecovery_2.8.26
Z3-lockeddualrecovery2.8.26.-RELEASE.combined.zip
3) Disabled antivirus
4) Installed USB drivers via Windows 7 plug-n-play. Unplug phone.
5) Downloaded SuperSU recovery flashable zip from here:
http://www.supersu.com/download#zip
6) Ran install.bat from extracted ZXDualRecovery zip
7) Enabled developer options in phone, enabled USB debugging, revoked USB devices, rebooted phone, plug in phone.
8) Connect Phone, wait for device to register in windows.
9) Okayed communication from PC.
10) Place in USB Install Mode on phone.
11) Choose option 2 to install to device rooted by SuperUser. Kingroot has blocked option 1 (old method)
12) Enter TWRP (Automatic) and go to Backup, check all boxes, create Nandroid by sliding the slider
13) Reboot, ensure phone boots. Put SuperSU.zip on the external flash drive. Go to your new App: NDR Utils. Choose TWRP as Primary Recovery. Choose Reboot to Primary recovery
14) Flash zip for SuperSU. DO NOTHING ELSE. Do not wipe cache, do not fix permissions. Click REBOOT.
15) Launch SuperSU App. Attempt to update Binaries. It will not, but it will detect Kingroot, and somehow can get rid of it itself using onboard capabilities. It will do so and update binaries.
16) Reboot (Automatic via SuperSU)
17) Check to make sure SuperSU binaries installed by launching the app.
18) Reboot to recovery using the steps from step 13) above.
19) Create another backup using step 12) above
20) Reboot and DONE.
To the best of my knowledge, nobody has indicated how to do this in a clear Step-By-Step for the final build of this ROM. So because I've troubled you all for small chunks of the process I figured I would.
This applies to T-Mobile's likely-final software release for the Xperia Z3 android 5.0.2 on build 23.1.C.0.399.
DISCLAIMER TO ANYONE ATTEMPTING THIS: It appears Kingroot is "onto" what it is being used for. Given the behavior of this application, there is no reason for anyone to believe it is not a malicious program, but it is a necessary evil for this purpose. Newer versions of SuperSU are capable of removing Kingroot on their own, but alternative methods may be necessary. I attempted an earlier version of SuperSU and it was incapable of removing Kingroot.
It might remove via debloater. This is the only way to remove the system apps on this phone reliably, so you WILL need it if you intend to keep the bootloader locked. I couldn't get any root-enabled appstore app to do it including ES File explorer and Titanium Backup. It looks like you need a computer to remove system apps on this phone. Fantastic. Debloater works great though so don't be afraid to use it. Use the filter to search for Apps. You can remove them, but they will not be gone until you reboot your device. Hooray no more filecommander and lookout! Debloater can be found here:
https://forum.xda-developers.com/and...bloat-t2998294
Plug in your phone. Give it root access. Easy peezy.
Then Xposed current framework and installer:
https://forum.xda-developers.com/sho....php?t=3034811
Version 3.1.1 fixed the bootloop problem, so you shouldn't need the fix zip, or at least I didn't. But if you do, you can find it here:
https://dottech.org/187028/how-to-fi...-z5-z4-z3-tip/
Flash the framework for your device in recovery (arm) and then the installer APK from the ROM using a file browser.
FINALLY Youtube Adblock and minimized playback. SCORE!
I think that's about it. That's literally the best we can currently hope for from this device. I think there is an Xposed module to heavily alter the look of the ROM here but I have not tried it. Plus it only claims to work w/ 4.4, and we have 5.0.1.
https://forum.xda-developers.com/z3/...6#post71601966
For devicewide adblocking I use DNS66 since there are no proxy settings for adblocking on this device, unless I'm missing something. I really hope I am. This means there's no native adblocking.
Xposed modules worth using you can find by searching in the Xposed store: Blurred System UI (LP), Gravity Box [LP], RootCloak, Xperia/AOSP NavBar Buttons, Xperia Super Radio, YouTube AdAway, YouTube Background Playback. And of course DNS66 (PlayStore).
I have tinkered with the rest and find them of no value.

I followed the steps but SU didn't ask to update anything. It just opens up and everything is fine?
Then all I did was unistall kingroot(purify) and it looks like it's gone, but is it?

Just leaving this here, this is how I rooted on Android 5.0.2 with the D6616
http://nut.xperia-files.com/
Read the documentation that comes with the latest XZDualRecovery and flash SuperSU or whatever you want.

stef-nix said:
Just leaving this here, this is how I rooted on Android 5.0.2 with the D6616
http://nut.xperia-files.com/
Read the documentation that comes with the latest XZDualRecovery and flash SuperSU or whatever you want.
Click to expand...
Click to collapse
Were you able to install twrp without rooting first on your PC? It doesn't work for me. I did option 3, install on unrooted device.
Are you able to systemless root?

When I run the installation it fails at step 3 on the install bat.

Hi, a bit of an old thread, but has anyone had any success rooting the D6616 without using Kingoroot or Kingroot? Both are malware which are designed to not be fully removed and be as resilient as possible, and uninstall does not actually uninstall them...

Yes, the old method still works. Use the search feature. I'd just link you, but I"m busy at the moment.

i followed these steps, and have gotten to the point where you flash supersu and reboot, but i'm stuck in a reboot loop now. wanted to use this old z3 as a dedicated audio player, and needed to root for some audio enhancements...
edit: i did have TWRP for a minute, but now when i go into recovery it's the stock recovery again, with options only to continue booting, boot to safe mode, factory recovery or power down. the first two options return to a boot loop. can/should i attempt to use flashtool, or factory recovery? i don't want to accidentally wipe something i might need in the backup.\
UPDATE 10/19: I was able to get back to ground zero using Sony's xperia companion software repair. Flashtool 9.25 and 9.26 would never successfully install flashmode drivers, nor would it display the stock .ftf file.

fierogt42 said:
Yes, the old method still works. Use the search feature. I'd just link you, but I"m busy at the moment.
Click to expand...
Click to collapse
this new method seems to fail for me on both of my old z3's. does the method you're referring to involve downgrading to 4.4.4? i've done some extensive searching of this forum (and the android development ones as well) but don't seem to be able to find any other info.