Develop Bugs

[Q] I think I bricked my phone. Need help.

I tried to use Odin to install the N7105 South Africa rom.
It was stuck for 10 minutes so I unplugged and reboot. Now the phone is stuck in a screen that reads
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I plugged in the phone to Kies and Kies won't pick up the device on USB.
I tried to re-rom the phone again and it Odin keeps failing. Here's the log from Odin:
<OSM> Please wait..
<OSM> N7105XXDLK7_N7105OJVDLK5_N7105XXDLK7_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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Please advise.

Are you still able to access your recovery? And what about your bootloader? You could always tweak with your device from the recovery or from the bootloader on the fastboot usb. Make sire you've got your device drivers if your gonna fastboot usb it!

MistedEvo said:
Are you still able to access your recovery? And what about your bootloader? You could always tweak with your device from the recovery or from the bootloader on the fastboot usb. Make sire you've got your device drivers if your gonna fastboot usb it!
Click to expand...
Click to collapse
Just the bootload screen to download roms. HOw do I tweak it from the recovery menu?

get a stock odin image and flash it again
it will probably get stuck... in which case, boot to recovery (it will be the stock one) by holding volume up + home + power until you see the recovery
wipe data
reboot.
good to go.

Thx. got it.

error when flashing ROM via Odin

hi, i'm trying flash a ROM to note 10.1 p605, it has Singapore ROM originally and im trying to flash German ROM
i get this error in Odin every time i try to flash:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P605XXUAMJ2_P605OJVAMI3_P605XXUAMJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

Mashari_F said:
hi, i'm trying flash a ROM to note 10.1 p605, it has Singapore ROM originally and im trying to flash German ROM
i get this error in Odin every time i try to flash:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P605XXUAMJ2_P605OJVAMI3_P605XXUAMJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
1) Have you tried to use an other usb port?
2) do you use the original usb cable?
3) do you have all the samsung drivers installed?
4) make eure that samsung kies is not running in the background
Hope it helps you
Gesendet von meinem SM-P600 mit Tapatalk

Got the same problem, so recovered it from kies
Skickat från min SM-P605 via Tapatalk

Hi... Anybody have a solution for this problem? Have the tablet returned from a service and tried to flash the recovery but it just doesn't work.
THanks a lot for any help.

ronaldphl said:
Hi... Anybody have a solution for this problem? Have the tablet returned from a service and tried to flash the recovery but it just doesn't work.
THanks a lot for any help.
Click to expand...
Click to collapse
Is it giving you a FAIL after flashing , or doesn`t show up after a successful flash.
If it doesn`t show up after flashing , re-flash but untick "Auto-Reboot" within odin before flashing & restart manually after flashing.

I have a "Fail after flashing" - complete (Write) - operation failed in Odin

Which odin
Hi,
When flashing with oder it depends on the package which oder will work.
At my p 605 the 1.86 version was working without probs.
The best is to use the Oden which is coming together the Roms Zipfile.
I hope this info helps please let me know.
Good luck

FSkyman said:
Hi,
When flashing with oder it depends on the package which oder will work.
At my p 605 the 1.86 version was working without probs.
The best is to use the Oden which is coming together the Roms Zipfile.
I hope this info helps please let me know.
Good luck
Click to expand...
Click to collapse
I tried all the possible combination... different Odin... different cables and ports... it just didn't work.
Since I read from a old post that flashing a original rom thru Odin helps... and i tried... Odin works and the rom can be flashed without prompting the signature verification failed error.
I suspect if Samsung has done something to make the recovery image fails...
I tried flashing the recovery using the stock recovery too and it failed as well

Recovery Flashing
ronaldphl said:
I tried all the possible combination... different Odin... different cables and ports... it just didn't work.
Since I read from a old post that flashing a original rom thru Odin helps... and i tried... Odin works and the rom can be flashed without prompting the signature verification failed error.
I suspect if Samsung has done something to make the recovery image fails...
I tried flashing the recovery using the stock recovery too and it failed as well
Click to expand...
Click to collapse
Now I am confused are you talking about recovery or rom ?
The only recovery I could get to work was the TWRP - this Zip file comes with a Odin that works.
Cwm philz are not working.
But keep in mind as soon you installed twrp your knox counter is tripped.
For rom flashing you have to wipe your tablet and then follow these instructions xxxx://www.droidgator.com/update-galaxy-note-101-sm-p605-android-43-xxubmj9-firmware/.
Before starting backup your tab then everything should be fine.

Thanks for your effort in helping me out...
Before I sent my tablet for servicing... I restored the tablet with Kies to the original factory setting and rom as I HAD rooted my P605 and flashed a custom rom before. [Although the Know count is 0*1 anyway.... but the service centre was kind enough to fix my tablet as it's a hardware failure instead of anything to do with the ROM ]
When I got my tablet back and tried to flash the TWRP into it, this problem surfaced. And I read from another post that some say flashing a Samsung original rom could help I tried but to no avail. Still I am waiting and looking for a solution.
I tried Odin 3.04 3.07 and 1.85 with the two versions of TWRP but still none of them work.

Cant flash Stock firmmware
Hi Guys
Tried all methods in the fourms but i am still not able to flash stock firmware from odin.
this is the error i get.
I am trying to update using Odin 3.09 as well as 3.07. but it is failing while writing system.
<ID:0/004> Added!!
<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> system.img.ext4
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone please help me? Is this because this shows Write Protection : Enable?

nihalvm said:
Hi Guys
Tried all methods in the fourms but i am still not able to flash stock firmware from odin.
this is the error i get.
I am trying to update using Odin 3.09 as well as 3.07. but it is failing while writing system.
<ID:0/004> Added!!
<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> system.img.ext4
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone please help me? Is this because this shows Write Protection : Enable?
Click to expand...
Click to collapse
---
Might you recall what the firmware version was before you started to flash this one?
I am also trying to recover from NC3 back to MJ4XAC and it is not allowing me to finish, Kies also does not recover the tablet. It looks like one of the filesystems is in a different state. With TWRP there are options to perform CHMOD on the file systems but I figure I have been mocking around long enough and for some reason beyond my experience the system is not responding.
Can you still get into ADB mode? That might be an option to see if you can gain access?

nihalvm said:
Hi Guys
Tried all methods in the fourms but i am still not able to flash stock firmware from odin.
this is the error i get.
I am trying to update using Odin 3.09 as well as 3.07. but it is failing while writing system.
<ID:0/004> Added!!
<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> system.img.ext4
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone please help me? Is this because this shows Write Protection : Enable?
Click to expand...
Click to collapse
Is the sm-p605v (verizon) synonymous with sm-p605 for technical purposes? I am having identical problems with lt03ltevzw. Odin 3

aelaan said:
---
Might you recall what the firmware version was before you started to flash this one?
I am also trying to recover from NC3 back to MJ4XAC and it is not allowing me to finish, Kies also does not recover the tablet. It looks like one of the filesystems is in a different state. With TWRP there are options to perform CHMOD on the file systems but I figure I have been mocking around long enough and for some reason beyond my experience the system is not responding.
Can you still get into ADB mode? That might be an option to see if you can gain access?
Click to expand...
Click to collapse
Although it failed, I was able to recover using kies and use tablet as normal without data loss. It might be because at that point I had not rooted my tab and system state was still original in odin.
By the way I was on MJ4 xsa(AUSTRALIA) trying to install NC2 TGY(HONG KONG).
Now I have rooted it and have I installed NC2. I am still not sure what the issue was. But the only thing I did different was, first was using a virtual machine, but now did in an actual windows machine.
Can you please try this? If you can, install back NC2 using odin. Boot it once, then try recovering using kies. Kies recover mode gets your latest firmware based on your serial number. Not what firmware you are running.
Please post back the result. Interested to know the outcome.
Sent from my SM-P605 using XDA Premium 4 mobile app
---------- Post added at 08:38 AM ---------- Previous post was at 08:33 AM ----------
Khazaad said:
Is the sm-p605v (verizon) synonymous with sm-p605 for technical purposes? I am having identical problems with lt03ltevzw. Odin 3
Click to expand...
Click to collapse
I don't think it is. Although the specs are the same, read somewhere that the internal partition structure for carrier branded firmware are different to generic. Don't remember where I read that. But can't confirm that either.
Sent from my SM-P605 using XDA Premium 4 mobile app

[Q] Phone SoftBricked in the middle of the night, help!

I haven't done any ROM updates for a couple of weeks, and I was sound asleep when the phone rebooted. It sat 'rebooting' for two hours before I woke up.
I'm able to reboot into Download Mode, but have been unable to install anything that has worked. I tried flashing both TWRP2.7.0.0 and the stock ROM, but neither have worked. TWRP is still showing as 2.6.3.1 on my phone, and I get a failure when loading the Stock rom that looks like this:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747MVLUFNH2_I747MOYBFNH2_I747MVLUFNH2_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> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I'm also able to boot into Recovery mode, but it appears that the phone is encrypted (it asks for a password, even though I've never encrypted it!) and when I try to factory reset or wipe dalvik or anything else, I get: E: Unable to mount '/cache'
Can you help? Phone is a rooted SGS-I7474M on Telus, and was running Slim 4.4.4 build 7.0 Official 5979. I'm using TWRP as my recovery.

Maybe try loading a stock from image using Odin? You can download the stock images from sammobile

Tony_YYZ said:
Maybe try loading a stock from image using Odin? You can download the stock images from sammobile
Click to expand...
Click to collapse
I think that's what I've been doing? I've downloaded this stock firmware: sammobile.com/firmwares/download/34793/I747MVLUFNH2_I747MOYBFNH2_TLS.zip/ and then tried loading it via ODIN?
Perhaps I'm missing something... Appreciate your thoughts!

hardidu said:
I think that's what I've been doing? I've downloaded this stock firmware: sammobile.com/firmwares/download/34793/I747MVLUFNH2_I747MOYBFNH2_TLS.zip/ and then tried loading it via ODIN?
Perhaps I'm missing something... Appreciate your thoughts!
Click to expand...
Click to collapse
Oh, my mistake. That's what I was suggesting. Sorry...I don't know what else to try.

What bootloader is on your phone?
You're trying to alter the bootloader which is causing the error after trying to flash aboot.mbn.

audit13 said:
What bootloader is on your phone?
You're trying to alter the bootloader which is causing the error after trying to flash aboot.mbn.
Click to expand...
Click to collapse
You've lost me... I have no idea. I don't think I've ever touched the bootloader unless that's packaged with Slimkat or TWRP,
How do I find out and what's my next step?

<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
The aboot.mbn file is a bootloader that Odin is trying to load onto your phone. but the current bootloader is preventing this because the bootloader your are trying to load is not compatible with your phone or the current bootloader is newer than the bootloader Odin wants to flash.
Does your phone still boot into download mode? You're sure your phone is an i747m (Canadian version of s3)?
If your phone can boot into download mode, I recommend you flash the latest version of Philz Touch for the d2lte, copy a custom ROM to your external SD card, boot into Philz, and flash the custom ROM so you can at least get your phone booted. Once booted, install the Samsung Phone info app. This app will tell you the baseband and bootloader on your phone.

audit13 said:
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
The aboot.mbn file is a bootloader that Odin is trying to load onto your phone. but the current bootloader is preventing this because the bootloader your are trying to load is not compatible with your phone or the current bootloader is newer than the bootloader Odin wants to flash.
Does your phone still boot into download mode? You're sure your phone is an i747m (Canadian version of s3)?
If your phone can boot into download mode, I recommend you flash the latest version of Philz Touch for the d2lte, copy a custom ROM to your external SD card, boot into Philz, and flash the custom ROM so you can at least get your phone booted. Once booted, install the Samsung Phone info app. This app will tell you the baseband and bootloader on your phone.
Click to expand...
Click to collapse
I tried loading I747MVLDLK4_aio.tar.md5 and here's the log from the fail I ended up with:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747MVLDLK4_aio.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Loading Philz also failed.

Are you flashing the latest Philz tar.md5 file? You can't flash the zip in Odin. You should be able to flash the Philz zip in TWRP.

audit13 said:
Are you flashing the latest Philz tar.md5 file? You can't flash the zip in Odin. You should be able to flash the Philz zip in TWRP.
Click to expand...
Click to collapse
I was using Skips Toolkit to try and load Philz... I'll try using TWRP

Flash Philz tar.md5 in Odin or the zip in TWRP. I prefer not to using any tool kits.

audit13 said:
Flash Philz tar.md5 in Odin or the zip in TWRP. I prefer not to using any tool kits.
Click to expand...
Click to collapse
The process all looks good, log:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.07.9-d2att.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Removed!!
But still boots with TWRP... despite a PASS in Odin.

[SOLVED] ODIN Flash failed (for downgrade, custom-to-stock, etc)

Hey there awesome people!
I have been weeping over my N3N refusing to accept Stock firmware I was downloading.
I followed these steps to flash the stock firmware I would download:
Flashing STOCK firmware (via ODIN):
Put phone off / battery pull
Download ODIN (this one or whichever is newest at the time you read this)
Open up ODIN (as Administrator on Windows PC)
Press and HOLD DOWN the Volume Down [AND] the Home buttons. THEN Press the POWER button. On the screen it will show, press Volume UP to go to DOWNLOAD mode
Plug your phone into the PC and ODIN will show you (in the log) that a device has been Added!
Click the AP button and navigate to your downloaded firmware.
Let ODIN finish the MD5 check and then press START to start flashing
So, at this point, your ODIN will either be showing PASS or FAIL.
If it shows PASS, you're good to go. Skip to Installing a recovery.
If it shows FAIL, read the Log (displayed in the program's left hand side) and observe this:
Code:
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> modem.bin
<ID:0/005> cache.img
<ID:0/004> hidden.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Before showing FAIL!, the last thing it should've listed should be hidden.img
If yours didn't show this, it probably didn't flash the phone upto this point. What we want is for the boot.img, recovery.img, system.img, modem.bin and cache.img to have been flashed to the phone.
When it shows FAIL!, it means that the bootloader it is trying to flash is older than what the phone already has. You will probably find that you are stuck here when you're coming from LL to KK or JB, or from a newer KK to an older one.
Fear not It still worked!
What we do now is just flash a recovery to the phone (we will be replacing the stock recovery that stock ROM comes with), (or root it) and we'll be good to go.
Installing a custom recovery:
Download a recovery (I use TWRP Materialized )
Unzip it and re-open your ODIN (if your ODIN was still open, hit the RESET button)
Do a battery pull on the phone, and boot into DOWNLOAD mode again.
Connect the phone to the PC. ODIN should show in the Log that a device has been added.
Click AP button and navigate to where your Custom recovery is.
After ODIN finishes MD5 check, hit START and let the Custom recovery be flashed.
After this is done, boot into recovery by holding down the Volume Up [AND] Home buttons then pressing Power button.
Go into recovery and wipe Data, Cache and Dalvik (factory reset) and reboot the phone.
BOOM! You'll see the Samsung logo doing its thing and we'll be good to go!
Leave a thanks if this helps :highfive:
Shoutout to @rihawi who pointed this trick out in this post!

boydee said:
What we do now is just flash a recovery to the phone (we will be replacing the stock recovery that stock ROM comes with), (or root it) and we'll be good to go.
Click to expand...
Click to collapse
Okay. I had the Odin Fail because I was trying to downgrade to a firmware with earlier bootloader and as you described I installed TWRP. But now I still get the same error in Odin when trying to install this firmware even with TWRP in place... What should I do?

mcpossity said:
Okay. I had the Odin Fail because I was trying to downgrade to a firmware with earlier bootloader and as you described I installed TWRP. But now I still get the same error in Odin when trying to install this firmware even with TWRP in place... What should I do?
Click to expand...
Click to collapse
List for the steps you're taking to install. I fear that we might have gotten lost somewhere along the way.
The idea is to FIRST install the firmware, THEN install TWRP, then reboot (TWRP should be the last thing you install.)

boydee said:
List for the steps you're taking to install. I fear that we might have gotten lost somewhere along the way.
The idea is to FIRST install the firmware, THEN install TWRP, then reboot (TWRP should be the last thing you install.)
Click to expand...
Click to collapse
Your post title says "for downgrade". So I have a firmware with, let's say, bootloader binary version 3 installed. I want to downgrade to an older firmware which has bootloader binary version 2. I can't just flash the older firmware, because Odin fails. So I was following your guide to install TWRP to somehow downgrade through that, but it doesn't work.
When it shows FAIL!, it means that the bootloader it is trying to flash is older than what the phone already has. You will probably find that you are stuck here when you're coming from LL to KK or JB, or from a newer KK to an older one.
Click to expand...
Click to collapse
This is where I'm at right now.

mcpossity said:
Your post title says "for downgrade". So I have a firmware with, let's say, bootloader binary version 3 installed. I want to downgrade to an older firmware which has bootloader binary version 2. I can't just flash the older firmware, because Odin fails. So I was following your guide to install TWRP to somehow downgrade through that, but it doesn't work.
This is where I'm at right now.
Click to expand...
Click to collapse
That's okay! it's perfectly fine for it to FAIL!
Flash it again and copy/paste the ODIN Log here for me to see and advise on what you should do next.
Cheers! :highfive:

odin fail
xda-developers LOGIN REGISTER search plus
Join the Experts
Post Preview:
i used odin3 v3.12.7
this is what appears on the log tab.
Added
Odin engine v(ID:3.1207)
File analysis
setupconnection
initialization
get pit for mapping
firmware update start
NAND write start
Singledownload
sboot.bin
cm.bin
Fail
Complete(write) operation failed
all threats completed. (success 0/ failed 1)
how can i fix this. please help..
please send me message @
[email protected]
facebook- fed refalbor
please. i badly need your help. i am using samsung j7 2016 (j710gn)

Fai always on installing at same way you said
Dear xdas .. I trying the same to download the firmware for the Gt-N5100 at the same steps you explain before but always failed , note that I try that to try resolve the wifi problem after last update, so cannot install firmware and that is the result of ODIN, please let me know if any result here:<ID:0/005> 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/005> Odin engine v(ID:3.1207)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

not helpful. you only flashed the recovery and not the whole system file. flashing the system file will took you a minute while the error on takes less than a second.

After i do the odin recovery it showed PASS . but after that phone tried to restart and the samsung logo came on thrice flashing and gone OFF . Now the phone is in dead mode. Please help me to help to resolve this. My phone is samsung note 2(GT7105)

hi, if i flash firmware via odin, programs and files on internal memory will erase or not? thanks

Hi, i was flashing an older version of android to my Samsung Galaxy S7 Edge, using odin, i entered all the files in Odin and it was working fine up until it was almost finished and i accidentally bumped my phone and Odin displayed a FAIL immediately... lol wow i am such a idiot. I disconnected, reconnected, tried to re-run Odin again, it told me it failed right away so theres no fixing it with Odin anymore. I tried restarting phone, i somehow got it to restart but it doesnt show samsung logo or anyting, i just see a Recovery Booting... in the top left corner of screen in tiny letters... i can get it into download mode but nothing else. I dont know what to do, somebody help me out here. How do i fix this??

Cyclone53 said:
Hi, i was flashing an older version of android to my Samsung Galaxy S7 Edge, using odin, i entered all the files in Odin and it was working fine up until it was almost finished and i accidentally bumped my phone and Odin displayed a FAIL immediately... lol wow i am such a idiot. I disconnected, reconnected, tried to re-run Odin again, it told me it failed right away so theres no fixing it with Odin anymore. I tried restarting phone, i somehow got it to restart but it doesnt show samsung logo or anyting, i just see a Recovery Booting... in the top left corner of screen in tiny letters... i can get it into download mode but nothing else. I dont know what to do, somebody help me out here. How do i fix this??
Click to expand...
Click to collapse
Hello, I got a very similar issue on my phone. I spent more than a week trying to find a solution and everytime I got a FAIL. This morning I got a PASS! here is what I did:
_ Use odin v3.12.7 with administrator priviledges.
_ In options I checked: Autoreboot, Re-Partition, F.Reset Time and Phone Bootloader Update.
_ I loaded BL, AP, CP and CSC Files (it was CSC and not Home_CSC).
_ I started the phone in transfert mode (home, volume down and start button). And then press volume up to activate the transfer mode.
_ I connected the phone to the computer and the Phone appeared in ID:COM.
_ I pressed "Start".
And this time the transfer did not fail. It took several minutes and then the phone rebooted and I got the welcome screen as good as new.
I don't know if it worked because I selected "Re-partition" and "phone bootloader update" this time or if it's because I downloaded the lastest stock rom from samsung I was able to find at present (maybe both). But I am so happy now.
Good luck to you and BE CAREFUL because Re-Partition and updating the bootloader could definitely brick your phone...

Secure boot fail
Im getting a secure boot fail after update. Ive tr8ed just AP and odin says boot fail. Phone says secure boot fail. And ive tried all ap,bl,csc,cp and i get from odin re partition fail and again on phone secure boot fail. Is there a way to maybe bypass secure boot. Oem is not optional and it will fail trying the combo rom for factory binary as well. Before the update i was ablento flash everything basically regardless of csc and verison.

Hello,
I downgrade and i tried many stock ROMs (marshmallow and lollipop) and checke all youtube videos, nothing is working. I always i got error. So i want to ask if with your instructions you managed to install stock marshmallow ROM from stock nougat on A510F just because you additionally chose "Re-Partition" and "Phone Bootloader Update" ?
Thanks.
zool_80 said:
Hello, I got a very similar issue on my phone. I spent more than a week trying to find a solution and everytime I got a FAIL. This morning I got a PASS! here is what I did:
_ Use odin v3.12.7 with administrator priviledges.
_ In options I checked: Autoreboot, Re-Partition, F.Reset Time and Phone Bootloader Update.
_ I loaded BL, AP, CP and CSC Files (it was CSC and not Home_CSC).
_ I started the phone in transfert mode (home, volume down and start button). And then press volume up to activate the transfer mode.
_ I connected the phone to the computer and the Phone appeared in ID:COM.
_ I pressed "Start".
And this time the transfer did not fail. It took several minutes and then the phone rebooted and I got the welcome screen as good as new.
I don't know if it worked because I selected "Re-partition" and "phone bootloader update" this time or if it's because I downloaded the lastest stock rom from samsung I was able to find at present (maybe both). But I am so happy now.
Good luck to you and BE CAREFUL because Re-Partition and updating the bootloader could definitely brick your phone...
Click to expand...
Click to collapse

boydee said:
That's okay! it's perfectly fine for it to FAIL!
Flash it again and copy/paste the ODIN Log here for me to see and advise on what you should do next.
Cheers! :highfive:
Click to expand...
Click to collapse
hello guys, sorry, i'm new here.. i've just faced the problem with my phone.. idk why my phone was stuck, i've tried to remove the battery and tried to restart, it seemed the same, just stuck on samsung logo. i tried to enter to recovery mode, it failed. i've tried to install the original stockrom and it's failed..
here the problem and condition:
1. stuck on samsung logo
2. can't enter recovery mode
3. only download mode can be use
i've tried the stockrom but in odin said...:
<ID:0/021> 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/021> Odin engine v(ID:3.1101)..
<ID:0/021> File analysis..
<ID:0/021> SetupConnection..
<ID:0/021> Initialzation..
<ID:0/021> Get PIT for mapping..
<ID:0/021> Firmware update start..
<ID:0/021> SingleDownload.
<ID:0/021> spl.img
<ID:0/021> NAND Write Start!!
<ID:0/021> sboot.bin
<ID:0/021> sboot2.bin
<ID:0/021> param.lfs
<ID:0/021> boot.img
<ID:0/021> recovery.img
<ID:0/021> system.img
<ID:0/021> cache.img
<ID:0/021> hidden.img
<ID:0/021> SPRDCP.img
<ID:0/021> FAIL!
<ID:0/021>
<ID:0/021> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
what should I do?
need help, please.. thanks

a few days ago my Samsung bootloop, I found a solution. Download the latest firmware for your Samsung, which is suitable for your country. enter download mode, just flash AP, later he will install and reboot. when rebooted later if it isn't mistaken it appears no modem / radio (I forgot). enter download mode again, flash CP only. then device will reboot and enter recovery default. in recovery select wipe factory. and my samsung will reset again. I hope this helps you.

hi my problem is this
<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> Added!!
<ID:0/008> Odin engine v(ID:3.1401)..
<ID:0/008> File analysis..
<ID:0/008> Total Binary size: 952 M
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<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> spl.img
<ID:0/008> sboot.bin
<ID:0/008> sboot2.bin
<ID:0/008> param.lfs
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i cant flash stock firmware for my samsung galaxy core prime, smg360hu but it stucks at system.img then fails always. help me please

Hi,
Just decided to use Odin v3.14 to update my Australian spare Samsung SM-G900iwith Indian G900IDDS1CSA1 firmware as it was a later build, seemed to proceed OK but finished with <OSM> All threads completed. (succeed 1 / failed 1.
It had previously been updated to G900IDVU1CQJ2_G900ITEL1CQJ2_G900IDVU1CQJ2_HOME.tar.md5 which was working perfectly.
<ID:0/003> Added!!
<ID:1/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/003> Odin engine v(ID:3.1401)..
<ID:1/004> Odin engine v(ID:3.1401)..
<ID:0/003> File analysis..
<ID:1/004> File analysis..
<ID:0/003> Total Binary size: 2496 M
<ID:1/004> Total Binary size: 2496 M
<ID:1/004> SetupConnection..
<ID:0/003> SetupConnection..
<ID:1/004> Initialzation..
<ID:1/004> Get PIT for mapping..
<ID:1/004> Firmware update start..
<ID:1/004> NAND Write Start!!
<ID:1/004> SingleDownload.
<ID:1/004> aboot.mbn
<ID:1/004> sbl1.mbn
<ID:1/004> rpm.mbn
<ID:1/004> tz.mbn
<ID:1/004> sdi.mbn
<ID:1/004> NON-HLOS.bin
<ID:1/004> boot.img
<ID:1/004> recovery.img
<ID:1/004> system.img.ext4
<ID:1/004> cache.img.ext4
<ID:1/004> hidden.img.ext4
<ID:1/004> modem.bin
<ID:0/003> Complete(Write) operation failed.
<ID:1/004> RQT_CLOSE !!
<ID:1/004> RES OK !!
<ID:1/004> Removed!!
<ID:1/004> Remain Port .... 1
<OSM> All threads completed. (succeed 1 / failed 1)
Click to expand...
Click to collapse
Can I retain the updated build and just use ODIN to replace what failed?
Any suggestions GREATLY APPRECIATED.
Cheerz

Hello, there is 'firmware upgrade encountered an issue' thing on my samsung. I plugged to pc and pc sees the device but odin stuck at initialzation or fail. Any suggestion?

G Morn Folks I m stuck in the same situation thought different phone mode. this is M205F. Odine FAILS @ Recovery.img
Background
Latest Stock ROM of Samsung Maisk Rooted nd TWRPed. Wanted to downgrade to ANdroid 9 from 10 after realizing severe restrictions of the latter.
Odin 14x ( wtith Chinese verbiage @ start up screen ) used and used 2 Versions of stock ROMs.
Tried AP solo & AP + HOME_CSC COmbos
Both FAIL and leave me with ocean blue screen message "an error has occured while updating the deivce software..Use he emergency recovery function in the smart switch sw." and smart switch isnt recognizing my mob either.
Where do I go from here ?

bootloop at note II logo

hi, need help with bootloop.
when I start the phone with the power button it'd restart back again after the note II logo
if I start with (power+home+VolUP), I'd get the teamwin logo, then bootloop like the case above, without even going into recovery mode
if I start with (power+home+VolDOWN), I'd get to the download mode.
I've tried to flash back to stock rom using odin. it goes without a hitch but the problem still continues.
however, i'd imagine if the flashing was done correctly and the phone's running on stock rom, shouldn't it stop showing the teamwin logo?

Try flashing the stock ROM again without auto reboot in Odin.
When you see the word reset in the Odin status window, remove the usb cable from the phone, remove the battery, replace the battery, boot into stock recovery, factory wipe, and reboot.

audit13 said:
Try flashing the stock ROM again without auto reboot in Odin.
When you see the word reset in the Odin status window, remove the usb cable from the phone, remove the battery, replace the battery, boot into stock recovery, factory wipe, and reboot.
Click to expand...
Click to collapse
nothing's changed, still cant enter recovery.
here's the log 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..
<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> hidden.img
<ID:0/004> modem.bin
<ID:0/004> recovery.img
<ID:0/004> sboot.bin
<ID:0/004> system.img
<ID:0/004> tz.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
any other ideas?

Looks like auto reboot was selected in Odin? I see it says removed towards the end.

Hi everyone! It seems that I got the same problem...
It started Yesterday when i was doing stuff and it drastically shuts down and started to bootloop.
So far I flashed a Stock ROM and nothing happened, reflashed the ROM I had ( CM12.1) with TWPR. Now I did a Repartition with Stock ROM and as you can imagine 0 good news.
I forgot to say that I can enter in Recovery and Download Mode.
Any tips?