SM-G955U1 boots directly to download mode with error message - Samsung Galaxy S8+ Questions & Answers

The error message reads "An error has occured while updating the device software. Use the emergency recovery function in the smart switch pc software."
Im picking up from a lot of you by reading various threads that this is no longer an option.
Backstory: This phone was given to me and from day 1 all the system apps would crash to the point where android would reboot. The phone wouldnt shut off completely like it was losing power, but it would go back to the second screen you see on boot. At this point, the settings reported the software build number as being G955USQS5CRI4, which i dont fully understand. Because on the back side of the phone, the model number reads SM-G955U1.
In an attempt to resolve this issue, i used odin and flashed various builds of g955u1 across a few versions of odin and even attempted some g955u builds. At some point during all of this, download mode switched from normal looking download mode to displaying a big ! in a triangle on the screen. None of the usual information youd see is displayed. However, odin still connects and it appears as though i can still flash. I fear i may have made a mistake.
This log is my latest attempt using SM-G955U1_1_20190709124427_xh7461wrxv_fac pulled from SamFirm. G955U1UES6DSG1 either XAA or VZW, i cant remember which.
Code:
<ID:0/008> 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..
<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/008> Odin engine v(ID:3.1301)..
<ID:0/008> File analysis..
<ID:0/008> Total Binary size: 5808 M
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> NAND Write Start!!
<ID:0/008> SingleDownload.
<ID:0/008> abl.elf
<ID:0/008> bksecapp.mbn
<ID:0/008> xbl.elf
<ID:0/008> tz.mbn
<ID:0/008> hyp.mbn
<ID:0/008> devcfg.mbn
<ID:0/008> pmic.elf
<ID:0/008> rpm.mbn
<ID:0/008> cmnlib.mbn
<ID:0/008> cmnlib64.mbn
<ID:0/008> keymaster.mbn
<ID:0/008> apdp.mbn
<ID:0/008> msadp.mbn
<ID:0/008> sec.dat
<ID:0/008> NON-HLOS.bin
<ID:0/008> storsec.mbn
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img.ext4
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
When this fails, on the screen of the phone, red text appears that says "secure check fail: system".
Does anyone have any suggestions on what I should do next? Im kind of stumped. Ive been at this for a couple days and cant seem to get different results. I have downloaded several firmwares attempting to resolve this and some of those i believe failed due to bootloader version, but the others typically say fail (auth) or SHA256 is invalid. Although that may be due to me kind of switching between odin 3.13.1 and some patched version of it with this ODIN3B logo in the banner. I would be grateful if anyone could offer me some advice or at least explain what is happening to me. Thank you.

Related

Trying to return to stock, Odin Won't flash

I lost my 4g randomly. Blown sim maybe? But i'm trying to return to a touchwiz stock rom so that I can attempt a sim reprovision, but odin won't flash the device.
Here's the odin log
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I535VRALG1_I535VZWALG1_743127_REV09_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Anyone seen something like this before? Or solutions to the no 4g problem as thats the root cause of all of this mess.
note: My IMEI is still in tact.
Back in the day I lost data and imei from flashing 4.2.2 roms
I would have to go back to stock to fix.
I would have this problem and I was clueless
For whatever reason I tired on my moms computer and it worked fine.
It was not a bad download either. I still use the same files to date.
Hope this works for you.
God bless the American people
howlatnight said:
I lost my 4g randomly. Blown sim maybe? But i'm trying to return to a touchwiz stock rom so that I can attempt a sim reprovision, but odin won't flash the device.
Here's the odin log
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I535VRALG1_I535VZWALG1_743127_REV09_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Anyone seen something like this before? Or solutions to the no 4g problem as thats the root cause of all of this mess.
note: My IMEI is still in tact.
Click to expand...
Click to collapse
Try this link, http://forum.xda-developers.com/showthread.php?t=1762709
Welp, just trying it from my desktop worked. odd. Brought it back to VZW got a new sim. The world is good again.

SCH-i535 Soft-Bricked - No boot recovery, and unable to use Odin to flash

Hello, this is a bit embarrassing seeing as how this is my first post here on XDA.
My issue is that I rooted my 4.4.2 Verizon SCH-i535 galaxy s3 and I bricked it. I know, I was extremely stupid for trying to do this while half-awake at 2 in the morning LOL... but i ended up with a screen stating that "this device has detected a software not authorized by verizon wireless, please go to a branch to get help"
When I use Odin to try and flash any ROMs, this is the result:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ODINRecovery.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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
InuyashaITB said:
Hello, this is a bit embarrassing seeing as how this is my first post here on XDA.
My issue is that I rooted my 4.4.2 Verizon SCH-i535 galaxy s3 and I bricked it. I know, I was extremely stupid for trying to do this while half-awake at 2 in the morning LOL... but i ended up with a screen stating that "this device has detected a software not authorized by verizon wireless, please go to a branch to get help"
When I use Odin to try and flash any ROMs, this is the result:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ODINRecovery.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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
check out this thread
http://forum.xda-developers.com/showthread.php?t=2791801
you may be able to get away with just flashing the booloader/recovery zip in the second post
good luck

[help] n8020 restarted alone & freez at logo & ODIN failed!!

oh my god!
what is happened?
it was at my side on the bed, not under usage. it did a restart .. alone .. and could not enter the system. it freez at logo!
i tried:
- to wipe, but could not help.
- get the last backup with cmw, but could not help.
- flash tle stock recovery with odin, but gone fail.
- flash a fresh stock room with odin, but gone fail.
- flash pit file with odin, but gone fail.
it can enter download and recovery modes.
what was happened?
i am not beginner and could help many people with much of problems, but .. this thing is totally new for me.
who can help please? i can not still without my note. i use it all the time, specially now where i am in a new country and city
so .... heeeeeeeeeeeeeeeeeelllllllllp
-------------- 1st update
wenn i try to flash stock recovery:
Code:
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8020-Stock-Recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> SingleDownload.
<ID:0/015> recovery.img
<ID:0/015> NAND Write Start!!
<ID:0/015> FAIL!
<ID:0/015>
<ID:0/015> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and wenn i try to flash stock rom 4.4.2:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8020XXUDNE4_N8020VFGDNE1_N8020BUDNE1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Added!!
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
-------------- 2nd update
I tried everything, but nothing could work.
At the end I tried to restore with the advance setting, because when I resore my CWM-backup, it stop at mount /system and can not do that. So, I did:
- restore boot --> work
- restore cach -- > don't work
- restore data -- > don't work, rebooted alone
- restore system -- > don't work
What is the ODIN fail message ??
JJEgan said:
What is the ODIN fail message ??
Click to expand...
Click to collapse
wenn i try to flash stock recovery:
Code:
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8020-Stock-Recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> SingleDownload.
<ID:0/015> recovery.img
<ID:0/015> NAND Write Start!!
<ID:0/015> FAIL!
<ID:0/015>
<ID:0/015> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and wenn i try to flash stock rom 4.4.2:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8020XXUDNE4_N8020VFGDNE1_N8020BUDNE1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Added!!
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
is there maybe any methode mith ADB or any tool?
I tried everything, but nothing could work.
At the end I tried to restore with the advance setting, because when I resore my CWM-backup, it stop at mount /system and can not do that. So, I did:
- restore boot --> work
- restore cach -- > don't work
- restore data -- > don't work, rebooted alone
- restore system -- > don't work
Can't open the serial(COM) port
Google suggests USB cable problem or KIES? USB drivers .
http://forum.xda-developers.com/showthread.php?t=1622790
https://www.google.co.uk/search?q=a...source=hp&gfe_rd=cr&ei=zkMFVp7fCaux0wW8nKLoCw
but i work with other devices, also with this device before this problem
i deinstalled Kies and the driver, reinstaller the driver and tried again, but it is the same
no help
where to sell it as bricked of defect?
dercncplaner said:
no help
where to sell it as bricked of defect?
Click to expand...
Click to collapse
EBay and describe the problem .
Samsung Tab GT-N8010 Rom doesn't Install, PIT issue, Flashing Screen, do not turn ON
I have Samsung Tab GT-N8010
When I try to turn on, its screen flashing White for half second and then Black and Continuosly till the Battery End.
I try to Install ROM 4.4.2 with ODIN 3.10.7 and get this error
<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>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried different PIT files including 3 different N8010.pit and 8013.pit and 8020.pit
but the issue remaining same
I read all the google search including Russian websites at-least but I couldn't find the issue
I have original cable
Solution
I know now the problem and the solution.
The problem: The flash memory on the mainboard is defect. This was the answer of Samsung Support Office.
The solution: The mainboard have to be replaced.
I am now in Turkey and here there is no N8020, but just a bad version (N8005) !!!
So, Samsung could not repair it for me. But I found everything I need for the repair on ifixit, also the board, BĀ“but I could not collect the money for that, so maybe I wait or sell it. Here in turkey no one want to buy it because the phones here have to be registered and this costs much of money. hmm

Phone stuck and wont boot

Hi, I recently fixed my note edge by installing 4.4 kitkat. A few days later I realized it was really slow and so I plugged it in and tried to flash marshmallow stock. This didn't work and now my phone goes automatically to download mode and every time I try to re-flash it it either insta fails or says aboot fused 2 binary 1. Also, I think i got twrp installed because it passed on odin but if I try to boot recovery it Says "Could not do normal boot and ddi: mmc_read failed". Thanks for the help!
https://forum.xda-developers.com/note-4-tmobile/general/ddi-mmcread-failed-boot-error-fix-t3434335
Bordo_Bereli51 said:
https://forum.xda-developers.com/note-4-tmobile/general/ddi-mmcread-failed-boot-error-fix-t3434335
Click to expand...
Click to collapse
Thanks for the link but the files included in the guide are listed for the note 4 so how do I use that in note edge thanks for help
UPDATE
I have got phone into download/ odin mode but still need help as my flash fails in odin\
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!
Same thing...
Here's my odin log.
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008>
<ID:0/008> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Removed!!
P.s I have the AT&T model.
UPDATE
<ID:0/008> Added!!
<ID:0/008> Removed!!
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N915AUCS2DQD1_CL8932341_QB13132575_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<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> AP_N915AUCS2DQD1_CL8932341_QB13132575_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<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> CP_N915AUCS2DQD1_CL8932341_QB13132575_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<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> CSC_ATT_N915AATT2DQD1_CL8932341_QB13132575_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> sbl1.mbn
<ID:0/008> rpm.mbn
<ID:0/008> tz.mbn
<ID:0/008> sdi.mbn
<ID:0/008> NON-HLOS.bin
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img.ext4
<ID:0/008> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)
It failed half way through on the phone it says
"ODIN : flash write failure"
1) ODIN 3.09
2) Get N915A 5.0.1 Modem
3) Get N915A 6.0.1 Firmware Stock (the AP file)
4) Get N915A 6.0.1 Modem
1)Place phone in DOWNLOAD MODE (volume down + home + power button)
2) Open ODIN 3.09
3) Place file N915A 5.0.1 Modem in CP
4) Place file N915A 6.0.1 Firmware.tar in AP box
5) Once ODIN is finished flashing the files power off your phone and go back into DOWNLOAD MODE, dont boot.
6) Place file N915A 6.0.1 Modem in CP box
7) Once the file is flashed your phone will be mmc error free and you will have a 100% working phone again.
thejug786 said:
Hi, I recently fixed my note edge by installing 4.4 kitkat. A few days later I realized it was really slow and so I plugged it in and tried to flash marshmallow stock. This didn't work and now my phone goes automatically to download mode and every time I try to re-flash it it either insta fails or says aboot fused 2 binary 1. Also, I think i got twrp installed because it passed on odin but if I try to boot recovery it Says "Could not do normal boot and ddi: mmc_read failed". Thanks for the help!
Click to expand...
Click to collapse
Tell me, how could you return to 4.4.4? I also have n915a on marshmallow, but I would like to return to kitkate. Tell me how you did it ??
"A few days later I realized it was really slow" tells us maybe that this is a emmc failure problem
https://www.sammobile.com/forum/showthread.php?t=30686
In this forum, this guy has the same problem like you. He tried different attempts. Even though he flashed succesfully and booted up, his phone was very slow and had freezing problem. A while later he got again the "Could not do normal boot and ddi: mmc_read failed" problem.

Custom binary blocked by FRP lock?

Hello,
I have a Samsung Galaxy S8 phone (with TWRP rooted). When I turn on my phone, I get a message 'Custom binary blocked by FRP lock'. I can only access the download mode. I tried to flash to the latest stock firmware with odin but when I click start, it says PASS!! but nothing happens. It just gets back and reboots again with the same message. I tried so many things, but now I give up because I can't find any solution. Can someone please help me?
When I open download mode I see:
Odin mode
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-G950F
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FRP LOCK: On
OEM LOCK: ON
Secure download: Enabled
(If you guys want to see more, I will post it)
This is what I get in Odin:
<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..
<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/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> sboot.bin.lz4
<ID:0/003> param.bin.lz4
<ID:0/003> up_param.bin.lz4
<ID:0/003> cm.bin.lz4
<ID:0/003> boot.img.lz4
<ID:0/003> recovery.img.lz4
<ID:0/003> system.img.lz4
<ID:0/003> userdata.img.lz4
<ID:0/003> modem.bin.lz4
<ID:0/003> modem_debug.bin.lz4
<ID:0/003> cache.img.lz4
<ID:0/003> Home Binary Download
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
After this I get PASS!! on odin.
Please help me.
Thank you
Another FRP locked mobile.
Is boot locked?
Try this
bluheart said:
Another FRP locked mobile.
Is boot locked?
Try this
Click to expand...
Click to collapse
Thank you for your reply. Unfortunately it didn't work. In odin it gives FAIL!:
<ID:0/003> Removed!!
<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/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 1996 M
<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> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I don't know what my PDA is. Is that a problem?
With OEM lock and FRP lock, you should be able to flash latest stock and reboot.
Maybe you should unzip the downloaded file then see for the contents and then flash.

Categories

Resources