I get what a bootloader is--the low level programming that checks everything and then boots the OS. And I have read that when they say "locked bootloader" it means "encrypted bootloader".
Have previous bootloaders been un-encrypted and thus made flashable? Or was some "exploit" found that enabled the bootloader to be replaced with one that would be unencrypted and thus ROMs could be flashed?
It sounds like the bootloader being locked/encrypted prevents much being done in the way of custom ROM flashing. So at this point we have Safestrap, unless that doesn't work on the AT&T g900a.
So, what are the designers working on at this time--unencrypting the bootloader, finding a way to simply replace it, or using something like Safestrap to create a space where a different ROM can be placed and the bootloader bypassed in some way?
I suppose I am curious to find out just how tough this locked bootloader problem is for the devs.
Sent from my SAMSUNG-SM-G900A using xda premium
kettir said:
I get what a bootloader is--the low level programming that checks everything and then boots the OS. And I have read that when they say "locked bootloader" it means "encrypted bootloader".
Have previous bootloaders been un-encrypted and thus made flashable? Or was some "exploit" found that enabled the bootloader to be replaced with one that would be unencrypted and thus ROMs could be flashed?
It sounds like the bootloader being locked/encrypted prevents much being done in the way of custom ROM flashing. So at this point we have Safestrap, unless that doesn't work on the AT&T g900a.
So, what are the designers working on at this time--unencrypting the bootloader, finding a way to simply replace it, or using something like Safestrap to create a space where a different ROM can be placed and the bootloader bypassed in some way?
I suppose I am curious to find out just how tough this locked bootloader problem is for the devs.
Sent from my SAMSUNG-SM-G900A using xda premium
Click to expand...
Click to collapse
From what I have seen very few bootloaders have ever been unencrypted publicly by the community. There have been some devices although rare that the manufacturer has had a change of heart and allowed to be decrypted in most cases at the cost of your factory warranty.
My last phonetic galaxy s3 was not encrypted and allowed an insecure boot image. This did not check to make sure the rom, modem, or kernel were not signed. The development community is still very alive today years after its release.
Hashcode's safestrap allows for a custom rom but to my knowledge has never allowed a viable custom kernel. He did amazing work with this technology around the Motorola Droid 3 but the community never really built up support for the device.
It's a shame as my old s3 with a good rom and custom kernel is much much faster and more usable than this locked down s5.
Sent from my ASUS Transformer Pad TF700T using Tapatalk
spasch said:
From what I have seen very few bootloaders have ever been unencrypted publicly by the community. There have been some devices although rare that the manufacturer has had a change of heart and allowed to be decrypted in most cases at the cost of your factory warranty.
Click to expand...
Click to collapse
I did a quick Google to find out if other carriers had the s5 with an unencrypted bootloader. Nothing came up immediately except mention of the Verizon s5 developer edition. Android Police had this to say about the developer version:
The unlockable bootloader on the Developer Edition allows end users to easily flash a custom recovery, and then root or flash a custom ROM. Other than the unlockable bootloader, this Galaxy S5 is exactly the same as the standard Verizon model in both hardware and software.
I did a comparison of the straight Verizon s5 to the GSM s5 on Phonescoop and noticed differences (less GSM levels). Therefore it would be a loss, as far as performance goes, to get the Verizon developer version.
Overall, I'm happy with my s5. I've got root. I've found ways to get the features I want (often through Xposed.) It definitely seems faster than my s5 even though I'm burdening it with Go Launcher (just to get all the pretty themes.) I can freeze the bloatware or even delete it via Titanium Backup. So I'm not super anxious about it. I just hate being locked out of anything on something I purchased and own.
kettir said:
I did a quick Google to find out if other carriers had the s5 with an unencrypted bootloader. Nothing came up immediately except mention of the Verizon s5 developer edition. Android Police had this to say about the developer version:
The unlockable bootloader on the Developer Edition allows end users to easily flash a custom recovery, and then root or flash a custom ROM. Other than the unlockable bootloader, this Galaxy S5 is exactly the same as the standard Verizon model in both hardware and software.
I did a comparison of the straight Verizon s5 to the GSM s5 on Phonescoop and noticed differences (less GSM levels). Therefore it would be a loss, as far as performance goes, to get the Verizon developer version.
Overall, I'm happy with my s5. I've got root. I've found ways to get the features I want (often through Xposed.) It definitely seems faster than my s5 even though I'm burdening it with Go Launcher (just to get all the pretty themes.) I can freeze the bloatware or even delete it via Titanium Backup. So I'm not super anxious about it. I just hate being locked out of anything on something I purchased and own.
Click to expand...
Click to collapse
Plz sign this
https://www.change.org/petitions/att-give-us-the-freedom-to-modify-and-build-unlock-our-bootloaders
Sent from my SAMSUNG-SM-G870A using XDA Premium 4 mobile app
Related
Hey everyone!
First off, I apologize if I am posting this in the wrong area, as this is my first post here.
About two months ago, I used TowelRoot on my phone and achieved root status. Afterwards, I installed Xposed Framework and started loading modules. When AT&T pushed out an OTA update which updated the kernel, making rooting impossible once again, I did lose my root status. However, Xposed Framework and all of my modules remained installed and still function.
The interesting part is, after a reboot, I noticed that my boot splash screen says "Samsung Galaxy S5 Active", and "Custom" with the unlocked padlock at the bottom. Also, under device status, it says "custom" instead of "official".
I haven't attempted to flash a custom recovery on this phone, but what I'd really like to know is -- is my device's bootloader unlocked now, can I flash a recovery on it, and is there any ROM like a Cyanogenmod base that will be compatible with this phone? I haven't had any luck with researching it because everyone with the AT&T variant of this phone has a locked bootloader, so there hasn't been much opportunity to play with it.
I'd appreciate any help I can get on the matter. I'd like to see what this thing is capable of!
dont mess with itttt leave it until someone replies we need to extract your firmware, hold onto it if you not messing around, im not experinced enough but someone will pm you im sure
MGArcher007 said:
Hey everyone!
First off, I apologize if I am posting this in the wrong area, as this is my first post here.
About two months ago, I used TowelRoot on my phone and achieved root status. Afterwards, I installed Xposed Framework and started loading modules. When AT&T pushed out an OTA update which updated the kernel, making rooting impossible once again, I did lose my root status. However, Xposed Framework and all of my modules remained installed and still function.
The interesting part is, after a reboot, I noticed that my boot splash screen says "Samsung Galaxy S5 Active", and "Custom" with the unlocked padlock at the bottom. Also, under device status, it says "custom" instead of "official".
I haven't attempted to flash a custom recovery on this phone, but what I'd really like to know is -- is my device's bootloader unlocked now, can I flash a recovery on it, and is there any ROM like a Cyanogenmod base that will be compatible with this phone? I haven't had any luck with researching it because everyone with the AT&T variant of this phone has a locked bootloader, so there hasn't been much opportunity to play with it.
I'd appreciate any help I can get on the matter. I'd like to see what this thing is capable of!
Click to expand...
Click to collapse
MGArcher007 said:
Hey everyone!
First off, I apologize if I am posting this in the wrong area, as this is my first post here.
About two months ago, I used TowelRoot on my phone and achieved root status. Afterwards, I installed Xposed Framework and started loading modules. When AT&T pushed out an OTA update which updated the kernel, making rooting impossible once again, I did lose my root status. However, Xposed Framework and all of my modules remained installed and still function.
The interesting part is, after a reboot, I noticed that my boot splash screen says "Samsung Galaxy S5 Active", and "Custom" with the unlocked padlock at the bottom. Also, under device status, it says "custom" instead of "official".
I haven't attempted to flash a custom recovery on this phone, but what I'd really like to know is -- is my device's bootloader unlocked now, can I flash a recovery on it, and is there any ROM like a Cyanogenmod base that will be compatible with this phone? I haven't had any luck with researching it because everyone with the AT&T variant of this phone has a locked bootloader, so there hasn't been much opportunity to play with it.
I'd appreciate any help I can get on the matter. I'd like to see what this thing is capable of!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=54642044
Sent from my SAMSUNG-SM-G900A using XDA Premium HD app
Apparently there are many different circumstances under which the splash screen says custom, which have nothing to do with the bootloader being locked or unlocked. I seem to recall it showing up for people when they just switched to ART runtime, and in some cases it didn't even go back when they switched back to Dalvik. Many of the methods for making this not appear just involve cosmetically hiding it, not actually cleaning up whatever it is that is being detected.
What I wouldn't give to have this bootloader unlocked
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
If there is a dev that wants a s5 to experiment with to get the bootloader unlocked I'll be happy to donate my s5 if I can get it back after finding an exploit . But the dev needs to come with unanimous recommendation by the devs. Let me know I can still use my s3.
Sent from my SAMSUNG-SM-T537A using XDA Free mobile app
Aw man, I was really hoping that the bootloader just somehow magically unlocked itself. Wishful thinking, I suppose. I love my S5 Active, I just wish I had a little more freedom with customizing it in ways like I could my S3.
I wonder if this is a result of Knox being disabled during the root... Either way, I hope I'll still receive OTA updates for things like 4.4.4 if they ever decide to release it, and eventually Android L.
For now, I can't complain -- surprisingly enough, even without root, my Xposed Framework still functions very well and I can still make backend and UI changes in GravityBox.
Regardless, thanks for all the replies, guys! I probably won't mess with trying to fix it unless they come out with an OTA update that I can't get as a result of this.
MGArcher007 said:
Aw man, I was really hoping that the bootloader just somehow magically unlocked itself. Wishful thinking, I suppose. I love my S5 Active, I just wish I had a little more freedom with customizing it in ways like I could my S3.
I wonder if this is a result of Knox being disabled during the root... Either way, I hope I'll still receive OTA updates for things like 4.4.4 if they ever decide to release it, and eventually Android L.
For now, I can't complain -- surprisingly enough, even without root, my Xposed Framework still functions very well and I can still make backend and UI changes in GravityBox.
Regardless, thanks for all the replies, guys! I probably won't mess with trying to fix it unless they come out with an OTA update that I can't get as a result of this.
Click to expand...
Click to collapse
Sadly. ...We may never see the bootloader unlocked without a factory method...
It's encryption prevents us from even being able to open it into a usable state...
We need either an encryption key....or a new bootloader entirely...
Not happening any time soon....g
So I actually don't have the S5, or any Samsung device for that matter, but a friend of mine does, and really wants to root their phone. I had no idea the AT&T S5 was so secure, but it's pretty interesting too. I've been researching for over 15 hours. I may not have been able to root his phone, but I think I have learned a couple things and maybe some possible root methods.
1.) Since using ODIN to downgrade would soft brick the phone, would it be possible to download the stock Lollipop update onto a computer, give the update super user access, replace the recovery with a custom one, or unlock the bootloader from the computer, then flash it through ODIN?
2.) Intercept any sort of OTA update, then alter it to flash a custom recovery or unlock bootloader? I don't know how you would go around this though.
3.) If someone hasn't taken the OTA update that patched the Stagefright exploit, could someone purposely use the exploit to allow installation of a custom recovery or even to unlock the bootloader since the Stagefright bug has super user access (or so I've heard).
Also, I'm sorry if these are stupid ideas. I know close to nothing about Samsung so everything I'm basing this off of is what I've read in the past 15 hours.
jsmithfms said:
So I actually don't have the S5, or any Samsung device for that matter, but a friend of mine does, and really wants to root their phone. I had no idea the AT&T S5 was so secure, but it's pretty interesting too. I've been researching for over 15 hours. I may not have been able to root his phone, but I think I have learned a couple things and maybe some possible root methods.
1.) Since using ODIN to downgrade would soft brick the phone, would it be possible to download the stock Lollipop update onto a computer, give the update super user access, replace the recovery with a custom one, or unlock the bootloader from the computer, then flash it through ODIN?
2.) Intercept any sort of OTA update, then alter it to flash a custom recovery or unlock bootloader? I don't know how you would go around this though.
3.) If someone hasn't taken the OTA update that patched the Stagefright exploit, could someone purposely use the exploit to allow installation of a custom recovery or even to unlock the bootloader since the Stagefright bug has super user access (or so I've heard).
Also, I'm sorry if these are stupid ideas. I know close to nothing about Samsung so everything I'm basing this off of is what I've read in the past 15 hours.
Click to expand...
Click to collapse
The issue is that AT&T (and Verizon) use an encrypted signature key to verify they are the correct unaltered files as well as the means to unlock the bootloader to allow the OTA. Without that key, the tasks you mention are near impossible. They are not stupid ideas at all..just very difficult with all the security checks included.
KennyG123 said:
The issue is that AT&T (and Verizon) use an encrypted signature key to verify they are the correct unaltered files as well as the means to unlock the bootloader to allow the OTA. Without that key, the tasks you mention are near impossible. They are not stupid ideas at all..just very difficult with all the security checks included.
Click to expand...
Click to collapse
Crap... well does anyone know how that encyption key is generated? Like, could I theoretically get an algorithm from a ROM?
Honestly for the time being I wouldn't bother with ROMS for that Device and carrier at the moment. Especially being that its someone elses device. Towelroot should be a good start. If Im not mistaken I don't think its supposed to trip knox.
Sent from my HTCEVODesign4G using XDA Free mobile app
jsmithfms said:
Crap... well does anyone know how that encyption key is generated? Like, could I theoretically get an algorithm from a ROM?
Click to expand...
Click to collapse
This is the riddle of the Sphinx my friend. I am sure the super devs have tried their best so far to crack it. It has been an ongoing effort to make phones more and more secure, not against the amateur developers and rooters, but against the hackers. These smartphones are now our personal computers, diaries, personal assistants, financial operator, and more. They basically are a person's (and business's) life. AT&T and Verizon have taken the big steps to appeal to the Exchange clients, corporate, government and military contracts. Even the general public want to know their phone is secure. This is what keeps me stuck on the Sprint network.
Have you tried Kingroot?
I successfully rooted my wife's AT&T S4 on OC3 lollipop (supposedly unrootable) with the desktop version. Mobile version didn't work but desktop did without a hiccup. Maybe it'll work on the S5.
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Rockin' a l337 with Goldeneye v49.1 + Wanam Xposed and loving life on AT&T's 4G LTE network
S5 on lollipop has a new nasty boot loader.... it was a miracle on its own that they ever came up with safestrap to duck the boot loader on earlier versions of android
the guy who unlocked the bootloader on Verizon's s5 variant has released a document detailing what I believe is the procedure. Could this open the door for ATT's variant to be unlocked?
https://twitter.com/firewaterdevs/status/713906161834192896
http://theroot.ninja/disclosures/SAMDUNK_1.0-03262016.pdf
sensei22 said:
the guy who unlocked the bootloader on Verizon's s5 variant has released a document detailing what I believe is the procedure. Could this open the door for ATT's variant to be unlocked?
https://twitter.com/firewaterdevs/status/713906161834192896
http://theroot.ninja/disclosures/SAMDUNK_1.0-03262016.pdf
Click to expand...
Click to collapse
Possibly, based on what I read from it though it needs the string from the dev-edition device, they have that with the Verizon version so it's easy to get, we only have the one, so I think(speculation) it would be trivial at best to repeat this in our model since we don't even know what to set the CID to to make it reflect that of the 'dev edition', I don't think we're getting a towelroot from this at least[emoji14]
Sent from my SAMSUNG-SM-G900A using Tapatalk
I'm going to take a guess that the Verizon and AT&T phones are both unlockable via the same method. I don't even know how to run Samdunk.. Phone or PC? (Can't be Phone if we have no root access :/)
this really seems promising, i still love my s5 and would like to have the bootloader unlocked at some point.
I wouldn't get your hopes up. That unlock requires root which means anyone on 5.0 or above already is SOL, even IF that method worked on AT&T.
You cant root 5.1.1 on atnt because root modifys the system partition.You can still gain hardware access if theres an exploit you just cant modify the system partition(or the device wont turn on again after a full power-down) because it is checksumed on every boot. (and you cant remove this because it is in the kernel that is signature checked on every boot(and the user and system partitions aren't mounted yet so you cant run a hack to get around it))
This does not mess with the system partition so you could run a kernel exploit and this right after with out rooting.
For the cid use the tmobile s5 cid it is bootloader unlocked right from the store and has the same hardware(gsm modem).
Although my atnt device has 11 toshiba memory and all atnt devices might.
Guicrith said:
You cant root 5.1.1 on atnt because root modifys the system partition.You can still gain hardware access if theres an exploit you just cant modify the system partition(or the device wont turn on again after a full power-down) because it is checksumed on every boot. (and you cant remove this because it is in the kernel that is signature checked on every boot(and the user and system partitions aren't mounted yet so you cant run a hack to get around it))
This does not mess with the system partition so you could run a kernel exploit and this right after with out rooting.
For the cid use the tmobile s5 cid it is bootloader unlocked right from the store and has the same hardware(gsm modem).
Although my atnt device has 11 toshiba memory and all atnt devices might.
Click to expand...
Click to collapse
My att s5 has 15 for the first 2 digits of the Cid.
Guicrith said:
You cant root 5.1.1 on atnt because root modifys the system partition.You can still gain hardware access if theres an exploit you just cant modify the system partition(or the device wont turn on again after a full power-down) because it is checksumed on every boot. (and you cant remove this because it is in the kernel that is signature checked on every boot(and the user and system partitions aren't mounted yet so you cant run a hack to get around it))
This does not mess with the system partition so you could run a kernel exploit and this right after with out rooting.
For the cid use the tmobile s5 cid it is bootloader unlocked right from the store and has the same hardware(gsm modem).
Although my atnt device has 11 toshiba memory and all atnt devices might.
Click to expand...
Click to collapse
Mine is 15, I may be willing to be the guinea pig for this as long as it's not a 100% brick. I'm not entirely sure about the tmo s5 simply having the same hardware will make it work, if something like that was the case why did Verizon folks have to wait for someone with the dev Verizon s5 to upload their aboot?
Sent from my SAMSUNG-SM-G900A using Tapatalk
Anyone here willing to risk bricking their device with a 15 series chip pm me!
I saw on a thread maybe the Verizon s5 bootloader unlocking thread a post about copying your original boot chain to an SD card so incase you brick you can still boot the original boot chain off of your SD. Apparently your SD has to be class 10. Just more food for thought.
How do I check my cid? I'm tempted to test as I have the S7 now. But if this works, I may very well return the S7 due to locked bootloader.
TehPirate_ said:
How do I check my cid? I'm tempted to test as I have the S7 now. But if this works, I may very well return the S7 due to locked bootloader.
Click to expand...
Click to collapse
Brickbug emmc from play store. Still not clear if we can make it work, it should and can, but I think we're missing the att 'dev edition'(maybe factory has it with this?) aboot as just using the Verizon one doesn't seem to work.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Rakuu said:
Brickbug emmc from play store. Still not clear if we can make it work, it should and can, but I think we're missing the att 'dev edition'(maybe factory has it with this?) aboot as just using the Verizon one doesn't seem to work.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Click to expand...
Click to collapse
Shame, mines Toshiba (11)
I just want to let everyone know that I've been involved with the thread over at Verizon and guinea pigged for us. I do have an active, however that shouldn't matter. At the moment, you can run both methods and it will appear to be successful, even changing the Cid, but it doesn't unlock the bootloader.
So for now, we're out of luck.
N4styN1ghtm4r3 said:
I just want to let everyone know that I've been involved with the thread over at Verizon and guinea pigged for us. I do have an active, however that shouldn't matter. At the moment, you can run both methods and it will appear to be successful, even changing the Cid, but it doesn't unlock the bootloader.
So for now, we're out of luck.
Click to expand...
Click to collapse
Damn, I was hoping this would pan out as I have a CID that starts with 15. Checked yesterday when advised in the TMS5 3.0 thread. I got this s5 from Samsung insights so I was hoping that'd help but it's At&t branded with locked bootloader. Waiting patiently for an option to unlock bootloader as I don't plan to get a new phone anytime soon.
~TMS5-3.0-TMBUILD on G900A with Blue Ice Theme
joshua14 said:
Damn, I was hoping this would pan out as I have a CID that starts with 15. Checked yesterday when advised in the TMS5 3.0 thread. I got this s5 from Samsung insights so I was hoping that'd help but it's At&t branded with locked bootloader. Waiting patiently for an option to unlock bootloader as I don't plan to get a new phone anytime soon.
~TMS5-3.0-TMBUILD on G900A with Blue Ice Theme
Click to expand...
Click to collapse
If you're comfortable doing this kind of stuff, then you can try without risking anything. Nobody with an original s5 has tried it, only me, but again, mine is an active. That may or may not be the reason it didn't work for me, but if somebody with an original s5 wants to try, that would give us a definitive answer.
I did both methods and everything went fine, with no errors. It simply didn't unlock. So feel free to give it a shot, you'll just have to restore your old Cid if it fails, which is no big deal. The only thing I'd give a heads up on, is both methods erase your SD card, so use a spare SD card or back up your files from it somewhere else.
Good luck if you try!!
N4styN1ghtm4r3 said:
If you're comfortable doing this kind of stuff, then you can try without risking anything. Nobody with an original s5 has tried it, only me, but again, mine is an active. That may or may not be the reason it didn't work for me, but if somebody with an original s5 wants to try, that would give us a definitive answer.
I did both methods and everything went fine, with no errors. It simply didn't unlock. So feel free to give it a shot, you'll just have to restore your old Cid if it fails, which is no big deal. The only thing I'd give a heads up on, is both methods erase your SD card, so use a spare SD card or back up your files from it somewhere else.
Good luck if you try!!
Click to expand...
Click to collapse
This will be something to try for the weekend. I have backups for both SS and FF so as long as I don't risk full bricking then I'm game. I have a few spare sd cards too. I never took any OTA updates, the first one that tried getting pushed on me while still within the 6 month insights program I rooted with TowelRoot and froze with TB. Other than that I didn't do much else until more recently to go to Muniz_ri 5.0 keeproot and then to TMS5-3.0-TMBUILD. I was hoping of convincing At&t to unlock the bootloader along with the sim unlock since they don't have any rights to this phone. I still have my Next plan s5 thru them so I can toy with this one, just don't want to end up completely bricking either. I have 2 S3 that I put full custom CM builds on for the kids to play with, just turned off root. Lol
~TMS5-3.0-TMBUILD on G900A with Blue Ice Theme
joshua14 said:
This will be something to try for the weekend. I have backups for both SS and FF so as long as I don't risk full bricking then I'm game. I have a few spare sd cards too. I never took any OTA updates, the first one that tried getting pushed on me while still within the 6 month insights program I rooted with TowelRoot and froze with TB. Other than that I didn't do much else until more recently to go to Muniz_ri 5.0 keeproot and then to TMS5-3.0-TMBUILD. I was hoping of convincing At&t to unlock the bootloader along with the sim unlock since they don't have any rights to this phone. I still have my Next plan s5 thru them so I can toy with this one, just don't want to end up completely bricking either. I have 2 S3 that I put full custom CM builds on for the kids to play with, just turned off root. Lol
~TMS5-3.0-TMBUILD on G900A with Blue Ice Theme
Click to expand...
Click to collapse
Yea like I said, as long as you follow the steps closely, there isn't a chance of bricking, it just won't unlock. Let us know when you give it a shot!
Still don't work as of yet...maybe never. The main thread on this is here:
http://forum.xda-developers.com/ver...locking-galaxys-s5-bootloader-t3337909/page77
samccfl99 said:
Still don't work as of yet...maybe never. The main thread on this is here:
http://forum.xda-developers.com/ver...locking-galaxys-s5-bootloader-t3337909/page77
Click to expand...
Click to collapse
It's likely to be never unless we get the proper CID, which as about a needle in a haystack to guess as the bootloader key.
Sent from my SAMSUNG-SM-G900A using Tapatalk
I tried installing several different ROMs onto my AT&T Galaxy Note 3 (N900A). I managed to downgrade to Android 4.4.2 and root the phone (from the current AT&T-forced OC3). I had different results for each ROM I tried. I used Safestrap to perform a Wipe of everything except my MicroSD card in the ROM Slot (#1) I was using before each ROM installation attempt.
Cyanogenmod (cm-13-20151101-UNOFFICIAL-hlte.zip) - Immediately produces a "failed" message trying to install from SafeStrap 3.75 hlteatt, because my phone is hlteatt and not hlte.
MagMa NX (MagMa_NX_UX10_Ultimate_XDA.zip) - Trying to install from Safestrap: progress bar freezes at 0% done.
Resurrection Remix (RR-N-v5.8.2-20170309-hlte.zip) - Installs successfully, but won't boot. First try reboot just stops on a black screen. 2nd reboot gives me the menu seen when booting with Vol Up + Home held down. (Is this the AT&T's firmware "bootloader?")
Any suggestions on getting any of these working? From reading other's experiences, it appears that some are successfully using some custom ROMs with this model phone. Barring that, what (stable) ROM works?
The phone has a locked bootloader; therefore, you can't install twrp. Only custom ROMs that are based off a stock rom and that can be flashed with safestrap will work.
I have yet to understand what it means for a bootloader to be "locked" in firmware/software terms. My initial reaction from the name is that the very first program the phone runs upon starting is the bootloader like a BIOS (apart from hardware self-testing), and the one that came with the phone cannot be bypassed to run a user-made one. But the existence of SafeStrap (originally leaked from Samsung iirc) shows the phone is capable of installing additional OSes. I would be very thankful if someone could provide a link or fill in my lack of knowledge about this.
From screenshots SafeStrap and TWRP almost look identical. I'm not sure what TWRP would do that SafeStrap can't. SafeStrap installed the Resurrection Remix ROM without complaining.
https://forum.xda-developers.com/wiki/Bootloader
Awesome, I'll unlock my bootloader then give it another try. Thanks!
EDIT: aha, that won't work. AT&T's "unlock" feature only allows the phone to be used with another carrier.
Solution: time to get a non-Samsung phone (definitely not from AT&T). This is all to stop being forcefed so many "offers" and "opportunities"—aka "spamware." For the life of me I can't think of a reason other than unchecked greed to deny the ability to remove unwanted software.
Only phones from att, sprint, and Verizon have locked bootloaders.
HTC is a good choice. M8 is a good cheap phone m10 is a good newer phone for 350ish
HTC phones are mostly all unlockable either for free by htcdev or if you require more then by sunshine for $25
Safestrap was not leaked by Samsung it was made by a dev named @Hashcode. He is very talented and worked hard also on the kindle scene. I believe he currently works for lenovo.
The software you are thinking of is odin.
It allows Samsung devices to flash firmware and software but it needs to be signed or your hardware needs to be unlocked. It will help a bootloop it will help you upgrade or get back to stock but it will not help you here.
Oh, thanks for the correction. That would explain why TWRP and SafeStrap look similar. (Neither looks like it is from a corporation.)
Do you mean that AT&T is technically capable of unlocking my phone so it can be flashed with a custom ROM that is not signed, e.g., Resurrection Remix?
Att is responsible for your locked bootloader.
Fun fact note3 was the first Samsung phone to be bootloader locked..
They requested it (demanded) of Samsung.
Verizon is even more demanding.
No, they will not unlock it.
It would be nice if after a device is no longer supported by a carrier they offered bootloader unlocks but that isn't happening either.
It is depressing that a 3 gig ram phone is stuck on lollipop.
I'm reading some conflicting stuff from years back on xda and now I'm not sure what the latest info is. I'm planning to purchase a g900a to replace my g900f that went crazy and I enjoyed the freedom of flashing whatever custom rom I wanted...
Is that still available to a g900a? The first hurdle would be rooting which I read was achieved using towel root.
The 2nd would be getting it to work on a different carrier since I live in the Philippines. I read that using a custom rom would negate this issue...
Then last would be the custom rom. Can I flash other rooms if it is rooted?
Where does the bootloader fit in all of this?
Sadly, it is still stuck on certain custom roms, and with the bootloader remaining locked by AT&T, the phone's age, and lack of developer interest, it's likely going to remain that way.
Be very wary of buying an AT&T Samsung model if you're interested in easy-rooting and ROMS like LineageOS and whatnot. Otherwise you'll probably just have to look elsewhere.