Database Info

Firmware help g930f

I HAVE A SM-G930F S7
GOT IT FROM ONE OF THOSE RENT TO OWN PLACES AND IT IS STUCK WITH THERE FIRMWARE
and i can not upgrade to the latest nougat build
was wondering how do i determine what the factory shipped firmware should be so i could download
it from sammobile... but i can not find my region code on the site..
I LIVE IN SAGINAW,MICHIGAN USA
any help would be appreciated
BASEBAND: G930FXXU1APB4
BUILD NUMBER:MMB29K.G930FXXU1APB4_RAC_V1.0.0
WOULD LIKE TO BE ABLE TO UPGRADE

I'm coming across the same issue - did you ever figure it out? I'm thinking of flashing a stock firmware (but can only find an updated one), then rooting. But without being able to access developer options, I'm leary of doing even that.

stgibson said:
I'm coming across the same issue - did you ever figure it out? I'm thinking of flashing a stock firmware (but can only find an updated one), then rooting. But without being able to access developer options, I'm leary of doing even that.
Click to expand...
Click to collapse
It might depend on who your carrier is.
Not being able to access developer options? What are you talking about? Go to system settings>about>build number or system settings>about>software info>build number or something similar, find the "build number" or "build no.", tap it 7 or 8 times quickly untli you see the notification that you've unlocked developer options.
Sent from my LGL84VL using Tapatalk

Droidriven said:
It might depend on who your carrier is.
Not being able to access developer options? What are you talking about? Go to system settings>about>build number or system settings>about>software info>build number or something similar, find the "build number" or "build no.", tap it 7 or 8 times quickly untli you see the notification that you've unlocked developer options.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thanks, @Droidriven! I'm going to be using it on AT&T, then on China Unicom. And I want it unlocked. Thus why I got the G930f, not g930a. This phone hasn't locked me out of the system (yet). I did manage to find a build with the same base as mine (G930FXXU1APB4 at https://updato.com/firmware-archive-select-model?record=07054BA22E5811E6815B0CC47A44B7B2). But my build is MMB29K.G930FXXU1APB4_RAC_v1.0.0, and device status says "custom". When I go into the software info, I can tap on everything else and get a "greyed" response, but not when I tap on build number. Seems to be a locked down version. [Edit: downloading a "developer options" app lets me get to it.] That said, I think this thread (https://forum.xda-developers.com/galaxy-s7/how-to/s7-sm-g930f-rent-center-lock-workaround-t3518682) may work, even though my device hasn't locked me out like some people have had. I'll try that method this morning with the similar stock build and see.
My main concern is causing an issue because of not having USB debugging and /or OEM unlock enabled. Especially if I go straight to a newer version that may require the pin unlock for boot (I saw one of the stock rom pages, can't find it again right now, with 8.0 roms had warnings all over that pin unlock on boot had to be enabled prior to flashing, otherwise you'd flash it and it'd ask for the pin and no luck).
So do you see any problem being able to flash according to the link above without the developer options enabled? [Edit: now that I can get access to developer options through the app, I'm less worried.]

For future reference, this worked, following the instructions (modified slightly here) by bishopag at https://forum.xda-developers.com/galaxy-s7/how-to/s7-sm-g930f-rent-center-lock-workaround-t3518682 worked, using the G930FXXU1APB4 baseband at https://updato.com/firmware-archive-select-model?record=07054BA22E5811E6815B0CC47A44B7B2.
1. Install one of the "bootloader options" from Play Store, use it to ensure that OEM unlock and USB debugging (optional?) are enabled
2. Download the Stock firmware of your choice from Sammobile [or from above link]
3. Unzip/unrar it and pull out the BL and CP for bootloader and modem
4. Grab TWRP from https://dl.twrp.me/herolte/twrp-3.2.3-0-herolte.img.tar.html
5. Grab Odin 3.12 from http://odindownload.com/SamsungOdin/#.WFBEZsmB3mE
6. Put the Device in Download Mode (Hold Vol Down, Power, Home)
7. Use Odin to flash TWRP to the device (AP)
8. Reboot into Recovery Mode (Hold Vol Up, Power, Home)
9. In TWRP use Advanced Wipe to Wipe everything except the SD Card. If it fails use Reset Data first, then Wipe
10. Go to Advanced -> Terminal Command -> hit "Select"
11. type these comands
dd if=/dev/zero of=/dev/block/sda11
dd if=/dev/zero of=/dev/block/sda13
(Note: I got a message that storage was full, but on inspection I could see that the data had been written based on input & output bytes)
12. Do a factory reset with the recovery
13. Reboot into Download mode from TWRP Reboot menu
14. Use Odin to Flash the BL, CP, and AP
15. That's it. Wait for it to boot and setup (might take 5-10 min)

stgibson said:
Thanks, @Droidriven! I'm going to be using it on AT&T, then on China Unicom. And I want it unlocked. Thus why I got the G930f, not g930a. This phone hasn't locked me out of the system (yet). I did manage to find a build with the same base as mine (G930FXXU1APB4 at https://updato.com/firmware-archive-select-model?record=07054BA22E5811E6815B0CC47A44B7B2). But my build is MMB29K.G930FXXU1APB4_RAC_v1.0.0, and device status says "custom". When I go into the software info, I can tap on everything else and get a "greyed" response, but not when I tap on build number. Seems to be a locked down version. [Edit: downloading a "developer options" app lets me get to it.] That said, I think this thread (https://forum.xda-developers.com/galaxy-s7/how-to/s7-sm-g930f-rent-center-lock-workaround-t3518682) may work, even though my device hasn't locked me out like some people have had. I'll try that method this morning with the similar stock build and see.
My main concern is causing an issue because of not having USB debugging and /or OEM unlock enabled. Especially if I go straight to a newer version that may require the pin unlock for boot (I saw one of the stock rom pages, can't find it again right now, with 8.0 roms had warnings all over that pin unlock on boot had to be enabled prior to flashing, otherwise you'd flash it and it'd ask for the pin and no luck).
So do you see any problem being able to flash according to the link above without the developer options enabled? [Edit: now that I can get access to developer options through the app, I'm less worried.]
Click to expand...
Click to collapse
I'm very familiar with flashing stock firmware on Samsung devices but I'm not familiar with the things that you are freaking out about.
Flashing a full stock firmware "should" remove the custom binary, it should say "official" when you're done.
As for build number, that shouldn't matter so much, as long as you are flashing a firmware that is meant for your model number. If you'll be using it on AT&T then flashing the AT&T stock firmware for G930F "should" work.
I've never encountered the issues that you are running circles around so I'm not sure my advice will do you any good. I don't want to walk you into any issues that I'm not sure I can help you solve.
Edit: It looks like the member that posted above has the solution you need, give it a try.
Sent from my LGL84VL using Tapatalk

Stuck with bootloader/eRecovery

Some context:
My MHA-L29C432B138 with TWRP got an OTA update on the phone itself, and I wanted to update (it wanted me to update to B182).
Since I had TWRP replacing the stock recovery I could not flash it through the normal way, so I went ahead to replace TWRP with the stock recovery so I could update.
I was unable to flash the stock recovery since I had no access to flashing in fastboot (FRP Lock, PHONE Unlocked, OEM unlocking option greyed out in developer settings), so I attempted to relock so I could unlock again, hoping that would solve my issue (fastboot oem relock KEY).
By doing this my phone went into a reset, now I'm stuck at FRP Lock, PHONE Relocked, and I can only access the bootloader and eRecovery.
eRecovery is attempting to download updates but fails every time, and I can't use HiSuite to do a system recovery neither (says my device is not supported).
So this is where I'm stuck, any help would be nice!

p3lim said:
Some context:
My MHA-L29C432B138 with TWRP got an OTA update on the phone itself, and I wanted to update (it wanted me to update to B182).
Since I had TWRP replacing the stock recovery I could not flash it through the normal way, so I went ahead to replace TWRP with the stock recovery so I could update.
I was unable to flash the stock recovery since I had no access to flashing in fastboot (FRP Lock, PHONE Unlocked, OEM unlocking option greyed out in developer settings), so I attempted to relock so I could unlock again, hoping that would solve my issue (fastboot oem relock KEY).
By doing this my phone went into a reset, now I'm stuck at FRP Lock, PHONE Relocked, and I can only access the bootloader and eRecovery.
eRecovery is attempting to download updates but fails every time, and I can't use HiSuite to do a system recovery neither (says my device is not supported).
So this is where I'm stuck, any help would be nice!
Click to expand...
Click to collapse
Try to unlock after this.
This does low-level format.
My device: Mate 9 supersu B190 Mediapad X2 GEM 701->703 B212 KangVIP (AJ mod)

Everything in fastboot (flashing, locking, unlocking) was unavailable, eRecovery was not working, HiSuite said my device was not supported, and dload didn't work neither (tried 3 different firmware versions).
After spending 1-2 hours on Telegram with others I ended up using funkyhuawei with eRecovery, only thing that worked for me.
Last time I buy a Huawei device for sure, their own services don't even work (eRecovery, HiSuite).

p3lim said:
Everything in fastboot (flashing, locking, unlocking) was unavailable, eRecovery was not working, HiSuite said my device was not supported, and dload didn't work neither (tried 3 different firmware versions).
After spending 1-2 hours on Telegram with others I ended up using funkyhuawei with eRecovery, only thing that worked for me.
Last time I buy a Huawei device for sure, their own services don't even work (eRecovery, HiSuite).
Click to expand...
Click to collapse
As I said here, for your case the patched HiSuite method would have worked. But it's too late now, you paid, I was in holidays.. I know it's a shame that HiSuite says unsupported or erecovery not working but you could have made your phone compatible by writing some text in a file and using Lucx's script instead of paying funkyhuawei, their service never worked for me.

dealth645 said:
As I said here, for your case the patched HiSuite method would have worked. But it's too late now, you paid, I was in holidays.. I know it's a shame that HiSuite says unsupported or erecovery not working but you could have made your phone compatible by writing some text in a file and using Lucx's script instead of paying funkyhuawei, their service never worked for me.
Click to expand...
Click to collapse
I'm on the same situation after a ROM installation using HWOTA failed, I don't want to pay $50 to unbrick the phone, could you please give me instructions on how to get this patched hisuite or which file I have to modify?
Thanks!

dealth645 said:
As I said here, for your case the patched HiSuite method would have worked. But it's too late now, you paid, I was in holidays.. I know it's a shame that HiSuite says unsupported or erecovery not working but you could have made your phone compatible by writing some text in a file and using Lucx's script instead of paying funkyhuawei, their service never worked for me.
Click to expand...
Click to collapse
Hi, am on the same situation, could you plz provide detailed steps to patch hisuite am unable to find any lucx's script.

i got my phone bricked like this

I could fix my phone flashing a factory firmware using DC Phoenix (Yes, I have to pay).
I Flash MHA-AL00 first, then I use eRecovery to install the latest stock firmware and finally HCU Client to repair the empty board (IMEI, S/N, MAC, etc).

I had the same then suddenly it is hardbricked no charging no nothing . It was a 1 month old phone. I didnt do anything other than downloading a c636 oreo and i was c185. But i received it trough the system update using firmware finder and even it authenticated itself. Even installed it with no problem. Then suddenly it broke and after soft brick became hard brick nothing. Now it in service centre i hope they can fix it. It is under warranty. pray for me

help me please
i have the same problem what should i do please help

dealth645 said:
As I said here, for your case the patched HiSuite method would have worked. But it's too late now, you paid, I was in holidays.. I know it's a shame that HiSuite says unsupported or erecovery not working but you could have made your phone compatible by writing some text in a file and using Lucx's script instead of paying funkyhuawei, their service never worked for me.
Click to expand...
Click to collapse
Same problem here with Mate 10, can you teach me how to write some text in a file and using lucx's script instead of funkyhuawei? THANKS!

Accidentally turned off Dev options after root and now FRP locked?

Had no idea the dev options needed to be left ON regardless after rooting, or it rejects the custom binary? Would have thought the FRP lock would have been bypassed with the rooting. Can't enter twrp recovery neither.
And to be 100% clear, phone is rooted. Dev option was unticked w/o realizing it'd retroactively lock the phone as it detects the non-oem firmware and refuses to boot, refuses recovery, refuses flashing.
Can I somehow flash a stock firmare via Odin and NOT get the wrath of FRP? I found the stock firmware for the phone from Samsung's site. For some reason, the firmware.zip is like 1.4gb? Do I need to strip out a file for the recovery image assuming it'll accept it? Or just select the entire thing in Odin?

OK, flashed the 2.5gb (unzipped it had THAT much bloat) factory Samsung firmware, which took about 2.5 minutes vs. like 4 sec for the root .img :silly: and phone boots back up w/o issue, all personal stuff is intact, and unsurprisingly it adds all the bloatware back that I just deleted earlier.
So, if you accidentally turn off the dev options or I'm assuming the OEM unlocker specifically on your J7, and the phone refuses to boot as it's retroactively detecting "custom binary", OR if you happen to accidentally truly delete an important app and/or it can't be brought back with 3rd party apps, going to Samsung's firmware section, finding your EXACT phone/model/software numbers including the most recent OS and security upgrade to it i.e. 7.1.1 in my case, flashing it with Odin (site said to use most recent, so used v3.13.1) will restore the phone, unrooted of course. But it's better than a paperweight.

Trouble in Rolling back to Stock ROM from OpenKirin on FRD-L14. Please Help~!

I tested the latest OpenKirin Omni ROM this weekend and decided to rollback to the stock OREO ROM on my FRD-L14. I followed the rollback instruction to the word - extract the image from the firmware downloaded from FF, flash the image file via Fastboot and I even relock the bootloader to turn it back to stock status.
However, I found that the phone contains only Huawei's software without any Google app. It is also impossible to input my Google account. After some panic, I decided to re-flash the ROM to try again but found I no longer can unlock the bootloader because the option got greyed out.
Now I have a phone with only voice and message access without any google app, so I cannot even brows the internet. Am I pretty much doomed? Please help!

CosmoHunter said:
I tested the latest OpenKirin Omni ROM this weekend and decided to rollback to the stock OREO ROM on my FRD-L14. I followed the rollback instruction to the word - extract the image from the firmware downloaded from FF, flash the image file via Fastboot and I even relock the bootloader to turn it back to stock status.
However, I found that the phone contains only Huawei's software without any Google app. It is also impossible to input my Google account. After some panic, I decided to re-flash the ROM to try again but found I no longer can unlock the bootloader because the option got greyed out.
Now I have a phone with only voice and message access without any google app, so I cannot even brows the internet. Am I pretty much doomed? Please help!
Click to expand...
Click to collapse
Can you enter into eRecovery? In eRecovery, you can connect to a Wi-Fi network and install the stock ROM.

ThePS4Gamer said:
Can you enter into eRecovery? In eRecovery, you can connect to a Wi-Fi network and install the stock ROM.
Click to expand...
Click to collapse
eRecovery connected to the Wifi but fail access info.

CosmoHunter said:
Now I have a phone with only voice and message access without any google app, so I cannot even brows the internet. Am I pretty much doomed? Please help!
Click to expand...
Click to collapse
I guess you can go to the apk mirror website, download Chrome (or Firefox), Google play store, Android webview etc, copy them to the phone via hisuite, and install them manually after switching on "Unknown sources".
Also, i have the impression (someone maybe correct me) that the OEM unlock stays greyed out only for a few days, and it will enable itself.

samsung galaxy s7 custom binary blocked by frp lock

Greetings, ever since i tried rooting my phone, i knew something went wrong (i used cf autoroot).
So the first thing i noticed, i was asked to reset the phone or something similar to that, meaning i would lose all my data.
I tried to find a workaround as this had never happened to me before while rooting a phone, and someone had said that i was supposed to download twrp
and change some partition and then change it back. I dont remember what else he mentioned and what exactly i tried doing, i realised it was formatted either way and i had to start fresh. As i setup my phone i went and switched the oem unlock back to "off", as i did not wanna attempt to root again, but i hadn't realised that my phone was infact rooted sucessfully, leading me to my first error after restarting. "Custom binary blocked by frp lock", with absolutely no access to recovery mode at all anymore. Again, trying to find a workaround, i download some stockfirmware that i atleast had hoped was the right one for my phone, after a couple failed attempts of flashing with odin, ( i had gotten various different error messeges on download mode screen such as (REV Check fail device 7 binary 0 and others witch i cannot remember), now im getting a new error screen, stating that an error has occured while updating the device software. I cant flash twrp recovery as the frp lock is on, and the only thing i can guess is that im flashing the wrong firmware, but i cant find a matching code at all.
Its the following: sm-g930fzkadbt
IMEI: 35214310282955
on the back of the phone it says uk yateley, although the phone was purchased in germany.
Im not sure what to do anymore, any advice would be greatly appreciated.
PS: I have managed to get back to the old error screen with the custom binary info, this time with bootloop, by checking the deviceinfo box on odin

Yep you've now learned the hard way not to mess about and read the proper guides.
Anyway "dbt" is just unbranded german firmware. Download UK "BTU" and flash with Odin, it's UK unbranded.
FRP lock means you'll need to unlock the phone with the google account and password that was on it before you started messing about with it.
If you don't know the google email and password you need to read up on how to bypass FRP lock and it's a nightmare.

cooltt said:
Yep you've now learned the hard way not to mess about and read the proper guides.
Anyway "dbt" is just unbranded german firmware. Download UK "BTU" and flash with Odin, it's UK unbranded.
FRP lock means you'll need to unlock the phone with the google account and password that was on it before you started messing about with it.
If you don't know the google email and password you need to read up on how to bypass FRP lock and it's a nightmare.
Click to expand...
Click to collapse
Thanks for your reply, just a question, will any btu update work? Should i download latest android version btu firmware?
(Also yes, it was stupid of me to try and do it quick but i had rooted 3 different samsung galaxy phones in the past without issues, either i did something wrong or it took something way too specific to do the job, perhaps the phone's unrootable, but thank you either way) :fingers-crossed:

Elef244 said:
Thanks for your reply, just a question, will any btu update work? Should i download latest android version btu firmware?
(Also yes, it was stupid of me to try and do it quick but i had rooted 3 different samsung galaxy phones in the past without issues, either i did something wrong or it took something way too specific to do the job, perhaps the phone's unrootable, but thank you either way) :fingers-crossed:
Click to expand...
Click to collapse
You'll likely only find the last version of BTU think it was August 2019. It isn't updated officially anymore but it'll be fine to use.

cooltt said:
You'll likely only find the last version of BTU think it was August 2019. It isn't updated officially anymore but it'll be fine to use.
Click to expand...
Click to collapse
I've found android 6 to android 8 with all the monthly updates, im just trying the latest of the latest though i dont remember my android version, ill try android 7 and 6 if that doesn't work, thanks again. I'll make sure to reply if this works or doesn't.

cooltt said:
Yep you've now learned the hard way not to mess about and read the proper guides.
Anyway "dbt" is just unbranded german firmware. Download UK "BTU" and flash with Odin, it's UK unbranded.
FRP lock means you'll need to unlock the phone with the google account and password that was on it before you started messing about with it.
If you don't know the google email and password you need to read up on how to bypass FRP lock and it's a nightmare.
Click to expand...
Click to collapse
OK so i thought it worked but i can only enter recovery mode now and download mode, but cant actually boot the system, it just boots up the battery screen whenever i plug the charger, and never shows the actual battery info, just the thunder icon. Formatting from recovery mode doesn't help either (Note whenever i launch recovery mode it says installing update, then says no command and brings me to the recovery menu) Any ideas?
PS: It fixed itself. Sorry for the pointless edit.