Hey guys, I have the g930FD version and stuck with the June update after I have rooted. I have reflashed the orignal rom still to no effect. I have used ODIN, Kies and Smart switch for restoring to the original firmware. I have restored to factory defaults and still stuck in the old update. Can you help me?
As per the usual, I take no responsibility for anyone who reads this and does it wrong and bricks their phone. This is just what works for me.
At this point, you can probably download any pushed updates, but they won't install. What you can do is get the latest firmware for your phone at sammobile and install it via Odin. A useful walkthrough (albeit an older one) can be found at http://forums.androidcentral.com/am...ide-samsung-how-flash-stock-rom-via-odin.html . Here's one that might be more recent, so read both: http://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin .
You will need to make sure you get the proper firmware for your particular country, so it will work with your provider. As an example, I have a 930f which originally had the TTT firmware (Trinidad/Tobago) so I would need to download the TTT firmware.* You should keep in mind that when you flash the .TAR.MD5 file with Odin, you will completely over-write your phone, so back up EVERYTHING. I even remove my SD card just in case.
*As I live in the USA, I can't flash the .TAR.MD5 file as it comes to me. I have to unzip it with 7zip, and then flash only some of the files. If you also have a European phone with an unlocked bootloader, you will need to haunt the Questions and Guides for advice on which files you should flash. This is because one of the files has to do with the radio/modem/setttings of that country, and if it doesn't match your country, your phone won't work with your provider anymore. The CSC maybe? Can anyone remind me?
For all of you out there who happened to get stuck on 955u firmware containing bootloader 2 installed on the 955u1, there is hope!
I have successfully gotten back to 955u1 firmware and running stock OREO. (and have service again for those who are on non-mainstream carriers {Verizon, Sprint, T-Mobile, AT&T})
You will need (links to be added soon) (My Carrier in BL says XAA and these linked are the XAA firmwares):
USB 2.0 PORT
PRINCECOMSEY ODIN 3.12... link
regular ODIN 3.13.1 (what i used) link
G955U1UES2AQL1_G955U1OYM2AQL1 Firmware link
G955U1UEU2CRB9_G955U1OYM2CRB9 Firmware link
Official Samsung Cable that came with phone (preferably)
Windows OS
A Galaxy S8+ 955u1 Phone (only tried with this)
For some reason flashing just the CRB9 firmware would not work, I had to use the AQL1 and then to the CRB9
Instructions:
1. Extract both firmware files/zips (Put in 2 seperate folders so no mixups)
2. Reboot your phone to download mode (Power off then -- Power + Bixby + Volume Down at same time)
3. Open up princecomsey ODIN and then connect your phone to USB 2.0 Port
4. Add in the AQL1 Files - (BL, AP, CP, CSC) -- (I personally first did the AP, CP, and CSC then had it reboot then i restarted and flashed the BL by itself then rebooted) and press start. (I unchecked everything but reboot and f.reset time)
5. Unplug and Wait for it to turn on to the setup screen, then finish the setup (to verify that it runs and the model number is showing the correct #). If you open up settings it will be all jumbled up and weird, but dont worry. If you dont have service yet - dont worry.
6. Now after the phone is all setup (or if you decided to skip), unplug and power off the phone then boot into download mode again.
7. Now open up Regular odin and reconnect the phone
8. Now put in the CRB9 files (BL, AP, CP, CSC) (I put all in this time and i used the Home_CSC this time but you can use csc normal but no guarantee that would work with getting service again as i didnt try it) and press start and wait til it finishes and reboots (same goes here reboot, f stop time. but also check nand erase all -- to fix storage issue)
9. ENJOY!!!
NewDev4IOS said:
For all of you out there who happened to get stuck on 955u firmware containing bootloader 2 installed on the 955u1, there is hope!
I have successfully gotten back to 955u1 firmware and running stock OREO. (and have service again for those who are on non-mainstream carriers {Verizon, Sprint, T-Mobile, AT&T})
You will need (links to be added soon) (My Carrier in BL says XAA and these linked are the XAA firmwares):
USB 2.0 PORT
PRINCECOMSEY ODIN 3.12... link
regular ODIN 3.13.1 (what i used) link
G955U1UES2AQL1_G955U1OYM2AQL1 Firmware (link in an hour or 2)
G955U1UEU2CRB9_G955U1OYM2CRB9 Firmware (link in an hour or 2)
Official Samsung Cable that came with phone (preferably)
Windows OS
A Galaxy S8+ 955u1 Phone (only tried with this)
For some reason flashing just the CRB9 firmware would not work, I had to use the AQL1 and then to the CRB9
Instructions:
1. Extract both firmware files/zips (Put in 2 seperate folders so no mixups)
2. Reboot your phone to download mode (Power off then -- Power + Bixby + Volume Down at same time)
3. Open up princecomsey ODIN and then connect your phone to USB 2.0 Port
4. Add in the AQL1 Files - (BL, AP, CP, CSC) -- (I personally first did the AP, CP, and CSC then had it reboot then i restarted and flashed the BL by itself then rebooted) and press start. (I unchecked everything but reboot and f.reset time)
5. Unplug and Wait for it to turn on to the setup screen, then finish the setup. If you open up settings it will be all jumbled up and weird, but dont worry. If you dont have service yet - dont worry.
6. Now after the phone is all setup (or if you decided to skip), unplug and power off the phone then boot into download mode again.
7. Now open up Regular odin and reconnect the phone
8. Now put in the CRB9 files (BL, AP, CP, CSC) (I put all in this time and i used the Home_CSC this time but you can use csc normal but no guarantee that would work with getting service again as i didnt try it) and press start and wait til it finishes and reboots
9. ENJOY!!!
Click to expand...
Click to collapse
Did you volte work again after you went back to stock u1 firmware. Also is the a quicker way to download AQL1 because sammobile is a joke thanks
Sent from my [device_name] using XDA-Developers Legacy app
bonebeatz1234 said:
Did you volte work again after you went back to stock u1 firmware. Also is the a quicker way to download AQL1 because sammobile is a joke thanks
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Im going to be uploading the firmware and yes the VoLTE is working.
Also When flashing the CRB9 after the ALQ1 -- A repartition or nand erase all should be done as when i looked at my storage last night it was only 16GB but since im back to u1 firmware it shouldnt be hard to fix for me. i will edit with main post after i do it to my phone to ensure which one works.
uploaded
bonebeatz1234 said:
Did you volte work again after you went back to stock u1 firmware. Also is the a quicker way to download AQL1 because sammobile is a joke thanks
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
files are uploaded now -- finally (took a few tries)
NewDev4IOS said:
For all of you out there who happened to get stuck on 955u firmware containing bootloader 2 installed on the 955u1, there is hope!
I have successfully gotten back to 955u1 firmware and running stock OREO. (and have service again for those who are on non-mainstream carriers {Verizon, Sprint, T-Mobile, AT&T})
You will need (links to be added soon) (My Carrier in BL says XAA and these linked are the XAA firmwares):
USB 2.0 PORT
PRINCECOMSEY ODIN 3.12... link
regular ODIN 3.13.1 (what i used) link
G955U1UES2AQL1_G955U1OYM2AQL1 Firmware link
G955U1UEU2CRB9_G955U1OYM2CRB9 Firmware link
Official Samsung Cable that came with phone (preferably)
Windows OS
A Galaxy S8+ 955u1 Phone (only tried with this)
For some reason flashing just the CRB9 firmware would not work, I had to use the AQL1 and then to the CRB9
Instructions:
1. Extract both firmware files/zips (Put in 2 seperate folders so no mixups)
2. Reboot your phone to download mode (Power off then -- Power + Bixby + Volume Down at same time)
3. Open up princecomsey ODIN and then connect your phone to USB 2.0 Port
4. Add in the AQL1 Files - (BL, AP, CP, CSC) -- (I personally first did the AP, CP, and CSC then had it reboot then i restarted and flashed the BL by itself then rebooted) and press start. (I unchecked everything but reboot and f.reset time)
5. Unplug and Wait for it to turn on to the setup screen, then finish the setup (to verify that it runs and the model number is showing the correct #). If you open up settings it will be all jumbled up and weird, but dont worry. If you dont have service yet - dont worry.
6. Now after the phone is all setup (or if you decided to skip), unplug and power off the phone then boot into download mode again.
7. Now open up Regular odin and reconnect the phone
8. Now put in the CRB9 files (BL, AP, CP, CSC) (I put all in this time and i used the Home_CSC this time but you can use csc normal but no guarantee that would work with getting service again as i didnt try it) and press start and wait til it finishes and reboots (same goes here reboot, f stop time. but also check nand erase all -- to fix storage issue)
9. ENJOY!!!
Click to expand...
Click to collapse
Thank you so much! it worked coming from the g955u on verizon.
Was on Verizon 955U CRC5. Did the AQL1 and didn't have any jumbled or weird settings and storage is fine. Regular Odin failed trying to do CRB9. Downloaded the Software Update/OTA CRB9 update and all is good. On build R16NW.G955U1UEU2CRB9 with March 1 Security patch.
Sorry for bugging, newb here. Will this work on my Sprint Galaxy S8 Plus smg955usqs2bql1? And if so if you could spare a few and and help me. I believe I need this right to get root on my device?
sacking76 said:
Sorry for bugging, newb here. Will this work on my Sprint Galaxy S8 Plus smg955usqs2bql1? And if so if you could spare a few and and help me. I believe I need this right to get root on my device?
Click to expand...
Click to collapse
What if you flashed the sm-g955u1 version on to a sprint sm-g955u phone? would there be any way to power that back on, asking for a friend I believe thats what he done. Now his phone will not turn on.
kingjay2013 said:
What if you flashed the sm-g955u1 version on to a sprint sm-g955u phone? would there be any way to power that back on, asking for a friend I believe thats what he done. Now his phone will not turn on.
Click to expand...
Click to collapse
Honestly I do not know all I have is a 955u1 and am unable to test for other models as I don’t have any others, and now since bootloader version 3 is out for the 955u1 it is the end of carrier switching unless there is a workaround found in the near future.
This should still work as long as you keep the device on the same bootloader v2 and not Flash any v3 bootloader Firmware as that will definitely brick the device from what I’ve heard of v3 bootloaders
Sorry for any late replies been really busy lately
kingjay2013 said:
What if you flashed the sm-g955u1 version on to a sprint sm-g955u phone? would there be any way to power that back on, asking for a friend I believe thats what he done. Now his phone will not turn on.
Click to expand...
Click to collapse
Honestly I do not know all I have is a 955u1 and am unable to test for other models as I don’t have any others, and now since bootloader version 3 is out for the 955u1 it is the end of carrier switching unless there is a workaround found in the near future.
This should still work as long as you keep the device on the same bootloader v2 and not Flash any v3 bootloader Firmware as that will definitely brick the device from what I’ve heard of v3 bootloaders
I’m guessing your friend must have flashed firmware running bootloader v3 on it
(To tell what BL ver. The firmware contains look at the 5th character from the end and it is should be a number like xxx1xxxx or xxx2xxxx etc...) and if it was a 3 then that would be why as that firmware will brick the phone if it’s flashed on a different model (until there is a workaround)
Sorry for any late replies been really busy lately
sacking76 said:
Sorry for bugging, newb here. Will this work on my Sprint Galaxy S8 Plus smg955usqs2bql1? And if so if you could spare a few and and help me. I believe I need this right to get root on my device?
Click to expand...
Click to collapse
I haven’t seen any root for 955u/1 models for Oreo yet the only root I’ve seen on the s8 running Oreo is the carrier versions and the international models
NewDev4IOS said:
Honestly I do not know all I have is a 955u1 and am unable to test for other models as I don’t have any others, and now since bootloader version 3 is out for the 955u1 it is the end of carrier switching unless there is a workaround found in the near future.
This should still work as long as you keep the device on the same bootloader v2 and not Flash any v3 bootloader Firmware as that will definitely brick the device from what I’ve heard of v3 bootloaders
I’m guessing your friend must have flashed firmware running bootloader v3 on it
(To tell what BL ver. The firmware contains look at the 5th character from the end and it is should be a number like xxx1xxxx or xxx2xxxx etc...) and if it was a 3 then that would be why as that firmware will brick the phone if it’s flashed on a different model (until there is a workaround)
Sorry for any late replies been really busy lately
Click to expand...
Click to collapse
I greatly appreciate your response, is it any possible way to fix it? right now it won't power up, not even in bootload mode, nor recovery.
Hello guys,
so some months ago my aunt approached me asking me to "repair" her phone which didn't boot anymore after she installled an OTA update.
Now she is been greeted by the Samsung Logo and the message "Custom binary locked by frp lock" and that in an ongoing loop.
What I tried:
> flashing several stock roms (Android 6, Android 7 oldest version and newest versions)
> flashing roms from other countries in EU (UK, Austria, CH)
> flashing with ODIN and KIES (Kies didn't really work tho)
but all of it didn't work.
I fear that I might didn't check if "Re-Partition" was checked in Odion because after several tries and downloading thos Stock Roms with 20 Kb/s I was kinda frustrated when it didn't work..
currently the phone is still boot-looping with the same message as before.
It doesn't matter if I loose every data, as my aunt has a new phone by now!
If the phone has be re-partitioned by Odin is there anyway to fix it or better what are the signs for a Re-Partition?
Thank you in advance!
Paachan said:
Hello guys,
so some months ago my aunt approached me asking me to "repair" her phone which didn't boot anymore after she installled an OTA update.
Now she is been greeted by the Samsung Logo and the message "Custom binary locked by frp lock" and that in an ongoing loop.
What I tried:
> flashing several stock roms (Android 6, Android 7 oldest version and newest versions)
> flashing roms from other countries in EU (UK, Austria, CH)
> flashing with ODIN and KIES (Kies didn't really work tho)
but all of it didn't work.
I fear that I might didn't check if "Re-Partition" was checked in Odion because after several tries and downloading thos Stock Roms with 20 Kb/s I was kinda frustrated when it didn't work..
currently the phone is still boot-looping with the same message as before.
It doesn't matter if I loose every data, as my aunt has a new phone by now!
If the phone has be re-partitioned by Odin is there anyway to fix it or better what are the signs for a Re-Partition?
Thank you in advance!
Click to expand...
Click to collapse
I am a noob in this, but logicaly reasoning i would say you bricked it bad by flashing away with all kind of csc and firmware down and upgrades.
Your aunt will not be happy.
Jopponius said:
I am a noob in this, but logicaly reasoning i would say you bricked it bad by flashing away with all kind of csc and firmware down and upgrades.
Your aunt will not be happy.
Click to expand...
Click to collapse
Well this reply isn't really that helpful...
1st she doesn't care anymore because as mentioned she already has a new phone and said I can just keep it or throw it away.
2nd even if it's bricked there are ways to get it back to working, I soft bricked my old HTC M8 once and restored it.
3rd If you're a noob with this just don't reply, I've never had experience with Samsung phones before thats why I'm seeking for help, if it comes to HTC or LG phones I usually get things done myself. Not in this case tho.
Jopponius said:
I am a noob in this, but logicaly reasoning i would say you bricked it bad by flashing away with all kind of csc and firmware down and upgrades.
Your aunt will not be happy.
Click to expand...
Click to collapse
No, as was already stated, it bricked with an OTA, flashing different stock ROMs & CSCs would not brick it
---
Try using Samsung SmartSwitch emergency firmware recovery, I think you'll need the phones serial number (Box / back of phone)
Other than that, using ODIN 3.12.3 or newer with the correct stock ROM & CSC the phone originally came with (newest available release), using CSC and not HOME_CSC to force a reset after the flash should work, then you'll need her google account login to get past the FRP lock
*Detection* said:
No, as was already stated, it bricked with an OTA, flashing different stock ROMs & CSCs would not brick it
---
Try using Samsung SmartSwitch emergency firmware recovery, I think you'll need the phones serial number (Box / back of phone)
Other than that, using ODIN 3.12.3 or newer with the correct stock ROM & CSC the phone originally came with (newest available release), using CSC and not HOME_CSC to force a reset after the flash should work, then you'll need her google account login to get past the FRP lock
Click to expand...
Click to collapse
These kind of replies is what I need, thank you! Sadly when trying to use Smart Switch it instructs me to use some kind of "Backup Code" from another PC, I know for a fact my aunt doesn't do any backups and she doesn't even have a proper privat PC. I have a the original packaging IME and such at my hands!
You said flashing with Odin after a flash should work, but should I first use the "HOME_CSC" to flash and then the normal "CSC" to reset it afterwards?
The CSC file is a carrier customization file.: https://forum.xda-developers.com/s7-edge/help/csc-home-csc-simple-t3464835
audit13 said:
The CSC file is a carrier customization file.: https://forum.xda-developers.com/s7-edge/help/csc-home-csc-simple-t3464835
Click to expand...
Click to collapse
so in this case with the DBT version it's just the default customization file from Samsung, am I right?
Flashing either Home_CSC or CSC didn't had any effect on the S7 tho, it's still stuck in Boot loop with FRP Lock.
Let's say the phone is soft bricked, is there any way to get it back working, so I can flash the stock firmware afterwards`?
Paachan said:
These kind of replies is what I need, thank you! Sadly when trying to use Smart Switch it instructs me to use some kind of "Backup Code" from another PC, I know for a fact my aunt doesn't do any backups and she doesn't even have a proper privat PC. I have a the original packaging IME and such at my hands!
You said flashing with Odin after a flash should work, but should I first use the "HOME_CSC" to flash and then the normal "CSC" to reset it afterwards?
Click to expand...
Click to collapse
SmartSwitch Windows version shouldn't ask for any backup codes, only maybe the phone serial number
And no, just forget about HOME_CSC, use CSC instead, this will initiate a factory reset after the flash
AP
BL
CP
CSC
Add all 4 parts to ODIN, put the phone in Download Mode (Volume Down & Home & Power) connect to PC USB and hit start on ODIN (3.12.3 or newer)
It "Should" flash the firmware and factory reset, and so long as there is no hardware fault, it should boot into Android and ask for the Google Login that was connected to the phone before it bricked, once you enter that it will allow the rest of the setup to continue and finally to homescreen
It is possible that there is a hardware fault that caused the OTA to brick in the first place, or that the phone is not what it claims to be (Check in download mode which model it says it is, some are faked to look like International G930F when they are actually Snapdragon US models and require different firmware
If it is G930F, then flashing the latest DBT should work fine so long as it is not hardware related
*Detection* said:
SmartSwitch Windows version shouldn't ask for any backup codes, only maybe the phone serial number
And no, just forget about HOME_CSC, use CSC instead, this will initiate a factory reset after the flash
AP
BL
CP
CSC
Add all 4 parts to ODIN, put the phone in Download Mode (Volume Down & Home & Power) connect to PC USB and hit start on ODIN (3.12.3 or newer)
It "Should" flash the firmware and factory reset, and so long as there is no hardware fault, it should boot into Android and ask for the Google Login that was connected to the phone before it bricked, once you enter that it will allow the rest of the setup to continue and finally to homescreen
It is possible that there is a hardware fault that caused the OTA to brick in the first place, or that the phone is not what it claims to be (Check in download mode which model it says it is, some are faked to look like International G930F when they are actually Snapdragon US models and require different firmware
If it is G930F, then flashing the latest DBT should work fine so long as it is not hardware related
Click to expand...
Click to collapse
That actually helps me a ton, the Product name is fine it says it's a SM-930F so non US, I guess?
After flashing it with the newest available Stock Android 6 firmware (on which it was shipped originally) doesn't lead to anything it's still stucked in boot loop.
I guess it's a hardware fault then and not recoverable in the first place, thank you very much for your help!
I'm gonna try one last time with an older Version of Odin, maybe this leads to something!
Have a great day
I recommend flashing the same firmware onto the phone. Trying to flash an older bootloader may cause the flash process to stop as downgrading the bootloader is usually not permitted.
Do you know if oem unlock was enabled in the ROM settings? I'm not 100% but this may contribute to the issues with factory resetting and getting the phone to work.
Partitioning is not usually required if the computer is able to read he phone's partition table information. If a re-partition is required, you need to use the correct pit file for the phone when flashing a stock ROM in Odin.
audit13 said:
I recommend flashing the same firmware onto the phone. Trying to flash an older bootloader may cause the flash process to stop as downgrading the bootloader is usually not permitted.
Do you know if oem unlock was enabled in the ROM settings? I'm not 100% but this may contribute to the issues with factory resetting and getting the phone to work.
Partitioning is not usually required if the computer is able to read he phone's partition table information. If a re-partition is required, you need to use the correct pit file for the phone when flashing a stock ROM in Odin.
Click to expand...
Click to collapse
the OEM unlock setting was on default, so off I guess? It was just a regular OTA update and then the phone was stuck in a boot loop.
As *Detection* said it's probably is a hardware related issue I just now noticed that the status LED doesn't even light up if you charge the device (maybe this is an idicator)
I would've gladly used it as a backup device but I think it's just an expensive paperweight by now.
Still thank you for your help, appreciate it!
Sounds like you have tried all you can on your own. Maybe take it to a cell repair shop and have them try to force flash the phone using hardware such as an octopusbox?
Paachan said:
That actually helps me a ton, the Product name is fine it says it's a SM-930F so non US, I guess?
After flashing it with the newest available Stock Android 6 firmware (on which it was shipped originally) doesn't lead to anything it's still stucked in boot loop.
I guess it's a hardware fault then and not recoverable in the first place, thank you very much for your help!
I'm gonna try one last time with an older Version of Odin, maybe this leads to something!
Have a great day
Click to expand...
Click to collapse
Yep G930F is International Exynos so you should be good
Some people have problems downgrading from 7.0 to 6.0, what I meant was flash the latest available firmware for DBT, which is 7.0
2018-04-23
Germany
7.0
G930FXXS2DRDI
As above, the bootloader can be a pain to downgrade, so always try unbricking with the latest firmware available
Same process as I posted above, only using the firmware in this post ^^
Good luck
---------- Post added at 19:59 ---------- Previous post was at 19:50 ----------
Paachan said:
I just now noticed that the status LED doesn't even light up if you charge the device (maybe this is an indicator)
Click to expand...
Click to collapse
Yea that doesn't sound good, possibly a faulty motherboard, they seem to be quite a high % of hardware faults of the S7 on XDA, at least that is the outcome of sending them in for repair, but also could be the repair centres way of making the most £
Paachan said:
the OEM unlock setting was on default, so off I guess? It was just a regular OTA update and then the phone was stuck in a boot loop.
As *Detection* said it's probably is a hardware related issue I just now noticed that the status LED doesn't even light up if you charge the device (maybe this is an idicator)
I would've gladly used it as a backup device but I think it's just an expensive paperweight by now.
Still thank you for your help, appreciate it!
Click to expand...
Click to collapse
What version bootloader is it running go to download mode to find out top left corner last line of writing will be AP SWREV B:? what number is next to the B you will need to match this to the firmware you are trying to flash for example i use unbranded australian G930FXXU2DRBE firmware and in download mode my AP SWREV is B:2 the number signifies the bootloader its running some exapmes are below for you
AP SWREV B:1 = G930FXX "U1" DRBE
AP SWREV B:2 = G930FXX "U2" DRBE
AP SWREV B:3 = G930FXX "U3" DRBE
You need to match the number next to AP SWREV B:? with the firmware number "U?" For it to work even if it is the same marshmallow or nougat OS it must use the correct bootloader and firmware appropriate to be able to boot i have encountered this problem on numerous occasions if you try to flash a U1 to a U2 binary it will not boot it will not even write it to the memory and you will end uo with a bricked device until the appropriate firmware has been flashed using odin.
You need to also make sure you are using the latest version of odin and have all the drivers installed to your pc for the phone also the status led will not illuminate either while its bricked like this either you will not get this until the OS has been repaired.
If none of this works you could always flash TWRP to it with odin in the AP tab download linage 15.1 oreo 8.1 custom rom for G930F exynos and a gapps .ZIP files move them to an sd card and insert into phone boot into twrp swipe to allow modifications first tap back up and select EFS & BASEBAND and backup this contains your imei number you always should have a back up before flashing a custom rom just incase something goes wrong now after that go to wipe tap the format button on the right and select everything exept otg this will wipe everything and i mean everything OS related which is really want you want to do and also remove the DM verity encryption from the device to be able to boot no after that go to install and select the .ZIP rom and gapps and install after boot you can then re flash stock rom with odin and it should boot however warranty will be void and samsung KNOX will be triggered which means secure file cannot be used nor samsung health app however there is a simple solution i have found to get samsung health running on a rooted device i hope this helps its always worked for me ive purposly bricked my dev G930F so many times on purpose even lost the imei number before and gotten it back without flashing the backup they are really quite hard phones to break software wise.
Thanks
Matty1993
Matty1993 said:
What version bootloader is it running go to download mode to find out top left corner last line of writing will be AP SWREV B:? what number is next to the B you will need to match this to the firmware you are trying to flash for example i use unbranded australian G930FXXU2DRBE firmware and in download mode my AP SWREV is B:2 the number signifies the bootloader its running some exapmes are below for you
AP SWREV B:1 = G930FXX "U1" DRBE
AP SWREV B:2 = G930FXX "U2" DRBE
AP SWREV B:3 = G930FXX "U3" DRBE
You need to match the number next to AP SWREV B:? with the firmware number "U?" For it to work even if it is the same marshmallow or nougat OS it must use the correct bootloader and firmware appropriate to be able to boot i have encountered this problem on numerous occasions if you try to flash a U1 to a U2 binary it will not boot it will not even write it to the memory and you will end uo with a bricked device until the appropriate firmware has been flashed using odin.
You need to also make sure you are using the latest version of odin and have all the drivers installed to your pc for the phone also the status led will not illuminate either while its bricked like this either you will not get this until the OS has been repaired.
If none of this works you could always flash TWRP to it with odin in the AP tab download linage 15.1 oreo 8.1 custom rom for G930F exynos and a gapps .ZIP files move them to an sd card and insert into phone boot into twrp swipe to allow modifications first tap back up and select EFS & BASEBAND and backup this contains your imei number you always should have a back up before flashing a custom rom just incase something goes wrong now after that go to wipe tap the format button on the right and select everything exept otg this will wipe everything and i mean everything OS related which is really want you want to do and also remove the DM verity encryption from the device to be able to boot no after that go to install and select the .ZIP rom and gapps and install after boot you can then re flash stock rom with odin and it should boot however warranty will be void and samsung KNOX will be triggered which means secure file cannot be used nor samsung health app however there is a simple solution i have found to get samsung health running on a rooted device i hope this helps its always worked for me ive purposly bricked my dev G930F so many times on purpose even lost the imei number before and gotten it back without flashing the backup they are really quite hard phones to break software wise.
Thanks
Matty1993
Click to expand...
Click to collapse
Holy, this is a pretty explicit answer, thank you!
Judging by that I seem to have the right firmware for my Boatloader:
{
"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"
}
Sorry for my late reply!
Paachan said:
Holy, this is a pretty explicit answer, thank you!
Judging by that I seem to have the right firmware for my Boatloader:
Sorry for my late reply!
Click to expand...
Click to collapse
No problem for the late reply yep firmware looks good matches to the BL however i noticed its says your binary and OS are custom when it should say official in donload mode was it previously rooted at some point ? Also have you downloaded the firmware from sammobile ? I would suggest using them for full original firmware packages as they have not been altered and will not apprear as custom when you try to flash with odin, does it complete the flash process and say pass or does it say fail ? Youll also notice when you flash on the screen of the phone it will have a progress bar in sync with odin does it complete the process and reboot or does it say blocked by frp lock if it says blocked by frp lock the firmware your trying to flash is not official you will need official firmware also as it already says custom find a twrp recovery.tar from the twrp website open odin place it in the AP section as soon as it reboots hold the power home ans volume up buttons until twrp appears swipe to allow modifications now go to wipe instead of factory resetting there will be a button saying format on the right tap that and type yes this will erase everything including the custom os it has on it i want you to do this step first before trying to flash the original firmware package as it will wipe everything for a fresh clean install.
Paachan said:
Holy, this is a pretty explicit answer, thank you!
Judging by that I seem to have the right firmware for my Boatloader:
Sorry for my late reply!
Click to expand...
Click to collapse
I'm not 100% sure about this, but that firmware states S2 not U2
See here, my BL is B:2 but all of the firmware files I can successfully flash are U2
Matty1993 said:
No problem for the late reply yep firmware looks good matches to the BL however i noticed its says your binary and OS are custom when it should say official in donload mode was it previously rooted at some point ? Also have you downloaded the firmware from sammobile ? I would suggest using them for full original firmware packages as they have not been altered and will not apprear as custom when you try to flash with odin, does it complete the flash process and say pass or does it say fail ? Youll also notice when you flash on the screen of the phone it will have a progress bar in sync with odin does it complete the process and reboot or does it say blocked by frp lock if it says blocked by frp lock the firmware your trying to flash is not official you will need official firmware also as it already says custom find a twrp recovery.tar from the twrp website open odin place it in the AP section as soon as it reboots hold the power home ans volume up buttons until twrp appears swipe to allow modifications now go to wipe instead of factory resetting there will be a button saying format on the right tap that and type yes this will erase everything including the custom os it has on it i want you to do this step first before trying to flash the original firmware package as it will wipe everything for a fresh clean install.
Click to expand...
Click to collapse
Actually scratch that frp lock is on you cannot flash anything custom to it while it is on just download your firmware from sammobile they have every country and are 100% official i will only download my firmwarw from there it is completely free to make an account and download the only thing is download speeds are slow so will take 2-3 hours to download is the only downfall but gauranteed to be official once downloaded place The files in corresponding slots in odin but with CSC just use CSC & not HOME_CSC this will perform a full wipe
Also maybe download U2 firmware aswell as S2 firmware
Matty1993 said:
Actually scratch that frp lock is on you cannot flash anything custom to it while it is on just download your firmware from sammobile they have every country and are 100% official i will only download my firmwarw from there it is completely free to make an account and download the only thing is download speeds are slow so will take 2-3 hours to download is the only downfall but gauranteed to be official once downloaded place The files in corresponding slots in odin but with CSC just use CSC & not HOME_CSC this will perform a full wipe
Click to expand...
Click to collapse
samfirm tool on XDA is full speed and downloads the latest stock ROM for whichever device you enter, direct from samsung servers
*Detection* said:
samfirm tool on XDA is full speed and downloads the latest stock ROM for whichever device you enter, direct from samsung servers
Click to expand...
Click to collapse
Or that also maybe yeah try U2 firmware instead of S2 as far as im aware S2 is the first of the B:2 binary updates
I'm currently running a T-Mobile Samsung Galaxy S7 with an AT&T sim card.
Model# SM-G930T.
Android Version 8.0.
Baseband Version G930TUVU4CRI2.
Build Numer R16NW.G930TUVU4CRI2.
I'm wanting to hopefully flash the AT&T firmware to this phone, but I'm not exactly sure how to go about doing it. I've spent about 2-3 hours searching back & forth between the AT&T forums & T-Mo forums but can't seem to find a definitive answer, or definitive guidance.
I think it's fairly simple via Odin once I have the appropriate firmware. But I just wanted to make sure since I'm flashing another carriers firmware on top of an existing carriers firmware.
Everything aside from video calling & WiFi calling is working. I would love to be able to use those 2 features & receive future OTA updates. Any info/guidance is greatly appreciated. Thanks!
No love?
I'd settle for an insulting reply guiding me in the right direction. I just don't want to brick my phone throwing AT&T firmware right over top of T-Mobile firmware.
The rom you are looking for is here: https://forum.xda-developers.com/att-galaxy-s7/development/rom-t3804287
I am using it now and love it. Several options for the install. Can root if desired.
ff-racer said:
The rom you are looking for is here: https://forum.xda-developers.com/att-galaxy-s7/development/rom-t3804287
I am using it now and love it. Several options for the install. Can root if desired.
Click to expand...
Click to collapse
Thanks for the response racer! I'm gonna bookmark that page and definitely save it. Right now I'm looking to stay 100% stock. But I'll definitely go that route if I can't get any guidance on going stock AT&T.
Drewbalicious said:
Thanks for the response racer! I'm gonna bookmark that page and definitely save it. Right now I'm looking to stay 100% stock. But I'll definitely go that route if I can't get any guidance on going stock AT&T.
Click to expand...
Click to collapse
Going stock AT&T is no harder than going stock for any carrier - here is the skinny, using SamFirm 0.3.6, the latest version of ODIN and a S7 of the Snapdragon sort (along with variations for the S7 Edge):
1. Automatic search using SamFirm - the easiest method - SM-G930A (for the S7 edge - SM-G935A) with a country/carrier code of ATT (both phones)
2. Once the firmware shows up, select where you want it stored on your PC, then select Download Automatically/Decrypt Automatically (this performs all the scutwork for you, such as checking for CRC32 errors, as well as separating the firmware itself so you can simply plus the parts into ODIN.).
3.. Once you have the firmware downloaded and decrypted, it's time to put ODIN to work; but before you can do that, you have to do two things; physically connect the phone to the PC, and get your phone itself ready to receive the files via ODIN. The ODIN part is easy - your newly-downloaded firmware is in multiple parts; each part fits in a specific block in ODIN. For the CSC part, you have a choice between CSC and HOME-CSC. Because I tend to make sure nothing is left over from the previous firmware, I choose CSC; this forces the new firmware to start from scratch. Lastly, before sending those files to the phone, you must enable the phone to be able to get them - you have to put the phone into Download Mode. (for all Snapdragon S7s - including the S7 Edge, it is Volume-up, Power, and Fingerprint-sensor (all at the same time)); a sky-blue screen will show, indicating you are in Download mode; this is what you want. Make sure your cable is properly connected, then hit the Start button in ODIN - that's it. (As long as the transfer is successful (which ODIN itself will tell you with a green PASS message) you're done the hard part; the phone will auto-reboot and start the Setup process for the new firmware.
Have at it.