I tried to root my sm-n900 note 3 and followed all the instructions to the letter on the forum and when I tried to root through odin, it says writing cache.img and I wait for a few minutes then it says FAIL, I unplugged then restarted my phone and it says "FIRMWARE UPGRADE ENCOUNTERED AN ISSUE, PLEASE SELECT RECOVERY MODE IN KIES AND TRY AGAIN" and now kies doesnt recognize my device anymore, So what can I do now? I really want to root but damn samsung wont let me!
I see this in odin btw
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-ha3g-ha3gxx-smn900.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> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> cache.img
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
UPDATE!
I tried using odin 1.85 to root, and now its stuck at cache.img it hasnt changed for maybe an hour now what?
UPDATE2
phew unticked autoreboot in odin and manually rebooted and everythings good
Sorry I could not tag your question due to failure with the mobile app. For starters I did not worry about using the auto-root option since I am not worried about tripping Knox counter. I prefer to flash twrp or cwm via Odin and then flash the current version of supersu from the recovery or if you are looking to install a custom Rom you can just flash it instead. Nothing against CF auto-root but this has always worked for me.
sm-900t: Powered by X-Note V13
FFTony said:
Sorry I could not tag your question due to failure with the mobile app. For starters I did not worry about using the auto-root option since I am not worried about tripping Knox counter. I prefer to flash twrp or cwm via Odin and then flash the current version of supersu from the recovery or if you are looking to install a custom Rom you can just flash it instead. Nothing against CF auto-root but this has always worked for me.
sm-900t: Powered by X-Note V13
Click to expand...
Click to collapse
Could you please explain that in noob terms?
firmware upgrade encountered an issue. please select recovery mode in kies and try ag
hi
i have same problem.
pls help me..
willzhang0 said:
I tried to root my sm-n900 note 3 and followed all the instructions to the letter on the forum and when I tried to root through odin, it says writing cache.img and I wait for a few minutes then it says FAIL, I unplugged then restarted my phone and it says "FIRMWARE UPGRADE ENCOUNTERED AN ISSUE, PLEASE SELECT RECOVERY MODE IN KIES AND TRY AGAIN" and now kies doesnt recognize my device anymore, So what can I do now? I really want to root but damn samsung wont let me!
I see this in odin btw
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-ha3g-ha3gxx-smn900.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> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> cache.img
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
UPDATE!
I tried using odin 1.85 to root, and now its stuck at cache.img it hasnt changed for maybe an hour now what?
UPDATE2
phew unticked autoreboot in odin and manually rebooted and everythings good
Click to expand...
Click to collapse
Awesome... Your technique worked for me.
You just have to uncheck the auto reboot option. Its so simple.
Thanks a lot man!
i have this same problem..pls help me..even i unticked reboot option but its not working...stuck in da middle while rooting..pls help me..
Hello guys.
My Galaxy S7 had a problem once where it was stuck at the Samsung Logo when booting. I took it to a Samsung Rep and they repaired it for me because it was on the warranty period. 3 months after this repair the phone had the same issue, but as it was out of warranty already i flashed a stock rom through odin and it worked. 2 weeks later i was using the phone playing some games while listening to music and then suddenly it restarted and now it boots straight into the "Downloading... please don't turn off" Odin Screen. When i restart the phone it shows the Samsung Galaxy S7 screen real fast and then goes to the "Downloading..." screen, without even showing the "Warning A custom OS...." screen. And when on this screen it does not show the usual Odin screen info on the top left corner. If i try to restart it with the Volume Down, Power and Home sometimes it shows the usual screens for Odin (First the Warning Screen and then the Downloading with the info on the top left corner).
I tried to flash a new firmware but it does not work. I searched a lot on the internet but couldn't find anyone with the same issue, only people who are stuck on odin mode but then when they press the volume down, home and power button the phone boots normally.
This is the Log when i try to flash with HOME_CSC
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> skip file list for home binary
<ID:0/004> param.bin
<ID:0/004> Home Binary Download
<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> cm.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And when i try with CSC i get the "No PIT Partition" error. The firmware that was flashed before this last problem is the same i'm trying to flash right now : G930FXXS1BPJC_G930FZTO1BPIF_ZTO (Brazil Unlocked) from 10/11/16. Downloaded on SamMobile
Thanks
icelest said:
Hello guys.
My Galaxy S7 had a problem once where it was stuck at the Samsung Logo when booting. I took it to a Samsung Rep and they repaired it for me because it was on the warranty period. 3 months after this repair the phone had the same issue, but as it was out of warranty already i flashed a stock rom through odin and it worked. 2 weeks later i was using the phone playing some games while listening to music and then suddenly it restarted and now it boots straight into the "Downloading... please don't turn off" Odin Screen. When i restart the phone it shows the Samsung Galaxy S7 screen real fast and then goes to the "Downloading..." screen, without even showing the "Warning A custom OS...." screen. And when on this screen it does not show the usual Odin screen info on the top left corner. If i try to restart it with the Volume Down, Power and Home sometimes it shows the usual screens for Odin (First the Warning Screen and then the Downloading with the info on the top left corner).
I tried to flash a new firmware but it does not work. I searched a lot on the internet but couldn't find anyone with the same issue, only people who are stuck on odin mode but then when they press the volume down, home and power button the phone boots normally.
This is the Log when i try to flash with HOME_CSC
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> skip file list for home binary
<ID:0/004> param.bin
<ID:0/004> Home Binary Download
<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> cm.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And when i try with CSC i get the "No PIT Partition" error. The firmware that was flashed before this last problem is the same i'm trying to flash right now : G930FXXS1BPJC_G930FZTO1BPIF_ZTO (Brazil Unlocked) from 10/11/16. Downloaded on SamMobile
Thanks
Click to expand...
Click to collapse
Hi mate
Why is not in warranty still...should be a year
Are you using the latest Odin?
Are you also flashing AP BL & CP?
Go into recovery do a factory reset and try again.......
Try a different stock firmware
MAX 404 said:
Hi mate
Why is not in warranty still...should be a year
Are you using the latest Odin?
Are you also flashing AP BL & CP?
Go into recovery do a factory reset and try again.......
Try a different stock firmware
Click to expand...
Click to collapse
Samsung is denying the warranty because my screen has 2 cracks and they are saying that this problem was caused because of my "bad use" of the smartphone.
Yes. Using Odin 3.12.3.
I'm flashing AP, BL, CP and CSC.
Can't go into recovery. The phone goes straight to the odin screen. Can't do anything other than odin.
Already tried 3 firmwares from my csc (ZTO) and 2 from the Official Stock Rom thread here at XDA.
icelest said:
Samsung is denying the warranty because my screen has 2 cracks and they are saying that this problem was caused because of my "bad use" of the smartphone.
Yes. Using Odin 3.12.3.
I'm flashing AP, BL, CP and CSC.
Can't go into recovery. The phone goes straight to the odin screen. Can't do anything other than odin.
Already tried 3 firmwares from my csc (ZTO) and 2 from the Official Stock Rom thread here at XDA.
Click to expand...
Click to collapse
Try leaving BL out from the flash, only flash the other 3 parts
*Detection* said:
Try leaving BL out from the flash, only flash the other 3 parts
Click to expand...
Click to collapse
This is the log when using the other 3 without the BL
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> Home Binary Download
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Try to flash Twrp then make format data and flash custom Rom..
Muhammad Rihawi said:
Try to flash Twrp then make format data and flash custom Rom..
Click to expand...
Click to collapse
Odin Fails to flash TWRP. This is the log:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Don't try flashing anything custom or you'll trip the KNOX warranty uFuse
Phone is still under warranty for 12 months, take it back, the repair failed they should fix it again
icelest said:
Samsung is denying the warranty because my screen has 2 cracks and they are saying that this problem was caused because of my "bad use" of the smartphone.
Yes. Using Odin 3.12.3.
I'm flashing AP, BL, CP and CSC.
Can't go into recovery. The phone goes straight to the odin screen. Can't do anything other than odin.
Already tried 3 firmwares from my csc (ZTO) and 2 from the Official Stock Rom thread here at XDA.
Click to expand...
Click to collapse
icelest said:
This is the log when using the other 3 without the BL
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> Home Binary Download
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Hi mate
In your first post you showed that odins fails on this step
cm.bin = Cryptography Manager , the function of this is to avoid downgrades
Do you remember what was the firmware you had? if not try to flash the very latest firmware available
Also i found a very similar case in a a S6 thread , the problem seems like the recovery was missing
http://forum.xda-developers.com/galaxy-s6/help/solved-stuck-download-mode-failed-odin-t3104736
check it out just in case the above solution fails
How to Extract Stock Recovery from Samsung Firmware!
MAX 404 said:
Hi mate
In your first post you showed that odins fails on this step
cm.bin = Cryptography Manager , the function of this is to avoid downgrades
Do you remember what was the firmware you had? if not try to flash the very latest firmware available
Also i found a very similar case in a a S6 thread , the problem seems like the recovery was missing
http://forum.xda-developers.com/galaxy-s6/help/solved-stuck-download-mode-failed-odin-t3104736
check it out just in case the above solution fails
How to Extract Stock Recovery from Samsung Firmware!
Click to expand...
Click to collapse
Thanks for the help. I'll try downloading the latest firmware and flashing it. After that i'll try the solution on the S6 thread. Thank you very much
MAX 404 said:
Hi mate
In your first post you showed that odins fails on this step
cm.bin = Cryptography Manager , the function of this is to avoid downgrades
Do you remember what was the firmware you had? if not try to flash the very latest firmware available
Also i found a very similar case in a a S6 thread , the problem seems like the recovery was missing
http://forum.xda-developers.com/galaxy-s6/help/solved-stuck-download-mode-failed-odin-t3104736
check it out just in case the above solution fails
How to Extract Stock Recovery from Samsung Firmware!
Click to expand...
Click to collapse
When trying the recovery.img method i got this log on Odin
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Currently downloading the latest firmware for tests
MAX 404 said:
Hi mate
In your first post you showed that odins fails on this step
cm.bin = Cryptography Manager , the function of this is to avoid downgrades
Do you remember what was the firmware you had? if not try to flash the very latest firmware available
Also i found a very similar case in a a S6 thread , the problem seems like the recovery was missing
http://forum.xda-developers.com/galaxy-s6/help/solved-stuck-download-mode-failed-odin-t3104736
check it out just in case the above solution fails
How to Extract Stock Recovery from Samsung Firmware!
Click to expand...
Click to collapse
I get this Odin Log when flashing the recovery method as displayed on the S6 thread
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
better try the different firmware but use some chrome or browser downloader to download the firmware not internet download manager.
any downloader which uses the single downloading node not multiple nodes like idm
it happened with me 2 i figured it out using this method.thanx
icelest said:
I get this Odin Log when flashing the recovery method as displayed on the S6 thread
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
What about flashing the latest firmware, you tried?
MAX 404 said:
What about flashing the latest firmware, you tried?
Click to expand...
Click to collapse
With the last firmware i get the same PIT error
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> param.bin
<ID:0/005> Home Binary Download
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
icelest said:
With the last firmware i get the same PIT error
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> param.bin
<ID:0/005> Home Binary Download
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
hi
are you using CSC or home_csc?
use CSC file it contains the pit file
MAX 404 said:
hi
are you using CSC or home_csc?
use CSC file it contains the pit file
Click to expand...
Click to collapse
With CSC i get this error
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What you have is a hardware fault. Aka brick.
icelest said:
With CSC i get this error
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Hi mate
Did you re installed the Samsung drivers , try a different USB cable....better yet try all this in a different PC, just to make sure all this problems are not PC related
MAX 404 said:
Hi mate
Did you re installed the Samsung drivers , try a different USB cable....better yet try all this in a different PC, just to make sure all this problems are not PC related
Click to expand...
Click to collapse
Hi.
Yeah, tried it on 3 different PCs. Always the same errors :/ I'm guessing it's some hardware issue. Now i'll have to fight Samsung so they fix the phone on warranty
Samsung gt-s7710
my phone was not booting so i tried to instal new stock firmware using odin.
after instaling firmware i get firmware upgrade encounter an issue use kies to recover.
i have used kies firmware upgrade and initialization. when that has finish. the phone reboots.
and i get the same error firmware upgrade encounter an issue use kies to recover
i cant get the phone in recover mode volume up ,home, power
the only thing i get on my phone now is that error screen. or i can boot in download mode.
how do i fix this.
Hi !
Would have helped to tell us what happened before ending up onto this problem
Here is a workaround https://forum.xda-developers.com/showpost.php?p=40232503&postcount=43
Good luck !
The Samsung was stuck on bootloop. Tried all the tips i could find. And ended up flashing new firmware. The firmware was correct, and passed. But i only got the kies. firmware update error screen when the phone booted up
tried flashing the phone with the first image file in the link. the flashing was a pass, but the phone reboots to the error Firmware update encounterd a issue. have tried many firmwares found on samsmobile. but the flash is a pass, and the phone reboots with the same error
<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> STE_boot1.img
<ID:0/006> STE_boot2.img
<ID:0/006> boot.img
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> modem.bin
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
Hi
When unrooting my phone I accidentally deleted the OS from my Samsung S6.
My model is SM-G920F
The phone was bought directly from Samsung via Amazon and is unlocked. I live in the UK and my sim is registered to Virgin.
Currently I can put the phone in Downloading (Odin mode) and TWRP.
I have attempted to Flash the firmware with Odin but I get the following fail message each time.
"<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> Added!!
<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> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!"
I have updated my drivers and attempted to use a different port on my PC.
I am using Odin v3.12
I have attempted to use Smart Switch but I get the error message
"SM-G920F does not support initialising. Please contact our service centre."
Samsung service centre did not know what to do with the phone.
I would appreciate any advice. I've accepted my phone data is gone.
Gullion said:
Hi
When unrooting my phone I accidentally deleted the OS from my Samsung S6.
My model is SM-G920F
The phone was bought directly from Samsung via Amazon and is unlocked. I live in the UK and my sim is registered to Virgin.
Currently I can put the phone in Downloading (Odin mode) and TWRP.
I have attempted to Flash the firmware with Odin but I get the following fail message each time.
"<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> Added!!
<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> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!"
I have updated my drivers and attempted to use a different port on my PC.
I am using Odin v3.12
I have attempted to use Smart Switch but I get the error message
"SM-G920F does not support initialising. Please contact our service centre."
Samsung service centre did not know what to do with the phone.
I would appreciate any advice. I've accepted my phone data is gone.
Click to expand...
Click to collapse
In twrp try and flash any rom , may work
hairyfred said:
In twrp try and flash any rom , may work
Click to expand...
Click to collapse
Where would I get access to roms to Flash in twrp?
Are they the same as .tar or .md5 files?
Gullion said:
Where would I get access to roms to Flash in twrp?
Are they the same as .tar or .md5 files?
Click to expand...
Click to collapse
......you've never flashed a rom have you.... Is this your first time rooting
hairyfred said:
......you've never flashed a rom have you.... Is this your first time rooting
Click to expand...
Click to collapse
I've flashed with Odin in the past. Not with TWRP.
But yeah, I'm honestly a noob in way over my head.
I've had a new error on Odin attempting to flash.
<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> boot.img
<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)
if u can accses twrp just flash a rom and it should be good
First of all. What Samsung Firmware are you flashing, are you trying to downgrade to a older firmware version than what is already on there?
Try the latest samsung firmware and make sure it's suited for the model of your device.
Try another usb port and another microUSB cable. It is common for bad microUSB cables to make ODIN flash fail.
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