Announcement

Collapse
No announcement yet.

Android Rooting issues with AT&T Skyrocket

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Android Rooting issues with AT&T Skyrocket

    So I rooted my phone a few weeks ago and I screwed up on it. While running Odin I accidentally unchecked the reboot option and my phone pretty much hung. So I unplugged it and pulled the battery and started the process all over. I don't know how I screwed it up but I did.

    Anyway I flashed Cyanogenmod and everything works great except for one thing. When I call someone I can't hear them and they can't hear me (or maybe I might be wrong on that but I definitely can't hear them). Works fine on speaker or Bluetooth but not through the phones speaker and microphone. I flashed it back to stock from a ROM I download off of XDA that was pretty close to stock (took me back to ICS or before that) and everything works that way but I have problems with the phone locking up whenever I reboot it. Unfortunately when I screwed everything up I didn't backup my stock ROM so that's why I downloaded a stockish one.

    Any ideas about this? I've posted on XDA but haven't gotten a good answer other than it sounds like it's a hardware issue but if that's the case why does it work with the stock ROM. If any good has come out of this I've got the rooting process down as well as flashing ROM's and backing up and restoring everything.

  • #2
    To begin with, any 4.2 and on rom is gonna be an alpha or beta at best and until Samsung publishes binaries for 4.2/4.3,there are gonna be issues since yall are using a "hacked up" 4.1 kernel.

    Having said that, try different kernels to see if they remedy the mic/speaker issue. The other problem(s) with stock are unrelated.

    Edit:You could also try this version of CM. It's not going to have some of the features of the later ones, but it's classified as Stable, so it'll have the least of any problems. http://get.cm/get/9b0 from


    Saved and Texan by the Grace of God, Redneck by choice.
    Last edited by Tx Redneck; 09-05-2013, 01:41 PM.

    Comment


    • #3
      I've tried the stable version of CM going back a few versions to make sure it's still stable and I still have the issues. Someone on XDA had mentioned it might be a Kernel issue but changed that since they felt if it's working on speaker and Bluetooth it shouldn't be an issue. I'll have to read up more on it.

      Either way I'm at least happy to have a somewhat working device now that I know what will work. I'm still 6 or so months away from an upgrade and I may start looking at buying a used Galaxy S3 if this bugs me enough.

      Comment


      • #4
        Have you tried doing a factory reset to get it back to bone stock unrooted? I had a similar issue once and this was how I managed to fix it. I also have an S3 and just downloaded the stock unrooted rom and installed it. I'm on Sprint but the stock firmware for your at&t should be in this thread in the first post. http://forum.xda-developers.com/show...stock+unrooted
        "You wouldn't know what crazy was if Charles Manson was eating Fruit Loops on your front porch"

        Comment


        • #5
          Originally posted by AdRock View Post
          Have you tried doing a factory reset to get it back to bone stock unrooted? I had a similar issue once and this was how I managed to fix it. I also have an S3 and just downloaded the stock unrooted rom and installed it. I'm on Sprint but the stock firmware for your at&t should be in this thread in the first post. http://forum.xda-developers.com/show...stock+unrooted
          I didn't have the stock ROM as I had to wipe my phone when I screwed up the Root. Regardless, I downloaded a stockish ROM and it works fine until I reboot it and than it locks up. I do not have to original ROM to restore from as I had to wipe the phone when I screwed it up and didn't have a chance to do a backup.

          Comment


          • #6
            Forget the s4 they made the last upgrade to where you cant change the boot loader. Only a way to root it has been found so far. Between Verizon and att there is over 15k bounty for the person who figures out how to get around it.
            FUCK ATT shit heads pushed the update when I was asleep. You can only postpone the upgrade a few times before it dont ask just does it. My fault for not having the update part froze.

            Comment


            • #7
              Originally posted by sig239 View Post
              Forget the s4 they made the last upgrade to where you cant change the boot loader. Only a way to root it has been found so far. Between Verizon and att there is over 15k bounty for the person who figures out how to get around it.
              FUCK ATT shit heads pushed the update when I was asleep. You can only postpone the upgrade a few times before it dont ask just does it. My fault for not having the update part froze.
              No way to odin back to the stock firmware? Surprised no one has found a way around that yet, Samsung is typically pretty easy to work with.

              But, shit like this is why I'll stick to nexus devices from now on.

              Comment


              • #8
                Originally posted by 90GT50 View Post
                No way to odin back to the stock firmware? Surprised no one has found a way around that yet, Samsung is typically pretty easy to work with.

                But, shit like this is why I'll stick to nexus devices from now on.
                Nope no way so far. The bootloader has certain software keys that get tied to the hardware, and when a new bootloader is put on the phone it also blows some qfuses that prevent older bootloaders from flashing. With up to 15k bounty on a fix its only a mater of time. I hope. They have a somewhat of a work around in the works with safe strap.

                Comment


                • #9
                  Originally posted by sig239 View Post
                  Forget the s4 they made the last upgrade to where you cant change the boot loader. Only a way to root it has been found so far. Between Verizon and att there is over 15k bounty for the person who figures out how to get around it.
                  FUCK ATT shit heads pushed the update when I was asleep. You can only postpone the upgrade a few times before it dont ask just does it. My fault for not having the update part froze.
                  I guess I'm going to start looking around for a used S3 than. I'm surprised they haven't figured it out with the S4 but I'm sure all they need is more time. Guess I need to visit the S4 forum on XDA as well.

                  Comment


                  • #10
                    On a side note, with all the problems I've had since screwing up my root. Since switching to CM10 I've been getting some amazing battery life. Regularly over 24 hours with my normal usage.

                    Comment


                    • #11
                      C'mon you dfwm ballas, if you want an S4 sans Ft Knox, pay up and get the GPE. It's the next best thing to a Nexus, or wait a lil longer and get the Nexus5

                      Saved and Texan by the Grace of God, Redneck by choice.

                      Comment


                      • #12
                        What's a GPE??

                        Comment


                        • #13

                          Saved and Texan by the Grace of God, Redneck by choice.

                          Comment


                          • #14
                            Ahhh! Google Play Edition. So can these be rooted as well or will they have the same problems as mentioned before?

                            Comment


                            • #15
                              None of the locked down bull feathers like att/vzw.

                              Saved and Texan by the Grace of God, Redneck by choice.

                              Comment

                              Working...
                              X