Related
Hi
I have tested the root tool from China forum. My device is SGP312 WIFI 32GB 10.3.1.C.0.136. No need to unlocked.
Download the attachment and install. One click and then it will reboot. It is rooted!
But the root-mangement software is Chinese. You can download Supersu or Superuser.
Use the Chinese root software to give Supersu or Superuser root access.
Run Supersu or Superuser and upgrade the binary. Exit and uninstall the Chinese root software.
Reboot. Then you are rooted with Supersu or Superuser.
This is the original link: http://www.mgyun.com/vroot
incredible...works on sgp321 .244......good job....juat install supersu afterwards and remove the chinese app....greatttttt
Good! I can confirm it works, just rooted my still locked SGP311FR with it.
What I don't like it's an exe file, install the app then run it to root.
If someone can extract the script and replace the root apk by superSU it would be cool.
Also I noticed while rooting my tablet that the screen became white two times (really fast for less than a second, sort of blink) like the Display tricks that were used before to root our xperia's.
Anyway thanks.
Btw : @insideccw posting a link to the source, and maybe the name of the autor of this tool, would be better if it's not your own tool.
babylonbwoy said:
Also I noticed while rooting my tablet that the screen became white two times (really fast for less than a second, sort of blink) like the Display tricks that were used before to root our xperia's.
Click to expand...
Click to collapse
That might be the exploit that is accessing the framebuffer causing it.
works like a charm on my sgp351 lte 16gb .244, recomended, thans for the post
Also working with Xperia sp
Sent from my C5303 using Tapatalk 4
I tried this with my 312, but upon removing the chinese superuser with Titanium-backup, i could no longer use Superuser or SuperSU from the play-store. Any insight on to what exactly you guys went about this? I have reset using PC Companion.
Word fine With 4.2.2 thx a lot
Sent from my SGP321 using XDA Premium 4 mobile app
bugger561 said:
I tried this with my 312, but upon removing the chinese superuser with Titanium-backup, i could no longer use Superuser or SuperSU from the play-store. Any insight on to what exactly you guys went about this? I have reset using PC Companion.
Click to expand...
Click to collapse
I think you need to install the alternative superuser app before deleting the Chinese one. I used superuser by chainsdd on my sp
Sent from my C5303 using Tapatalk 4
works great...thanks
That's pretty much what I did. I've tried SuperSU, superuser, and the cwm app. The problem seems to be that the updated binaries don't "stick", SuperSU claimed updating was a success but then prompted me to do so every time I opened it.
bugger561 said:
That's pretty much what I did. I've tried SuperSU, superuser, and the cwm app. The problem seems to be that the updated binaries don't "stick", SuperSU claimed updating was a success but then prompted me to do so every time I opened it.
Click to expand...
Click to collapse
I don't know if the info in this thread may be of any use : http://forum.xda-developers.com/showthread.php?t=1539711.
Specifically in the OP :
Remember, if you remove older first without installing newer one, you will lose Root n newer won't run.
One more thing market version will be regular application, so hard reset can delete it. So better install with flashable zip, to make it system application.
And in Post #8 :
Confirmed working fine! Recommended to install via CWM. It will replace the other (superuser) automatically so you don't have to manually remove it.
I used the above zip file and instructions a long time ago on my Galaxy S....but it may still be relevant for Tablet Z.
What I've been doing us installing from the play store, updating binaries, and then removing the Chinese app. Once I do that, I lose root in the market superSU and other root apps.
I'll probably end up unlocking the boot loader and flashing an image over adb.
Thanks for the help!
bugger
That is because you dont have /system r/w access.
bugger561 said:
What I've been doing us installing from the play store, updating binaries, and then removing the Chinese app. Once I do that, I lose root in the market superSU and other root apps.
I'll probably end up unlocking the boot loader and flashing an image over adb.
Thanks for the help!
Click to expand...
Click to collapse
bugger561 said:
What I've been doing us installing from the play store, updating binaries, and then removing the Chinese app. Once I do that, I lose root in the market superSU and other root apps.
I'll probably end up unlocking the boot loader and flashing an image over adb.
Thanks for the help!
Click to expand...
Click to collapse
It worked for me...I accidentally removed the Chinese app.
1. I did a reroot again.
2. installed dualrecovery and flashed the UPDATE-SuperSU-v1.65.zip.
3. It works now.
Supersu and cwm superuser caused my phone to go in a reboot loop when I tried updating the binaries. Superuser by ChainsDD is working fine though.
Sent from my C5303 using Tapatalk 4
insideccw,
Any tips on how t go about correcting this? Would I need to use adb or can I handle this form within android?
EDIT: Looks like others are having the same issue.
Doesn't work with SGP321 LTE tablet (on the newest firmware .244)
1. in order to uninstall the chinese root app one needs to have SuperSu
2. once you install SuperSU the root checker shows "OK, you're rooted"
3. once you get rid of the chinese root the root checker shows "you're NOT rooted" and the SuperSU binaries can't get updated (strange it needs another update)
Geezer said:
Doesn't work with SGP321 LTE tablet (on the newest firmware .244)
1. in order to uninstall the chinese root app one needs to have SuperSu
2. once you install SuperSU the root checker shows "OK, you're rooted"
3. once you get rid of the chinese root the root checker shows "you're NOT rooted" and the SuperSU binaries can't get updated (strange it needs another update)
Click to expand...
Click to collapse
Works on mine. Update the superuser binaries before deleting Chinese superuser app. On mine, supersu detected the Chinese one and deleted it for me
Sent from my C5303 using Tapatalk 4
bugger561 said:
That's pretty much what I did. I've tried SuperSU, superuser, and the cwm app. The problem seems to be that the updated binaries don't "stick", SuperSU claimed updating was a success but then prompted me to do so every time I opened it.
Click to expand...
Click to collapse
For those of you having this issue as I was, I just got mine to work with SuperSU. Hopefully these steps will work for you too:
-Gain root with the magical Chinese root tool
-install SuperSU
-update SuperSU binaries
-in SuperSU settings, choose "Switch superuser app"
-reboot the tablet and immediately go to the playstore and install SuperSU
-update SuperSU binaries
Let me know if it works!
SM-T700 UK version stock 5.0.2
1. Root using Kingroot 4.5
2. ONLY now !!! install and run Super-Sume
3. Update SuperSu binaries
That's all : you have root, SuperSu and Knox still "O" and Kingroot it's gone...
Would people please post the full build version of the firmware they have success or failure with, so others are aware of which ones work.
has this method been verified by other users?
Share your experience please!
It's brand new...
Verified by myself
Have you maintained root after reboot?
ashyx said:
Already tried it, v4.5 is posted in my kingroot thread, didn't work on lollipop for t805.
Neither did supersu me, binary always fails to update, once it did manage after several tries, but root is lost after reboot.
Supersu me is just the same script as posted in the kingroot thread. Root always lost after reboot.
Have you maintained root after reboot?
Click to expand...
Click to collapse
Just following your thread, messing with Kingroot 4.5 (from your tread) I obtained root.
Also someone there suggesting SuperSume to remove Kingroot.
I use it and that's it
Yes the root it's permanent
stefan.pilsu said:
Just following your thread, messing with Kingroot 4.5 (from your tread) I obtained root.
Also someone there suggesting SuperSume to remove Kingroot.
I use it and that's it
Yes the root it's permanent
Click to expand...
Click to collapse
Can you then install SuperSu or do you need to keep the SuperSume?
Anyone else confirm this method ?
louiscar said:
Can you then install SuperSu or do you need to keep the SuperSume?
Anyone else confirm this method ?
Click to expand...
Click to collapse
Super-Sume install SuperSu
Update binaries and done
I waiting also others to confirm
stefan.pilsu said:
I waiting also others to confirm
Click to expand...
Click to collapse
Ok Thanks for putting this up, if it's reliable it will save a lot time for many.
..guys try install first busy box while with kingo root, then install supersu. update binary. if successful,
..uninstall kingoroot . reboot supersu rules!!!!!!
angelshie said:
..guys try install first busy box while with kingo root, then install supersu. update binary. if successful,
..uninstall kingoroot . reboot supersu rules!!!!!!
Click to expand...
Click to collapse
Super_Sume make all this "work" with one click !
Ok guys, thanks for confirming, Sweet
Thanks for the tip. This worked perfectly. I installed Kingroot 4.5. When Kingroot runs scroll down and press "Try it" and it rooted. I then immediately installed Busybox from the Google Play store and ran the smart installer. After a successful install of Busybox, I then installed Super-Sume from the Play store. I ran Super-Sume and it installed Super SU and removed Kingroot. After that, I opened Super SU and allowed it to update the binary. Rebooted. I checked root with Root Checker app and checked Knox with an app called Knox Status on the Play store. Root is still active and Knox is still at "0". I powered off, then restarted again. Root has stayed.
I did this on a brand new US region SM-T700 pulled straight from the box and updated to Lolilipop from OTA.
System Version:
SM-T700
LRX22G.T700XXU1BOE3
*ROOT WORKING !! SMT-700 OTA 'lollipop'
Confirmed working on Lollipop NEE-T805XXU1BOE3 firmware.
Reflashed back to complete stock then ran Kingroot v4.5, root succeeded first time.
Ran Supersu me to remove Kingroot and install Supersu then updated the su binary.
Rebooted then checked root status. Full root access still available.
No need to install busybox as Supersu me already installs busy box.
Looks like we have a winner, no need to downgrade to Kitkat any more. :good:
Hopefully now T807/707 users can now get root.
Credits go to the devs of Kingroot, Chainfire and Supersu me.
ashyx said:
Confirmed working on Lollipop T805XXU1BOE3 firmware.
Reflashed back to complete stock then ran Kingroot v4.5, root succeeded first time.
Ran Supersu me to remove Kingroot and install Supersu then updated the su binary.
Rebooted then checked root status. Full root access still available.
No need to install busybox as Supersu me already installs busy box.
Looks like we have a winner, no need to downgrade to Kitkat any more. :good:
Hopefully now T807/707 users can now get root.
Credits got to the devs of Kingroot, Chainfire and Supersu me.
Click to expand...
Click to collapse
I've told you ...
ashyx said:
Confirmed working on Lollipop T805XXU1BOE3 firmware.
Reflashed back to complete stock then ran Kingroot v4.5, root succeeded first time.
Ran Supersu me to remove Kingroot and install Supersu then updated the su binary.
Rebooted then checked root status. Full root access still available.
No need to install busybox as Supersu me already installs busy box.
Looks like we have a winner, no need to downgrade to Kitkat any more. :good:
Hopefully now T807/707 users can now get root.
Credits go to the devs of Kingroot, Chainfire and Supersu me.
Click to expand...
Click to collapse
It does not appear to work on T707a with 5.0.2.
Maybe ashyx could help.
What exactly didn't work for you ?
stefan.pilsu said:
I've told you ...
Click to expand...
Click to collapse
Do you think this is likely to work for KitKat ANL1? I already downgraded as part of Ashyx's tutorial to ANF7.
My only reservation to going to Lollipop is that I want to use the Xposed framework which I think is still in it's infancy for 5.x or still not compatible.
So before this my options are to keep the original Kitkat by Flashfire - ANL1 or go directly to Lollipop. For the latter I could just get the OTA and do this method now. But not sure if I go to ANL1 kingroot will work as easily
If not I'll continue in the normal way I guess.
Once you have root with Kingroot install Super Sume and run it.
Kingroot 4.5 from ashyxs tread works for me.
Super-Sume just install busybox, SuperSu and get rid of Kingroot.
Why not use Flashfire to install whatever you want: KK or L ?
I downgraded my Xperia M2 dual d2302 to 4.3 and rooted with towelroot and then flash 4.4.4 followed by flashtool force towelroot using super su. This would uninstall super su on my phone and install its own super su binaries and busybox content. The super su pro would however, remain installed. So, I would have to redownload the super su and as soon as i would open it, it would ask for binary update and then ask for reboot. I would just follow the prompt without question. As soon as it reboots,though the root would be there but sd card and system rewriteable will be gone and there is no way to make my system rewriteable without flashtool reflashing back to 4.3 and following the long procedure. I till now, would blame kitkat and sony for that. This continued for over 8 days till I realised that the real culprit was not sony or kitkat but super su binary update followed by reboot. This is highly anoying. What is the point of root if system or sd card writing is not allowed? For now, I am living with super su by canceling the binary update everytime I open it. I have OCD and I find it highly annoying. I tried searching for an option to cancel auto search for updates bur in vain. My phone works just fine without update. I need no updates and need a way to stop super su asking for update everytime. Please suggest me something.
I have now discovered that even if I cancel binary updates, supersu auto updates causing the same problem. So, now I have decided to live without Supersu as supersu is not needed for root. I have an unlimited root access for all my apps which have root permission now and to add icing to the cake, my bootloader is locked. If anyone else is searching for a way to make Sony Xperia M2 dual 4.4.4 system writebale without unlocking bootloader, just follow:
LOCKED BOOTLOADER
1. Downgrade to JB, Root your Phone using Towel Root in Jelly Bean
2. Update via OTA to KK 4.4.2 or KK 4.4.4 whatever you need (4.4.4 is recommended)
3. In this process, don't try to install or uninstall anything
4. Wait for booting finish
5. Install latest SuperSU from Play Store
6. Open Flashtool in PC
7. Connect your phone to PC
8. Now flashtool will describe your phone information, then click Root Tab in top, after that choose force root by TowelRoot
And after this, do not install supersu or any other root control app. Just let your phone be as such without updating binaries or anything and you will have root. You will have unrestricted root on Xperia M2 dual, Enjoy and remember not to install supersu, kingsu, cm superuser or any similar app.
I was thinking to help you, but then i was worried if something else goes wrong, then you will blame me, just like you blame super su.
Yeah I'm sure of that. Just a note for you: I already have root. Super Su is not needed for root. It only controls which app gets access to root. The only problem without super su is that there is less safety as any app can get root without restrictions. I just want super su to be polite and less invasive by learning to live with whatever it gets rather than forcing itself on us. If I don't want binary updaye, super su has no business updating on its own. I just want a way to stop super su from updating binaries and I don't think you can help unless you can patch the app which I doubt
gauthamraob said:
Yeah I'm sure of that. Just a note for you: I already have root. Super Su is not needed for root. It only controls which app gets access to root. The only problem without super su is that there is less safety as any app can get root without restrictions. I just want super su to be polite and less invasive by learning to live with whatever it gets rather than forcing itself on us. If I don't want binary updaye, super su has no business updating on its own. I just want a way to stop super su from updating binaries and I don't think you can help unless you can patch the app which I doubt
Click to expand...
Click to collapse
I think you are misunderstand about the binary thing, supersu need to update the binary so it will work properly, its not like updating app on playstore, binary is the root system itself i believe.
Help me out on this one, afaik, root access need atleast 1 superuser app to allow and control the root access for any root app. Any root app will need to request for granted the root at least once ti get the root access.
So tell me, how do you manage to have rooted device without any root management app such [email protected]@cm supersu?
---------- Post added at 02:42 PM ---------- Previous post was at 02:31 PM ----------
BTW, tell us what do you need on your device that will make you feel better. (About the superuser @ root thing of course)
NeoLogY said:
I think you are misunderstand about the binary thing, supersu need to update the binary so it will work properly, its not like updating app on playstore, binary is the root system itself i believe.
Help me out on this one, afaik, root access need atleast 1 superuser app to allow and control the root access for any root app. Any root app will need to request for granted the root at least once ti get the root access.
So tell me, how do you manage to have rooted device without any root management app such [email protected]@cm supersu?
Click to expand...
Click to collapse
No, I am already having root . I have integrated most of the updates to my system app to my sys/app folder through lucky patcher and have installed the modded play store . I can even edit and delete system files in "ES explorer" file manager and stop items from startup using "all-in-one-toolbox" boot manager. I have an older version of su binaries which was installed automatically into my phone by "flashtool by androxide" using the force root mode using towel root :good: . But the supersu app was not installed and if the app existed before rooting, flashtool would uninstall it and also replace the new su binaries with an older version ! So, I already have full root access without the supersu app.
As far as i know, supersu is not needed for root. It is only a gatekeeper app which restricts the unlimited access of root to any app by making the apps that need root to ask for permission first. Without supersu installed, root apps get root access without asking permission provided binaries (any version) are already present. Also, for normal people who don't know or can't install binaries directly, they rely on apps like supersu, CM etc for installing the binaries. But once the binaries are installed, the supersu app is no longer needed for root (except in cases of OTA updates or updation of binary to a newer version) but instead works as a security guard for root.
Edit:
What I want is a way to make supersu submissive and to make do with whatever binaries are already present. If it is not broken, then there is not need to fix/update it. But supersu is extremely adamant. Even when I cancel the update, it gets the binary updated by itself when it gets an internet connection. And after reboot, my system rewriteable access would be gone! And how do I know for sure that Supersu updated binaries without my consent? That is because when I open supersu, it no longer asks for binary updates implying that it updated it on its own. I want supersu to understand that it is my phone and I will install only those things that i deem fit to be installed. Auto update services are something which i don't like.
What I want is a way to make supersu submissive to my command and to make do with whatever binaries are already present. If it is not broken, then there is not need to fix/update it. But supersu is extremely adamant. Even when I cancel the update, it gets the binary updated by itself when it gets an internet connection. And after reboot, my system rewriteable access would be gone! And how do I know for sure that Supersu updated binaries without my consent? That is because when I open supersu, it no longer asks for binary updates implying that it updated it on its own. I want supersu to understand that it is my phone and I will install only those things that i deem fit to be installed. Auto update services are something which i don't like and must not be done
Actually, you do have a good point here, as by mean we want root for full control of our property. And i just realize about the binary being updated thru network without our consent. I am hoping if you could get a logcat of the device when this happened next time. Including modem log, system, main, event, audit log, if possible. Im not sure if i can help you on this one, but i really want to look deeper into this one. Hope you can help me, using SysLog app. Can you do that, please?
NeoLogY said:
Actually, you do have a good point here, as by mean we want root for full control of our property. And i just realize about the binary being updated thru network without our consent. I am hoping if you could get a logcat of the device when this happened next time. Including modem log, system, main, event, audit log, if possible. Im not sure if i can help you on this one, but i really want to look deeper into this one. Hope you can help me, using SysLog app. Can you do that, please?
Click to expand...
Click to collapse
At present I am using my phone without supersu as I will have to spend a lot of time downgrading to 4.3 and then rooting followed by painfully slow 4 OTAs in succession (there is no single direct OTA from 4.3 to 4.4.4 on Xperia M2 dual, unfortunately :crying: ) followed by installation of all my apps. I too wish there was a fix for supersu but the time I'll have to spend on that will be enormous and also considering that in this september my phone will mostly get lollipop 5.1, the 4.4.4 woes will soon be history.
Also, I want to mention that I haven't unlocked my bootloader yet. If I unlock my bootloader, all these problems with supersu will vanish. The actual difficulty I am facing is because there is no single post on the internet that says how to get system to be rewriteable without unlocking bootloader in Xperia M2 devices. Every post I have read of only has people with unlocked bootloader saying what to do and people with locked bootloader complaining that they aren't able to make their system rewriteable. I am probably one of those rare people who managed to get complete root with locked bootloader and hence facing the issue of lack of peer help.
Anyways, I really appreciate your interest shown in helping me. If I ever have to update my binaries in the future I will definitely take a log of it and pm it to you in case similar situation arises.
Cheers.
Same thanks to you. Actually, i think it is better to put the log here, as more hands and mind will be able to reach it, meaning higher percentage on discovering any hidden in the log. You are right about the lock bootloader, even until now i still unable to manage to truely understand about bootloader, as i didn't have any device with it to get inhand with the system. As always, i do appreciate any kinda knowledge exchange. Thanks in any way.
That's exactly why your system is read only and you can't move apps/data to sd ect without supersu installed and the binaries updated and Sony ric killed you don't have full root r/w access to system. The way you have rooted your device is the same way I did mine it's the easiest way there is if you can't get it right doing that way then maybe you should put your Phone back to stock. Flash jb, root with towelroot apk(at this point do not update anything), now update over the air to 4.4.2 then again to 4.4.4(again update nothing but phone)root will stick after each update. Download supersu connect your phone to flashtool and click on the force root tab(kills Sony ric installs supersu binaries and busybox) making system r/w
Search on here for the m2 forum if you still have problems
D2303,18.3.1.C.1.15 kk, deodexed, debloated, rooted, philz touch recovery, bravia engine 2+x-reality+z3 super vivid, viper audio, xposed mods.
Hello,
I recently used the toolkit to unlock and root my Sprint N6. Super user was installed and works. I installed Rootcheck after everything was complete and it verifies that the phone is rooted. I have installed Nexus 6 double tap to wake and LED control and both state that the phone is not rooted. Super user shows both those apps have super user access.
What am I missing? Thank you!!
itlbok333 said:
Hello,
I recently used the toolkit to unlock and root my Sprint N6. Super user was installed and works. I installed Rootcheck after everything was complete and it verifies that the phone is rooted. I have installed Nexus 6 double tap to wake and LED control and both state that the phone is not rooted. Super user shows both those apps have super user access.
What am I missing? Thank you!!
Click to expand...
Click to collapse
use the latest SuperSU
I am on version 2.65 and from what I can tell, that is the latest.
itlbok333 said:
I am on version 2.65 and from what I can tell, that is the latest.
Click to expand...
Click to collapse
you will also need to install busybox as well, as many root apps need it. install from the play store, then install from the app. search busybox in the play store, then choose stericsons version.
---------- Post added at 11:17 AM ---------- Previous post was at 11:15 AM ----------
and supersu 2.71 http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Thank you for the reply, Sorry I failed to mention I do have the move listed busy box installed as well. I have clicked on install from within the app as well. Still none of the mentioned root apps work, all say phone appears to not be rooted...
itlbok333 said:
Thank you for the reply, Sorry I failed to mention I do have the move listed busy box installed as well. I have clicked on install from within the app as well. Still none of the mentioned root apps work, all say phone appears to not be rooted...
Click to expand...
Click to collapse
try flashing the supersu 2.71 with twrp recovery, you should have root when you boot up. dont use the toolkit.
simms22,
I flashed version 2.71 through recovery, after reboot it was installed. Same "phone does not appear to be rooted" when trying to use the root apps... Root check still says phone is rooted. This is puzzling!
itlbok333 said:
simms22,
I flashed version 2.71 through recovery, after reboot it was installed. Same "phone does not appear to be rooted" when trying to use the root apps... Root check still says phone is rooted. This is puzzling!
Click to expand...
Click to collapse
very odd! tell me, which rom are you using? and did you wipe your data before rooting? if not, you might have to wipe your data then reflash your rom/gapps, and supersu.
I am stock rooted. Yes I wiped data and started from scratch after unlock and root.
itlbok333 said:
I am stock rooted. Yes I wiped data and started from scratch after unlock and root.
Click to expand...
Click to collapse
when you try to use a root app, so you get a little popup that asks you to give the app root? do yoh have the supersu app installed as well?
Yes SuperSU 2.71 flashed, the popup comes up and I grant access. Then each app says not rooted. Makes zero sense... The apps even show up in SuperSU app.
Yes, there is a popup and I have granted SU access to the above root apps, still no joy. I have SuperSU 2.71 flashed and installed, Root check verifies root.
I had this. The fix is to uninstall Busybox and reinstall into an alternative directory where it can be found. Mine appears to work fine in /su/bin, but if that doesn't work for you try the others (/system/xbin, /system/bin etc.)
It may not even need to be uninstalled - you could just try installing into the different directories until you find the one that the root apps are checking for root, though I'm not sure whether that would clutter your device with redundant binaries. I'm sure someone will be able to advise on that.
I just got a new Fire 7" 5gen, with Fire OS 5.3.1. I immediately used Supertool to root it and install the CM ROM.
So far so good.
But not realising how CM deals with root access, I manually installed SuperSU. SuperSU wanted to update the binary, which I accepted. It also wanted to remove the existing root manager, which I also accepted... And then the binary update failed.
It's only then I realised that I somehow ended up with a custom ROM but no root. Neither SuperSU nor Superuser can get root access (both failing binary update), and Kingroot can't root it either. I'd have just flash CM again, but FlashFire also doesn't work without root. So I'm kind of stuck now...
Any idea how I can get root?
Just realised that I had to turn on root in Dev options. I did that and rebooted, but Super SU still fails to update the binary. FlashFire now says "Root was found but access could not be acquired".
Make sure you did reboot after root activation in dev options
Yes, as I said, I already rebooted. Any other idea?
ulysseh said:
I just got a new Fire 7" 5gen, with Fire OS 5.3.1. I immediately used Supertool to root it and install the CM ROM.
So far so good.
But not realising how CM deals with root access, I manually installed SuperSU. SuperSU wanted to update the binary, which I accepted. It also wanted to remove the existing root manager, which I also accepted... And then the binary update failed.
It's only then I realised that I somehow ended up with a custom ROM but no root. Neither SuperSU nor Superuser can get root access (both failing binary update), and Kingroot can't root it either. I'd have just flash CM again, but FlashFire also doesn't work without root. So I'm kind of stuck now...
Any idea how I can get root?
Click to expand...
Click to collapse
ulysseh said:
Just realised that I had to turn on root in Dev options. I did that and rebooted, but Super SU still fails to update the binary. FlashFire now says "Root was found but access could not be acquired".
Click to expand...
Click to collapse
At this point your best/only option is to reload FireOS via Amazon's stock recovery (same version as before) and redo root, Flashfire, etc. There is no reliable way to secure root on a custom rom as device lacks access to a 'real' recovery environment. Don't bother with KingRoot on CM - likely won't work.
Davey126 said:
At this point your best/only option is to reload FireOS via Amazon's stock recovery (same version as before) and redo root, Flashfire, etc. There is no reliable way to secure root on a custom rom as device lacks access to a 'real' recovery environment. Don't bother with KingRoot on CM - likely won't work.
Click to expand...
Click to collapse
Yeah, I did the whole thing from zero again. Happily it worked this time. Thanks!