Hi, so I've nearly given up on doing this, but I've done it before, so I should be able to do it again.
I accidentally upgraded to android 8.0 on my Samsung J5-G570M (J5 Prime - Oi - Brazil) phone, so I would like to go back to 7.0/7.1 or even 6.0. I used Odin last time, and it worked after a few tries, but this time it won't go through. I keep getting the FAIL message on my screen.
This is what I get:
ID:0/006> 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/006> Odin engine v(ID:3.1303)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 3508 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Right now, I just reset the device so I got OEM locked , but the message that I've been getting is still the same. I've downloaded all the correct firmware versions for 7.0 and 6.0 for my device, but none of them seem to work!
Could someone point me towards the right direction?
What I do know is wrong is that this shows up on my phone when I try to flash the old FW:
Kernel Rev. Check FAIL Device:4 Binary:1
So I'm assuming I need to find a FW with another Binary? The Binary changes to 0 sometimes, and if I try to flash AP/BL/CP/CSC as well, it shows "device: 6 Binary: 3" It took me about 4 hours to download each firmware, but I downloaded 4 of them from Sammobile and 2 from updato.
I'm not sure if this is the correct place to ask this question, but please help me. I really want to go back to the previous version!
Also, USB debugging was also on.
I've already reset the device, so I have no issues losing my data. I just want to go back to the previous version of android!
Thank you,
Leo
Related
when I boot it just gives me some kernel is not seandroid enforcing so i'm trying to flash a stock firmware. G900P_SPR_G900PVPU3BOG1_G900PSPT3BOG1_Original.zip. is the name of file and its for a sprint S5.
Here is the odin output
<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/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
HELP ME please.
I can flash the backup although it gets stuck at yellow boot screen. but that does get rid of the seaandroid enforcing
If someone could help me as well I'm having a similar problem. I have tried using multiple Odin versions and many stock SM-G900P 4.4.2 firmwares from multiple sources, but always have the same messages pop up.
Odin:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_SPT_G900PVPU1BOA6_G900PSPT1BOA6_CL3859396_QB3804569_REV00_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<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)
USB debugging is on and Odin does recognize the device is connect, I have also already installed the drivers again just to be sure. I have used Odin before with no trouble maybe its the fact the phone is from sprint and on lollipop since sprint is stingy on unlocking -_-. If someone could point me in the right direction or 100% working firmware links I'd appreciate it. I have also tried going about this through Heimdall and failed not even being able to obtain the pit file. If someone could provide a working one I'd also appreciate it I am fully aware it may brick the phone as everything else may do. Or show me the me the step by step to flash with Heimdall with a .tar. I'll take any advice thank you
you can try the newer firmware ok4
maybe this will work . unzip and place md5 in ap slot of odin
http://forum.xda-developers.com/spr...t/rom-sprint-ok4-stock-tar-file-odin-t3262667
Sprint new locked bootloaders
unteaglejohnk said:
when I boot it just gives me some kernel is not seandroid enforcing so i'm trying to flash a stock firmware. G900P_SPR_G900PVPU3BOG1_G900PSPT3BOG1_Original.zip. is the name of file and its for a sprint S5.
Here is the odin output
<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/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
HELP ME please.
Click to expand...
Click to collapse
I have the same problem myself and it took me a few minutes to realize what the problem is. I just got a new phone from Sprint because my other one the USB port was basically broken I couldn't connect or charge. So after a few failed attempts at flashing a ROM I decided to look at my firmware and realized that it was the new updated bog1 version. Sprint decided to lock all the boot loaders so as of this moment I don't know how to flash any ROM or downgrade as the bootloader will not let you. As a matter of fact just last night I was walking into Walmart I pulled my phone out of my pocket to look at it and it was just finishing up installing some security policy updates. My phone then immediately restarted and got stuck at the spark screen. Just the fact that I was rooted sent my phone into a boot loop. As of right now the only thing I can do is reflash the stock bog 1. I have managed to get access to this one and I'm working on modifying the bootloader in anyway I can. I'm a little newer to this but I catch on pretty quick. As of now I have all the permissions unlocked for me to access all the files in that stock bog1 rom but haven't found a way to make them stick yet. I'm going to have to break down each individual file and hopefully I can come up with a solution or anybody for that matter because I'm a few months away from my contract being up and if I can't root my phone and customize it I don't want it. If they want my phone lock down and toddler mode then they can pay for it that's how I look at it lol. Make sure you turn off automatic security updates. There's also a post in here of how to clean that out so you don't have the newest security policy update. I know the exact file the bootloader is in but haven't found a way to get into it or modify it yet even though I have permission. It shows it copying /deleting but doesnt change. There is way too many people in this world to not have someone come up with a solution by now and anytime I search for it I get results from a year to five years ago , hardly anything recent thanks google. I also posted on times and started a thread I'm trying but I'm not as advanced as some of these developers on here but I am determined lol
I finally got it to boot up. Just took like 20 mins. Now it boots sometimes while others it won't and says process has stopped responding after the yellow screen. Why does it do this. The rom is official rom directly off Samsung kids.
may have cracked bootloader BOG1 G900P
i have been playing in thr sys files and today i managed to get a custom animation boot installed. after that i flashed a modded bog1 file from philz. it took and succesfully booted and am now reinstalling all my apps. i think i over wrote or blocked my bootloader. ill get back when i know for sure:laugh:
http://samsung-updates.com/device/?id=SM-G900P
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/
I'm having trouble with flashing the stock rom for the Samsung Galaxy S3 on Odin, as I get a fail everytime I try to flash the rom onto my device.
This comes up everytime I try to flash:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGOK1_I9300NZCGOK1_I9300XXUGOK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The model number is a GT-i9300, and no stock roms so far have succeeded.
I have used Odin 3.07 and Odin 3.09, my samsung drivers are up to date and Odin still fails to flash the rom.
On the S3 it's currently running TWRP version 3.0.2-1, it also asks me whether or not I keep it "System Read only" whenever I go in recovery mode. And each time I always choose the option of keeping it read only. I don't know if these has anything to do with Odin failing to flash the rom but might as well mention it. I was also running CyanogenMod13 for roughly a month before the brick happened.
Any help would be appreciated !
Hello
Thank you for using XDA Assist.
Please use the below link to register a XDA Account first, prior to start posting and replying onto our forums.
Join the Experts
When you complete your registration, I invite you to post over your request in the below forum as our team of experts there should be able to help you:
Galaxy S III Q&A, Help & Troubleshooting
Best regards and good luck.
.
XDA Visitor said:
I'm having trouble with flashing the stock rom for the Samsung Galaxy S3 on Odin, as I get a fail everytime I try to flash the rom onto my device.
This comes up everytime I try to flash:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGOK1_I9300NZCGOK1_I9300XXUGOK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The model number is a GT-i9300, and no stock roms so far have succeeded.
I have used Odin 3.07 and Odin 3.09, my samsung drivers are up to date and Odin still fails to flash the rom.
On the S3 it's currently running TWRP version 3.0.2-1, it also asks me whether or not I keep it "System Read only" whenever I go in recovery mode. And each time I always choose the option of keeping it read only. I don't know if these has anything to do with Odin failing to flash the rom but might as well mention it. I was also running CyanogenMod13 for roughly a month before the brick happened.
Any help would be appreciated !
Click to expand...
Click to collapse
Hi there,
I have a G930W8 (Canadian S7) that I am trying to flash a stock 7.0 ODIN file to, I have used ODIN several times without issue... but this time it doesn't seem to be working.
I downloaded the latest 7.0 from Sammobile, and put the respective files (BL/AP/CP/CSC) in their boxes, but everytime I try I get a FAIL message, and it seems to be only the BL that's causing it:
<ID:0/006> 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/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> param.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My device reads SW REV. CHECK FAIL. DEVICE: 3, BINARY: 2
The other files seem to work but when I reboot without flashing the BL I keep getting force closes.... I tried downloading the latest file twice to make sure it's not corrupted but it keeps happening, any ideas what it might be?
You're not trying to downgrade are you? I'm not 100% if it carried over into Oreo, but the last bootloader in 7.0 locked it from downgrading.
Beanvee7 said:
You're not trying to downgrade are you? I'm not 100% if it carried over into Oreo, but the last bootloader in 7.0 locked it from downgrading.
Click to expand...
Click to collapse
No I am not; but it appears I wasn't using the latest available version of 7.0, tried downloading from another source and it worked now, thanks.
Cryceratops said:
No I am not; but it appears I wasn't using the latest available version of 7.0, tried downloading from another source and it worked now, thanks.
Click to expand...
Click to collapse
thank you very much
Hello,
I recently tried to install a ROM on a Samsung galaxy s6 (SM-G920F) while following a guide. The guide said to reset to factory settings and to wipe the cache, which i did.
The custom ROM i tried to install didn't work, and now i have an error message when trying to turn the phone on. It says "An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software"
I tried to flash stock firmware onto the phone that i downloaded from sammobile.com, but this doesn't seem to work.
I select the .tar.md5 file with the AP button in Odin3 v3.13 and hit Start once it allows me. It fails near the end, this is in the log:
<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/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 3740 M
<ID:0/006> SetupConnection..
<ID:0/006> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
I also tried to install this Smart Switch PC software, but cannot find it anywhere. EDIT: Found it now, but couldn't install it. Translated the message says: Application cannot be started because the configuration next to each other is wrong.
Can anyone please tell me what i'm doing wrong? I really need to get the phone back in working order.
EDIT: It was getting much further through the flash when i tried it yesterday, looked like it was about 90% done before it failed. Now it doesn't even properly start. The Odin log i posted is one from today.
EDIT2: The information at the top of the download screen is as follows:
odin mode
product name: sm-g920f
current binary: Samsung Official
system status: official
reactivation lock: off
secure download: enabled
knox warranty void: 0 (0x0000)
rp swrev: B:6 K:2 S:2
SW REV. Check fail. Device: 6. Binary: 4
EDIT3: tried to run a flash again, it failed at the same point it did yesterday. the log:
<ID:0/006> 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/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 3712 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> cm.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Managed to fix my issue through following the steps on this post:
https://forum.xda-developers.com/showpost.php?p=66418660&postcount=25