I have a Nexus 4, rooted, Franco kernel, and factory stock rom. Downloaded CyanogenMod mako build, extracted CM File Manager, installed the apk successfully, but am unable to access the advanced options in the settings menu - specifically access mode. Also tried reinstalling it by copying to /system/app, changing permissions rw -r -r, but the app's advanced options still remained inaccessible. When I first open up the app, SuperSU never prompts me to grant root access. I'm assuming it does that if I was able to change the access mode from safe to root.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 4 using Tapatalk 2
Your devices must have all the command listed at https://github.com/CyanogenMod/android_packages_apps_CMFileManager/tree/cm-10.1(property shell_required_commands). Otherwise, you shouldn't be able to access root functionality.
The link doesn't work, can you explain me what are the command required to enable the root mode? Thanks.
- sorry for my bad english -
Related
Today when trying to update the busybox binaries it failed. Whereupon I lost root and wifi stopped working and I couldn't root the device again.
I did factory reset/wipe to no avail (wifi still dead and couldn't reroot). Then I restocked using odin doing wipe again. After the restock wifi worked again but now I'm not able to root the device (I'm using the root.zip method from recovery). Superuser can't update the su binary and neither can SuperSU.
Any help with this dilemma (getting root back) would be appreciated. Thanks.
First uninstall the update of version 3.0 of superusers. In the handler for app not see more' the application but if you go in the menu you will notice it is still there, given that many ROM cook have a default. Then the total uninstall does not, you can do. Now download the package of the binaries and flash using Recovery http://www.mobilegeek.it/?dl_id=397 once finished initiated the device and download from the market the update to version 3.0 . Now open superuser /settings and select "Track on v3.0 " to update correctly the rails. If the process give you all the "OK" green vul say that everything is alright. If by some red writing reboot the device and try to reflash the rails ...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have been wondering how I can make good use of my C++ knowledge apart from developing kernels, so came up with this.
Presenting you with AndroidUtils, a menu driven interface for some ADB functions.
Features
Neat UI, with Serial and Name of device connected.
Reboot to Recovery, Bootloader or normal reboot.
Print kmsg, get last_kmsg.
Print/Dump logcat.
Screen Capture.
Screen Recording (for certain phones only).
Batch Installation of multiple Applications.
Settings interface to reset cache.
Download - AFH Mirror (Version 1.0)
How-to
Download and extract the zip.
Run android-utils.exe
Note
You need to have ADB set up properly.
kmsgs needs root to be dealt with, so root access to ADB must be granted.
Screen Recording need screenrecord binary to work properly. If its there, you are good to go, else don't try that.
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello, this is a simple process which will replace your default HTC emojis by the more common ones used on iOS.
I have tested it on Lollipop and Marshmallow, it works fine. I am not sure if it will work on Kitkat though.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You will need to have access to system partition and be able to modify it (write access).
This can be either achieved by - entering twrp recovery and using the file manager,
- also by using a root explorer on an S-OFF phone/or has custom kernel which enable write to system.
either way is fine, provided you know what you're doing.
Here are the steps into completing it:
1. browse to system/fonts/
2. rename hTC_ColorEmoji.ttf to hTC_ColorEmoji.bak
(that way, if you ever want to revert to stock emoji, all you will have to do is to delete the new one and rename this one back)
3. copy the iOS emoji from the zip to system/fonts/ and ensure permission is set to rw-r-r (644)
4. Reboot.
That's all! Enjoy the new emoji!
VERY IMPORTANT SET OUTPUT GAIN TO -8DB OR -10db or YOU WILL DAMAGE YOUR HEARING TURN ON ADVANCED UI MODE
YouTube app no longer works use the youtube mobile website or
if you follow this method you can get it to work temporarily by Uninstalling it and reinstalling it from Google play
You have to delete it on every boot and reinstall it
Requires root and bootloader unlock
delete sound alive first by booting to twrp and mounting all partitions and using in advanced options file manager and go to system priv app folder and find sound alive and delete whole folder
Then reboot
Then go to this thread and install kali nethunter using the tw lolipop directions
I installed Kali nethunter and it works
http://forum.xda-developers.com/verizon-galaxy-s5/general/installed-kali-nethunter-t3466507/page1
Then I used the unofficial version of v4a avaliable on Google play store
You can also use the official version but it has a couple less features
Sent from my SM-G900V using Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-G900V using Tapatalk
Before anything, I'm pretty bad with all these stuff, so if I'm doing a stupid mistake sorry about that
I was trying to install Island (by Oasisfeng) on my rooted Galaxy S7 (stock) as I needed something to replicate Secure Folder. My device has root access, and has Magisk Manager installed. However, apparently Samsung won't let me install it due to having custom OS (which is just TWRP I believe)
So, the setup guide for Island says I could manually install it like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ADB recognizes my device, however, I get an error while trying to create a user as well as trying to change the limit. I've looked up for a while, and found out that my ADB doesn't have root access, as I get "Permission denied" if I type "su". In addition, my command line shows a $ instead of #.
Now, I've also gone through forums to find a reason why this is the case. Obviously my USB debugging is enabled, I have rooted my phone, and in my Magisk Manager settings Superuser Access is set to "Apps and ADB", which I thought would be the fix for this but apparently not.
Am I missing a step or trying to do something meaningless?
Thanks in advance.