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.

[Q] Black Screen of Death after flashing Stock-Rom with Odin

Hi everybody,
i have same problems with the Stock-Rom of Lolipop with VD2-Branding.
ODIN has faild with:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T805XXU1BOCC_T805VFG1BOC4_T805XXU1BOC1_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> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> 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)
Now i have a "Black Screen of Death".
The ROM: VD2-T805XXU1BOCC-20150403134302.zip
Odin: 3.10.6
Hardware: Samsung Galaxy Tab S LTE 16GB (SM-T805) from Vodafone D2 Germany
Flashing with TWRP also failed. Is it possible, that i use the wrong image?
Edit: Now it works, but the way was very terrible. Odin flashing till error. Following this i have flash the Recovery TWRP. Now the Tablet has booted, but i disbelieve it works fine.
Can someone help me to install the offiicial Rom correctly?
Thanks a lot and have a nice day!
best regards masterkifke

Masterkifke said:
T805XXU1BOCC_T805VFG1BOC4_T805XXU1BOC1_HOME.tar.md5
Click to expand...
Click to collapse
Masterkifke said:
VD2-T805XXU1BOCC-20150403134302.zip
Click to expand...
Click to collapse
Masterkifke said:
Hardware: Samsung Galaxy Tab S LTE 16GB (SM-T805) from Vodafone D2
Click to expand...
Click to collapse
Does your SM-T805 have a letter after the model? Like C, M, W or Y?
If not, then when I search www.sammobile.com for your firmware, this is the download file name I find that you should be using. I am not sure what the file name will be after extracting the zip though. Would take five hours of downloading for me to find out.
But if you compare this name to the file you originally downloaded and it is the same, then I think you are flashing the correct firmware.
T805XXU1BOCC_T805VFG1BOC4_VD2.zip

Ignore the error then boot into recovery and wipe cache.
Job done.

Thanks for help.
The device comes without an extension like C , M, W or Y and the ROM is from sammobile. So i think the ROM is correct.
But the problem is after flashing and getting the error, i don't have any access to recovery and for wipe the cache -> POWER + VOLUME UP + HOME goes directly into "Back Screen of Death".
So i must install TWRP before.
But my target is to the device bringing back into factory state.
At the moment it works fine.
Thank you for help.
best regards from germany
masterkifke

It won't boot if you don't have a valid recovery installed. Flashing stock firmware always installs stock recovery.
So either reflash stock firmware, flash stock recovery or flash twrp.
However I can quite clearly see from your first post that recovery has flashed fine, so it seems the problem is you are not using the right timing and button combo to enter recovery mode.
Many people have encountered the hidden.img fail when flashing a different region firmware as its csc specific.
All you need do to solve it is enter recovery mode and wipe cache.

HELP! Galaxy S6 (SM-G920P) (SOLVED)

I recently rooted my device. I had uninstalled superSU on accident. I reinstalled and it said it couldn't update the binary. I then prompted to try to run the root again. It failed and reboot except this time my phone now reboots in maybe 1-2 minutes and it seems the cell service wont start either. I tried safe mode and the same issue. It would reboot in 1-3 minutes. I factory reset and wiped the cache several times. Currently downloading stock firmware to try to flash via odin. Any suggestions on fixing it?
UPDATE
Was able to flash stock 5.1.1. Even stock firmware, still rebooted every minute even in safe mode.
Ended up flashing stock 5.1.1 and run the same root and also flash twrp to the device. Nonetheless It still reboots every minute, even in safe mode. Below is the recovery.txt and also attached is a photo of where it's stuck because of rebooting. I swear it's something with the cellular...
recovery.txt
Where it stuck due to rebooting every minute
Update 2
The reboot does not occur in twrp or download mode
Update 3
Following Koops second method
1) Return to Stock via TAR.
2) Install TWRP via Odin.
3) From TRWP do an Advanced Wipe - Dalvik Cache, Cache, Data and Internal Storage. (That is as complete a wipe as I know how to do.)
4) Go back to Stock via TAR.
Click to expand...
Click to collapse
After the stock flash, booting up hangs on the sprint loading screen, dims, then restarts (only first time star. then ting up after flash) goes through setup, but again reboots every minute. The bars at the top sometime show up and sometime don't show up.
Also every reboot, i turned on voice assistant and "system update" is said every time.
At this point im open to any suggestions. If it's not fixed today ill most likely have to go buy an s5 off of amazon.
UPDATE
Got the phone through setup. Baseband and software version is unknown and notification of "Checking device status" is constant. Even after flashing stock 5.1.1. After about a minute, the device status becomes official.
Might try this:
technobezz.com/fix-samsung-galaxy-unknown-baseband-version/
UPDATE
forum.hovatek.com/thread-116.html
Tried using these methods to fix the baseband issue yet still havent fixed it.
UPDATE Finale
For some reason Koops stock firmware didn't work with my phone. I'e uploaded the firmware that did in case others run into the same issue.
mediafire.com/download/c55xaeb7geq0i2d/G920PVPU3BOJ7_G920PSPT3BOJ7_SPR.zip
Thank you everyone who helped!
Pictures of device info added below for specific info
Also if it helps I had flashed twrp before anything. I forget specifically if I did anything in twrp that may have helped or not.
http://imgur.com/vUmjfbX
http://imgur.com/CXql8Li
http://imgur.com/2dUJ1om

x1xmadex1x said:
I recently rooted my device. I had uninstalled superSU on accident. I reinstalled and it said it couldn't update the binary. I then prompted to try to run the root again. It failed and reboot except this time my phone now reboots in maybe 1-2 minutes and it seems the cell service wont start either. I tried safe mode and the same issue. It would reboot in 1-3 minutes. I factory reset and wiped the cache several times. Currently downloading stock firmware to try to flash via odin. Any suggestions on fixing it?
Click to expand...
Click to collapse
Flash back to stock via Odin and install twrp then flash THIS version of SuperSU. Unlike the normal version, this one will not install in the system thus lowering the risk of breaking your device(s)

Flash failed
I tried flashing stock:
<ID:0/005> 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/005> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
on phone: SW REV. Check Fail Device: 3,Binary: 1
Any input?
Edit Only had "AP" selected in odin...fairly new to droid...how would I go about fixing this hodgepodge of a mess

Try this TAR, it is the latest:
https://www.androidfilehost.com/?fid=24343351889231947
OCF, which failed for for, is 5.02 from May. The one above is 5.11 from December.

Still rebooting
I flashed the newest one, the one linked and yet it still reboots after about a minute...cant get past the "Optimizing app" part now...it reboots before it can finish.
It seems like it reboots when trying to get signal....my bars come up but no reception..then just reboots...

Helpful info?
If it helps, I used this to root it:
autoroot.chainfire.eu
samsung SM-G920P zerofltespr zerofltespr universal7420 exynos5 LMY47X.G920PVPU3BOJ7 5.1.1
Like i said i uninstalled super su, reinstalled, than ran that through odin again and it crashed.

x1xmadex1x said:
I tried flashing stock:
<ID:0/005> 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/005> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
on phone: SW REV. Check Fail Device: 3,Binary: 1
Any input?
Edit Only had "AP" selected in odin...fairly new to droid...how would I go about fixing this hodgepodge of a mess
Click to expand...
Click to collapse
What do you have ticked under options?

1619415 said:
What do you have ticked under options?
Click to expand...
Click to collapse
It successfully flashed the samsung Official
sm-G920P
I checked the "AP" and used the latest 5.1.1 previously linked and in options I had auto-reboot and F-Reset Time ticked

x1xmadex1x said:
It successfully flashed the samsung Official
sm-G920P
I checked the "AP" and used the latest 5.1.1 previously linked and in options I had auto-reboot and F-Reset Time ticked
Click to expand...
Click to collapse
Try doing it this time without rooting

1619415 said:
Try doing it this time without rooting
Click to expand...
Click to collapse
Second time flashing stock 5.1.1 which was previously linked thanks to koop1955.
G920PVPU3BOL1_G920PSPT3BOL1_G920PVPU3BOL1_HOME.tar.MD5
-First time was successful but nonetheless have the same issue; Continuous reboot after about a minute being on.
-Second time flashing the 5.1.1 stock with "AP" checked and in options "Auto-reboot" and "F. Reset Time" checked.
Log from odin below:
<ID:0/006> 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/006> Odin engine v(ID:3.1100)..
<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> 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> modem.bin
<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)
Yet I am still getting the same issue: rebooting about every minute to being turned on

koop1955 said:
Try this TAR, it is the latest:
https://www.androidfilehost.com/?fid=24343351889231947
OCF, which failed for for, is 5.02 from May. The one above is 5.11 from December.
Click to expand...
Click to collapse
Correct tar and successful, but doesnt solve my problem...still rebooting a minute to being turned on even in safe mode

Updated main

Does it do this while in download mode and TWRP (not plugged in)? To me it sounds like maybe the battery is bad...

1619415 said:
Does it do this while in download mode and TWRP (not plugged in)? To me it sounds like maybe the battery is bad...
Click to expand...
Click to collapse
No, it does not happen in twrp or download mode (plugged in or not plugged in)...I just got the galaxy s6 less than a month ago

I am having a very similar issue, can't seem to figure out how to fix it.

x1xmadex1x said:
No, it does not happen in twrp or download mode (plugged in or not plugged in)...I just got the galaxy s6 less than a month ago
Click to expand...
Click to collapse
When I first got mine, it had a battery problem and I brought it to Sprint and they gave me a new one right there for free.... Mine would power off every hour because it couldn't hold a charge.

1619415 said:
When I first got mine, it had a battery problem and I brought it to Sprint and they gave me a new one right there for free.... Mine would power off every hour because it couldn't hold a charge.
Click to expand...
Click to collapse
My knox counter is tripped and the galaxy s6 doesnt have a removeable battery...it says it has a charge..i dont think the battery is the issue...

x1xmadex1x said:
Second time flashing stock 5.1.1 which was previously linked thanks to koop1955.
G920PVPU3BOL1_G920PSPT3BOL1_G920PVPU3BOL1_HOME.tar.MD5
-First time was successful but nonetheless have the same issue; Continuous reboot after about a minute being on.
-Second time flashing the 5.1.1 stock with "AP" checked and in options "Auto-reboot" and "F. Reset Time" checked.
Log from odin below:
<ID:0/006> 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/006> Odin engine v(ID:3.1100)..
<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> 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> modem.bin
<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)
Yet I am still getting the same issue: rebooting about every minute to being turned on
Click to expand...
Click to collapse
After it flashes, boot to STOCK recovery and perform a data wipe/factory reset. My guesses are you have stale leftovers from previous ROM/build and the system can't find what it is looking for and terminates.

Last hope if everything else has failed:
1) Return to Stock via TAR.
2) Reboot to recovery (Stock) and do a factory reset.
See if that fixes it. If not -
1) Return to Stock via TAR.
2) Install TWRP via Odin.
3) From TRWP do an Advanced Wipe - Dalvik Cache, Cache, Data and Internal Storage. (That is as complete a wipe as I know how to do.)
4) Go back to Stock via TAR.
DO NOT USE THE CHAINFIRE SUPERSU ANYMORE. That seems to have caused problems.

koop1955 said:
Last hope if everything else has failed:
1) Return to Stock via TAR.
2) Reboot to recovery (Stock) and do a factory reset.
See if that fixes it. If not -
1) Return to Stock via TAR.
2) Install TWRP via Odin.
3) From TRWP do an Advanced Wipe - Dalvik Cache, Cache, Data and Internal Storage. (That is as complete a wipe as I know how to do.)
4) Go back to Stock via TAR.
DO NOT USE THE CHAINFIRE SUPERSU ANYMORE. That seems to have caused problems.
Click to expand...
Click to collapse
Thank you, will try that in a little.
What about a "PIT" file?

[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?