[Completed] [Q] King root assist - XDA Assist

I have used kingroot to root my phone, as i was trying to change the super user to SuperSU, i deleted kinguser, it removed my root, Now when running kingroot it acts as though i am already rooted, how can i fix this?
This is the first root i have used that worked because i have a Mediatek phone. Please help Orion pro x500a 4.4.2 android
I think i may still have bootloader.... http://prntscr.com/5rha93
I have SuperSu as a system app, but no binary. It fails every time
I think i could flash a custom recovery the flash supersu, but would that have the binary?
If i could do this what program would i use?

I dont even know
Anyone?

N_psycho_PD_uh? said:
Can you boot to system at all? Since you have prerooted there might be enough vulnerability left to use cydiaimpactor to try getting root again, it attacks the android master key exploit and one other abd will not harm your device if the nethod doesn't work. Have you tried flashing superuser or superSU by ADB to your device, if you can get a recovery installed then you are rooted, if you can get to recovery mode then you can flash a ROM you can also flash a ROM through ADB but you've got to be sure you're rooted before you can do ADB.
Click to expand...
Click to collapse
I can boot to system, i can use android normally, i have supersu but no binary, it is a system app, it stayed through a factory reset. I have a bootloader of some sort. I posted a image of it, i can try to get a clearer one if needed. As i said it is a mediatek phone, what program would i use to flash? Couldnt i just flash supersu? Instead of whole rom, i will flash rom if there is a supported one.

N_psycho_PD_uh? said:
If you already have CWM or other custom recovery then yes you can flash a superuser or superSU zip through recovery. Did you try the cydiaimpactor for pc to see if you could get root binaries to act correctly, if it fails it won't damage anything. this program puts the su binaries into system so you can download superuser and install from playstore, cydiaimpactor is supposed to work on most android devices.
---------- Post added at 05:17 AM ---------- Previous post was at 05:15 AM ----------
If you have a custom recovery then you can flash superuser or superSU zip.
Click to expand...
Click to collapse
Trying impactor again

http://prntscr.com/5ri8s8
:/
Using the default
# drop SuperSU su to /system/xbin/su

Hi,
You asked about this device previously, and we couldn't find anything relevant on XDA. Please use the second link I gave you previously to ask for help on your device,
http://forum.xda-developers.com/general/xda-assist/help-root-orion-pro-t2982390
Thank you for understanding. Thread closed.

Related

[Q] Rooted but no Root access

Hi every one,
I currently am using an LG G2 from tmobile (801 model). My device says its rooted but it doesnt have root access because I forgot to flash supersu binaries before i flashed the 4.4.2 version of the software. But now my custom recovery doesnt exist anymore.
I've tried using LG flash tools to flash back to 4.2. stock settings to start over but I am unable to do so for some reason. LG Flash tools isnt able to recognize my G2 in download mode. My computer is able to recognize my G2 when it is turned on though.
So is there anyway to flash a custom recovery without root access?
Or is there anyway to flash supersu binaries without a custom recovery using ADB?
I've tried trouble shooting with multiple threads and multiple downgrade methods but none of them are giving me any luck. I really want to flash a custom rom on my LG g2 and have the benefits of root access.
Any help would be greatly appreciated.
sai.nissankula said:
Hi every one,
I currently am using an LG G2 from tmobile (801 model). My device says its rooted but it doesnt have root access because I forgot to flash supersu binaries before i flashed the 4.4.2 version of the software. But now my custom recovery doesnt exist anymore.
I've tried using LG flash tools to flash back to 4.2. stock settings to start over but I am unable to do so for some reason. LG Flash tools isnt able to recognize my G2 in download mode. My computer is able to recognize my G2 when it is turned on though.
So is there anyway to flash a custom recovery without root access?
Or is there anyway to flash supersu binaries without a custom recovery using ADB?
I've tried trouble shooting with multiple threads and multiple downgrade methods but none of them are giving me any luck. I really want to flash a custom rom on my LG g2 and have the benefits of root access.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
All you need to do is install the towelroot.apk to give instant temporary root. Then install SuperSU from the dev thread here on xda or from the play store. After installing SuperSU go to its settings and select install as a system app and reboot when finished. It might take 2 attempts before it successful (it always takes me 2 tries). Then uninstall towelroot as it's no longer required since you've gained permanent root. Now install the autorec.apk and you'll install TWRP recovery. Now that you have root and recovery and have control of your device you can customise to taste. In my case I always install busybox and a terminal emulator so I can further fine tune my system.
I hope this helps
Ciao
still got issues :/
Odysseus1962 said:
All you need to do is install the towelroot.apk to give instant temporary root. Then install SuperSU from the dev thread here on xda or from the play store. After installing SuperSU go to its settings and select install as a system app and reboot when finished. It might take 2 attempts before it successful (it always takes me 2 tries). Then uninstall towelroot as it's no longer required since you've gained permanent root. Now install the autorec.apk and you'll install TWRP recovery. Now that you have root and recovery and have control of your device you can customise to taste. In my case I always install busybox and a terminal emulator so I can further fine tune my system.
I hope this helps
Ciao
Click to expand...
Click to collapse
However even when i go into supersu, it keeps saying my binaries are not up to date. So i cant install anything and I cant do anything to install a custom recovery without root access.
sai.nissankula said:
However even when i go into supersu, it keeps saying my binaries are not up to date. So i cant install anything and I cant do anything to install a custom recovery without root access.
Click to expand...
Click to collapse
So you have installed Towelroot, achieved root then having issues installing the SuperSU.apk this is indeed an issue. Towelroot should allow for it to be installed. When you install Towelroot do you get the warnings from the installer and Lookout that the package contains an exploit? Do you interrupt or stop it from fully installing when you see the warnings? The only thing I can think of is you are doing something wrong when installing towelroot which is prohibiting it from doing its job in gaining root.

[Q] Why does Super su says "No binaries installed"

Just flashed the factory Rom and got everything set up. I flashed TWRP then tried to flash the latest SuperSu to get root and it installed it but when I went to open it it would say that I don't have any binaries installed and I can't uninstall SuperSU either. I tried to install CWM Recovery and refresh it through there but I still have the same issues... :/ What am I doing wrong or how can I get my phone rooted properly? Thanks for any help!
Nocturnal86 said:
Just flashed the factory Rom and got everything set up. I flashed TWRP then tried to flash the latest SuperSu to get root and it installed it but when I went to open it it would say that I don't have any binaries installed and I can't uninstall SuperSU either. I tried to install CWM Recovery and refresh it through there but I still have the same issues... :/ What am I doing wrong or how can I get my phone rooted properly? Thanks for any help!
Click to expand...
Click to collapse
You need to flash a kernel that is permissive and then flash SuperSU there are a few in the forums if you search you shall find them
Instead of a permissive kernel, simply use Chainfire's AutoRoot, which will flash a more secure kernel and SuperSU automatically. You don't even need TWRP for this. http://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip
Go to http://autoroot.chainfire.eu/ to get AutoRoot for other devices.
aalaap said:
Instead of a permissive kernel, simply use Chainfire's AutoRoot, which will flash a more secure kernel and SuperSU automatically. You don't even need TWRP for this. http://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip
Go to http://autoroot.chainfire.eu/ to get AutoRoot for other devices.
Click to expand...
Click to collapse
So I flash this in ADB? Is the secure kernel the same as stock? and if I were to flash a customer kernel like FK would I lose root? Sorry for all the questions just trying to clarify some stuff so I'm not completely ignorant to what I'm doing lol
There's a batch file that does it. You run it in the bootloader, not ADB.
FK has a Lollipop compatible kernel, but try and root stock first. Then flash FK's Lollipop version (it's different) and run CF AutoRoot again. Just to be sure things are working. Personally, I'm going to use stock for a while, understand the performance and then try FK or EX or whatever, so I'll be able to tell the difference.

[Q] Is it impossible to Root and put a custom rom on this device?

I can't find a guide for dummies for it, nor any compatible automatized program or a rom created for it...
Pizzadelivefr said:
I can't find a guide for dummies for it, nor any compatible automatized program or a rom created for it...
Click to expand...
Click to collapse
Been away for a while now so can't vouch if there is a custom ROM available at this moment for your specific K2 variant. However, rooting is very possible. Simply unlocking your bootloader and booting up TWRP recovery is enough to do the job since TWRP will root the device for you. TWRP will or should detect if the device is rooted or not. If it is not then when you select to reboot your system it should ask if you would like to install SuperSU or in lamen terms, to root your device. Obviously you will say yes at this point. When the device reboots then go to the play store to update SuperSU. Once it is updated open the SuperSU app so it can update the su binary. It will ask to update the su binary either normally (by writing to your system with write permissions) or via twrp\cwm. To select the normal option you must either be S-Off or have a custom kernel specific to your K2 variant which has write protection removed. Otherwise, you must select the twrp\cwm method where it will reboot back to the custom recovery and make the change from there. Once the su binary is successfully updated then you are now properly rooted. Do not EVER flash a custom ROM unless the ROM Developer states that it is compatible for your device.

SuperSU - There is no SU binary installed, and SuperSU cannot install it.

Hi
I use a Samsung Galaxy Note 4 (exynos) which I recently updated to Marshmallow (6.0.1). The update was a success through Odin and after that I was able to root and install TWRP 2.8.7 did a back up and later upgraded to TWRP 3.0.1-0 which at this point is only accessible through home, volume + and power button and not Quick boot as I was previously able to.
1. Somehow I lost root access and can't figure if out if I should revert back to TWRP 2.8.7 IS THAT THE PROBLEM?
2. Should I re-root manually (don't even know what this means as I can only assume using Odin)?
I've tried to uninstall SuperSU AND and reinstall as some forums had suggested to no avail.
I realized this problem when I didn't get prompts to grant access to certain apps and when I opened the actual SU app I got the message ,
'' There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 5.0, you need to manually re-root- consult the relevant forums for your device!"
I have researched and read all types of related solutions but none that talks abut this particular issue... Am I alone out there, please assist as I'm about to wipe the entire phone and stick to basic android, which will see me die of boredom.
I have same problem as well. Tried unintalling and reinstalling SuperSU but the problem still the same. I even flash the AutoCFroot, but still no luck.
Please help
Hi @rxk since I was impatient for responses I figured I had no option but to redo the process from scratch... so I wipe the cache and did a factory reset.
Reinstall the official marshmallow 6.0.1
Used CF-Auto-Root-tre3g-tre3gxx-smn910h for root access
Installed TWRP 2.8.7 instead of the I previously had 3.0.1
I just restored my backup everything was working fine for about 20 mins and we're back to square one. Depressed.
Download another super su version.zip and flash it through recovery.some su versions I used had this problem
Thanks I installed BETA-SuperSU-v2.72-20160510112018 and it worked perfectly for me.
Glad it worked for you
I also get the error above and need to update Super SU. When I go to recovery I have 3 options to install. Through ADB, External storage or Cashe.
How to proceed? The recovery is not TWRP but Android recovery. Thank you
The problem is with su version .pls try another version su version. Download another su version.zip and flash it through recovery
[email protected] solution worked for me... I tried a few other versions of the su and found one that worked well. I wonder what happend to his/her "thanks" button thou.
When I go to recovery I have 3 options to install. Through ADB, External storage or Cashe.
I don't know which option to follow.
I dont think that there is samsung stock 6.0 SU release... if you need root access then revert back to 5.0... or you can flash a custom ROM
I'm running an eRobot 6.0.1 custom rom, installed BETA-SuperSU-v2.72-20160510112018 and it worked perfectly for me.
Just start from square one .download a another version SuperSU.zip file and flash it in recovery
Just forget about the other 3 options
---------- Post added at 11:11 AM ---------- Previous post was at 11:11 AM ----------
@gizomot ikr lol
I'm sorry, I don't understand what to do.
Just download a super su.zip file say betasupersu2.52 .zip .now head on to recovery click install and install the 2.52.zip
https://drive.google.com/file/d/0B-CJc5WWY-robUtYQ0dscDJqS00/view?usp=drivesdk .
Is there a option install from zip in your android recovery then go ahead and install the above file if not try twrp or cwm
i have the same problem just like you.
i have a nexus 5 and lately l've flashed nougat Aosp 7.0
and it's running fine,afyer that i flashed supersu.zip and regained root access,then installed busybox which asked me to disble an option that has to do with scanning supersu.
i confirmed yes,my phone rebooted,and then i figured out that i lost root cuz Supersu says ''Su binaries aren't installed and supersu can't install them.
i tried reflashing several versions of supersu via recovery(twrp) including v2.76, v2.77 ,and v2.78
it says succesful.
but when i reboot,no supersu in app drawer,an eeven if i install it from play store,the pop-up window saying no su binary is installed is still there.
please heeeelp help Sos ? ?
---------- Post added at 06:53 PM ---------- Previous post was at 06:51 PM ----------
i have the same problem just like you.
i have a nexus 5 and lately l've flashed nougat Aosp 7.0
and it's running fine,after that i flashed supersu.zip and regained root access,then installed busybox which asked me to disble an option that has to do with scanning supersu.
i confirmed yes,my phone rebooted,and then i figured out that i lost root cuz Supersu says ''Su binaries aren't installed and supersu can't install them.
i tried reflashing several versions of supersu via recovery(twrp) including v2.76, v2.77 ,and v2.78
it says succesful.
but when i reboot,no supersu in app drawer,an eeven if i install it from play store,the pop-up window saying no su binary is installed is still there.
please heeeelp help Sos 😁 😀

root my stock unrooted rom

hi guys.....
i had recently unroot my moto g3 and install stock root to use my jio sim.
but i really miss the root access so, is there any way to to have root access.
when i flash supersu it will get stuck into bootlogo and will not proceed.
i waited for half an hr but no sign of booting up
anyone have a way to get root access to stock rom plzz help........
Just flash this super user zip file
http://forum.xda-developers.com/attachment.php?attachmentid=3655401&d=1456122222
is supersu installing systemless?
make sure to do this first in twrp terminal: "echo SYSTEMLESS=true>>/data/.supersu"
Sushilsingh said:
hi guys.....
i had recently unroot my moto g3 and install stock root to use my jio sim.
but i really miss the root access so, is there any way to to have root access.
when i flash supersu it will get stuck into bootlogo and will not proceed.
i waited for half an hr but no sign of booting up
anyone have a way to get root access to stock rom plzz help........
Click to expand...
Click to collapse
You already have an existing thread on this problem, and were told what needs to be done and where to go to get that information and additional assistance... Why are you not using the resources that were given to you previously? There is no magic fix, something was done incorrectly or you are using the incorrect files.
The answer and all support you will need are in this thread: http://forum.xda-developers.com/2015-moto-g/general/guide-how-to-root-moto-g-2015-model-t3448572
acejavelin said:
You already have an existing thread on this problem, and were told what needs to be done and where to go to get that information and additional assistance... Why are you not using the resources that were given to you previously? There is no magic fix, something was done incorrectly or you are using the incorrect files.
The answer and all support you will need are in this thread: http://forum.xda-developers.com/2015-moto-g/general/guide-how-to-root-moto-g-2015-model-t3448572
Click to expand...
Click to collapse
buddy i just install a clean XT1550_OSPREY_RETASIA_DS_2GB_6.0.1_MPI24.107-55_cid7_subsidy-DEFAULT_CFC.xml.zip
stock rom and twrp twrp-osprey-3.0.2-r1.img as you told.
and that command also
echo SYSTEMLESS=true>>/data/.supersu
cat /data/.supersu
it shows systemless=true
and installed latest supersu SR1-SuperSU-v2.78-SR1-20160915123031.zip from its official site
after that i wipe cache and dalvik.
i reboot it.
and its get reboot without supersu (root) permission.
what should i do?
Sushilsingh said:
buddy i just install a clean XT1550_OSPREY_RETASIA_DS_2GB_6.0.1_MPI24.107-55_cid7_subsidy-DEFAULT_CFC.xml.zip
stock rom and twrp twrp-osprey-3.0.2-r1.img as you told.
and that command also
echo SYSTEMLESS=true>>/data/.supersu
cat /data/.supersu
it shows systemless=true
and installed latest supersu SR1-SuperSU-v2.78-SR1-20160915123031.zip from its official site
after that i wipe cache and dalvik.
i reboot it.
and its get reboot without supersu (root) permission.
what should i do?
Click to expand...
Click to collapse
So you fastboot flashed the ROM and verified it booted successfully (an initial boot is essential prior to rooting, it sets up the RAM disk and other boot image things the first time), rebooted, flashed TWRP (3.0+) and backed up, did the echo command and flashed SuperSU 2.78 SR1 and it still failed?
Flash the 2.62-3 beta of SuperSU https://download.chainfire.eu/751/SuperSU/ it forces systemless install regardless of detected options. You can update normally in the Play Store, then update the binary in the app.
One of those two methods will work, if it doesn't then you have something more going on then meets the eye or there is a piece of information you are not giving us. This is a tested and working process on every single known Moto G 2015 variant.
BTW, clearing cache and dalvik is not required when rooting, you are just increasing the time it takes to boot for no reason.
acejavelin said:
So you fastboot flashed the ROM and verified it booted successfully (an initial boot is essential prior to rooting, it sets up the RAM disk and other boot image things the first time), rebooted, flashed TWRP (3.0+) and backed up, did the echo command and flashed SuperSU 2.78 SR1 and it still failed?
Flash the 2.62-3 beta of SuperSU https://download.chainfire.eu/751/SuperSU/ it forces systemless install regardless of detected options. You can update normally in the Play Store, then update the binary in the app.
One of those two methods will work, if it doesn't then you have something more going on then meets the eye or there is a piece of information you are not giving us. This is a tested and working process on every single known Moto G 2015 variant.
BTW, clearing cache and dalvik is not required when rooting, you are just increasing the time it takes to boot for no reason.
Click to expand...
Click to collapse
well, all the things get installed successfully but even the installation of supersu.zip file also
but it always reboot without any root access or supersu app
i try to install supersu from playstore but it wont help much
after that i tried BETA-SuperSU-v2.62-3-20151211162651.zip this version
and this version does the job
thanks buddy, i really appreciate your help.
acejavelin said:
So you fastboot flashed the ROM and verified it booted successfully (an initial boot is essential prior to rooting, it sets up the RAM disk and other boot image things the first time), rebooted, flashed TWRP (3.0+) and backed up, did the echo command and flashed SuperSU 2.78 SR1 and it still failed?
Flash the 2.62-3 beta of SuperSU https://download.chainfire.eu/751/SuperSU/ it forces systemless install regardless of detected options. You can update normally in the Play Store, then update the binary in the app.
One of those two methods will work, if it doesn't then you have something more going on then meets the eye or there is a piece of information you are not giving us. This is a tested and working process on every single known Moto G 2015 variant.
BTW, clearing cache and dalvik is not required when rooting, you are just increasing the time it takes to boot for no reason.
Click to expand...
Click to collapse
Thanks, thats works for me..! i tried 3 time until work
PD: (when you root, install recovery or unlock bootloader without enough time happens this kind of things)..

Categories

Resources