BoгИX

Moderator
  • Content count

    4,732
  • Joined

  • Last visited

  • Days Won

    134

BoгИX last won the day on April 6

BoгИX had the most liked content!

About BoгИX

  • Rank
    WTF Really?
  • Birthday 06/25/1986

Profile Information

  • Gender
    Male
  • Location
    somewhere in the mountains of North Carolina

More Info

  • Device
    XT1575

Recent Profile Visitors

20,512 profile views
  1. Can you link to the sammobile file you downloaded? Sent from my Nexus 6P using Tapatalk
  2. Wow. I'm astounded by how not surprised I am! Sent from my Nexus 6P using Tapatalk
  3. So get this: I got a N6P last week. I called in to activate, and the lady acted like I'd called in a bomb threat. I hung up and called back. Mark was very pleased that I knew what both an IMEI and SIM number were, and that I'd written them down and powered off both devices. (I got extra points for knowing how to *228!) But he had a very hard time. I waited on hold for ~30 seconds and this all took nearly an hour. Instead of lying and calling it a Nexus 6 like I had considered, I believed that they had all the kinks worked out. But Mark could not activate it as a Huawei Nexus 6P. But good news: there's a Google Nexus 6P code! "Just a couple more minutes, the system is slow today," he said, and we both had a good laugh about how "it was a day that ends with "Y". I told him about the 5X trick, and after a few minutes of that awkward phone support silence he decided to buck the system and try my idea. It didn't work. I told him about the Moto Nexus 6 trick. Still nothing. At this point the guy is determined to complete this task. He tried a few other phone models while I sat on hold for a few more minutes. When he came back on the line, he said he'd finally gotten a model code to work and that my phone was on the network, it's time to boot up and *228. USCC's completely incompetent system believes that my brand new Nexus 6P is actually a Galaxy S4, and wouldn't let me on their top of the line network that seems to be stuck in 2009 . FFS. I'm switching to Fi next week, and I recommend it highly. Fi is some for real next gen stuff. Sent from my Nexus 6P using Tapatalk
  4. The main consideration here is if/when root will be attainable again. Sent from my Nexus 6P using Tapatalk
  5. You'll see it here if there were! I wouldn't hold my breath if I were you though Sent from my thingyding straight to your eyeholes using Crapatalk.
  6. ...or 4 hours lol. Got busy. OP updated with download link!
  7. on it, gimme an hour to finish uploading lol
  8. Hello @sean19661, welcome to TeamUSCellular! Please use the search feature and read through the forums before posting a new question, oftentimes the answer is already right in front of you! See this post: Click here Also, we don't have any safestrap recovery for the Galaxy S5. US Cellular did not lock the bootloader for the GS5, so we can use normal custom recoveries.
  9. It sounds like your phone isn't being recognized in fastboot. I'll try to help, but keep in mind I've never used 2.3.5, so some of my tips may require a bit of interpretation. Boot the phone and plug it into your PC. Open a command prompt window (or cd to) the folder where the ADB executable is. Run "adb devices" without quotes. It'll launch a daemon and list your device if it's working properly. If it's not working properly it will either list your device as unavailable, or simply list nothing at all and go back to the terminal input. If it lists your device properly, I'll have to rethink some things. However, if it doesn't list it as ready, go into your phone settings, About Phone, and tap "Build Number" 7 times. This will enable Developer Options in your settings menu. Go into dev options and enable ADB Debugging. Unplug your phone and replug it and you should be prompted to allow access to your PC. Check the box to remember the permission and accept. Now retry the "adb devices" command. If it works this time, you should be good to retry your tool in the screenshot above. Is your phone in fastboot mode when you try the tool? If it isn't, then there's your problem. Google how to boot to fastboot for this phone, I have no idea how to do it myself. Hope this helps! If it doesn't, report back and we can try something else. Sent from my thingyding straight to your eyeholes using Crapatalk.
  10. Didn't they recall all the Note 7s, even the ones that had gotten battery replacements? It'll be extra impossible to get any customer service on a US regional phone that was supposed to be returned and is not even on the market. Sent from my thingyding straight to your eyeholes using Crapatalk.
  11. You're doing it all wrong bro. That's the official Xposed for AOSP, not the modified one for TW. Install this Xposed app: https://forum.xda-developers.com/attachment.php?attachmentid=3921508&d=1477916609 Then flash this Xposed framework: https://www.androidfilehost.com/?fid=529152257862685343 ::All hail the mighty Google:: Sent from my thingyding straight to your eyeholes using Crapatalk.
  12. You can't use the standard Xposed framework, you have to use a fork for TW. Hang on, I'll find you a link... Sent from my thingyding straight to your eyeholes using Crapatalk.
  13. First, the N5 is arm64, not sure if you took that into consideration. Second, which version of Android are you running? That will determine which SDK level to use: SDK21 = 5.0 Lollipop SDK22 = 5.1 Lollipop SDK23 = 6.0 Marshmallow If you're on Nougat, there is no Xposed for 7.0+ yet. Are you running stock TW or a custom AOSP ROM? Because TW ROMs require a special modified version of Xposed, you can't use the regular one. Sent from my Nexus 9 using Tapatalk
  14. What do you need in particular, the correct Xposed framework for the Note 5 (TW)? Sent from my thingyding straight to your eyeholes using Crapatalk.