Question Has anyone had any luck flashing unlocked firmware to this phone? - Samsung Galaxy A12

I have the T-Mobile variant (TMB firmware, A125U) and I would like to flash unlocked firmware (XAA, A125U1), but when I tried it failed. I tried flashing a combination file first but all the tutorials I was following were old and I had no success there either. I'm using the latest version of Odin and a good USB cable. Just the other day, I was able to flash TMB firmware without an issue, now I'm getting the Complete(Write) operation failed error. Anyone know what I'm doing wrong?

eddieofny said:
I have the T-Mobile variant (TMB firmware, A125U) and I would like to flash unlocked firmware (XAA, A125U1), but when I tried it failed. I tried flashing a combination file first but all the tutorials I was following were old and I had no success there either. I'm using the latest version of Odin and a good USB cable. Just the other day, I was able to flash TMB firmware without an issue, now I'm getting the Complete(Write) operation failed error. Anyone know what I'm doing wrong?
Click to expand...
Click to collapse
Try with patched odin, not normal odin.

TheWorldYT said:
Try with patched odin, not normal odin.
Click to expand...
Click to collapse
That's what I've been using. Odin will throw a generic "failed to partition" error, but on my phone display, I'll get an error about not being allowed to flash different software than what's already on the phone. I did some more research and came to the conclusion that I need to get the phone to change it's KG Status. It was stuck on Prenormal until I blocked Knox's connection to the internet with a firewall, at which point the KG Status changed to Checking. Still can't flash firmware though. The last thing I could think to try is to leave the phone on for 7 days and hope the KG Status will change again and show me the option for OEM Unlocking, which currently missing completely from my Developer Options. If there are any other solutions, I'd be happy to give them a try.

eddieofny said:
That's what I've been using. Odin will throw a generic "failed to partition" error, but on my phone display, I'll get an error about not being allowed to flash different software than what's already on the phone. I did some more research and came to the conclusion that I need to get the phone to change it's KG Status. It was stuck on Prenormal until I blocked Knox's connection to the internet with a firewall, at which point the KG Status changed to Checking. Still can't flash firmware though. The last thing I could think to try is to leave the phone on for 7 days and hope the KG Status will change again and show me the option for OEM Unlocking, which currently missing completely from my Developer Options. If there are any other solutions, I'd be happy to give them a try.
Click to expand...
Click to collapse
Oh, you have to use BROM, which involves opening up phone. You can search a tutorial how to do BROM mode in your phone.

eddieofny said:
That's what I've been using. Odin will throw a generic "failed to partition" error, but on my phone display, I'll get an error about not being allowed to flash different software than what's already on the phone. I did some more research and came to the conclusion that I need to get the phone to change it's KG Status. It was stuck on Prenormal until I blocked Knox's connection to the internet with a firewall, at which point the KG Status changed to Checking. Still can't flash firmware though. The last thing I could think to try is to leave the phone on for 7 days and hope the KG Status will change again and show me the option for OEM Unlocking, which currently missing completely from my Developer Options. If there are any other solutions, I'd be happy to give them a try.
Click to expand...
Click to collapse
If the bit version of your phone is 3, flash the earliest bit 3 U package files. Then after flash bit 3 U1 package.
When flashing the U package just leave off the user data file. Must be using patched modded odin.
If you are bit 4, then you will be out of luck for a while.
I only know this because I ran into this same issue and that is how I resolved it on bit 3.

Related

FRP Lock ON, Secure Download Enabled, No Serial Number, Custom Boot Lock -HELP!

I have experience rom'ng Samsung phones and have never run into something this bad. My S6 Edge SM-G925P will not flash any stock/non-stock rom. Tried OI1/OH/OJ/OF, all fail Nand Write. Some suggest, split ROM in pieces and install separately in ODIN, but do not explain what that means and how to do it. When USB (official samsung cable) plugged in, phone gives Smart Switch error. I am attaching screenshots as these say it all. Please, any 'good' advice on how to attempt fixing this and getting ANY Android OS version installed? Am at wits end with this. Also, I can't get the SN because the dog ate the box and it's not on the back of the phone, plus phone won't boot other than download mode.
I was finally able to successfully install a Stock ROM and when it rebooted it showed the Samsung & Sprint logos and started charging. Currently at 40% and will try to boot the device shortly. I wanted to share that what helped was to use this specific ODIN version found at http://www.galaxys6edgeupdate.com/odin3-v3-10-6-download/ and OJ7 rom. Note the image on the website shows Odin with SM-G920/G925 where other ODINs don't show this. Confirmed! The phone rebooted and is now working. As a matter of fact, much of the data on it was maintained. Now just need to unlock it!
What files did you use.. I am on CUstom Binary and Status and get a nand fail on sboot.sh with a SW REV CHECK FAIL DEVICE 4 BINARY 3
anonymoustl said:
What files did you use.. I am on CUstom Binary and Status and get a nand fail on sboot.sh with a SW REV CHECK FAIL DEVICE 4 BINARY 3
Click to expand...
Click to collapse
I am in the same boat as well ;(
yall still need help with frp lock? if so message me
Kennii said:
yall still need help with frp lock? if so message me
Click to expand...
Click to collapse
Kennii,
I am experiencing the issues mentioned above. Can't flash with any of the stock roms using odin for my SM-G925P neither can come up with a serial number that works with smart switch.
I found a serial number for SM-G925I and the smart switch software goes to the next step. Do you have any serial number that goes with SM-G925P?

Stuck at Powered by Android please help SM-N915G

My Fried gave this phone to me (SM-N915G) which is stuck at Powered by Android, and told me to fix it.
He said that when he update to MM from LP without KIES or Odin, the phone suddenly restarted and stuck there getting HOT
He had no experiece to repair it so he asked me to fix it.
So for 3 days lately, i have tried many ways to fix it but wihout any progress, as follow :
1. Flashing Official MM wby using Odin -> still stuck
2. Downgrading Flash Official LP using Odin -> still stuck
3. Installed TWRP, and flasing CFW Micky387_MM_V3.0 for 915F/FY/G (flashing Bootloader and modem as required) -> still stuck with set warranty bit : kernel
4. After Flashing Micky CFW and Failde, i try to flash Emotion Kernel -> still stuck with Kernel is Seandroid Enforcing
5. Redoing Flash Micky CFW with other CSC -> Still Stuck (even i tried with 915F and 915FY as in the aroma installer)
6. Never failed during flash procedure with Odin or TWRP, everything is smooth
7. When stuck, the device is getting Hot slowly but and when left as long as 15 minutes, the HH is getting HOT (TWRP read 72 degree at most)
**Update
8. Tried using Official SmartSwitch sucessfully but the result is still the same -> Still Stuck and getting hot as usual T.T
Last Download Mode status is :
Odin Mode (High Speed)
Product name: SM-N915G
Current Binary: Samsung Official
System Status: Official
Reactivation Lock: Off
Knox warranty void: 0x1 (2)
Quallcomm secureboot : Enable (CSB)
RP SWREV: S1, T1, R1, A1, P1
Secure Download: Enable
UDC START
I am now thinking, should i flash another Kernel or PIT or Bootloader? but i still cant decide what to do next to revive this Phone
Please help, any suggestion is greatly appreciated, thank you.
Please give some help, thank you.
Help Please anyone?
This is Hard Brick or Soft Brick?
Any suggestion or Opinion please
Thank you
wingz17 said:
Help Please anyone?
This is Hard Brick or Soft Brick?
Any suggestion or Opinion please
Thank you
Click to expand...
Click to collapse
Have you tried a reinstall using KIES?
The Radius Kid said:
Have you tried a reinstall using KIES?
Click to expand...
Click to collapse
Yes i have try to recover but not using KIES, but using smartswitch...
Is it diffrent by using KIES or SmartSwitch?
Thank you.
wingz17 said:
Yes i have try to recover but not using KIES, but using smartswitch...
Is it diffrent by using KIES or SmartSwitch?
Thank you.
Click to expand...
Click to collapse
I can tell you that Kies and NOT Kies 3 was what worked for me when I downloaded/installed Marshmallow from Samsung's website.
Figure that one out.
That was also using a 64 bit version of Windows 7 Pro.
The Radius Kid said:
I can tell you that Kies and NOT Kies 3 was what worked for me when I downloaded/installed Marshmallow from Samsung's website.
Figure that one out.
That was also using a 64 bit version of Windows 7 Pro.
Click to expand...
Click to collapse
Thank you for the suggestion,
I will try that one out and let you know.
wingz17 said:
Thank you for the suggestion,
I will try that one out and let you know.
Click to expand...
Click to collapse
The Radius Kid said:
I can tell you that Kies and NOT Kies 3 was what worked for me when I downloaded/installed Marshmallow from Samsung's website.
Figure that one out.
That was also using a 64 bit version of Windows 7 Pro.
Click to expand...
Click to collapse
Sorry For the long response, i have tried flasing using KIES but still stuck on the android, and no progress.
Right now i am run out of option, please help, thank you.
wingz17 said:
Sorry For the long response, i have tried flasing using KIES but still stuck on the android, and no progress.
Right now i am run out of option, please help, thank you.
Click to expand...
Click to collapse
I'm going to guess that you've tried installing MM using Kies directly from Sammobile?
If so,have you tried turning off your computer's antivirus when you download/install?
It sounds like the bootloader is looking for something and can't find it.....kind of like what happened to me when I totally ripped KNOX out of my phone.
Restore time!
Good thing I did CWM backups.
In your case,your computer's anti virus could be seeing something in the download and ripping it out.
I've seen my browsers do that when I download stuff....pain in the....
Have you tried a different battery?
Maybe a search of the forums to see if anyone else has had this problem and solved it?
I kind of remember seeing something like this a while back.
The Radius Kid said:
I'm going to guess that you've tried installing MM using Kies directly from Sammobile?
If so,have you tried turning off your computer's antivirus when you download/install?
It sounds like the bootloader is looking for something and can't find it.....kind of like what happened to me when I totally ripped KNOX out of my phone.
Restore time!
Good thing I did CWM backups.
In your case,your computer's anti virus could be seeing something in the download and ripping it out.
I've seen my browsers do that when I download stuff....pain in the....
Have you tried a different battery?
Maybe a search of the forums to see if anyone else has had this problem and solved it?
I kind of remember seeing something like this a while back.
Click to expand...
Click to collapse
Thank you for the response,
I was using KIES 2.64 that downloaded from Samsung website to fix the phone as your suggestion (tools->firmware upgrade and initialisation) but still fail to fix it.
Nope, the antivirus still active when KIES download the FW and Flash it into the phone, but it is new to me that antivirus will intercept ongoing dowloaded files, if so i think the antivirus will give some notification or warning about the content of the file that being downloaded and in my case, my antivirus is still cool and no notification whatsoever.
The bad thing is i do not have any cwm backup and since this is my friend phone and not mine, well... we dont have any backup for this phone.
Regarding the battery, i admit that i havent try other battery, since i dont see any connecton between it, in my opinion, the phone works well, the charging animation working, and no sign of weak battery... but i will try to do it if i can get some other battery
I have surfed many forums and websites, but almost 90% can be fixed with simple flashing from odin or just by clearing up cache and data from recovery.
Other that that, wither, no one respond to the problem, or just some discussion without conclusion, really frustrating.
I even go further to read about android booting sequence to identify whats wrong with the boot sequence, but still confused...
But i have some question if you would to answer :
1 . Stuck at Android logo, bootloader or kernel problem?
2 . Is it possible that one of the mainboard chip that have some part in booting process is malfunctioning? But if so, the phone will be dead bricked right?
3. How about the booting process is halted due some hardware failure? ex : some chip (other than chip that have part in booting process) is bad and so the bootloader init is halted
4. The Worst guess, is it possible that the phone is fake? (the serial number behind the baterry is accepted by kies though)
Thank you very much, you are the only one who still response to my problem. :good:
As it seems you use the wrong Bootlaoder. Is his phone N915P or N915G? When you flash N915G Bootloader to N915P, it will not boot but the bootloader will work correctly. Try to flash the N915P bootloader.
I have N915FY phone but did not know first if I had N915F or FY. I flashed the N915F bootloader version, which flashed successfully, but was not booting. Bootloader said that my phones model is N915F. After flashing the FY Bootloader version, it successfully booted to system.
Bordo_Bereli51 said:
As it seems you use the wrong Bootlaoder. Is his phone N915P or N915G? When you flash N915G Bootloader to N915P, it will not boot but the bootloader will work correctly. Try to flash the N915P bootloader.
I have N915FY phone but did not know first if I had N915F or FY. I flashed the N915F bootloader version, which flashed successfully, but was not booting. Bootloader said that my phones model is N915F. After flashing the FY Bootloader version, it successfully booted to system.
Click to expand...
Click to collapse
Thank you for the Response,
First, his phone is N915G (according to the box and the information in the battery compartment)
(Really sorry for the mistake i made at the thread title)
And regarding bootloader, that is also my concern at first, i think maybe i was flasing wrong region and bootloader, and so i search the way to find out the real version of the phone, but after trying many ways described on the net (by imei or serial number) , i still cannot found out the way.
But one instance when i try using KIES, and KIES asked for the version and serial number when device upgrade and initialisation, i entered the exact version and serial number that is found behind the phone in battery compartment. KIES immediately confirms that the version and serial number is valid, (i still wonder though, is KIES check it online at Samsung server or there are some serial number database embedded in the KIES) and continue to run trough the official fw download and installation by KIES but at the end still no success.
Is it possible that the version and serial number is wrong ? if so, how to determine the correct one?
and is it safe to try flasing another bootloader?
Thank you very much
Hello, there is no bootloader related to serial number or something. There are different bootloaders for different models and android version. When you flash MM-Version, you need to be sure that you use the right bootloader and baseband files for MM. If you flash different region-locked firmware/bootloader, it will not affect btw. not solve the boot-stuck problem.
http://samsung-updates.com/device/?id=SM-N915G Try to flash 6.0.1 firmware that is related to your region if you still want to try to flash different region-firmware.
Maybe download the XSA 6.0.1 Firmware with the pit file XSA http://gsm-firmware.com/index.php?a=browse&b=file-info&id=15892.
Then flash XSA 6.0.1 and TBLTE_SEA_XSA.pit together in odin. Under Odin 3 V3.12 ticke the re-partition at option-tab and select TBLTE_SEA_XSA.pit under pit-tab.
Bordo_Bereli51 said:
Hello, there is no bootloader related to serial number or something. There are different bootloaders for different models and android version. When you flash MM-Version, you need to be sure that you use the right bootloader and baseband files for MM. If you flash different region-locked firmware/bootloader, it will not affect btw. not solve the boot-stuck problem.
http://samsung-updates.com/device/?id=SM-N915G Try to flash 6.0.1 firmware that is related to your region if you still want to try to flash different region-firmware.
Maybe download the XSA 6.0.1 Firmware with the pit file XSA http://gsm-firmware.com/index.php?a=browse&b=file-info&id=15892.
Then flash XSA 6.0.1 and TBLTE_SEA_XSA.pit together in odin. Under Odin 3 V3.12 ticke the re-partition at option-tab and select TBLTE_SEA_XSA.pit under pit-tab.
Click to expand...
Click to collapse
Thanks for the reply!
Although there is no bootloader related to serial number, but if we put the serial number in KIES, it will identify what CSC and region, which can be use as a guide to choose the correct FW or let KIES do the Flashing according to the inputted serial number, and as long as the serial number is correct one, that is my opinion but please CMIIW.
When flashing MM, if i use the MM that has been downloaded, the bootloader and baseband is included in the MM image right? or shouuld i flash it separately?
i have tried your suggestion but with no sucess, i have dowloaded the PIT and the FW, flash it trough odin which was sucess, but still stuck.
I do not tick auto restart at Odin, so i manually restart the phone, but i encounter an event which at 20% installing system update (below the greed droid guy) the progress bar is vanished and replaced with erasing, and after that the phone stuck again at the same spot.
Do you have any idea why?
Thank you very much.
Just thinking, should i erase the NAND in ODIN?
If so, how to restore it?
I think that if i backup the NAND using custom recovery and restore it later, it just bring back the same problem, if the NAND causing all this.
Do anyone have some NAND backup that i could use? or any other suggestion?
Thank you
Can you boot to recovery? if yes, try to wipe data and cache.
If it still not working, try to backup your efs with a custom recovery (ex. TWRP), or better the entire System like data, system, boot, efs, modem and save it to your computer.
After saving the backup, try to flash the firmware with pit file while checked NAND erase all.
When its finished and your device boots up, you can flash back your custom recovery and recover only the efs-partition.
If its not working, then there is maybe problems with your eMMC. But be aware using nand erase all. It is the last riskfully option left after trying several things.
I have a backup of my resurrection rom. If you want it I can upload it.

S7 in system install bootloop (I have read and tried what I could find)

Hello, My Sprint S7 was frp locked and I wanted to sim unlock it. I downloaded odin v3.12. ADB does not see the phone. I flashed with a firmware file. It is now in a boot loop where it says system install. At one time it came up and said it failed and to use Smart Switch emergency repair. I downloaded smart switch and it says unsupported device. I can put the phone in download mode. I have searched and gotten firmware. Everything I try fails in odin. Is it bricked for good or is there a way to fix it? Are there reputable companies that can unbrick it for a small fee? This site is tough to navigate and everytime I search it seems I come up with another place. One had a link to download firmware to flash and fix bricked phone but when I tried to open it my antivirus said it was full of adware. The phone is SM-G930P running 7.0. I was going to flash to a universal one or at&t. I can try odin and screenshot the results if I need to. I am willing to try about anything. Thanks in advance for any help. I have another one (they came as a pair) it is not frp locked but is simlocked. Not blacklistedd but it does show an unpaid balance. I cannot get a hold of the person I bought them from. I know what to check now though. Lesson learned.
KeithSherley said:
Hello, My Sprint S7 was frp locked and I wanted to sim unlock it. I downloaded odin v3.12. ADB does not see the phone. I flashed with a firmware file. It is now in a boot loop where it says system install. At one time it came up and said it failed and to use Smart Switch emergency repair. I downloaded smart switch and it says unsupported device. I can put the phone in download mode. I have searched and gotten firmware. Everything I try fails in odin. Is it bricked for good or is there a way to fix it? Are there reputable companies that can unbrick it for a small fee? This site is tough to navigate and everytime I search it seems I come up with another place. One had a link to download firmware to flash and fix bricked phone but when I tried to open it my antivirus said it was full of adware. The phone is SM-G930P running 7.0. I was going to flash to a universal one or at&t. I can try odin and screenshot the results if I need to. I am willing to try about anything. Thanks in advance for any help. I have another one (they came as a pair) it is not frp locked but is simlocked. Not blacklistedd but it does show an unpaid balance. I cannot get a hold of the person I bought them from. I know what to check now though. Lesson learned.
Click to expand...
Click to collapse
If its stopping on sboot.bin install samfirm and download latest firmware then flash again
kpwnApps said:
If its stopping on sboot.bin install samfirm and download latest firmware then flash again
Click to expand...
Click to collapse
Hey. Thanks for responding. I downloaded samfirm. It says device not supported. I have been searching around to make sure I try to flash the correct software. At this point I am not as concerned about sim unlocking as just getting it to boot up again. Is it possible I tried to go further back and an older bootloader bricked it? Thanks
KeithSherley said:
Hey. Thanks for responding. I downloaded samfirm. It says device not supported. I have been searching around to make sure I try to flash the correct software. At this point I am not as concerned about sim unlocking as just getting it to boot up again. Is it possible I tried to go further back and an older bootloader bricked it? Thanks
Click to expand...
Click to collapse
Install firmware from updato.com and try again
kpwnApps said:
Install firmware from updato.com and try again
Click to expand...
Click to collapse
Hey. I have been trying to download from updato. I guess the free download is not very good. It says 2 days and keeps disconnecting. Fianlly aborted when about halfway through. I have found another site to give a shot. Maybe I just did not have the correct file the first time. Thanks for checking in. I appreciate any input or ideas.
Btw, the other s7 I have is working. It is sim locked from Sprint. It is not listed as stolen or lost. To flash to Sprint would I just use the latest download? Thanks
KeithSherley said:
Hey. I have been trying to download from updato. I guess the free download is not very good. It says 2 days and keeps disconnecting. Fianlly aborted when about halfway through. I have found another site to give a shot. Maybe I just did not have the correct file the first time. Thanks for checking in. I appreciate any input or ideas.
Btw, the other s7 I have is working. It is sim locked from Sprint. It is not listed as stolen or lost. To flash to Sprint would I just use the latest download? Thanks
Click to expand...
Click to collapse
The saga continues. I did download stock firmware. It still failed when trying to flash with Odin. I can get it to load the recovery menu and the download menu now. Before the recovery menu would not load. on the log the last two things say
xbl.elf
FAIL! (Auth)
I tried Kies and Switch, neither support the device. I am currently downloading a stock rom from SamFirm, once I figured out the exact way to type on model and region code. I will try that in a little while and search for odin auth fials for the s7.
Thanks again for the help. I have learned quite a bit and it is fascinating. Any thoughts on the fail would be greatly appreciated. I hope after I get the stock rom back I can find the correct process to unlock it.

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.

Someone HELP!!!

Hi all,
I'm having a nightmare of a time with my Galaxy S7... For some unknown reason I decided to root my phone about 2 months ago using CF Auto Root.. worked great.. This morning, was having bad lag issues, so I restarted the phone.. as soon as the Samsung logo came up, I got a red message at the top of the screen saying "Custom Binary locked by FRP".. kind of freaked out and booted the phone into Recovery mode.. wiped Cache and wiped phone (to go back to factory setting I guess).. restarted... since then, I had no boot.. it did loop for a while as I was trying to charge the phone.. but that's it.
Now, the only way the phone will power on is if I plug it into my computer in Download Mode. I am trying to flash the ROM, custom or stock, but Odin fails almost as soon as it starts the sboot.bin and the phone screen shows "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 6, BINARY: 1".. Also, When I try to power on the phone, it HAS to be plugged in to my computer or charger cable and it just loops with a message at the top of the screen.
I can't do anything with this phone and cant find any solutions online... please help! :crying:
PM me for images of all screens please
I had the some problem while playing with my handset I switched off OEM unlock for some reason under developer option..
Next time i reset my handset it stuck on that warning
You need to download combination file, flash it with odin, then unlock developer mode, toggle OEM unlock, than flash back your current firmware, or if you have full twrp back up restore it
JayMor81 said:
Hi all,
I'm having a nightmare of a time with my Galaxy S7... For some unknown reason I decided to root my phone about 2 months ago using CF Auto Root.. worked great.. This morning, was having bad lag issues, so I restarted the phone.. as soon as the Samsung logo came up, I got a red message at the top of the screen saying "Custom Binary locked by FRP".. kind of freaked out and booted the phone into Recovery mode.. wiped Cache and wiped phone (to go back to factory setting I guess).. restarted... since then, I had no boot.. it did loop for a while as I was trying to charge the phone.. but that's it.
Now, the only way the phone will power on is if I plug it into my computer in Download Mode. I am trying to flash the ROM, custom or stock, but Odin fails almost as soon as it starts the sboot.bin and the phone screen shows "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 6, BINARY: 1".. Also, When I try to power on the phone, it HAS to be plugged in to my computer or charger cable and it just loops with a message at the top of the screen.
I can't do anything with this phone and cant find any solutions online... please help! :crying:
PM me for images of all screens please
Click to expand...
Click to collapse
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
cooltt said:
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
Click to expand...
Click to collapse
Dammit.. I tried to put as much detail as possible in there lol.. obviously I forgot some.. My mistake the Galaxy s7 that I am using is a Rogers Mobile (Canada) SM-G930W8. As for not signing out before modification, omfg, that makes perfect sense.. didn't even think of doing that before rooting.. I appreciate the help!! I will give this a go and see what outcome I get.. Thanks!
[/COLOR]That was nice of you to respond so helpfully, despite you having seen the scenario posted over and over.
cooltt said:
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
Click to expand...
Click to collapse
Can't make or receive calls
Please I need help my I rooted my S7 (flat) flashed the original OS with odin Installed Twrp flashed Andriod 9 and since then I can't make or receive calls wifi seems fine. Someone please come to my rescue:crying:
Cesilina said:
Please I need help my I rooted my S7 (flat) flashed the original OS with odin Installed Twrp flashed Andriod 9 and since then I can't make or receive calls wifi seems fine. Someone please come to my rescue:crying:
Click to expand...
Click to collapse
The S7 didn't receive Android 9 so the ROM is a custom one. Any issues with custom ROM's should be asked on the ROM thread itself where you got the ROM from. It's quite normal for custom ROM'S to have bugs.
You can try flashing the ROM (Android 9 Pie) again to see if it works. If not there are several different A9 ROM's to choose from.
cooltt said:
The S7 didn't receive Android 9 so the ROM is a custom one. Any issues with custom ROM's should be asked on the ROM thread itself where you got the ROM from. It's quite normal for custom ROM'S to have bugs.
You can try flashing the ROM (Android 9 Pie) again to see if it works. If not there are several different A9 ROM's to choose from.
Click to expand...
Click to collapse
Thank you for reply. I have tried atleast 4 different custom ROMs but to avail
Cesilina said:
Thank you for reply. I have tried atleast 4 different custom ROMs but to avail
Click to expand...
Click to collapse
Do you still have an imei number listed in settings?
Can't make or receive calls
cooltt said:
Do you still have an imei number listed in settings?
Click to expand...
Click to collapse
Yes please I still have an IMEI number

Categories

Resources