Sign Up Now FAQ
Signup Now
In order to make a post or to start a new thread and or to interact with other
members of this board, you wil need to create an account first.
If this is your first visit, be sure to check out the FAQ. You have to register before you can post. If you have any problems, please contact us.
Flash a phone to Cricket Wireless Become a supporting member of Cricket Users Forum

 
Welcome to Cricket Users!



Page 3 of 8 FirstFirst 1 2 3 4 5 ... LastLast
Results 31 to 45 of 109
  1. #31
    Member
    Points: 1,159, Level: 18
    Overall activity: 0%

    Reputation
    Reputation 11
    Join Date
    Jul 2011
    Posts
    117



    Quote Originally Posted by s23bog View Post
    If you copy/paste the output of mount, I can tell you.
    ubuntu@ubuntu:~$ mount
    aufs on / type aufs (rw)
    none on /proc type proc (rw,noexec,nosuid,nodev)
    none on /sys type sysfs (rw,noexec,nosuid,nodev)
    none on /dev type devtmpfs (rw,mode=0755)
    none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
    /dev/sdb1 on /cdrom type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=cp437, iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
    /dev/loop0 on /rofs type squashfs (ro,noatime)
    none on /sys/fs/fuse/connections type fusectl (rw)
    none on /sys/kernel/debug type debugfs (rw)
    none on /sys/kernel/security type securityfs (rw)
    none on /dev/shm type tmpfs (rw,nosuid,nodev)
    tmpfs on /tmp type tmpfs (rw,nosuid,nodev)
    none on /var/run type tmpfs (rw,nosuid,mode=0755)
    none on /var/lock type tmpfs (rw,noexec,nosuid,nodev)
    none on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
    binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
    gvfs-fuse-daemon on /home/ubuntu/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=ubuntu)
    /dev/sr0 on /media/WDTV type iso9660 (ro,nosuid,nodev,uhelper=udisks,uid=999,gid=999,io charset=utf8,mode=0400,dmode=0500)
    /dev/sr1 on /media/Mobile Partner type iso9660 (ro,nosuid,nodev,uhelper=udisks,uid=999,gid=999,io charset=utf8,mode=0400,dmode=0500)
    /dev/sdd1 on /media/D84D-2678_ type vfat (rw,nosuid,nodev,uhelper=udisks,uid=999,gid=999,sh ortname=mixed,dmask=0077,utf8=1,flush)
    /dev/sdd14 on /media/C320-1810_ type vfat (rw,nosuid,nodev,uhelper=udisks,uid=999,gid=999,sh ortname=mixed,dmask=0077,utf8=1,flush)
    /dev/sdd12 on /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b____ type ext4 (rw,nosuid,nodev,uhelper=udisks)
    /dev/sdd6 on /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b___ type ext4 (rw,nosuid,nodev,uhelper=udisks)
    /dev/sdd13 on /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b_____ type ext4 (rw,nosuid,nodev,uhelper=udisks)
    /dev/sda2 on /media/SYSTEM RESERVED type fuseblk (rw,nosuid,nodev,allow_other,blksize=4096,default_ permissions)
    /dev/sda3 on /media/Acer type fuseblk (rw,nosuid,nodev,allow_other,blksize=4096,default_ permissions)

  2. Remove this advertisement.
  3. #32
    Member
    Points: 1,458, Level: 21
    Overall activity: 0%
    s23bog's Avatar
    Reputation
    Reputation 16
    Join Date
    Nov 2011
    Customer Since
    4/2008
    Location
    Louisville, KY
    Posts
    197
    Phone
    Huawei Mercury



    cd /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b____

    It is the one for /dev/sdd12

    When you get to that directory, do an ls....you should see the app and bin directories.

  4. #33
    Member
    Points: 1,159, Level: 18
    Overall activity: 0%

    Reputation
    Reputation 11
    Join Date
    Jul 2011
    Posts
    117



    Quote Originally Posted by s23bog View Post
    cd /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b____

    It is the one for /dev/sdd12

    When you get to that directory, do an ls....you should see the app and bin directories.
    ubuntu@ubuntu:/media/57f8f4bc-abf4-0000-675f-946fc0f9f25b____$ ls -l bin/su
    -rwsr-sr-x 1 2000 2000 22228 2008-02-29 09:33 bin/su
    ubuntu@ubuntu:/media/57f8f4bc-abf4-0000-675f-946fc0f9f25b____$ ls -l bin/busybox-rwxr-xr-x 1 2000 2000 1867568 2011-10-03 23:01 bin/busybox
    ubuntu@ubuntu:/media/57f8f4bc-abf4-0000-675f-946fc0f9f25b____$ ls -l app/Superuser.apk
    -rw-r--r-- 1 2000 2000 785801 2008-02-29 09:33 app/Superuser.apk


    bin/su is colored red background with white text and bin/busybox is colored green text. app/Superuser.apk is just normal color. Does that mean anything?
    Last edited by papasmurf520; 12-31-2011 at 03:40 PM.

  5. #34
    Member
    Points: 1,458, Level: 21
    Overall activity: 0%
    s23bog's Avatar
    Reputation
    Reputation 16
    Join Date
    Nov 2011
    Customer Since
    4/2008
    Location
    Louisville, KY
    Posts
    197
    Phone
    Huawei Mercury



    Aha...methinks I see the problem. Do:

    sudo su
    chown bin/su
    chown bin/busybox
    chown app/Superuser.apk



    Then, don't forget to update Superuser.apk and busybox (there are numerous busybox installers in the market).

    Looks like that Windows batch file needs to be updated.
    Last edited by s23bog; 12-31-2011 at 03:51 PM.

  6. #35
    Member
    Points: 1,159, Level: 18
    Overall activity: 0%

    Reputation
    Reputation 11
    Join Date
    Jul 2011
    Posts
    117



    Quote Originally Posted by s23bog View Post
    Aha...mehinks I see the problem. Do:

    sudo su
    chown bin/su
    chown bin/busybox
    chown app/Superuser.apk



    Then, don't forget to update Superuser.apk and busybox (there are numerous busybox installers in the market).

    Looks like that Windows batch file needs to be updated.
    root@ubuntu:/media/57f8f4bc-abf4-0000-675f-946fc0f9f25b____# chown bin/su
    chown: missing operand after `bin/su'
    Try `chown --help' for more information.


    I used OPs and PlayfulGod's zips. They were both different versions.

  7. #36
    Member
    Points: 1,458, Level: 21
    Overall activity: 0%
    s23bog's Avatar
    Reputation
    Reputation 16
    Join Date
    Nov 2011
    Customer Since
    4/2008
    Location
    Louisville, KY
    Posts
    197
    Phone
    Huawei Mercury



    oops....correct those to

    chown root.root bin/su
    chown root.root bin/busybox
    chown root.root app/Superuser.apk

    ---------- Post added at 05:04 PM ---------- Previous post was at 04:53 PM ----------

    Wait a minute....isn't busybox supposed to go in /system/xbin?

    The directions I followed said that I believe. That is where my busybox is, and it is working for me. If just changing permissions doesn't do the trick, you might just mv it over there.

    mv bin/busybox xbin

    But the ownership of the files definitely needs to be corrected, so make sure you do that first.
    Last edited by s23bog; 12-31-2011 at 05:32 PM.

  8. #37
    Member
    Points: 1,183, Level: 18
    Overall activity: 0%
    davidolas's Avatar
    Reputation
    Reputation 10
    Join Date
    Aug 2011
    Location
    san diego
    Posts
    155
    Phone
    Huawei Mercury



    do all three files have to have read/write all the way down, cause user said read/write group only read and so on

    ---------- Post added at 03:15 AM ---------- Previous post was at 03:07 AM ----------

    Quote Originally Posted by s23bog View Post
    Thanks, Derrick. 10.04 worked for me.

    I still find it odd that there is not lost+found directory under /system; but I looked at my Zio and found no lost+found either. I guess it is so that some options are not allowed with the filesystem (perhaps journaling, or something). This probably causes problems with newer versions of Linux (perhaps just mount) that default to read-only when those options are not available.

    Also noted that Astro was unable to write to the partition (mount showed rw). I suspect it is for the same reason. Anybody know why there is no lost+found, and what the repercussions of not having that directory are?

    Oh...just recalled that the Zio is squashfs, so it makes sense that there is no lost+found on that.
    I seen a lost and found, i have the problem that i put files in right folders and still no go like papa smurf

    ---------- Post added at 03:49 AM ---------- Previous post was at 03:15 AM ----------

    Quote Originally Posted by s23bog View Post
    oops....correct those to

    chown root.root bin/su
    chown root.root bin/busybox
    chown root.root app/Superuser.apk

    ---------- Post added at 05:04 PM ---------- Previous post was at 04:53 PM ----------

    Wait a minute....isn't busybox supposed to go in /system/xbin?

    The directions I followed said that I believe. That is where my busybox is, and it is working for me. If just changing permissions doesn't do the trick, you might just mv it over there.

    mv bin/busybox xbin

    But the ownership of the files definitely needs to be corrected, so make sure you do that first.
    chown: cannot access 'bin/su' : no such file or directory

    tried the xbin , no go

    ---------- Post added at 03:57 AM ---------- Previous post was at 03:49 AM ----------

    Quote Originally Posted by papasmurf520 View Post
    Good call! I used 10.04 Ubuntu instead and I was able to paste the files into the directories. Except when did this and the files are in the right directories my phone still isn't rooted. I have no idea now why this is.


    Edit
    ----------------
    Ok after I redid the adb commands and everything I now have a superuser icon on my apps menu. However it denies ever app trying to get superuser access. I'll update if I fix it.
    i am exactly where you aresuper user app on phone now, put su and busybox in bin and nothing, if you figure out how to fix it please let me know

  9. #38
    Member
    Points: 1,458, Level: 21
    Overall activity: 0%
    s23bog's Avatar
    Reputation
    Reputation 16
    Join Date
    Nov 2011
    Customer Since
    4/2008
    Location
    Louisville, KY
    Posts
    197
    Phone
    Huawei Mercury



    You need to change the owner of the files.

    It should be root.root

    The chown command does that but you need to be in the correct directory to execute it. I explain that a post or two beforehand.



    Quote Originally Posted by s23bog:39988
    cd /media/57f8f4bc-abf4-0000-675f-946fc0f9f25b____

    It is the one for /dev/sdd12

    When you get to that directory, do an ls....you should see the app and bin directories.
    I got that info from the mount command. You directory will be different. You will have to cd to the correct directory before executing the chown commands.

    After doing that, do an ls -l on the files and I will let you know if they look right.

  10. #39
    Member
    Points: 1,159, Level: 18
    Overall activity: 0%

    Reputation
    Reputation 11
    Join Date
    Jul 2011
    Posts
    117



    Quote Originally Posted by s23bog View Post
    oops....correct those to

    chown root.root bin/su
    chown root.root bin/busybox
    chown root.root app/Superuser.apk

    ---------- Post added at 05:04 PM ---------- Previous post was at 04:53 PM ----------

    Wait a minute....isn't busybox supposed to go in /system/xbin?

    The directions I followed said that I believe. That is where my busybox is, and it is working for me. If just changing permissions doesn't do the trick, you might just mv it over there.

    mv bin/busybox xbin

    But the ownership of the files definitely needs to be corrected, so make sure you do that first.
    If changing the ownership you mean the chown commands. I did those thanks! They probably work. I'm still getting my superuser app but it's still constantly denying root access.

    You said get an updated superuser except the Superuser.apk file I've been using is from PlayfulGod's zip. I'm not totally sure if that's updated enough? Let me know I'd appreciate it.

    By the way happy new year!
    Last edited by papasmurf520; 01-02-2012 at 09:22 PM.

  11. #40
    Member
    Points: 1,183, Level: 18
    Overall activity: 0%
    davidolas's Avatar
    Reputation
    Reputation 10
    Join Date
    Aug 2011
    Location
    san diego
    Posts
    155
    Phone
    Huawei Mercury



    Quote Originally Posted by s23bog View Post
    You need to change the owner of the files.

    It should be root.root

    The chown command does that but you need to be in the correct directory to execute it. I explain that a post or two beforehand.





    I got that info from the mount command. You directory will be different. You will have to cd to the correct directory before executing the chown commands.

    After doing that, do an ls -l on the files and I will let you know if they look right.
    do i do it from linux

  12. #41
    Member
    Points: 1,458, Level: 21
    Overall activity: 0%
    s23bog's Avatar
    Reputation
    Reputation 16
    Join Date
    Nov 2011
    Customer Since
    4/2008
    Location
    Louisville, KY
    Posts
    197
    Phone
    Huawei Mercury



    Quote Originally Posted by davidolas View Post
    do i do it from linux
    Put the phone in download mode (volume up&down + power).
    Connect phone to PC via USB.
    Boot into Linux (Ubuntu 10.04), open up a terminal, then:

    sudo su
    mount|grep 12|grep media
    # (this should show you which partition is the system partition)
    cd /media/xxxxxxxx
    # (where xxxxxxxx is the directory found above)
    chown root.root bin/su
    chown root.root bin/busybox
    # (or xbin, if you have it there)
    chown root.root app/Superuser.apk

    # then report back the results of
    ls -l bin/su
    ls -l bin/busybox
    # (or, again xbin, if you have it there)
    ls -l app/Superuser.apk
    Last edited by s23bog; 01-01-2012 at 12:10 PM.

  13. #42
    Member
    Points: 1,183, Level: 18
    Overall activity: 0%
    davidolas's Avatar
    Reputation
    Reputation 10
    Join Date
    Aug 2011
    Location
    san diego
    Posts
    155
    Phone
    Huawei Mercury



    said this
    chown: changing ownership of 'bin/su' : Operation not permitted

    agh, nothing wants to work
    Last edited by davidolas; 01-01-2012 at 03:22 PM.

  14. #43
    Member
    Points: 1,458, Level: 21
    Overall activity: 0%
    s23bog's Avatar
    Reputation
    Reputation 16
    Join Date
    Nov 2011
    Customer Since
    4/2008
    Location
    Louisville, KY
    Posts
    197
    Phone
    Huawei Mercury



    What directory were you in when you tried?



    You also must be root when you do it.

    I.e. sudo su

  15. #44
    Member
    Points: 1,183, Level: 18
    Overall activity: 0%
    davidolas's Avatar
    Reputation
    Reputation 10
    Join Date
    Aug 2011
    Location
    san diego
    Posts
    155
    Phone
    Huawei Mercury



    davidolas@ubuntu:/media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__$ chown root.root bin/su
    chown: changing ownership of `bin/su': Operation not permitted

    ---------- Post added at 04:42 PM ---------- Previous post was at 04:41 PM ----------

    davidolas@ubuntu:/media/57f8f4bc-abf4-0000-675f-946fc0f9f25b__$ sudo su
    /sbin/su: 1: Syntax error: word unexpected (expecting ")")

    ---------- Post added at 04:46 PM ---------- Previous post was at 04:42 PM ----------

    @ubuntu:~$ sudo su
    [sudo] password for davidolas:
    /sbin/su: 1: Syntax error: word unexpected (expecting ")")

  16. #45
    Member
    Points: 1,458, Level: 21
    Overall activity: 0%
    s23bog's Avatar
    Reputation
    Reputation 16
    Join Date
    Nov 2011
    Customer Since
    4/2008
    Location
    Louisville, KY
    Posts
    197
    Phone
    Huawei Mercury



    sudo su - root

 

 
Page 3 of 8 FirstFirst 1 2 3 4 5 ... LastLast

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Advertise With Us?
Advertise with us? (Position 1 - Advertise with Us) Small Banner