yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A3, A5, A7 (2017) Questions & Answe] lamplighter13:
Here you go;

http://www.mediafire.com/file/kmq4n024l1pakun/recovery.img

http://www.mediafire.com/file/jdelguvg72zt0a1/param.bin

http://www.mediafire.com/file/qhtxuwvkm9aqv9t/boot.img

If you need anything else just let me know.

Cheers, LL- :highfive:
[Samsung Galaxy A3, A5, A7 (2017) Questions & Answe] zainifame:
Thanks :)
[Samsung Galaxy A3, A5, A7 (2017) Questions & Answe] mahdimilanix:
Hi my friend

Please help me how to use this files

Thanks for helping me
[Xiaomi Redmi Note 3 Questions & Answers] faisalwin7:
somehow I found Redmi note 3 are difficult to connect to several access point that using 5Ghz. Even using Stock or Custom ROM (in this case , nitrogen OS).

is there any fixes yet? Thanks.
[Verizon Galaxy Note 4 Q&A, Help & Troubleshooting] ticholas:
Newbish post. As the title states, I'm hoping us 910V users can get some love and start seeing some RR Builds
[Verizon Galaxy Note 4 Q&A, Help & Troubleshooting] Bren123:
I wish to but there is no public Marshmallow or nougat device tree and there's only one person with one and that's [MENTION=5868929]hsbadr[/MENTION] he does not share.

---------- Post added at 04:42 AM ---------- Previous post was at 04:40 AM ----------

I have heard of flashing N910F resurrection remix and it works but data doesn't work can't really confirm.
[Verizon Galaxy Note 4 Q&A, Help & Troubleshooting] ticholas:
Added poll to possibly persuade dev interest
[Verizon Galaxy Note 4 Q&A, Help & Troubleshooting] mojoswagger1980:
considering hsbards affiliation with team emotroid it is most likely not his property to hand out .
[Verizon Galaxy Note 4 Q&A, Help & Troubleshooting] mojoswagger1980:
.

it is my firm belief he's just using the 910f device tree listing .....I'm basing that on his affiliation with emotroid who pretty much exclusively dev for the international varient . the 910f device tree is on github so is multisystem kernel . off u go then. PS : any 910f ROM will install/load/run on the 910v as long as you are on the same firmware/bootloader combination . you cannot have updated the firmware beyond BL however to maintain compatability. as far as the data is concerned the data fix from Dr ketans 6.0.1 ROM should fix (might be necessary to manually enter APN given the international varient isn't carrier branded)
[T-Mobile Samsung Galaxy S 5] bobbylo:
3 most recent odin flashable bootloaders and modems For S5 G900T&T3 From 12/16 - 4/17

These were created from the stock roms and tested on my g900T using odin 3.11.2

So,if you want to update your bootloader and modem without having to flash the stock rom,then these are what you need.

Instructions:

Turn off your phone completely and manually boot into download mode.

Open odin 3.11.2,then plug your phone into your usb,and make sure odin sees it.

Load the bootloader into the BL tab of odin.

Load the modem into the CP tab of odin,and check the reboot

Hit start.....

The G900T will NOT work with the G900T3,If you need the G900T3 files,please download the right ones,towards the bottom of the page

As always,flashing is risky,so i am not responsible if you blow up your device..

G900TUVS1GPK3 Modem --> https://www.androidfilehost.com/?fid=529152257862710896

G900TUVS1GPK3 Bootloader --> https://www.androidfilehost.com/?fid=529152257862710897

G900TUVS1GQA2 Modem --> https://www.androidfilehost.com/?fid=673368273298939131

G900TUVS1GQA2 Bootloader --> https://www.androidfilehost.com/?fid=673368273298939132

G900TUVU1GQC2 Modem --> https://www.androidfilehost.com/?fid=745425885120722406

G900TUVU1GQC2 Bootloader --> https://www.androidfilehost.com/?fid=529152257862717494

(G900T3 ONLY) G900T3_GPK3_Bootloader--> https://www.androidfilehost.com/?fid=745425885120743020

(G900T3 ONLY) G900T3_GPK3_modem--> https://www.androidfilehost.com/?fid=889764386195910331

(G900T3 ONLY) G900T3_GQC2 Bootloader--> https://www.androidfilehost.com/?fid=817550096634777324

(G900T3 ONLY) G900T3_GQC2 Modem --> https://www.androidfilehost.com/?fid=673368273298962831

Here is the link to the Full TMB-G900TUVU1GQC2 stock rom.Extract the zip and load the md5 in CP tab of odin.

https://www.androidfilehost.com/?fid=673368273298945491

If i helped you out,please hit the thanks button
[T-Mobile Samsung Galaxy S 5] X_Mojahed:
Good work Bro

Thanks
[T-Mobile Samsung Galaxy S 5] bobbylo:
your welcome,glad you made use of them..
[T-Mobile Samsung Galaxy S 5] Jhfreeze:
Thanks for this, i needed a way to update those without going the long way.
[T-Mobile Samsung Galaxy S 5] bobbylo:
NP,i updated the long way,then decided to learn how to create these.Of course,i tested them on my own device first.If any newer ones come out,i'll make those and post them here also. Thanks
[T-Mobile Samsung Galaxy S 5] SuperBrolySSJ:
Are these from stock marshmallow roms?
[T-Mobile Samsung Galaxy S 5] bobbylo:
Yes they are,all marshmallow.....
[T-Mobile Samsung Galaxy S 5] DickyG:
This is driving me nuts...I'm following the instructions. Odin is recognizing modem and my phone...but when I hit "start" it's giving me a "fail" message immediately after "now writing...please wait about 2 minutes" I've tried 3 USB ports and 3 cords. I have a 5.1.1 modem and can't flash to 7.x unless I update my modem to MM. I have no idea what to do.
[T-Mobile Samsung Galaxy S 5] bobbylo:
Your using the G900T right??Are you running a custom rom?Try downloading the file again.Also,what odin version are you using?
[T-Mobile Samsung Galaxy S 5] DickyG:
Yes...G900T...currently running CM13.0 but would like to upgrade to one of the Nougat ROM's. My Odin version is 3.11.1...I know you call for 3.11.2...I'll download it if you think it will really make a difference.

Thanks...
[T-Mobile Samsung Galaxy S 5] bobbylo:
Yeah,try using Odin 3.11.2...Also,try turning the phone off,remove the battery for a minute,then boot into download mode.Also,are your USB drivers up to date on your computer?...If you can't get it to work still,you may have to flash the latest stock rom to get the modem and boot update,then just reflash TWRP,and restore your backup...
[T-Mobile Samsung Galaxy S 5] DickyG:
For some reason or another, Norton is kicking 3.11.2 off my computer...but I've even tried a newer version...3.12.3...still didn't work. I always do a battery pull before flashing and (according to Windows) my USB drivers are current. I thought about flashing a stock rom but that requires Odin and if I can't flash a modem, I certainly can't flash a ROM. Geez...the phone gods hate me!
[T-Mobile Samsung Galaxy S 5] bobbylo:
Get rid of Norton,uninstall it...Its got to be norton....No one else has had a problem flashing these files...try uninstalling norton,then try again..Got to be something on your computer..What windows are you using?
[T-Mobile Samsung Galaxy S 5] DickyG:
Well, I tried disabling Norton...same result. Using Windows 10. The computer is new...Christmas present...but that doesn't mean its foolproof. Tomorrow I'm gonna download Odin and a couple modem files to my wife's laptop and try again. I think your instructions are fine...I've used every port and every USB cord I can find...maybe my computer has some sort of glitch...who knows.
[T-Mobile Samsung Galaxy S 5] bobbylo:
Well,can't speak for windows 10. don't like anything past windows 7. I run a dual boot windowsXP-windows 7 PC,I use the windows 7 to do all flashing.What OS is your wife's laptop? Let me know how it turns out.
[T-Mobile Samsung Galaxy S 5] DickyG:
Failed again...tried on wife's laptop (windows 8.1)...made sure to use 3.11.2 and Samsung USB cord...recognized phone and failed as it always does...right after "writing...wait 2 minutes". Got to be a glitch in my phone somewhere and I don't think I want to go through the aggravation of doing a complete system wipe. I do have an old Dell desktop running XP in the closet...maybe I'll break it out and try it...but like I said, I think it's my phone. Thanks for all your help.
[T-Mobile Samsung Galaxy S 5] bobbylo:
I find it hard to believe its your phone...i don't think windows XP will work,Tryed it once,and its just too old of a operating system...If you know someone with a windows 7 computer,you can try that..Mine always works find when i boot into windows 7 and flash.Its very possible its those newer windows versions that are doing it..But i can't say for sure.Good luck with it,and let me know how it turns out.

You did try with all the modems and bootloaders i posted here,right?
[T-Mobile Samsung Galaxy S 5] DickyG:
I've let this sit for a few days and am pretty much out of options. I've used every port on my Windows10 desktop and wife's Windows 8.1 laptop...multiple Samsung cords (including the original one), multiple Odin versions, every posted modem. Windows says my drivers are up to date and Odin recognizes my phone every time. The only thing I can think of is that somehow my phone has developed a glitch..doesn't seem logical because it is working fine...but who knows. Have even tried to flash with Norton disabled, bluetooth disabled..and who knows what else. Not even thinking of trying to flash back to stock since I can't even flash a modem. But what about bootloaders? Have not tried to flash the comparable bootloader because I don't see how that effects the modem..but what do you think?
[T-Mobile Samsung Galaxy S 5] bobbylo:
Yeah,What bootloader are you running?
[T-Mobile Samsung Galaxy S 5] DickyG:
FOG6...same as the modem...came with the phone...supports 5.1.1. Haven't tried to flash the comparable bootloader yet because: 1. I never thought about it and 2. I figured if Odin didn't let me flash a modem, probably wouldn't let me flash a bootloader either.
[T-Mobile Samsung Galaxy S 5] bobbylo:
When i flash a modem,it looks at the bootloader....Try flashing the GPK3 bootloader...So your also running a 5.1.1 rom?
[T-Mobile Samsung Galaxy S 5] DickyG:
Running CM13 (6.0.1). When I flashed up from Lollipop the bootloader and modem never changed. The problem arose when I flashed Lineage and lost data connection after I left wifi range...it was suggested to me that I couldn't run a 7.1 ROM with a 5.1.1 modem. So I've been trying to flash a MM modem ever since.

My wife has MM stock with the CQg2 modem....that's the one I would ideally like. Should I try the comparable bootloader first or both at the same time?
[T-Mobile Samsung Galaxy S 5] bobbylo:
you can do them both at the same time,just put them under the right tab.Bootloader goes into the BL tab,and modem goes into the CP tab in Odin 3.11.2

Odin will automatically flash the bootloader first...Go for it,i think thats the whole problem.Trying to flash a MM modem with a LP bootloader...

By the way,when you flash an updated rom it does'nt include the the bootloader and modem.Only when you flash a stock rom those are updated
[T-Mobile Samsung Galaxy S 5] Destroky:
Bad USB Cable

I was running into problems whenever I tried to flash anything with Odin. It turns out the USB cable was bad. I used my original USB 3.0 cable and it worked like a charm! :good:

Thank you for uploading these, especially the T3 version. It usually doesn't get as much love as the T.
[T-Mobile Samsung Galaxy S 5] bobbylo:
No problem,I will be uploading the bootloader and modem for the firmware prior to the newest one in a few minutes.Always nice to have a few different modems to try..
[T-Mobile Samsung Galaxy S 5] DickyG:
Just downloaded the K3 stuff...probably won't get to it until next week but I'll flash it...thanks for posting it.
[T-Mobile Samsung Galaxy S 5] bobbylo:
No problem,At least there's two to choose from now,for all the T3 people
[T-Mobile Samsung Galaxy S 5] invisiblewave:
Thanks for these! I just updated my Resurrection Remix 900T3 without having to restore anything and without any data loss. Much better than flashing the full update image. This was my full procedure:

Download the tar files in the OP.

Boot into Download mode.

In Odin (3.09 is the only version I can get to work on W7), uncheck AutoReboot.

Click BL & select the bootloader tar.

Click CP & select the modem tar.

Click Start.

When finished, boot into stock recovery with Vol+, Home, Power, then reboot to System. I've found this step necessary in the past, it does something subtle but I forget what.

Reboot to Download mode, click on AP & select TWRP image (or whatever recovery you're using).

Make sure AutoReboot is UNCHECKED.

Click Start.

When finished, boot into TWRP with Vol+,Home,Power. If you skip this step, stock recovery will be restored on boot.

Reboot to System.
[T-Mobile Samsung Galaxy S 5] bobbylo:
Hey invisible,i don't get it..Why did you have to flash twrp again if you were running RR and you were just upgrading the bootloader and modem?Do you have to do that with the 900T3?
[T-Mobile Samsung Galaxy S 5] invisiblewave:
Good question, I'm not sure. My guess is that the bootloader includes recovery.
[T-Mobile Samsung Galaxy S 5] bobbylo:
Hummm...that may explain why all the G900T bootloaders are 1.9mb and the G900T3 is 2mb.I thought that little extra was maybe the factory reset protection that the T3 has.So,its gotta be the stock recovery i quess...

interesting...
[T-Mobile Samsung Galaxy S 5] invisiblewave:
Are you sure it doesn't do it on every device? Most things you flash make changes to the bootloader, and I'm guessing TWRP does too, which would mean that replacing the bootloader would also require replacement of the recovery.
[T-Mobile Samsung Galaxy S 5] bobbylo:
I'm almost positive i didn't have to do it on mine.i have the 900T...And i do remember when i extracted the stock firmware there's a file named recovery,thats not included in the bootloader files...I'm gonna check it

Update: I reflashed from the GQC2 down to the GPK3,and still had my twrp,even after reboot.Then flashed back up,and still had it.That recovery.img is present in both the G900T and T3 factory firmware,don't know if thats part of the stock recovery,but thats not used in building the bootloaders.Its also around 15mb.
[T-Mobile Samsung Galaxy S 5] invisiblewave:
Maybe I booted into Download rather than Recovery? I'll pay closer attention next time!
[T-Mobile Samsung Galaxy S 5] marvinnn:
After weeks of frustration with terrible cell service under Lineage OS 14.1 I stumbled across this page to update my bootloader and modem from G900TUVU1FOG6 to G900TUVU1GQC2. I loaded everything into ODIN and got a PASS! and my phone rebooted like normal. However when I go into settings can check my baseband it still reports FOG6.

Any suggestions on what I might have done wrong? Should I just repeat the process and hope the second time's the charm?

Thanks!
[T-Mobile Samsung Galaxy S 5] oocubain:
As of 2017-11-18 I think G900TUVU1GQC2 is still the latest version for G900T, at least according to sammobile

I am attempting to update on linux and I am using latest heimdall from git. For some reason my heimdall-frontend looks different than the screenshots here, there doesn't seem to be an option to just do specific parts. So I am attempting to use the command line heimdall tool.

I did a "print-pit" to get a dump of all the entries, partition names, flash filenames, etc. Then I untar'd the two GQC2 files mentioned at the start of this thread into a directory and ran the following with the phone in download mode:

heimdall flash --MODEM modem.bin --SBL1 sbl1.mbn --APNHLOS NON-HLOS.bin --DBI sdi.mbn --ABOOT aboot.mbn --RPM rpm.mbn --TZ tz.mbn --no-reboot

All were uploaded successfully and heimdall completed the session and then I rebooted.

When I go into phone status for "Baseband version" I still see the old "G900TUVS1FOL1" version I have always had. Should that update? I wasn't sure if it should so I was trying to use other ways to determine if the bootloader and modems got updated. I found an app call "Network Signal Info" that provides some info on it's "system info" tab. It lists "Bootloader: G900TUVS1FOL1", "Radio/Serial: G900TUVS1FOL1 / ########", but interestingly it's got "Fingerprint: samsung/kltetmo/kltemo:6.0.1/MMB29M/G900TUV1GQC2:user/release-keys".

Am I running the newer bootloader and modem? Anything wrong with how I updated them? Any other ways I can check the versions?

Thanks, this thread has been very helpful.
[T-Mobile Samsung Galaxy S 5] kckish:
Difference between PK, QA and QC?

If they are all for the SM-G900T and Marshmellow, what is the difference between the bootloader/modem files ending with PK*, QA* and QC*?

I'm trying to test replacing just the BL with ODIN (already flashed TWRPs successfully) to see if it affects the user data partition. Does it matter which one to try?

SM-G900T: Running Android 6.0.1 (MM); Baseband: G900TUVU1GPE1

Thanks in advance! :)
[T-Mobile Samsung Galaxy S 5] comexx:
Will these work for Nougat? I'm using LineageOS 14 nightly with Android 7.1.2.
[T-Mobile Samsung Galaxy S 5] cat_dev_nu11:
Have the same question. Can anyone clarify what the differences in modem/bootloader pairs are for the G900T, and how we figure which pair to use?
[T-Mobile Samsung Galaxy S 5] cat_dev_nu11:
My current baseband version is G900TUVU1CNK2. I'm on CM 12.1 (Android 5.1.1).

Any pointers to clarify which pair of G900T files I'd need would be very appreciated. This is my first attempt flashing, I don't want to brick my phone from guessing and picking the wrong of the three pair.
[Galaxy Grand 2 Q&A, Help & Troubleshooting] honghongleong:
Guys my phone emmc chip is dead will putting the motherboard inside the freezer helps or any other ways.

My warrenty has expired.
[Google Pixel XL Questions & Answers] droidan:
Hello, Iam having a bricked Google Pixel XL 128GB with black screen, no fastboot, no recovery(phone only detected as HS-USB QDLoader 9008).

Is there anyway to unbrick the phone?
[Google Pixel XL Questions & Answers] fiffan86:
What was your setup before this happened? What were you trying to do before this happened?
[Google Pixel XL Questions & Answers] droidan:
Bad Flash on OTA update :eek:
[Google Pixel XL Questions & Answers] 5.1:
Hey... Actually, there's no easy way to get the pixel back up and running. I tried to read a bit about the issue on different phones. I'm not sure it could be of some use for our device.. It also involves, either having someone to pull a full backup of his phone for you which you'll have to find... Or finding special Qualcomm files and firmware used for flashing using Qualcomm tool QFIL... I haven't found Qualcomm files/firmware on the internet yet... And i'm not 100% sure the first solution would work either, since we have now different system partitions.

If you don't have any warranty on your phone, you could try it. Otherwise, send it back. There's likely no way to recover personnal datas anyway... :(

Also about getting out of EDL mode, i've read in the N6P forum, someone saying you'll have to push the power button for no less than 40 seconds. Try it maybe and try to reboot into bootloader afterward...

Good luck...
[Google Pixel XL Questions & Answers] droidan:
I tried QFIL, MSMToolDownloader(from OnePlus 3T), MiFlash, etc. They all ask RawProgramm0.xml, Patch0.xml, MSM8996..mbn, and xxx_firehose_emmc_8996.xxx specifically for our Google Pixel XL 128GB. None of them are available yet.
[Google Pixel XL Questions & Answers] 5.1:
Yeah I haven't found anything either. I think it will take some time before someone share those.

Check this thread:

https://xdaforums.com/yureka/help/question-qualcomm-download-mode-k-t3068040

This part:

2. REVIVING YOUR YU BACK

2.a NEW "Qualcomm HS-USB QDLoader 9008" MODE

As I said earlier, since our phone has a different partition layout, I don't know if the same process can be achieved. Also you'll have to pull the IMG from a working device.

You don't have a valid warranty? :(
[Google Pixel XL Questions & Answers] droidan:
Thank you for your reply and information.

I believe I have an OLD 9008 mode.

Here's what I have found:

1. The 8996 firehose is specific to the device. Other 8996 version do not work. (Oneplus 3T, ZUK, Xiaomi, LEECO)

2. Quote from Ghassani on Le Pro3 bricked thread:

"Since it was suggested to contact me about this issue, I am going to answer here what I told the OP through email:

This is a hard brick. Meaning, you probably flashed a wrong SBL partition, or you flashed in the wrong order, or in the wrong mode.

When this happens, and the device has secure boot enabled (which all production devices do) you only have two options:

1) Using a signed recovery programmer to send via emergency mode (Sahara mode), then transferring to that programmers protocol (streaming DLOAD or the newer firehose). From there you can recover the emmc.

2) JTAG on the emmc for direct recovery.

It is easy to find these programmer files, both signed and unsigned. The problem is each device is using a different private key generated by the OEM to build the SoC. Without a properly signed programmer, Sahara will reject the programmer and go into a no-interrupt loop until you power cycle the device. Pretty much all OEMs do not give out these files. The ones you can find floating around for various devices are generally leaked, or rarely given out by the OEM. For most devices, JTAG is the only option.

I have a small collection of both signed and unsigned programmer files on this github repository:

https://github.com/ghassani/openpst-assets

If anyone has properly signed files for devices I do not have, please send them in to me and I can add them or you can put in a pull request directly to the repository and add it that way."

Hopefully someone from Google/HTC can share those 3 files.(eMMc_firehose_8996.elf, rawprogram0.xml and patch0.xml for Google Pixel XL 128GB)

Or maybe I can ask Google assistant to leak the files..lol
[Google Pixel XL Questions & Answers] bobby janow:
What does that mean? Were you rooted, unlocked? If so return the device, no?
[Google Pixel XL Questions & Answers] 5.1:
Yeah, unless someone leaks official programmer, you are SOL...

Good luck... :good:
[Google Pixel XL Questions & Answers] wingman021280:
Hi guys,

I've opened a similar thread on google forum - related to pixel 128gb being bricked and in chipset download mode.

If there are enough bricked pixels out there perhaps google will (hopefully) share those files?

Cheers,

Dan
[Google Pixel XL Questions & Answers] markitzer00:
The deluge of bricked Pixels resulting from the Oreo update continues...

I did, however, find these pages posted in the last couple weeks, and wondering if they're the answer to the Q's posted earlier ITT (sry I'm too new to post live links, so you'll have to paste these):

- androidauthority.com/download-android-8-0-oreo-794622/

- androidauthority.com/install-android-oreo-758342/

- developers.google.com/android/ota

Earlier ITT, posters were saying that they couldn't find the firmware or other files that would allow someone to recover from the hard-bricked state...but are those 'official' factory images and OTAs what they were saying they needed, but which they couldn't find at the time? In short, might we now actually have the files necessary to save our bricked Pixels without engaging in Macguyvering that would void the warranty?
[Google Pixel XL Questions & Answers] Pain-N-Panic:
Out of curiosity, was your bootloader locked prior to running into this issue?
[Google Pixel XL Questions & Answers] markitzer00:
I assume so...I bought the Pixel directly from Google, so assumed I was getting the purest Android installation possible / no provider bloatware etc...if i'm not mistaken, the bootloader would have been Locked when I initially received the phone, right?...if so, then yes it would still have been locked when it bricked, as I didn't take any actions to unlock it (nor would i know how)
[Google Pixel XL Questions & Answers] Fast Unlocker:
hopefully files will be shared soon for sure it is exists
[Google Pixel XL Questions & Answers] almightysiman:
I have the same problem and all I can do is rma.
[Google Pixel XL Questions & Answers] GuestK00254:
Is it possible to pull the files from a working pixel?
[Google Pixel XL Questions & Answers] mattwheat:
I wonder if the files in question would hold the key to VZW Pixel XL customers to somehow use /find an exploit to gain temp root to ultimately unlock their bootloader. :confused:
[Google Pixel XL Questions & Answers] GuestK00254:
Maybe that's why they aren't giving the files