I have a friend's phone a SAMSUNG S6 (SM-G920P) that won't boot, because he took it to some phone repair shops that have messed it more than it already is. I have this on the boot screen :
Code:
Kernel is not seandroid enfrocing.
Custom binary is blocked by FRP lock.
The first thing I've done is download a stock rom : G920PVPU1AOCF_G920PSPT1AOCF_G920PVPU1AOCF_HOME.tar.md5 and I tried to flash it via ODIN3.10.6, but I keep getting a fail message :
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920PVPU1AOCF_G920PSPT1AOCF_G920PVPU1AOCF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And this on the phone :
Code:
SW REV. CHECK FAIL. DEVICE: 3, BINARY: 1
Then, after searching online for this problem, I found out that I've been using the wrong stock firmware. But there is no way for me to check the modem and bootloader version, I tried fastboot but it keeps waiting for the device. I tried SmartSwitch and Kies, then can't find my device, and when I try using the model number (SM-G920P) and the serial number which is the MEID I found in the download mode>Home button (only that with the barcode), I get that this S/N is invalid. I really don't know what to do next, and I wish that someone could help me.
Thanks a lot!
Downloaded last firmware and flashed it. All things working fine, thanks.
http://www.sammobile.com/firmwares/database/SM-G900P/
Related
Hi all,
I have Samsung Galaxy S6 G920F . I am trying to unroot my phone back to its factory settings. I downloaded the fimware and odin however i am getting below error message once i press the start in ODIN. I really dont have any idea what is going on. I tried different USB cables, frimware but didnt work out. Any help is highly appreciated . These are what i am getting ;
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1101)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> cm.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> G920FXXU1AODE_G920FOXE1AODE_G920FXXU1AODE_HOME.tar .md5 is valid.
is this version of firmware lower than the one curently instaled.
i had similar problem
it appears that is was on portugal firmware G920FXXS4DPG2_G920FOXX3DPD1_TPH (latest update of 109MB) and was trying to downgrade to G920FXXU3DPDP_G920FOXX3DPD1_TWO ,and was getting error ''cm sw rev check fail device 4 binary 3''
and smart switch failed because my it was trying TWO_CRO with lower verion.
hello
i have a problem , i can flash new costums roms , but i cant get back the stock with odin please help
in odin mode shows
--------------------------------------------
Odin mode
product name : SM-G900p
Current binary : custom
system status : custom
reactivation lock ( kk) : off
knox warranty void : 0x1 (4)
qualcomm secureboot : enable ( csb )
rp swrev : s1 ,t3 r1 a3 p1
secure download enable
udc start
----------------------------------------------------------
and after adding the stock rom in AP and clicking start it shows :
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900PVPU1ANCB_G900PSPT1ANCB_G900PVPU1ANCB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
------
And on my phone shows
SW REV CHECK FAIL :[aboot] Fused 3 > Binary 1
---
i have tried those ones :
G900PVPU1ANCB_G900PSPT1ANCB_SPR
and
G900P_NKD_FullRestore.tar
and it gives me the same error
imageshack.*****com/a/img923/5454/PmP1X7.jpg
imageshack.***com/a/img924/606/6WnxEU.jpg
imageshack.**com/a/img921/1732/nb7OIt.jpg
Please Delete the starts on the link
try OK4. That one seems to be the most bulletproof
Wipe everything in twrp then try to install a stock ROM. If that doesn't work try a different stock ROM
youdoofus said:
try OK4. That one seems to be the most bulletproof
Click to expand...
Click to collapse
thanks for you help, i will test it ^_^ and i will see if its work or no
i7vSa7vi7y said:
Wipe everything in twrp then try to install a stock ROM. If that doesn't work try a different stock ROM
Click to expand...
Click to collapse
i did :/ isnt working
yassinehari said:
thanks for you help, i will test it ^_^ and i will see if its work or no
i did :/ isnt working
Click to expand...
Click to collapse
tried a different cable and/or a different computer?
Reactivation lock is a note thing, not galaxy.
I believe. .
yassinehari said:
hello
i have a problem , i can flash new costums roms , but i cant get back the stock with odin please help
in odin mode shows
--------------------------------------------
Odin mode
product name : SM-G900p
Current binary : custom
system status : custom
reactivation lock ( kk) : off
knox warranty void : 0x1 (4)
qualcomm secureboot : enable ( csb )
rp swrev : s1 ,t3 r1 a3 p1
secure download enable
udc start
----------------------------------------------------------
and after adding the stock rom in AP and clicking start it shows :
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900PVPU1ANCB_G900PSPT1ANCB_G900PVPU1ANCB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
------
And on my phone shows
SW REV CHECK FAIL :[aboot] Fused 3 > Binary 1
---
i have tried those ones :
G900PVPU1ANCB_G900PSPT1ANCB_SPR
and
G900P_NKD_FullRestore.tar
and it gives me the same error
imageshack.*****com/a/img923/5454/PmP1X7.jpg
imageshack.***com/a/img924/606/6WnxEU.jpg
imageshack.**com/a/img921/1732/nb7OIt.jpg
Please Delete the starts on the link
Click to expand...
Click to collapse
Try using twrp 3.0.0. I've had the same problem before. Also use Odin 3.09. I never have a problem when using those two. Make sure you have USB debugging enabled in developers menu. Tap build in device info 7 times to activate developer options. Hope this helps. Also if your on lollipop you can't flash kit kat firmware. Try BOG1 or if you want MM use CPCA.
I have this problem i cant reflash it on odin. Ive already rooted the device because when i get this it has a deep sleep issue so i fix it. After i rooted and install twrp recovery it works fine. But after i accidentally rooted again. It stuck up to boot loop t mobile logo.
Now when im flashin it on odin it say fails en recovery mode says.
SW REV. CHECK FAIL. DEVICE: 4 BINARY 3
Here is the log file i get from odin when im flashing a stock firmware on odin
GT-N920T T-mobile
Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N920TUVU3DPG1_N920TTMB3DPG1_N920TUVU3DPG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> cm.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Somebody help me please? For this fix
I have a Galaxy s6 edge SM-G925P and it said Custom Binary Blocked By FRP Lock at boot logo. I have tried to flash the stock firmware but i keep on getting a failure.
I also get the message SW REV. Check Fail. Decive: 4, Binary: 3.
Please help.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Hi !
FRP lock occurs on Lollipop after rooting and disabling OEM unlock so don`t do it next time
Here is a thread that it may help
https://forum.xda-developers.com/tm...o-to-5-0-2-t3142946/post61531848#post61531848
Good luck !
Hey,
I was successfully running LineageOS on my GT-N8010.
However, it froze at one point and I force turned it off, and ever since I just get the 'Firmware upgrade encountered an issue' screen. However, I am still able to get into download mode.
I'm now wanting to get it back to stock so I can re-try LineageOS on it. I have the stock image but if I try to install through ODIN I just get an error(posted below) and also on the tablet I get SW Rev. Invalid magic string.
Any idea how I could try sort it out?
In the details section of the download screen it shows;
ODIN MODE
Product name: GT-N8010
Current Binary: Samsung official
System status: Custom
Log:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> tz.img
<ID:0/004> NAND Write Start!!
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Odin requires TAR files not image .
Flash stock rom via Odin .
Sboot.bin fail means you are flashing firmware with an older bootloader than is currently on the device .
JJEgan said:
Odin requires TAR files not image .
Flash stock rom via Odin .
Sboot.bin fail means you are flashing firmware with an older bootloader than is currently on the device .
Click to expand...
Click to collapse
Edit:
Looks like I didn't have the latest version, tried a newer one but it now gets stucks and after about 5mins of trying it stops at system.img;
Logs:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 1746 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> tz.img
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Stuck on system.img means odin not recognized your system partition..
And or change USB port change usb cable .
Make sure that you have the least official firmware for your device and if it still fails,
it looks like a eMMC failure.
This problem is very common on the N80XX devices.
I already had to replace hundreds of eMMC's on them.