Galaxy s7 stuck at certain build - Samsung Galaxy S7 Questions and Answers

I flashed in my galaxy s7 G930F
Alexndr.G930FXXUS3ERI1
Then tried to install another build of this rom
My sim card won't work like it's not even inserted
G930FXXU2ERGE that's the other build i tried to install
And tried an s8 rom can't remember its name and same issue
Even when i tried to flash the stock AUT & UK builds with odin and it fails and gives my system rev. check fail device:1, binary:0
Or system rev. check fail device:1, binary:2
Unless it's the build as the one i mentioned G930FXXUS3ERI1
My phone is exynos and suppose to flash any rom with problems before
Can anyone plz tell me what's is going on

G930FXXUS3ERI1 is higher version of G930FXXS3ERHD and samsung is locked the bootloader in G930FXXS3ERHD Version. So you cant downgrade from G930FXXUS3ERI1 and G930FXXS3ERHD to G930FXXU2ERGE. This problem is happen with me and my phone is under warranty (Knox 0x000) and service center will change the motherboard. you have no option to downgrade. Phone will accept only G930FXXUS3ERI1 version, so wait for next official update version of your country. When a similar or higher version come in your country you can able to flash.
I post on xda and i found one solution for root user. See here
Sorry for bad English.

My phone originally from Switzerland so it's AUT firmwares
And i always tried many custom roms with other countries and it worked just fine
I was on G930FXXU2ERGE
After trying this build G930FXXUS3ERI1 it got stuck on it
So u telling me that build is stuck on the motherboard
And i can't downgrade to nougat roms or other oreo builds but the one I'm on?! ?

justin tofa said:
I flashed in my galaxy s7 G930F
Alexndr.G930FXXUS3ERI1
Then tried to install another build of this rom
My sim card won't work like it's not even inserted
G930FXXU2ERGE that's the other build i tried to install
And tried an s8 rom can't remember its name and same issue
Even when i tried to flash the stock AUT & UK builds with odin and it fails and gives my system rev. check fail device:1, binary:0
Or system rev. check fail device:1, binary:2
Unless it's the build as the one i mentioned G930FXXUS3ERI1
My phone is exynos and suppose to flash any rom with problems before
Can anyone plz tell me what's is going on
Click to expand...
Click to collapse
Once you flash a ROM with a "3" bootloader, you can no longer revert to one with a "2" (or lower). Since you flashed 3ERI1, you can't revert to 2ERGE. Since the "3" bootloader was just released, there really isn't much to roll back to (there is currently a choice between 3ERI1 and 3ERH*).
Having said that, the Alexndr ROM is quite nice and virtually stock (I use it). And with the 3ERI1 build, Samsung appears to have overcome the very annoying random reboot problem that has plagued its recent ROMs.

Yes i been using it too
And that's my current rom nw also same build as yours
But idk why the complication with the bootloader thing with the firmwares
They should have left it like it was
With no restrictions

Related

Not to flash Samsung Galaxy S6 via Odin

Hello
I have the official version of Android 5.1.1 SK region and would like to upload Officiální Android version 5.1.1 CZ region. Flash Odin FAIL. Please someone help? Thank you.
JABV90 said:
Hello
I have the official version of Android 5.1.1 SK region and would like to upload Officiální Android version 5.1.1 CZ region. Flash Odin FAIL. Please someone help? Thank you.
Click to expand...
Click to collapse
Had a similar issue yesterday when I tried to update my rooted 5.0.2 to an official 5.1.1. I have used ODIN many times before since SGS3, and back then you were able to mix your system image from other regions, but that apparantly has been locked down by Samsung. Now you can only update an official version of the rom if it exactly matches your existing region. Because you updated your SK international S6 and tried a region set rom from Czech it most likely failed towards the very end of flash with "FAIL".
Your options are: 1) you download the 5.1.1 version for your region in ODIN format from SAMMobile or 2) you use Smart Switch and let it do it for you - in this case you will need to know the SN of your phone as it is used for verification.
Samsung has locked down the serial number with the regions that come with it. So if you have to install, you should update it or use same region odin file. There is a way to break this chain if you are rooted and some additional files are being used in the odin but I am not completely sure as I have not tried it yet. But there are chances that you may void your warranty if you try that or the worse hard brick as it can sometimes change your serial number if not used properly. but I wouldn recommend that. I'll let you know once I understand the usage correctly.

[Q] HELP G920T flashed wrong carrier stock ROM

I recently received a T-Mobile Galaxy S6, and it was rooted and had a custom kernel, which was a complete mess (the person who owned the phone previously clearly did not know what they were doing) so I just wanted to restore it back to full stock.
I am decently experienced with ODIN, rooting, custom firmware etc, but I have just done one of the biggest rookie mistakes I have ever done. I had accidentally downloaded the most recent firmware for my G920T, not realizing that the file was not for T-Mobile. It was the (XAR) carrier (I believe that is C-Spire but i could be wrong) and the latest was PK1.
It flashed perfectly and all seemed fine until I decided to unlock the device. The T-Mobile S6 requires the use of the "Device Unlock" app and since I had flashed the wrong ROM, the phone thinks the Device Unlock app is not compatible. When I put a different GSM SIM card in the phone, it prompts me to use the Device Unlock app.
I do not have a previous NANDROID backup from the original T-Mobile ROM, and now that I am on the lastest Bootloader for XAR, it will not let me downgrade. I have tried flashing pretty much every MM bootloader and TWRP for both T-Mobile and XAR and none will work (except for what is currently on the device of course) I always get the error "Device: 5 Binary: 4" (sometimes the binary is 3, depending on which version of MM rom or BL I try)
To sum it all up, I am on PK1 (latest for XAR) and I need a way to get back to the official T-Mobile ROM (latest is PD1). Is there a magic method to get this figured out or am I pretty much stuck with what I got until T-Mobile releases an update that is PK1 or higher?
Thank you in advance to all of you that take your time to help (and I am sincerely sorry if I am posting in the wrong section)

ROM Dilemma

Hi Everyone,
I bought Samsung Galaxy S7 Duos from Dubai.
The phone becomes so annoying as it has some kind of Adware built-in, which always opens different kinds of websites, pop-up ads and PlayStore links (after every few minutes).
I tried every possible way to get rid of it but nothing useful, even the factory reset or hard rest doesn't work. Because the OS it self is buggy.
According to its Settings, the phone has Model No. SM-G930FD, and Android 7.0
Now I want to install the fresh and updated firmware, so I can free my self from this Adware and can enjoy Android 8.0
I have downloaded Android 8.0 firmware for SM-G930FD
I tried Odin to install this new firmware but encountered a new issue:
According to Phone's Download Mode, the phone model is SM-G930S instead of SM-G930FD
This means someone installed the local ROM on the Korean Phone. (am I right?)
Now when I'm trying to install Android 8.0 firmware for SM-G930FD (of any other region) it shows the error:
"Secure Check Fail: (PIT)"
I am out of ideas on what to try next
Whatever it says in download mode is what the phone actually is, everything else has been faked.
It's a common scam to use modified firmware to make a phone appear to be a different model, as some models sells for more than others.
This is likely what has happened to you, and also the cause of the apparent adware.
Stock G930F or FD firmware will bootloop a G930S, which is probably why Odin is refusing. You would either need to flash stock G930S firmware, or use a custom ROM compatible with G930S
Beanvee7 said:
Whatever it says in download mode is what the phone actually is, everything else has been faked.
It's a common scam to use modified firmware to make a phone appear to be a different model, as some models sells for more than others.
This is likely what has happened to you, and also the cause of the apparent adware.
Stock G930F or FD firmware will bootloop a G930S, which is probably why Odin is refusing. You would either need to flash stock G930S firmware, or use a custom ROM compatible with G930S
Click to expand...
Click to collapse
Thank you for the clarification
Now when I'm sure that my phone has G930S model, the option of stock ROM is only one: Android 8.0, Korea (SK Telecom)
1. By Googling a lot about this scam I'm afraid that changing the ROM may covert the phone into Single SIM version!
2. And if I install Korea (SK Telecom) ROM, will it lock the phone to Korean network only?
3. Do you think that "Korea (SK Telecom) ROM" will change everything into Korean?
Can you please clear my doubts
I don't know enough about the Korean stock ROM to answer those unfortunately.
But I do know many custom ROM's are compatible with G930F/FD and S, so I would assume allow dual SIM.

[HELP] SM-G930F stuck in boot loop after flashing wrong stock firmware

A while ago, I installed TWRP and then flashed Pixel Experience (herolte) onto my SM-G930F, but experienced some problems with it, namely random freezes and temporary boot loops, and decided to revert back to stock firmware.
I accidentally flashed SM-G930FD firmware instead of SM-G930F firmware, and now I am unable to re-flash and get out of a boot loop. I can boot into download mode and ODIN recognizes it, but whenever I boot into recovery mode, it will crash within the first 5 minutes (sometimes instantly, other times I can use it for at most 5 minutes before it crashes and reboots).
When trying to flash the correct firmware, I get revision check errors, with the device number being one above the binary number.
Is there any way to fix this, or should I give up? Can provide more information as necessary.
Edit: I believe the problem may be that I flashed an Android 9.0.0 firmware, and stock firmwares for the device are at latest 8.0.0. I am also unable to re-flash Pixel Experience, though, as TWRP crashes mid-flash every time.
Rustiniz said:
A while ago, I installed TWRP and then flashed Pixel Experience (herolte) onto my SM-G930F, but experienced some problems with it, namely random freezes and temporary boot loops, and decided to revert back to stock firmware.
I accidentally flashed SM-G930FD firmware instead of SM-G930F firmware, and now I am unable to re-flash and get out of a boot loop. I can boot into download mode and ODIN recognizes it, but whenever I boot into recovery mode, it will crash within the first 5 minutes (sometimes instantly, other times I can use it for at most 5 minutes before it crashes and reboots).
When trying to flash the correct firmware, I get revision check errors, with the device number being one above the binary number.
Is there any way to fix this, or should I give up? Can provide more information as necessary.
Edit: I believe the problem may be that I flashed an Android 9.0.0 firmware, and stock firmwares for the device are at latest 8.0.0. I am also unable to re-flash Pixel Experience, though, as TWRP crashes mid-flash every time.
Click to expand...
Click to collapse
Region / country are you?
Please quote the FD firmware you flashed I need to know the boot loader version.
Do you know what version firmware the device came with?
Please confirm you can enter Download mode?
cooltt said:
Region / country are you?
Please quote the FD firmware you flashed I need to know the boot loader version.
Do you know what version firmware the device came with?
Please confirm you can enter Download mode?
Click to expand...
Click to collapse
Hi, thank you for the reply.
The region of the phone was BRI/TGY (for some reason it was able to be either?) After searching, I couldn't find any SM-G930F firmware for these regions, which leads me to believe that despite the model being shown as SM-G930F in download mode, it might've actually been an SM-G930FD?
The FD firmware I flashed was G930FXXS4ESC7 (TGY).
I believe the device came with FD firmware? My memory may be tricking me but I believe when I checked with Phone Info SAM, the model showed up as SM-G930FD, with the firmware G930FXXS4ESC7 (but may be misremembering).
I can definitely enter download mode with an 100% success rate, and crashes do not occur while in download mode.
Rustiniz said:
Hi, thank you for the reply.
The region of the phone was BRI/TGY (for some reason it was able to be either?) After searching, I couldn't find any SM-G930F firmware for these regions, which leads me to believe that despite the model being shown as SM-G930F in download mode, it might've actually been an SM-G930FD?
The FD firmware I flashed was G930FXXS4ESC7 (TGY).
I believe the device came with FD firmware? My memory may be tricking me but I believe when I checked with Phone Info SAM, the model showed up as SM-G930FD, with the firmware G930FXXS4ESC7 (but may be misremembering).
I can definitely enter download mode with an 100% success rate, and crashes do not occur while in download mode.
Click to expand...
Click to collapse
Hi there, the firmware you have flashed is the latest version for Hong Kong and Taiwan so it is correct if your device is G930FD.
G930FD is dual SIM right? G930F is single SIM. However G930FD WILL work on a G930F device but G930F WILL NOT work on a G930FD
G930F = Europe and Canada
G930FD = Far East and Asia
On Sammobile website there is an earlier version of your firmware G930FXXS4ESB5, try this one instead and you can only use firmware which is "S4" G930FXXS4ESB5
Try flash it again
cooltt said:
Hi there, the firmware you have flashed is the latest version for Hong Kong and Taiwan so it is correct if your device is G930FD.
G930FD is dual SIM right? G930F is single SIM. However G930FD WILL work on a G930F device but G930F WILL NOT work on a G930FD
G930F = Europe and Canada
G930FD = Far East and Asia
On Sammobile website there is an earlier version of your firmware G930FXXS4ESB5, try this one instead and you can only use firmware which is "S4" G930FXXS4ESB5
Try flash it again
Click to expand...
Click to collapse
Thanks for the reply! I'll try it again using that firmware.
Also, I checked the SIM slot, and it says SIM1 and SD/SIM2, so I think it's a SM-G930FD. Weird that it says SM-G930F in download mode, is that based on firmware?
cooltt said:
Hi there, the firmware you have flashed is the latest version for Hong Kong and Taiwan so it is correct if your device is G930FD.
G930FD is dual SIM right? G930F is single SIM. However G930FD WILL work on a G930F device but G930F WILL NOT work on a G930FD
G930F = Europe and Canada
G930FD = Far East and Asia
On Sammobile website there is an earlier version of your firmware G930FXXS4ESB5, try this one instead and you can only use firmware which is "S4" G930FXXS4ESB5
Try flash it again
Click to expand...
Click to collapse
Okay, I tried flashing G930FXXS4ESB5, and ended up with the same error, being that the device version is higher than the binary version. (5 vs 4 for bootloader)
At this point I don't think the error has anything to do with the fact that I flashed different firmware, but rather that the version of the bootloader, kernel, etc. are patched higher than the firmware, but there is no Android 9.0.0 firmware that I can flash.
Rustiniz said:
Okay, I tried flashing G930FXXS4ESB5, and ended up with the same error, being that the device version is higher than the binary version. (5 vs 4 for bootloader)
At this point I don't think the error has anything to do with the fact that I flashed different firmware, but rather that the version of the bootloader, kernel, etc. are patched higher than the firmware, but there is no Android 9.0.0 firmware that I can flash.
Click to expand...
Click to collapse
Ok try Singapore XSP that has a version 5 Binary, here
Also to get it faster Google "Samfirm tool" and how to use it.
cooltt said:
Ok try Singapore XSP that has a version 5 Binary, here
Also to get it faster Google "Samfirm tool" and how to use it.
Click to expand...
Click to collapse
The flash passed, but now (as before), the phone simply comes up with "Error!" once installing system update finishes, followed by another reboot and no command.
Rustiniz said:
The flash passed, but now (as before), the phone simply comes up with "Error!" once installing system update finishes, followed by another reboot and no command.
Click to expand...
Click to collapse
Ok when no command comes up reboot to system recovery and choose wipe/ factory reset and reboot.
No command means the firmware has worked just needs a final factory reset
cooltt said:
Ok when no command comes up reboot to system recovery and choose wipe/ factory reset and reboot.
No command means the firmware has worked just needs a final factory reset
Click to expand...
Click to collapse
That's where the unfortunate final problem comes in, in that the recovery menu will freeze within about 10 seconds of reaching recovery mode, sometimes even before getting past "#MANUAL MODE 1.0.0#" and rebooting automatically. The time seems to be almost random, but I've never been able to perform a factory reset. The furthest I get is formatting /data, even leaving that overnight, it was definitely frozen.
Edit: I managed to perform both a factory reset and cache partition wipe, but still get "No Command" when booting the phone.
Edit 2: Nevermind, apparently factory reset and cache partition wipe worked! I can now boot successfully and the phone works. Although I still have the problem with random freezing and reboots, it's better than a bricked phone. Thank you!

g970n vs g970f

Hi all,
Yesterday I bought an S10e under the impression that it is sm-g970F.
Trying to flash Android 11 I discovered that it is actually sm-g970N.
Is there really a difference between them?
Should I be worried that some functions will be missing/unavailable?
Also, in the settings, it appears as g970F. How did the seller change it??
I have the same problem i tried to update the phone to the latest sm-g970f rom (figured if it's already installed it's possible)
And non of the roms flashed only when i decided to try latest sm-g970n rom it flashed however i bricked the phone and i have no idea what to do now.
almogkm said:
Hi all,
Yesterday I bought an S10e under the impression that it is sm-g970F.
Trying to flash Android 11 I discovered that it is actually sm-g970N.
Is there really a difference between them?
Should I be worried that some functions will be missing/unavailable?
Also, in the settings, it appears as g970F. How did the seller change it??
Click to expand...
Click to collapse
So after digging into the issue since i have the same problem here are my conclusions:
1. The phone is a Korean Variant G970N it is probably a renewed phone and not a new one.
apparently it's okay for an importer to take used phones (from Korea in this case) and replace all the cosmetics but of cause leaving the used MB.
Now here is what you should worry about, in order to flash the G970F Fixed Rom (there is no way you have updates) they used a Custom Kernel which means the phone was rooted and now Knox is tripped (this not reversible).
(Download Phone Info from play store and check knox if it shows 0x1 then your phone warrenty is void and some features won't be available any more for example - Samsung Pay).
So what should you do?
Well if you still have the option i would have demanded my money back!!
One thing that i am perplexed about is how in hell is this legal?!!!
If you no longer have this option or you want to keep the phone you have two option:
1. Flashing Korean Unbranded Firmware (KOO) which is pretty good it doesn't have bloatware or issues as far as i can tell, i only found one down side for it, the phone language selection is small but if you only need English (like any normal Human) then you are golden.
2. Keep the G970F ROM but bare in mind it will receive no updates and no security patches.
I am still looking for a proper way to flash G970F Firmware over G970N for now i haven't found any internet source that will confirm it's even possible.
So how did those importers\sellers did it, they probably flashed it with a Cellphone Lab Software (not Odin solution) and used a custom Kernel to fool Knox, like i said before this is practically a crime and i don't understand how can they sell used phones as new and get away with it!!!!
I had the same suspicions....
I'll try going to the lab that sold the previous owner the device and deal with them tho it looks like I just got scammed...
Sorry to bring this up again but I've just had an idea following JerryRigEverything's video:
What if I transplant SM-G970F components from a broken device that no longer works or in use in my SM-G970N which is supposedly new.
My N device is now bricked for some reason I couldn't solve, though my suspicion is that it has to do with incompatibility with the SIM card I use.
When my device did work, it worked great! ...besides battery issues that are most likely a result of the incompatibility aforementioned.
Will this work? If so, what components do I need? I already know I'll need the logic board but as seen in the video, there are several more antennas, should I just copy what Jerry did?
Vegetto32 said:
I have the same problem i tried to update the phone to the latest sm-g970f rom (figured if it's already installed it's possible)
And non of the roms flashed only when i decided to try latest sm-g970n rom it flashed however i bricked the phone and i have no idea what to do now.
Click to expand...
Click to collapse
Hi Vegetto,
I am from India and buy a galaxy S10e from UAE, It is showing G970F in the Phone's about but the problem is It is a G960N. Now, When I see in Sam Phone Info app there is Bootloader version - G970N, PDA Version - G970F, CSC G970F.
It is also a Knox tripped phone. Knox 0/1.
But if I see in Samsung code by typing in keypad *#12580*369#
it showing like all option in Odin:
BL: G970F
AP: G970F
CP: G970F
CSC: G970F
Does this means I can flash new Firmware on the list of SAM Mobile website, with G970F series firmware, It also showing in SAM Phone Info App that there latest firmware G970FXXSEFUL1/G970FOXMEFUJ2/G970FXXSEFUJ2.
I am in India right now.
Please help me, My email Id is -- [email protected]
It actually means you cannot flash SM-G970F the only roms you can flash are G970N.
Also if you want the phone to get security updates you must flash the original phones bootloader version, my suggestion download the G970N KOO firmware it's a global firmware. As for the knox it is tripped and there is nothing you can do about it.
Vegetto32 said:
It actually means you cannot flash SM-G970F the only roms you can flash are G970N.
Also if you want the phone to get security updates you must flash the original phones bootloader version, my suggestion download the G970N KOO firmware it's a global firmware. As for the knox it is tripped and there is nothing you can do about it.
Click to expand...
Click to collapse
How can I flash the original phone's bootloader version?
Where from I can download the original phone's G970N KOO Firmware and is it official Samsung Firmware?
How are they able to flash G970F? Is it custom Rom or do they use the original one?
I searched that my phone is using G970FXXS4BTB3 firmware which Vietnam XXV and same number found at https://www.sammobile.com/samsung/galaxy-s10e/firmware/SM-G970F/XXV/download/G970FXXS4BTB3/322678/ in an old update in 2020.
So see the attached screenshot, can I flash its latest version with odin. Of course, there is a chinese written in recovery mode installed when I go to its recovery mode for flashing with Odin.
I have a similar problem right now on my Korean S10E. Device is SM-G970N. I need it to be in Turkish. Only Themes item in Settings is in Turkish- very interesting- The rest is in English. App names are mostly Turkish Settings app name is in English.
The bootloader is unlocked but the phone is not rooted, Knox seems not tampered.
Could not start OTA update at first, I have upgraded a few versions from PC via Smartswitch. Just then noticed OTA also started downloading. The rest of the updates went on from the phone until upgrading to 12, there was a message like "All of the updates were not succesful." OTA update no longer responded. This time I turned back to Smart Switch. Update finished this time and finally I am at the latest version.
I only need Turkish in Settings. I used some ADB commands and an app called MoreLocale2. It did not work either. This has to be simple. Turkish exists. Keyboard is Turkish but not Settings. Quick links and most other things are strangely mixed English and Turkish.
How can I enable full Turkish?

Categories

Resources