yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 5] g923851:
Flashfire doesnt work anymore

Flashfire crashes after "checking for pro." Did I miss something new?
[AT&T Samsung Galaxy S 5] AptLogic:
Use a newer version from apkmirror
[AT&T Samsung Galaxy S 5] g923851:
Didn't work. I'm going to start from scratch again because this method worked for me before.
[AT&T Samsung Galaxy S 5] RebelLion_:
Check changelog for latest version, dev set a timebomb for non-pro users and you need to set your device's date to before the timebomb's date before you open FlashFire
[AT&T Samsung Galaxy S 5] g923851:
THANKS!

And one last question... Do I have to do the rollback after I follow the updated post?

---------- Post added at 03:54 AM ---------- Previous post was at 03:50 AM ----------

I hope its the time that an issue...
[AT&T Samsung Galaxy S 5] RebelLion_:
The rollback post is a guide in case you brick your phone flashing a fancy ROM or some kind of tweak that leaves you bootlooped. Follow the 3 steps in updated guide, and in case you cant get your phone to boot up the rollback will save your day
[AT&T Samsung Galaxy S 5] KawaiiNeko_:
When i try installing the experimental fw via odin, it flashes correctly but at boot i get "Subsystem Crashed: Modem!" error..

Full thing:

"Subsystem Crashed: MODEM!"

MODEM INFO

Err type: Error Fatal

Task : rf

File: rfc.cpp

Line: 895

ASM PID=0X072 MID=0x248, USID=0xa [00:00:00:274]

: 0x0

Wait..

Done!

UDC Start"

Anyone able to help me?
[AT&T Samsung Galaxy S 5] AptLogic:
Try completely reflashing stock with the roll back stuff and then start over. This should flush out your modem and hopefully get things working again
[AT&T Samsung Galaxy S 5] KawaiiNeko_:
After using the roll back firmware(s) it's still giving the same modem error at boot

Edit: I used both coi5 and bof3, got the same error on both after flashing the experimental fw..
[AT&T Samsung Galaxy S 5] RebelLion_:
https://xdaforums.com/verizon-galaxy-s5/general/testers-required-easier-root-method-t3561529

So I was reading through this and got overly excited. Does this pertain ONLY to Verizon variants? I checked that i have the 15 CID eMMC but I'm guessing AT&T wasn't nice enough to leave us that same vulnerability, am i right?
[AT&T Samsung Galaxy S 5] daakal:
I took this advise and went looking for the right date to change my date time to, for this to work. Couldn't find it, so I took a stab at it.

Rolled my date back to 4/22/2016 and then launched FlashFire and it loaded fine. Hope this helps any late comers messing with old S5's :D Personally trying to build myself the perfect pokemon go alt account phone :)
[AT&T Samsung Galaxy S 5] RebelLion_:
Sadly I'm not sure you'll be able to pass safetynet with this device. I think you must have Magisk to do this, and with a locked bootloader that won't happen for the G900A

---------- Post added at 06:14 AM ---------- Previous post was at 05:25 AM ----------

And also, you find the date in the changelog for Flashfire. For anyone curious on the exact date
[AT&T Samsung Galaxy S 5] RebelLion_:
[MENTION=7597286]AptLogic[/MENTION] So I have a question. If I were to update to, say, QD1 Marshmallow 6.0.1 on the G900A, would I be able to flash the "experimental" firmware and root on lollipop again if I choose to revert after upgrading? Very curious about the Marshmallow experience on the S5 as I'm getting a little tired of some of the instability of its root. But I am anxious for the new version of X ROM and don't want to lose the ability to try a new ROM
[AT&T Samsung Galaxy S 5] AptLogic:
Yes, downgrading to the experimental firmware is supported on all Android releases for the G900A. You'll be fine.
[AT&T Samsung Galaxy S 5] RebelLion_:
Ah that's amazing, I've been so back and forth about upgrading to try it out but didn't want to miss out on your great work :D. Will be upgrading probably tonight and eagerly awaiting your next release of X ROM. Thanks!
[AT&T Samsung Galaxy S 5] RebelLion_:
Update: I flashed to QD1 successfully, however I am not able to login to my Samsung account during the initial setup. It tells me "unable to process" or something. And I tried factory resetting while on stock OF3 but it doesn't work. Pressing "reset device" after entering my credentials does nothing. So I'm essentially locked out once I upgrade. Any ideas would be appreciated
[AT&T Samsung Galaxy S 5] Diabolical_Mir:
Hey guys,

I used the Odin method to upgrade my AT&T Samsung S5 G900A from Kitkat4.4.2 straight up to Marshmallow 6.0.1. QD1.

Can I use the method listed in the first post of this thread to root my device?
[AT&T Samsung Galaxy S 5] AxelAndy:
Yes.
[AT&T Samsung Galaxy S 5] superGrumpy:
I made this account just to say THANK YOU! This worked flawlessly with my G900A (AT&T), which up to this point I thought was impossible. The entire process took about 20 minutes from start to finish, most of which was waiting time.
[AT&T Samsung Galaxy S 5] Diabolical_Mir:
Hey,

I have an unrooted S5 G900A, and I have been thinking about rooting it, and came across your post about how Flashfire provided in the zip in the first post was causing issues due to date

Can these issues be circumvented if you just use the latest version of FlashFire 0.73 from the play store using the link below?

https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=en_US

Or pay for the pro version of 0.73 and use that instead? The question is that do we HAVE to use the flashfire.apk provided in the first post of this thread?
[AT&T Samsung Galaxy S 5] Diabolical_Mir:
Hey, thanks for the info. Just to be clear, the method listed in the first post will work regardless of what kernel or baseband version I have running? (I have attached a screenshot of my phone information)

Further, I wanted to ask, I assume that the pre-rooted ROM OF3 that is flashed in step 3 of post 1 is Lollipop 5.0?

Are we stuck on Lollipop 5.0 if we want to keep root?

Also, apologies if this is a stupid question, but if I were the follow step 1 and flash the experimental firmware, then follow step 2 and install SuperSu, and Towelroot, to gain root, and not proceed to installing the pre-rooted ROM in step 3, am I correct in assuming that I will have root on my QD1 Marshmallow that will not be persistent, and will revert back to not rooted after I reboot the device or will it result in a soft/hard brick?

Finally, a User was mentioning that he had trouble with date bombs with FlashFire, and I wanted to know if these problems can be circumvented using the latest version of FlashFire from the Play Store, or if we MUST use the flashfire provided in Post 1?

I am mentioning [MENTION=7597286]AptLogic[/MENTION] as this is his thread, and he may be the most qualified person to respond to these questions.

I have poor vision (legally blind), and my biggest problem is with being able to see black text on a white background. All I really want is the ability to have a system wide theme of white text on black background. Currently, I use apps where I can manually set the background to black, but this is on a per app basis. And for some reason, I cannot change the default dialer on the Stock QD1 ROM as the AT&T g900a forces me to use the inbuilt AT&T dialer.

I am looking towards either installing substratum, Samsung's own theme engine which you can do if you have root, or install the Alliance ROM which appears to have a builtin theme engine.

Any information/responses would be most appreciated.

Edit;

Is the modified "from-noship" pre-rooted OF3: https://www.androidfilehost.com/?fid=673368273298933039 in Post #1 and the G900A_OF3 pre-rooted stock ROM https://www.androidfilehost.com/?fid=24052804347788226 from Post #3 the same ROM/File? Or is the first one only for completing the rooting process, and the second one needed to be flashed before flashing a ROM?
[AT&T Samsung Galaxy S 5] scoobydooami:
Hi all. I have an AT&T Samsung Galaxy S5 which I have discontinued service with as I upgraded to an S9 through Comcast. I would like to use this device for books, music and the like. All I want to do is root it so that I may uninstall the AT&T/Samsung bloatware. I don't intend to flash any custom roms.

Model number is Samsung-SM-G900A

Android version is 6.0.1 - Marshmallow

Baseband version is G900AUCS4DQD1

If I'm reading the very first post of this thread correctly, can I just flash the experimental firmware for the OS, then install flashfire, towelroot and the supersu, then run towelroot and be able to install an app which requires root to remove the bloatware?

I imagine I'll still be stuck with the AT&T bootloader? If so, I can live with that.

Thanks, in advance
[AT&T Samsung Galaxy S 5] AxelAndy:
The *experimental* firmware flashed in step #1, is an engineering ROM (KitKat). (Your phone won't be on QD1 after flashing this.)

Step one resets the phone's date to January 1, 2014, so you shouldn't have to worry about FlashFire working. If FlashFire closes on you (as it might after you have completed all the steps and try to use it again), will have to set the phone's date to before April 1, 2018. This is true with the latest version of FlashFire also.

Yes, it will work regardless of what kernel or baseband version.

Yes, we are stuck on Lollipop 5.0 (OF3 is 5.0) if we want to keep root.

There are some nice roms to try though:

https://xdaforums.com/att-galaxy-s5/general/unofficial-list-roms-t3440214

---------- Post added at 04:33 AM ---------- Previous post was at 04:00 AM ----------

They are NOT the same file.

---------- Post added at 04:36 AM ---------- Previous post was at 04:33 AM ----------

In order to gain root access, you have to follow the steps which result in your phone having rooted Lollipop (Android v5.0).
[AT&T Samsung Galaxy S 5] Diabolical_Mir:
Hey, thank you so much for taking the time to respond to my extremely long post.

I just have two final question that I hope that you can address.

With regards to this point, any idea why it would do this? Does it have something to do with the file (modified OF3 rooted ROM from step #3 in Post #1)? Does it matter if I am using the Pro version of FlashFire?

Finally, lets say I go through the process, and end up with a rooted version of Lollipop 5.0. If I decide that I was better off with unrooted Marshmallow 6.0.1 QD1, can I just put the phone in download mode, and use Odin to flash the G900AUCS4DQD1 update or do I need to first rollback using Odin to the COI5 update mentioned in post #2 of this thread, and then follow that up with a flash to QD1?

Once again, thanks so much for your help.
[AT&T Samsung Galaxy S 5] AxelAndy:
FlashFire checks if you have the Pro version when you open it. If you don't have the Pro version, FlashFire checks the system date and then closes if it's not before April 1, 2018. (It has nothing to do with the version of the ROM.)

You can Odin flash directly to (stock unrooted) Marashmallow at any point.
[AT&T Samsung Galaxy S 5] Diabolical_Mir:
Thank you so much for the info!

Can you recommend a custom ROM like the Alliance ROM that allows me to set the background colors for the system apps such ass Settings/Notification Panel/Dialer/etc? I can use the Alliance ROM but it is 1.4GB in size, and I have been reading the thread you linked for me earlier where many Users have complained that it has gotten slower over time.

I really like that the APTOS2.5 is only 500MB or so in size, but I have no Idea if it will give me the ability to set background color to black for system apps, or if I can use some third party tool to do this? Do you have any ideas/suggestions tips?

Thanks in advance!
[AT&T Samsung Galaxy S 5] AptLogic:
Yeah no

They are not the same file. While they may serve to install the same ROM, their method installation, as we as what's included in the package, is slightly different.

The from-noship OF3 contains extra bootloader and radio binaries that are needed to safely upgrade to OF3. You can see this is true by attempting to use the regular muniz_ri prerooted OF3 to go from rooted KitKat to lollipop. If you were to try that (which I have), the phone won't boot and you'd have to go back to KitKat and start over.
[AT&T Samsung Galaxy S 5] AxelAndy:
Thanks for the correction.

I made an Odin flashable file containing non-hlos.bin, recovery.img, rpm.mbn, sbl1.mbn, sdi.mbn, tz.mbn, aboot.mbn, boot.img, modem.bin from stock OF3 that would make an easy fix in that situation. (It also removed the custom padlock when I flashed it after installing Phoenix v11.)

---------- Post added at 12:43 PM ---------- Previous post was at 12:33 PM ----------

Sorry, I don't have a recommendation for you.

I didn't use the Alliance Lollipop ROM. (I prefer the Phoenix v11 Lollipop ROM.) I know that phones can slow down over time (with usage) with pretty much any ROM though, so you might just want to give it a try. I used the Alliance KitKat ROM for years, and loved it.
[AT&T Samsung Galaxy S 5] scoobydooami:
Thank you so much. Okay, so directly after flashing the firmware, I install towelroot, supersu and flashfire, then do I need to install OF3 BEFORE installing OI5 or do I skip OF3 and flash OI5?

Also, I don't see a link to unrooted QD1, to return it to unrooted Marshmallow should I mess things up.

Sorry if I sound not too bright or if I have missed a post linking to that. I just really, really don't want to accidentally brick it.

Thank you.
[AT&T Samsung Galaxy S 5] Diabolical_Mir:
In post #1 of this thread, it says you need to flash the modified OF3 file (link is provided).

I am not sure where you're getting OI5 from, but if you mean OI5 from Post #2, that is provided only for you to rollback to an unrooted stock firmware in case something goes wrong during the rooting process, or during the installation of the custom ROM process.

Here is a link to the full QD1 Odin update. https://xdaforums.com/att-galaxy-s5/general/g900aucs4dqd1-odin-update-v6-0-1-t3603897

Instead of rolling back to OI5 in case of something going wrong, you can just use Odin to flash the official QD1 update at any point. I have quoted one of the members below who confirmed this information a few posts back.
[AT&T Samsung Galaxy S 5] scoobydooami:
Okay, thank you. I was confused. I thought that I had to flash OI5 in order to have Android be at Lollipop after flashing the OF3 file.

What version of Android will the phone be on, at that point, please?

Thank you.
[AT&T Samsung Galaxy S 5] Diabolical_Mir:
Android 5.0 after finishing step 3 and flashing OF3.
[AT&T Samsung Galaxy S 5] tredfield1:
Can't get past step one

I have a 900A fresh out of the box with 5.1.1 After flashing with odin (no errors) it just boots to a black screen. When I try to restart it goes into kernel panic. I have reflashed several times same result. When plugged in my pc still sees the phone and I have access to the files. What am I missing here?
[AT&T Samsung Galaxy S 5] Diabolical_Mir:
Have you tried maybe flashing to another firmware like unrooted OF3 version provided for a rollback in Post #2, and then retrying step 1 in Post #1?
[AT&T Samsung Galaxy S 5] tredfield1:
Tried that and with 5.1.1 stock too. Get "Software not authorized by ATT..... turn of and take to store"
[AT&T Samsung Galaxy S 5] AxelAndy:
Did you flash the "*experimental* firmware" from step 1 ?
[AT&T Samsung Galaxy S 5] tredfield1:
Yes the experimental flashed without error in odin. Still no joy.
[AT&T Samsung Galaxy S 5] Diabolical_Mir:
So, the experimental firmware isn't working for you. I assume you flashed it as per the instructions such as loading the firmware in the AP slot, and so on.

Have you at least been able to rollback your phone using one of the rollback files in Post #2 of this thread so as to get it back to operational condition, or are you currently in a soft/hard brick situation?
[AT&T Samsung Galaxy S 5] tredfield1:
Soft bricked at this point. When I roll back I get the "Software not authorize ... head to ATT store" I have loaded using the AP slot and still get "kernel panic" sometimes or just the samsung logo and ATT sound jingle then to black screen. PC still sees the drives on the phone with the back screen situation.

I also tried the unbrick fix here

So the main thing I have learned is I should have bought the T-Mobile version of this phone.
[AT&T Samsung Galaxy S 5] Diabolical_Mir:
So you were unable to unbrick your phone? I was on the fence about going through the rooting process on my Galaxy S5, but I'm not going to do that now.

Did you try booting into the stock samsung recovery and wiping the cache partition after flashing the stock firmware?
[AT&T Samsung Galaxy S 5] tredfield1:
Update: I got the phone functional again on 5.1.1 The stock file I found also had files in addition to the AP slot file. After loading the AP slot I still got the "Software not supported message". So I figure I had nothing to lose and also loaded a file named BL_G900AUCS4CPA6_CL5869384_QB10479026_REV00_user_low_ship_MULTI_CERT.tar in the BL slot and it worked So at least I am back to where I started.
[AT&T Samsung Galaxy S 5] Diabolical_Mir:
The stock recovery firmware provided in Post #2 is a zip file that has FOUR files. The link below is taken from Post #2 of this thread.

https://androidfilehost.com/?fid=24438995911970945

So, when you're flashing that file, you need to have all four of your AP, BL, CP, CSC slots in ODIN to be populated with their respected files that you have extracted from the zip. The exact instructions are provided in Post #2 of this thread.

So, how you're only using two slots, and what firmware/file you're using, and it ending up with a working device is a bit of a mystery to me. Either way, you need to do a proper flash. Wipe cache/data partition, all that good stuff.

Then try Step 1 in Post #1 again and see if that helps.
[AT&T Samsung Galaxy S 5] tredfield1:
So it flashed just fine but step one of the the new method gave the the same result (yes I wiped the cache) boot to black screen. So when I have time I will try the old method. Thanks for the advise.
[AT&T Samsung Galaxy S 5] ahvamaria:
Be sure to flash all 4 of these filed at once In Odin, yes this works.
[AT&T Samsung Galaxy S 5] mls76:
Root and recovery
[AT&T Samsung Galaxy S 5] ahvamaria:
QD1 is MM stock. I am on it.

---------- Post added at 04:56 PM ---------- Previous post was at 04:50 PM ----------

I too got tired of all the rooting, especially since it is the AT&T splashscreen/sound I only wanted to dump. QD1 MM stock is sooo much nicer and smoother than Lollipop, use "package disabler" app from appstore (cost 1.49) to disable the AT&T bloat apps, they dont even run in background. Works. I could not retain root in any way shape or form from 5.0.1. but from what I understand can revert back through the previous process, I will just have to live with the carrier splash screen, with the bloat disabled mm was worth it. ...:eek:
[AT&T Samsung Galaxy S 5] Diabolical_Mir:
Were you able to change your default dialer to something other than the builtin dialer when you were on rooted lollipop?
[AT&T Samsung Galaxy S 5] ahvamaria:
Yes ?
[AT&T Samsung Galaxy S 5] cuaran89:
Hi everyone,

Hope everything is going well.

I wonder, can I use the original root method in post #1 to root my Galaxy G900AUCS4DQD1 V6.0.1 ?

Thanks for your time.
[AT&T Samsung Galaxy S 5] AxelAndy:
The method is post #1 will work for you.

You will be downgrading and then flashing to G900AUCU4BOF3 V5.0 in order to have root.
[AT&T Samsung Galaxy S 5] dkwemn:
["Step 1: Goin' Wayy Down

Use ODIN to flash the experimental firmware.

MASTER CAUTION: This will wipe ALL data on the device!! Backup your stuff before proceeding. I nor XDA is responsible for loss of your memes!

Simply flash the .TAR.MD5 file in the zip using the AP slot in ODIN, and then wait for the phone to boot (which is literally all of 10 seconds). /]

Step 3: Back to the Future!

Open FlashFire, grant it root access, and flash the modified OF3 with these settings:

Mount /system read/write

A wipe isn't required, but it is recommended (if you do wipe, make sure to put that card B E F O R E the flash zip/ota card!)

Hit "flash", let it flash, reboot, and load."

I'm a newbie to this, but just carefully used this on my used Samsung Galaxy S5 ATT version & it worked perfectly, thanks!

Just 2 things for newbies :

1. After the Flashing with Odin, & the process completes at "Leave CS..", you must hit the "START" button for the phone to reboot.

2. FlashFire must have been updated since this last updated post, since the flash process is now fully automatic; just search for & choose the firmware package, then the app simply fills-in the process fields for you to simply push the "flash the firmware" button & voila! :)
[AT&T Samsung Galaxy S 5] mr_horsepower:
I bought a AT&T G900A today that I want to root. it's running 4.4.2 with a baseband version 2ANG3 with a kernel build date of 4/2014.

Is this the best method for me to aquire root, or should I be looking towards some of the other methods that existed prior to most all kernels being patched back in 7/14?

If it's not the best method, what would be?

If it is the best method, where do I start this process since I don't have to revert to an earlier version?

If this applies, Is there any reason for me to try and stay on 4.4 or should I definitely update to 5.0?

*I swear I've been reading up and trying to research this to avoid asking obvious/ easy questions, but it seems I'm in a unique situation with my phone not having been updated ever plus I've been reading up on this most all night and I'm only getting dumber now by the minute.
[AT&T Samsung Galaxy S 5] AxelAndy:
You can just start at Step 2 and use towelroot to root your phone, then install supersu. You can stop there, but I would continue to Step 3 and update to 5.0 because my baking app and many apps available in the play store won't work on kitkat.
[AT&T Samsung Galaxy S 5] dkwemn:
RE: [GUIDE] Root, ROMs, and Other Cool Stuff Step #2

This actually threw me off a day in rooting my sm-900a, because I went strictly by sequence, not realizing that step #2 was a "just-in-case" if step#3 didn't work; had to start all over again at Lollipop 5.0 before I got it right, but I DID! :)
[AT&T Samsung Galaxy S 5] mr_horsepower:
Ok, so I'm currently rooted, have su and I've verified root after a reboot, all good there. I'm running the stock rom with adblock, a firewall, I'm not watching vids and I've got auto retrieve turned off on mms (stage fright protection).

My questions are -

1. Although I've got an earlier, 4/14, bootloader (so prior to them getting updated in 7/14), it's still not an unlocked bootloader is it?

2. Will anything about updating it with a new kernel to match a newer, custom rom, keep me from being able to revert back to it later, or would that have only been a concern with factory ota updates?

*i feel like i stumbled across a real gem having found this barely used, pristine, never updated at&t s5 and i don't want to do something that had i slowed my roll a little bit i would've done differently.

3. Any basic, no frills rom recommendations?

*I'm not much on animations or fancy b.s., i hate the factory 4.4 dialer, i need the camera to function as good as possible (although i could live without some of the settings the stock camera has. I use auto, low light occasionally, never used the front facing cam, never took a selfie in my life. . .. never even been on facebook in my life), and i do like watching news clips, videos and occasionally a movie on my phone.
[AT&T Samsung Galaxy S 5] mr_horsepower:
I updated to 5.0 using the "fromnoship" ROM from the first post of this thread. is there any reason to not use this ROM as my daily driver, or is there anything to be gained by not having the additional bootloader and binaries (per the OP in post #2118) taking up space on my phone?

*the only thing keeping me from flashing the stock, rooted ROM (with a single bootloader) in post 3 of this thread is I got this one debloated and set-up like I want prior to reading about the extra bootloader installed with this ROM and then my not knowing if it mattered.

*for anyone inclined to stick with the stock, rooted 5.0 ROM like I did (from post 1), know that it (and any ROM from that era I'd think) will need patched due to having critical stagefright vulnerabilities. this one had all but two patched, CVE-2015-3864 & CVE-2015-6602.