Related
Ok so some background, I am running the newest molten and enjoying it thouroughly but just noticed that when i open terminal emulator and type SU to get root access in the terminal it says permission denied and most other commands return same error, i downloaded a differant terminal emulator that checks for the su.bin and it shows no su binary is installed yet when i goto the directory system/bin/ in es file explorer su is indeed there?
Could someone please tell me why none of the terminal emulators are finding the superuser binary? I ve already tried opening superuser app and updating the su binary (it did update and i rebooted after) but it hasnt helped, I also read on other forums that there are multiple su binaries on some phones? could this be the problem and if so where would i find the right binaries?
It just seams odd that terminal emulator would be included in the build if it is completly unusable
su then hit enter
lol, thanks, im not the smartest with linux commands but i know to hit enter.
I tried typing su and hitting enter in 3 differant terminal emulators but keep getting permission denied in all of them
You should get a super user request once you hit enter. Maybe permission was already denied. Try clearing defaults for su.
Sent from my DROID X2 using xda premium
Did you recent apply the 2.3.5 update? When I went from rooted 234 to 235 I lost root privileges even though the superuser app was still there.
Could be your root isnt quite right. What setup do you have. Also try going into your superuser application and see if they are on the not allowed list.
Also should go from a "$" to a "#" sign after you hit enter if su took.
thanks for the ideas, that really narrowed it down, i cleared data for superuser and terminal, reinstalled terminal, still didnt work.....then i realised im a idiot, my keyboards autocap was on and su has to be "su" not "SU"
lol well thanks again for all the help
brilock42 said:
thanks for the ideas, that really narrowed it down, i cleared data for superuser and terminal, reinstalled terminal, still didnt work.....then i realised im a idiot, my keyboards autocap was on and su has to be "su" not "SU"
lol well thanks again for all the help
Click to expand...
Click to collapse
If it is solved then put (solved) in the OP subject line and list what fixed it for you. It can help future users
Pesky case sensitive terminal
Sent from my DROID X2 using xda premium
No SU in SSH
su did not work here as I did use a bad SSH-app.
I now use sshdroid
So I bricked my Kinde Fire HDX by changing the build.prop and not fixing permissions. I have adb access but no root (I don't know why :S). Would a factory reset work? If not, how can I get to fix the build.prop or replace it with the old one? thank very much, I've been a couple hours looking for solution but I couldn't find any.
No, a factory reset would only break it further. It would remove your adb access and not fix anything. What makes you think you lost root? Have you tried "adb shell" then "su"?
Sent from my Amazon Tate using Tapatalk
r3pwn said:
No, a factory reset would only break it further. It would remove your adb access and not fix anything. What makes you think you lost root? Have you tried "adb shell" then "su"?
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
I used the HDX ToolKit v0.92 to check the root access, and it said "Please grant root on your device"
I've also tried "adb shell", and then "su", but it just returns "su" again. I am new with adb commands so I don't really know what it should show.
Thank you very much for your help
May I ask what version you were on before you bricked?
Sent from my Amazon Tate using Tapatalk
14.3.2.3.2, last update I think.
?
peter_b93 said:
14.3.2.3.2, last update I think.
Click to expand...
Click to collapse
Fixed?
jimyv said:
Fixed?
Click to expand...
Click to collapse
Nope, I couldn't find any way to get root acces again. But nevermind, my new kindle fire will be here in two days. I am surprised how well amazon costumer service works. Even though I bought my kindle in the US and now I am in Spain (not going back), they called me from the US for free, and they are paying all the shipping costs and sending it by priority shipping.
I am still interested if anyone knows how to fix it, just for fun
well
peter_b93 said:
Nope, I couldn't find any way to get root acces again. But nevermind, my new kindle fire will be here in two days. I am surprised how well amazon costumer service works. Even though I bought my kindle in the US and now I am in Spain (not going back), they called me from the US for free, and they are paying all the shipping costs and sending it by priority shipping.
I am still interested if anyone knows how to fix it, just for fun
Click to expand...
Click to collapse
It sounds like to me that you still root access you just were not mounted RW in other words it would not boot up completely so you could hit allow to the adb Shell. So you will have to mount system rw manually Try last 3 pages of this thread http://forum.xda-developers.com/showthread.php?t=2588608. He can fix you most likely if you can comprehend and follow directions.. or if ur understanding adb is fair you'll be able to probably extract your repair from the thread as is.
jimyv said:
It sounds like to me that you still root access you just were not mounted RW in other words it would not boot up completely so you could hit allow to the adb Shell. So you will have to mount system rw manually Try last 3 pages of this thread http://forum.xda-developers.com/showthread.php?t=2588608. He can fix you most likely if you can comprehend and follow directions.. or if ur understanding adb is fair you'll be able to probably extract your repair from the thread as is.
Click to expand...
Click to collapse
I've tried what it is said in the other thread. However, the problem there is that the guy cannot get his device to be recognized.
I've tried this:
adb root
adb shell
su
mount -o rw,remount /system *****- if this fails, try: mount -o remount /system
chmod 644 /system/build.prop
chown root.root /system/build.prop
reboot
But adb root gives me this error:
adbd cannot run as root in production builds
On the other hand if I skip the "adb root" step I cannot go further than "su" since I don't get the "[email protected]:/ #" line.
well
peter_b93 said:
I've tried what it is said in the other thread. However, the problem there is that the guy cannot get his device to be recognized.
I've tried this:
adb root
adb shell
su
mount -o rw,remount /system *****- if this fails, try: mount -o remount /system
chmod 644 /system/build.prop
chown root.root /system/build.prop
reboot
But adb root gives me this error:
adbd cannot run as root in production builds
On the other hand if I skip the "adb root" step I cannot go further than "su" since I don't get the "[email protected]:/ #" line.
Click to expand...
Click to collapse
Well since you do have ADB connectivity why can't you hook a bruting utility and push root ? Romaster_3.4.3.7593_Setup use as describe back in the roll back thread and the rooting thread 4 the new yes I kno wat is in chinese but this is the 1 that you must use sent you cannot install the apk install software plugin your tablet look at the upper right corner you will see an gear icon tap that then second row down second icon over "root"
jimyv said:
Well since you do have ADB connectivity why can't you hook a bruting utility and push root ? Romaster_3.4.3.7593_Setup use as describe back in the roll back thread and the rooting thread 4 the new yes I kno wat is in chinese but this is the 1 that you must use sent you cannot install the apk install software plugin your tablet look at the upper right corner you will see an gear icon tap that then second row down second icon over "root"
Click to expand...
Click to collapse
FIXED!!!!!
The chinese software worked! Thank you very much! As I first rooted with towelroot I wasn't aware that it was possible to root without booting into android! I think I won't edit the build.prop again lol.
peter_b93 said:
FIXED!!!!!
The chinese software worked! Thank you very much! As I first rooted with towelroot I wasn't aware that it was possible to root without booting into android! I think I won't edit the build.prop again lol.
Click to expand...
Click to collapse
Ok now use this http://forum.xda-developers.com/showthread.php?t=2532818 and uninstall romanager from pc...and reboot... And BTW modifying your build prop is alot easier useing build prop editing app. It takes care of permissions anyway as long as you entrys are correct..
jimyv said:
Ok now use this http://forum.xda-developers.com/showthread.php?t=2532818 and uninstall romanager from pc...and reboot... And BTW modifying your build prop is alot easier useing build prop editing app. It takes care of permissions anyway as long as you entrys are correct..
Click to expand...
Click to collapse
Good call on RomMaster. I have no idea what it is doing since I haven't had any time to look at it, but I'd figured it was an app like TR. At any rate, nicely done. :good:
sweet
GSLEON3 said:
Good call on RomMaster. I have no idea what it is doing since I haven't had any time to look at it, but I'd figured it was an app like TR. At any rate, nicely done. :good:
Click to expand...
Click to collapse
I'm not sure either that's why when I used it I was on a blacklisted unit and I kept the PC and the tablet and airplane mode at all times. Until I was certain I got all the files off of both before I let them go to Wi-Fi Chinese files that is.. But one thing I was very curious about is if you open that tool up the Chinese tool that is an you go to the same page you would hit the anchor to root to your device just below that it says fastboot I'm wondering if they have a fastboot working for also too bad nobody here know Chinese..
Hi guys,
I found a method to change System Status in Odin mode to 'Official/Samsung' that is very simple and only using the busybox application "devmem". Use this command in adb shell or terminal emulator. Just type it in, hit enter, and reboot. Bam.
Code:
devmem 0xF91CF8C 32 0xFF000000
This will change your status to Official and remove the padlock with 'Custom' on it. If you want 'Custom', replace FF with EE.
Immediately upon reboot, Odin mode and the device recognize the device as official.
The explanation is that this is from a small region of memory that stores what's known as DDI data. I don't know what that means yet, but some other information like the CC Mode flag and device name/product number are stored here. I'm still doing further research on what else resides here.
Enjoy.
Seem that "DDI" can be either:
A "MAC-e header parameter" as specified HERE.
Data Description Indicator (DDI):
The DDI field identifies the logical channel, MAC-d flow and size of the MAC-d
PDUs concatenated into the 3GPP associated MAC-es PDU. The mapping between the
DDI values and the logical channel ID, MAC-d flow and PDU size is provided by
higher layers. The length of the DDI field is 6 bits. When, due to the
quantization in the transport block sizes that can be supported, the size of the
data plus header is less than the TB size originally selected by the E-TFC
selection entity minus 6 bits, the DDI value [111111] shall be appended at the
end of the MAC-e header to indicate that there are no more MAC-es PDUs
concatenated into this MAC-e PDU. In any other case it will be understood that
another MAC-es PDU would not fit and it will therefore not be necessary to
reserve room in the transport block for this additional DDI field.
Click to expand...
Click to collapse
QVGA Display Driver IC (DDI) chip that incorporates QUALCOMM's Mobile Display Digital Interface (MDDI).
I'd vote its the second, as it also contain a good chunk of SRAM memory.
Couldn't get this to work. Anyone else have any luck?
coreydkoster said:
Couldn't get this to work. Anyone else have any luck?
Click to expand...
Click to collapse
What didn't work? Do you have busybox installed?
ryanbg said:
What didn't work? Do you have busybox installed?
Click to expand...
Click to collapse
I havent got it to work either. Though im guessing its only good til a reboot before it gets rewritten?
I thought I read in passing that syscope was the app that checked to see if the system was modified or not. I think it said if you get your phone to say official and freeze/uninstall syscope you won't have the padlock show up anymore.
Sent from my SM-N900V using XDA Premium HD app
Triangle away app gets rid of the padlock.
Sent from my SM-N900V using xda premium
Wanam Xposed module also can get rid of the custom status padlock also.
I get to here but not anywhere else. Am I on the right track.. If so what next?
Sent from my SM-N900V using XDA Free mobile app
---------- Post added at 06:52 AM ---------- Previous post was at 06:50 AM ----------
Sent from my SM-N900V using XDA Free mobile app
Hi
I have "blocked by cc mode" on my S7
I have TWRP installed which has a terminal. I can't use USB for anything
I try "busybox devmem..." But it comes back saying can't find /dev/mem. I'm guessing this is what's called. Do you know where I can download "mem" from please.
I need to bring my phone back to life. I can use the SD card to copy across.
Please help
Deansmithok said:
Hi
I have "blocked by cc mode" on my S7
I have TWRP installed which has a terminal. I can't use USB for anything
I try "busybox devmem..." But it comes back saying can't find /dev/mem. I'm guessing this is what's called. Do you know where I can download "mem" from please.
I need to bring my phone back to life. I can use the SD card to copy across.
Please help
Click to expand...
Click to collapse
Busybox is an app. It creates s series of links to commands that are typically available on a Linix (unix) system. Android kernel is linix based.
devmem is a command available in an adb shell or in terminal mode.
No idea if the hack still works or not.
If it does still work I am sure it would require root.
Sent from my SM-N900V using Tapatalk
donc113 said:
Busybox is an app. It creates s series of links to commands that are typically available on a Linix (unix) system. Android kernel is linix based.
devmem is a command available in an adb shell or in terminal mode.
No idea if the hack still works or not.
If it does still work I am sure it would require root.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Hi
I have root.
I have terminal and busybox, but the devmem command fails.
I can install anything on the phone using TWRP
I'll try your hack. I really hope it works. There is almost no other info on cc mode available.
Best regards
Deansmithok said:
Hi
I have root.
I have terminal and busybox, but the devmem command fails.
I can install anything on the phone using TWRP
I'll try your hack. I really hope it works. There is almost no other info on cc mode available.
Best regards
Click to expand...
Click to collapse
This is what I get running devmem
[email protected]:/ $ devmem
BusyBox v1.24.2-Stericson (2016-04-23 13:23
:09 EDT) multi-call binary.
Usage: devmem ADDRESS [WIDTH [VALUE]]
Read/write from physical address
ADDRESS Address to act upon
WIDTH Width (8/16/...)
VALUE Data to be written
1|[email protected]:/ $
To actually use it, you need to su first to get the # root prompt like this:
1|[email protected]:/ $ su
[email protected]:/ #
Then try the command /dev/mem isn't writeable by ordinary users
Sent from my SM-N900V using Tapatalk
Hi
Thanks for the "su" headup.
The problem is that I have so little installed on the phone now.
I need the dev/mem code
I even need the "su" code. At the moment it says "su not found".
So I need to install some zips. Can you suggest some for me please... I guess busybox would be one, do you know where I can get all the code for the "dev" folder please - which Zip is that?
Regards
Dean
Deansmithok said:
Hi
Thanks for the "su" headup.
The problem is that I have so little installed on the phone now.
I need the dev/mem code
I even need the "su" code. At the moment it says "su not found".
So I need to install some zips. Can you suggest some for me please... I guess busybox would be one, do you know where I can get all the code for the "dev" folder please - which Zip is that?
Regards
Dean
Click to expand...
Click to collapse
Both busybox and supersu are available in the playstore. /dev/mem is a file directory not a file, unless you are root, it's not acessible to you.
Sent from my SM-N900V using Tapatalk
donc113 said:
Both busybox and supersu are available in the playstore. /dev/mem is a file directory not a file, unless you are root, it's not acessible to you.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Hi
I have root. Thank God.
I don't have play store, but I can find the Zips and install them through TWRP.
Then I'll su and busybox that devmem command.
I'll let you know how it goes.
Regards
Deansmithok said:
Hi
I have root. Thank God.
I don't have play store, but I can find the Zips and install them through TWRP.
Then I'll su and busybox that devmem command.
I'll let you know how it goes.
Regards
Click to expand...
Click to collapse
How do you not have play store (Google Play)? They are not zips, they are apps.
Sent from my SM-N900V using Tapatalk
donc113 said:
How do you not have play store (Google Play)? They are not zips, they are apps.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Hi
I don't have the play store because I don't have android.
The apps need android, but my phone won't even boot. I have "custom rom blocked by cc mode"
Download is blocked by it too.
All I have left is TWRP in recovery mode.
Regards
I got adb shell to work. I connected to the phone...
[email protected]:/dev # ./su
[email protected]:/dev # ./mem
sh: ./mem: can't execute: Permission denied
126|[email protected]:/dev # busybox devmem
BusyBox v1.22.1 bionic (2016-08-25 18:25 -0400) multi-call binary.
Usage: devmem ADDRESS [WIDTH [VALUE]]
Read/write from physical address
ADDRESS Address to act upon
WIDTH Width (8/16/...)
VALUE Data to be written
1|[email protected]:/dev # busybox devmem 0xF91CF8C
Bus error
135|[email protected]:/dev #
Deansmithok said:
I got adb shell to work. I connected to the phone...
[email protected]:/dev # ./su
[email protected]:/dev # ./mem
sh: ./mem: can't execute: Permission denied
126|[email protected]:/dev # busybox devmem
BusyBox v1.22.1 bionic (2016-08-25 18:25 -0400) multi-call binary.
Usage: devmem ADDRESS [WIDTH [VALUE]]
Read/write from physical address
ADDRESS Address to act upon
WIDTH Width (8/16/...)
VALUE Data to be written
1|[email protected]:/dev # busybox devmem 0xF91CF8C
Bus error
135|[email protected]:/dev #
Click to expand...
Click to collapse
You just need devmem and the address. Not busybox devmem and the address.
The only thing I can suggest is that you use ODIN to flash back to whatever the latest stock ROM you were on and go through the rooting process all over again.
The bootloader won't allow you to boot with a non stock recovery unless you unlock the bootloader.
Sent from my SM-N900V using Tapatalk
Hi
I've installed CM10.2 (last update) (http://forum.xda-developers.com/showthread.php?t=2499796) on my Archos 80G9. It also runs the SDE firmware from Archos (http://forum.xda-developers.com/showthread.php?t=1653566). So far, so good, it runs quite nicely, all things concerned. Here's a screenshot to the system info: https://www.dropbox.com/s/0ri8n4jb6gyrfz7/Screenshot_2014-11-17-20-56-01.png?dl=0
Now I'm trying to install X-posed Framework, but this won't work. When I try, I get an error that tells me /system can't be mounted. (Screenshot: https://www.dropbox.com/s/ryaryqkie023sl4/Screenshot_2014-11-17-20-40-16.png?dl=0 )
When I take a look is ES3 if the folder is mounted, it looks like this: https://www.dropbox.com/s/4kwv0ja16qz52tq/Screenshot_2014-11-17-20-49-21.png?dl=0 . I can't tick the other boxes here, I get the message "sorry, operation failed" when I try.
I've already tried to use the "mount -o remount,rw /" command, to no avail...
I have no idea how I have to fix this problem and if it's even fixable.
Does anyone have any idea? Thanks in advance!
Same here...
No solution for that yet.
Before you type the mount command did you type "su" first (without the quotes)?
Just opening up terminal gives you regular user permissions which will not let you run the mount command. You need to become root/superuser first and that's what su does.
Yes I did ... Terminal emulator gives a notification that It's been granted superuser permission, but it still doesn 't Work.
Sent from my Ascend Y300 using XDA Free mobile app
Can you send a screenshot of the "mount" comand and response?
Did the prompt change from $ to #? What was the output of "mount"?
If terminal doesn't work try with superuser adb (allow superuser not only from applications, but from adb). Connect to the device with "adb shell" and issue this command.
Hi, thanks for your response. Here are two screenshots: the first is of the mount command in Terminal Emulator, the second of the same via abd shell. No results.
Very strange, since filesystem seems to be remounted rw Ok.
In fact, I've installed xposed some two days ago on 101g9/cm10.2, so this should work.
Let's try to sort it out.
1) What version of xposed do you try to install? I've used latest stable (2.6 IIRC).
2) Do you use "standard" installation mode in xposed settings (just under the popup window on your screenshot)?
3) Try to issue the following commands in shell after remounting "/" (terminal or adb - doesn't matter)
# touch /system/bin/mytest.tmp
# ls -la /system/bin/mytest.tmp
If the file is created Ok, then the filesystem is mounted read-write correctly.
You can delete this file afterwards with
# rm /system/bin/mytest.tmp
4) Did you grant permanent or one-time superuser permission for xposed? If one-time, try permanent: it can be so, that "cp" fails due to lack of superuser permission.
Bor-ka said:
Very strange, since filesystem seems to be remounted rw Ok.
In fact, I've installed xposed some two days ago on 101g9/cm10.2, so this should work.
Let's try to sort it out.
1) What version of xposed do you try to install? I've used latest stable (2.6 IIRC).
2) Do you use "standard" installation mode in xposed settings (just under the popup window on your screenshot)?
3) Try to issue the following commands in shell after remounting "/" (terminal or adb - doesn't matter)
# touch /system/bin/mytest.tmp
# ls -la /system/bin/mytest.tmp
If the file is created Ok, then the filesystem is mounted read-write correctly.
You can delete this file afterwards with
# rm /system/bin/mytest.tmp
4) Did you grant permanent or one-time superuser permission for xposed? If one-time, try permanent: it can be so, that "cp" fails due to lack of superuser permission.
Click to expand...
Click to collapse
1) I had 2.7 Experimental, so I uninstalled it and installed 2.6 Stable instead.
2) I do indeed use the "classical" option for installing Xposed.
3) Tried it, gave the following result: the file is created in /System/bin, so I guess /sytem is mounted okay. (see screenshots)
4) I use SuperSU, XPosed had root acces (see screenshot)
Seems to me /system is mounted fine, but Xposed just doesn't know it...
Ok.
The problem is with xposed, obviously.
For me, it complained that it can not remount /system (obviously), but then installed Ok.
So, what I would do
1) Check the filesystem mounts. May be, for some reason, you have /system mount (quite improbably, but nonetheless). Try in the terminal
# mount
It will show a list of all active mounts with the following format
[what is mounted] [where mounted] [blah-blah and stuff]
For example, from anothe device
/dev/block/platform/hi_mci.1/by-name/system /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
You can see that something is mounted at "/system" readonly ("ro" attribute)
2) Check if the /system/bin/app_process.orig already exists
# ls -la /system/bin/app_process.orig
3) Try to use logcat to obtain info. That is tricky
a) On the PC issue command "adb logcat > logcat.txt"
b) Start xposed installer, try to install, get an error
c) on PC press Ctrl-C
Bor-ka said:
Ok.
The problem is with xposed, obviously.
For me, it complained that it can not remount /system (obviously), but then installed Ok.
So, what I would do
1) Check the filesystem mounts. May be, for some reason, you have /system mount (quite improbably, but nonetheless). Try in the terminal
# mount
It will show a list of all active mounts with the following format
[what is mounted] [where mounted] [blah-blah and stuff]
For example, from anothe device
/dev/block/platform/hi_mci.1/by-name/system /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
You can see that something is mounted at "/system" readonly ("ro" attribute)
2) Check if the /system/bin/app_process.orig already exists
# ls -la /system/bin/app_process.orig
3) Try to use logcat to obtain info. That is tricky
a) On the PC issue command "adb logcat > logcat.txt"
b) Start xposed installer, try to install, get an error
c) on PC press Ctrl-C
Click to expand...
Click to collapse
Alright, did all of it.
1) Don't fully understand what is listed here, but in the first screenshot is the list of mounts.
2) Checked it, doesn't seem to exist, see second screenshot.
3) Logcat is attached.
Ok, it appears that I got the problem. Need a little time to think how to solve this.
The problem is rather technical. In newer androids supersu has isolated filesystem mounts for different processes.
It means that if you remount filesystem rw in one process, it (read-write-ness) is not accessible to the other process.
I have a little older cm10.2 build (for low-memory devices), perhaps, this was enforced later.
http://su.chainfire.eu/#how-mount (3.5)
So you're saying there's a good chance that if I install version 22_12_2013-13_29_20 (which i was planning anyway), instead of the latest one, the problem could be fixed?
Hmm, I installed the previous version of CM10.2, the problem seems to be persisting...
I noticed something today. I can create and remove files in /system using the emulator. I can't however do this using ES3 file explorer, even though it has root access. I was trying to edit the build.prop file, but it wouldn't let me save my changes.
I then tried to copy a file to /system in es3, this didn't work. Creating a tmp file using emulator did work. Seems I do have rw access to /system, but not with all apps...
I noticed something today. I can create and remove files in /system using the emulator. I can't however do this using ES3 file explorer, even though it has root access. I was trying to edit the build.prop file, but it wouldn't let me save my changes.
I then tried to copy a file to /system in es3, this didn't work. Creating a tmp file using emulator did work (permission denied). Seems I do have rw access to /system, but not with all apps...
Well, it seems like what I've said, filesystem mount encapsulation.
I've noticed one thing - you are using the standalone supersu application. And for me superuser mode is integrated in the system settings near the developer options. May be this is the case, internal superuser is patched already.
Alright, I'll uninstall superSU for now, give it a go with the built-in superuser app. I'll let you know!
Supersu application, theoretically, could have replaced libsuperuser and other stuff integrated in the CM.
So, if just uninstalling does not work, perhaps it will make sense to reinstall CM itself.
P.S. I have mixed feelings with CM. On the one hand it is definitely more fluid, than 3.* or 4.* stock ROMs. On the other hand deep sleep works, well, strange, and the tablet sometimes freezes in the sleep or turns off by itself.
Yes, I have enabled deep sleep, but the battery drains definitely faster in the sleep. For me it is essential, since I mostly use it as a amazon kindle / google books / pdf reader terminal. And most of the time it just sleeps.
Bor-ka said:
Supersu application, theoretically, could have replaced libsuperuser and other stuff integrated in the CM.
So, if just uninstalling does not work, perhaps it will make sense to reinstall CM itself..
Click to expand...
Click to collapse
Eureka! I re-installed CM, issued the mount-command i used earlier and installed X-posed! I used the built-in superuser app, no such problems as before. I did have to issue the mount-command, but that isn't a problem Is it normal I have to re-issue the mount-command each time I want to access /system rw?
Thanks a million! I can't believe it was something this trivial But I'm so glad it's solved, thanks!
Bor-ka said:
P.S. I have mixed feelings with CM. On the one hand it is definitely more fluid, than 3.* or 4.* stock ROMs. On the other hand deep sleep works, well, strange, and the tablet sometimes freezes in the sleep or turns off by itself.
Yes, I have enabled deep sleep, but the battery drains definitely faster in the sleep. For me it is essential, since I mostly use it as a amazon kindle / google books / pdf reader terminal. And most of the time it just sleeps.
Click to expand...
Click to collapse
I don't use the deepsleep-option. I do use Greenify to ensure certain apps (like Youtube or Chrome) aren't active in the background. Boot manager to be sure only essential apps boot in the first place. This seems to save me some battery life. Airplane mode as well.
I got this tablet from my dad because it was so slow he couldn't work with it. Even after factory reset, it very quickly became sluggish again. With CM, it feels like it's a new tablet. So no doubts about CM for me
I do have another issue: My pc won't show the tablet in explorer. I can access it via ADB, but I can't access the storage via explorer... I suppose I best start a new topic for that...
Glad the issue was solved. I wonder why the superuser application didn't work.. Deepsleep - it allowed the tablet to lose, say, 10-15% charge during a week sleep. Very handy if the tablet is used not often - really miss it.
Explorer connection - if I remeber correctly, you should go to settings -> storage (where the size of apps/pictures etc is shown). Then press the three dots in the upper right corner, select "usb computer connection" and select MTP.
P.S. I wonder also if CM12/Android 5.0 in the "development" section is worth a try...
Hi
I've unlocked and rooted my phone. Everything works fine, except one little thing. The system partition is still read-only.. I have tried "# mount -o rw,remount /system" in adb on computer and terminal on the phone, but I get an error saying that the operation is not permitted. I find this wery odd, because I have granted superuser permissions. Also, when i type the command "adb devices", there is an empty list. Any suggestions?
Also, I can't install busybox.. Getting an error saying it failed, if anyone know how to fix this too, i will be wery greatfull
Skanin said:
Hi
I've unlocked and rooted my phone. Everything works fine, except one little thing. The system partition is still read-only.. I have tried "# mount -o rw,remount /system" in adb on computer and terminal on the phone, but I get an error saying that the operation is not permitted. I find this wery odd, because I have granted superuser permissions. Also, when i type the command "adb devices", there is an empty list. Any suggestions?
Also, I can't install busybox.. Getting an error saying it failed, if anyone know how to fix this too, i will be wery greatfull
Click to expand...
Click to collapse
This is because of a protection called Sony RIC. You can find some solutions if you make a search.
pec0ra said:
This is because of a protection called Sony RIC. You can find some solutions if you make a search.
Click to expand...
Click to collapse
Okey, thanks