Search the Community

Showing results for tags '4.4.2'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Blogs

  • TeamUSCellular Blog

Forums

  • **-[-READ BEFORE POSTING-]-**
    • * -[READ THIS THREAD]- * Common Q&A and our Terms!
    • Shoutbox
  • Team US Cellular
    • Contests and Giveaways
    • Site News and Blog
    • Reviews
    • General Discussion
    • Suggestion Box
    • (¯`·.¸¸.-> °º Birthdays º°
    • Ask The Employees
  • US Cellular
    • News
    • Rumor Mill
    • Contract & Billing
  • Android
    • Android Discussion
    • Android Development
  • Google Pixel
    • Pixel & Pixel XL Discussion and Development
  • Nexus 6P
    • Nexus 6P Discussion
    • Nexus 6P Development
  • Nexus 5X
    • Nexus 5X Discussion
    • Nexus 5X Development
  • Nexus 6
    • Nexus 6 Discussion
    • Nexus 6 Development
  • Apple iPhone
    • General Discussion
    • Development Q&A
  • Ubuntu for Android
    • General Discussion
  • Windows Phone
  • LG V20
    • LG V20 Discussion
    • LG V20 Development
  • LG G3
    • LG G3 Discussion
    • LG G3 Development
  • LG G4
    • LG G4 Development
    • LG G4 Discussion
  • LG G5
    • LG G5 Discussion
    • LG G5 Development
  • LG G Flex 2
    • G Flex 2 Discussion
    • G Flex 2 Development
  • Motorola Electrify M
    • Electrify M Discussion
    • Electrify M Development
  • Motorola Moto X
    • Moto X General Discussion
    • Moto X Development
  • Motorola Moto X (2nd Gen)
    • Moto X (2nd Gen) Discussion
    • Moto X (2nd Gen) Development
  • Moto X Pure Edition 2015
    • Moto X Pure Edition Discussion
    • Moto X Pure Edition Development
  • Motorola Moto G
    • Moto G General Discussion
    • Moto G Development
  • Samsung Galaxy S8
    • Galaxy S8 Discussion
    • Galaxy S8 Development
    • Galaxy S8 Plus Discussion
    • Galaxy S8 Plus Development
  • Samsung Galaxy S7
    • Galaxy S7 Discussion
    • Galaxy S7 Development
    • Galaxy S7 Edge Discussion
    • Galaxy S7 Edge Development
  • Samsung Galaxy S6
    • Galaxy S6 Discussion
    • Galaxy S6 Development
    • Galaxy S6 Edge Discussion
    • Galaxy S6 Edge Development
  • Samsung Galaxy Note 5
    • Note 5 Discussion
    • Note 5 Development
  • Samsung Galaxy Note 4
    • Note 4 General Discussion
    • Note 4 Development
  • Samsung Galaxy Note 3
    • Note 3 General Discussion
    • Note 3 Development
  • Galaxy Note Edge
    • Note Edge Discussion
    • Note Edge Development
  • Samsung Galaxy Mega
    • Mega General Discussion
    • Mega Development
  • Legacy Devices
    • BlackBerry
    • Samsung Galaxy S5
    • HTC Desire
    • HTC Hero S
    • HTC Merge
    • HTC Pro 7
    • HTC Wildfire S
    • Huawei Ascend II
    • LG Apex
    • LG Genesis
    • LG Optimus F7
    • LG Optimus U
    • LG Splendor
    • Motorola Defy XT
    • Motorola Electrify
    • Samsung Acclaim
    • Samsung ATIV Odyssey
    • Motorola Electrify 2
    • Samsung Axiom
    • Samsung Galaxy Note 2
    • Samsung Galaxy S Aviator
    • Samsung Galaxy S II
    • Samsung Galaxy S III
    • Samsung Gem
    • Samsung Galaxy S4
    • Samsung Note 7
    • Samsung Galaxy S4 Mini
    • Samsung Mesmerize
  • Tablets
    • Windows Phone Discussion
    • Asus Eee Pad Transformer
    • Windows Phone Apps & Media
    • Asus Eee Pad Transformer Prime
    • Galaxy Note 10.1
    • Galaxy Tab 8.9
    • Galaxy Tab 10.1
    • Galaxy Tablet 2 7.0
    • Galaxy Tablet 2 10.1
    • HP TouchPad
    • HTC Flyer
    • Kindle Fire
    • LG G Pad 7.0
    • Motorola Xoom
    • Nexus 7
    • Tab S2
    • LG GPad 8.0 V2
  • Other
    • The Lounge
    • Buy/Sell/Trade
  • Trash
    • Trash Bin

Categories

  • Google Apps
  • Alcatel Shockwave
  • Blackberry 9350
  • Blackberry 9850
  • HTC Desire
  • HTC Hero
  • HTC Merge
  • HTC One V
  • HTC Wildfire
  • Huawei Ascend II
  • LG Splendor
  • Motorola Electrify
  • Motorola Electrify 2
  • Motorola Electrify M
  • Moto X
  • Odin 3.09/3.10
  • Samsung Aviator
  • Samsung Axiom
  • Samsung Galaxy Note II
  • Samsung Galaxy S II
  • Samsung Galaxy S III
  • Samsung Galaxy S4
  • Galaxy S5
  • Samsung Mesmerize
  • Samsung Metrix
  • Samsung Repp
  • Samsung Galaxy S6
  • Samsung Note III
  • Samsung Galaxy Note 4

Found 7 results

  1. READ THROUGH FIRST BEFORE DOING. MAKE SURE IT APPLIES TO YOUR SITUATION. THREAD WAS WRITTEN FOR PEOPLE WHO WERE ON STOCK 4.3. ANYTHING BELOW 4.3 WILL NOT WORK WITH THESE FILES. SAME PROCESS, JUST NEED THE RIGHT FILES YOUR STOCK TOUCHWIZ VERSION. Works with Windows XP, Vista, 7, 8, 8.1, and 10. Hey guys. If you're an idiot like me, you might have flashed the wrong firmware for your phone and now the Galaxy SIII is as useful as a brick. Well, you've come to the right place. I accidentally flashed the MD4 radio on my SCH-R530U. After countless hours of research I finally conceived a plan on how to revive the phone. Symptoms of a Soft Brick: Bootloops, Stuck at Galaxy SIII screen, uhh and other stuff where the display actually turns on. If it does any of these, wrong thread. Symptoms of a HARD BRICK (what you're probably here for): Power does nothing, no output to display, no download mode, no recovery mode, computer recognizes it as QHUSBLOAD or something like that. ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Let's get fixing. You'll need: 16 or 32GB CLASS 10 Non UHC-I MicroSD Card (complicity matches internal memory of the phone, although I used a 32GB SD card for a 16GB phone and it worked just fine), a hardbricked Galaxy SIII duh, a Windows PC with a SD Card reader, MicroSD to full size SD card adapter, proper files (included later), a wall charger, and time. I'm writing this thread to try and not have people go through hours of research to get their phone back. 1. Download all the required files. 2. Make sure that the SD card is class 10, non UHC-I (I used a SanDisk Ultra 32GB card), and has no files on it. ALL FILES ON THE SD CARD WILL BE OVERWRITTEN. 3. Unzip the Win32DiskImager program and run as administrator. YOU MUST BE AN ADMIN ON THE PC. 4. Put the MicroSD card into the Micro to full size adapter and plug it into the PC (if you haven't already). In the DiskImager program, click on the drop-down box under device, and select the SD card's drive letter. Mine was F: for example. 5. Click on the folder-looking icon and point it towards the file named "SCH-R530U_CND4_debrick.img" once downloaded. http://upload.teamuscellular.com/5Ig 6. Once you are sure that that is the drive letter click "write" and then "Yes". The write process should only take a couple of seconds to finish. Once finished, take out the MicroSD card from the adapter. 7. Open up the Samsung Galaxy SIII. Take any existing MicroSD for SIM card out as well as the battery. Put the SD card that we just formatted and insert it into the phone. Plug the phone in using the wall charger. The red LED should light up indicating that the phone still knows that the MicroUSB slot still exists. If there is no red LED, then this will probably not work. 8. Reinsert the battery. The phone may start up on it's own or you may have to hold down the power button. My phone started on it's own. If all goes right you should get output to the display and maybe boot into Android. If you were like me and flashed the wrong ROM, you're gonna need to flash a new one. 9. For the people that the phone booted into Android, you MUST have the SD card in your phone or else it will become unbootable again. Don't want to have to have the card in there 24/7? Keep reading. 10. For both the groups of wrong ROMs and anti SD booters, you'll have to flash the stock TouchWiz firmware. So backup your data (if there is any) and download this file: http://upload.teamuscellular.com/38m?d=1 11. This file will take people that were still running 4.3 and move them up to 4.4.2 KitKat. People that already had 4.4, this will work too. I was still on 4.3 because I rooted. 12. Open Odin Download: 13. REMOVE THE SD CARD FROM THE PHONE OR ELSE ODIN WILL WRITE THE BOOTLOADER ONTO THE SD CARD WHICH MEANS YOU'VE SUCCESSFULLY DID NOTHING YOU WANTED TO DO. 14. Press "start". No, not the Start Button. Start in Odin. Yeah I'm bad at this. 15. This will take several minutes to complete. Be patient. Do not touch the phone just to reduce the chance of something screwing up. 16. If Odin finishes and says "PASS!" in a green box, congratulations! You've just successfully unbricked your Samsung Galaxy SIII! (Yes you can boot without the SD card now too. If you want to keep the SD card as a "Oh sh*t I messed up" card, feel free. But you can use the card normally by using a free Windows program called Minitool Partition Wizard and make the card normal again by deleting all the small partitions and creating one big one.) If this helped you, you're welcome. If you wouldn't mind swinging by my YouTube channel and giving it a sub, it would be greatly appreciated. https://www.youtube.com/channel/UC6a_9cLDE_9KTBfvKGbpXxw Twitter: realZekTech Instagram: zek_tech Have a great day with your SIII!
  2. Here is a rom that you guys if curious should try, its not by me but ive been using it for a while till I switched over to AOSP Bliss stalk Rom. I love the features in that rom but as of touch wiz this rom is sick and with ktoonsez kernel. you must be on 4.4.2. bootloader. dont flash the sprints. just keep your device the same with the software from this site. if you have issues installing it inside your current recovery, download the recovery from the app store like twrp or cwm then flash an updated sprint recovery or a universal recovery that will not give you an error while installing. this rom is sick. LOADS OF OPTIONS AND TWEAKS. also try the wicked x8.0 http://forum.xda-developers.com/showthread.php?t=2750674
  3. Here is a rom that you guys if curious should try, its not by me but ive been using it for a while till I switched over to AOSP Bliss stalk Rom. I love the features in that rom but as of touch wiz this rom is sick and with ktoonsez kernel. you must be on 4.4.2. bootloader. dont flash the sprints. just keep your device the same with the software from this site. if you have issues installing it inside your current recovery, download the recovery from the app store like twrp or cwm then flash an updated sprint recovery or a universal recovery that will not give you an error while installing. this rom is sick. LOADS OF OPTIONS AND TWEAKS. also try the wicked x8.0 http://forum.xda-developers.com/showthread.php?t=2750674
  4. Hello all, I got the OTA update for my s5 today and stupidly updated to the "newest" 4.4.2. With this towelroot will not work because of the kernal (being to new) BUT I have found a solution and with your guys help we can get root back via towelroot. I was reading on XDA on people using this method and sadly US cellular doesn't get much love on there so I figured if i brought it here we could get something done. Here's the thread : http://forum.xda-developers.com/galaxy-s5/general/how-to-root-triggering-knox-2nd-method-t2843044/post55377594 Pretty much we just need downloads for the old kernal and the new kernal according to this. I am wayyyyy to big of a rookie to even try to get the files so I figured someone else might throw in some help? Thanks guys.
  5. Team OctOs presents Octo-Kat. Check out our Feature's video at the link below. http://youtu.be/HUmReo-YokQ We maintain a current release record and change-log on our website: http://www.teamoctos.com -Do Not Mirror our files without talking to us. We can do that ourselves should we desire to.- Frequently Asked QuestionsQ: Why isn't there XXXXXXX feature.A: Shoot us a Suggestion if you want to see something added. While we are not going to promise to implement, we will always look into it Q: But CM and all the others have..A: ROM developers, including CM, build something they want to use. The ROM dev that includes something they won't run implies less than 100% effort to ensure it does work. As a team, we have similar goals and objectives. If XYZ ROM has a feature you want, and we don't (or don't want), feel free to use XYZ ROM, or build your own custom version of Octo-Kat ADB Logcat tutorial here: How to create a logcat log Bugs:Let us know if you run into bugs. Get Syslog from the Android Market, if you don't already have it. No logs and we can only try to recreate the event off of vague descriptions. Please also include what you were doing when it FCed or failed. Logs can be emailed to: teamoctos@gmail.com Basic Instructions: Download ROM .zip fileReboot to Recovery (Note: Use hardware buttons or adb reboot recovery - ROM Manager or similar software is NOT supported)--- TWRP is the ONLY recovery Team OctOs uses - We do not support flashing on CWM ---Flash ROM and GApps .zip filesReboot A Note about the Team OctOs GAppsWe in Team OctOs believe in choices. We believe in leaving the fundamental decisions about your phone to you. In that spirit, Team OctOs gives you options for your GApps experiences. While any GApps package should work, we offer you the choice of using some of the same GApps packages that we use ourselves, and leave the choice up to you. The Dalvik-Enhanced packages are NOT ART compatible. If you plan to run ART, don't use those. @broodplank1337 for the great AOSP source to start@buckmarble for helping on a lot of random issues. We would also like to thank CyanogenMod for their device specific files and driversChameleonOSSlimROMAnyone else who has ever submitted Open-Source code Follow Us at the various website below!
  6. link back to the OP: http://teamuscellular.com/Forum/topic/6241-romkang442-teambaked-jflteusc/ might need this just in case
  7. Team OctOs presents Octo-Kat. Check out our Feature's video at the link below. http://youtu.be/HUmReo-YokQ We maintain a current release record and change-log on our website: http://www.teamoctos.com -Do Not Mirror our files without talking to us. We can do that ourselves should we desire to.- Frequently Asked QuestionsQ: Why isn't there XXXXXXX feature.A: Shoot us a Suggestion if you want to see something added. While we are not going to promise to implement, we will always look into it Q: But CM and all the others have..A: ROM developers, including CM, build something they want to use. The ROM dev that includes something they won't run implies less than 100% effort to ensure it does work. As a team, we have similar goals and objectives. If XYZ ROM has a feature you want, and we don't (or don't want), feel free to use XYZ ROM, or build your own custom version of Octo-Kat ADB Logcat tutorial here: How to create a logcat log Bugs:Let us know if you run into bugs. Get Syslog from the Android Market, if you don't already have it. No logs and we can only try to recreate the event off of vague descriptions. Please also include what you were doing when it FCed or failed. Logs can be emailed to: teamoctos@gmail.com Basic Instructions: Download ROM .zip fileReboot to Recovery (Note: Use hardware buttons or adb reboot recovery - ROM Manager or similar software is NOT supported)--- TWRP is the ONLY recovery Team OctOs uses - We do not support flashing on CWM ---Flash ROM and GApps .zip filesReboot A Note about the Team OctOs GAppsWe in Team OctOs believe in choices. We believe in leaving the fundamental decisions about your phone to you. In that spirit, Team OctOs gives you options for your GApps experiences. While any GApps package should work, we offer you the choice of using some of the same GApps packages that we use ourselves, and leave the choice up to you. The Dalvik-Enhanced packages are NOT ART compatible. If you plan to run ART, don't use those. @broodplank1337 for the great AOSP source to start@buckmarble for helping on a lot of random issues. We would also like to thank CyanogenMod for their device specific files and driversChameleonOSSlimROMAnyone else who has ever submitted Open-Source code Follow Us at the various website below!