Database Users

DROID - Busybox Works, Then Doesn't

So I was trying to install Busybox on my DROID to use Metamorph and some other root applications. Stericson said I should be able to download via DroidSwap, but that didn't work so I went for the manual installation.
Following these instructions (http://www.novoda.com/blog/?p=3) I was able to successfully install Busybox on my phone. I typed busybox in the terminal and got a list of commands, I typed cp in the terminal and got the Copy syntax.
So I exited the terminal and went to perform something else and going back into the terminal I typed busybox again, except this time I get "busybox: busybox not found" ... I even navigated back to /data/busybox and if I do an ls of that directory the busybox file is in there, but I still get the "not found" when trying to run it.
Any thoughts as to why it would work once and now it doesn't.

Your best bet is probably to install it to /system/bin so it's in your path. Then you don't have to navigate anywhere to run busybox.
Just put the busybox binary into /system/bin and chmod to 755.

[Q] ONE-CLICK Root for Spica?

Hi Everyone,
I noticed to today that there are multiple application for 1-click root for some android phone like Droid X, Samaung Galaxy S, Nexus One, ...
Is there any application that roots the mentions phone can root Samsung Galaxy Spica GT-I5700 ?
Regards

Get Odin and the latest lk. Not as simple as one click, but it should not take more than five minutes.

Pr0fess0rX said:
Hi Everyone,
I noticed to today that there are multiple application for 1-click root for some android phone like Droid X, Samaung Galaxy S, Nexus One, ...
Is there any application that roots the mentions phone can root Samsung Galaxy Spica GT-I5700 ?
Regards
Click to expand...
Click to collapse
rooting with ODIN it's so easy, just input the file (kernel from samdroid v.LK2.08) and click start,
just one minutes your spica now is under root

Instructions
Sorry im a total noob. Can anyone link to descriptive instructions to root the Spica? I sooo scared..

i did it yesterday, not as hard as i though. just search "i5700 flashing" in youtube and you should find ~8min video.

2black0 said:
rooting with ODIN it's so easy, just input the file (kernel from samdroid v.LK2.08) and click start,
just one minutes your spica now is under root
Click to expand...
Click to collapse
Hi Friends, I found out an eassy way of rooting but before you start format your card with FAT32 and follow instructions as mentioned here -
http://www.addictivetips.com/mobile/root-samsung-galaxy-spica-i5700-with-leshaks-kernel/

Guys I did it already, With Odin is so wasy, I was just asking if there is a way more easier.
Thank you

Z4root is now available for spica.

z4root
z4 root working for spica go at this link
http://forum.xda-developers.com/showthread.php?t=833953
i have done it successfully both mode working temporary and permenant

z4root not work superuser...

Pr0fess0rX said:
Guys I did it already, With Odin is so wasy, I was just asking if there is a way more easier.
Thank you
Click to expand...
Click to collapse
Z4root is not a full root for spica or any other phone.
to get it follow these steps
Enjoy

Not fully one click but almost there
Install z4root 1.3.0.apk.
Install any terminal emulator apk.
Do the permanent root to get the superuser apk and su binaries installed.
(the permanent root does not work because the rfs filesystem used by the spica does not support the suid bit)
Then do a temporary root. (z4root creates a tmpfs filesystem which supports the suid bit).
Launch the terminal emulator.
Get root by typing su at the $ prompt. The superuser apk should ask for permissions. Allow the terminal.
The prompt should change to #.
Type dmesg > /sdcard/dmesg.txt
This should dump the boot logging output to dmesg.txt. Connect your phone to the PC or eject the sdcard and open dmesg.txt in any editor.
Search the log file for cannot find.
In my case it was
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
The important part is the "/system/etc" and the ".sh".
For some reason spica allows editing in the /system/etc directory which remains after reboots. Any edits to / do not remain after reboots.
If you dont have a cannot find error by init generated by a script in /system/etc then youre out of luck. The only way out is to run z4root and get a temporary root everytime (although it kind of makes the phone a bit unstable after the temporary root).
Then type
mount -o remount,rw,codepage=utf8,vfat,xattr,check=no /dev/stl5 /system
(wonder why this works, cos my device shows /system mounted as /dev/stl6. anyways it works)
Change directory to the system folder by typing
cd /system/sbin
Create a symbolic link to /xbin/su in /system/sbin. Do this because typically in the path variable /system/sbin comes before /system/bin (where z4root dumps the su binary). The suid bit is not set after reboot in the /system/bin/su so it dosent work.
ln -s /xbin/su /system/sbin/su
Have script prepared on your PC with the following lines:
#!/system/bin/sh
mkdir /xbin
mount -t tmpfs -o size=100k tmpfs /xbin
cat /system/bin/su > /xbin/su
chmod 6755 /xbin/su
Save it to your sdcard as the missing sh. In my case it was install-recovery.sh.
Copy it from the sdcard to the /system/etc folder by typing
cat /sdcard/install-recovery.sh > /system/etc/install-recovery.sh
Thats it.
Reboot when your done.
On reboot init should read the init.rc file in /. Then it should execute install-recovery.sh. (Just make sure the install-recovery.sh or whatever script is marked as oneshot in the init.rc file)
install-recovery.sh should create a small tmpfs partiition, copy the su binary there and set the suid permissions creating a permanent root.

I try to root my spica with super one click, android sdk and no work but i find a way to update cupkake 1,5 to eclair 2.1 with odin and finaly i made it . Than i use lkmod 2.5 to root but i cant find the super user or any root explorer in the phone and i dont know if my phone is root-ed or not ... any idea...?

one click root is impossible on spica

the stock OS on spica i think it was android 2.1, the one click root kits (at least the few i tried) didnt work on androdi 2.1
As soon as i flashed a 2.2/2.3 rom i had no problem rooting using z4root for example.

Where I can find the PDA for odin...
murat1369 said:
z4root not work superuser...
Click to expand...
Click to collapse
where I can find PDA file for odin..

[Q] Change resolution on Gingerbread

Hello guys,
I have downloaded the SD ram [JAN 28][REL]Cope's SD HD2 Gingerbread/CyanogenMod7. The build is awesome and my HD2 is totally trasformed. The only thing that worries me is the resolution because icons and fonts are extremely small. I tried to find where to change with no luck.
Can anyone help me to change this to normal resolution?
Thanx a lot.

Download a terminal emulator from the market and do the following:
1. Open terminal and type the following code:
su
cp /system/build.prop /sdcard/
2. Edit build.prop, it's on your sd card. Use a file editor on your phone or do it though a computer, whatever. The following needs to be changed: look for "lcd_density" and change its corresponding value to 240.
3. Open the terminal again:
su
cp /sdcard/build.prop /system/
4. Reboot

already tried, but says cp: not found
any idea?

You haven't installed Busybox... Download Titanium Backup (free version will do), launch it, and there will be a rather small button called 'Problems?'. Click it, let it do it's thing, maybe reboot, and then try again, should work. Are you sure you're rooted? If you just installed this emulator, it should have asked you for superuser permissions after you entered 'su'. If it didn't, download z4root on the market and root your phone, reboot afterwards and repeat the steps in my last post.

If you don't feel comfortable about editing build.prop manually, try LCD Density Changer from the market. You need Busybox installed either way.
Edit: there's a free version too: http://forum.xda-developers.com/showthread.php?t=765639, but the change won't stick after a cold reboot. Therefore you need the paid version.
Sincerely,
Mac

I downloaded the busybox through titanium backup but again on terminal when I enter cp it says cp: not found.
I search also the market for z4root application but market says it does not exist.
I have made the change on the prop file but I cannot copy it back on the system folder propably due to insufficient rights.
Is there any other way to copy the file back to \system since the cp command does not work?

Your problem is that you're not rooted, and without root you ain't gonna change any system file. Search for z4root here on xda or google and install it manually, or flash another rom which has root access by default (MDJ's Gingerbread for example - although sometimes you have to flash a second time).

Just rooted - unable to backup

Hi all,
Ive spent to weekend reading about rooting and ROMS/Kernels and decided to try it. I used a root kit found here from Mskip (great kit). Ive sucessfully rooted, and then sucessfully installed Smooth Rom 4.3 with the Motley kernel.
Ive downloaded Titanium Backup and Rom Manager. TB worked and I did a backup (which I now cant find) (i have ES File Explorer). I upgraded to Titanium Pro, and now when I open the app is states root was denied. I remember when I first opened TB SuperSu asked me to grant it access. After a reboot I opened SuperSu and stated a Binary update was necessary and performed it.
Now TB pro states root was denied, when I open SuperSu there is nothing there in the apps list, and I dont know how to manually grant TB root access.
Sorry if this is noobish, not sure what to do and I dont want to keep going without a backup.
Edit: When I try to backup in ROM Manager I hit backup, it brings up the notification to name the backup, I hit ok and nothing happens.

cam75 said:
After a reboot I opened SuperSu and stated a Binary update was necessary and performed it.
Now TB pro states root was denied, when I open SuperSu there is nothing there in the apps list, and I dont know how to manually grant TB root access.
Click to expand...
Click to collapse
That sort of sounds like the SuperSU "su" update might have failed. Can you get root with other apps? (e.g. go in to a terminal emulator and type "su")
Note there is a chicken-and-egg problem if (either) SuperSU/su or Superuser/su fail: they need root themselves to remount /system so that the "su" binary can be updated.
If no apps can get root, then you sort of have "lost root", and the fix is to manually insert the .apk and su binary into /system/app and /system/bin/su (or /system/xbin/su depending on flavor!) either with a flash package in recovery, or manually via the adb shell command line (with custom recovery running).
HTH
PS you should be able to just manually start the recovery and do a backup in the meantime, no? The fact that ROM manager isn't doing anything could either be a lack-of-root problem or something else (a busybox dependency?)

bftb0 said:
That sort of sounds like the SuperSU "su" update might have failed. Can you get root with other apps? (e.g. go in to a terminal emulator and type "su")
Note there is a chicken-and-egg problem if (either) SuperSU/su or Superuser/su fail: they need root themselves to remount /system so that the "su" binary can be updated.
If no apps can get root, then you sort of have "lost root", and the fix is to manually insert the .apk and su binary into /system/app and /system/bin/su (or /system/xbin/su depending on flavor!) either with a flash package in recovery, or manually via the adb shell command line (with custom recovery running).
HTH
PS you should be able to just manually start the recovery and do a backup in the meantime, no? The fact that ROM manager isn't doing anything could either be a lack-of-root problem or something else (a busybox dependency?)
Click to expand...
Click to collapse
thx for the quick response, however much of that is WAY over my head. I opened terminal emulator and typed su and this is what popped up. 1 [email protected]:/ $
When TB is opened it states error "sorry I could not acquire root privilegdes. this applidation will not work. please verify that your rom is rooted and try again. this attempt was made using the "/system/xbin/su" command.
I dont see busybox in my app drawer

cam75 said:
thx for the quick response, however much of that is WAY over my head. I opened terminal emulator and typed su and this is what popped up. 1 [email protected]droid:/ $
Click to expand...
Click to collapse
If the SuperSU app (and companion binary) were working correctly, you should have seen one of those "Accept / Deny" pop-up messages coming from the SuperSU app... assuming that you didn't previously grant root access to that terminal emulator app. You didn't mention that happening.... ?
Also, usually the command prompt usually changes from $ to # when you have root, but not always; the explicit way to check would be to (after you have tried the "su" command) to type in "id" and hit return at the prompt - that will tell you explicitly if you are root or not. (That's the letter "i" followed by the letter "d" followed by the return key).
From the way you describe this, it is sounding like you lost root.
I gotta go watch part of the game. In the meantime, perhaps you should at least create a backup manually.
As I said, the simplest fix-up would be to get Superuser.apk/su or SuperSU/su re-installed into /system/app and /system/{x}bin/su (it seems that chainsDD and chainfire use different locations).
There might be floating around someplace a flashable zip file with this stuff in it - to be used for "lightly rooting" a stock ROM after a custom recovery is in place. But things have been in flux recently with both the SuperSU (chainfire) and Superuser (chainsDD) kits because of the JellyBean multi-user support, so the version you might need is important. So you would have to do the research to figure out where.
gotta go - good luck.

bftb0 said:
If the SuperSU app (and companion binary) were working correctly, you should have seen one of those "Accept / Deny" pop-up messages coming from the SuperSU app... assuming that you didn't previously grant root access to that terminal emulator app. You didn't mention that happening.... ?
Also, usually the command prompt usually changes from $ to # when you have root, but not always; the explicit way to check would be to (after you have tried the "su" command) to type in "id" and hit return at the prompt - that will tell you explicitly if you are root or not. (That's the letter "i" followed by the letter "d" followed by the return key).
From the way you describe this, it is sounding like you lost root.
I gotta go watch part of the game. In the meantime, perhaps you should at least create a backup manually.
As I said, the simplest fix-up would be to get Superuser.apk/su or SuperSU/su re-installed into /system/app and /system/{x}bin/su (it seems that chainsDD and chainfire use different locations).
There might be floating around someplace a flashable zip file with this stuff in it - to be used for "lightly rooting" a stock ROM after a custom recovery is in place. But things have been in flux recently with both the SuperSU (chainfire) and Superuser (chainsDD) kits because of the JellyBean multi-user support, so the version you might need is important. So you would have to do the research to figure out where.
gotta go - good luck.
Click to expand...
Click to collapse
Thanks again.
Im watching Superbowl as well. I didnt grant Terminal access. I rebooted into recovery and restored to right after I rooted. SuperSu auto updated through the play store, and stated the binary need updated. I canceled that. TB and ROM manager are showing up in SuperSu. So now Im rebooting into recovery again to after I installed the Smooth Rom/Motley Kernal. I did make a backup of where SuperSu lost root. I now have three backups.
Question on installing the SuperSu apk file. I want to be sure I do it right, if needed. Download the file on my 7. it will go to my download folder. Move it to the system folder and open/run it? what do i do with the current SuperSu folder?
thanks again

I went to my restore point after root and reinstalled 4.3 Smooth ROM Mkernel. I did not take the SuperSu update, (ill wait for the next update) and everything is fine TB an ROM manager working fine, did a backup in both.
Thanks for your help on this.

cam75 said:
Question on installing the SuperSu apk file. I want to be sure I do it right, if needed. Download the file on my 7. it will go to my download folder. Move it to the system folder and open/run it? what do i do with the current SuperSu folder?
Click to expand...
Click to collapse
Dealing with .apk's is not that difficult - drop them into the correct place and reboot.
In Android, apps (.apk files) are stored in one of two places: /system/app or /data/app. It is even possible for two versions of an app to be on the phone - one in /system/app and one in /data/app; that is how upgrades of factory-installed apps happen: the pre-installed app is in /system/app... and never gets deleted (read-only filesystem), whereas update versions get dropped into /data/app. Generally you can just drop an .apk file into either of these locations, wipe the dalvik cache and reboot. During the android boot, these files are compiled into .dex objects in the dalvik-cache, and various version, consistency, rights and permissions are cross-checked.
Think of it this way: when you boot a new ROM for the first time, /data starts out completely empty. Everything needed to support each pre-installed app in /system/app gets created automatically during the android layer start-up.
The "su" native binary is a bit more complicated - it needs to be:
- owned by the user.group root.root
- be executable
- be setuid/setgid
Imagine that you had a copy of these two files on your "/sdcard". If you booted into the custom recovery, you could affect these changes like this:
C:\foo> adb shell
# mount # show what is already mounted
# mount /sdcard # if needed
# mount /system # if needed
# mv /system/app/SuperSU.apk /system/app/SuperSU.apk.old
# cp /sdcard/SuperSU.apk /system/app/SuperSU.apk
# mv /system/xbin/su /system/xbin/su.old
# cp /sdcard/su /system/xbin/su
# chown root.root /system/xbin/su
# chmod 6755 /system/xbin/su
# cd /
# umount /system
# exit
C:\foo>
*
As a practical matter, it is probably easier to just make sure to make a fresh backup if you are about to update the su binary - in case anything goes wrong. It might also be useful to use a root-aware file manager to remount the /system partition in rw mode prior to doing the "update su binary" procedure in the SuperSU app.
Good luck
* note that SuperSU and Superuser apps choose different locations for the su executable file - one uses /system/bin/su and the other /system/xbin/su. There might also be a symlink between these locations. Best policy is probably to examine a known-working installation to determine how to proceed.

How do i remove the su file in xbin

Hi, I'm using Samsung Note 3, i had never root my device. Usually, when i installed some official apps, i still be able to use it. However, when i updated those apps to the latest version recently, my device can no longer use the apps, those apps include some samsung official apps. I had checked those requirements for the apps to work, i had met those requirements like Minimum RAM, android version and etc..
So, i try to checked whether my phone is rooted or not using the "Root Checker" app. It shown as follow:
Root Access: No access
SU: su found [/system/xbin]
UID/GID: n/auid=10378(u0_a378)
gid=10378(u0_a378)
groups=3003(inet),50378(all_a378)
context=u:r:untrusted_app:s0
Unix Utils: n/a
PATH: /sbin
/vendor/bin
/system/sbin
/system/bin
/system/xbin
There is a su file found, but i never root my device.
1. Can i know is it possible for user accidentally rooted a phone when installing some unofficial app? or any other action that caused the existence of su file in my device?
2. I had installed "ES File Explorer", and tried to remove the su file by enabling the Root explorer, but it shown " the feature cannot run on your device", so i had tried to remove the su file by going to the "/", then "system", and "xbin", to remove the su file, but it shown that "su file cannot be deleted". Is there any possible way to remove the su file?
3. Lastly, does anyone know that my device can't run those apps is it whether caused by the "su" file or any other main problem?
Kindly need your help, please. Thank you in advance.
Note: Tested on Latest version of "pokemon go" app, same problem appears, unable to run the app as those official Samsung apps.