Database Info

Root Explorer ICS issue...

No matter what I do, whether it's the 1 click odin or the cwm backup that is rooted/deodexed, root explorer will not allow my /system/ to be r/w.
I have wiped and rebooted and formatted and reflashed a dozen times now, and every time I boot up and get root going, root explorer will flip to r/w for ONE operation. after the first operation it will no longer work, and if i try to toggle the r/w switch it won't move from r/o. Sometimes I don't even get one opeartion, it just doesn't work.
I have superuser installed, i tried checking for updates, i tried fixing permissions, i tried clearing cache. I dont get it!
SOmeone help?

Did you try another rom?
I have Sensation XE with ICS and Sense4 and Root Explorer is working good here.
Flash another Rom and see if it works.
Sent from my Sensation XE powered by InsertCoin Sense 4 with Tapatalk 2

Sirgatory said:
No matter what I do, whether it's the 1 click odin or the cwm backup that is rooted/deodexed, root explorer will not allow my /system/ to be r/w.
I have wiped and rebooted and formatted and reflashed a dozen times now, and every time I boot up and get root going, root explorer will flip to r/w for ONE operation. after the first operation it will no longer work, and if i try to toggle the r/w switch it won't move from r/o. Sometimes I don't even get one opeartion, it just doesn't work.
I have superuser installed, i tried checking for updates, i tried fixing permissions, i tried clearing cache. I dont get it!
SOmeone help?
Click to expand...
Click to collapse
It might be related to this... Read posts 5+
http://forum.xda-developers.com/showthread.php?t=1568382

oops hit thanks by mistake, freebie for you.
This happened to me a lot with the deodexed version and happens every now and then with the rogers cwm file. most times a reboot helps but don't know whats causing it.

No problems with mounting R/W with stock leaked ICS here via Root Explorer.
I just deleted a bunch of .apk's w/out problem.

Yeah, I'm having similar issues. Clockworkmod won't fix permissions either.

Frogacuda said:
Yeah, I'm having similar issues. Clockworkmod won't fix permissions either.
Click to expand...
Click to collapse
For me, ROM Manager won't fix permissions. But CWM does.
Someone else said if you install busybox from Market, that will fix it so ROM Manager will fix permissions also.
edit: confirmed, installing busybox allowed ROM Manager to fix permissions for me.
And it's doing a lot more than the CWM fix permissions did!

I had to reflash su zip from sd card again to get rom manager to fix permissions.
Sent from my SAMSUNG-SGH-I727 using xda premium

CZ Eddie said:
For me, ROM Manager won't fix permissions. But CWM does.
Someone else said if you install busybox from Market, that will fix it so ROM Manager will fix permissions also.
Click to expand...
Click to collapse
Can confirm that this worked for me.. used the app called Busybox (not Busybox Installer) and ROM Manager was able to run through and complete fixing permissions.
-EDIT-
Seems to be kinda hit and miss.. was able to get ROM Manager to fix permissions on mhx's CWR backup by using the Busybox app. Just tried it on tpmullen's ROM and it would hang, so I used the app to reinstall Busybox again and it still hangs.

Go to to romracers kernel thread and try flashing his ics kernel. (Unsecured)
EDIT:
This did not work for me I can freeze apps but not delete.

[mohan_kr][KERNEL] Stock UCALC4 (ICS) - CWM - insecure, bash

Due to xda new member rules, I have to resort to the General Section. The new ICS kernel, has locked down adb root access. What this means is when you adb shell you will be dropped into normal shell (even though you have su installed). This would probably help ROM creaters who are bundling the kernel. It has init.d support and the bootanimation (this file should be /system/media/bootanimation.zip, if it does not work, link it as sanim.zip)
* This also defaults to bash shell when you (adb shell) not the default ICS mksh. Also, it can read bash_profile from /sdcard/bash_profile
db.tt/RcDapiMg (prepend with) as xda does not allow this yet
Cheers
Click to expand...
Click to collapse
Simply posting this for mohan_kr. This deserves more attention than just the General section.
Original Thread:
http://forum.xda-developers.com/showthread.php?p=24208186
db.tt/RcDapiMg

sorry but how is this different from the kernel romracer released?

I think its exactly the same. Regardless neither one let me delete the .qmg files in system/media in order to add a bootanimation
Swyped from my Galaxy S2 Skyrocket using XDA premium

bts0uth said:
I think its exactly the same. Regardless neither one let me delete the .qmg files in system/media in order to add a bootanimation
Swyped from my Galaxy S2 Skyrocket using XDA premium
Click to expand...
Click to collapse
I was able to use bootanimation.zip on this kernel.
-----------
sent from my calculator with android

does this kernel fix the reboot/power issue? i found that the original ucalc kernel actually made my phone less stable and lagged horribly. i was using it with the ics smooth ice rom.

Bootanimation.zip confirmed working on this kernal along with being able to edit files under /system unlike before
Sent from my SAMSUNG-SGH-I727 using XDA

jnicks510 said:
does this kernel fix the reboot/power issue? i found that the original ucalc kernel actually made my phone less stable and lagged horribly. i was using it with the ics smooth ice rom.
Click to expand...
Click to collapse
Someone said freezing shutdown app fixed it for them in another thread

Power/reboot works for me now, as does a custom boot animation. Great work! Any chance we can get the BLN mod put into this kernel?

+1 for BLN

onearmedscissor said:
Someone said freezing shutdown app fixed it for them in another thread
Click to expand...
Click to collapse
I tried this, didn't work, still gets stuck on Shutting down...

I flashed the CWM Touch recovery and found that the shutdown/reboot freezing was gone.
I used the odin flash with the Roboto font from here: http://rootzwiki.com/topic/19217-recovery-clockworkmod-touch-5504-v2/
oh, and after flashing this CWM, I reflashed the superuser zip and was finally able to mount and modify /system

morehush said:
I flashed the CWM Touch recovery and found that the shutdown/reboot freezing was gone.
I used the odin flash with the Roboto font from here: http://rootzwiki.com/topic/19217-recovery-clockworkmod-touch-5504-v2/
oh, and after flashing this CWM, I reflashed the superuser zip and was finally able to mount and modify /system
Click to expand...
Click to collapse
Did nothing here. Used roboto font version through ODIN and reflashed super user...
Shutdown / restart is still hanging for me.
I still can't modify system.

bts0uth said:
Did nothing here. Used roboto font version through ODIN and reflashed super user...
Shutdown / restart is still hanging for me.
I still can't modify system.
Click to expand...
Click to collapse
Try reflashing this kernel with the new clockwork mod touch, then reflash superuser, then reboot recovery and fix permissions.

morehush said:
Try reflashing this kernel with the new clockwork mod touch, then reflash superuser, then reboot recovery and fix permissions.
Click to expand...
Click to collapse
Got remount,rw of system working by reflashing the UCALC4 one click, then CWM 5.5.0.4, then this kernel and superuser via CWM, only then allowing system to fully boot. Then installed busybox.
Seems that if UCALC4 stock kernel is allowed to fully boot I'm not able to remount system as rw. It appears to remount, but the /proc/mounts shows it as ro and attempts to write system result in 'read-only filesystem'.

cschmitt said:
Got remount,rw of system working by reflashing the UCALC4 one click, then CWM 5.5.0.4, then this kernel and superuser via CWM, only then allowing system to fully boot. Then installed busybox.
Seems that if UCALC4 stock kernel is allowed to fully boot I'm not able to remount system as rw. It appears to remount, but the /proc/mounts shows it as ro and attempts to write system result in 'read-only filesystem'.
Click to expand...
Click to collapse
Yup, the stock kernel the f**ls changed the adbd to not honor the ro.secure flag. If you have any ICS builds, drop in the adbd and viola...

This fixed my power off issue. Thanks mohan and thanks for posting this. Now after this and running silver's rom I am full of Ice Cream Sammich goodness.
Sent from my SAMSUNG-SGH-I727 using xda premium

Ooops never mind. This was meant for a different thread.
Sent from my SAMSUNG-SGH-I727 using xda premium

[Q] How do I temporarily "unroot" device?

Hello,
I need to unroot by ICS ROM temporarily so I can install and run certain application, how do I do that with minimum amount of work?
Thanks,
G

Questions belong in Q&A. Moved

artisticcheese said:
Hello,
I need to unroot by ICS ROM temporarily so I can install and run certain application, how do I do that with minimum amount of work?
Thanks,
G
Click to expand...
Click to collapse
i cant c y u would have to unroot, it shouldnt matter as apps dont care if it is rooted or unrooted, correction some apps u have to b rooted to work properly.
do u actually get an error message when trying to install an app
the only way is to restore back to stock, or if u just rooted ur stock firmware, meaning u didnt flash a rom, u can try flashing the system.img file, that might work but i never heard of any1 doing that

Yes, application refuses to work telling me that "rooted" phones are not supported. So basically it installs, checks if phone is rooted and refuses to proceed. I hoped I can flash something in CMW to temporarely unroot, then run application, let it do it one time thing (I need to run this application only once successfully) and then I root back in CWM again.

artisticcheese said:
Yes, application refuses to work telling me that "rooted" phones are not supported. So basically it installs, checks if phone is rooted and refuses to proceed. I hoped I can flash something in CMW to temporarely unroot, then run application, let it do it one time thing (I need to run this application only once successfully) and then I root back in CWM again.
Click to expand...
Click to collapse
dont think there is a temporary unroot method, going back to stock was the true method to unrooting, which app were u trying to install.
u can trying going back to stock, installing app, let it do its thing, backup with tibu or some other backup, reroot and then restore backup of app.....maybe wont work as restoring a backup is actually reinstalling the app
edit: try this i havent so try at ur own risk http://www.thespicygadgematics.com/2012/06/how-to-easily-unroot-any-android-phone.html it seems easy enough, i didnt think it was possible but it seems to b

artisticcheese said:
Hello,
I need to unroot by ICS ROM temporarily so I can install and run certain application, how do I do that with minimum amount of work?
Thanks,
G
Click to expand...
Click to collapse
Using root explorer or ES File Explorer, mount system as r/w, delete /system/app/Superuser.apk, /system/bin/su or /system/xbin/su (it will be in one of those two places), and then reboot. done.

cschmitt said:
Using root explorer or ES File Explorer, mount system as r/w, delete /system/app/Superuser.apk, /system/bin/su or /system/xbin/su (it will be in one of those two places), and then reboot. done.
Click to expand...
Click to collapse
thats deleting the app the rooted the phone, but does it actually undo the rooting process, the system files the app changed to make it rooted r still there, the way to check is if u do delete su app, c if root explorer can can mount ur system folder to r/w, or op can c if it the app does install after deleting su.
actually u need su to grant su, so that might not b a good test

cschmitt said:
Using root explorer or ES File Explorer, mount system as r/w, delete /system/app/Superuser.apk, /system/bin/su or /system/xbin/su (it will be in one of those two places), and then reboot. done.
Click to expand...
Click to collapse
Thanks,
How do I root back after that though?

vincom said:
thats deleting the app the rooted the phone, but does it actually undo the rooting process, the system files the app changed to make it rooted r still there, the way to check is if u do delete su app, c if root explorer can can mount ur system folder to r/w, or op can c if it the app does install after deleting su.
actually u need su to grant su, so that might not b a good test
Click to expand...
Click to collapse
The superuser cwm zip installs su and superuser.apk, that's it. There are no other modified apps.
You can remove busy box also if you like, but it's not much use without su.

artisticcheese said:
Thanks,
How do I root back after that though?
Click to expand...
Click to collapse
Flash superuser zip in cwm.

cschmitt said:
The superuser cwm zip installs su and superuser.apk, that's it. There are no other modified apps.
You can remove busy box also if you like, but it's not much use without su.
Click to expand...
Click to collapse
kool. i learn something everyday

There is cool app in Playstore (free) which allows rooting/unrooting with no reboots and other complicated steps
FYI
https://play.google.com/store/apps/...51bGwsMSwxLDMsImV1LmNoYWluZmlyZS5zdXBlcnN1Il0

Voodoo OTA can do a temp unroot as well. The Flixter app will not allow you to stream movis on a rooted phone. I used Voodoo to temp unroot then went back into Flixter and it started to play the movie.

I use an app called Temp root remover
It allows you to temporarly unroot and reroot in a matter of seconds

Why can't I edit build.prop or push to /system/app?

Odd.
In the original firmware I was able to edit build.prop to change my dpi to 120 but now I cannot. It won't save any changes. Also, I tried pasting an .apk into my /system/app folder and it blocked me. Then I tried pushing it with adb and it gave me a read-only error.
I know I am rooted - can run Titanium Backup, etc.
Anyone have any idea?

mitchellvii said:
Odd.
In the original firmware I was able to edit build.prop to change my dpi to 120 but now I cannot. It won't save any changes. Also, I tried pasting an .apk into my /system/app folder and it blocked me. Then I tried pushing it with adb and it gave me a read-only error.
I know I am rooted - can run Titanium Backup, etc.
Anyone have any idea?
Click to expand...
Click to collapse
Did you try another root explorer?
Root explorer can be finicky.
Also try clearing it out of super su and and reallowing it. Or wipe app data.
But from my experience with root explorer, I have always hated it!! Try File Manager HD, It is great and has root explorer and system mountable all the time

BeerChameleon said:
Did you try another root explorer?
Root explorer can be finicky.
Also try clearing it out of super su and and reallowing it. Or wipe app data.
But from my experience with root explorer, I have always hated it!! Try File Manager HD, It is great and has root explorer and system mountable all the time
Click to expand...
Click to collapse
Downloaded File Manager HD. Tried replacing the Snotes.apk. No dice. All attempts do do anything with that .apk fail. Seems pretty well locked down.
Same thing with build.prop. No changes will save.

mitchellvii said:
Downloaded File Manager HD. Tried replacing the Snotes.apk. No dice. All attempts do do anything with that .apk fail. Seems pretty well locked down.
Same thing with build.prop. No changes will save.
Click to expand...
Click to collapse
Hmm..
I will try it on my note and see if it works.
Also did u make sure it was called the right name and have the right permissions?
I will let you know tomorrow or maybe tonight if it works

Yep. I've done all this many times before. They have Snotes locked down tight.
Sent from my GT-N8013 using Tapatalk 2

mitchellvii said:
Yep. I've done all this many times before. They have Snotes locked down tight.
Sent from my GT-N8013 using Tapatalk 2
Click to expand...
Click to collapse
You don't have proper root. Reroot and try again. Works like a charm! See below.
Sent from my GT-N8013 using XDA Premium HD app

Huh that seems odd as everything that requires root to work seems to work just fine. Oh well will give it a shot.
Curious as to which method you used to achieve root?
Sent from my GT-N8013 using Tapatalk 2

did you make sure to mount the system folder as r/w? i've never memorized the command since i just use root explorer.

madsquabbles said:
did you make sure to mount the system folder as r/w? i've never memorized the command since i just use root explorer.
Click to expand...
Click to collapse
Yes I did everything correctly. Just not working. That's OK.
Sent from my GT-N8013 using Tapatalk 2

mitchellvii said:
Huh that seems odd as everything that requires root to work seems to work just fine. Oh well will give it a shot.
Curious as to which method you used to achieve root?
Sent from my GT-N8013 using Tapatalk 2
Click to expand...
Click to collapse
Custom Recovery, root.zip, TriangleAway. Although root access is being granted, there may be an issue with permissions on "/system". Tried fixing permissions yet?
Sent from my GT-I9300 using XDA Premium HD app

Mister_Mxyzptlk said:
Custom Recovery, root.zip, TriangleAway. Although root access is being granted, there may be an issue with permissions on "/system". Tried fixing permissions yet?
Sent from my GT-I9300 using XDA Premium HD app
Click to expand...
Click to collapse
No haven't done that. Will run a permissions fix.

mitchellvii said:
No haven't done that. Will run a permissions fix.
Click to expand...
Click to collapse
I was wondering if you have resolved this issue because im having the same problem now. Do you recall doing anything that may have caused this issue? Everything for me started going heywire once i installed init.d support just a second ago. I Can r/w and r/o in certain parts of the system but i cant paste anything anywhere. I also noticed increase cpu load afterwards. Might i add this is the second time i have had these issues after installing init.d support script. The way i solved this the first time was i had to odin stock firmware and this solved everything. Id like to refrain from doing this again though because ill loose all my stuffs and have to set everything up again.
Sent from my GT-N8013 using Tapatalk 2

How did you achieve root? In other threads, problems with write access to /system are reported when a rooted firmware was flashed. Only the method with CWM (install CWM, flash SuperSU) did work.

akxak said:
How did you achieve root? In other threads, problems with write access to /system are reported when a rooted firmware was flashed. Only the method with CWM (install CWM, flash SuperSU) did work.
Click to expand...
Click to collapse
Oh the first time i rooted with the CWM method. But the second time, i did odin a rooted firmware Now that i think about it, the first time i was able to write to /system but now i can't after a rooted firmware flash. So the init.d script wasnt the problem. I just made an assumption because before, i havent touched anything in /system but when i installed init.d script it was actally the first time i tried to edit /system after the rooted firmware. So yes looks like im going to have to odin a stock non-rooted firmware. Thanks man! Makes alot of since now.
edit: couldn't i just try the cwm method and see it it overwrites, cause the only UEALGB firmware i can find is prerooted. I don't want to switch to UEALH2.
Sent from my GT-N8013 using Tapatalk 2

mitchellvii said:
Odd.
In the original firmware I was able to edit build.prop to change my dpi to 120 but now I cannot. It won't save any changes. Also, I tried pasting an .apk into my /system/app folder and it blocked me. Then I tried pushing it with adb and it gave me a read-only error.
I know I am rooted - can run Titanium Backup, etc.
Anyone have any idea?
Click to expand...
Click to collapse
me to same error

Try Root Explorer(or ES File Explorer) & enable R/W for system files
Check your SuperSU/Superuser app.
See if your access is granted & not denied.
If SuperSU/Superuser asking for update, update it (usually binary update)
If your SuperSU/Superuser is gone, re-install it from Play Store & run it for the first time to update binary.
Retry modifying your system file(s)

Bro I cannot change build.prop product model....
I tried root explorer and es explorer
From yuphoria

Is that cannot or don't know how.
One is no root two is edit.
Sent from my SM-N930F using XDA-Developers mobile app
---------- Post added at 02:13 PM ---------- Previous post was at 01:20 PM ----------
JJEgan said:
Is that cannot or don't know how.
One is no root two is edit.
Sent from my SM-N930F using XDA-Developers mobile app
Click to expand...
Click to collapse
Edit is at the top of the RH side.
Sent from my SM-N930F using XDA-Developers mobile app

I have the same problem...
I can change my build.prop but after a reboot all the changes are gone.
I have rerooted it 2-3 times already. I can just change it sucessfully at the beginning but after some time it doesn't work anymore.
I have a samsung galaxy a3 2017.

Try forum for your phone .
Post lacks any information to help.
Suggest FX Explorer.

AROMA file manager that works on Explorer? [SOLVED]

Is there any version of AROMA file manager that works properly on the Explorer? I have discovered that I have some how lost the busybox binary from /system/xbin and now I need to replace it, which I think would probably be easiest by copying from /system/bin with AROMA FM. (If there's a better way, please let me know and I'll do it instead).
(At the moment, my phone won't boot, so it's kinda urgent...)

Isn't easyer to just flash the rom that you already have, with wiping only cache?

shortyoko said:
Isn't easyer to just flash the rom that you already have, with wiping only cache?
Click to expand...
Click to collapse
No, seeing as that wouldn't fix anything...I'm on stock ROM which does not include busybox, so flashing it would achieve nothing. (To clarify, busybox is required by some script(s) I have installed)
EDIT: Turns out that the latest version of AROMA FM works fine. Booting is certainly getting further now than it did before

then flash something new

TUDVAD said:
then flash something new
Click to expand...
Click to collapse
No thank you. I have fixed the issue now, without needing to flash a new ROM or anything silly like that (my current setup is exactly what I want, there is no point in me changing it and having to go through the hassle of restoring all my apps, setting up all my accounts again etc.).
All I needed to do was use the latest AROMA FM to copy busybox from /system/bin to /system/xbin. Took all of about 20 seconds once I got a card reader and the latest version of AROMA. Compared to the time required to download and flash a new ROM, and all the app restoring that would be required following doing so (and I don't even have completely updated backups, so I'd be missing some apps/data), I think my solution was better.

....
SifJar said:
No thank you. I have fixed the issue now, without needing to flash a new ROM or anything silly like that (my current setup is exactly what I want, there is no point in me changing it and having to go through the hassle of restoring all my apps, setting up all my accounts again etc.).
All I needed to do was use the latest AROMA FM to copy busybox from /system/bin to /system/xbin. Took all of about 20 seconds once I got a card reader and the latest version of AROMA. Compared to the time required to download and flash a new ROM, and all the app restoring that would be required following doing so (and I don't even have completely updated backups, so I'd be missing some apps/data), I think my solution was better.
Click to expand...
Click to collapse
if u found it can u plz post the link/.......:good:

bid4sumit said:
if u found it can u plz post the link/.......:good:
Click to expand...
Click to collapse
Like I said, the latest version of AROMA FM (1.8 was the version I used) works fine as-is. Here's a link to it: http://forum.xda-developers.com/showthread.php?t=1646108