I'm unable to recover to stock firmware. I use this download from the root thread but Odin gives the following errors:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> stock.recovery.tar.md5 is invalid.
<OSM> End...
how to correct md5?
Try to redownload it. Maybe it is corrupted.
Sent from my SM-T210R using xda app-developers app
Hey guys,
i have a serious phone damage/brick over here.
I can start the device only in download mode, which is probably not that bad.
Anything i flash through Odin is not working:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9195XXUCOE4_I9195OXACOE1_I9195XXUCOE4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
I tried flashing the stock firmware, only the stock recovery, firmware with pit file, because of missing pit file on phone and of course Odin 1.85, 3.09 and 3.10.7
3.09 and 3.10.7 are not working at all:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
So, is there any possibility left, or the phone really dead?
Background information: phone was working the other day and then turned black. Bootlooping for a while, and then even the visual effects (samsung logo) didn't even show up. At this point, only download mode is working.
Hope someone knows a solution, or even a possibility to check if emmc is still working?
Hi
Yesterday i installed TWRP on my Tab S4 Wi-Fi and accidentally deleted the OS.
I tried to flash it via Odin but it immediately fails.
I have switched USB cables, FW-Versions, Odin Versions and even the PC.
Odin Log:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 6291 M
<ID:0/006> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
I'm having the same issue
Also unable to install ROM via TWRP, it fails and force reboots a few seconds in
DouJinFlip said:
I'm having the same issue
Also unable to install ROM via TWRP, it fails and force reboots a few seconds in
Click to expand...
Click to collapse
I get this error even when I try to go to download mode to flash via ODIN
"Security error: this device has been flashed with unauthorized software & is locked."
r3flux said:
I get this error even when I try to go to download mode to flash via ODIN
"Security error: this device has been flashed with unauthorized software & is locked."
Click to expand...
Click to collapse
I had the same issue on my Tab S4, tried all combinations of buttons and somehow it booted to download mode.
I can get to Download mode by first rebooting into TWRP recovery, but the issue I've been having is that Odin fails to flash anything to the tablet. I've tried multiple stock ROMs and no Boot, AP, or CSC file succeeds to load.
DouJinFlip said:
Odin fails to flash anything to the tablet.
Click to expand...
Click to collapse
Make sure you have all the USB drivers installed and working. If it's not that, then try using a different version of Odin and TWRP. You will have to find the right combination between Odin and TWRP. I remember I had to do this when flashing my Samsung Note.
Also, did you make sure Developer Options > OEM Unlocking is enabled to unlock the bootloader? And that you signed out from your Google/Samsung account? When you first connect to Odin it tells you that you should do this, otherwise it will trip FRP.
I've been trying for a long time to unlock the bootloader of my SM-T210R, to install twrp and change the rom, but odin doesn't work at all.
I have already downloaded my rom stock, but it doesn't even install properly, here is the error:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> T210RUES0CQA1_T210RXAR0CQA1_HOME.tar.md5 is invalid.
<OSM> End...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> T210RUES0CQA1_T210RXAR0CQA1_HOME.tar.md5 is invalid.
<OSM> End...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T210RUEU0COI1_T210RXAR0COI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried dozens of solutions and etc., with different versions of odin and even different recoverys, but none will. There's this guy rootjunky(.com) who has made several videos with this model, so it works, but he never mentions bootloader and does not favor.
I am not a novice in this area, I had a moto g3 osprey and exchanged direct rom and kernel on it, however motorola facilitates the unlocking of the bootloader.
An important information is that it has root king root, I don't even remember how I did it, but the system status is as custom, and the rom is from the factory.
I once used odin on it and installed the rom stock to remove a flawed root, and did not delete anything, just removed the root.
Dude I'm going crazy I don't know what to do lol
I await a salvation
I made a profile just so I could respond to this. I've been searching the internet over for 6 years - so many so close, but sm-t210r will be made a fool of by no man!! I've seriously spent 100s of hours, even acquired EXTRA tablets just so I could break them in different ways. You can't put the baby back in the mother. Even with the heroics of gr8nol - t210r's true firmware remains exit only :-(
I have Samsung Galaxy Note 10+. At the back of the phone it says the model is SM-N975FD 256G. However, in the software, the model is given as SM-N976N/DSM, the CSC is N975FOXM4CTE9, CP is N976NKOU1BSLA and AP IS N976NKSU1BSLB.
This phone seems to be working with most functions, but the S-Pen has connection problems and the phone cannot connect to Samsung servers for automatic updates.
I am trying to correct this by flashing official stock firmware to ensure its does not fail to get automatic updates. I was about to flash N975F....... in an effort to match the model written at the back of the phone believing that my vendor sold me a device that was tampered with.
Will I be right to flash N975F...... replacing the N976N....?
Please help. I want a phone that is based on official firmware. Thank you in advance
Sternford said:
I have Samsung Galaxy Note 10+. At the back of the phone it says the model is SM-N975FD 256G. However, in the software, the model is given as SM-N976N/DSM, the CSC is N975FOXM4CTE9, CP is N976NKOU1BSLA and AP IS N976NKSU1BSLB.
This phone seems to be working with most functions, but the S-Pen has connection problems and the phone cannot connect to Samsung servers for automatic updates.
I am trying to correct this by flashing official stock firmware to ensure its does not fail to get automatic updates. I was about to flash N975F....... in an effort to match the model written at the back of the phone believing that my vendor sold me a device that was tampered with.
Will I be right to flash N975F...... replacing the N976N....?
Please help. I want a phone that is based on official firmware. Thank you in advance
Click to expand...
Click to collapse
SM-N975f is the Note 10+ and SM-N976n is the Note 10+ 5G.
Type *#0*# and go to version, you will see the model here.
To be one more step sure, type *#06# to see your IMEI number, then compare with the given in the box.
SubwayChamp said:
SM-N975f is the Note 10+ and SM-N976n is the Note 10+ 5G.
Type *#0*# and go to version, you will see the model here.
To be one more step sure, type *#06# to see your IMEI number, then compare with the given in the box.
Click to expand...
Click to collapse
Thank you SubwayChamp. There is indeed something fishy about this phone. The model is given as SM-N976N as mentioned earlier. However, the serial number given by *#06# is different from the serial number stuck at the back of the phone.
So my question now, which is the true model for this phone? How come it has both N975F and N976N in its firmware packages?
If I have to use 1 type of firmware, which 1 should I go for 975F or 976N?
Unfortunately, I do not have the box - I will have to hunt for it
Your assistance is most appreciated
Thank you
Sternford said:
Thank you SubwayChamp. There is indeed something fishy about this phone. The model is given as SM-N976N as mentioned earlier. However, the serial number given by *#06# is different from the serial number stuck at the back of the phone.
So my question now, which is the true model for this phone? How come it has both N975F and N976N in its firmware packages?
If I have to use 1 type of firmware, which 1 should I go for 975F or 976N?
Unfortunately, I do not have the box - I will have to hunt for it
Your assistance is most appreciated
Thank you
Click to expand...
Click to collapse
I believe the issues I am experiencing are a direct result of these mismatches. The S-PEN is not connecting and its not getting updates. I really want a phone that updates on its own automatically
Sternford said:
Thank you SubwayChamp. There is indeed something fishy about this phone. The model is given as SM-N976N as mentioned earlier. However, the serial number given by *#06# is different from the serial number stuck at the back of the phone.
So my question now, which is the true model for this phone? How come it has both N975F and N976N in its firmware packages?
If I have to use 1 type of firmware, which 1 should I go for 975F or 976N?
Unfortunately, I do not have the box - I will have to hunt for it
Your assistance is most appreciated
Thank you
Click to expand...
Click to collapse
By dialing *#06# you get the IMEI, did you see the IMEI in the back cover too, or you opened the back cover? Can you type your IMEI in a site like this https://imei.org/ or similar? And see what it throws.
If the AP and CP partitions were flashed with the firmware for N976N then I have to assume that you can incline to this firmware as they're the most important parts, probably the last user flashed the CSC for N975F to have better signal and regional compatibility.
Also, you can check in the stock recovery screen, and see which original firmware came with.
SubwayChamp said:
SM-N975f is the Note 10+ and SM-N976n is the Note 10+ 5G.
Type *#0*# and go to version, you will see the model here.
To be one more step sure, type *#06# to see your IMEI number, then compare with the given in the box.
Click to expand...
Click to collapse
I have checked the box in which I received the phone. The label shows that its SM-N975FD Samsung Galaxy Note10+. The IMEI number is the same as that returned by *#06#.
I suspect the phone was tampered with and loaded with Note10+5G firmware for some reason.
Given this scenario, can I flash this phone with Note10+ (SM-N975F). I am afraid of bricking the phone, but I just want my phone to be official.
Please assist.
Thank you
The
SubwayChamp said:
stock recovery screen
Click to expand...
Click to collapse
Checking on IMEI.org shows a Galaxy Note 10+
Also the back label and the box label shows the model SM-N975F which is again Note10+.
I am tempted to try out the Note10+ firmware. I pray that I will still have a working phone at the end of it all
Thank you very much. I will update on my progress
Sternford said:
The
Checking on IMEI.org shows a Galaxy Note 10+
Also the back label and the box label shows the model SM-N975F which is again Note10+.
I am tempted to try out the Note10+ firmware. I pray that I will still have a working phone at the end of it all
Thank you very much. I will update on my progress
Click to expand...
Click to collapse
Probably the irrefutable question, how much did you pay for? (don't tell me how much) Is it worth for a Note 10+ or for the 5G version? It might be a noticeable difference. I'm inclined to think is the N10+.
Both firmware are compatible although not totally suitable, for any of them, just may encounter some glitches or unexpected results/behavior.
Guys, I am still struggling with the problem above. I have tried to flash the Galaxy Note 10+ firmware to resolve my odd situation. I am however failing (See Log below) What could be the problem. I get the error " ....<ID:0/004> Re-Partition operation failed.....". Re-partition check box is not checked
<ID:0/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..
<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/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 9164 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Sternford said:
Guys, I am still struggling with the problem above. I have tried to flash the Galaxy Note 10+ firmware to resolve my odd situation. I am however failing (See Log below) What could be the problem. I get the error " ....<ID:0/004> Re-Partition operation failed.....". Re-partition check box is not checked
<ID:0/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..
<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/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 9164 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Use a different Odin version, a modified one like this https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/ if the problem persists probably you need to use the re-partition option as it seems your device was previously flashed with a non-proper firmware.
SubwayChamp said:
Use a different Odin version, a modified one like this https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/ if the problem persists probably you need to use the re-partition option as it seems your device was previously flashed with a non-proper firmware.
Click to expand...
Click to collapse
I took a lot of time to give feedback, I had been away and did not try the flashing until today.
Your guidance have been very helpful Subway Champ. I hope you can still be patient with me.
Unfortunately, I still cannot flash the phone. I have tried several versions of ODIN with various error messages. When I check re-partition, it takes me a step further, but still fails with an error that it cannot open a specified file.
Using Odin 13.3B_Patched
<ID:0/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..
<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/004> Odin engine v(ID:3.1303)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 9164 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Can't open the specified file. (Line: 2057)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Sternford said:
I took a lot of time to give feedback, I had been away and did not try the flashing until today.
Your guidance have been very helpful Subway Champ. I hope you can still be patient with me.
Unfortunately, I still cannot flash the phone. I have tried several versions of ODIN with various error messages. When I check re-partition, it takes me a step further, but still fails with an error that it cannot open a specified file.
Using Odin 13.3B_Patched
<ID:0/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..
<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/004> Odin engine v(ID:3.1303)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 9164 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Can't open the specified file. (Line: 2057)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Click to expand...
Click to collapse
It seems a restriction related to your PC/OS.
- Move the firmware to your main directory and rename it as simple as GN10 (for example).
- Run the tool as admin.
- Check the antivirus.
- Uncheck re-partition option.
- Use a different Windows version.
- Use a different PC.
- Try the firmware from GN10+.
- Try firmware from both models.
SubwayChamp said:
It seems a restriction related to your PC/OS.
- Move the firmware to your main directory and rename it as simple as GN10 (for example).
- Run the tool as admin.
- Check the antivirus.
- Uncheck re-partition option.
- Use a different Windows version.
- Use a different PC.
- Try the firmware from GN10+.
- Try firmware from both models.
Click to expand...
Click to collapse
Thank you. Let me try all that and see what happens. Thanks a lot
Sternford said:
Thank you SubwayChamp. There is indeed something fishy about this phone. The model is given as SM-N976N as mentioned earlier. However, the serial number given by *#06# is different from the serial number stuck at the back of the phone.
So my question now, which is the true model for this phone? How come it has both N975F and N976N in its firmware packages?
If I have to use 1 type of firmware, which 1 should I go for 975F or 976N?
Unfortunately, I do not have the box - I will have to hunt for it
Your assistance is most appreciated
Thank you
Click to expand...
Click to collapse
I believe the original case was broken and replaced with the wrong model number.
I had this problem from purchasing a unit on Ebay. When I contacted the seller, he said the case had been replaced with a different model unit and that they do this all the time. I requested and received a full refund, (primarily because the case was a little lose and did not match the model displayed on the software.