i am running BML4 and wanted to root the phone, i tried all sorts of methods, saferoot, towelroot, impactor, all failed so i just flashed a custom recovery and installed supersu 2.00 from a flashable zip, boot the phone and adb shell in, type su, it returns me to $, every time, super su sees no problem and the su binary and daemonsu are in ./system/xbin but still i cannot get root access, have samsung finally won or something?
i also tried flashing a custom rom that already rooted, but any roms just bootloop as nothing seems to be based on bml4 and older stuff just doesnt seem to agree with this bootloader, any attempt to flash to an earlier version results in the bootloader just blocking boot entirely (thanks for that samsung, i really needed you to protect me from doing what i want with my device)
does anyone know a way to root this thing or should i just give up
Try installing BusyBox
you do not need busy box to have root.
But many root apps as well as settings in custom roms use busybox to run the scripts that make them work. so while you can root without busybox you are very limited as to what you can do with it.
so while you dont need it to have the phone rooted. its still prety much needed to take advantage of that rooting
Click to expand...
Click to collapse
from Here
I am running rooted BML4 without any issues. I have rooted using this post:
http://forum.xda-developers.com/showthread.php?t=2364980
Related
Please can someone explain why android commander is allways reporting me my HOX has no root access?
This happens to me on every rom I've tried yet.
Or is this related to S-On?
Try rooting a few times, make sure busy box is installed and use different methods to root if available.
icke said:
Please can someone explain why android commander is allways reporting me my HOX has no root access?
This happens to me on every rom I've tried yet.
Or is this related to S-On?
Click to expand...
Click to collapse
Connect your phone to your pc and execute these
Code:
adb shell su
then you should get this # if you have root
!!!Solution
"The Root access : No because" you'r using the stock rom which have a "secured adb" (even when you'r rooted)
Download the "adbd insecure" in this thread and "Enable insecure adbd", problem solve:
http://forum.xda-developers.com/showthread.php?t=1687590
problem not solved for SM-T900
ADBD Insecure says me
Binary : Insecure
USB Debugging : Enable
But always Root access : No in Android Commander
Calimero Oeuf said:
problem not solved
ADBD Insecure says me
Binary : Insecure
USB Debugging : Enable
But always Root access : No in Android Commander
Click to expand...
Click to collapse
I installed the latest BusyBox, then re-rooted and now it sees root.
popeye2014 said:
I installed the latest BusyBox, then re-rooted and now it sees root.
Click to expand...
Click to collapse
You re-rooted after Busybox, so you rooted a second time ?
and now you have Root access : availlable in Android Comander ?
You have the galaxy Tab Pro 12.2 SM-T900 ?
Calimero Oeuf said:
You re-rooted after Busybox, so you rooted a second time ?
and now you have Root access : availlable in Android Comander ?
You have the galaxy Tab Pro 12.2 SM-T900 ?
Click to expand...
Click to collapse
No, not the Galaxy but was having the same problem with Android Commander not recognizing root. Saw the post above about re-rooting and also applying the adb insecure app. Did both and I mean just doing the same root process without un-rooting first. I use Super One Click for my phone. Anyway, still didn't work.
So I downloaded BusyBox Free from the playstore and installed it. Ran Super One Click again, also doing the Shell root, and it worked! Don't know if coincidence or just got lucky but posted hoping it might help others.
popeye2014 said:
No, not the Galaxy but was having the same problem with Android Commander not recognizing root. Saw the post above about re-rooting and also applying the adb insecure app. Did both and I mean just doing the same root process without un-rooting first. I use Super One Click for my phone. Anyway, still didn't work.
So I downloaded BusyBox Free from the playstore and installed it. Ran Super One Click again, also doing the Shell root, and it worked! Don't know if coincidence or just got lucky but posted hoping it might help others.
Click to expand...
Click to collapse
I already have Busybox installed and ticked option in adb insecure app so I will try to re-root my SM-T900 but I don't believe it'll work
It worked on Huawei Honor 6 L02 with root, busybox + adbinsecure. Thank you all for the tips.
Same issue in my side
I am using Xolo Q900 and installed MIUI custom rom for the device.
But When I connect android commander its showing no root access.
I have tried the Insecure ADB but it failed to patch. showed an error message "Patching not done"
Also showing USB debugging not enable but I have enabled it and its showing active in my phone.
When I am opening titanium backup in my phone Its showing I have root access. I have also installed new version of Busy Box but still no heal.
Can anybody help me on this?
It worked
After installing the ADB Insecure [http://forum.xda-developers.com/showthread.php?p=26885208] I can now see the Root status OK in Android Commander.
I was making mistake in the Permission Manager in MIUI rom. After allowing the ADB Insecure app from there I was able to patch.
Although You need to restart it again after exiting from the app or phone restart.
My device xolo q900
My moto G xt1031 is on lollipop 5.0.2 running stock. What i did was go to the binary file in AC. delete everything in it and then replace the adb file frome the most current version. Then i installed adb insecure on my phone. works great now.
As title.
I always rooted my gnex using an unsecure boot image.
Now I can boot with an unsecure boot image, I can push/chmod su, superuser and daemonsu using adb but than what should I do?
What should I do to root the phone?
Thanks.
sblantipodi said:
As title.
I always rooted my gnex using an unsecure boot image.
Now I can boot with an unsecure boot image, I can push/chmod su, superuser and daemonsu using adb but than what should I do?
What should I do to root the phone?
Thanks.
Click to expand...
Click to collapse
You can either flash the SuperSU .zip by Chainfire in a custom recovery or you can take the .zip apart and do it manually. Push all of the files in the .zip to the corresponding locations on your phone and look at the updater-script to see if you need to do any other commands. Root in 4.3 is different and Chainfire's method basically uses a script to enable it at every boot. I have not read about any other superusers working for 4.3, though I could have missed it.
mwalt2 said:
You can either flash the SuperSU .zip by Chainfire in a custom recovery or you can take the .zip apart and do it manually. Push all of the files in the .zip to the corresponding locations on your phone and look at the updater-script to see if you need to do any other commands. Root in 4.3 is different and Chainfire's method basically uses a script to enable it at every boot. I have not read about any other superusers working for 4.3, though I could have missed it.
Click to expand...
Click to collapse
is there a way to undo this process once done?
sblantipodi said:
is there a way to undo this process once done?
Click to expand...
Click to collapse
Naturally, backtrack your steps.
beekay201 said:
Naturally, backtrack your steps.
Click to expand...
Click to collapse
Can I safely remove all the files copied from the zip ?
sblantipodi said:
Can I safely remove all the files copied from the zip ?
Click to expand...
Click to collapse
Yes.. Restoring whatever in the process..if you modified anything that was there already.
Galaxy Nexus 4.3 NO ROOT w/ SuperSU_1.51.zip
Ok XDA - you're my only hope. I've completely lost root after flashing the last two PA releases. I just flashed the most recent (dirty), flashed GApps, rebooted, Flashed SuperSU_1.51/zip, Wiped Dalvik/cache in TWRP, rebooted, SuperSU says no binary installed, please manually root. Losing my mind here, need to get rooted again, could someone lend me some backup?
innerspace said:
Ok XDA - you're my only hope. I've completely lost root after flashing the last two PA releases. I just flashed the most recent (dirty), flashed GApps, rebooted, Flashed SuperSU_1.51/zip, Wiped Dalvik/cache in TWRP, rebooted, SuperSU says no binary installed, please manually root. Losing my mind here, need to get rooted again, could someone lend me some backup?
Click to expand...
Click to collapse
Did you manage to solve this problem?
I've got the same problem now...(There is no SU Library installed... This is a problem!)
Previously I had root but SU Library wouldn't update, ChainFire told me to re-root which caused me to lose root completely, tried again to root, without any luck.
Stuck without Root
AMKhatri said:
Did you manage to solve this problem?
I've got the same problem now...(There is no SU Library installed... This is a problem!)
Previously I had root but SU Library wouldn't update, ChainFire told me to re-root which caused me to lose root completely, tried again to root, without any luck.
Stuck without Root
Click to expand...
Click to collapse
download the most current supersu.zip and flash it in recovery.
if you're using a toolkit (i bet you are) STOP IT.
Zepius said:
download the most current supersu.zip and flash it in recovery.
about 2 minutes prior to your reply, I updated the "Toolkit" along with all the other items (supersu, img, etc..)
And after that, my device is rooted again.
Although, the main reason I started all of this was to update my device's build further, but it seems the OTA update is now gone... I'll have to wait for it appear again and see how it goes...
Zepius said:
I'll keep that in mind...
if you're using a toolkit (i bet you are) STOP IT.
Click to expand...
Click to collapse
Thanks for the reply!
Much appreciated!
Click to expand...
Click to collapse
AMKhatri said:
Did you manage to solve this problem?
I've got the same problem now...(There is no SU Library installed... This is a problem!)
Previously I had root but SU Library wouldn't update, ChainFire told me to re-root which caused me to lose root completely, tried again to root, without any luck.
Stuck without Root
Click to expand...
Click to collapse
I did, though I'm fuzzy on how exactly, and no, no toolkits here. IIRC I ended up wiping, updating recovery, and then manually flashing, but I had to do it multiple times to get root to stick. Sorry I don't have any better info to provide, glad to hear a) I wasn't the only one who experienced this problem, and b) you got your root back.
I installed a stock recovery to update to 4.4.4 OTA. I then installed TWRP(openrecovery-twrp-2.8.1.0-m8) through fastboot and attempted to install the super SU zip 2.00.
The file seemed to install properly as it gave me no errors, but I did not have root access when booting into the phone. I then tried CWM recovery (recovery-clockwork-6.0.4.8-m8). CWM installed the super SU 2.00 zip without any errors as well, but warned me before reboot that my root access was not found, I selected the option that "fixes" that, but still I am without root.
I like the 4.4.4 features but I don't want to be without root, please help me guys.
Let me know if you guys figure anything out for the stock rom. I just jumped on the latest cyanogenmod nighty till I figure this out.
Do you have s-off?
You should definitely get s-off as it makes everything so much easier.
But in the meantime, I would download the sunshine.apk and run it. It will reboot your phone and ask you to confirm and enter PayPal info. I believe your phone at this point has a soft root. If you now run superSU and allow it to install the binary, you should have root.
I've seen posts instructing how to root via SuperSu and Magisk; I know those methods have to be done a certain way because of the partition system. But I have not seen any posts about Kingroot. Would it work the successfully? I imagine it going like this:
1) root with Kingroot
2) boot to TWRP via ADB
3) flash TWRP
4) flash SuperSU if desired
Or
4) if desired, flash a kernel, flash Magisk, flash TWRP again
5) boot to system, uninstall Kingroot
Does that sound right? Would Kingroot even work to begin with?
GroovinChip said:
I've seen posts instructing how to root via SuperSu and Magisk; I know those methods have to be done a certain way because of the partition system. But I have not seen any posts about Kingroot. Would it work the successfully? I imagine it going like this:
1) root with Kingroot
2) boot to TWRP via ADB
3) flash TWRP
4) flash SuperSU if desired
Or
4) if desired, flash a kernel, flash Magisk, flash TWRP again
5) boot to system, uninstall Kingroot
Does that sound right? Would Kingroot even work to begin with?
Click to expand...
Click to collapse
Why use kingroot? Remove the first step and you basically have hot to flash su..
pcriz said:
Why use kingroot? Remove the first step and you basically have hot to flash su..
Click to expand...
Click to collapse
True, but if you happen to want to root while away from a computer it could be useful.
In any case, it was simply a curiosity about whether it would even work at all. I doubt I'd ever use Kingroot for my Pixel.
Sent from my Google Pixel XL using XDA Labs
GroovinChip said:
True, but if you happen to want to root while away from a computer it could be useful.
In any case, it was simply a curiosity about whether it would even work at all. I doubt I'd ever use Kingroot for my Pixel.
Click to expand...
Click to collapse
Oh okay. I was just curious. I haven't tried kingroot but since rooting requires patching the boot.img and I don't know if you can do that while booted into the OS I'd say no. I am only assuming how kingroot works but again whatever the solution it needs to be able to make changes to the boot.img without already having root privs.
The closest solution I would see is having twrp already loaded.
pcriz said:
Oh okay. I was just curious. I haven't tried kingroot but since rooting requires patching the boot.img and I don't know if you can do that while booted into the OS I'd say no. I am only assuming how kingroot works but again whatever the solution it needs to be able to make changes to the boot.img without already having root privs.
The closest solution I would see is having twrp already loaded.
Click to expand...
Click to collapse
This makes sense. Thanks
Sent from my Google Pixel XL using XDA Labs
Even if it did work it wouldn't work the way you are describing. King Root basically acts like malware and refuses to give root privileges to any app that interferes with its functioning. Adaway won't work with King Root because adware is part of the King Root program. You also wouldn't be able to install SU while King Root is on your phone. King Root will actively prevent you from installing any other root program. People used to be able to do what you describe but King Root was updated to prevent you from installing SU.
i tried to install SuperSu, including the sr5 version, and get caught in the google logo, plus ss will no longer be updated. after unlocking the bootloader, installing twrp are there any tips on installing magisk? i am also unsure on what flashing the "stock rom" is about. is that the oem, custom rom or either. i am mostly looking for the su function but root would be ok to. thanks
dr1445 said:
i tried to install SuperSu, including the sr5 version, and get caught in the google logo, plus ss will no longer be updated. after unlocking the bootloader, installing twrp are there any tips on installing magisk? i am also unsure on what flashing the "stock rom" is about. is that the oem, custom rom or either. i am mostly looking for the su function but root would be ok to. thanks
Click to expand...
Click to collapse
Your best bet would be to do some more reading "new one".... While your misunderstanding of the relation between root and su have me thinking that you are not ready to root yet. On a serious note, Magisk is a excellent alternative for SuperSu. Head over to the Magisk forums and read up for more info.
being a user not developer, i have no intention to modify software code, there for i do not require root. su is useful to run certain apps, like twrp manager to grant permissions. i like the linux sudo command better on my pc, but that is just one operators opinion and my not even be feasible on google firmware. i got into this with a nex 4 wanting to get onboard with ubuntu phone to ditch all the commercial and media bloat. since i had the nex 4 as a development phone why not try a custom rom and update to 7.1? after a few go rounds i got 14.1 installed. my adventures with the nex 5x and 6p and SuperSU both lead to a bricked phone, which i learned to get operational. basically nothing ventured nothing gained.
su is the command used to gain root access. If you've installed either SuperSU or Magisk you have rooted your device.
The current Magisk works well on the current Oreo image for the Nexus 5X. The bonus is that you can use apps that refuse to work if they think the device is rooted.
dr1445 said:
i tried to install SuperSu, including the sr5 version, and get caught in the google logo, plus ss will no longer be updated. after unlocking the bootloader, installing twrp are there any tips on installing magisk? i am also unsure on what flashing the "stock rom" is about. is that the oem, custom rom or either. i am mostly looking for the su function but root would be ok to. thanks
Click to expand...
Click to collapse
For me, stock 8.1, sr5 works. Stock rom is oem, but it doesn't have to be the whole oem, you can have a stock rom and twrp, so basically system and the kernel remain stock but recovery can be something other than stock, and so on...
Sent from my Nexus 5X using Tapatalk