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!



Results 1 to 4 of 4
  1. #1
    Junior Member
    Points: 1,466, Level: 21
    Overall activity: 0%

    Reputation
    Reputation 10
    Join Date
    Jan 2012
    Location
    Salt Lake City, UT
    Posts
    27
    Phone
    M886



    Factory data reset issues... or, DAMNIT!

    Okay, a little back history. I have had my Mercury rooted for a while now, and have manually removed some bloatware, and used a modified version of the bloatware removal script, just to remove the SNS garbage. With the new update, of course it won't work, so I put the bloat back on with the installer, and restored the original recovery.img. As close to stock as I could get it. Did a factory data reset, and now Swype won't work, and the damn thing still won't update. Keeps having an error on Email.apk.
    So, I know I've seen it here before and can't find it now, but does anyone know how to get Swype functioning again? It is there, it just won't start. No errors or anything. It just won't run.
    I'm still on 2.3.5, running the stock recovery.img and haven't removed anything since the recovery.

    EDIT: I think I see a problem. The version of Swype that was installed by the Bloatware Installer script is 3.26.92.37742, and libSwypeCore is 3.23.89.33382

    Looks like Swype.apk that is installed from the script is newer than what I had.

    ---------- Post added at 07:29 PM ---------- Previous post was at 06:40 PM ----------

    I fixed it. I found the same version of libSwypeCore in the optimized rom from Oriax, and was able to get that into /system/lib and set the permissions using Super Manager. I can't seem to get the filesystem to mount rw in Linux. It wants to always mount read-only for some reason when mounting /dev/sd*12.

    Now, if I can figure out how to get the 2.3.6 official update without Muve, and get rid of the bloat.
    Last edited by moldavia; 04-08-2012 at 09:01 PM.

  2. Remove this advertisement.
  3. #2
    Recognized Dev |Łĝıť.|
    Points: 49,090, Level: 100
    Overall activity: 0%
    oriax123's Avatar
    Reputation
    Reputation 135
    Join Date
    May 2011
    Location
    Alamo, Texas
    Posts
    2,045



    Quote Originally Posted by moldavia View Post
    Okay, a little back history. I have had my Mercury rooted for a while now, and have manually removed some bloatware, and used a modified version of the bloatware removal script, just to remove the SNS garbage. With the new update, of course it won't work, so I put the bloat back on with the installer, and restored the original recovery.img. As close to stock as I could get it. Did a factory data reset, and now Swype won't work, and the damn thing still won't update. Keeps having an error on Email.apk.
    So, I know I've seen it here before and can't find it now, but does anyone know how to get Swype functioning again? It is there, it just won't start. No errors or anything. It just won't run.
    I'm still on 2.3.5, running the stock recovery.img and haven't removed anything since the recovery.

    EDIT: I think I see a problem. The version of Swype that was installed by the Bloatware Installer script is 3.26.92.37742, and libSwypeCore is 3.23.89.33382

    Looks like Swype.apk that is installed from the script is newer than what I had.

    ---------- Post added at 07:29 PM ---------- Previous post was at 06:40 PM ----------

    I fixed it. I found the same version of libSwypeCore in the optimized rom from Oriax, and was able to get that into /system/lib and set the permissions using Super Manager. I can't seem to get the filesystem to mount rw in Linux. It wants to always mount read-only for some reason when mounting /dev/sd*12.

    Now, if I can figure out how to get the 2.3.6 official update without Muve, and get rid of the bloat.
    The optimized 2.3.6 is the official stock firmware without muve. I just pulled it off my phone and optimized the pngs to use less space and ram. Then just use bloatware remover and your good to go.

    ~Sent by Oriax123
    Add me on Facebook.com/oriax123

    If I helped you, please click '*' at the bottom left of that post.



  4. #3
    Recognized Dev |Łĝıť.|
    Points: 49,090, Level: 100
    Overall activity: 0%
    oriax123's Avatar
    Reputation
    Reputation 135
    Join Date
    May 2011
    Location
    Alamo, Texas
    Posts
    2,045



    If using Linux try in terminal :

    nautilus

    Will open file manager with root permissions to edit those partitions.
    Might have to Google the command since I'm on mobile and can't recall the actual command

    ~Sent by Oriax123
    Add me on Facebook.com/oriax123

    If I helped you, please click '*' at the bottom left of that post.



  5. #4
    Junior Member
    Points: 1,466, Level: 21
    Overall activity: 0%

    Reputation
    Reputation 10
    Join Date
    Jan 2012
    Location
    Salt Lake City, UT
    Posts
    27
    Phone
    M886



    Quote Originally Posted by oriax123 View Post
    The optimized 2.3.6 is the official stock firmware without muve. I just pulled it off my phone and optimized the pngs to use less space and ram. Then just use bloatware remover and your good to go.

    ~Sent by Oriax123
    I was wondering what changes you made. So what is the suggested method of installing? Using the wipe tool first then installing through the custom recovery image? Looks like it formats /system and /data so the wipe shouldn't be necessary.
    I just wish I knew why the official update hangs up on Email.apk.

    ---------- Post added at 12:02 AM ---------- Previous post was at 12:00 AM ----------

    I don't have nautilus installed. I'm actually mounting it from the command line as root, as it appears recent Linux distros that try to use udev or dbus to do the mounting don't like to mount correctly, or let go of the mounted partitions on the phone. Oh well, there's other methods to get things to /system. Even if they are a few more steps.
    Last edited by moldavia; 04-09-2012 at 02:20 AM.

 

 

Thread Information

Users Browsing this Thread

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

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