Rooted flashed rebelrom all is fine but still cannot access root in ANY file Brower , I've install supersu, updated, uninstall and installed again still can't get root access.
Had this problem with all roms I've used.
I need root acess!
Despite being first post I'm not a noob
Use other forums just this its the best place to be.
Any help would be appreciated.
Try re flashing supersu or superuser zip in cwm.
Sent from my SPH-D710 using xda premium
is it just file browser or other apps too? have you tested with titanium? whose method did you use to obtain root?
Updated SU, on the thrid go root access fully granted!!
Thanks for help, i ended up flashing from zip
Crazy stuff like this will happen when flashing roms. For the most part making sure you update the su binary before using root apps helps btw
Sent from my SGH-I747 using Tapatalk 2
Related
Hey everyone. Just got the Samsung Nexus S... and I've got a question.
I've read on these forums that the OTA makes it so you have to flash CWM recovery everytime you want to reboot into recovery to flash a ROM and that it's more difficult to root.
Should I flash the OTA then root or root prior to OTA?
Thanks in advance.
m00n
Sent from my SGH-T959 using XDA App
You should get the OTA before you root and it is very easy to make the root stick. I did it with root explorer but I heard you can do it without it.
Sent from my Nexus S using XDA App
tominater12 said:
You should get the OTA before you root and it is very easy to make the root stick. I did it with root explorer but I heard you can do it without it.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Which method did you use to root. And how did you manage to use root explore to get root access when root explorer needs root access first in order to operate? Thanks for your response.
Sent from my SGH-T959 using XDA App
No after you root you can use root explorer to make the recovery stick and there are like 5 guides on how to root on every OS in the android development sub-section. (They are stickied)
m00nshake said:
Which method did you use to root. And how did you manage to use root explore to get root access when root explorer needs root access first in order to operate? Thanks for your response.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Sent from my Nexus S using XDA App
Thanks again for your response and for the clarification about using root explorer. I have read the stickies regarding rooting the phone, and because there are a few, I was wondering which method you used. I've read that superboot is the easiest and that you can rename a particular system file so the recovery sticks. Thanks again for your response.
Sent from my SGH-T959 using XDA App
m00nshake said:
Thanks again for your response and for the clarification about using root explorer. I have read the stickies regarding rooting the phone, and because there are a few, I was wondering which method you used. I've read that superboot is the easiest and that you can rename a particular system file so the recovery sticks. Thanks again for your response.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Get the OTA.
Apply it.
Boot up to make sure everything is ok. Then boot to bootloader
fastboot oem unlock, confirm it, wipes everything including your internal sd.
flash clockwork mod recovery.
go to clockwork mod recovery from bootloader menu.
mount "internal sd" copy the su-2.3.6.1-ef-signed.zip you downloaded (from the guide) to your internal sd.
unmount internal sd.
mount /system
flash the su-2.3.6.1-ef-signed.zip file.
reboot phone as normal.
login to your gmail account. go to market, download a rooted app like titanium backup free version, and also download rom manager, and buy/get root explorer.
install all those make sure super user is granted and works.
use root explorer to rename/delete the file in: /etc/recovery.sh file or whatever it's actually called.
go to rom manager, and flash the latest clockworkmod recovery (3.0.0.5)
turn off phone and boot to recovery and make sure it's clockwork mod 3.0.0.5, if it is, you're set.
Very helpful post, nxt. Thank you very much.
Sent from my Nexus S using XDA App
nxt said:
Get the OTA.
Apply it.
Boot up to make sure everything is ok. Then boot to bootloader
fastboot oem unlock, confirm it, wipes everything including your internal sd.
flash clockwork mod recovery.
go to clockwork mod recovery from bootloader menu.
mount "internal sd" copy the su-2.3.6.1-ef-signed.zip you downloaded (from the guide) to your internal sd.
unmount internal sd.
mount /system
flash the su-2.3.6.1-ef-signed.zip file.
reboot phone as normal.
login to your gmail account. go to market, download a rooted app like titanium backup free version, and also download rom manager, and buy/get root explorer.
install all those make sure super user is granted and works.
use root explorer to rename/delete the file in: /etc/recovery.sh file or whatever it's actually called.
go to rom manager, and flash the latest clockworkmod recovery (3.0.0.5)
turn off phone and boot to recovery and make sure it's clockwork mod 3.0.0.5, if it is, you're set.
Click to expand...
Click to collapse
Don't you need the android sdk?
tominater12 said:
Don't you need the android sdk?
Click to expand...
Click to collapse
Yes, you need to have the Android SDK properly installed and you're able to do a 'fastboot devices' command properly and your Serial number comes up.
This may seem like a basic question to you guys.
I work in an industry where our emails our monitored.
We now have the ability to get emails on android phones instead of only being able to use blackberry.
The email is transmitted securely by an app called GOOD.
GOOD will not work on rooted phones.
Can I root & remove bloatware & then unroot ? Or does it all come back?
I assume the phone has to be rooted to run a custom ROM?
Apologies if these are basic questions
Check out this thread here:
http://forum.xda-developers.com/showthread.php?t=1255214
The steps to follow would be to:
1) Install clockworkmod recovery using the one-click recovery flasher that tga gunmann has posted in the development section.
2) Download the 2 zips that jboxer posted in the thread I linked to above and save them to the sdcard on your phone
3) Using clockworkmod recovery flash the root zip and then reboot into Android.
4) Use Root Explorer or some other file explorer with root access and get rid of whatever bloatware you don't want.
5) Reboot into clockworkmod recovery and flash the unroot zip.
6) Reboot phone
That will allow you root access to make any system changes and then unroot the phone to remove su privileges.
Yes u can root and remove bloat with titanium back up then unroot and then the bloat will still be gone. Also I believe u can unroot certain roms. Not sure
Sent from my LG-P999 using xda premium
thanks for your help
NP. Keep us updated? Everything work?
Sent from my LG-P999 using xda premium
I am about to get good next week hopefully , will post back.
I wonder why it wouldn't work on rooted phone's though?
It detects the presence of the su binary among other things and refuses to run.
buru898 said:
I wonder why it wouldn't work on rooted phone's though?
Click to expand...
Click to collapse
Sent from my LG-P999 using XDA App
Just bought a new TF. The serial is BCO..... Rooted via nachoroot. Superuser installed from market. Everything that requires root works except gnufabio's recovery installer app. Everytime I try to run the app, it keeps saying "sorry you are not rooted!"
Can't seem to find a cwm version that can be flashed via the stock recovery. Can someone please point me in the right direction? Thanks.
Added by edit.
Nevermind. Figured out what was wrong. Problem solved. Recovery installer works.
Share please.... I'm having the same problem and would like to know.
Thanks!
Have you tried installing it via ROM Manager?
I hope you don't have any light bleed issues..oh wait you won't care
Tripsyk said:
Have you tried installing it via ROM Manager?
Click to expand...
Click to collapse
ROM Manager not compatible with the TF as far as flashing CWM recovery.
drowe said:
Share please.... I'm having the same problem and would like to know.
Thanks!
Click to expand...
Click to collapse
Did you install ota rootkeeper, backup root, and tested out before trying to install the recovery installer app? That's what I did. To solve, you need to redo the rooting procedure.
goodintentions said:
Did you install ota rootkeeper, backup root, and tested out before trying to install the recovery installer app? That's what I did. To solve, you need to redo the rooting procedure.
Click to expand...
Click to collapse
Ti Backup, Ad Block, Root Check Basic all say I have root and I can read/write the / filesystem. Maybe because I did it with nachoroot.
Same here, on ww.8.6.6.23 rooted....but it says no root. I did install vodoo ota root keeper...already unistalled and deleted backup.
Sent from my Transformer TF101G using xda premium
Found the answer scanning other posts, I copied su from /system/bin to /system/xbin. I haven't removed the original su file.
Thank you Sir....you made my day.
Sent from my Transformer TF101G using xda premium
+1 on the thanks, I have also been looking for 2 days for this answer, You made my week...THANKS
IG1975
drowe said:
Found the answer scanning other posts, I copied su from /system/bin to /system/xbin. I haven't removed the original su file.
Click to expand...
Click to collapse
It seems easy right, what if my TF101 does not allow me to copy and past to the system files, even after downloading the proper Root Explorer files. Why is that why can't I just copy and paste, is there a way I can control this via PC?
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.
My wifes S3 is rooted but, stock and removed some bloat. She tried to do the OTA update and it downloaded but, failed of course. I have changed the OTA cert file name so it shouldnt allow OTA updates any longer. But, now it seems nightly it reboots into CWM to install the OTA update. What do I need to do to get that to stop?
This was the tips that someone gave me.
1. Use Titanium Backup to delete/uninstall SDM
2. Using a file explorer (e.g., Root Explorer), go to system/etc/security and change "Otacert.zip" to "Otacerts.zip.bak"
3. Using a file explorer, go to cache/fota and delete the file in there
Samsung.Galaxy.S3 said:
This was the tips that someone gave me.
1. Use Titanium Backup to delete/uninstall SDM
2. Using a file explorer (e.g., Root Explorer), go to system/etc/security and change "Otacert.zip" to "Otacerts.zip.bak"
3. Using a file explorer, go to cache/fota and delete the file in there
Click to expand...
Click to collapse
I had step 2 done but, will do 1 & 3 thanks!
For me the easiest was step one haven't had another update message since
Sent from my SCH-I535 using xda app-developers app
bump
bump for usefulness
Correct me if I'm wrong, but the OTA won't install because of cwm. The OTA does not know how to use it and causes it to fail.
If you want use Odin and flash the stock recovery and it will install just fine. Otherwise just freeze the app causing the update to download. I forgot the apps name at the moment but a simple search will reveal it name.
As for the update it self, its prolly just an updated modem. You can download thos in the development section and flash them in cwm.
Hope this helps out.
Sent from my Nexus 7 using xda premium