At wits end, but can't get my WiFi to turn on at all.
The setup l had before was stock Bell 4.4.2 but rooted and TWRP (with backups).
Forgot to turn off (replacement phone, forgot to turn off), auto-updates. Phone tried to update to 5.0.1 but failed, telling me to use Kies. Had to flash in Kies as my phone got stuck in Samsung's boot logo. Before plugging into Kies, l tried wipe cache, battery out, and then wipe/reset, none worked. So l plugged into Kies, it did it's thing. Went smooth. Now, my wireless just won't turn on at all. Rooted it with CF AutoRoot. Went to wpa_supplicant folder, to find l don't have the .conf file. Renamed the folder, power cycles, system created the folder but no file again. Created a file named "wpa_supplicant.conf" and power cycled, renamed it, system didn't create it again. So l think l found the issue but any fix to this? Maybe running the wrong version, even though l have stock Bell apps (how l missed them )
MODEL SGH-I337M
VERSION 5.0.1
BASEBAND I337MVLUFNI2
KERNEL 3.4.0-4508315 [email protected] #1
BUILD LRX22C.I337MVLUGOC4
KNOX 2.3 (TRIPPED)
Side note: I do get a WiFi MAC address that appears valid (haven't compared to my router logs) under status.
=================
Update I FIXED IT! YAY!
For those who are having the same issue. Do the following steps:
Download Odin 3 - Make sure Kies isn't running
Verify ID COM has a number like COM0 or something.
Leave everything else alone.
Download ROM from SamMobile or another ROM site Link (filtered to Bell)
Unplug phone
Place phone into download mode (Vol Down, Home, Power)
Using Odin, hit PDA and put the ROM in, give it some time
Plug phone in, and verify COM and message saying ADDED!!
Start it, then give it some time.
If you want to root it, do the same procedures but grab CF-Auto-Root and repeat it. Easy root.
Optional stepsbut l did it anyways:
Before doing this, l rooted it with CF Chain, and installed TWRP. Wiped Cache, Dalvik, System.
Hello dear friend
i wanted to thank you for your solution and specially download links, had the exact same issue which was resolved by the solution you provided.
I recommend flashing with Odin and a stock ROM from Sam mobile.com. kies has never worked for me so no now stick with Odin.
Related
recently got a Galaxy Note 3 from Verizon. I wanted to root the device, it was really easy with my old original galaxy so I looked at a few guides which were all using "Root de la Vega" and finally tonight in an attempt to root my device I used the guide at:
phonearena.com/news/How-to-Root-the-Verizon-Samsung-Galaxy-Note-3_id48247
I put the phone into download mode and connected it to Odin with the included Samsung USB 3.0 cable. I selected the root de la vega firmware using the AP button and hit Start to begin flashing. Almost immediately after the write starts it fails and on the phone it says:
Quote:
"Secure check failed: cache"
In the guide it mentions there may be problems using the USB 3.0 cable so I tried it with a USB 2.0 cable with the same results. I tried rebooting the phone to see if it had wiped it. Indeed, it had been wiped and is now going to the screen which says there was a problem updating the firmware and says to use the Software Recovery Assistant to restore the firmware.
I am not sure why this has happened. I feel like I followed the instructions to the letter. After looking at some different guides I am noticing that many have you put the phone into USB debugging mode which the guide I was following doesn't mention. Is this why it has failed. Is this strictly required?
I would like to get this device rooted, but now my number one priority is getting it back into a state where it will be more useful than the paperweight on my desk. I tried downloading Kies 3 which I read can restore the stock firmware on the phone. I was extremely annoyed when I realized that Kies 3 would not recognize my phone at all. It says that the device is not supported by Kies 3 and gives me a link to check support (which just brings me to the Kies download page which clearly states that my phone (Note 3) is supported. I even tried to download the original Kies software which will not even recognize the device enough to tell me it's not supported.
Can anyone point me to a way to restore my phone to factory settings? Can I download the stock firmware and flash it with Odin, will this work if I couldn't get the custom firmware to flash in Odin (possibly because of not setting USB debugging?).
EDIT: Note that, following the guide, I did not check which build number my phone is before running Odin, now I have no idea which it is and what stock firmware to download. Is there anyway to figure out which build my phone was on or which stock firmware I need to download?
EDIT: So it looks like my problem is similar to this problem posted on XDA. I followed the link in that thread to this guide to restore the stock firmware. However, it has three different downloads for different builds, I am not sure which I should download or if there is a way to figure it out. Will any of them work? Can I try them one at a time safely until one of them works. I don't want to mess things up any worse than I already have.. I downloaded the MI9 firmware from that page, but this is just a guess... Anyone have any idea?
Any help will be very much appreciated.
vivek318795 said:
recently got a Galaxy Note 3 from Verizon. I wanted to root the device, it was really easy with my old original galaxy so I looked at a few guides which were all using "Root de la Vega" and finally tonight in an attempt to root my device I used the guide at:
phonearena.com/news/How-to-Root-the-Verizon-Samsung-Galaxy-Note-3_id48247
I put the phone into download mode and connected it to Odin with the included Samsung USB 3.0 cable. I selected the root de la vega firmware using the AP button and hit Start to begin flashing. Almost immediately after the write starts it fails and on the phone it says:
Quote:
"Secure check failed: cache"
In the guide it mentions there may be problems using the USB 3.0 cable so I tried it with a USB 2.0 cable with the same results. I tried rebooting the phone to see if it had wiped it. Indeed, it had been wiped and is now going to the screen which says there was a problem updating the firmware and says to use the Software Recovery Assistant to restore the firmware.
I am not sure why this has happened. I feel like I followed the instructions to the letter. After looking at some different guides I am noticing that many have you put the phone into USB debugging mode which the guide I was following doesn't mention. Is this why it has failed. Is this strictly required?
I would like to get this device rooted, but now my number one priority is getting it back into a state where it will be more useful than the paperweight on my desk. I tried downloading Kies 3 which I read can restore the stock firmware on the phone. I was extremely annoyed when I realized that Kies 3 would not recognize my phone at all. It says that the device is not supported by Kies 3 and gives me a link to check support (which just brings me to the Kies download page which clearly states that my phone (Note 3) is supported. I even tried to download the original Kies software which will not even recognize the device enough to tell me it's not supported.
Can anyone point me to a way to restore my phone to factory settings? Can I download the stock firmware and flash it with Odin, will this work if I couldn't get the custom firmware to flash in Odin (possibly because of not setting USB debugging?).
EDIT: Note that, following the guide, I did not check which build number my phone is before running Odin, now I have no idea which it is and what stock firmware to download. Is there anyway to figure out which build my phone was on or which stock firmware I need to download?
EDIT: So it looks like my problem is similar to this problem posted on XDA. I followed the link in that thread to this guide to restore the stock firmware. However, it has three different downloads for different builds, I am not sure which I should download or if there is a way to figure it out. Will any of them work? Can I try them one at a time safely until one of them works. I don't want to mess things up any worse than I already have.. I downloaded the MI9 firmware from that page, but this is just a guess... Anyone have any idea?
Any help will be very much appreciated.
Click to expand...
Click to collapse
I'm running into the exact same issue, did you ever find a solution?
Same issue
I have the same issue. Is there no help? Chainfire? do you have a CF-Root for SM-N900V yet?
Thanks. any help is appreciated.
Hey guys quick question before I download and attempt it, I have an Australian i9506 (Cat 4 LTE) but we don't have an official 5.0.1 firmware yet.
Can I just download the Nordic version from http://www.sammobile.com/firmwares/database/GT-I9506/ and install it, or would it brick my phone/radios not work?
Thanks
juzza87 said:
Hey guys quick question before I download and attempt it, I have an Australian i9506 (Cat 4 LTE) but we don't have an official 5.0.1 firmware yet.
Can I just download the Nordic version from http://www.sammobile.com/firmwares/database/GT-I9506/ and install it, or would it brick my phone/radios not work?
Thanks
Click to expand...
Click to collapse
Hi mate,
Yes you can !! it will not brick it , you may have (or not) problems with the modem as maybe is not the best for your region but you can always flash another...
should not be a problem
BACKUP first , nandroid and your EFS Folder, just in case there is a problem
Just to add to the previous suggestion, use Wanam's EFS Backup Tool rather than Samsung Tool, as it not only backs up the EFS partition but the hidden partitions where the IMEI and the modem are stored.
Strephon Alkhalikoi said:
Just to add to the previous suggestion, use Wanam's EFS Backup Tool rather than Samsung Tool, as it not only backs up the EFS partition but the hidden partitions where the IMEI and the modem are stored.
Click to expand...
Click to collapse
+1 mate!!
It also depends if your phone is carrier locked.
Thanks for the advice guys I'm giving it a try now, will edit as I go. My phone is not carrier locked (Voda AU don't lock them fortunately but they provide the codes on their website for free to unlock anyway).
So I downloaded Odin3 3.09 and the firmware I9506XXUDOA6_I9506NEEDOA6_NEE (this is the link from sammobile).
I'm following the instructions I found on another site but it's basically put the phone into download mode (home, power and volume down), agree to enter download mode, in Odin for AP select the .tar.md5, make sure Auto Reboot and F. Time Reset are ticked but not Re-Partition or anything else and start.
EDIT 1: The phone rebooted into recovery and updated something, now the phone is booting with a new boot animation. (for those referring to this I was on the latest AU Voda FW, then updated to CM12 5.0.2).
EDIT 2: After the usual nerve-wracking amount of time of first boot the boot logo finally went away and the usual "optimizing apps" message has come up and it's started (235 apps whoa the bloat). Waiting for that but at least it's working to a point where I can recover it. I just realised it's 6:10AM now and I FORGOT TO MAKE A BACK UP. I hope this works but worse case scenario there's a 4.4.2 Vodafone firmware I could flash and try my luck with if this doesn't work out.
EDIT 3: I'm not sure if it's part of the setup process but the word "UP" then a short progress bar appeared on the screen, now I've got only a black screen with a status bar (4G icon is there but no clock). I have rebooted from the power menu, let's see what's going on here.
EDIT 4: Cache wipe from stock recovery didn't work, trying factory reset from stock recovery. I note that the first time I set up the phone it was plugged into the computer with ODIN still running, I don't think it could have interfered but I unplugged the phone this time just in case.
EDIT 5: I'm not sure if it was ODIN or needing to do a factory reset but it's working now, I'm running through the set up. WiFi is working 100%.
Final EDIT: Everything is working 100%, tested the camera, proximity sensor, screen rotation, voice calls, mobile data, wifi and it's all 100%.
juzza87 said:
Thanks for the advice guys I'm giving it a try now, will edit as I go. My phone is not carrier locked (Voda AU don't lock them fortunately but they provide the codes on their website for free to unlock anyway).
So I downloaded Odin3 3.09 and the firmware I9506XXUDOA6_I9506NEEDOA6_NEE (this is the link from sammobile).
I'm following the instructions I found on another site but it's basically put the phone into download mode (home, power and volume down), agree to enter download mode, in Odin for AP select the .tar.md5, make sure Auto Reboot and F. Time Reset are ticked but not Re-Partition or anything else and start.
EDIT 1: The phone rebooted into recovery and updated something, now the phone is booting with a new boot animation. (for those referring to this I was on the latest AU Voda FW, then updated to CM12 5.0.2).
EDIT 2: After the usual nerve-wracking amount of time of first boot the boot logo finally went away and the usual "optimizing apps" message has come up and it's started (235 apps whoa the bloat). Waiting for that but at least it's working to a point where I can recover it. I just realised it's 6:10AM now and I FORGOT TO MAKE A BACK UP. I hope this works but worse case scenario there's a 4.4.2 Vodafone firmware I could flash and try my luck with if this doesn't work out.
EDIT 3: I'm not sure if it's part of the setup process but the word "UP" then a short progress bar appeared on the screen, now I've got only a black screen with a status bar (4G icon is there but no clock). I have rebooted from the power menu, let's see what's going on here.
EDIT 4: Cache wipe from stock recovery didn't work, trying factory reset from stock recovery. I note that the first time I set up the phone it was plugged into the computer with ODIN still running, I don't think it could have interfered but I unplugged the phone this time just in case.
Click to expand...
Click to collapse
Hi mate
How is it going?
If trouble , do a factory reset and flash it again....
Thanks mate that did the trick!
juzza87 said:
Thanks mate that did the trick!
Click to expand...
Click to collapse
glad to hear it mate, you did it!!
Thanks for let in us know.
For any other Aussies out there trying this I'm on day two and everything is working perfectly, getting root is super easy too, just use Odin to flash a custom recovery (Solk's CWM from May 2014 works great), boot into the recovery and install UPDATE-SuperSU-v2.45.zip, exit and when it asks if you want to repair root say yes. Reboot, go to the play store, update to the latest SuperSU and all is well.
First of all please forgive me for opening yet another S4 wifi problem after kitkat upgrade, but I have tried everything I could possibly find here, on youtube and other forums. The only thing left to try is flash the modem but I'd rather ask before I brick my phone
I'm not quite sure if this is the same issue every single time or if in my case it is due to my ignorance and errors. I was an iphone/unlock/jailbreak user until last year so please bear with me. Android is new and fun (but scary) territory to me.
Situation, what I did and possible mistakes on my side:
-I'm in Spain but I bought my factory unlocked phone on amazon and it was for the Polish market (GT-I9505 Black, 16 Gb)
-My device was rooted don't even remember how I did it last year so no useful info on that side a part of using odin for windows.
- Until yesterday I was on jellybean, not quite sure if 4.2.2 or 4.3
- Yesterday I upgraded to 4.4.2 via mobile odin and yes I checked the boxes about clearing/deleting cache or whatever it's called.
- Used a stock firmware downloaded from other site (that one starting with "S" and with a great amount of firmwares for samsung devices of several countries)
- I chose a firmware randomly (maybe this was my mistake) because I hade read that the firmware was not that important and people where usimg leaked german firmwares on on phones from elsewhere. But I did choose one that matched the country of my phone (XEO/XX Poland)
- Everything is working fine but without wifi I'm buying new Mb bundles almost every 2 hours and I'll be broke very soon
If you guys think the solution is flashing the modem which file should I use? I see lots of them with different models/codes and I'm completely lost and have read a lot about messing with bootloaders/modems etc bricking devices so I'm freaking scared and ask for your charitative help!
All the info I could gather about my device right now (now I know I should have gathered this info also before attempting to upgrade but it's too late now!
SAMSUNG GALAXY S4 GT-I9505 Black Edition
Manufacturing date: 2013-12-23
BASEBAND Version: I9505XXUEMK8
BOOTLOADER Version:I9505XXUEMK8
PDA Version: I9505XXUGNG8
CSC Version: I9505YXZGNH2
Kernel: 3.4.0-2309103
KOT49H-I9505UGNG8
Android 4.4.2
Product code: GT2I9505ZKAXEO
Original CSC: XEO
Firmsware's CSC: XEO
Active CSC code: XEO
CSC Country: Poland
Any help would be greatly appreciated, I feel so dumb and frustrated right now that any joke or insult would be accepted with humbleness lol
Forgot to add I used the *#0011# command and went to wifi menu. Tried the ping test and it states: passed
status: DISCONNECTED
SSID: Unknown SSID
( In case this info is of any use )
voxel.xyz said:
Forgot to add I used the *#0011# command and went to wifi menu. Tried the ping test and it states: passed
status: DISCONNECTED
SSID: Unknown SSID
( In case this info is of any use )
Click to expand...
Click to collapse
Relax it has solution . The problem becomes coz the baseband and the bootloader are olds (android 4.3).
SAMSUNG GALAXY S4 GT-I9505 Black Edition
BASEBAND Version: I9505XXUEMK8
BOOTLOADER Version:I9505XXUEMK8
PDA Version: I9505XXUGNG8
CSC Version: I9505YXZGNH2
* Quick solution for recover WIFI:
1. Reflash the STOCK I9505XXUGNG8 (XEO) firmware via ODIN.
2. Let the process finish and reboot normally.
3. Dial *#1234# and have to appear this:
AP: I9505XXUGNG8
CP: I9505XXUGNG8
CSC: I9505YXZGNH2
4. Reflash again if not. Good luck
Thank you so much for your helpful reply Joku1981 !!!!! You made my day!!!
Can I do that with Mobile Odin??? My PC broke (Graphics card burnt) and until a couple of months won't be able to buy a new one.
To make sure I understand you: You mean Flash again the same firmware I used to upgrade to 4.4.2 in the first place?
I used this Firmware: I9505XXUGNG8_I9505YXZGNH2_XEO
should I try Flashing that same Stock Firmware again? and if does not work keep reflashing until the baseband and the bootloader get updated?
Why did they not update ? is this common or an error on my side???
I hope it can be done with mobile Odin since I can keep my root status, If I have to do it in Desktop Odin do I have to Re-Root after flashing???
Thank you so much for you kind help!!!!!!
Joku1981 said:
Relax it has solution . The problem becomes coz the baseband and the bootloader are olds (android 4.3).
SAMSUNG GALAXY S4 GT-I9505 Black Edition
BASEBAND Version: I9505XXUEMK8
BOOTLOADER Version:I9505XXUEMK8
PDA Version: I9505XXUGNG8
CSC Version: I9505YXZGNH2
* Quick solution for recover WIFI:
1. Reflash the STOCK I9505XXUGNG8 (XEO) firmware via ODIN.
2. Let the process finish and reboot normally.
3. Dial *#1234# and have to appear this:
AP: I9505XXUGNG8
CP: I9505XXUGNG8
CSC: I9505YXZGNH2
4. Reflash again if not. Good luck
Click to expand...
Click to collapse
SOLVED!!!!!
After nobody answered if I could use again "mobile Odin" to flash once more and try to fix my wifi not working I opened mobile odin and it gave me a warning about my version and having a wrong bootloader as a possibility of soft bricking my phone so I decided to stay away of mobile Odin this time.
I used desktop Odin (at work since my pc broke) and exactly the same firmware file downloaded from sammobile (but re-downloaded it just in case) and had to flash twice, the first time it went through the whole process ok right until the end where it showed the FAIL message.
I didn't know if I should turn off the phone stuck in download mode and with the process bar at 100 % or retry flashing without turning it off. So I decided not to turn it off (afraid it would get soft bricked or something). I closed mobile Odin but left phone On with download mode screen active and opened mobile Odin again got the "added"message and the blue color showing it was properly connected to the phone and started flashing process again....
I started getting red error messages saying the progress bar display was wrong (and it wasn't updating/kept stuck in the previous 100%) but after it finished it was flashed and everything was ok. WIFI WORKED!!!!!!
Now the weird part.....in case this happens /helps someone else:
- My phone DID NOT get wiped. My launcher and my apps stayed intact (I thought flashing even the same firmware always wiped data, I'm I wrong???)
- All my root apps (root explorer, titanium backup, so on and so forth) where there and working fine. One root checker stated I was rooted and another one stated I wasn't but even my launcher (nova) was working just as if I never flashed the phone.
- Since I was unsure of my "root" state and I did not have "supersu" app in my apps drawer I tried installing it via playstore but It always gave an error message (the application could not be installed in the default location)
- I rooted again just in case and the root process finished without errors but still I had no "supersu" app and one root checker said I was rooted and the other I wasn't. Tried installing "supersu" from the playstore but same error and could not get installed.
- I searched here and in other forums for similar problems/solutions but nothing worked until I tried several things that fixed the problem. Not really sure which fixed it so I will write them down in the order I did them:
1. Opened folder mount which I already had installed and it gave me an error and asked me to try the fix which I did.
2. Opened linked2sd which I already had installed also previous to the firmware flash. It gave me an error and asked me which was the partition to use (as when I first installed it) in my case it was ext4. And it seemed to start working as it normally does. No further error when reopening it.
3. Rebooted the phone and tried entering recovery mode to wipe cache etc but It never entered recovery mode. I get the message about going into recovery mode (top left corner small red letters) But right after that it reboots and I get the samsung logo and my home screen.
4. Tried reinstalling supersu again and no success. (By the way before I did all this steps I tried rooting again but got to the same point. No supersu on my apps drawer)
5. Downloaded BusyBox install (opened it but did not use it in any way, maybe something in the installation fixed my problem)
6. Opened mobile Odin just for curiosity sake and it opened fine and asked for downloading of the extra stuff as when I installed it the first time. After that I closed it
7. Rebooted normally (no recovery mode since I'm stuck without it)
8. Tried installing "supersu" and NOW it worked!!!
9. Checked in both root checker apps and both confirm I'm rooted and supersu started asking for granting permissions to apps again as it normally does!
10. Everytime I attempted flash, root, and even after some reboots I took the battery off (since I read in several threads it helped/was mandatory)
Conclusion now my WIFI problem is fixed, my root problem (that appeared doing the reflash for fixing my wifi problem) is also fixed. The only thing I could not fix is not being able to get into recovery mode.
Does anyone know a solution for recovering the ability to get into recovery mode????
Thanks to Joku for lighting me into re flashing once and again until my wifi was fixed!
Okks lets start...
I have this moto g4+ that already came updated (build number MPJ24.139-23.1)
then one fine day i decided to root the device and also installed xposed(thanks to XDA) all went gud..but then i started getting FC for my file manager and some other apps too..soo i thought that this would be due to xposed..
all thanks to my intelligent mind-LOL..
rather flashing uninstaller zip for xposed i decided to flash the stock rom..and this is whr all went wrong..i flashed the old firmware for the device and i lost the IMEI and wifi address..as soon as i figured out i downloaded the correct firmware and flashed the same and my phone was back to normal.
then once again i decided to root my device wherein the procedure was (all must be knowing already) 1st to flash recovery then to flash a certain .zip file (dont remember the name) and after that to flash the supersu.zip but instead i did what..i skipped flashing that "certain zip" and it leaded to bootloop..
Then i went to bootloader and folloed the proper steps again.and just rooted my device no xposed..
but all this led to a major issue that when eva i startup my phone 1st it automatically goes to bootloader then i need to hit start..then my phone starts..
even when i shutdown my device and put it to my default wall charger the phone automatically goes to bootloader and the phone shows usb connected status...
soo i flashed the stck rom once again bt the issue is still present..PLZ provide me relief from this issue..THANKS in advance..
Hi all,
New user here, not much experience rooting or messing with firmware for phones. I was following the guide on how to flash the SM-935U firmware to the verizon model of the Galaxy S7 Edge, and may have bricked my phone. Here's what I did.
Followed the guide to the letter.
Powered off phone, booted to Download mode
Fired up Odin, selected the SM-935U firmware files, and clicked start.
It gave me an Auth error, which research revealed means that I forgot to turn off Reactivation Lock. I figured, "Fine, I'll just disable it. However, I can't get the phone to boot again. Every time I leave download mode, it boots into Android Recovery, where, no matter what I do, it just reboots into Android Recovery. I can't Wipe anything because it can't mount /system - probably due to Reactivation Lock?
I've been research and researching ways around this, and everything I find just points back to flashing it with the stock firmware. But then I read that you can't even do that if Reactivation lock is on, because Odin will still fail with the Auth error. So, I can only get it to boot to recovery mode, and I can't flash it with anything?
I did read somewhere that if I choose to wipe the phone's EFS with Odin that it should override activation lock, but then it clears the phones IMEI, which is an even bigger mess, isn't it?
I feel like I have to be missing something... since it never did the wipe, why is it that I can't get past the recovery mode. Shouldn't I still be able to get into the system somehow?
Does Anyone have any thoughts or suggestions for me? I'd really like to not be stuck with a permanently bricked S7 edge if at all possible....
Solved
Just wanted to post this to help anyone else who might have this issue. Turns out that you can flash the stock firmware, as long as you're flashing at least the same version or newer of the stock firmware as what the phone was running prior to getting stuck in recovery mode. It shows you what version it was running in the recovery mode at the top.
So for me, I googled the exact firmware version that recovery mode said the phone was running, downloaded it, flashed it with ODIN, and it worked just fine. Had to choose to wipe with the recovery mode after I flashed it, but then it booted like normal. - Then I enabled OEM unlocking under the developer menu, and tried flashing the U firmware again with ODIN, and it still failed with the auth error. Huh.
Turns out (maybe I wasn't doing it right or something) that you can't flash older versions of the firmware to the phone. But, as long as OEM unlocking is enabled, you can flash the U (unlocked) version of the current firmware to the phone and it will take just fine. Hint: I was able to determine the "version" number by looking at the last 4-5 characters of the build number... the verizon version I was running for my SM-935V was: VZW-G935VVRU4API3 - So I googled the API3 firmware and found the U (unlocked) version for my carrier (I happen to be using T-Mobile) on this site: https://samsung-firmware.org/model/SM-G935U/ and found the zip file name which was TMB-G935UUEU4API3-20161011161050.zip, googled that, got the rapidgator link, downloaded it, and that flashed just fine to the phone, and now my T-Mobile SIM works perfectly in what was previously the SM-935V, which now identifies as an SM-935U in settings. It's beautiful.
Also, you need the PIT file, but I was able to use the PIT file for the phone model number (again, found at the top of the android recovery menu), which for my phone was: HERO2QLTE_USA_VZW.pit (googled that and got it off androidfilehost) - I was able to use that PIT file for the T-Mobile U version of the firmware and it worked just fine.
Hope this helps someone.