Affichage des articles dont le libellé est G900A. Afficher tous les articles
Affichage des articles dont le libellé est G900A. Afficher tous les articles

lundi 23 février 2015

[Q] Tmobile 4gLTE for AT&T UNLOCKED G900A topic






I've been searching far and wide.. Each theory to understand the failures that's inside. DUN DUN
So, anyways I have an AT&T unlocked and currently using it for TMOBILE.
I've read things from build.props changes to flashing band radios such as .33 to try to obtain 4gLTE.
Also changing APN settings. Went through t-mobile services at least 5 times through live chat and calling.
Went through AT&T live chat. EVEN WENT AS FAR TO CONTACT SAMSUNG.
Every attempt failed to help me achieve 4gLTE for Tmobile using the unlocked AT&T s5.
People said they are able to use their AT&T phones and have LTE for Tmobile.
But on the other hand people said it is not possible because the 2 carriers use different bands or radio towers or whatever.

So, can someone please tell me is there a solution to having and keeping LTE for T-mobile using an unlocked AT&T phone. It's been about 3 days of search after work and this search for the philosopher stone is tiring.






dimanche 22 février 2015

[Q] Soft-Bricked Galaxy S5 G900A topic






I'm new to this and I bricked my phone pretty quickly. I'm trying to return it to stock. I have the MD5 file from sammobile. Whenever I try to start the process in Odin v3.10 (I've tried other versions and other MD5 files) I get

<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar .md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

I've been all over different forums trying to find any way to fix my problem but I can't get anything to work. Literally any help would be fantastic!






[Q] Soft-bricked S5 G900A after downgrading from OA1 topic






Hi all. Long time reader, first time poster.

I was rooted on NG3 and figured I'd downgrade to NCE so I could get the 4.4.4 update. 4.4.4 wouldn't update in that condition and I wanted to ensure I'd be able to get Lollipop (it is coming, AT&T, right?). I backed up everything in Kies, downgraded to NCE and took the OTA to 4.4.4. All was well and then when I went to restore my backup from Kies, it told me I could backup everything except my apps. Being lazy, I figured I'd start all over and do the restore of all my apps while still on 4.4.2, then take the OTA to 4.4.4 again.

I started all over using the method linked below, but after Odin finishes and the S5 reboots, the Samsung splash logo animation almost finishes, pauses for a few seconds and the screen goes black and the notification LED is on blue and becomes non-responsive.

I've tried going into recovery and wiping cache and data and starting the Odin process linked below again with the same results for the past 3-4 hours. I've tried Kies update and initialization but that tells me my phone isn't compatible. Did 4.4.4 do something with the boot-loader and now it's incompatible with 4.4.2?

Any ideas or other options? Thanks in advance!


HTML Code:


http://forum.xda-developers.com/showthread.php?t=2785363

This was linked from a factory reset thread I believe.

ODIN MODE
PRODUCT NAME: SM-G900A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK(KK): OFF
KNOW WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T1, A1, A2, P1
SECURE DOWNLOAD : ENABLE
UDC START

Here are the last few lines from Odin:

<ID:0/006> modem.bin
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes [at this point it was less than a minute to get to the end]
<ID:0/006> Receive Response from boot-loader
<ID:0/006> cache.img.ext4
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Removed!!






samedi 14 février 2015

Need serious help: Bricked Phone (G900A) topic






Hey guys,

Was a little schwasted last night and decided to play around with my phone. I was trying to root it and install a custom ROM, but I just ended up bricking the damn thing instead.

Needless to say, I will not be trying to root this thing anymore but please help me fix it by tonight.

I've been up all night trying to fix it, and I've done pretty much everything possible and it's starting to get very frustrating. I've downloaded the stock ROM .zip file and loaded it into Odin, where it installs successfully. Then I boot it into recovery mode, do a factory reset, wipe the cache, and reboot. No difference - the Custom Bootloader still shows up and then it displays a few seconds of the Samsung animation before freezing and eventually turning black (blue light on top left is still on though).

Please help.






vendredi 13 février 2015

Will AT&T g900a work on straight talk(AT&T) topic






Can At&t block this if its a clean phone? I'm going to buy out my at&t contract it will pay for itself. Straight talk has LTE and is a better deal.






lundi 9 février 2015

[Q] G900A Wifi Problems topic






For the past 24 hours I have been having weird connectivity problems with my s5. While connected to my universities wifi, I am unable to load certain things like thumbnails in the Play Store, any imgur gifs on my Reddit Now app, any photos or videos on my Facebook news feed and other random connection problems. However, I am still able to send Facebook messages over Messenger, and all webpages will load on Google Chrome. But when I am connected through LTE, everything seems to work. I have done a complete factory reset, wiped the cash and re installed all my apps, but I still having the same problem. My schools wifi security protocol is wpa2 enterprise and uses the AES encryption type if that is relevant. Also, I had just updated my phone to 4.4.4 just before this became a problem.