Hello XDA community! My interest in a smart tracker lead me to the Gear Fit. I purchased one brand new a few weeks ago. Since then I downgraded the firmware, updated the firmware, and recovered my own bricked Gear Fit from using the details and files below. I did not create any of the programs or firmware below. I simply sourced the files out when working on my Gear Fit. All credit and respect goes to the original file and program creators, I believe folks at Samsung. Although all of this information isn't new, I could not locate it all together in one easy to follow format with the necessary files. Put it this way, I wish it existed when I was working on mine.
I also wanted to note all of the attached files were scanned with Avast Free Antivirus version 11.1.2245, with virus definition 160225-1, which is the most recent at the the time of this post. Some of the files you will use aren't hosted by me here. Due to this I strongly suggest you scan all the files you download for viruses prior to using them. Lastly, although proven to work for myself, all of the files and details below are meant for guidance only. I am not responsible for anything you do with or to your Gear Fit. Please use and follow at your own risk knowing you are accountable for any and all of the outcome.
With that said, I appreciate the support of XDA so much I always like to give back when I can. Below you'll find guidance for updating firmware from Kies3, how to downgrade or upgrade firmware using ODIN, how to install USB drivers for your computer, and how to unbrick a Gear Fit from a bad firmware flash. Please let me know if anyone has any questions!
Updating Gear Fit USB Driver
Download and install Kies3 from here.
Run Kies3.
Connect the Gear Fit to the computer via charging adapter and micro USB cable.
Click Tools and select Reinstall Device Driver.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Upgrading to the newest firmware via Kies3
Download and install Kies3 from here.
Run Kies3.
Connect the Gear Fit to the computer via charging adapter and micro USB cable.
If it’s giving an error that it’s not being detected please try another USB port. If it’s a desktop computer preferably one in the back that’s attached to the motherboard. If still not being detected please try to unplug it and plug it back in, several times if necessary.
If this still isn’t working you may need to install a Samsung USB Driver for Mobile Phone. Please refer to the Updating Gear Fit USB Driver section in this post.
If a firmware update is available follow the onscreen prompts.
Upgrading or Downgrading from Odin
Download and install Odin3 v3.0.9.5.
Enter download mode on the gear fit by following the instructions in the image below.
Once successfully in download mode run Odin3 v3.0.9.5
Connect the Gear Fit to the computer via charging adapter and micro USB cable. If done correctly it should read that it’s been added in the message window in the lower left corner. The ID:Com port field should also display the Com port.
If not please try to unplug it and plug it back in, several times if necessary.
If it’s giving an error that it’s not being detected please try another USB port. If it’s a desktop computer preferably one in the back that’s built into the motherboard. If this still isn’t working you may need to install a Samsung USB Driver for Mobile Phone. Please refer to the Updating Gear Fit USB Driver section in this post.
If upgrading firmware with 3 .tar.md5 files place the BL in the BL field, AP in the AP field, and CSC in the CSC field. If you are upgrading from a .zip file that contains 1.ex.bin file and 1 .in.bin file only, please place the entire .zip file in the AP field.
Once complete press Start and wait for the message to indicate if it succeeded or if it failed.
Recover Gear Fit after a bad firmware flash (possibly bricked)
If something goes wrong during the Odin flash and you see an image similar to below
you can easily recover the Gear Fit as long as Odin detects it.
Download and install Odin3 v3.0.9.5.
Open Odin3 v3.0.9.5
Connect the Gear Fit with the error into the computer via charging adapter and micro USB cable. If done correctly it should read that it’s been added in the message window in the lower left corner. The ID:Com port field should also display the Com port.
If not please try to unplug it and plug it back in, several times if necessary.
Download the following three files from here and install them in the corresponding slots.
AP: AP_R350XXU0BND8_eng.tar.md5
BL: BL_R350XXU0BND8_user.tar.md5
CSC: CSC_OXA_R350OXA0BND8.tar
Once complete press Start and wait for the message to indicate if it succeeded or if it failed. This has been proven to unbrick a bad firmware flash by me personally.
Hello... you said you updated the gear Fit to latest firmware... it is working also with Open Fit app? Or there is something strange? Thanks!
spino1970 said:
Hello... you said you updated the gear Fit to latest firmware... it is working also with Open Fit app? Or there is something strange? Thanks!
Click to expand...
Click to collapse
Well, out of the box it was updated to the newest firmware, I saw no issues. However I eventually did downgrade to the version the developer of open fit recommended as that's what he is building and it with.
Hi LilLowEK
Many thanks for the FAQ
As my GearFit is all in German (when connected to a mates Sammy Note 4 - it shows in English, but when disconnecting the Bluetooth it goes back to German!! :crying::crying
So I have decided to follow your instructions LilLowEK
I have a problem - How long does it take to flash??
I've had Odin running for 30 + minutes and it is just seems it is not moving at all!
See attachment screen grab please.........
Thanks
Dave
After waiting an age, I disconnected and restarted the GearFit.
Cant see it has done anything at all!!
Still in German - But now cant connect via bluetooth....arhhhhh
Need some advice please
Related
My I9100G was connecting to PC fine, but then for some reason, it stopped connecting to Kies, and even stopped being seen as a mass storage media! WinXP SP3 says problem occurred while installing Samsung mobile MTP Device and that's it! Here is a photo:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have checked threads about this matter on this forum and other fora, and nothing seems to be working:
I have completely uninstalled Kies and its drivers, installed WMP11, updated .NET Framework, then reinstalled Kies, connected using debug mode, then normal mode, made connection troubleshooting and it still didn't work! It's very frustrating!
Thank you.
what rom you got on?
MagnumJoe said:
My I9100G was connecting to PC fine, but then for some reason, it stopped connecting to Kies, and even stopped being seen as a mass storage media! WinXP SP3 says problem occurred while installing Samsung mobile MTP Device and that's it! Here is a photo:
I have checked threads about this matter on this forum and other fora, and nothing seems to be working:
I have completely uninstalled Kies and its drivers, installed WMP11, updated .NET Framework, then reinstalled Kies, connected using debug mode, then normal mode, made connection troubleshooting and it still didn't work! It's very frustrating!
Thank you.
Click to expand...
Click to collapse
The possibility is that the samsung drivers you have in the PC is not updated. Download the updated Samsung Drivers online - you can use google to search for it - including KIES. This should solve your problem
HIT THANKS IF IT HELPS YOU IN ANYWAY!!!
nursespecialist said:
The possibility is that the samsung drivers you have in the PC is not updated. Download the updated Samsung Drivers online - you can use google to search for it - including KIES. This should solve your problem
HIT THANKS IF IT HELPS YOU IN ANYWAY!!!
Click to expand...
Click to collapse
No they are up to date. I updated them with the 4th June update actually.
linkhunter said:
what rom you got on?
Click to expand...
Click to collapse
No: nothing special: didn't flash my mobile yet.
It's:
2.3.6
Baseband: I9100GXXKL4
Kernel Version: 2.6.35.7 [email protected] #2
Build Number: GINGERBREAD.JPLC1
My build number has a problem with doomlord's kit. I don't wanna lose warranty. I am going easy on flashing.
Bump
Bump
Just so everybody would know, even after i restored my phone to factory settings, Samsung Mobile MTP Device still failed, i have completely given up hope.
MagnumJoe said:
Just so everybody would know, even after i restored my phone to factory settings, Samsung Mobile MTP Device still failed, i have completely given up hope.
Click to expand...
Click to collapse
Depending on your skills Microsoft's Media Transfer Protocol Porting Kit could help you debugging the problem. Furthermore the error you are experiencing does not seem specific to Samsung devices. Therefor chances are good you get help if you post your problem in one of the many forums run by Microsoft (if you did not already do so). However you will have to do some research to find the right forum, don't ask me please
fxrb said:
Depending on your skills Microsoft's Media Transfer Protocol Porting Kit could help you debugging the problem. Furthermore the error you are experiencing does not seem specific to Samsung devices. Therefor chances are good you get help if you post your problem in one of the many forums run by Microsoft (if you did not already do so). However you will have to do some research to find the right forum, don't ask me please
Click to expand...
Click to collapse
You mean the problem is in my system?
MagnumJoe said:
You mean the problem is in my system?
Click to expand...
Click to collapse
Yes, looks like.
I do not really understand your question: didn't you try to connect your phone to some other Windows system ? Only then you are able to tell if your problem is related to the phone or the host system or both.
Before debugging with the Media Transfer Protocol Porting Kit you should definitely have done the following things:
use another USB cable
use another USB port (no port on hub)
connect phone to another Windows system
fxrb said:
Yes, looks like.
I do not really understand your question: didn't you try to connect your phone to some other Windows system ? Only then you are able to tell if your problem is related to the phone or the host system or both.
Before debugging with the Media Transfer Protocol Porting Kit you should definitely have done the following things:
use another USB cable
use another USB port (no port on hub)
connect phone to another Windows system
Click to expand...
Click to collapse
I have done everything you can imagine! I even installed the omap4430 drivers! The only thing I didn't try is black magic! And what's making me suspect what you are saying its that this happened after some windows updates and installs and reinstalls. I will reinstall a clean version anyway and change the hard dusk because it's having troubles. So I guess it's that.
It connects fine with HTC sync, but I can't find my phone in "my computer". What am I doing wrong? I'm running Vista 32bit, btw.
now sync can't even find my phone. I tried all the usb ports on my tower, it's a fresh install of Vista that is up to date, tried reinstalling the sync program, installed some mtp drivers I found on the Microsoft site. USB debugging on and off, nothing works! and it's the stock Rom, just with some mods. ATT phone btw. any suggestions? mtp stinks btw...... I wanna flash some roms darn it!
May I suggest something to you? Uninstall all your current drivers and also remove HTC Sync, then try to follow this step-to-step guide : HERE or a more complete one HERE. If you need help or precision I will be glad to assist you.
Well i fallowed your walk through and still no luck. Im sure its not the chord i tried 3 different ones, including the the one that came wit the phone. :crying: Im completely at a loss....
NoobDude said:
Well i fallowed your walk through and still no luck. Im sure its not the chord i tried 3 different ones, including the the one that came wit the phone. :crying: Im completely at a loss....
Click to expand...
Click to collapse
you might have to connect directly from usb like the ports in the back of the pc rather then the ones in the front. also try using a different computer and see if it works or not.
well I just about given up. the issue isn't solely with my computer, as it connects just fine with every other usb device in my house, iphone, gs3, digital camera, etc. so up its an issue primarily with my phone or both my pc and phone. I haven't had a chance to try my phone on another computer yet, can't get mtp working on ubuntu. or maybe it does work, and my phones just messed up. maybe something I did, I need to stop messing with system files :laugh:. BUT I had an epiphany, ADB over WiFi, I found a bunch of apps, they all mention running apps and debugging, but can they be used as a replacement for adb via usb? can I use adb Wi-Fi to push a kernel and or recovery?
Well I made some headway! I FINALLY got my computer to at least recognize my phone. I did this control panel>add hardware and manually installing the drivers that way. SO now in device manager Android phone (sdk drivers) and HTC MTP device, finally show up. I get a code 10 on both those deives, BUT when I scan for hardware the drivers from the phone begin to install, how ever they fail to install. MY brain is beat from this, can some help give me the next little push to finally ending this debacle!?
May I ask if you have administrator privileges on your computer? On Vista this a prerogative, you MUST be an administrator otherwise the installation will fail.
Click on Start -> Control Panel -> Control Panel window opens click on the Uninstall a program (If you are using the Classic View of the Control Panel, then you would double-click on the Programs and Features icon instead.) -> The screen contains a list of the programs installed on your computer, locate everything starting with HTC and uninstall all of them.
Make sure your phone is not plugged in. Reboot your computer.
Download this file containing the Vista 32bit drivers. Put this file on your Desktop.
Plug your phone. Use Device Manager to install the driver.
Click Start, right-click Computer, and then click Properties.
In the Tasks pane, click Device Manager.
If you are prompted for an administrator password or confirmation, type your password or click Continue.
In Device Manager, locate the Android USB or MTP Device for which we want to install the driver.
Right-click the device, and then click Update Driver Software.
Click Browse my computer for driver software, click Let me pick from a list of device drivers on my computer, and then click Have Disk.
In the Install From Disk dialog box, click Browse, locate in the file you just downloaded an androidusb.inf and then click Open.
Follow the steps in the Update Driver Software Device Name dialog box to update the driver.
Reboot your computer.
Lets see the results.
NoobDude i may be beating a dead horse here but Ubuntu 13.04(even in the beta which i use as a daily os) has mtp out of the box maybe try that and install sdk, java , adb fastboot.
if lucky thirteens suggestion doesn't work, I'll try that next. cheers gents!
Lucky thirteens post didn't work at all, when i tried to update the drives I would get an error. Either that the driver wasn't compatible or the the current driver was up to date. I haven't tried updating to Ubuntu 13.4 yet. BUT, I kinda made some headway again. After several reboots and trying different things I get this, what you see in the first picture. SUCCESS!, Oh wai....(refer to second picture)..... When i plug my phone in via a USB (on the back of the computer), i get NOTHING. Sooo. One X+ FOR SALE! :laugh: :crying:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can you try one those drivers?
HTC USB Driver_x32_1.0.5375
Universal Naked Driver 0.72.zip
Intel® Android* USB Driver
Media Transfer Protocol Porting Kit
Also make sure your computer BIOS is up to date, try an online scan for your computer Dell PC Diagnostic
I'll give em a try fist chance I get!
NoobDude said:
I'll give em a try fist chance I get!
Click to expand...
Click to collapse
There is a universal driver from Koushik Dutta (dev of CWM). This worked on my Win8 x64 PC (nothing else would).
At least it shows my device when I type adb devices.
See if that works.
Google for it. I am not sure if I am allowed to attach the file here - hence not attaching. I also have forgotton / not saved the link. It was in his google+ post...
See if that helps
Okk the link was first when I googled .
https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Hi guys.
I need some clear instructions, and software needed to install Windows 7 on my TG01. I do not know most of the stuff I see posted in threads, so I need something even a retard could do.
It already has WM 6.5 on it. And it works well. I need something with a great chance of not bricking it.
anyone help plz
N00b guide
There is certainly not an obvious way to flash a TG01, especially to WP7, so here is a rough guide it's not perfect but hopefully this works for you. Please read and download everything you need before beginning the process.
Step 1: Flash WP7 bootloader
1) Download and install TG Downloader and the USB drivers. Reboot PC.
2) Fully charge your device battery. (Buy a cheap universal battery charger from eBay if necessary.)
3) Switch off your device.
4) Place your TG01 into "Download mode" as follows...
Devices with 0321 ROMs: Hold down Camera + Power buttons on boot.
Otherwise: Remove back cover, battery and SIM card. Carefully remove black sticker where the SIM card was. Get a piece of copper wire and twirl it so that you can easily hold it and touch Pin 1 and Pin 3 at the same time (known as "shorting"), see below image. Replace battery, short the pins with the copper wire and press the Power button.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After either of these your device should display a white LED on the front which means it is in Download mode. If not, switch off and try again. Also if using the PIN method, maybe try holding the Reset button on the back for 10 seconds straight after pressing the Power button.
5) Connect phone to PC. Start TG Downloader with admin rights (right-click shortcut or EXE and choose "Run as administrator".
6) TG Downloader will display an error, click "yes". Click change port to change to Toshiba DL port if necessary. Click "Download mode".
7) Download and extract wp7boot.bin, browse to it in TG Downloader and click "Start Download".
8) Do not disconnect your phone until the process completes, it shouldn't take longer than 5-10mins.
Step 2: Flash WP7 ROM
1) Download and extract these OS files. Install the Acer driver (32 or 64bit) and the ZTEiT Common Downloader.
2) Download a WP7 ROM. I recommend one of the latest 7.8 builds. Once the ROM is downloaded, extract, rename to flash.bin and place in the same directory as NPRG8650.hex and partition.mbn.
3) Fully charge your device battery.
4) Switch off your device.
5) Hold Camera + Power to boot into Download mode, device should display a blue LED.
6) Connect to PC. Start ZTEiT Common Downloader. Select Multi-Download.
7) Browse to folder with downloaded files. Click advanced and for each of the three files (flash.bin, NPRG8650.hex and partition.mbn) browse to them.
8) Click Start to begin flashing process. Do not disconnect device until complete. Could take 15-25mins.
Then your device should boot up into your new WP7 software. Please note camera does not function in any WP7 builds AFAIK and there may be bugs or other limitations.
If this guide works, please go thank these guys: qinwengui, mirolg, arag0n85 and kevinpwhite. Of course thank the ROM creator too :victory:
help please
I never got to put the mobile in download mode, load some files previously in sd?
Thanks, I need it
p.d: I could only sd dowloading but gives error sd
TG01 SOS Failed in Flash wm6.5 to wm 7.0
Hi
Could anyone please help/assist me with this problem i would be great full.
I have a toshiba TG01 phone with windows moblie 6.5
I'm trying to upgrade/flash to load windows mobile 7 (mi7ROM_4_tango_8773_final.zip)
and i am failling to do it..
when i get to short hot wireing the phone to force it to install the contents of the "PRG" folder it comes with a white screen saying filed to download.
what files should be in the "PRG" and what do they do/mean?
My email: [email protected]
Hey, I know it's pretty outdated but does anybody here happen to have the TG Downloader still?
If so, that'd be very helpful if you can re-upload it to somewhere...
My fellows and friends,
One of these days, I received an update from LineageOS and when installing it from OTA ( using TWRP ), the first lines ( about 10 to 15 ) from the istallation sequence activities were all red, showing that something went wrong. Immediately I removed the batery to stop the process and installed the first version of the custom rom, using the TWRP. It worked fine and I received some notifications about the new revisions of the rom. I skipped the one that caused problems and accepetd the download the one on the Nov, 17, 2018 of the rom, and had installed. It appeared to me that everything was ok but, one day I turned the phone off during thje night. The next morning, I tryed to boot the phone without success. It started an infinite loop situation..... So, I tryed to repeat the same procedure to install the very first version of the rom using TWRP at the recovery mode. When I was using the TWRP to perform the advanced wipe, the dalvik cache, data and system could not be wiped. The answer about the problem was shown as : failed to mount /efes ( inavlid argument ).
I got the information that, in cases like that, the stock rom should be installed. I downloaded it from www.stockrom.net and had it istalled with the use of Odin. Unfortunately, the boot loop was there again.
What was worse now was that no TWRP was installed and Odin could not recognize the phone, although I had installed the newest set of drivers from Samsung, applicable to any devices from them.
Please I need your help to see if there is a possible solution to solve this case. Phone Model: GT-i9300 SSN -I9300GSMH - in Brazil
The message I got from the phone: E: failed to mount /efes ( inavlid argument )
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I thank you in advance any help from you guys,
Gilberto Leite
Flashing a stock ROM will always replace TWRP with the stock recovery.
Are you trying to flash the latest stock ROM?
Do you have a backup of the EFS directory? It's an important directory as that is where a lot of information, including the IMEI is stored.
Hi Audit 13, thnaks for replying.
No I don't have the back up for the folder you mentioned. I was trying to install the last stock rom downloaded from www.stockrom.net, which I suppose was the last one. The worst part is that to computer does not recognize the phone since then.... I do not know what to do. I suppose that there is not a way to back up the folder you mentioned. I think that I have to install something from the very begining, as if the phone was to receive the installation of the very first program, as if it was just coming from the factory, totaly clean. Is that so? Am I right? And, how to do it? I tryed to download the stock rom from Samsung, but I think it was difficult and could not have it accomplished.
Thanks a lot and I'm still waiting instructions of how to solve this problem.
You should try using different USB cables and different USB ports to recognize the phone.
I assume you are using Windows since you mentioned Odin. When you connect the phone, do you see any new devices appear under Device Manager?
What is the phone's model # in download mode?
Is the the ROM you used: https://www.stockrom.net/2015/11/stock-rom-original-de-fabrica-samsung_19.html ?
Did you try using Odin 3.07?
Hi Audit13!
Thanks a lot for your help! I've already got hte files you mentioned and am preparing for trying to do the procedure you taught me.
Thanks again and soon, I hope, to be back to confirm whether it succeded.
Bie....
Hi Audit13,
Unfortunately the computer is not recognizing the SGS device.
I was ready to install the sock rom you suggested, had downloaded the Odin 3.07. I use Windows 10 and the latest drivers have been installed. The phone was in the download mode and tryed all available USB port. I've waited some minutes in each USB port for recognition with no success.
I thank you for your help. Is there any other method we could try? If you could please indicate, I thank you again.
Is there a method available using ADB procedures?
Hope there is.
Thanks, anyway for the help.
Hi Audit13
I think that the situation got a little worse. I tryed to do some recovery on the emergency recovery mode, but none of them succeeded. Now, what I get when tryng to get to the recovery mode is an android robot with an open belly with a red triangle coming out of it.... It gets to thedownload mode, but no recognition from the computer. This happened after trying to ionstall the stock rom obtained from the site you mentioned. The only thing that I could do was through the Universal-Android-Diag-Enabler-V2, what made the qualcomm start. Is there a way to make a comand to the phone that could star the USB debbuging? I tryed the various ODIN versions but with no success.
There is another problem - I'm using Windows 10 and the PowerShell uses different command lines not recognized by adb. I tipped devices and the program indicated that there was an mistake.
Is ther an Instructions Booklet for Odin?
What is your opinion? Do you think that there still exists a solution for my phone's case? If so, what to do?
Please, I ask you to help me on solving this problem.
Thanks in advance...
Wanted to share for someone who may have had the same issue as me or is looking to change the device over to the unlocked (non-branded) Firmware.
G715AUCU2ATL4 -TO- G715U1UES7AUB6 (Download states ATL1 but installed it says AUB6)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Been forever since I used Odin and dived into the forums but I was trying to unlock and unbranded the phone and maybe root, I bricked mine in Odin with the wrong Firmware.
Turns out the firmware for the 715(A) AT&T locked version isn't anywhere to be found online except a single unlegit pay site.
-First thing to note is the newest Odin version will not work for the phone at all regardless, only the mod/patched version 3.14.1_3b_PatcheD (Other versions produce "odin repartition failed" error.
https://forum.xda-developers.com/attachments/odin3-v3-13-1_3b_patched-zip.5158499/
Put your phone in download mode:
Remove battery and reinstall (unplugged from PC)
Press the Volume Up, Volume Down, and Power Button(All 3 on right side) at the same time and it will pop up in download mode almost immediately)
Connect to PC
Doesn't matter if you launch Odin before or after connecting.
Install the Samsung Drivers first before using Odin(Use this link or Google it) :
Download Latest Samsung USB Driver v1.7.59 for Galaxy Devices
Download the latest Samsung Android USB drivers for Windows 10 and Smart Switch. USB drivers are required for seamless connection to a PC.
technastic.com
-Secondly this is the only firmware that will work, ill probably fileshare later, who knows how long it will be available:
Select CSC: ATT
Download Galaxy Xcover Pro SM-G715U1 (ATT) G715U1UES6ATL1 in Samfw - Samsung firmware download
Galaxy Xcover Pro SM-G715U1 (ATT - United States) G715U1UES6ATL1 Q(Android 10) samsung firmware download all model, lastest, fast update, completely free and fast speed in Samfw.com ✅
samfw.com
-Forth, it stayed on the Samsung Boot screen after flashing for a long time(Good 3 minutes), unusually long but everything started up fine after that, and every boot since has been normal. (You'll Note the first sign of the change is the Samsung Logo on boot instead of AT&T)
-Forth, this will downgrade you likely ATL4 Version to ATL1/AUB6(Android 10 vs 11) However first thing I did after setup was check for updates and install, it successfully upgraded to Android 11:
11 Working fine:
Thanks for sharing
Thanks for sharing, by the way, It is ODIN3-v3.14.1-3B-PatcheD that works for me.
Download Odin3 Patched (Modded) v3.14.1-3B - Odin download for pc
Share Odin3 Flash Tool: 0 Shares Facebook Twitter LinkedIn Copy Link More
odindownload.club
not this odin3-v3-13-1_3b_patched-zip.5158499/
ronsolus said:
Thanks for sharing, by the way, It is ODIN3-v3.14.1-3B-PatcheD that works for me.
Download Odin3 Patched (Modded) v3.14.1-3B - Odin download for pc
Share Odin3 Flash Tool: 0 Shares Facebook Twitter LinkedIn Copy Link More
odindownload.club
not this odin3-v3-13-1_3b_patched-zip.5158499/
Click to expand...
Click to collapse
By the way, if anyone wants to keep unlocked, please do not update immediately. I found it hard to unlock bootloader after its version upgraded to 9
Please take this as reference: https://forum.xda-developers.com/t/sw-rev-check-fail-bootloader-device-8-binary-6.4035053/
New updates:
Different CSC of the same version (i.e. G715U1) may have different functions. The point most noteworthy is that XAA did not have a dual sim manager. But ZTO does. (XAA is for the AT&T North America version and ZTO is for the Brazil version of G715U1, all can be downloaded from https://samfw.com/firmware/SM-G715U1)
I had tried to use other versions (i.e. G715FN, combination firmware), but all failed.
Glad it did not go brick.
It is also not possible to use firmware of lower Bit/SW REV.
So hold your upgrade to higher Bit/SW REV. if you want to do some changes.
just wanted to say a thank you for this post!
I used a newer version of the SM-G715U1 firmware (2021-09-25) on my G715A...
https://samfw.com/firmware/SM-G715U1/ATT/G715U1UESBBUI1
it probably didn't have any real advantage, other than that I needed fewer updates when I was done...
~R.
I recently got one of this Xcover Pro suckers for very cheap running Verizon software, I tried crossflashing to G715U1UESEBVA4 MXO since I popped my Mexican SIM card and a toast message appeared everytime telling me to call Verizon and the phone suddenly lost signal. With the new software the message doesn´t pop anymore, but I keep loosing network after 5 minutes. Someone has an idea of what could be going on? One thing that does still appear on the Odin menu is the Carrier ID set as VZW, my guess is that is what causing the network issue, but nevertheless I could be wrong, if someone has experience with this device and trying to use foreign SIM cards and is willing to lend some help it would be greatly appreciated!