Solution: Maybe not the best one but I wiped /oem in TWRP and apps are gone
https://forum.xda-developers.com/z2-force/help/modifying-oem-partition-t3738313
How I can mount /oem directory that I can uninstall system apps from there? I have tried mount -o rw,remount /oem from terminal but it didn't worked. TWRP can't mount that too. When i try this adb command: "mount -o rw,remount /oem" I will get this error: '/dev/block/dm-0' is read-only
Phone is Moto G6 Plus and I have rooted it with Magisk.
What apps are you trying to remove that aren't in system?
Sent from my moto g(6) plus using Tapatalk
Xplorer4x4 said:
What apps are you trying to remove that aren't in system?
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
LinkedIn, Rebublic Wireless and Prip that are located in /oem/app
Also Outlook app that is located in /oem/priv-app
All System app uninstaller apps (like Titanium Backup) can only delete apps in /system directory.
Personally I feel disable app is good enough for me. It's not exactly what you are looking for, but it's fix the problem, more or less.
VarunAgw said:
Personally I feel disable app is good enough for me. It's not exactly what you are looking for, but it's fix the problem, more or less.
Click to expand...
Click to collapse
I understand. I have disabled now Outlook etc. apps. But disabling won't remove bloatware. It's still here but hidden.
I have searched multiple times for how to mount /oem but all the guides just explains how to mount /system. It's ridiculous that I have root access but I can't still mount /oem
I'm not expert so you can ignore my reply. But have you tried mounting it in TWRP. Also are you sure it's installed in oem partition?
VarunAgw said:
I'm not expert so you can ignore my reply. But have you tried mounting it in TWRP
Click to expand...
Click to collapse
I can mount /oem in TWRP. After that I can also go to TWRP File Manager and delete needed files from there. But when I reboot phone the apps are still there and the files wasn't deleted. So TWRP does not seem to work.
VarunAgw said:
Also are you sure it's installed in oem partition?
Click to expand...
Click to collapse
Yes, they are installed in /oem. I used Apk Analyzer app to double check that https://play.google.com/store/apps/details?id=sk.styk.martin.apkanalyzer
Related
Here are the App and Framework system files for 4.1.57 fully deodexed.
You must already have Root access in 4.1.57.
Typical disclaimer as always...
USE AT YOUR OWN RISK.
This is for experienced users only please.
Remember to make a backup of your existing framework and app folders BEFORE you do this.
Link: Atrix-1.57deodexed IGNORE the instructions in the zip. Updated ones below.
Feel free to mirror.
Note: Photoedit.apk was pulled form the 1.26 Adeo file as the 1.57 version would not deodex properly.
This file did not change from 1.26. to 1.57, so I see no issue with using it.
UPDATE: The instructions contained in the zip have an error... oops.
This is why I don't write scripts. I type to fast.
Hopefully some of you guys caught that before entering the commands.
Again, backup your original system/framework and system/app files BEFORE you do this in case you want to revert back to an odexed system.
Here is the correction:
Put your phone in USB Mass Storage Device mode.
Copy the app and framework directory and their contents from the zip file to the root of your sdcard.
***Verify the copy was successful before you continue.***
Set USB mode back to None.
Type the following commands via ADB.
Code:
adb shell
su
stop
mount -o rw,remount /dev/block/mmcblk0p12 /system
cp /sdcard/app/* /system/app/
cp /sdcard/framework/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount /dev/block/mmcblk0p12 /system
reboot
Thanks, you beat me to it!
lindsaytheflint said:
Thanks, you beat me to it!
Click to expand...
Click to collapse
I deodexed them last night, but wanted to run through some testing before I packaged them up.
Anyone feel like scripting this, go for it.
I must have done something wrong in shell... soft brick, certain it was my fault.
tl_bull said:
I must have done something wrong in shell... soft brick, certain it was my fault.
Click to expand...
Click to collapse
Not your fault... I found an error in my instructions.
cp /sdcard/frame/* /system/framework/
should be
cp /sdcard/framework/* /system/framework/
rjohnstone said:
Here are the App and Framework system files for 4.1.57 fully deodexed.
Typical disclaimer as always...
USE AT YOUR OWN RISK.
This is for experienced users only please.
Link: Atrix-1.57deodexed IGNORE the instructions in the zip. Updated ones below.
Feel free to mirror.
Note: Photoedit.apk was pulled form the 1.26 Adeo file as the 1.57 version would not deodex properly.
This file did not change from 1.26. to 1.57, so I see no issue with using it.
Been running all day with these files with no issues.
UPDATE: The instructions contained in the zip have an error... oops.
This is why I don't write scripts. I type to fast.
Hopefully some of you guys caught that before entering the commands.
Here is the correction.
Copy the app and framework directory to the root of your sdcard.
Type the following commands via ADB.
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/app/* /system/app/
cp /sdcard/framework/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
Click to expand...
Click to collapse
Another error with the commands
it should be the following for the mounts command:
mount -o rw,remount /dev/block/mmcblk0p12 /system
mount -o ro,remount /dev/block/mmcblk0p12 /system
lpsi2000 said:
Another error with the commands
it should be the following for the mounts command:
mount -o rw,remount /dev/block/mmcblk0p12 /system
mount -o ro,remount /dev/block/mmcblk0p12 /system
Click to expand...
Click to collapse
Thx. Updated OP.
The mount commands I originally posted did work for me without any issue though.
Sent from my MB860 using XDA App
It looks like this isn't complete. There are some files in framework that you did not deodex, installing this on any phone will very likely brick.
Ririal said:
It looks like this isn't complete. There are some files in framework that you did not deodex, installing this on any phone will very likely brick.
Click to expand...
Click to collapse
What is missing?
Running on mine without any issues at all.
EDIT:
I see what you're talking about and it's a non-issue if you follow the commands to load them.
The 4 files missing from the framework folder were not odexed to begin with, so the originals will remain.
Remember, I'm not having anyone delete the entire contents of the framework folder, only the .odex files AFTER they copy over the deodexed versions first.
rm /system/framework/*.odex
These files are not odexed to begin with, so they are not touched.
blur-res.apk
framework-res.apk
moto-res.apk
android.test.runner.jar
You will also notice that 19 files are missing from the app folder as well... again, I'm not deleting any .apk files in the instructions, only the .odex files.
The 19 .apk files that are not included in my zip file are already present on a 1.57 system in a deodexed state.
I saw no point in adding them.
Make sense now?
Sent from my MB860 using XDA App
I followed every step however when I attempt to run the following command
mount -o rw,remount /dev/block/mmcblk0p12 /system
I'm receiving Permission denied.
Edit:
Had to use usb port on the rear instead of the front when rooting.
zeyoner said:
I followed every step however when I attempt to run the following command
mount -o rw,remount /dev/block/mmcblk0p12 /system
I'm receiving Permission denied.
Click to expand...
Click to collapse
Sounds like you don't have root access.
Do you see a $ or a # in your command prompt?
i have $ in my root access... i'm getting permission denied at when i type 'su' but im pretty sure i rooted it earlier today
edit fixed i wasnt rooted
rjohnstone said:
What is missing?
Running on mine without any issues at all.
EDIT:
I see what you're talking about and it's a non-issue if you follow the commands to load them.
The 4 files missing from the framework folder were not odexed to begin with, so the originals will remain.
Remember, I'm not having anyone delete the entire contents of the framework folder, only the .odex files AFTER they copy over the deodexed versions first.
rm /system/framework/*.odex
These files are not odexed to begin with, so they are not touched.
blur-res.apk
framework-res.apk
moto-res.apk
android.test.runner.jar
You will also notice that 19 files are missing from the app folder as well... again, I'm not deleting any .apk files in the instructions, only the .odex files.
The 19 .apk files that are not included in my zip file are already present on a 1.57 system in a deodexed state.
I saw no point in adding them.
Make sense now?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Yeah I looked it over again, should be fine.
EDIT: Nvm saw you updated.
I'm working on a new method to automate this, I'll post something when I have it working reliably.
looking for another way
Question, possibly a dumb one but anyway it is. . . I couldn't get the script for root on update to work so if I go this route is it the same as getting from moto and is it possible to still have root with it?
Very nice contribution!
Rad ryan said:
Question, possibly a dumb one but anyway it is. . . I couldn't get the script for root on update to work so if I go this route is it the same as getting from moto and is it possible to still have root with it?
Click to expand...
Click to collapse
This won't work without having root access first.
Sent from my MB860 using XDA App
I am still on 4.1.26 rooted and deodexed. Do I have to update my phone to 4.1.57 before copying the framework and apps folder? I know the script in OP won't work in my case but I can come up with another script. Thanks.
Immix said:
I am still on 4.1.26 rooted and deodexed. Do I have to update my phone to 4.1.57 before copying the framework and apps folder? I know the script in OP won't work in my case but I can come up with another script. Thanks.
Click to expand...
Click to collapse
Right - this is only for 4.1.57. If you do it on 4.1.26 you'll get a soft brick.
rjohnstone, its always best to do stuff like this under Early USB Enumeration mode. It is possible to get it to stop the automatic rebooting by typing "stop" into the console.
shawnbuck said:
Right - this is only for 4.1.57. If you do it on 4.1.26 you'll get a soft brick.
rjohnstone, its always best to do stuff like this under Early USB Enumeration mode. It is possible to get it to stop the automatic rebooting by typing "stop" into the console.
Click to expand...
Click to collapse
Thx for the tip.
I did use the stop command in my process and was able to prevent a reboot.
The process is so quick that I didn't see a single FC during the copy.
I think it should be mentioned in the OP that root is required.
Hi,
I get through this with my eye's closed but when I have to type in the chmod line,and hit enter, it says, "unable to chmod : / Read-Only file system / I've asked this on many different forms, and researched it and tried a lot of code to fix it, none of witch worked, so now I'm just asking strait out if anyone knows how I can fix this, It's done this on 2 separate computers so It's doubtful that it's a PC problem.
Thanks for reading this and perhaps helping me, I'm about to rip my hair out, lol,
Kn0t
Wait what?
So it's rooted tab yeah and your? Terminal or abd? Into the system. So you have super user rights huh? And the system files are mounted as read/write? If you said yes to these questioned which I assume you will as it sounds like you are savvy with permissions and how android mounts its system files from the "eyes closed" part then its a new one on me, I have never heard of this problem?
Oh and what kernel you running? is it gingerbread or froyo?
Sent from my GT-P1000
Don't forget to grant superuser its permissions. Check if the app is asking for it. Perform adb with tab on, superuser will pop up.
I felt for that couple of times.
Anyway use root explorer navigate into //system/ and there will be a button on the top to mount the system read/write. Then long press your file and select the permissions you want. Hit the same. Button as before to remount as read only and your away..
Sent from my GT-P1000
speldenaar said:
Don't forget to grant superuser its permissions. Check if the app is asking for it.
I felt for that couple of times.
Click to expand...
Click to collapse
No having super user rights doesn't mean you can write or change system files per say.. you first need the system mounted read/write which as a super user you do have the rights to....
So yes su is important but I suspect the issue here is the way the system is mounted...
Sent from my GT-P1000
And lastly I'm thinking this doesn't qualify to be in the development section bud .. its a little cause and general and should be in General section not Here.
Sorry but its out of control on these boards.... these threads shouldn't be in the development section unless you are developing something or are replying to a development thread about, well.... a development ... or finally, ahhhhh....ummm, bah... development... just had to say it one more time and couldn't get a third reason... I don't want to be harsh or you think I'm flaming you its just my 2 cents....
Sent from my GT-P1000
You're trying to write data to a partition mounted as read only.
To mount the system partition so you can write to it, simple issue this command:
mount -o remount,rw /dev/block/mtdblock3 /system
And of course to mount it back to read only again:
mount -o remount,ro /dev/block/mtdblock3 /system
i have a SGH-T849..
i want to carrier unlock it.. also i couldn't find the dialer & the messaging application in the phone.. so wanted to know how to make voice calls & send messages in it??
Sorry for the bad English & for being a noob
it's adb,, and I have super permissions, yes and it says it's a Read-only file system when I go to write my chmod. The "eye's closed" part of my post was just me being sarcastic about the amount of phones I've done this too and the amount of time I've done it with zero problems.. that's all.
Yup, I did that.. thanks a lot for the advice..!!
nobleskill said:
No having super user rights doesn't mean you can write or change system files per say.. you first need the system mounted read/write which as a super user you do have the rights to....
So yes su is important but I suspect the issue here is the way the system is mounted...
Sent from my GT-P1000
Click to expand...
Click to collapse
Yes I agree but I don't know how to fix it that way.. thanks for helping
Sorry man. It was supposed to be moved to Q and A some time ago and it just never happened. My fault, my mistake. sorry to all that this bothers, and thank you to all that are helping me out.
~k~
nobleskill said:
Anyway use root explorer navigate into //system/ and there will be a button on the top to mount the system read/write. Then long press your file and select the permissions you want. Hit the same. Button as before to remount as read only and your away..
Sent from my GT-P1000
Click to expand...
Click to collapse
Thanks a lot for this advice, I tried it and got a message that says, "System permissions cannot be changed because the file system is Read-only"
Thanks again, it was worth a try.
~K~
quick question....
When do I enter that into my command prompt? right before I try to chmod or right after????
thanks a lot
~K~
mchampeli said:
i have a SGH-T849..
i want to carrier unlock it.. also i couldn't find the dialer & the messaging application in the phone.. so wanted to know how to make voice calls & send messages in it??
Sorry for the bad English & for being a noob
Click to expand...
Click to collapse
I think you have to put on a new rom that does that. try http://theunlockr.com/2010/11/29/how-to-flash-a-custom-recovery-image-on-the-samsung-galaxy-tab/
good luck
~K~
GldRush98 said:
You're trying to write data to a partition mounted as read only.
To mount the system partition so you can write to it, simple issue this command:
mount -o remount,rw /dev/block/mtdblock3 /system
And of course to mount it back to read only again:
mount -o remount,ro /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
I tried that. I tried it like this and this is what happened..
# mount -o remount,rw /dev/block/mtdblock3 /system
# chmod 755 / data/local/bin/flash_image
Unable to chmod /: Read-only file system
Did I do it wrong. Should I of put that code in a different spot?
either way thank you for trying to help me out..
~K~
Yea I tried that and it said "system permission cannot be changed becausethe file system is Read-Only" so I don' know. But I do really appriciate you trying to help me out.
knotrkr said:
I tried that. I tried it like this and this is what happened..
# mount -o remount,rw /dev/block/mtdblock3 /system
# chmod 755 / data/local/bin/flash_image
Unable to chmod /: Read-only file system
Did I do it wrong. Should I of put that code in a different spot?
either way thank you for trying to help me out..
~K~
Click to expand...
Click to collapse
Whoops, I thought the file you were chmod'ing was in the system partition.
The data partition is already mounted with read/write.
Your chmod command is incorrect... there is an extra space in there.
It should be:
chmod 755 /data/local/bin/flash_image
I don't think the data partition is mounted as read only (I could be wrong, but I didn't think it was)
trying to install the DSPmanager apk i got here.
i've tried in ADB, and it gives an invalid install location error, tried in OI file manager and it gives me a big, happy green arrow and says "application not installed"
running GinSense 0.9
any help would be appreciated.
(sorry if this is the wrong thread)
(and i did search and will continue to do so until/unless i hear back)
EDIT to say - also tried app installer - same happy arrow and not installed as OI manager.
Most likely on your default install location there is no more space left to install the application. You can try to modify that by
Code:
adb shell pm setInstallLocation 2
from your PC having connected your phone in debugging mode.
The different locations are described in more details in this post.
i managed to get it installed with
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/DSPManager.apk /system/app
i don't understand why neither of my app installers were doing this, but i'm new to this, so maybe i'm missing something. that link looks like some useful info, though. thanks!
Ok, in that way you installed DSPManager on your /system partition. Generally this is read only and there is no space left. Applications normally will be installed on /data, /sdcard or (if supported by to ROM) on /sd-ext.
AndDiSa said:
Ok, in that way you installed DSPManager on your /system partition. Generally this is read only and there is no space left. Applications normally will be installed on /data, /sdcard or (if supported by to ROM) on /sd-ext.
Click to expand...
Click to collapse
i'm running ginsense with S2E, so i assume normally would be on sd-ext.
i tried both using the install feature and just manually placing the .apk in /sd-ext to no avail. i also tried placing it in /data with no luck.
what are the practical differences with putting it in /system? FWIW, it's running fine with it there (both the rom and the app)
i don't know if it makes a difference, but the app is DSP manager
i removed it from /system/app then used ADB shell. i *think* i figured out what i was doing wrong, the command line wanted me to specify an install location, which i wasn't doing. is this a "cleaner" install method?
Code:
adb shell
install /sdcard/DSPManager.apk /sd-ext/app
app shows up in the launcher again.
Typically just doing an
adb install /locationofapkonyourcomputer
Click to expand...
Click to collapse
will do the trick. You don't need to copy the .apk onto your phone just to install it.
As mentioned previously, it may be that your default install location is NOT set to /sd-ext/app and that /data is full.
Hi, I'm trying to install Xposed on my Acer A1-810 tablet but I'm getting mount error while doing it. It says that it can't mount /system as red-write and therefore can't create app_process.orig file.
The problem is that my device is rooted and even mounting /system as rw by hand doesn't fix this error.
I remember having the same problem when I tried to install xposed on my xperia phone couple months ago so it seems like it's not a rare issue but I can't find anything on it.
Thanks in advance.
If you use custom Recovery, try another installation method (flashing zip via Recovery)
Yeah, I know about different methods of installation but unfortunately there is no way to unlock bootloader on my tablet so It's classic way or nothing.
bump
bump
bump
czesu said:
Hi, I'm trying to install Xposed on my Acer A1-810 tablet but I'm getting mount error while doing it. It says that it can't mount /system as red-write and therefore can't create app_process.orig file.
The problem is that my device is rooted and even mounting /system as rw by hand doesn't fix this error.
I remember having the same problem when I tried to install xposed on my xperia phone couple months ago so it seems like it's not a rare issue but I can't find anything on it.
Thanks in advance.
Click to expand...
Click to collapse
What SU are you using? I had the same problem on my rooted Z3. As a workaround, I went into SuperSU settings, and disabled "Mount namespace separation". Then, after a reboot, I used Root Explorer to mount /system as r/w, then went back into Xposed installer to install the framework.
It looks like for some reason the Xposed installer can't mount the system partition r/w, but Root Explorer can in my case.
A1-81x does not have a mountable/writable system. The only way to root system is by dumping it to an img file, adding su, etc., to it and then restoring it again. This can be done through the MTK Logger. I have created similar instructions for Acer S1 that has a similar issue:
forum.xda-developers.com/android/development/root-acer-liquid-s1-s510-a10-kk-rom-t3004333
The Iconia toolkit is supposed to do this for you, but some devices and KK versions do not work anymore because it uses the Network Utility. Here's the toolkit:
http://forum.xda-developers.com/showthread.php?t=2240029
With regards to Xposed, I tried adding it to my phone by simply copying the app_process before transfering the img back to my phone:
Code:
sudo cp de.robv.android.xposed.installer_v33_36570c.apk /media/iconia/app/
sudo cp -a /media/iconia/bin/app_process /media/iconia/bin/app_process.orig
sudo cp de.robv.android.xposed.installer_v33_36570c/assets/arm/app_process_xposed_sdk16 /media/iconia/bin/app_process
sudo chmod 0755 /media/iconia/bin/app_process
That didn't work though! So... if anyone from these Xposed threads why just using the new app_process does not work, I'd appreciate the help.
(btw - I did already have the Xposed app installed and confirmed that the app_process is new and the apk is in the system folder)
Regards,
Nika.
I'm attempting to mount the xbin folder to copy over a file into it (sqlite3) and am unable to. When I attempt to mount R/W in Root Explorer nothing happens. If I copy the file directly and attempt to mount from the prompt Root Explorer states that the copy failed. I've even attempted chmod and that also fails.
I did a clean install of Marshmallow, flashed TWRP 2.8.5.0, flashed ElementalX-N6-2.03 kernel, then SU Beta 2.49. Root Checker tells me that I have root access and busybox is installed properly.
As a test I tried all of the above on other folders such as bin and that failed as well. I've attempted copying sqlite3 in TWRP over to bin (couldn't find xbin in the file manager) and it said successful, but doesn't show when I boot back up. Does anyone have any idea what is causing this?
dudeman27 said:
I'm attempting to mount the xbin folder to copy over a file into it (sqlite3) and am unable to. When I attempt to mount R/W in Root Explorer nothing happens. If I copy the file directly and attempt to mount from the prompt Root Explorer states that the copy failed. I've even attempted chmod and that also fails.
I did a clean install of Marshmallow, flashed TWRP 2.8.5.0, flashed ElementalX-N6-2.03 kernel, then SU Beta 2.49. Root Checker tells me that I have root access and busybox is installed properly.
As a test I tried all of the above on other folders such as bin and that failed as well. I've attempted copying sqlite3 in TWRP over to bin (couldn't find xbin in the file manager) and it said successful, but doesn't show when I boot back up. Does anyone have any idea what is causing this?
Click to expand...
Click to collapse
ElementalX hasn't got the R/W protection removed. You'll have to use Hellscore (or maybe some others) until the protection is removed in Ex. It is next on the list for that Kernel I thin.
danarama said:
ElementalX hasn't got the R/W protection removed. You'll have to use Hellscore (or maybe some others) until the protection is removed in Ex. It is next on the list for that Kernel I thin.
Click to expand...
Click to collapse
Thanks! That resolved the mounting problem but for some reason copying over the file still fails. I even chmod 0777 on xbin and it won't copy. Hmm.
dudeman27 said:
Thanks! That resolved the mounting problem but for some reason copying over the file still fails. I even chmod 0777 on xbin and it won't copy. Hmm.
Click to expand...
Click to collapse
Convert or uninstall unnecessary Google apps in /system the free space on stock /system is only about 2mb, this was one of the reasons I initially couldn't install layers.
Sent from my Nexus 6 using Tapatalk
djkinetic said:
Convert or uninstall unnecessary Google apps in /system the free space on stock /system is only about 2mb, this was one of the reasons I initially couldn't install layers.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
You sir are a saint! I read about that and thought 16 MB was enough, but I went up to 64 MB and everything works perfectly now. Thank you.
danarama said:
ElementalX hasn't got the R/W protection removed. You'll have to use Hellscore (or maybe some others) until the protection is removed in Ex. It is next on the list for that Kernel I thin.
Click to expand...
Click to collapse
Hey, I'm on Hellscore kernel and I cant mount system as R/W either. I am having exactly the same issues as OP. I cant edit the build.prop or change layers. I got one layers theme to work but I cant change it since I cant uninstall it from /system. Any idea?
BluntSmokeTrauma said:
Hey, I'm on Hellscore kernel and I cant mount system as R/W either. I am having exactly the same issues as OP. I cant edit the build.prop or change layers. I got one layers theme to work but I cant change it since I cant uninstall it from /system. Any idea?
Click to expand...
Click to collapse
Do you have root explorer? If so, does the mount r/w button work?
danarama said:
Do you have root explorer? If so, does the mount r/w button work?
Click to expand...
Click to collapse
Yes, I have root explorer. When I hit the button nothing happens. I downloaded the app called Mount /system and when I hit the button to mount it in there it tells me my device may not be rooted or compatible. In terminal emulator when I type su the $ changes to #, and in supersu everything has the proper root rights so I know my root is working.
I guess I should also mention that I am running the xTraSmooth 6.0 rom that came pre rooted with the hellscore kernel. I flashed it from stock M after flashing TWRP.
BluntSmokeTrauma said:
Yes, I have root explorer. When I hit the button nothing happens. I downloaded the app called Mount /system and when I hit the button to mount it in there it tells me my device may not be rooted or compatible. In terminal emulator when I type su the $ changes to #, and in supersu everything has the proper root rights so I know my root is working.
I guess I should also mention that I am running the xTraSmooth 6.0 rom that came pre rooted with the hellscore kernel. I flashed it from stock M after flashing TWRP.
Click to expand...
Click to collapse
I got weird behavior like that as well. Try converting apps to free up space. I had 64 MB free om the system partition when mine started working.
dudeman27 said:
I got weird behavior like that as well. Try converting apps to free up space. I had 64 MB free om the system partition when mine started working.
Click to expand...
Click to collapse
I've been looking through the thread for the rom and some other people had the same issue. They reflashed the rom and it seemed to fix it for some reason. So I'm going to try that in a bit and see how it goes.
BluntSmokeTrauma said:
Yes, I have root explorer. When I hit the button nothing happens. I downloaded the app called Mount /system and when I hit the button to mount it in there it tells me my device may not be rooted or compatible. In terminal emulator when I type su the $ changes to #, and in supersu everything has the proper root rights so I know my root is working.
I guess I should also mention that I am running the xTraSmooth 6.0 rom that came pre rooted with the hellscore kernel. I flashed it from stock M after flashing TWRP.
Click to expand...
Click to collapse
Well not sure about.that xtrasmooth. Seems.like it has plenty of.issues.. Try and download hc again or try another rom.
danarama said:
Well not sure about.that xtrasmooth. Seems.like it has plenty of.issues.. Try and download hc again or try another rom.
Click to expand...
Click to collapse
No other issues than that really. I'm gonna reflash
BluntSmokeTrauma said:
No other issues than that really. I'm gonna reflash
Click to expand...
Click to collapse
Actually, I think someone said they did that in that rom thread to fix this.
danarama said:
Actually, I think someone said they did that in that rom thread to fix this.
Click to expand...
Click to collapse
Yep. I read thru it and saw that, just got done and it fixed the issue. Sweet.