Develop Bugs

[HELP] Cyanogenmod 12 Root Access

After months of sitting on the stock rooted rom I finally decided to install CM12 [Official] this morning.
everything is working fine but I have one issue. I've lost my root during install and can't seem to get it back.
So far I've installed SuperSU from the play store and the only thing that happens after telling me that the su binaries need to be updated is me getting the failed message when i hit update. I've also tried the secondary option of installing through TWRP but once you click that it does absolutely nothing.
Obviously there's something that i'm missing or doing wrong. does anybody have any input

Under development you have to enable Root for it to work
Sent from my LG-D851 using Tapatalk

That's the thing.... It is enabled under development.
I've restarted my phone numerous times and even did another fresh install enabled it again and the only difference this time around is that root checker is saying i have root now but supersu still wont update the binaries.

Root is now built into Privacy Guard for CM Roms, so if you need to manage anything you have to go to Privacy Guard in the settings. (In other words supersu is no longer needed)

I dont know if you should do this, but i did....
I launched odin and "re-rooted" my phone and it worked.
I already had Cyanogenmod 12 installed. I just put it in download mode and installed supersu through odin and its worked so far

SuperSU and Xposed are built in to Cyanogenmod 12. There is no need for either. Enable root access under Developer Options from the settings.
Sent from my LG-D851 using XDA Free mobile app

Found a working root for 4.6.1

Greetings!
I was successfully able to root my US unlocked Fire Phone (on 4.6.1) by installing and running KingRoot 4.0!
KingRoot appears to work on other 4th gen Amazon devices as well!
http://forum.xda-developers.com/kindle-fire-hdx/general/to-root-4th-gen-amazon-device-t3104853
One caveat:
KingRoot installs KingUser as its superuser app, and KingUser appears to prevent the su binary from being overwritten.
Because of this, I have not yet been able to replace KingUser with SuperSU or similar.
Hopefully someone more knowledgeable can resolve this, but until then
I've opted to install the Xposed Framework and LightningWall module in order to block KingUser's network activity.
najoor has found a way to replace KingUser via adb:
najoor said:
Instructions for replacing Kinguser with SuperSU are posted in the general forum:
http://forum.xda-developers.com/fire-phone/general/root-fire-phone-supersu-t3105546
Click to expand...
Click to collapse
Also, hydromän pointed out that HDXPosed is working to enable widgets and block potential updates. Awesome!
hydromän said:
How to Block now Amazon Updates?
Fixed. Using xposed with hdxmodules. Now working all Launchers with Widgets and Updates Are disabled
http://forum.xda-developers.com/showthread.php?t=2618158
Click to expand...
Click to collapse

Granted! Root working!

z64 said:
Greetings!
I was successfully able to root my US unlocked Fire Phone (on 4.6.1) by installing and running KingRoot 4.0!
Everything seems to be working, however, I am not sure how safe KingRoot is actually.
KingRoot installs KingUser as its superuser app, and KingUser appears to prevent the su binary from being overwritten.
Because of this, I have not yet been able to replace KingUser with SuperSU or similar.
Maybe someone more experienced than myself could take a look at it.
Other than that, seems great.
Hope this bit of news helps!
Click to expand...
Click to collapse
Thanks z64 for the information about a working root for 4.6.1 (US Unlocked GSM) Fire Phone.
I would like to know if KingRoot 4.0 is really safe to use, and if will make a FULL or a PARTIAL root to the Amazon Fire Phone?
I also would like to know if after rooting, you will be able to go backward and UnRoot later the Fire Phone, to the default and normal original state?

z64 said:
Greetings!
I was successfully able to root my US unlocked Fire Phone (on 4.6.1) by installing and running KingRoot 4.0!
Everything seems to be working, however, I am not sure how safe KingRoot is actually.
KingRoot installs KingUser as its superuser app, and KingUser appears to prevent the su binary from being overwritten.
Because of this, I have not yet been able to replace KingUser with SuperSU or similar.
Maybe someone more experienced than myself could take a look at it.
Other than that, seems great.
Hope this bit of news helps!
Click to expand...
Click to collapse
Is KingRoot a PC based program or a APK file? I'm Google searching now, just wondering which you used.

http://androidxda.com/download-kingroot-application
Choose 4.0

does this survive a reboot? that would be great news =)

After rebooting root checker report" ROOT" but you are right superSU is not working actualy it got installed but the SU binary upgrade failed

Can I go backward and UnRoot later the FirePhone to Default/Normal Original State??
Please, can someone that has already Rooted their Fire-Phone, if after rooting would be able to go backward and UnRoot later the Fire Phone, to the default and normal original state?

ulises.rodriguez said:
Thanks z64 for the information about a working root for 4.6.1 (US Unlocked GSM) Fire Phone.
I would like to know if KingRoot 4.0 is really safe to use, and if will make a FULL or a PARTIAL root to the Amazon Fire Phone?
I also would like to know if after rooting, you will be able to go backward and UnRoot later the Fire Phone, to the default and normal original state?
Click to expand...
Click to collapse
I'm not sure what qualifies as a full or partial root; the bootloader is still locked, so no custom recovery or custom roms.
It is possible to unroot using the included KingUser app.
You have to uncheck "Backup Root permission" first to completely unroot it.
(Still haven't figured out how to replace KingUser with SuperSU while it's rooted.)
Viperise152 said:
Is KingRoot a PC based program or a APK file? I'm Google searching now, just wondering which you used.
Click to expand...
Click to collapse
I used the latest KingRoot 4 apk from kingroot.net/down
"KingRoot-4.0.0.233-release-201505071219_105001.apk"
drdoomgod said:
does this survive a reboot? that would be great news =)
Click to expand...
Click to collapse
It does survive reboot!
I just installed the Xposed Framework with LightningWall to control net access.

How to Block now Amazon Updates?
Fixed. Using xposed with hdxmodules. Now working all Launchers with Widgets and Updates Are disabled
http://forum.xda-developers.com/showthread.php?t=2618158

works !

Failed for me. Wouldn't install.
EDIT: Got it working!!
Sent from my SD4930UR using XDA Free mobile app

The question is what can we do with it now? Can we get rid of the lock screen and install a new settings apk??

TheDynamo said:
The question is what can we do with it now? Can we get rid of the lock screen and install a new settings apk??
Click to expand...
Click to collapse
Xposed framework is the first thing I did

Hi, i have the xposed framwork installed but not sure what to do with it lol

Instructions for replacing Kinguser with SuperSU are posted in the general forum:
http://forum.xda-developers.com/fire-phone/general/root-fire-phone-supersu-t3105546

Not sure why - but after following instruction (after rooting etc) tried to follow the guide for making phone look like normal android and thats when all hell broke loose on my phone. Unresponsive bottom button, wiget's not loading, super su showing nothing then refreshing a while later showing apps in there etc.
Kinda killed my phone so going to factory reset and start again.

This is great! I got the now launcher to work, although I'm not exactly sure how. I tried the supersu replacement and only made it to steps 6 and 7 mostly because I couldn't understand what exactly I was supposed to do, so step 8 didn't work and I'm still using the kingsu. I then d/l the now launcher and the google (search) apps, tried to run it a couple of times with no luck. Then force stopped the home app, restarted, and I was given the choice to use the now launcher.

Its easy. If u have root, convert Google Now Launcher and Google Search with Titanium Backup to a System App... And you can Choose Google Now Launcher.

This is great. I was able to fix my play store/services issues by changing my build.prop to nexus 5 after rooting. Awesome!

[Q] Fire Phone: SuperSU-me, Xposed Framework and other Issues

Hi,
I just got a fire phone and I'm facing multiple issues. It updated to 4.6.6.1 once i started it. Now I want it to act like a normal android phone so I installed google now launcher.
Next thing i wanted to do is to customize the laucher. So I did research how to root it. Did it with kingroot and afterwards followed various instructions to change to superSu. Non of them worked. Neither via adb nor SuperSU me nor the terminal version. only rooted when on kingsroot. SuperSU binaries also would never succesfuly update. Anyways.
So after I got the root, I wanted to install Xposed Framework to finally customize the launcher. Now xposed is saying, that it is not (yet) compatible wit the ANdorid SDK Version 19 or my Prozessor architecture. (armeabi-v7a)
I'm running the phone on german language. Don't know what to do anymore with both. SUpersu and Xposed. Appreciate any help.

So you already bought Super-Sume-Pro? Good, because removing / replacing Kingroot was possible even with the (early) free version of Super-Sume (9.1.6).
Download this old version* of Kinguser.
Yes, like always, it's classified as a virus / exploit / PUP, because it uses very aggressive methods of achieving root.
"But Bingo, this is only Kinguser, I need Kingroot."
No you don't. I used this combo many times, it always worked, from the latest version down to Fire OS 4.6.1 when I first tried it.
Uninstall your current version of Kingroot / Kinguser and remove the leftover folders from the internal storage.
Install the old version (disable auto update within in the app, it can be quite annoying), let it "achieve" root, disable WiFi if you want.
Run Super-Sume. It will have no problem replacing Kinguser with 2 steps.
Download this compatible version of the Xposed Installer.
Install framework, etc. You know the drill.
For BusyBox, I'd recommend either Stericson's version or Meefik's.
I tested one of my devices with 4.6.6.1 and the above mentioned customizations (mainly to enjoy microG on Fire OS ^^), so I can say it definitely works.
* Had to use OCH, because the "good guys" like Dropbox and Google Drive won't allow hosting / linking this file, since it's a bad azz virüs.

I always found W0lfdroid's script to be quite effective and efficient in removing Kingroot:
http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html

Plonko said:
I always found W0lfdroid's script to be quite effective and efficient in removing Kingroot.
Click to expand...
Click to collapse
Ugh, so many letters, I'm so confused, please... no more, let's stay with "dumb it down". This saves time so I can roll around in my own feces. :victory:

Plonko said:
I always found W0lfdroid's script to be quite effective and efficient in removing Kingroot:
http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
Click to expand...
Click to collapse
W0lfdorid was one of the versions i tried. no success. I can start the script but then it says failure and every single steps fails. I finally made it to the supersu installed, but it wont update the binaries. installation always failed

coolni said:
W0lfdorid was one of the versions i tried. no success. I can start the script but then it says failure and every single steps fails. I finally made it to the supersu installed, but it wont update the binaries. installation always failed
Click to expand...
Click to collapse
Hmmmm...I don't know what to say. I just used it today after returning a phone to stock Fire OS for my niece. The only thing I can think of is I'm using an earlier version of Kingroot? I'm using KingRoot-4.1.0.524.apk if that matters. I can try to PM it to you, but I'm not sure it will work because, as Bingo mentioned, it is seen as a virus by most servers.

Yup, I also used the oldest version I had on my PC, this way I can avoid the cat and mouse game between Kingroot and Super-Sume ^^ ... well, for the Fire Phone and some "older" KitKat devices that is.
But since 'coolni' popped his Fire Phone cherry just recently, he naturally went for a current version of Kingroot and he's also on the latest Fire OS release; thought process = better bring the big guns so that root is guaranteed.

Bingo Bronson said:
Yup, I also used the oldest version I had on my PC, this way I can avoid the cat and mouse game between Kingroot and Super-Sume ^^ ... well, for the Fire Phone and some "older" KitKat devices that is.
But since 'coolni' popped his Fire Phone cherry just recently, he naturally went for a current version of Kingroot and he's also on the latest Fire OS release; thought process = better bring the big guns so that root is guaranteed.
Click to expand...
Click to collapse
can anybody help to root 4.6.6.1 ?
Kingroot 4.0.0.233 from zip file did not work on my phone with 4.6.6.1.

Having problems on custom recovery
Hello sir I am using amazon 4.6.6.1 almost 1 year ago I have backed up my custom recovery from flashify and deleted accidentally now I need that but can't do anything I have tried most things to get back but can't and also can't root my phone with king root I am installing it but it's saying that app not installed any solution please my email is [email protected]

Snapchat gives "login temporarily failed" error with CM ROM

Hey guys,
I've done some searching around on this issue, and it looks like Snapchat is not allowing me to login as my device is rooted. However, I had the factory OxygenOS ROM (rooted as well) installed before and never had this issue. Now that I have installed Sultanxda's "Unofficial CyanogenMod 13.0 with custom kernel", I can no longer get Snapchat to login. Like I said, from the searching that I've done it look like it is root related, so I went into SuperSU and did a complete unroot. This still hasn't solved the issue yet, so now I'm stuck and not sure what to do. Is there something I'm missing or is there a way to solve this without having to reflash a different ROM and loose all the time spent setting this one up?
Thanks for the help!

saleenman95 said:
Hey guys,
I've done some searching around on this issue, and it looks like Snapchat is not allowing me to login as my device is rooted. However, I had the factory OxygenOS ROM (rooted as well) installed before and never had this issue. Now that I have installed Sultanxda's "Unofficial CyanogenMod 13.0 with custom kernel", I can no longer get Snapchat to login. Like I said, from the searching that I've done it look like it is root related, so I went into SuperSU and did a complete unroot. This still hasn't solved the issue yet, so now I'm stuck and not sure what to do. Is there something I'm missing or is there a way to solve this without having to reflash a different ROM and loose all the time spent setting this one up?
Thanks for the help!
Click to expand...
Click to collapse
Hi, the searching can be useful sometimes
http://forum.xda-developers.com/search/forum/5476?query=snapchat
You need an fully unrooted rom to login into snapchat, after that you can flash supersu.

NevaX1 said:
Hi, the searching can be useful sometimes
http://forum.xda-developers.com/search/forum/5476?query=snapchat
You need an fully unrooted rom to login into snapchat, after that you can flash supersu.
Click to expand...
Click to collapse
Ah, looks like I just didn't search enough. This seems to have done the trick, thanks!

I think you just need to uninstall Xposed Framework for Snapchat to login and then after login you can install Xposed again.

This sounds weird but what worked for me was to download superkiwi via xposed installer, it's supposed to bypass root detection for banking apps in New Zealand but works with snapchat [emoji14]
I found this workaround in a thread somewhere and thought that it wouldn't hurt to try but actually works mighty fine!
Sent from my ONEPLUS A3003 using Tapatalk

Leaving this here in the hopes it helps someone else, took me a bit to find the correct steps.
Currently running the last official CM 13 build for the Droid Turbo (will be moving to LOS soon), rooted with SuperSU Pro, Xposed framework v87, on the newest TWRP.
Nothing worked, not Xposed Switch, Root Switch, nothing. In fact I had to reinstall Xposed Switch to be able to turn root back on, while Root Switch simply uninstalled the SuperSU binary, I had to reflash it. Finally I put it all together and in the following order I got Snapchat to work.
Make sure any OS root (my case CMroot) was turned off.
Download the correct version of Xposed framework Installer, Xposed Uninstaller, and the SuperSU binary (all flashable zip files) for your device to a location on your system that you can easily access from recovery. For me its my TWRP folder.
Uninstall Snapchat. Open a File Explorer and delete the entire Snapchat folder left over.
Select the uninstall "permanently unroot" option from SuperSU, but DON'T let it install the original... Whatever it is, the name escapes me. But don't let it!
Phone will reboot automatically after taking out root, boot to recovery, run Xposed Uninstaller, wipe Cache & Dalvik, reboot phone.
When the phone boots, confirm it is unrooted and Xposed Framework is uninstalled. A root checker app and opening the Xposed App worked for me here.
Install Snapchat, sign into Snapchat. It will accept your login if you did everything correctly.
*This step I did to save myself work in the future, but you can do it later. Turned on CMroot and took a TiBackup of logged in Snapchat in case I ever have to login again, I can just reload the data.*
Boot to recovery. Flash the Xposed framework and the SuperSU binary (in that order), wipe Cache and Dalvik, reboot system.
Open Snapchat to confirm its still logged in. If so grab a TiBack of it for use as needed later.
I hope this helps!
Sent from my DROID Turbo using XDA-Developers Legacy app

Magisk and Wifi Tether Router...Help!

I have a Google version Pixel 2 XL that is BL unlocked and rooted with Magisk. I have a rooted S8 on Vzw and I use Wifi Tether Router and VPN for my hotspot. I bought the Pixel 2 XL to replace my S8 and use as my hotspot. I have made the needed changes to get the hotspot to work on the Pixel, but it will not work and all with the Wifi Tether Router app. I have contacted the creator of the app and he said my issue is with Magisk and that I should uninstall and root with SuperSu. Are there any other apps that can redirect all hotspot traffic through VPN?

I was told many people have rooted Pixel 2 XL with SuperSu. I have tried flashing the latest stable SuperSu zip and also the lastest (I could find) betas, 2.82(SR1 and SR5), and they all failed. Can someone help me root the phone using SuperSu?

txcharlie said:
I was told many people have rooted Pixel 2 XL with SuperSu. I have tried flashing the latest stable SuperSu zip and also the lastest (I could find) betas, 2.82(SR1 and SR5), and they all failed. Can someone help me root the phone using SuperSu?
Click to expand...
Click to collapse
I've had the P2XL since release. The only root method currently available is magisk. Don't know where you heard that about SU, but all the rom and kernel Devs have said that magisk is the only thing that works. ?

I was told that by the app developer. Now I have more issues...I've bricked my phone and can't get past the Google logo on boot. I have flashed the boot, bootloader, modem, system, system other, etc and it's still bricked. I'm getting the "corrupt device" message.

Use the flash all bat file in the factory image zip. If you have data you want to save, open the flash all bat file with notepad or the like and remove the, "<sp>-w" from the file and save it. This is a moot point if you haven't unlocked critical.
Unzip the factory image, but not the zip file inside, and move it all to where your fastboot is located. And run the flash-all.bat file.

txcharlie said:
I was told that by the app developer. Now I have more issues...I've bricked my phone and can't get past the Google logo on boot. I have flashed the boot, bootloader, modem, system, system other, etc and it's still bricked. I'm getting the "corrupt device" message.
Click to expand...
Click to collapse
If you have a backup of the month your on stock in twrp you may be able to get out of it. If not your most likely going to have to flash the factory image with the W in it do a full wipe. you're not bricked though I've been where you're at many times

Did flash-all...Had my hopes up but got error "cannot generate image for userdata". Still getting the "corrupt device". Boots to Google screen and stuck there.
I'm not concerned with any data on it. It's only 4 days old..LOL!

txcharlie said:
Did flash-all...Had my hopes up but got error "cannot generate image for userdata".......
Click to expand...
Click to collapse
remove the -w from the script, or the command if you are doing it manually.
it should flash, then do a factory reset after it boots normally (if you want, I would recommend it to clean it up). Of course if there is anything you want saved off the device, grab it before you reset.

Thanks for the help on the brick situation. I used Deuces' script and it's working fine now. I think I'm going to lock the BL and sell it since I can't use it for what I intended.

txcharlie said:
I have a Google version Pixel 2 XL that is BL unlocked and rooted with Magisk. I have a rooted S8 on Vzw and I use Wifi Tether Router and VPN for my hotspot. I bought the Pixel 2 XL to replace my S8 and use as my hotspot. I have made the needed changes to get the hotspot to work on the Pixel, but it will not work and all with the Wifi Tether Router app. I have contacted the creator of the app and he said my issue is with Magisk and that I should uninstall and root with SuperSu. Are there any other apps that can redirect all hotspot traffic through VPN?
Click to expand...
Click to collapse
I'm in a similar situation. Is there no way to get this to work with Magisk?

davejames500 said:
I'm in a similar situation. Is there no way to get this to work with Magisk?
Click to expand...
Click to collapse
Has anyone figured out how to use Tether on there Magisk rooted Pixel?