Hi all
I am newbie to the android world, i was gifted an at&t. S4 i337 model for new year. It was purchased as an unlocked device so it can work in india, but it wasnt,when i load my indian sim ,s4 always prompts with simunlock code.
I read lot of the xda thread to overcome this , intially s4 was in 4.2.2 MF3 build, i was able to root the device but i wasnt able to unlock for international band. So i updated to 4.3 using the thread "http://forum.xda-developers.com/showthread.php?t=2573080" since most of the reviews had positive feedback for unlocking. My software version got updated to 4.3 mk2 build But to my notice after this s4 loads with custom unlocked padlock symbol and rooting dosent work, it always fails when i run the supersu app in disabling knox step.
I followed every step as it said in the thread ,but failed every single time, the thread says it will work only with stock rom, since it boots with custom is this the reason for failure. How can i recover from this. Ur help will be appreciated, i have my s4 unused for past 1 month because of this.
Thanks
Hi Everyone,
I have finally decided to get the S6 edge as the prices have fallen within my budget. I want to get an unlocked 64 GB GSM model and root it using pingpong root. Can anyone tell me which variant I should get so that I can root and continue to sideload updates while not losing any features.
Thanks!
I suggest you get the international model SM-G925F.
It is unlocked and has the widest support of the community (I saw kernels only support international models G925F/I for the first few versions, before supporting other variants).
Any idea if I can root it and then update it to the latest firmware (while keeping the root)? Don't need OTA, just any way to do it is fine. I love this phone but it has so many hoops to jump through. I need root for adblocking and also need latest firmware for samsung pay.
Sorry if these are dumb questions... I have searched unsuccessfully for answers here and I am new to the forums and to Android... not sure where to ask this...
I just bought a new (unsold stock) T-Mobile Samsung Galaxy S5 (SM-G900T) phone and activated it on the T-Mobile network. The phone came with G900TUVU1ANE6 (4.4.2) from the factory. After only a few hours of operation T-Mobile has pushed an unnamed update to the phone which I assume is G900TUVU1GPE1 (6.0.1) Marshmallow. I have postponed installation of the update but don't know how long I can postpone it or if I can prevent its installation.
Will installing Marshmallow cause my S5's bootloader to become locked? I ask because I found this on Wikipedia (link not allowed) "As of Marshmallow, the Android Compatibility Definition Document contains new security mandates for devices, dictating that those that are capable of accessing encrypted data without affecting performance must enable Secure boot and device encryption by default".
Or is my G900T's bootloader already locked? I ask because I found this at root my galaxy dot net (link not allowed) "If your device’s bootloader is locked then you will get the update via OTA. [...] If your device is rooted or bootloader is unlocked then you have to manually Flash / Install Official Android 6.0.1 Marshmallow Firmware On T-Mobile Galaxy S5 using Odin Flash tool".
The second question worries me more. I bought a T-Mobile S5 because so many sources claim the G900T bootloaders are unlocked. Now I'm unsure. Is there an easy way to determine if my bootloader is locked or unlocked? (I have Heimdall available on a Linux laptop but no windows machine).
I hope to install CM10 or CM13 on my S5. Thanks in advance for any definite information or guidance anyone can provide.
I'm thinking about buying an S5 and am wondering this as well.
xda-hayduke said:
Sorry if these are dumb questions... I have searched unsuccessfully for answers here and I am new to the forums and to Android... not sure where to ask this...
I just bought a new (unsold stock) T-Mobile Samsung Galaxy S5 (SM-G900T) phone and activated it on the T-Mobile network. The phone came with G900TUVU1ANE6 (4.4.2) from the factory. After only a few hours of operation T-Mobile has pushed an unnamed update to the phone which I assume is G900TUVU1GPE1 (6.0.1) Marshmallow. I have postponed installation of the update but don't know how long I can postpone it or if I can prevent its installation.
Will installing Marshmallow cause my S5's bootloader to become locked? I ask because I found this on Wikipedia (link not allowed) "As of Marshmallow, the Android Compatibility Definition Document contains new security mandates for devices, dictating that those that are capable of accessing encrypted data without affecting performance must enable Secure boot and device encryption by default".
Or is my G900T's bootloader already locked? I ask because I found this at root my galaxy dot net (link not allowed) "If your device’s bootloader is locked then you will get the update via OTA. [...] If your device is rooted or bootloader is unlocked then you have to manually Flash / Install Official Android 6.0.1 Marshmallow Firmware On T-Mobile Galaxy S5 using Odin Flash tool".
The second question worries me more. I bought a T-Mobile S5 because so many sources claim the G900T bootloaders are unlocked. Now I'm unsure. Is there an easy way to determine if my bootloader is locked or unlocked? (I have Heimdall available on a Linux laptop but no windows machine).
I hope to install CM10 or CM13 on my S5. Thanks in advance for any definite information or guidance anyone can provide.
Click to expand...
Click to collapse
After installing the latest firmware, you can still flash custom ROMs, you can still root, etc.
Just look in the Android Development sub-forum, and you will see several custom ROMs for MM on the SM-900T.
You can also flash ROMs from the International S5 forum. I've never flash a CM ROM, but there are several on this forum that have and do.
Rob
Are u done with cm 13 bcz I want to ask same question that whether s5 T-Mobile bootloader is locked or no
And plz send me the whole process u did for cm 13
Thanks best regard Hadi!
hadi008 said:
Are u done with cm 13 bcz I want to ask same question that whether s5 T-Mobile bootloader is locked or no
And plz send me the whole process u did for cm 13
Thanks best regard Hadi!
Click to expand...
Click to collapse
G900T T-Mobile's bootloader is not locked. I've downgraded from MM to KK without problems. I flashed RR MM without problems
No brother . I mean if I need to root s5 T-Mobile than shall I downgrade it first or I can easily do it on marshmallow.
Can u tell me any authentic root process!
Thanks
http://forum.xda-developers.com/tmo...l/root-how-to-root-sm-g900t-firmware-t3358190
It's exactly the same process on MM as it is on LP or KK.
I rooted my G900T about two weeks ago. It had MM the latest patches and everything, so you don't need to worry about the bootloader ever being locked.
marshmallow to Lollipop?
Reyse said:
G900T T-Mobile's bootloader is not locked. I've downgraded from MM to KK without problems. I flashed RR MM without problems
Click to expand...
Click to collapse
Hi, I just bought a brand new S5 and it has marshmallow already, I am trying to downgrade to 5.1.1 and it acts like the boot loader is locked, Ordin fails mid flash. How were you able to do it?
jtatex said:
Hi, I just bought a brand new S5 and it has marshmallow already, I am trying to downgrade to 5.1.1 and it acts like the boot loader is locked, Ordin fails mid flash. How were you able to do it?
Click to expand...
Click to collapse
Hi! is your smartphone really a G900T?
IF it is so... It is pretty sure you download a firmware and it is incomplete.
Where do you download from?
Which version is it?
it is a G900T, I downloaded stock Lollipop 5.1.1 from T mobile
jtatex said:
it is a G900T, I downloaded stock Lollipop 5.1.1 from T mobile
Click to expand...
Click to collapse
Could you tell us exactly filename and size?
sorry, it's a G900t3
Reyse said:
Could you tell us exactly filename and size?
Click to expand...
Click to collapse
My bad, it's a G900T3
jtatex said:
My bad, it's a G900T3
Click to expand...
Click to collapse
I almost sure it doesn't matter
Try to download the firmware from sammobile
https://www.sammobile.com/firmwares/galaxy-s5/SM-G900T3/
I did, i finally settled on an AOSP rom, Resurrection Remix 7.1.1. But i still miss Touchwiz. Thanks for your help.
jtatex said:
I did, i finally settled on an AOSP rom, Resurrection Remix 7.1.1. But i still miss Touchwiz. Thanks for your help.
Click to expand...
Click to collapse
you can try this
https://forum.xda-developers.com/showpost.php?p=65063785&postcount=102
Hello everyone,
I have tried to look for an answer to my question with no luck. I have an unlocked t-mobile galaxy S5 unrooted with stock ROM and I am with At&t. I need to use wifi calling and therefore I was wondering if I can root then flash a stock AT&T ROM on my device, and what tools I should use. I mean are ROMs cross compatible. I would really appreciate your advice on this.
Thanks
It's a shame no one has an answer for this.
I'm looking for information on this, as well.
I have a SM-G900T (bootloader unlocked). I'm wondering if I can get it to be "stock" (without the yellow Knox warning on boot) and not have the T-Mobile startup animation or apps.
I have an UNLOCKED Galaxy S9+ SM-G965U (Snapdragon). It's factory unlocked but isn't the G965U1 version (There isn't any branded booting or mobile network bloatware. I also haven't tripped my Knox or rooted my device but I have manually installed the Android Pie Beta. I know the Official Pie Update is out for the SM-G965F version but I'm not sure about any other. I'm not new to rooting or android devices in general as I've been using them for almost a decade now. However, I am new to understanding how the different versions of devices operate. Now my questions are:
1. Is there any huge difference between the G965U and the G965U1? or is the firmware interchangeable?
2. Is it possible to install firmware for the G965F onto the G965U without any negative impact?
3. Are all versions getting the Pie update eventually or is it reserved for a select few?
I would really appreciate it if someone could give me a breakdown of all this. Sort of a "Device Versions for Dummies" explanation but specific to the S9+
Thanks