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?
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.
Okay, first off, I have searched. For the last 3 hours I have searched!!
I foolishly used Razorclaws one-button root method and it worked, However everything after that point has been an utter failure. I tried to flash recovery, and nothing. I tried using CWM, and nothing. I open Super User and it just closes. I don't know what else to do. Yes, I saw post 275 in the razorclaw thread, but when I put in the command list, it tells me it doesn't recognize the command. I previously had a Nook Color and had the easy adb installed. I don't know if this is my problem. I have a B70 transformer, I just want to unroot. I tried the Super User update fixer, nothing. The Transformer is running fine, I get force closes on some apps. I just want to return to stock. Any help will be greatly appreciated.
I unrooted it. But the superuser apk remains in the app drawer. Is there any harm that can be done by having it? I would like to 'successfully' root and flash a rom, but judging from my inability to flash recovery using the one-button method I will wait. I would love to overclock this beast!
You can delete this thread, I apologize for wasting time and resources!
have you tried rebooting and then re-rooting?
how did you unroot ?
Sent from my tf101 using xda premium 1.54Ghz
To get rid of Super user app and binary
http://forum.xda-developers.com/showpost.php?p=19505946&postcount=221
Also if you want to try again and get SU working you can try this
http://forum.xda-developers.com/showthread.php?p=19555429
Thanks for the replies
I did not reboot and reroot, I did have to download the SDK in order to use the adb functions. I used the info provided by doaist to remove su permissions, I suppose. When I checked through the razorclaw app, and terminal. I was not given su access. So, I assumed I didn't have su permission.
And as soon as I try to get into the adb shell and type 'su' it says 'permission denied' , I don't know what else to do to remove it.
Thanks for your input guys, it means a lot.
Okay, so I redownloaded said apps, and I am now performing a backup. Which rom should I use? Which rom will allow me to retain stock functionality , and which OC kernal should I use. Is there a rom that has both?
When flashing recovery, does it go to the emmc or the extrernal sd???
woundedworld said:
When flashing recovery, does it go to the emmc or the extrernal sd???
Click to expand...
Click to collapse
External micro sd card
I backed up my app data with Titanium and went back to stock. So I'd like to restore my data but you need root for that. So I flashed superuser to gain root access, but is there a way to now 'unflash'?
Something through emulator and delete some binaries?
I see this: http://forum.xda-developers.com/showthread.php?t=1516740
which leads to: http://forum.xda-developers.com/showpost.php?p=7386761&postcount=2
Download ES File Explorer. In the app, go to Settings, and choose to go up to 'root level' If it asks for Superuser, go ahead and allow it. Remove /system/bin/su, or /system/xbin/su, and then remove /system/app/Superuser.apk. Reboot and enjoy your un-rooted phone.
mabry said:
...Remove /system/bin/su, or /system/xbin/su, and then remove /system/app/Superuser.apk...
Click to expand...
Click to collapse
Hey marby!
I've been looking for an answer to my issue but could not find it so may I ask you for help, please?
I have rooted my SGSIII (the process added CWM and superSU).
After a month I recieved the update to JB4.1.1; I installed it and the root acces disapeared but SuperSU app stills there!!
I want to root my phone again, do you know if I have to uninstall SuperSU before I manage to root with any method for JB 4.1.1?
Thank you very much in advance!
manohd87 said:
Hey marby!
I've been looking for an answer to my issue but could not find it so may I ask you for help, please?
I have rooted my SGSIII (the process added CWM and superSU).
After a month I recieved the update to JB4.1.1; I installed it and the root acces disapeared but SuperSU app stills there!!
I want to root my phone again, do you know if I have to uninstall SuperSU before I manage to root with any method for JB 4.1.1?
Thank you very much in advance!
Click to expand...
Click to collapse
No, but that's the wrong place to ask, since this is the Nexus S forums.
polobunny said:
...that's the wrong place to ask, since this is the Nexus S forums.
Click to expand...
Click to collapse
I'm sorry, since the subject was root/unroot I thought it will apply to any phone with JB 4.1.1
Thank you anyway! I will tell you later how it went!
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
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.