Database Info

[Q] S6 demo unit. Odin doesn't recognise.

Bought a banged up s6 demo unit on ebay. All I want is a pocketable tablet.
The demo software keeps respawning. Even using the pass codes and resetting.
Update recovery wipe says MDM doesn't allow wipe.
I would love to just Odin a ROM but Odin doesn't recognise when plugged in download mode.
I've tried many different Odin 3.10.6 3.9 etc
Tried dev mode adb to adb push various cfroot twpr etc.
but signature not verified. I can push files like this!!
Also the USB is recognised for normal file transfer.
I can't change the recovery without root.
Can't get root without decent recovery.
What can I do? What is wrong with Odin?

Demo unit...it has antitheft measures built in to protect against theft. I'd get your money back if you can.

Just to let you know Quarzar Odin recognises my S6 demo unit. I may try to flash a custom recovery. I hope nothing goes wrong... Do I need to root first to install a custom recovery with ODIN?

quatzar said:
Bought a banged up s6 demo unit on ebay. All I want is a pocketable tablet.
The demo software keeps respawning. Even using the pass codes and resetting.
Update recovery wipe says MDM doesn't allow wipe.
I would love to just Odin a ROM but Odin doesn't recognise when plugged in download mode.
I've tried many different Odin 3.10.6 3.9 etc
Tried dev mode adb to adb push various cfroot twpr etc.
but signature not verified. I can push files like this!!
Also the USB is recognised for normal file transfer.
I can't change the recovery without root.
Can't get root without decent recovery.
What can I do? What is wrong with Odin?
Click to expand...
Click to collapse
This sounds like more of a driver issue than an Odin issue. What does your device show up as in device manager?

Is it fixable? Bricked S6 won't boot or accept ROM flashes.

Previously, I've talked about how I bricked my G920T by using an apk to try to root my phone.
Then I tried to do a factory reset with the stock recovery but it wouldn't even go into the stock recovery. So I flashed TWRP and wiped the whole phone including the system partition.
Then I tried to flash a stock 6.0.1 firmware to the phone but doing so did not improve the situation as my phone still won't boot. Even worse, when I power my phone, all I see is the blue LED indicator, no Samsung logo, nothing.
Then I tried to flash a custom ROM like XtreStoLite but that didn't fix anything either.
When I use TWRP or the stock recovery, the error "failed to mount /efs (invalid argument)" comes up on the log. I tried using the ADB method to fix it but my phone would not get recognized by ADB probably because USB debugging isn't on by default.
I cannot shut down the phone without having it charged to a power source then holding down PWR+DOWN VOLUME+HOME until the screen shuts off.
When I enter download mode, I don't see the warning screen, I enter the download mode directly.

It will warm you when you enter download. Or use TWRP and reboot into Download.Once in download flash the ROM using Odin. Get the latest one from SamFirm.
P.S. Next time root using CF Auto Root

yasteellutch said:
It will warm you when you enter download. Or use TWRP and reboot into Download.Once in download flash the ROM using Odin. Get the latest one from SamFirm.
P.S. Next time root using CF Auto Root
Click to expand...
Click to collapse
It doesn't warn me when I enter download mode, that's one of the problems.
I tried flashing the official ROM using ODIN, it still won't boot because of the efs error.

1) Download the latest SmartSwitch
2) Click on more -> Emergency software recovery and initialization
3) Go into Device initialization, enter your model name, search for it and proceed as advised by the assistant
That should fix everything, otherwise:
1) Download the latest official firmware for your model, the 4-File (or 3-File) Version
2) Use latest ODIN, check repartition in options
3) Select all the files and flash it

If EFS or DRK is corrupted, flashing roms, custom or not won`t help, it can be fixed via repair box maybe (Octoplus/Z3X)
Try to flash CF auto root for your model, if it still won`t boot, then find someone with a box to try to help you remotely or not.
But Smart Switch emergency initialization with phone sn would be the first thing I would try.

Orginator said:
1) Download the latest SmartSwitch
2) Click on more -> Emergency software recovery and initialization
3) Go into Device initialization, enter your model name, search for it and proceed as advised by the assistant
That should fix everything, otherwise:
1) Download the latest official firmware for your model, the 4-File (or 3-File) Version
2) Use latest ODIN, check repartition in options
3) Select all the files and flash it
Click to expand...
Click to collapse
Which mode should I be in when using SmartSwitch? No devices are shown when I have it plugged in during the bootup, and is so too in download mode but shows a not supported message.
brenner650 said:
If EFS or DRK is corrupted, flashing roms, custom or not won`t help, it can be fixed via repair box maybe (Octoplus/Z3X)
Try to flash CF auto root for your model, if it still won`t boot, then find someone with a box to try to help you remotely or not.
But Smart Switch emergency initialization with phone sn would be the first thing I would try.
Click to expand...
Click to collapse
How can someone with a box help me remotely?

zheyizhu said:
Which mode should I be in when using SmartSwitch? No devices are shown when I have it plugged in during the bootup, and is so too in download mode but shows a not supported message.
Click to expand...
Click to collapse
Download mode offcourse. Nevermind the not supported message.
Follow instructions from link below, I made it for such occasions:
http://forum.xda-developers.com/galaxy-s6/help/how-to-smart-switch-emergency-t3383448
zheyizhu said:
How can someone with a box help me remotely?
Click to expand...
Click to collapse
Well if you know someone who have a box, it doesn`t have to be remotely.
If not, it is possible to fix it remotely, with help of usb hub (FlexiHub or similar), tunneling (TeamViewer or similar) and box software (you connect phone to your computer, the other guy connects box to his computer, both of you are connected through a gateway to a wonderfull thing called internet, and everybody is happy ) .
Same as on site, just with few more things in between the phone, and the box.

brenner650 said:
Download mode offcourse. Nevermind the not supported message.
Follow instructions from link below, I made it for such occasions:
http://forum.xda-developers.com/galaxy-s6/help/how-to-smart-switch-emergency-t3383448
Well if you know someone who have a box, it doesn`t have to be remotely.
If not, it is possible to fix it remotely, with help of usb hub (FlexiHub or similar), tunneling (TeamViewer or similar) and box software (you connect phone to your computer, the other guy connects box to his computer, both of you are connected through a gateway to a wonderfull thing called internet, and everybody is happy ) .
Same as on site, just with few more things in between the phone, and the box.
Click to expand...
Click to collapse
The S/N sticker on the back of the phone is long gone, is there any other way I can find it besides from going into settings because I can't do that?
EDIT: I am able to borrow a friend's serial and got the firmware installed.
The Samsung boot logo is back now, however, the device still won't boot. The efs error is still there but the download mode warning sign came back.
EDIT #2: Okay, I flashed TWRP now and ADB is working once again. Can I utilize this to fix the efs error?

Help only can enter download mode sm-g955fd

Hello everyone i have a big issue on samsung s8 plus model sm-g955fd. My phone only can go to download mode
I already try to flash using 3 diffent firmware. In odin it say PASS which is mean flash was succed, but my phone wont boot up. Even boot image didnt appear, when odin said PASS it just like turn off my phone.
After flash i try to enter Recovery mode, but didnt work just black screen nothing happen. Then i try to charge the phone, but it still same, led indicator not turn on. The only way i can go is only to download mode again
Even with pit file it still have same result
Now im stuck i dont know what must i do
Does anyone have any solution please tell me i really need a help

S8+ G955F not going into download mode, only recovery mode is working,
phone had custom blocker inside, so flashed it with 'simple factory setting apk,
but now phone isn't going into download mode..
please help to find solution for this..??

I have the same issue

hi im having same kind of thing s8 plus sm.g955f son clicked a link saying viruss on phone downloaded file now wont turn on recovery safemode anything but loads to s8 plus screen an sticks can get in downloadmoad where ive tried loads says pass then same again stuck on s8plus sceen

jlnicholls1 said:
hi im having same kind of thing s8 plus sm.g955f son clicked a link saying viruss on phone downloaded file now wont turn on recovery safemode anything but loads to s8 plus screen an sticks can get in downloadmoad where ive tried loads says pass then same again stuck on s8plus sceen
Click to expand...
Click to collapse
get a fresh DL of your firmware from a reputable source and reflash it in Odin, if that doesnt work, get a fresh DL of Odin. I use sammobile.com/firmwares for my FW's and i use samfirm to download them as they literally go 4 to 5x faster on Frija or SamFirm. Frija and SamFirm are damn near the exact same thing, so its a eenie meenie miney moe thing there. But for sure use one or the other unless you dont care about a 20 min disparity LoL
if the flash with fresh FW and fresh Odin downloads dont work, try a different cable. Then a different computer. I have 7 computers and for whatever reason, one of my lappys just wont link with the target devices very well... not sure why... im sure i just havent made the proper sacrifices to the USB gods on that particular machine. purported deities aside, literally all of whose things could be the culprit... well.... minus the USB gods one, of course

Youdoofus said:
get a fresh DL of your firmware from a reputable source and reflash it in Odin, if that doesnt work, get a fresh DL of Odin. I use sammobile.com/firmwares for my FW's and i use samfirm to download them as they literally go 4 to 5x faster on Frija or SamFirm. Frija and SamFirm are damn near the exact same thing, so its a eenie meenie miney moe thing there. But for sure use one or the other unless you dont care about a 20 min disparity LoL
if the flash with fresh FW and fresh Odin downloads dont work, try a different cable. Then a different computer. I have 7 computers and for whatever reason, one of my lappys just wont link with the target devices very well... not sure why... im sure i just havent made the proper sacrifices to the USB gods on that particular machine. purported deities aside, literally all of whose things could be the culprit... well.... minus the USB gods one, of course
Click to expand...
Click to collapse
Hi, I'm new here, basically I made this account just to get help. I have the same issue, I bought my S8+ back in 2018 and never received OTA updates automatically, it's still in Nougat. Recently I decided to update the OS to Android 9 based off of Sammobile, the model number is SM-G955FD, in the Service Provider SW ver. it shows SM-G955F only(is this an issue?). I dowloaded the latest firmware for SM-G955FD with csc XTC. Now there is the other thing where the volume up button isn't working due to water getting inside, it still works. The key combination can only get me to recovery mode same with ADB, when I try to reboot to bootloader(OEM unlocked) my phone just restarts, same with ADB reboot bootloader, when I do ADB fastboot it gives a blank response. That being said I can't proceed to flash with Odin, I'm thinking of using ADB sideload but I don't know where to find the zip file or whether it's the same one I downloaded from Sammobile(pretty sure it's not).

Jonutz06 said:
Hi, I'm new here, basically I made this account just to get help. I have the same issue, I bought my S8+ back in 2018 and never received OTA updates automatically, it's still in Nougat. Recently I decided to update the OS to Android 9 based off of Sammobile, the model number is SM-G955FD, in the Service Provider SW ver. it shows SM-G955F only(is this an issue?). I dowloaded the latest firmware for SM-G955FD with csc XTC. Now there is the other thing where the volume up button isn't working due to water getting inside, it still works. The key combination can only get me to recovery mode same with ADB, when I try to reboot to bootloader(OEM unlocked) my phone just restarts, same with ADB reboot bootloader, when I do ADB fastboot it gives a blank response. That being said I can't proceed to flash with Odin, I'm thinking of using ADB sideload but I don't know where to find the zip file or whether it's the same one I downloaded from Sammobile(pretty sure it's not).
Click to expand...
Click to collapse
in cases such as yours with micro usb equipped samsungs in the past, there was a jig that you could plug in and it would automatically put t he phone into download mode. All the jig did was provide 300k ohms of resistance between 2 of the jumpers inside the micro usb port. I wasnt able to find a type c jig, but there are type c test boards that basically expose every pin in the cable into a nice wide board thatll allow for easy connection between 2 of the jumpers by hand to test it out. I did read somewhere that the newer ones require 301k ohms, but its hard to say. The usb port board is 13 bucks and a resistor is gonna be less than a buck. Maybe worth a shot since the micro usb jigs were gold

also, the only difference between the F and FD firmwares is the D is for dual sim

ich have same problem

Samsung s10 (SM-G973F) Stuck in Download mode, after normal Update.

Hey XDA Members,
Im completely new here, and found this site through google searching.
So yesterday night i updated my Samsung S10 regulary, cause i got a notification that a new update is downloadable, so i did it.
While updating, the phone crashed, and got in "Download Mode".
Since then its in download mode with the following error message in the top left corner:
ODIN MODE (AVB FAIL)
system: Hash of data does not match digest in descriptor. (3)
Root Hash in (system) : 1a32eac088, (VBMETA) : 74e6cee89
Samsung System, G973FXXSCFUH5, 42802073R
VBMETA G973FXXUCFUH3, 42324606R
I tried several things allready. Reset the phone trough holding Volume Down + Power. It just resets and goes directly back in the same screen again. Loading the Recovery mode (doesnt work).
So yeah, i hope someone here can help me
Thanks

Looks like the update you flashed isn't suitable to phone.

jwoegerbauer said:
Looks like the update you flashed isn't suitable to phone.
Click to expand...
Click to collapse
It was the normal update, that everyone gets^^

I have similar problem, though my error is:
Code:
ODIN MODE (AVB Fail)
System: Error validating footer. (6)
SAMSUNG system, 6973FXXSCFUH5, 42802073A
VBMETA 6973FXXSCFUH5, 42802073A
(Looks like i've messed up with the region when trying to flash stock Samsung firmware with newer Android version)
I've tried to download and flash another Samsung stock firmware for my region.
Although it didn't work so far through neither of the means:
Heimdall:
It says: ERROR: Protocol initialisation failed!
(Event though the very first time i was able to flash stock firmware using Heimdall; so it is not the problem with USB interface or wire or similar)
And this happens from heimdall-frontend when trying to flush whole firmware or from heimdall cli when trying to flush custom recovery.
JOdin:
This guy has some troubles with big files and constantly throws:
Code:
Exception in thread "Thread-54" java.lang.OutOfMemoryError: Requested array size exceeds VM limit
at CASUAL.communicationstools.heimdall.odin.OdinFile.extractOdinContents(OdinFile.java:145)
at CASUAL.communicationstools.heimdall.odin.Odin.getHeimdallFileParametersFromOdinFile(Odin.java:50)
at com.casual_dev.jodin.JOdinController.getHeimdallCommandFromOdinPackageList(JOdinController.java:621)
at com.casual_dev.jodin.JOdinController.access$3300(JOdinController.java:54)
at com.casual_dev.jodin.JOdinController$13.run(JOdinController.java:572)
at java.lang.Thread.run(Thread.java:745)
ADB:
Tried to sideload another Samsung firmware but it fails with similar error:
Code:
E:footer is wrong
I'm wondering what are the options now.

I finally fixed it.
The problem turned out to be the incorrect firmware region indeed.
So, first of all, i downloaded correct firmware (my region was XSG).
(Using samloader).
Then, i had to use ODIN on Windows.
There were some troubles for odin being able to recognize the phone though.
I had to manually install drivers. Also tried couple of different USB ports.
And at the end odin was able to see the phone and i flashed the stock firmware with latest Android 11.

sepo27 said:
I finally fixed it.
The problem turned out to be the incorrect firmware region indeed.
So, first of all, i downloaded correct firmware (my region was XSG).
(Using samloader).
Then, i had to use ODIN on Windows.
There were some troubles for odin being able to recognize the phone though.
I had to manually install drivers. Also tried couple of different USB ports.
And at the end odin was able to see the phone and i flashed the stock firmware with latest Android 11.
Click to expand...
Click to collapse
Could you please send me the Heimdall you use?

g465559090 said:
Could you please send me the Heimdall you use?
Click to expand...
Click to collapse
I used Odin on Win

Question HELP... PANIC MODE

OK.. so here it is in a nutshell... my S22 is soft-bricked...
I plugged my phone into my Mac (my primary computer) to back everything up. But, Smart Switch said I need to update the phone's version of Smart Switch. This was the fatal mistake. It hung the process. Over an hour later with zero movement on the progress bar I finally unplugged the phone.
Now, it is stuck in Odin mode. Well, I can boot to recovery mode. but none of the options work at all. I keep getting errors saying the partition geometry is corrupted. Normally, this would not be much of a problem, if I could mount the phone on my computers. I have a Mac, and a Forensics laptop setup with Odin3, as well as a number of other apps.
On my mac, in the Linux terminal, I cannot gain access to the device no matter what I have tried so far. I tried adb sideboot, but it cannot gain access to the device.
On the PC, the driver will not recognize the device. I updated to the newest Samsung Adroid drivers, with no joy. If I plug in my Android tablet, the driver is identified as "ssudb.sys". When I plug in my s22, the PC will not allow me to use this driver, insisting it be a .inf file. When I point it to the newest Samsung drivers, it says I am already using the best driver available, which of course does not work.
Natrually, since it is stuck in Odin mode, the s22 will not boot, so therefor I have no control over any aspect of the device.
Please help.
It is most critical I recover the /data partition. But, I would certainly like to have my phone back operational as well. I am stuck using an old s6 with very limited options in the meantime.
PLEAE HELP!
Thank you

How did it come to being bricked?

raul6 said:
How did it come to being bricked?
Click to expand...
Click to collapse
I believe he already said so, although I've never used smartswich before and I'm unsure how updating an application would cause a brick, unless I'm missing something or he meant the phone software itself needed the update and that's where things went wonky
"I plugged my phone into my Mac (my primary computer) to back everything up. But, Smart Switch said I need to update the phone's version of Smart Switch. This was the fatal mistake. It hung the process. Over an hour later with zero movement on the progress bar I finally unplugged the phone."

AthlonGFX said:
I believe he already said so, although I've never used smartswich before and I'm unsure how updating an application would cause a brick, unless I'm missing
Click to expand...
Click to collapse
It shouldn't cause brick and also software update popup comes before any operation commences

Since you can get into odin download mode, download your phones software from samfw.com or SamMobile.com and flash it with Odin.
When you download the firmware, it will be a zip file. Extract it and you'll get 5 files (starting with BL, AP, CP, CSC, and HOME_CSC)
When you're flashing with Odin, use HOME_CSC for the CSC slot and you won't wipe your data. Don't use CSC or it will wipe your data. Do not use anything for the USERDATA slot in Odin.

Odin 3 will not work. It gets stuck at setup connection. I have all the binaries, including the .pit file.
The partition information on the android is hosed.

So far, I have tried- (on Windows)
Odin 3.14.1
Odin 3.14.4
Droidkit
Fonelab
ADB sideload
Ultfone Android System Repair
Ultfone Android Data Recovery
Reiboot for Android
Android Studio (I have no idea even where to begin with this app)
And several apps on my Mac as well.
I have no joy with any attempts so far.
I finally managed to get the ddrivers installed so at least some of the apps like Odin will see the phone. But that's about it.

Also, I have a replacement phone coming tomorrow, but I still need my data- documents and imagery.

Ghostvet said:
So far, I have tried- (on Windows)
Odin 3.14.1
Odin 3.14.4
Droidkit
Fonelab
ADB sideload
Ultfone Android System Repair
Ultfone Android Data Recovery
Reiboot for Android
Android Studio (I have no idea even where to begin with this app)
And several apps on my Mac as well.
I have no joy with any attempts so far.
I finally managed to get the ddrivers installed so at least some of the apps like Odin will see the phone. But that's about it.
Click to expand...
Click to collapse
Use patched odin 3.13

kraz01 said:
Use patched odin 3.13
Click to expand...
Click to collapse
Why? What would that do that a newer version wouldn't?

Could you solve the problem? Could you at least recover your data?

No luck. Just shipped it off to Samsung with explicit instructions not to wipe the /data. I told them only to fix the partitions and not to write anything to the /data drive so I can dramatically recover the data.