Related
OK, no matter what method I try I am unable to achieve a successful flash of my phone. I have tried it via odin with many different firmware versions but all seem to fail almost immediately. The only way to resolve this is to use samsung switch and reset phone to stock. The problem is stock firmware is german vodafone full of vodafone bloatware, I want to get rid of it and flash a UK unbranded firmware but no matter what I do I am unable to achieve this. I can see from the forum that there are many people out there with the same flashing problem but with no real responses on how to achieve the goal. There must be people out there that have achieved this task but don't seem to be offering up much help?
ok
sinbrad said:
OK, no matter what method I try I am unable to achieve a successful flash of my phone. I have tried it via odin with many different firmware versions but all seem to fail almost immediately. The only way to resolve this is to use samsung switch and reset phone to stock. The problem is stock firmware is german vodafone full of vodafone bloatware, I want to get rid of it and flash a UK unbranded firmware but no matter what I do I am unable to achieve this. I can see from the forum that there are many people out there with the same flashing problem but with no real responses on how to achieve the goal. There must be people out there that have achieved this task but don't seem to be offering up much help?
Click to expand...
Click to collapse
Is your phone international unlocked out of the box? I dont believe it was, because as far as I've read international unlocked phones come with "unbranded" firmware. The unlocked ones I know can be pretty much flashed with "any" international firmware, which is what you are trying to do.
If you dont know for sure. Odin the stock German Vodaphone. Let the phone boot. Boot back to stock recovery, then factory reset and clear cache.
Then let the phone boot...Download phone info app by vndnguyen (free version is fine)...Open the app, go to CSC Code tab. Then that will tell you the active CSC code and your firmware CSC code...you are looking for the line that says Available CSC Codes. If it only lists German Vodaphone (VD2), then I believe you are stuck til the phone is unlocked.
Anyone, jump in here if I'm mistaken. I am using this as reference as, I've checked my G920F. Mine is unlocked tho and I can flash any firmware from any region with no problem. Hopefully I've answered your question.
I had no luck with the firmwares on the firmware page either.
If you are on OI9 check http://forum.xda-developers.com/galaxy-s6/general/guide-android-6-0-marshmallow-beta-how-t3277533
And try flashing the first stock firmware https://drive.google.com/folderview...sharing&tid=0B40ItdHKfkyQd1hJQXVDU3dDU2c#list (not the android M one!) via ODIN.
Basic process is:
Download the above file, extract, there should be 4 files inside (AP,BL,CP,CSC), simply select each one to go in the relevant box on ODIN, then go into download mode on your phone and click start...
N.B. Be aware that the above firmware contains a PIT file which will reformat and resize the partitions on your phone, so make sure you have a copy of the stock firmware that works before trying the flash (i.e. the one which Smart Switch downloads). You can grab it from your windows %TEMP% directory during the smart switch download (it first downloads a file to TMPxxx, then extracts it into a directory of the same name, its these files you want. They should be the four files beginning with the type of ODIN file you are flashing (AP,BL,CP,CSC). The files get deleted after the firmware has flashed so make sure you watch the process. If things go wrong you can re-flash these files via ODIN
As far as I was led to believe and when I purchased the phone it did state factory unlocked. I was able to put in any sim when I received it and didn't have to go through any aftermarket unlock process?
I have the same problem i have a unlocked G-920F with egyptian CSC and firmware 5.1.1 .when i try to flash BTU 5.1.1 via odin, i have the same problem and only way to recover is via smart switch.BTU firmware is from sammobile
abdussamad said:
I have the same problem i have a unlocked G-920F with egyptian CSC and firmware 5.1.1 .when i try to flash BTU 5.1.1 via odin, i have the same problem and only way to recover is via smart switch.BTU firmware is from sammobile
Click to expand...
Click to collapse
So, seems this is not uncommon?
ok the way to do it is download this file
https://drive.google.com/folderview...sharing&tid=0B40ItdHKfkyQd1hJQXVDU3dDU2c#list
its BTU firmware of 5.1.1
and flash this firmware you'll have 4 files AP,BL,CP,CSC,put it in the respective boxes in odin.I have tested this right now and it works
Press "thanks" if i have helped
Well downloaded the app for CSC info and it states available CSC codes are...
ATL, AVF, CNX, CYV, MOB, MTL, OMN, SIM, SWC, TCL, VD2, VDC, VDF, VDH, VDI, VGR, VIP & VOD
Any ideas?
Ok, tried to get stock firmware when samsung smart switch was downloading and installing but couldn't see where the firmware was being downloaded to? Tried windows temp etc but nothing appeared during download and install?
sinbrad said:
Ok, tried to get stock firmware when samsung smart switch was downloading and installing but couldn't see where the firmware was being downloaded to? Tried windows temp etc but nothing appeared during download and install?
Click to expand...
Click to collapse
Just type in %TEMP% into you windows explorer address bar and it will take you there. arrange by date modified and you will see the size ticking up during the download, before the flash starts it will extract into a folder with the same name, the md5 files can be grabbed from there
No probs here
abdussamad said:
I have the same problem i have a unlocked G-920F with egyptian CSC and firmware 5.1.1 .when i try to flash BTU 5.1.1 via odin, i have the same problem and only way to recover is via smart switch.BTU firmware is from sammobile
Click to expand...
Click to collapse
I flashed BTU firmware on my 920F international unlocked that came with UAE firmware without any problems. Idk
sd_N said:
I flashed BTU firmware on my 920F international unlocked that came with UAE firmware without any problems. Idk
Click to expand...
Click to collapse
Which file and which method?
aaronjp said:
Just type in %TEMP% into you windows explorer address bar and it will take you there. arrange by date modified and you will see the size ticking up during the download, before the flash starts it will extract into a folder with the same name, the md5 files can be grabbed from there
Click to expand...
Click to collapse
Ok, Got it this time, all four files. Will give the method above a go and if it fails at least I've got the stock firmware to fall back on?
Magic, have had great success. Now on the BTU firmware and everything is up and running. Got the stock as well just in case but if this continues to work won't be reinstalling stock. So a big thanks to those who helped
sinbrad said:
Magic, have had great success. Now on the BTU firmware and everything is up and running. Got the stock as well just in case but if this continues to work won't be reinstalling stock. So a big thanks to those who helped
Click to expand...
Click to collapse
Glad you are sorted
Hi, I recently tried to get my phone unlocked. I watched the guy do it, he flashed an older modem and then flashed a UAE firmware.
My original is O2 UK, and I'd like to revert to this firmware as the About Device section shows up with Unted Arab Emirates and the mobile networks section shows LTE rather than 4G.
I have tried flashing the latest revision of the O2 stock rom and odin fails attempting to write sboot.bin with the error message SW Rev. fail (I don't recall the exact numbers after this) appearing on the phone.
I am guessing this is the secure boot loader, which I am aware you can't downgrade, but is there any way of flashing this stock rom since I know it is compatible with the phone?
Try to flash G920FXXU5DQA7 (CSC code:BTU)
chemeleon said:
Hi, I recently tried to get my phone unlocked. I watched the guy do it, he flashed an older modem and then flashed a UAE firmware.
My original is O2 UK, and I'd like to revert to this firmware as the About Device section shows up with Unted Arab Emirates and the mobile networks section shows LTE rather than 4G.
I have tried flashing the latest revision of the O2 stock rom and odin fails attempting to write sboot.bin with the error message SW Rev. fail (I don't recall the exact numbers after this) appearing on the phone.
I am guessing this is the secure boot loader, which I am aware you can't downgrade, but is there any way of flashing this stock rom since I know it is compatible with the phone?
Click to expand...
Click to collapse
You could possibly use smartswitch if you have the serial number of the phone which would download the default firmware that the phone came with if odin fails again
Yes i agree, smartswitch could be your best option.
Thanks for the suggestions. Tried Smart Switch, same error. It appears on the phone as sw rev. check fail.
What exactly is the problem here? Is it that the installed firmware has a newer bootloader than the most recent O2 firmware? In which case is there any way around it?
chemeleon said:
Thanks for the suggestions. Tried Smart Switch, same error. It appears on the phone as sw rev. check fail.
What exactly is the problem here? Is it that the installed firmware has a newer bootloader than the most recent O2 firmware? In which case is there any way around it?
Click to expand...
Click to collapse
Yeah looks like this is a bootloader issue, it won't let you install a firmware which contains an older bootloader, only thing I can is to download the latest non branded UK firmware and see if that flashes.
I'm getting this error too with Device 4 Binary 3 but i didn't find the right firmware yet
I hope in Nougat release
chemeleon said:
Thanks for the suggestions. Tried Smart Switch, same error. It appears on the phone as sw rev. check fail.
What exactly is the problem here? Is it that the installed firmware has a newer bootloader than the most recent O2 firmware? In which case is there any way around it?
Click to expand...
Click to collapse
LollosoSi said:
I'm getting this error too with Device 4 Binary 3 but i didn't find the right firmware yet
I hope in Nougat release
Click to expand...
Click to collapse
As I said before;
Try to flash G920FXXU5DQA7 (CSC code:BTU)
forumber2 said:
As I said before;
Try to flash G920FXXU5DQA7 (CSC code:BTU)
Click to expand...
Click to collapse
Sammobile is under maintenance right now and there are no mirrors reasonably fast... 8 hours for a download.
Anyway update is coming these weeks, I'll wait
LollosoSi said:
Sammobile is under maintenance right now and there are no mirrors reasonably fast... 8 hours for a download.
Anyway update is coming these weeks, I'll wait
Click to expand...
Click to collapse
You could try using samfirm which a windows application which downloads samsung firmwares
LollosoSi said:
Sammobile is under maintenance right now and there are no mirrors reasonably fast... 8 hours for a download.
Anyway update is coming these weeks, I'll wait
Click to expand...
Click to collapse
As @sofir786 said, you can use SamFirm;
https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462
When you open it, set the settings like this;
sofir786 said:
You could try using samfirm which a windows application which downloads samsung firmwares
Click to expand...
Click to collapse
Wow I didn't know, it works thanks
forumber2 said:
As I said before; Try to flash G920FXXU5DQA7 (CSC code:BTU)
Click to expand...
Click to collapse
I'll try flashing when the download finishes
Edit:
WORKING!
I used last(I think) ITV
File names:
AP: AP_G920FXXU5DQA7_CL8821257_QB12271362_REV02_user_low_ship.tar
CSC: CSC_ITV_G920FITV5DQA2_CL10387678_QB12242913_REV02_user_low_ship.tar
BL: BL_G920FXXU5DQA7_CL8821257_QB12271362_REV02_user_low_ship.tar
CP: CP_G920FXXU5DPL3_CL8821257_QB11771442_REV02_user_low_ship.tar
Samsung updated their bootloaders to 4XX in September/October so you cant flash back an older one or downgrade,so the only solution you have is to flash the new one which is 5XX released this year.
Flashed the latest UK revision (not the O2 branded one) and it worked
chemeleon said:
Flashed the latest UK revision (not the O2 branded one) and it worked
Click to expand...
Click to collapse
Told you
Hello Guys, this forum is my last hope. I have a problem with my S7 (DBT Germany), I think after flashing an older stock rom and going back to newest, something happened that my phone doesn't detect any sim cards anymore. If I type *#06# , it only shows the SN Number, no IMEI. WIFI still works without problem, but I can not use my sim card anymore, so it's pretty useless now :crying:
The sim card works on another devices, so it's for sure a problem with my s7, I might have messed up something. What do you think is here the problem and how can I solve it? Any help is much appreciated, I really hope to fix this because my phone is only 2 weeks old.
I currently have the latest Firmware for DBT from updato, (December 14, 2017 for Android 7.0)
IMEI = unknown
SIM Card status: Not avaliable
Have you tried a stock ROM from sammobile.com? Updato and sammobile.com should have the same ROM but maybe there is a difference between the 2?
Did you confirm that the phone is running the latest modem?
audit13 said:
Have you tried a stock ROM from sammobile.com? Updato and sammobile.com should have the same ROM but maybe there is a difference between the 2?
Did you confirm that the phone is running the latest modem?
Click to expand...
Click to collapse
I did not try sammobile because updato and sammobile were the same firmware. Sammobile does have a newer firmware from 28/01 but it says I need to join in order to download.
Is there a way I can fix a damaged/corrupted EFS ? My phone is pretty useless now without sim card detection
Sorry, I know of no way to fix imei issue if a combination of Odin and a stock ROM does not work. You may have to take it to a cell repair shop that can force flash the ROM and EFS using hardware like an octopus box: https://octopusbox.com/eng/features/models
audit13 said:
Sorry, I know of no way to fix imei issue if a combination of Odin and a stock ROM does not work. You may have to take it to a cell repair shop that can force flash the ROM and EFS using hardware like an octopus box: https://octopusbox.com/eng/features/models
Click to expand...
Click to collapse
Hey, flashing a Stock Rom with Odin + Root works for me with no problem, how can I flash my EFS? I do know my S/N and IMEI number..
Do you have an EFS backup? If yes, this may help: https://forum.xda-developers.com/showpost.php?p=72355071&postcount=3
audit13 said:
Do you have an EFS backup? If yes, this may help: https://forum.xda-developers.com/showpost.php?p=72355071&postcount=3
Click to expand...
Click to collapse
I don't have an EFS backup. Any chance without a backup? I do know my S/N and IMEI...
You would need a way to recreate the contents of the folder. Unfortunately, I'm not sure how to create the contents.
Maybe this will help: https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
audit13 said:
You would need a way to recreate the contents of the folder. Unfortunately, I'm not sure how to create the contents.
Maybe this will help: https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
Click to expand...
Click to collapse
Hey, I have finally found the solution and my sim card is working again :victory:
It really was just that the firmware was 1 version older.. I downloaded the latest DBT Firmware from samsung-updates (Build Date: 15/01/2018)
Put Bootloader to BL , AP to AP , CP to CP , CSC (not Home_CSC!) to CSC , flashed it and finally my IMEI etc. is back.
Thank you for taking your time trying to help me
Congratulations on your success
I have the SM-G955F.
I flashed TWRP using the instructions on here and everything worked perfectly fine. I even booted back into the stock OS - however, the Magisk app was not there.
I was going to boot back into TWRP when I got the message "Only official released binaries are allowed to be flashed" and went into a bootloop.
Then I followed the instructions to flash the stock firmware back on to my S8+, but it failed. Can someone point me in the right direction please?
I used Odin3_v3.13.1. I have attached 2 pictures to show the error.
negative_silent said:
I have the SM-G955F.
I flashed TWRP using the instructions on here and everything worked perfectly fine. I even booted back into the stock OS - however, the Magisk app was not there.
I was going to boot back into TWRP when I got the message "Only official released binaries are allowed to be flashed" and went into a bootloop.
Then I followed the instructions to flash the stock firmware back on to my S8+, but it failed. Can someone point me in the right direction please?
I used Odin3_v3.13.1. I have attached 2 pictures to show the error.
Click to expand...
Click to collapse
Sounds like you are trying flash older firmware than what is on your phone. Odin saying you are flashing firmware with bootloader ver 3. Download mode saying you have ver 4 bootloader. You will need latest version of firmware with ver 4 bootloader or higher and flash with Odin.
Bootloader version number is 5th number from right of firmware name.
spawnlives said:
Sounds like you are trying flash older firmware than what is on your phone. Odin saying you are flashing firmware with bootloader ver 3. Download mode saying you have ver 4 bootloader. You will need latest version of firmware with ver 4 bootloader or higher and flash with Odin.
Bootloader version number is 5th number from right of firmware name.
Click to expand...
Click to collapse
Thanks so much for responding. So from my reading and researching, I figured that was the case. However, I could only find the the official firmwares from here:
https://forum.xda-developers.com/galaxy-s8+/development/rom-galaxy-s8-t3749444
Which happens to be v3 bootloaders. Is there any specific v4 bootloader that I should be flashing? I am at my wits end here. I followed all the instructions perfectly...
I read that everything works fine until reboot then you get the "Only official released binaries are allowed to be flashed"
https://forum.xda-developers.com/galaxy-s8/how-to/guide-how-to-root-galaxy-s8-crgh-rom-t3846009
Any help would be greatly appreciated.
negative_silent said:
Thanks so much for responding. So from my reading and researching, I figured that was the case. However, I could only find the the official firmwares from here:
https://forum.xda-developers.com/galaxy-s8+/development/rom-galaxy-s8-t3749444
Which happens to be v3 bootloaders. Is there any specific v4 bootloader that I should be flashing? I am at my wits end here. I followed all the instructions perfectly...
I read that everything works fine until reboot then you get the "Only official released binaries are allowed to be flashed"
https://forum.xda-developers.com/galaxy-s8/how-to/guide-how-to-root-galaxy-s8-crgh-rom-t3846009
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Firmware can be download from sammobil or updato and flashed with odin
https://www.sammobile.com/firmwares/
https://updato.com/firmware-archive-select-model
Select phone model then search for firmware for your region ( and carrier ).
Only official binary error is probably due to your rmm state being in prernormal state which means if you unlock your bootloader ( oem ) and reboot it will relock bootloader causing this message.
Reflash firmware to get phone running again.
Have a read through this guide for more info about rmm state
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
spawnlives said:
Firmware can be download from sammobil or updato and flashed with odin
https://www.sammobile.com/firmwares/
https://updato.com/firmware-archive-select-model
Select phone model then search for firmware for your region ( and carrier ).
Only official binary error is probably due to your rmm state being in prernormal state which means if you unlock your bootloader ( oem ) and reboot it will relock bootloader causing this message.
Reflash firmware to get phone running again.
Have a read through this guide for more info about rmm state
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
Click to expand...
Click to collapse
Thank you for the links. I can't tell you how much I appreciate you helping me out.
I bought the phone from eBay, it's a SM-G955F - as for the region and carrier, I live in United States using AT&T. My primary reason getting the international version is to install a custom ROM on it. Is there a specific firmware for my region (U.S.) and carrier (AT&T) that I should flash? I don't see it US listed.
Also, using the guide I mentioned above, I did flash the RMM bypass, however, it was not the version 2, found in the guide you posted. Is that where I messed up?
negative_silent said:
Thank you for the links. I can't tell you how much I appreciate you helping me out.
I bought the phone from eBay, it's a SM-G955F - as for the region and carrier, I live in United States using AT&T. My primary reason getting the international version is to install a custom ROM on it. Is there a specific firmware for my region (U.S.) and carrier (AT&T) that I should flash? I don't see it US listed.
Also, using the guide I mentioned above, I did flash the RMM bypass, however, it was not the version 2, found in the guide you posted. Is that where I messed up?
Click to expand...
Click to collapse
I don't live in the US but there should be filters on the websites to filter by region. I normally use updato and firmware for your region shows up under U.S.A it will show you all your carrier's like at&t, Sprint, t-mobile and non carrier firmware.
As for the rmm zip version 2 may have been better it is more up to date and is smaller in size. Both should do the same job though.
spawnlives said:
I don't live in the US but there should be filters on the websites to filter by region. I normally use updato and firmware for your region shows up under U.S.A it will show you all your carrier's like at&t, Sprint, t-mobile and non carrier firmware.
As for the rmm zip version 2 may have been better it is more up to date and is smaller in size. Both should do the same job though.
Click to expand...
Click to collapse
I looked on updato and sammobile, both do not have USA region. Can I flash firmware from another region and still get it to work on my carrier?
For example, can I flash U.K. (Vodafone) since its on ver 4 firmware and uses GSM - regardless of region and carrier?
negative_silent said:
I looked on updato and sammobile, both do not have USA region. Can I flash firmware from another region and still get it to work on my carrier?
For example, can I flash U.K. (Vodafone) since its on ver 4 firmware and uses GSM - regardless of region and carrier?
Click to expand...
Click to collapse
Just doubled checked saw you have the f series while updato has u1 version firmware that I can see.
You can flash firmware from the UK if you want but can't say for certain you will have full network capabilities due to the difference in region and carriers ( network capabilities ). I would try and find an unbranded version ( non carrier branded) firmware first if not then something like Vodafone .
There is a simple reason for this. If you came from TWRP as "reboot to download", this creates the problem. Turn off the phone. Go to download mode with Vol_Down+Bixby+Power and then press Vol_Up button. When I enter download mode like this, it flashes without any problems.
(WIP, files are currently processing and uploading)
For those who aren't already aware, F711U is the model number of all of the US carrier versions of the Z Flip3. The F711U1 is the model number of the same device, but sold by Samsung SIM unlocked and with no carrier bloatware. Firmware is 100% interchangeable among these models: any U or U1 firmware version can be flashed to any U or U1 device at any time, assuming that you're not trying to downgrade the bootloader. A "U to U" or "U1 to U1" flash does not require a factory reset, but changing from one firmware to the other will require one. Also, U firmware is identical for the 4 base files (AP, BL, CP, CSC) for each individual build, no matter which carrier it comes from. So if you download 2 different carrier versions of the exact same build, the 4 base files will be identical. Where the firmware differs is in the USERDATA file - that's where the carrier bloatware and customizations reside.
Manual Odin flashing is designed for those who:
- want to manually update to a newer version of U firmware on their U device, either because they don't want to wait for their carrier's OTA or because OTAs aren't working on their device, or a different carrier got a new feature/patch before they did
- want to flash U1 firmware to their U device
- want to convert from U1 firmware to carrier U firmware
- want to convert from one carrier's U firmware (with all apps and bloatware) to a different carrier's U firmware (with all apps and bloatware)
For those who aren't already aware, anyone can now download firmware for almost any Samsung device any time that they want, via the various firmware download tools posted here on XDA like SamFirm or Frija. There are threads and info about them here on XDA so I won't waste time explaining - do a search if you're not already familiar with these tools. But they only provide whatever the latest/newest/current version is - nothing older. I have access to an internal Samsung firmware download tool that usually gets new versions before they hit the public firmware download tools, so that's where my files come from.
This is not a "beginner's guide to Odin flashing" -type post/thread, so I won't list basic, step-by-step flashing instructions. My threads are geared towards those who already know what they're doing. If you're new to manually flashing Samsung firmware (or haven't done it in a long time), I recommend you consult one of those "beginner's" guides- there are tons of them here on XDA.
Happy flashing!
U firmware: https://www.androidfilehost.com/?w=files&flid=327752
U1 firmware: https://www.androidfilehost.com/?w=files&flid=327753
Notes:
- DON'T QUOTE THE OP WHEN YOU REPLY, kthx
- I have lots of threads just like this one for other Samsung flagships, if it interests you. For those who have already made use of my previous threads for a different device and are upgrading, welcome back
- My zips are compressed extra small for space and bandwidth savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc
- it's quite time consuming to download the files, zip them up, and upload them to AFH. And, I do threads like this for every single flagship model, so I won't be uploading every single version. The only full builds that I upload are ones where I get access to a new bootloader and/or Android version early, before they hit the firmware download tools.
- My naming method for folders on AFH is: build - bootloader - Android version
So "SAT - 1 - 9.0" means the full build number ends in SAT, it's bootloader version 1, and it's Android 9.0. When bootloader and Android versions increment, the first build to have those changes will have its folder notated appropriately.
- HOME CSC file keeps data intact; using the other CSC will wipe data. Flashing USERDATA will also wipe data.
- Since AT&T doesn't allow their firmware to be publicly available (for any of their devices), I'll try to always upload at least one USERDATA per bootloader increment for AT&T (and Cricket, if they get this model). I'll also upload any full builds if AT&T is the only carrier to get that specific build, because you won't be able to find the files anywhere else.
- For identifying USERDATAS, and to know what region/CSC to use in the firmware download tools if you're downloading yourself:
AIO = Cricket (not available via firmware download tools)
ATT = AT&T (not available via firmware download tools)
BST = Boost Mobile
CCT = Xfinity Mobile (Comcast)
CHA = Spectrum Mobile (Charter)
DSH = Dish Network
TMB = T-Mobile
TMK = Metro PCS
USC = US Cellular
VZW = Verizon (available via firmware download tools, but Manual Entry is required - Auto will not work)
XAA = U1 firmware
Flashed a physical T-Mobile F711U to a F711U1 XAA firmware using Odin(Can't stand the bright pink boot up animations).
Flash worked perfectly. But, when I tried to test doing an update from Google settings it failed every time with "Registration Failed". I flashed the device back to the T-Mobile F711U firmware and was able to update without issue.
Not sure if you ran into this issue, but it's worth noting you might not be able to update the phone if the carriers are checking the Firmware.
Edit: Also forgot to mention, had to use the patched Odin due to the Firmware Model mismatch. Phone does work properly though.
nwb_sam said:
Flashed a physical T-Mobile F711U to a F711U1 XAA firmware using Odin(Can't stand the bright pink boot up animations).
Flash worked perfectly. But, when I tried to test doing an update from Google settings it failed every time with "Registration Failed". I flashed the device back to the T-Mobile F711U firmware and was able to update without issue.
Not sure if you ran into this issue, but it's worth noting you might not be able to update the phone if the carriers are checking the Firmware.
Edit: Also forgot to mention, had to use the patched Odin due to the Firmware Model mismatch. Phone does work properly though.
Click to expand...
Click to collapse
What do you mean by "doing an update from Google settings"?
What type of update? What "Google settings" exactly?
iBowToAndroid said:
What do you mean by "doing an update from Google settings"?
What type of update? What "Google settings" exactly?
Click to expand...
Click to collapse
From "Settings" App > "Software Update" > "Download and Install" and pressing the "Download and Installing.
I get "Connecting to server" and then immediately "Registration Failed" I've attempted over Wi-Fi and with that option toggled off.
This could also be the phone is new and T-Mobile doesn't have the F711U1 XAA firmware at their carrier level, but the registration failed annoys me. On F711U (official T-Mobile firmware) I simply get a notification that the device is up to date.
nwb_sam said:
From "Settings" App > "Software Update" > "Download and Install" and pressing the "Download and Installing.
I get "Connecting to server" and then immediately "Registration Failed" I've attempted over Wi-Fi and with that option toggled off.
This could also be the phone is new and T-Mobile doesn't have the F711U1 XAA firmware at their carrier level, but the registration failed annoys me. On F711U (official T-Mobile firmware) I simply get a notification that the device is up to date.
Click to expand...
Click to collapse
Which F711U1 version did you flash?
iBowToAndroid said:
Which F711U1 version did you flash?
Click to expand...
Click to collapse
I flashed my phone using the F711U1OYM1AUG7 (F711U1 XAA) firmware from sammobile.
I flashed it back to the T-Mobile firmware, (F711UOYN1AUGB (F711U TMB) and the issue went away.
I did flash it again to the XAA to confirm the problem this evening. Never retained data during the process. Factory reset and removed my account information (Google and Samsung) before updating the firmware each time.
I've done this on a few phones in the past. If I'm making a blunder in the process causing this then I'm truly sorry for wasting anyone's time.
Edit: Typo
nwb_sam said:
I flashed my phone using the F711U1OYM1AUG7 (F711U1 XAA) firmware from sammobile.
I flashed it back to the T-Mobile firmware, (F711UOYN1AUGB (F711U TMB) and the issue went away.
I did flash it again to the XAA to confirm the problem this evening. Never retained data during the process. Factory reset and removed my account information (Google and Samsung) before updating the firmware each time.
I've done this on a few phones in the past. If I'm making a blunder in the process causing this then I'm truly sorry for wasting anyone's time.
Edit: Typo
Click to expand...
Click to collapse
Well UG7 is the latest that's available. So yes, I would expect you to get an error.
Once an update is available, if the phone is still giving the same error, then you can worry about it
Hello, well from my understanding Xfinity is bootloader unlockable after 60days and fully played for. I am wondering if anyone is planning on making a thread for Xfinity specifically. Or want too work with me on One. Sorry too spam or thread. But if u are familiar with how rom building, and flashing was with any other recent samsung model/Xfinity/bootloader unlock. It would be highly appreciated too know your experience.
jokono421 said:
Hello, well from my understanding Xfinity is bootloader unlockable
Click to expand...
Click to collapse
Incorrect. No US models of any Samsung device have been user-unlockable for years now, dating back to the S7
iBowToAndroid said:
Incorrect. No US models of any Samsung device have been user-unlockable for years now, dating back to the S7
Click to expand...
Click to collapse
I think network unlock got mixed up with bootloader unlock. You can unlock the phones for use with another carrier after X days and completed payment.
twistedumbrella said:
I think network unlock got mixed up with bootloader unlock. You can unlock the phones for use with another carrier after X days and completed payment.
Click to expand...
Click to collapse
Probably so
Can someone locate the thom browne fimware please?
blkghost22 said:
Can someone locate the thom browne fimware please?
Click to expand...
Click to collapse
Well normally I would say that you can get it yourself from the various firmware download tools like SamFirm or Frija. But it looks like Samsung changed something over the weekend, as the current versions of the tools are failing to pull any firmware
So I can grab it for you
iBowToAndroid said:
Well normally I would say that you can get it yourself from the various firmware download tools like SamFirm or Frija. But it looks like Samsung changed something over the weekend, as the current versions of the tools are failing to pull any firmware
So I can grab it for you
Click to expand...
Click to collapse
Thank you and always the best.
blkghost22 said:
Thank you and always the best.
Click to expand...
Click to collapse
Added, UGC build
iBowToAndroid said:
Added, UGC build
Click to expand...
Click to collapse
Guess its taking time to upload? Dont see the files just yet..
Edit:
Nvm i see the files now... again thank you so much
I know long time ago it didnt work but just wanted to throw it out there... if i flash the u1 or thom browne am i able to flash the att userdata to get the advance msging and video calls?
blkghost22 said:
I know long time ago it didnt work but just wanted to throw it out there... if i flash the u1 or thom browne am i able to flash the att userdata to get the advance msging and video calls?
Click to expand...
Click to collapse
1. Thom Browne *is* U1 firmware
2. USERDATA belongs to U firmware, not U1. So I have absolutely no idea. You'll have to try it and see what happens
Have successfully flashed F711U1 to F711W. Everything working fine. Used Odin 3.14, CSC_OMC_OYV, and working on Telus with all available features working.
Please note that AFTER the flash, you will be prompted to reset the device to stock. Reason being is that it needs to install the appropriate CSC linked to the inserted SIM card.
Can anyone confirm if cross flashing different build firmwares that it will unlock the unlock bootloader option?
Currently on carrier firmware for TMobile and I'm wondering if this is possible or if the u1 firmware has the unlock bootloader option available