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 1 of 8 1 2 3 ... LastLast
Results 1 to 15 of 109
  1. #1
    Senior Member
    Points: 11,591, Level: 70
    Overall activity: 0%
    salas's Avatar
    Reputation
    Reputation 49
    Join Date
    Aug 2011
    Location
    Houston, Texas, United States
    Posts
    1,677



    [ROOT] How to Root the Cricket Huawei Mercury M886

    All credit goes to Tilbert at UnleashedPrepaids.com for finding how to root the mercury!!!

    MAKE SURE YOU READ ALL THE STEPS BEFORE STARTING!! additional setups may be required!!

    I AM NOT RESPONSIBLE FOR YOU MESSING UP YOUR PHONE BY FOLLOWING THESE INSTRUCTIONS!!!

    If your not comfortable with the procedure then don't do it!!!
    I'm sure it won't be long before someone smarter than me figures out a one-click method for root.




    1. First download su, busybox and Superuser.apk

    http://www.mediafire.com/?or723znkep9s3o3





    2. Use ADB to push these 3 files to /data/local/tmp


    3. In ADB shell:
    $ chmod 6755 /data/local/tmp/su
    $ chmod 755 /data/local/tmp/busybox
    $ chmod 644 /data/local/tmp/Superuser.apk


    4. Shut down phone with the power button/menu


    5. Holding the Vol+ AND Vol- AND Power together when the phone is off will put the phone into a mode that gives you a BRIGHT purple screen....
    this is good! Nothing should be happening, just a static purple screen.


    6. THIS NEXT STEP HAS TO BE DONE FROM A LINUX DISTRO!
    Plug the phone into the computer through USB and you will notice that you can access all of the partitions of the phone with full R/W.
    Browse to /data/local/tmp and move su and busybox to /system/bin/
    Move Superuser.apk to /system/app/


    7. Unplug the phone from USB


    8. Pull the battery out, put it back in, boot the phone normally and ENJOY YOUR NEWLY ROOTED MERCURY!!!!!!!!!!


    Some notes:
    Superuser.apk will need to be updated (found on market)
    From inside the Superuser app: update the su binary's
    Download the BusyBox installer from the market and update busybox to the latest version


    SEE post 5 for more information


    Last edited by Chris Rodriguez; 12-26-2011 at 09:45 AM.

  2. Remove this advertisement.
  3. #2
    Jumpmaster
    Points: 1,992,576, Level: 100
    Overall activity: 100.0%
    Chris Rodriguez's Avatar
    Reputation
    Reputation 444
    Join Date
    Oct 2010
    Customer Since
    Sept 2010
    Location
    Des Moines, IA
    Posts
    4,392
    Phone
    Note 3 / Galaxy S5



    Thank you for postings this find. I'm in the middle of nowhere with my laptop and a slower connection than I have at home or I would have done a video immediately.

    I need to setup a linux box anyways...
    Please check the forum and post there before PMing me. I have over 674 unread PMs due to the fact that they are issues which should have been addressed here.

    If you need to buy something from (Ebay), please use this LINK every time and support the forum!

  4. #3
    Senior Member
    Points: 11,591, Level: 70
    Overall activity: 0%
    salas's Avatar
    Reputation
    Reputation 49
    Join Date
    Aug 2011
    Location
    Houston, Texas, United States
    Posts
    1,677



    Quote Originally Posted by chrisngrod View Post
    Thank you for postings this find. I'm in the middle of nowhere with my laptop and a slower connection than I have at home or I would have done a video immediately.

    I need to setup a linux box anyways...
    or you can use Wubi

  5. #4
    Verified Developer
    Points: 3,291, Level: 35
    Overall activity: 0%
    PlayfulGod's Avatar
    Reputation
    Reputation 20
    Join Date
    Aug 2011
    Location
    NW Georgia
    Posts
    355



    a live cd/dvd should work too.

    Some try this for me

    Code:
    adb reboot fastboot
    or

    Code:
    adb reboot bootloader
    nm got my answer, bootloader will boot it. Only thing now is to figure out how boot n recovery are booting off the same partition so I can get CWM going.
    Last edited by PlayfulGod; 12-25-2011 at 08:10 PM.

  6. #5
    Verified Developer
    Points: 3,291, Level: 35
    Overall activity: 0%
    PlayfulGod's Avatar
    Reputation
    Reputation 20
    Join Date
    Aug 2011
    Location
    NW Georgia
    Posts
    355



    here this may help, has pix etc to help you see whats done:


    Article : How to Root Any Android Device Manually




    I have put together a zip to run the adb commands for you. The part done in download mode via a nix live cd/usb with nautilus tho I cant make easier for u. Its about like moving things around in windows tho with the gui.


    Mercury-Root.zip




    Just download the zip to your PC, unzip and run the appropriate install for your OS (windows-install.bat for Windows and linux-install.sh for Linux)

    You will need the drivers for the Mercury installed and USB Debugging enabled on your phone and if there is a internet connection option when connecting usb.

    And again, this only does the first part that pushes the files to the phone n sets permissions.

    ---------- Post added at 09:01 PM ---------- Previous post was at 08:43 PM ----------

    This is from the guide I found, all credit goes to its author. All I've done thus far is create some scripts for those no to cmdline savvy.

    Requirements and rooting process

    Requirements and rooting process


    • Your pitiable unrooted Android device
    • ADB drivers for your device installed on your pc (I used WinXP. You may use Win 7/Vista or the Linux distro of your choice)
    • su, busybox, Superuser.apk (included in the zip posted in the OP)
    • A working linux distro with Nautilus (I used a
      live usb stick of Ubuntu 11.04


      )
    • Strength, courage and whatever makes you a man according to Emerson.



    Rooting Process

    To start, you must have adb installed on the OS of your choice.
    I used my trusty WinXP system.

    To confirm your device is properly detected, in the command prompt, run
    Code:
    adb devices
    Now copy busybox, su, superuser.apk to /data/local/tmp/ using adb.

    Code:
    adb push busybox /data/local/tmp adb push su /data/local/tmp adb push Superuser.apk /data/local/tmp


    Now run adb shell

    Code:
    adb shell
    Note that you see a "$" sign in the command prompt. That means you are not rooted.
    Next run the following commands in the shell to change permissions and get some limited privileges for the Superuser files:

    Code:
    chmod 6755 /data/local/tmp/su chmod 755 /data/local/tmp/busybox chmod 644 /data/local/tmp/Superuser.apk
    Note that the names of the files are case sensitive.



    Done?
    Turn off your Android device using the power button.

    Now you need to reboot your system into a Linux distro which has Nautilus.
    Android and Linux, having a similar heritage, makes it possible for us to get root access over the Android phone if you are running with root privileges within Linux. I used an Ubuntu 11.04 Live USB disk to save the hassle of installing another os.

    When you have booted into Linux, open up terminal and type:
    Code:
    sudo nautilus
    This would open up the Nautilus file browser with root privileges.

    Now put your Android device into Download mode.
    For Spice MI-410/Huawei Ideos X6/CherryMobile Magnum HD/Wellcom A99 the method is to hold down the Volume up button and simultaneously turn on the phone using the power on switch.

    Once in download mode, connect the Android device using the microusb cable to the computer.
    Now using the open Nautilus window, navigate to /UserData/local/tmp/ folder and verify that you have the files you sent to the device viz. su, busybox and Superuser.apk

    Move/cut-paste su and busybox to /system/bin/ using Nautilus.
    Move/cut-paste Superuser.apk to /system/app/ using Nautilus.

    Now pull out the battery from your Android device.
    I swear, this was the most tedious part on my MI-410 which has such a crappy back cover.

    Now simply turn on your device.
    You must now have root.

    Verify by running:
    Code:
    adb shell su
    You'll note that the "$" prompt will turn into a "#" and you'll be prompted by a Superuser permission notification on your
    device



    You have now completed your initiation brethren.
    Welcome to the root club.



    Disclaimer:
    For all purposes, consider that your warranty will be void if you follow these steps

    I am not responsible for any loss, monetary or otherwise arising as a result of this article.
    If you don't feel up to it, quit now and close this web page.

    I must assert that although I am aware of no reason why this should not work on *any* Android device, phone or tablet, I have only tested this on my Spice MI-410 crossflashed with the leaked CherryMobile MagnumHD Gingerbread 2.3.4 firmware.

    I have tried to explain it in the easiest way I can, but I must state here that this is by no means an easy task and you must persevere. If you can't follow the steps to the letter, its better you don't follow them at all and wait for a single click app for this or a custom rooted firmware.
    He conquers who endures.






  7. #6
    Jumpmaster
    Points: 1,992,576, Level: 100
    Overall activity: 100.0%
    Chris Rodriguez's Avatar
    Reputation
    Reputation 444
    Join Date
    Oct 2010
    Customer Since
    Sept 2010
    Location
    Des Moines, IA
    Posts
    4,392
    Phone
    Note 3 / Galaxy S5



    Wubi install messed up after reboot. It added the entry to the bootmanager, but it couldn't be started.
    Please check the forum and post there before PMing me. I have over 674 unread PMs due to the fact that they are issues which should have been addressed here.

    If you need to buy something from (Ebay), please use this LINK every time and support the forum!

  8. #7
    Verified Developer
    Points: 3,291, Level: 35
    Overall activity: 0%
    PlayfulGod's Avatar
    Reputation
    Reputation 20
    Join Date
    Aug 2011
    Location
    NW Georgia
    Posts
    355



    Quote Originally Posted by chrisngrod View Post
    Wubi install messed up after reboot. It added the entry to the bootmanager, but it couldn't be started.
    wubi should have installed grub

  9. #8
    Junior Member
    Points: 1,201, Level: 19
    Overall activity: 2.0%
    Cthulhu336's Avatar
    Reputation
    Reputation 11
    Join Date
    Nov 2011
    Customer Since
    July 2009
    Location
    Graham, NC
    Posts
    25
    Phone
    SSG s4 (jfltecri)



    Dumb question . . . but . .

    I had used the PDANet app to install drivers for the Huawei Ascend II, the Mercury isn't showing up in my devices list. What / where / can I get the Mercury drivers?


    Thanks

  10. #9
    Jumpmaster
    Points: 1,992,576, Level: 100
    Overall activity: 100.0%
    Chris Rodriguez's Avatar
    Reputation
    Reputation 444
    Join Date
    Oct 2010
    Customer Since
    Sept 2010
    Location
    Des Moines, IA
    Posts
    4,392
    Phone
    Note 3 / Galaxy S5



    Quote Originally Posted by Cthulhu336 View Post
    I had used the PDANet app to install drivers for the Huawei Ascend II, the Mercury isn't showing up in my devices list. What / where / can I get the Mercury drivers?


    Thanks
    There are drivers on the device... Those worked for me...
    Please check the forum and post there before PMing me. I have over 674 unread PMs due to the fact that they are issues which should have been addressed here.

    If you need to buy something from (Ebay), please use this LINK every time and support the forum!

  11. #10
    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



    Could someone please post the output of the mount command while booted into Linux and connected to the phone in download mode?

  12. #11
    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



    Still not able to get rw access to the system partition. It is #12 on the device, correct? Tried with my existing Fedora 16 install and with a Ubuntu 11.04 LiveCD.

    When I remount, specifying rw, it says rw until I try to actually write to the partion, then it goes back to ro. Booted into Linux now. Let me get some error messages to post.

    brb

    When I umount the parition, I get the following error, repeatedly:

    Message from syslogd@lusitania at Dec 26 14:39:56 ...
    kernel:[ 839.989620] journal commit I/O error


    Attempts to mount as rw:

    [root@lusitania mnt]# mount|grep sdc
    /dev/sdc12 on /mnt/sdc12 type ext4 (ro,relatime,user_xattr,acl,barrier=1,data=ordered )
    [root@lusitania mnt]# umount /dev/sdc12
    [root@lusitania mnt]# mount -o rw,noacl,barrier=0 /dev/sdc12 sdc12
    [root@lusitania mnt]# mount|grep sdc
    /dev/sdc12 on /mnt/sdc12 type ext4 (ro,relatime,user_xattr,barrier=0,data=ordered)
    [root@lusitania mnt]# umount /dev/sdc12
    [root@lusitania mnt]# mount -o rw,barrier=0 /dev/sdc12 sdc12
    [root@lusitania mnt]# mount|grep sdc
    /dev/sdc12 on /mnt/sdc12 type ext4 (rw,relatime,user_xattr,acl,barrier=0,data=ordered )
    [root@lusitania mnt]# touch sdc12/zzz
    touch: cannot touch `sdc12/zzz': Read-only file system
    [root@lusitania mnt]# mount|grep sdc
    /dev/sdc12 on /mnt/sdc12 type ext4 (ro,relatime,user_xattr,acl,barrier=0,data=ordered )
    From /var/log/messages:

    Dec 26 14:48:37 lusitania kernel: [ 1361.557619] EXT4-fs warning (device sdc12): ext4_clear_journal_err:4181: Filesystem error recorded from previous mount: IO failure
    Dec 26 14:48:37 lusitania kernel: [ 1361.557638] EXT4-fs warning (device sdc12): ext4_clear_journal_err:4182: Marking fs in need of filesystem check.
    Dec 26 14:48:37 lusitania kernel: [ 1361.559518] EXT4-fs (sdc12): warning: mounting fs with errors, running e2fsck is recommended
    Dec 26 14:48:37 lusitania kernel: [ 1361.561659] EXT4-fs (sdc12): recovery complete
    Dec 26 14:48:37 lusitania kernel: [ 1361.563379] EXT4-fs (sdc12): mounted filesystem with ordered data mode. Opts: barrier=0
    Dec 26 14:48:42 lusitania kernel: [ 1366.289115] EXT4-fs error (device sdc12): ext4_init_inode_table:1288: comm ext4lazyinit: Something is wrong with group 0
    Dec 26 14:48:42 lusitania kernel: [ 1366.289125] Used itable blocks: 427itable unused count: 0
    Dec 26 14:48:42 lusitania kernel: [ 1366.289130]
    Dec 26 14:48:42 lusitania kernel: [ 1366.289144] Aborting journal on device sdc12-8.
    Dec 26 14:48:42 lusitania kernel: [ 1366.292141] EXT4-fs (sdc12): Remounting filesystem read-only
    Dec 26 14:48:42 lusitania kernel: [ 1366.292177] EXT4-fs error (device sdc12) in ext4_init_inode_table:1331: IO failure
    Dec 26 14:52:21 lusitania kernel: [ 1584.964202] EXT4-fs error (device sdc12): ext4_put_super:801: Couldn't clean up the journal
    Dec 26 14:52:37 lusitania kernel: [ 1601.126451] EXT4-fs (sdc12): barriers disabled
    Dec 26 14:52:37 lusitania kernel: [ 1601.151737] EXT4-fs warning (device sdc12): ext4_clear_journal_err:4181: Filesystem error recorded from previous mount: IO failure
    Dec 26 14:52:37 lusitania kernel: [ 1601.151755] EXT4-fs warning (device sdc12): ext4_clear_journal_err:4182: Marking fs in need of filesystem check.
    Dec 26 14:52:37 lusitania kernel: [ 1601.156147] EXT4-fs (sdc12): warning: mounting fs with errors, running e2fsck is recommended
    Dec 26 14:52:37 lusitania kernel: [ 1601.157595] EXT4-fs (sdc12): recovery complete
    Dec 26 14:52:37 lusitania kernel: [ 1601.159091] EXT4-fs (sdc12): mounted filesystem with ordered data mode. Opts: barrier=0,nouser_xattr
    Dec 26 14:52:38 lusitania kernel: [ 1602.707117] EXT4-fs error (device sdc12): ext4_init_inode_table:1288: comm ext4lazyinit: Something is wrong with group 0
    So, I ran fsck, and this is what I got:

    [root@lusitania mnt]# fsck /dev/sdc12
    fsck from util-linux 2.20.1
    e2fsck 1.41.14 (22-Dec-2010)
    /dev/sdc12: recovering journal
    /dev/sdc12 contains a file system with errors, check forced.
    Pass 1: Checking inodes, blocks, and sizes
    Pass 2: Checking directory structure
    Pass 3: Checking directory connectivity
    /lost+found not found. Create<y>? no

    Pass 4: Checking reference counts
    Pass 5: Checking group summary information

    /dev/sdc12: ********** WARNING: Filesystem still has errors **********

    /dev/sdc12: 915/20481 files (0.0% non-contiguous), 69612/81920 blocks
    I suppose the thing to do is to allow fsck to create a lost+found dir, but I really don't know enough about Android to do this without asking for advice first. So does anybody that has successfully rooted the phone have a lost+found in the root of the 12th partition?
    Last edited by s23bog; 12-26-2011 at 02:13 PM.

  13. #12
    Gold Member
    Points: 1,159, Level: 18
    Overall activity: 0%

    Reputation
    Reputation 11
    Join Date
    Jul 2011
    Posts
    117



    Quote Originally Posted by Cthulhu336 View Post
    I had used the PDANet app to install drivers for the Huawei Ascend II, the Mercury isn't showing up in my devices list. What / where / can I get the Mercury drivers?


    Thanks
    hey Chris can you explain how you get the drivers installed that are on the device? I see the driver folders youre talking about I just don't know what to do with them. I'd appreciate it.

  14. #13
    Jumpmaster
    Points: 1,992,576, Level: 100
    Overall activity: 100.0%
    Chris Rodriguez's Avatar
    Reputation
    Reputation 444
    Join Date
    Oct 2010
    Customer Since
    Sept 2010
    Location
    Des Moines, IA
    Posts
    4,392
    Phone
    Note 3 / Galaxy S5



    Quote Originally Posted by papasmurf520 View Post
    hey Chris can you explain how you get the drivers installed that are on the device? I see the driver folders youre talking about I just don't know what to do with them. I'd appreciate it.
    Off the top of my head, all I can recall doing is turning on USB debugging. After that it showed up in my device manager, and I updated the driver to the one I thought was appropriate.

    Windows 7:

    Right click > update driver > browse my computer for driver software > let me pick from a list of device drivers on my computer > have disk > browse > find the driver folder and you'll select the .inf file.
    Please check the forum and post there before PMing me. I have over 674 unread PMs due to the fact that they are issues which should have been addressed here.

    If you need to buy something from (Ebay), please use this LINK every time and support the forum!

  15. #14
    Gold Member
    Points: 1,159, Level: 18
    Overall activity: 0%

    Reputation
    Reputation 11
    Join Date
    Jul 2011
    Posts
    117



    Quote Originally Posted by chrisngrod View Post
    Wubi install messed up after reboot. It added the entry to the bootmanager, but it couldn't be started.
    Quote Originally Posted by chrisngrod View Post
    Off the top of my head, all I can recall doing is turning on USB debugging. After that it showed up in my device manager, and I updated the driver to the one I thought was appropriate.

    Windows 7:

    Right click > update driver > browse my computer for driver software > let me pick from a list of device drivers on my computer > have disk > browse > find the driver folder and you'll select the .inf file.
    Ah ok. Thanks. I got it to work on my own too. So either way I guess.

    Here's what I did. I right clicked command prompt and clicked run as administrator . Then I typed in cd and the direct path where the inf file was located. So for example I typed in cd C:\Program Files (x86)\Android\android-sdk\drivers\adb_driver

    Then I typed in
    PnPUtil -i -a android_winusb.inf
    Now there's a device when I type in adb devices in the command prompt.
    Last edited by papasmurf520; 12-27-2011 at 09:12 PM.

  16. #15
    Gold 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
    Still not able to get rw access to the system partition. It is #12 on the device, correct? Tried with my existing Fedora 16 install and with a Ubuntu 11.04 LiveCD.

    When I remount, specifying rw, it says rw until I try to actually write to the partion, then it goes back to ro. Booted into Linux now. Let me get some error messages to post.

    brb

    When I umount the parition, I get the following error, repeatedly:

    Message from syslogd@lusitania at Dec 26 14:39:56 ...
    kernel:[ 839.989620] journal commit I/O error


    Attempts to mount as rw:



    From /var/log/messages:



    So, I ran fsck, and this is what I got:



    I suppose the thing to do is to allow fsck to create a lost+found dir, but I really don't know enough about Android to do this without asking for advice first. So does anybody that has successfully rooted the phone have a lost+found in the root of the 12th partition?
    I'm having the same luck as s23bog. I'm unable to root my phone because I can't get read/write permission to the drive that has the bin and app directory in it. When I try to change the permission from clicking properties it says I can't because it's read-only. So I'm unable to cut and paste anything onto it. Also nowhere on any drives does it have the path /system/bin/ and /system/alpha system on one drive contains totally different subdirectories and data/local/tmp doesn't exist. However on one drive there's local/tmp and all three files on there. Just letting you guys know. I'd appreciate the help!
    Last edited by papasmurf520; 12-28-2011 at 12:50 PM.

 

 
Page 1 of 8 1 2 3 ... 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) Advertise with us? (Position 2 - QualityCricketPhones) Advertise with us? (Position 3 - Advertise with Us) Advertise with us? (Position 4 - Advertise with Us) Small Banner