Hi All,
Have s6 SM-G920F international model. now my brother accidentally try wrong attempts in pin to unlock the phone. so phone got locked. and i give to guy who unlock the phone and after that i am not able to get official update . so have decided to install official stock firmware. details are below. when phone is return back to me have below version.
Old firmware :-
G920FXXU1AOCY 5.0.2 Lollipop, Initial release on 3/29/2015 for EE only.
New firmware which i try using ODIN :-
G920FXXU3QOJF Galaxy S6 SM-G920F 5.1.1 Stock Firmware -- This firmware is officially released on November 2015 for EE UK Galaxy S6 alone.Build date: October 12, 2015.
Got success in above firmware , PASS is result in ODIN.
But when phone reboot after this ,after erasing screen appear then it hang on logo screen. have waited around 20 mins but nothing happen. Have tried recovery mode also via wipe cache / factory reset , no change in result.
Have again try to install G920FXXU1AOCY but got sof rev fail in ODIN .
Have tried samsung switch for software update it's successful but when phone reboot it again stop there at logo screen.
In recovery mode -- G920FXXU3QOJF this show on top.
I don't whether phone was root or not as guy says he just unlock the phone. got this from UK .
Can anyone please help which firmware will now work on this case ? how to solve this issue.
Please help me as i mess up with my phone which work great before .
Tons of thanks to all.
Is there any firmware which work on all unlock or root phone for this model ? the above step from 5.0.2 have installed 5.1 is correct step ? i am working this phone from india,before doing this firmware update my sim card work properly. as phone was already unlock or rooted (not sure here whether it's rooted or not but sure as it's unlocked phone) as i can see EE apps in phone. please help me . it's hurt me on my decision to do this upgrade and create mess. :crying:
Can anyone pls help.. Thanks
dbarot87 said:
Can anyone pls help.. Thanks
Click to expand...
Click to collapse
have you solved this yet?
this helped me:
http://forum.xda-developers.com/gal...d-development/kernel-stockmod-kernel-t3100395
Related
Hello everybody,
I usually find my answers in the specific phone related forums. But this time I'm stuck.
A friend of mine bought a Samsung Galaxy J7 (SM-J700F to be specific) in India. After using his phone there he came back home to Israel.
His phone didn't worked here for some reason and he went to a phone lab which flashed his ROM to stock Israel ROM.
They called him in the middle of the process and asked him what was his Google account thet he signed to while the first setup. Unfortunately, he cant remember his email address.
I took the phone to try bypassing the frp lock.
After a small search I realized I need an otg cable, which I bought.
I received the cable (1.5 mounths wait) and tried the otg cable method with no success.
After some experiments I successfully managed to open the settings menu. Pressed factory data reset and after a restart it stopped on recovery menu with the yellow message "dm-verity verification failed".
Well, this is annoying. I realized I need to flash the stock ROM again(Dated 01/16). So I did And the message dissapperd.
Back to the FRP lock issue. I did the process again and it didn't stopped in the recovery mode this time and I could see the Android logo with a little erasing.. Under it. Finally I thought.
I was wrong.
The FRP lock is still there! Dammit.
It is time to pull the big guns.
I thought I will flash the OLDER version of the stock ROM. Dated 09/2015 I Understand google updated the FRP lock protection on January 2016. Is the downgrade OK? I don't know if a downgrade is possible on Samsung phone.
And if you have an idea how to bypass this. Please share it.
Thank you so much!
Hello epopcop
I try so hard for three days like ure problem
The issue not from odin or pc
Th problem from samsung you cannot downgrade any update
So maybe u use software sysgem update and install it on ure device
So you cannot use any old firmware
(You shloud last updated firmware)
Link
Sorry just search in androidfilehost make a search for j700f and download the 2016 firmware
I cannot post links sorry
Use it and live ure life happy
Wishes
Hello, I have a soft bricked (hopefully thats the case) Samsung Galaxy S6 SM-G920F xme region (Malaysia) with android 6.0.1 latest stock rom.
It started when my device suddenly restarted and got stuck at the samsung logo (first screen).
I am able to boot it into Download Mode, tried reflashing with a fresh stock rom MM 6.0.1 with odin, flashing proccess was completed with no fail but it still stuck at the same screen.
I can't even boot into recovery mode so i can't wipe the cache partition, i noticed the Reactivaction Lock status is ON, i suspect that might be the culprit?
The things i tried so far:
1- Reflash with the latest stock firmware. Ticking the NAND erase all and repartition it with pit file also didn't work.
2- Samsung Smart Switch and Kies3. Flash completed but no effect.
3- Flashing any recovery files returns with "Custom binary(recovery) Blocked by R/L".
4- Sent it to my nearest Samsung service centre, they did try to repair it but only to be told that my S6 need a new motherboard the next day, which is out of my budget limit. But i am still hoping to find some other way to fix it, i believe this is just a "soft-brick" not a hard brick device.
Ideas guys? thanks.
Try to re flash stock odin firmware with erase all ticked ok ,
Good luck ,,
thereassaad said:
Try to re flash stock odin firmware with erase all ticked ok ,
Good luck ,,
Click to expand...
Click to collapse
Already tried that, still no luck..
mrkage said:
Hello, I have a soft bricked (hopefully thats the case) Samsung Galaxy S6 SM-G920F xme region (Malaysia) with android 6.0.1 latest stock rom.
It started when my device suddenly restarted and got stuck at the samsung logo (first screen).
I am able to boot it into Download Mode, tried reflashing with a fresh stock rom MM 6.0.1 with odin, flashing proccess was completed with no fail but it still stuck at the same screen.
I can't even boot into recovery mode so i can't wipe the cache partition, i noticed the Reactivaction Lock status is ON, i suspect that might be the culprit?
Ideas guys? thanks.
Click to expand...
Click to collapse
Try Samsung Smart Switch, it has some recovery features that can automate the process for you.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Try Samsung Smart Switch, it has some recovery features that can automate the process for you.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Thank you for taking a look at my problem here, i forgot to mention that i did try Samsung Smart Switch and Kies3, both managed to succesfully flashed the stock firmware, it reboots my device and still stuck at the same first screen.
mrkage said:
Thank you for taking a look at my problem here, i forgot to mention that i did try Samsung Smart Switch and Kies3, both managed to succesfully flashed the stock firmware, it reboots my device and still stuck at the same first screen.
Click to expand...
Click to collapse
I believe it is doing that because you have a locked bootloader. Normally that shouldn't be a problem unless you're trying to flash a firmware that is older than what you had.
What stock firmware version/build number did your device have? What firmware version/build number is what you are flashing? If what you're flashing is older it might be downgrading your bootloader, bootloader can't be downgraded on most locked bootloader Samsung devices these days.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
I believe it is doing that because you have a locked bootloader. Normally that shouldn't be a problem unless you're trying to flash a firmware that is older than what you had.
What stock firmware version/build number did your device have? What firmware version/build number is what you are flashing? If what you're flashing is older it might be downgrading your bootloader, bootloader can't be downgraded on most locked bootloader Samsung devices these days.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Don't remember the build number, but it was a 6.0.1 firmware, i flashed it with the same stock firmware version.. but maybe the build number didn't match.
I read somewhere about the engineering bootloader, i know it is not so easy or even possible at the moment to find one for my current firmware version, but let's say if i have it, will it be possible for me to use it to remove the RL on my device?
mrkage said:
Don't remember the build number, but it was a 6.0.1 firmware, i flashed it with the same stock firmware version.. but maybe the build number didn't match.
I read somewhere about the engineering bootloader, i know it is not so easy or even possible at the moment to find one for my current firmware version, but let's say if i have it, will it be possible for me to use it to remove the RL on my device?
Click to expand...
Click to collapse
Did you flash a firmware from a different g920 series device? Or did you flash the firmware for your specific model number and your and carrier?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Did you flash a firmware from a different g920 series device? Or did you flash the firmware for your specific model number and your and carrier?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Only did for my specific model number and carrier
mrkage said:
Only did for my specific model number and carrier
Click to expand...
Click to collapse
Let me backtrack. Do you know if USB debugging is on?
Did you flash TWRP with a locked bootloader before this happened? Is that what caused the issue?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Let me backtrack. Do you know if USB debugging is on?
Did you flash TWRP with a locked bootloader before this happened? Is that what caused the issue?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
USB debugging and Developer Mode was never turned on that device.
Negative, i did try flashing TWRP but it was after it got stuck at the logo screen and only able to boot into Download Mode, the flashing came back failed with "Custom Binary (recovery) Blocked by RL" message.
Flashing it with the latest stock recovery i found online also gave me the same error message.
mrkage said:
USB debugging and Developer Mode was never turned on that device.
Negative, i did try flashing TWRP but it was after it got stuck at the logo screen and only able to boot into Download Mode, the flashing came back failed with "Custom Binary (recovery) Blocked by RL" message.
Flashing it with the latest stock recovery i found online also gave me the same error message.
Click to expand...
Click to collapse
Just out of curiosity, have you tried booting to safe mode? If any of the apps that you installed before this happened were causing an issue or bootloop before you flashed are still there, it/they could still be causing the bootloop. Remember, I said that it doesn't wipe data unless you are upgrading or downgrading bootloader/baseband, what you flashed wasn't an upgrade or a downgrade so your data is there. Boot to safe mode and disable/uninstall the apps that might be causing the issue.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Just out of curiosity, have you tried booting to safe mode? If any of the apps that you installed before this happened were causing an issue or bootloop before you flashed are still there, it/they could still be causing the bootloop. Remember, I said that it doesn't wipe data unless you are upgrading or downgrading bootloader/baseband, what you flashed wasn't an upgrade or a downgrade so your data is there. Boot to safe mode and disable/uninstall the apps that might be causing the issue.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Didn't try that... but nevermind. I accidentally damaged my screen while trying to dissasemble it last night, a very stupid mistake from me.
Thank you for trying to help me mate. Forum mods can close this thread now. Thanks all.
problem
i have too but with A/L
hi,i update my galaxy edge g925p from 6.0.1 stock to nougat 7.0 custom successfully,it work almost 10 days after that it restarting then i try to downgrade via odin to 6.0.1 stock,odin error sw version fail,then i download nougat 7.0 sprint firmwares from diffrent site and flash via odin successfully but problem remain the same restarting logo,then i found a firmware sprint nougat with 4 files (BL,AP,CP,CSC,)G925PVPU4DQC7,
after flash this firmware via odin mobile starts successfully on setup options,then i try to click to setup,only check 2 or 3 options like country select,wifi,then phone restarts again,
i can go into stock recovery still,
recovery status shown
odin mode
product name:samsung official
current binary:custom
system status:custom
frp lockff
secure download:enabled
plz help me to fix it,thanks.
waiting still help,,,,,,,,,
i have the sam froblum did u solve this problum ar not
Im on the same boat
If anyone can provide solutions
any solution for this?
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
DM verity failed
Frp locked
Bricked
Unlocked bootloader.
Odin different errors! If everything goes fine it stucks at something for minutes /hours then give fail message!
Smart switch is useless
Adb sideload /fastboot , the only commands that responds is the one used to get connected devices. When I try to flash there it reboot to recovery instantly.
Recovery is damaged or blocked!!
I cannot instal TWRP because the phone is locked.
I can flash only a stock firmware for my region . Is region matter? (no need to unlock??)
Please browse the pictures . Everything is portrayed. Simply I cannot flash! My mother's device. Not only me. But also the technicians!
Reflash phone's Stock ROM to get rid off of all modifications you applied so far.
[RESOLVED]Thank you.
The issue :I used frija to give me the last firmware for my region and the firmware was downgraded , B:4 .it is the last for my region , security level 4 . While the frimware I need to replace , is B6 ,its SWREV is B6 ,K1 S2. So level 6. I tried low level B for 10 days it is why I got Fail messages all the time. But did not give up. I'm a newbie thou. Learned many things in this processe .I used all possible tricks trying to solve the issue.
I thought it is obligatory to flash a firmware from same region if the bootloader is locked , and FRP is locked. I read it from a blog but no! The value of B , stands for security level and bootloader matters. Also the phone version SM-J710F matters ,That 's it. If you flashed ROM with higher B , and failed then adjust the technical stuffs, USB , ports and so on . Or try a Combination frimware create one or get it from the net , use pit files too...goodluck . Dear reader