i installed latest release of the democracy room and it have the application super user installed.
The problem is that the super user access window( allow or deny) doesn't appear.
In a terminal i write su and it stays there ( su window missing)
i downloaded supersu and it stays on "installing su binaries".
sorry for my english
Sent from my Ace
did you try erasing the data from the super user app? or maybe wipe (factory reset, cache, dalvik) and install rom again?
Are you sure that Superuser.apologize and the binary su have been chmodded to 755?
Sent from my GT-S5830 using Tapatalk 2
Related
Hi Guys, I was trying to make a clean install of Asylum CM9 but however while i was able to have full root(copy paste permission into system folder) on ginger bread, i wiped cache and factory reset, i was only able to gain partial root, i already done this twice but its showing the same results. help!
elijahtan said:
Hi Guys, I was trying to make a clean install of Asylum CM9 but however while i was able to have full root(copy paste permission into system folder) on ginger bread, i wiped cache and factory reset, i was only able to gain partial root, i already done this twice but its showing the same results. help!
Click to expand...
Click to collapse
Did you tty asking this on the rom's thread? It may be a known bug of this rom. I'm now on paranoid and also tried cm9 and don't have this problem.
Hope this helps...
Sent from my GT-N7000 using Tapatalk 2
elijahtan said:
Hi Guys, I was trying to make a clean install of Asylum CM9 but however while i was able to have full root(copy paste permission into system folder) on ginger bread, i wiped cache and factory reset, i was only able to gain partial root, i already done this twice but its showing the same results. help!
Click to expand...
Click to collapse
did you wipe dalvik cache?
do post this in the rom's thread.
I did... sorry for posting it over here because as I have flashed other ROM, i have always faced the partial root issue, i do not think it is rom specific as I have gone onto kingdroid, criskelo and alba and all faced the same issue before...
EDIT: I realised something very perculiar, I used ES explorer and Root Browser lite...they didnt seem to ask for superSU permission like they did in GB rom.... that could be the reason?? bt I have no idea why they dont prompt as such
elijahtan said:
I did... sorry for posting it over here because as I have flashed other ROM, i have always faced the partial root issue, i do not think it is rom specific as I have gone onto kingdroid, criskelo and alba and all faced the same issue before...
EDIT: I realised something very perculiar, I used ES explorer and Root Browser lite...they didnt seem to ask for superSU permission like they did in GB rom.... that could be the reason?? bt I have no idea why they dont prompt as such
Click to expand...
Click to collapse
Check in the Superuser app for settings regarding prompt messages. Maybe sone option is selected there!
Sent from my GT-N7000 using Tapatalk 2
I am facing the exact same problem, no matter what I try I can't get rw on /system
$ adb remount
remount failed: Read-only file system
[email protected]:/ # mount -o rw,remount /system
[email protected]:/ # mount
rootfs on / type rootfs (rw,relatime)
...
/dev/block/mmcblk0p9 on /system type ext4 (ro,relatime,barrier=0,data=ordered)
Any help will be appreciated. Currently on TMT 1.3 with CF-Root kernel, Mobile ODIN Pro works fine and SuperSU shows all apps getting root, but /system is stuck in ro
Try using rom toolbox and it has root browser embedded
Sent from my GT-N7000 using XDA
Hello,
I'm trying to reinstall BusyBox on a Stock rom in a GT-S5830C but I get this error when using BusyBox Installer for any version of BusyBox:
reloc_library[1312]: 7993 cannot locate 'android_reboot'...
CANNOT LINK EXECUTABLE
Click to expand...
Click to collapse
I've already installed BusyBox once using another BusyBox app, but that app is very slow and it seems it is not working properly (BusyBox by Stephen). I'm trying to apply the modifications that enable init.d in a Stock rom (http://forum.xda-developers.com/showthread.php?t=1422061&page=2), and BusyBox is a important part of it, it looks like no busybox command is working.
Sorry for bad english,
Thanks for reading!
It looks like I fixed, removed BusyBox Installer by Stephen, unrooted and rooted phone again (recovery mode), cleaned cache partition (recovery mode), fixed permissions (CWM recovery), installed BusyBox Installer by Stephen again, installed BusyBox with success.
I have the same problem
eumax said:
It looks like I fixed, removed BusyBox Installer by Stephen, unrooted and rooted phone again (recovery mode), cleaned cache partition (recovery mode), fixed permissions (CWM recovery), installed BusyBox Installer by Stephen again, installed BusyBox with success.
Click to expand...
Click to collapse
I have the same problem code 1312, 2739. I currently have busybox installed in system/xbin. But I allowed a smart install. After experiencing the downloading of the new busybox installer. Tried to update busybox. It said it is not compatible with my version 1.20.2 ? Relly don't want to go the unroot and root course. Maybe a simpler way. Sorry if I put this request in the wrong place. Thanks
wally18324 said:
I have the same problem code 1312, 2739. I currently have busybox installed in system/xbin. But I allowed a smart install. After experiencing the downloading of the new busybox installer. Tried to update busybox. It said it is not compatible with my version 1.20.2 ? Relly don't want to go the unroot and root course. Maybe a simpler way. Sorry if I put this request in the wrong place. Thanks
Click to expand...
Click to collapse
Put the busybox binary in either system/bin or system/xbin using root explorer. Set correct permissions. Then uninstall busybox installer.
Reboot into cwm and do a fix permissions. This should help, but if it doesn't, you can always go the unroot thing..
___________XDA Premium__________
Don't be a noob. Be a newbie..!!
Details here.
____________________________________
I have a Rooted HTC Vivid running Android 4.0.3, HTC Sense 3.6, ROM 3.26.502.56, Software Holics-1.2, Kernel Version 3.0.38_Holics_0730:
I'm in a poor ATT cell area and have to put the phone in a specific spot on top of a shelf and talk via BT at my desk. When using the phone as a phone without BT, the other party hears garble. I can use a wired ear/mic but I am chained to the shelf. Last week the BT just would not turn on at all. I've researched, rebooted, even factory booted but the BT function tries to turn on and just goes back to the off position.
Any suggestions would be highly appreciated as I am without reasonable phone commo without a BT.
Have you tried wiping all of the partitions using recovery. Or use the Superwipe script found in the devolpment section after try flash the rom of your choice and it should work.
Sent from my HTC Velocity 4G using Tapatalk 4 beta
HTC Vivid Rooted - Bluetooth Quit Working
WildfireDEV said:
Have you tried wiping all of the partitions using recovery. Or use the Superwipe script found in the devolpment section after try flash the rom of your choice and it should work.
----------
Thank you. I have used recovery last time. Now when I try to go to SuperSU it shows:
1) "The SU binary needs to be updated. Continue?"
2) *Continue (entered)
3) "If you have a custom recovery like TWRP or CWM, that can be used to (try to) install the SU binary. This is recommended for HTC devices. How would you like to install the SU binary?
4) *TWRP/CWM
5) "SuperSU will attempt to reboot your device into TWRP or CWM. This does not work on all devices. IF this app just closes, please reboot into recovery manually."
6) *OK
7) "Shutting down"
8) Restarts into:
"- reboot system now
- Install zip from sdcard
- wipe data/factory reset
- wipe cache partition
- backup and restore
- mounts and storage
- advanced
- go back"
9) * wipe cache partition
10) "Are you sure? This can not be undone"
11) * wipe cache partition
12) * reboot system now
13) * Turn bluetooth on
14) + Doesn't turn on as before.
Any ideas would be greatly appreciated.
Click to expand...
Click to collapse
dbcdn said:
WildfireDEV said:
Have you tried wiping all of the partitions using recovery. Or use the Superwipe script found in the devolpment section after try flash the rom of your choice and it should work.
----------
Thank you. I have used recovery last time. Now when I try to go to SuperSU it shows:
1) "The SU binary needs to be updated. Continue?"
2) *Continue (entered)
3) "If you have a custom recovery like TWRP or CWM, that can be used to (try to) install the SU binary. This is recommended for HTC devices. How would you like to install the SU binary?
4) *TWRP/CWM
5) "SuperSU will attempt to reboot your device into TWRP or CWM. This does not work on all devices. IF this app just closes, please reboot into recovery manually."
6) *OK
7) "Shutting down"
8) Restarts into:
"- reboot system now
- Install zip from sdcard
- wipe data/factory reset
- wipe cache partition
- backup and restore
- mounts and storage
- advanced
- go back"
9) * wipe cache partition
10) "Are you sure? This can not be undone"
11) * wipe cache partition
12) * reboot system now
13) * Turn bluetooth on
14) + Doesn't turn on as before.
Any ideas would be greatly appreciated.
Click to expand...
Click to collapse
So do you mean that after updating the Su binary your Bluetooth stopped working.
Sent from my HTC Velocity 4G using Tapatalk 4 beta
Click to expand...
Click to collapse
WildfireDEV said:
dbcdn said:
So do you mean that after updating the Su binary your Bluetooth stopped working.
Sent from my HTC Velocity 4G using Tapatalk 4 beta
Click to expand...
Click to collapse
No, I reset because the Bluetooth stopped working. Thanks.
Click to expand...
Click to collapse
Just flashed Sinless ROM and although it came with SuperSU by chainfire. I decided I wanted to remove it and install superuser by clockworkmod instead. For some reason superuser app didn't actually root the system, so I attempted to uninstall it and reinstall SuperSU. This is where I'm stuck. I cannot remove superuser app no matter what I try, even deleting it with a file manager or disabling the app. Anyone have any ideas? Really need my root back. Thanks
One Hype said:
Just flashed Sinless ROM and although it came with SuperSU by chainfire. I decided I wanted to remove it and install superuser by clockworkmod instead. For some reason superuser app didn't actually root the system, so I attempted to uninstall it and reinstall SuperSU. This is where I'm stuck. I cannot remove superuser app no matter what I try, even deleting it with a file manager or disabling the app. Anyone have any ideas? Really need my root back. Thanks
Click to expand...
Click to collapse
If it's in /system, you need root to remove it (which you don't have). I suggest going into recovery and then flashing Superuser with the SU binaries that allows root to work.
Link to ClockworkMod's Superuser: http://download.clockworkmod.com/superuser/superuser.zip
KiraYahiroz said:
If it's in /system, you need root to remove it (which you don't have). I suggest going into recovery and then flashing Superuser with the SU binaries that allows root to work.
Link to ClockworkMod's Superuser: http://download.clockworkmod.com/superuser/superuser.zip
Click to expand...
Click to collapse
Tried this and that is what I am attempting to remove from the system to no avail. Anything else I can try? I don't know why it won't give superuser access either.
One Hype said:
Tried this and that is what I am attempting to remove from the system to no avail. Anything else I can try? I don't know why it won't give superuser access either.
Click to expand...
Click to collapse
So flashing that zip didn't flash the SU binaries either?
Try flashing this then: http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
The main important thing is to get the SU binaries installed to allow the superuser apps to work. Once you have that installed try to change superuser apps again (do not choose the full remove option as that will also remove the SU binaries).
Another option is to try flash the ROM again.
KiraYahiroz said:
So flashing that zip didn't flash the SU binaries either?
Try flashing this then: http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
The main important thing is to get the SU binaries installed to allow the superuser apps to work. Once you have that installed try to change superuser apps again (do not choose the full remove option as that will also remove the SU binaries).
Another option is to try flash the ROM again.
Click to expand...
Click to collapse
Just did this buy with v.1.8 of SuperSU and everything worked perfect. Thank you
This is my installation process [last post summary]
https://forum.xda-developers.com/gal...ageos-t3576865
Downloaded lineage-14.1-20170322-nightly-klte-signed.zip
flashed this ROM with TWRP
rooted with CF-Auto-Root - same problem
downloaded again addonsu-ARM-signed_14.1
flashed this ROM again with TWRP
cleaning Dalvik and cache [kind of never done it before here]
rooted with addonsu-ARM-signed_14.1
all works
PS after flashing 20170322 ROM, on the first run I almost sh*at myself as SD card was not recognized. Restarted and was OK.
CATLOG screenshot
https://dl.xda-developers.com/4/1/0....jpg?key=J9F9olpmOpltDNbjtBwaxQ&ts=1491479200
If I try to update binaries in TWRP, it stops, restarts and stops during Lineage loading screen forever. [nothing in TWRP logs about SU I can see]
So I flash ROM again, and addonsu-ARM-signed_14.1 from TWRP to fix it.
I was reading that after flashing addonsu-ARM-signed_14.1 - during first restart it should ask me something like "DO you want to keep root" - it doesn't happen.
Is there a way to have it done?
Is it sometimes necessary to set permissions in Terminal for some SU files/folders before updating binary? I think ages ago I was doing something like this...?
Is it possible that
1. flash ROM
2. root fith CF root
3. dirty flashROM
4. use correct root addonsu-ARM
can have anything to do?
SM-G900F
lineage-14.1-20170329-nightly-klte-signed.zip
lineage-14.1-20170405-nightly-klte-signed.zip
addonsu-ARM-signed_14.1
The link for your install process, gives an XDA 404 page loading error.
One question though with SuperSU settings. Do you have it set to allow SU to run during boot? Maybe that's why it seems to take forever to load after updating binaries through TWRP?
Sent from my SM-G930P using Tapatalk