Okay I've been searching around and believe me I have, but there is just a lack of answers here for me. So I'm making my own post for this.
I recently used a rooted package of the rogers stock gingerbread. Only thing was the OP included root in his back to stock. Below is a link to the ROM I used.
http://forum.xda-developers.com/showthread.php?t=1193927
How can I remove the root?
(Please don't say super one click because it doesn't work for me for some reason)
I'm not 100% sure if his Rom is even true stock. I'm wanting to return to true 2.3.3 gingerbread stock without root.
Right now I'm on stock 2.3.3 gingerbread for Rogers.
If I can get some info, maybe from our fellow Rogers members here on how they get rid of their root it would be so appreciated.
Thanks.
---------------------
EDIT:
DOES anybody know how to get a Rogers 2.3.3 Stock rom that isnt modified or rooted that you can flash with odin?
I've searched like mad for answers and im just wondering if someone who is running the pure stock rom can package it for me or something because I have no clue how to do these things.
Sent from my SAMSUNG-SGH-I997R using xda premium
Did you get an error message when you used the unroot from Super One Click? If so, what was it?
That package is complete stock, just with root, but I'm not sure how you would remove root.
Sent from my phone. :3
Sarius24 said:
Okay I've been searching around and believe me I have, but there is just a lack of answers here for me. So I'm making my own post for this.
I recently used a rooted package of the rogers stock gingerbread. Only thing was the OP included root in his back to stock. Below is a link to the ROM I used.
http://forum.xda-developers.com/showthread.php?t=1193927
How can I remove the root?
(Please don't say super one click because it doesn't work for me for some reason)
I'm not 100% sure if his Rom is even true stock. I'm wanting to return to true 2.3.3 gingerbread stock without root.
Right now I'm on stock 2.3.3 gingerbread for Rogers.
If I can get some info, maybe from our fellow Rogers members here on how they get rid of their root it would be so appreciated.
Thanks.
Sent from my SAMSUNG-SGH-I997R using xda premium
Click to expand...
Click to collapse
Maybe you can find a stock Rodgers kernel?
Have you tried factory data reset?
Also I'm pretty sure I mentioned this in a previous thread to you but, you can manually remove root by removing the superuser app then, find "su" binary file with root explorer and delete that too, busybox will probly have to go too.
wx690 said:
Did you get an error message when you used the unroot from Super One Click? If so, what was it?
Click to expand...
Click to collapse
The program freezes up every single time I dont know why. To the above poster. I still need superuser to access root explorer. Oh lordy this is tough to get rid of. And yeah I have tried factory data reset. Superuser is like hard coded or something, so even after that I still have root.
i think if you go into the "how to root for rogers thread" and reinstall the stock rogers kernel with Odin and then go into samsung "ezupdater" and restore firmware it'll get rid of root and everything else on the phone.
Just a theory, but feel free to try that
You'll probably need an 'unroot' update.zip file which deletes the necessary files.
badhobz said:
i think if you go into the "how to root for rogers thread" and reinstall the stock rogers kernel with Odin and then go into samsung "ezupdater" and restore firmware it'll get rid of root and everything else on the phone.
Just a theory, but feel free to try that
Click to expand...
Click to collapse
Sorry that solution wont work . Thanks though.
Sarius24 said:
The program freezes up every single time I dont know why. To the above poster. I still need superuser to access root explorer. Oh lordy this is tough to get rid of. And yeah I have tried factory data reset. Superuser is like hard coded or something, so even after that I still have root.
Click to expand...
Click to collapse
Maybe you can do it through your PC?
I got rid of the root with z4root. Now getting rid of the SU I dont know how to find the SU binary.
Sarius24 said:
I got rid of the root with z4root. Now getting rid of the SU I dont know how to find the SU binary.
Click to expand...
Click to collapse
I have never heard Z4 root being used on the Infuse, sounds sketchy but ok haha I'm pretty sure its in the system/bin somewhere.
So what is the reason you are getting rid of root? Cuz if you no longer have root, you might not need to delete anything, search "root checker" in the market to find out if you are still rooted or not.
The reason why I need root off is because I have a protection plan that I pay into every month. If my phone were to break or anything happens to it, they imediatley switch the phone of anything of my choice. (That's how I went from Captivate to this) I need to keep the ROOT access off of it in case anything were to happen. And I only needed the root access in the first place just for the Camera 30FPS hack.
Anyway I did as you said and im going to post the logs.
For busy box:
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
BusyBox binary location:
BusyBox binary file information:
Installed BusyBox Version:
BusyBox is not sharing its version information
BusyBox supports the following applets:
BusyBox is not sharing its supported applets
For SU:
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 2.3.6.1 - Added clear log to menu in log tab, More languages, Bugfixes is installed!
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as root
Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location:
/sbin/su: No such file or directory
Alternate su type binary location:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
You can use 'find' to find the files on the filesystem. For example, in the adb shell, type
Code:
busybox find / -name 'su'
or
Code:
busybox find / -name 'busybox'
Of course, if you've deleted busybox then issuing the above commands would be difficult.
On my Infused 2.2.3 install, the 'su' and 'busybox' are located in the following:
/system/xbin/su
/system/bin/su
/voodoo/extensions/su
/system/xbin/busybox
/bin/busybox
/system/app/Superuser.apk
/voodoo/extensions/su/Superuser.apk
I've attached an update.zip file (rename it as such) which will delete those files. The script is as follows:
Code:
assert(getprop("ro.product.device") == "SGH-I997R" ||
getprop("ro.build.product") == "SGH-I997R" ||
);
show_progress(0.1, 0);
mount("MTD", "system", "/system");
delete("/system/bin/su");
delete("/system/xbin/su");
delete_recursive("/voodoo/extensions/su");
delete("/system/xbin/busybox");
delete("/bin/busybox");
delete("/system/app/Superuser.apk");
unmount("/system");
show_progress(0.1, 10);
Should you decide to use my script, I'm not responsible for breaking things on your phone.
Your stock may contain some differences to Infused. To make an update script that's custom to your phone, I would do the same exercise I did in order to ensure that everything that needs to be removed is actually removed (for example, I am not sure whether you have the the /voodoo directory and if so, whether it needs to be removed).
wx690 said:
You can use 'find' to find the files on the filesystem. For example, in the adb shell, type
Code:
busybox find / -name 'su'
or
Code:
busybox find / -name 'busybox'
Of course, if you've deleted busybox then issuing the above commands would be difficult.
On my Infused 2.2.3 install, the 'su' and 'busybox' are located in the following:
/system/xbin/su
/system/bin/su
/voodoo/extensions/su
/system/xbin/busybox
/bin/busybox
/system/app/Superuser.apk
/voodoo/extensions/su/Superuser.apk
I've attached an update.zip file (rename it as such) which will delete those files. The script is as follows:
Code:
assert(getprop("ro.product.device") == "SGH-I997R" ||
getprop("ro.build.product") == "SGH-I997R" ||
);
show_progress(0.1, 0);
mount("MTD", "system", "/system");
delete("/system/bin/su");
delete("/system/xbin/su");
delete_recursive("/voodoo/extensions/su");
delete("/system/xbin/busybox");
delete("/bin/busybox");
delete("/system/app/Superuser.apk");
unmount("/system");
show_progress(0.1, 10);
Should you decide to use my script, I'm not responsible for breaking things on your phone.
Your stock may contain some differences to Infused. To make an update script that's custom to your phone, I would do the same exercise I did in order to ensure that everything that needs to be removed is actually removed (for example, I am not sure whether you have the the /voodoo directory and if so, whether it needs to be removed).
Click to expand...
Click to collapse
^To the above poster thanks a lot. Only thing is I dont have CWM so I can't run an update script =S.
Also I used this:
http://forum.xda-developers.com/showthread.php?t=1193927
Whenever I do a factory reset, the root comes back. I realized this today after removing the root and everything.
What I need was like a pure stock rogers 2.3.3 that has not been modified at all to put back on my phone. But It doesnt seem to be anywhere =S.
K im really really willing to pay someone to get a pure stock rogers gingerbread 2.3.3 odin flash. Like I will pay someone to do it because im that desperate...
Related
With the help of jt1134, we managed to get clockworkmod installed and functional on a Samsung Mesmerize. This will assume you have the android SDK installed and some knowledge of how to use adb.
First off you need to have your phone rooted. This can be done with SuperOneClick. You will also need a couple of files, recovery.bin and redbend_ua, both of which are attached to this post.
You will need to install redbend_ua first extract the zip file then;
Code:
adb push path/to/redbend_ua /sdcard/redbend_ua
then you need to make it executable
Code:
adb shell
su
chmod 777 /sdcard/redbend_ua
Now you need to move it to the /system/xbin
Code:
adb shell
su
mv /sdcard/redbend_ua /system/xbin/redbend_ua
Extract the recovery.zip and then we push the recovery.bin to the sd card.
Code:
adb push path/to/recovery.bin /sdcard/recovery.bin
Finally we need to flash the recovery.bin
Code:
redbend_ua restore /sdcard/recovery.bin /dev/block/bml8
After this the only thing left to do is download Rom Manager from the market and install the clockworkmod for the Fascinate. This is working on my Mesmerize. Please leave feedback!
Nice! now if only I had a Mesmerize...
Congrats! Hope this gets US Cell folks more active...
hey guys this worked great for me! thanks. I ran into a problem though when trying to make the redbend_ua file executable while it was on my sdcard so i moved it to the root of my phone memory using root explorer, than I ran the command
adb shell
su
chmod 777 /redbend_ua
than to move the file I used the command
adb shell
su
mv /redbend_ua /system/xbin/redbend_ua
and than follow the remaining steps that thescorpion420 has posted up, it shouldnt take more than 5 minutes for the process, I am flashing a rom to my USCC mesmerize as we speak and I will report back!
Enjoy guys
And thanks to the devs for figuring this out.
rom
ok so i was able to install a rom and not get an error, however I am stuck on the samsung screen when the phone boots up, it makes the power on noise, however it wont start up. any suggestions?
I tried to reflash the phone with a different rom and here is what happens when I go to install the rom
Finding update package
opening update package
installing update
deleting files
formatting system
copying files
deleting files
deleting files
deleting files
deleting files
deleting files
deleting files
deleting files
deleting files
deleting files
deleting files
installation complete
install from sdcard complete
Any ideas??
working
hey guys, I freaked out and didnt think I had made a successful backup of my rom before messing with it but I found it and I got the phone to go back to stock. So now I'm going to try a few things to see if I can get some roms to install on this thing.
Wow... Awesome news. Subbed for updates. Now to read some tutorials on how to get through the whole process... Won't be doing any flashing until I see someone confirm they got it up and running.
help
i getting failed on redbend _ua cross device link please help lol what am i doing wrong
You could try
Code:
cat /sdcard/redbend_ua > /system/xbin/redbend_ua
more help lol
now i get permission denied on the last step any hints as to what the heck im missing her sorry ima noob
Nice. Very nice.
mesmerbelly said:
now i get permission denied on the last step any hints as to what the heck im missing her sorry ima noob
Click to expand...
Click to collapse
Did you chmod 777 redbend_ua?
mesmerize
Scorpion 420 I sent u a pm please read
hey guys, so after trying different roms by different devs none of them are working with my mesmerize, I keep having to revert back to the original rom on the phone. Does anyone have any idea whats going on? I hate the stock rom and I want to change it.
reply
Ill start flashing roms as soon as I get this recovery installed I need help with it in okc anyone need some extra cash in okc help me out ill pay
ok, so Im able to recover my phone back to stock all the time so what I'm looking for is someone who has a custom rom installed and has done a backup with clockworkmod and if they can upload the backup they made, I think this is going to be the easiest way to install roms on the mesmerize for now.
Thanks
help
why do i keep getting permission denied on the last step of the recovery prosess
Originally Posted by mesmerbelly:
now i get permission denied on the last step any hints as to what the heck im missing her sorry ima noob
Click to expand...
Click to collapse
make sure you're using the root prompt # rather than the standard prompt $. This is why you're getting permission denied.
OKAY. So I have clockworkmod installed but when I try to backup my ROM it reboots into the recovery thing and then fails to update using the update.zip that clockwork downloaded. What should I do?
Just because you can get Clockwork Recovery for the Fascinate working with Rom Manager does not mean that you can start flashing Fascinate specific ROMs and/or kernels to your Mesmerize. You still have a Mesmerize and until the ROMs are made for the Mezmerize, or at least compatible, you can't use them. This is a great first step, though.
People are already pulling ROMs apart to make some of them compatible so it won't be too much longer.
Sent from my SCH-I500 using XDA App
I'll just leave this here . . .
Flash in clockworkmod not made by me, thanks jt1134.
How would I go about pushing clockworkmod custom recovery via ADB/Terminal instead of using the D2Bootstrap.apk?
You don't and even if it did it wouldn't work because the D2, D2G, DX and Dpro have locked bootloaders stick with koush it has never done me wrong and I've been romming my D2 since we got root and roms back in september 2010.
Sent from my DROID2 using XDA App
newk8600 said:
You don't and even if it did it wouldn't work because the D2, D2G, DX and Dpro have locked bootloaders stick with koush
Click to expand...
Click to collapse
I'm just asking how the app can do something that a terminal can't? I don't know how to comprehend that, I would think that there would be a way.
I wonder if the apk will have any useful information. Thank you for the reply
fKngFtd said:
I'm just asking how the app can do something that a terminal can't? I don't know how to comprehend that, I would think that there would be a way.
Click to expand...
Click to collapse
I'm sure there is a way but why figure it out when it's already been done?
The app pushes files (not sure what) to locations (not sure where) that hijack the booting process on startup before getting to moto's software. If it sees a specific file (I think logwrapper.bin but I'm not sure) is boots into clockworkmod. If it doesn't it just boots like normal.
Sent from my DROID2 using XDA App
newk8600 said:
I'm sure there is a way but why figure it out when it's already been done?
Click to expand...
Click to collapse
I would like to figure out how so "I" won't need an app, and to hopefully bring more info to our Community of D2G owners. Just my own opinion.
You need to get the hijack file from Koush's App. Download droid2bootsrapper either from his site or the market. View it with your favorite zip viewer, say 7zip or Winrar. Look in the assets folder for the hijack file.
Adb push hijack to /system/bin
Chmod 755 hijack
Rename logwrapper to logwrapper.bin (in the /system/bin folder)
Symlink hijack to a new file called logwrapper ("cd /system/bin", "ln -s hijack logwrapper")
Don't try it if you don't know how to SBF.
Sent from my DROID2 GLOBAL using XDA App
Thank you bro, I will try and report back. The SBF is my friend, it has fixed my D2G multiple times. Hah
Sent from my DROID2 GLOBAL using Tapatalk
buryboi said:
You need to get the hijack file from Koush's App. Download droid2bootsrapper either from his site or the market. View it with your favorite zip viewer, say 7zip or Winrar. Look in the assets folder for the hijack file.
Adb push hijack to /system/bin
Chmod 755 hijack
Rename logwrapper to logwrapper.bin (in the /system/bin folder)
Symlink hijack to a new file called logwrapper ("cd /system/bin", "ln -s hijack logwrapper")
Don't try it if you don't know how to SBF.
Sent from my DROID2 GLOBAL using XDA App
Click to expand...
Click to collapse
I tried what you said and but I believe that there is another step?
# adb push hijack /system/bin
# mv /system/bin/logwrapper /system/bin/logwrapper.bin
# cd /system/bin
# ln -s hijack logwrapper
#
Do I need to flash the recovery still, I'm stuck.
(Edit)
I searched further into the apk, and found the recovery image along with *.sh scripts. All help is appreciated.
No, you cant "flash" recovery as the D2G has a locked bootloader.
I'm not positive, but when the App is installed there are additional files in /data (like an update.zip)
I dont know if the hijack loads that update.zip or not...I'm inclined to think it doesn't since most of the custom roms just include the hijack and the symlink and nothing else...
the .sh file is the script that runs when you press "reboot recovery" in the app.
There is another .sh script that runs adbd is su mode when your phone first boots.
To get into recovery type the following in terminal
$su
#touch /data/.recovery_mode
#reboot
When the phone boots, init.rc calls logwrapper, which symlinks to hijack, which checks for the file /data/.recovery_mode. If it finds that file, it unmount system and loads bootstrap/Clockwork Recovery. If it doesn't find it /data/.recovery_mode it creates it, just in case you're phone doesn't boot. When your phone successfully boots, Droid2Bootstraper.apk starts and deletes /data/.recovery_mode so that next time you boot you wont automatically go into Boostrap recovery.
If you dont have the Boostrapper app, then you will probably boot into recovery every time you restart your phone.
Gang, I've searched and couldn't find. I rooted the Sprint Nexus S 4G and installed CW recovery.
Would some one please be kind enough to point me on how to unroot and return to stock recovery for a return.
Thank you!
Why do you want to return it?
dmora01 said:
Why do you want to return it?
Click to expand...
Click to collapse
Exchanging for another, I appear to have a defective screen which flickers when phone is shaken.
Yeah this would be good to know, as when you unlock it there is now a big unlocked icon when booting. I could see a sprint rep throwing the phone in my face saying they can't support it.
r80ies said:
Yeah this would be good to know, as when you unlock it there is now a big unlocked icon when booting. I could see a sprint rep throwing the phone in my face saying they can't support it.
Click to expand...
Click to collapse
Use a file manager like Root Explorer or SuperManager (any file manager that can run with root access)
Delete /system/app/Superuser.apk
Delete /system/xbin/su
Delete /system/bin/su
Reboot the phone into the bootloader.
Plug the phone into USB.
Type "fastboot oem lock"
Good to go.
What about the custom CWM recovery?
oldblue910 said:
Use a file manager like Root Explorer or SuperManager (any file manager that can run with root access)
Delete /system/app/Superuser.apk
Delete /system/xbin/su
Delete /system/bin/su
Reboot the phone into the bootloader.
Plug the phone into USB.
Type "fastboot oem lock"
Good to go.
Click to expand...
Click to collapse
a2k said:
What about the custom CWM recovery?
Click to expand...
Click to collapse
Oh, my bad. Before deleting root, go to /system/etc and find whatever you renamed the install-recovery.sh file to, and rename it back to install-recovery.sh. Then follow my instructions to delete root, and once you reboot back into the ROM, it will erase ClockworkMod and install the stock recovery. That said, here is a set of updated instructions:
Use a file manager like Root Explorer or SuperManager (any file manager that can run with root access)
Go into /system/etc and find the install-recovery.sh file that you renamed originally, and rename it back to install-recovery.sh. (This will ensure that the stock recovery will be restored on first boot)
If you installed busybox, you'll have to delete it along with all the symlinks that it created.
Delete /system/app/Superuser.apk
Delete /system/xbin/su
Delete /system/bin/su
Reboot the phone into the bootloader.
Plug the phone into USB.
Type "fastboot oem lock"
Good to go.
Click to expand...
Click to collapse
oldblue910 said:
Oh, my bad. Before deleting root, go to /system/etc and find whatever you renamed the install-recovery.sh file to, and rename it back to install-recovery.sh. Then follow my instructions to delete root, and once you reboot back into the ROM, it will erase ClockworkMod and install the stock recovery. That said, here is a set of updated instructions:
Use a file manager like Root Explorer or SuperManager (any file manager that can run with root access)
Go into /system/etc and find the install-recovery.sh file that you renamed originally, and rename it back to install-recovery.sh. (This will ensure that the stock recovery will be restored on first boot)
If you installed busybox, you'll have to delete it along with all the symlinks that it created.
Delete /system/app/Superuser.apk
Delete /system/xbin/su
Delete /system/bin/su
Reboot the phone into the bootloader.
Plug the phone into USB.
Type "fastboot oem lock"
Good to go.
Click to expand...
Click to collapse
Many thanks!!!!
Titanium Backup did install busybox, how do I delete it along with all the symlinks that it created?
a2k said:
Titanium Backup did install busybox, how do I delete it along with all the symlinks that it created?
Click to expand...
Click to collapse
Did Titanium Backup install busybox into /system/xbin? If so, (I assume you have a nandroid backup just in case), I would delete absolutely everything in that folder except dexdump. If it installed busybox somewhere other than /system/xbin, then we'll cross that bridge when we get there.
oldblue910 said:
Did Titanium Backup install busybox into /system/xbin? If so, (I assume you have a nandroid backup just in case), I would delete absolutely everything in that folder except dexdump. If it installed busybox somewhere other than /system/xbin, then we'll cross that bridge when we get there.
Click to expand...
Click to collapse
I don't believe it to be installed in /system/xbin/ as the only two items showing there are:
dexdump
su
a2k said:
I don't believe it to be installed in /system/xbin/ as the only two items showing there are:
dexdump
su
Click to expand...
Click to collapse
OK check /system/bin then. Is BusyBox in there?
oldblue910 said:
OK check /system/bin then. Is BusyBox in there?
Click to expand...
Click to collapse
OldBlue, I really appreciate your assistance!
I feel really stupid, there are numerous files inside /system/bin, heck I stopped counting at 40!! I do not see a "BusyBox" file there, what should I look for?
a2k said:
OldBlue, I really appreciate your assistance!
I feel really stupid, there are numerous files inside /system/bin, heck I stopped counting at 40!! I do not see a "BusyBox" file there, what should I look for?
Click to expand...
Click to collapse
Yeah there will be a bunch. Do you have a terminal emulator installed? If so, go into the terminal emulator:
Type "su" (without quotes)
Type "busybox which busybox" (without quotes)
Tell me what it says.
oldblue910 said:
Yeah there will be a bunch. Do you have a terminal emulator installed? If so, go into the terminal emulator:
Type "su" (without quotes)
Type "busybox which busybox" (without quotes)
Tell me what it says.
Click to expand...
Click to collapse
I installed Terminal Emulator:
Typed: su
Typed: busybox which busybox
Response: busybox: not found
Although TB says:
Root Access: OK (BusyBox 1.16.0 from app)
a2k said:
I installed Terminal Emulator:
Typed: su
Typed: busybox which busybox
Response: busybox: not found
Although TB says:
Root Access: OK (BusyBox 1.16.0 from app)
Click to expand...
Click to collapse
Oh no wonder! You're all set then. BusyBox is located within Titanium Backup's data folder. You don't need to worry. BusyBox will go away when you uninstall Titanium. So just follow my updated instructions and you're good. Let me know if you have any problems. Make sure you have a nandroid backup of your ROM before you delete root, just in case! You can never be too careful!
Use a file manager like Root Explorer or SuperManager (any file manager that can run with root access)
Go into /system/etc and find the install-recovery.sh file that you renamed originally, and rename it back to install-recovery.sh. (This will ensure that the stock recovery will be restored on first boot)
If you installed busybox, you'll have to delete it along with all the symlinks that it created.
Delete /system/app/Superuser.apk
Delete /system/xbin/su
Delete /system/bin/su
Reboot the phone into the bootloader.
Plug the phone into USB.
Type "fastboot oem lock"
Good to go.
Click to expand...
Click to collapse
Quote: Go into /system/etc and find the install-recovery.sh file that you renamed originally, and rename it back to install-recovery.sh. (This will ensure that the stock recovery will be restored on first boot)
what if there is no install-recovery.sh file!!!!!! under system/etc?
i didnt delete it!!!!!!! i was woundering way everybody was talking about renameing it? i dont have that file..
spdwiz18 said:
Quote: Go into /system/etc and find the install-recovery.sh file that you renamed originally, and rename it back to install-recovery.sh. (This will ensure that the stock recovery will be restored on first boot)
what if there is no install-recovery.sh file!!!!!! under system/etc?
i didnt delete it!!!!!!! i was woundering way everybody was talking about renameing it? i dont have that file..
Click to expand...
Click to collapse
Hmmm....try just /etc. Is it in there? Every stock Android build since 2.3.1/GRH78 has had that file in there. It checks the MD5 hash of the current recovery and if it doesn't match up, it flashes the stock one over it. That's really strange.
oldblue910 said:
Hmmm....try just /etc. Is it in there? Every stock Android build since 2.3.1/GRH78 has had that file in there. It checks the MD5 hash of the current recovery and if it doesn't match up, it flashes the stock one over it. That's really strange.
Click to expand...
Click to collapse
Nope .... no such file. I even did a search for it with root explorer and it does not come up. If worse come to worse ill pull it from someone's Tom just so I have it on my phone. But I know I did not delete it.
Sent from my Nexus S 4G using XDA Premium App
That is very strange indeed. I wonder if Google didn't install it on the Nexus S 4G. Can any other NS4G owners verify if /etc/install-recovery.sh exists on your phone?
this was what happened
i rooted my samsung galaxy pocket gt-s5300 succesfully
i replaced superuser.apk file in "system\app" by new one
and again i copied new binary file "su" in system\bin.previously there was not su file in this directory
when i restart it superuser permission denied everything.and so now i cannot delete the su binary file i copied in system\bin directory
do anyone know the solution for this?
GAEENG said:
this was what happened
i rooted my samsung galaxy pocket gt-s5300 succesfully
i replaced superuser.apk file in "system\app" by new one
and again i copied new binary file "su" in system\bin.previously there was not su file in this directory
when i restart it superuser permission denied everything.and so now i cannot delete the su binary file i copied in system\bin directory
do anyone know the solution for this?
Click to expand...
Click to collapse
Really really really wrong section!!!!! This is not you're device thread!!
With that being said.
U should have not replaced anything!
Re-root your phone than swap your root control app or update the existing one. As u need one to allow permissions to the other!!
After that use tit backup and uninstall the other superuser app
Take care and pay attention to where are u posting
Sent from my GT-I9300 using xda premium
ver3go said:
really really really wrong section!!!!! This is not you're device thread!!
With that being said.
U should have not replaced anything!
Re-root your phone than swap your root control app or update the existing one. As u need one to allow permissions to the other!!
After that use tit backup and uninstall the other superuser app
take care and pay attention to where are u posting
sent from my gt-i9300 using xda premium
Click to expand...
Click to collapse
thank u my friend.
I really dont know where to post.i searched for almost 3 days.
Could u guide me?pls.
Thank u again
Sit tight. Mods have been asked to move your thread to the appropriate forum, they'll do it soonish.
Ver3go said:
Really really really wrong section!!!!! This is not you're device thread!!
With that being said.
U should have not replaced anything!
Re-root your phone than swap your root control app or update the existing one. As u need one to allow permissions to the other!!
After that use tit backup and uninstall the other superuser app
Take care and pay attention to where are u posting
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I FINALY FOUND MY PROBLEM
I have two binaries one in /system/xbin/su and the other in /system/bin/su
#ls -l /system/*/su gives me this:
-rwxrwxr- system sdcard_rw 380532 2013-05-22 17:13 su
-rwsr-xr-x root root 22236 2013-05-22 17:13 su
#chmod 06775 /system/bin/su gives me this:
unable to chmod /system/bin/su: readonly filesystem
#echo $PATH gives me this
/system/bin/su: /system/Xbin/su
so what should i do next?
is it possible to swap the path variables
i mean to make "echo $path give /system/Xbin/su:/system/bin/su"
10Q
Hello, i read a lot on google about root but didn't find the answears that i'm looking for, hope some of you can explain.
I want to access the /system of my phone to change hosts file for example.
I know i need root access for that of course but that is my question.
What is neccessary for that, is placing the su binary in
/system/xbin/su
enough to access /system?
do i have then root access? or i need busybox, superuser.apk and some commands also?
thank you guys
if you have su already pushed into system partition means you got root access but if you dont have supersu installed you can't manage permissions that an application would request
so it is just the *su binary* necessery without chmod or something else? (theoretic)