Database Users

odin error

i think i smurfed up!!!!!! i started a Odin recovery to get back to factory settings after installing the new loki mod for att and verizon bootloaders and got 2 errors. im using odin 304 and the factory .tar file for the att galaxy s4. some one please save my baby i dont know what i would do without her :crying:

novacaine86 said:
i think i smurfed up!!!!!! i started a Odin recovery to get back to factory settings after installing the new loki mod for att and verizon bootloaders and got 2 errors. im using odin 304 and the factory .tar file for the att galaxy s4. some one please save my baby i dont know what i would do without her :crying:
Click to expand...
Click to collapse
You're not offering anything for people to help you. What errors? What were you trying to Odin? What settings? What machine (PC, Mac, Linux)? Odin has a 3.07 for this, so you might try that, but otherwise, you just said "it's broke -fix it!". More information gets better answers.
And you didn't even say what or why you started this in the first place.

that would be kinda important smh.
errors
start [224, 1440]
bar [240, 1440]
it gives a third one but it blinks out faster than i can read it....it started after i attempted to flash slimbeans rom onto it. it boots all the way up to att and just sits there if anymore information is needed just ask ill give all i can to fix this problem

i got it to go odin 307 didnt fix it if any one else has this problem on windows or any system that has kies just run emergency recovery and it will fix it

novacaine86 said:
i got it to go odin 307 didnt fix it if any one else has this problem on windows or any system that has kies just run emergency recovery and it will fix it
Click to expand...
Click to collapse
I had to use KIES emergency firmware recovery. ODIN flashed fine for me after loki, but I was stuck on the samsung custom screen afterwards. The KIES emergency firware recovery did the trick. Hopefully this helps others.

[Q] Odin Keeps Failing

Hello. I have been searching for hours like a mad man on Google for a solution to my problem, but i'm having no luck. Excuse the nooby nature of this post please. So I rooted my Galaxy S4 and I am trying to get it back to stock by flashing the AT&T md5 onto my phone (Galaxy S4 SGH-I337) through ODIN and it fails every single time. Initially, with ODIN 3.07, it would return something like fail (auth). Then I tried with ODIN 1.85, but that version returns "Complete(Write) operation failed." In addition, I attempted Kies but it too failed (no specific error code), and now the phone wont boot. It says that the firmware upgrade encountered an issue. I am not able to access stock recovery or TWRP because it will automatically go to Download Mode with "Could not do normal boot" in the top left corner if I in any way attempt to access it. I am using the stock cable with USB Debugging enabled. I also tried two different computers, two different cables (one being stock of course), and tried every single usb port on both computers. What went wrong? I will give you my upmost respect if you can solve this. I also am absolutely willing to supply any information you may need. Just ask. (Please don't be bricked. Please don't be bricked)
-With kind regards, Branden.

Let me guess you had the att mf3 firmware and tried retoring by flashing the MDL firmware via odin? You said md5 so I assume mdl? You might at this point still be able to fix it visiting a best buy near you if it has a samsung center. Also att store can reflash mf3.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

Click Here throw this thread in the MF3 pile... guys we got another noob here, take a trip to your closest best buy and hope the samsung experience will flash the mf3 update for u

You mention md5, which as febby assumed I'll assume to be mdl, and twrp. Do you have mdl firmware on your phone and did you have twrp installed. Assuming you had twrp you were probably on mdl firmware. If so, I would re-download the firmware and try again. It would help if you could explain where Odin is failing too.

jd1639 said:
You mention md5, which as febby assumed I'll assume to be mdl, and twrp. Do you have mdl firmware on your phone and did you have twrp installed. Assuming you had twrp you were probably on mdl firmware. If so, I would re-download the firmware and try again. It would help if you could explain where Odin is failing too.
Click to expand...
Click to collapse
I never actually got TWRP working. I flashed it through Goo Manger and I was never able access it (It went to download mode with "Could not do normal boot" in the corner). Does this change the type of firmware I was on? In both cases of ODIN, the newer version (3.07) fails immediately after you start the process at around NAND Write start. It returns Fail (auth). In the older version (1.8.5), it reports that the write operation failed. I attached screenshots of both cases.

If you never got twrp to work then I'm almost positive you have mf3 firmware. You're best bet is best buy and have them re-flash the firmware.

Astrophysicist789 said:
I never actually got TWRP working. I flashed it through Goo Manger and I was never able access it (It went to download mode with "Could not do normal boot" in the corner). Does this change the type of firmware I was on? In both cases of ODIN, the newer version (3.07) fails immediately after you start the process at around NAND Write start. It returns Fail (auth). In the older version (1.8.5), it reports that the write operation failed. I attached screenshots of both cases.
Click to expand...
Click to collapse
There is no way to fix your problem currently so like jd1639 said, take it to best buy to the Samsung Experience area and tell them Samsung Kies firmware update fail and it did this to your phone. Thats what I did yesterday, they flashed it and I have my phone working again.

gandes said:
There is no way to fix your problem currently so like jd1639 said, take it to best buy to the Samsung Experience area and tell them Samsung Kies firmware update fail and it did this to your phone. Thats what I did yesterday, they flashed it and I have my phone working again.
Click to expand...
Click to collapse
Okay. I thank everybody for their assistance. You are very helpful people. I will head down to best buy and see what they can do for me.

Astrophysicist789 said:
Okay. I thank everybody for their assistance. You are very helpful people. I will head down to best buy and see what they can do for me.
Click to expand...
Click to collapse
Your welcome

And just so everyone knows...md5 is part of the package name I believe... (.tar.md5) or could be referring to md5 checksum...anyways as was mentioned and you acknowledged, best buy is your best bet
Sent from my SGH-I337 using Tapatalk 4

Hey guys I used oden to flash back to stock amdl and then a att update keep trying ro come threw durring the night I noticed.it downloadwd went into recovery and was on flash update I hit no instead and rebooted now I noticed my baseband changed to amdb . update is back again and I now hit remind me later is this the update witch will lockbootloader
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

ralphie1267 said:
Hey guys I used oden to flash back to stock amdl and then a att update keep trying ro come threw durring the night I noticed.it downloadwd went into recovery and was on flash update I hit no instead and rebooted now I noticed my baseband changed to amdb . update is back again and I now hit remind me later is this the update witch will lockbootloader
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Yeah it is the dreaded one! Root your device and flash a custom ROM or use titanium backup to freeze the update apps.
Sent from my SGH-I337 using Tapatalk 2

[Q] DOWNLOAD mode N9005 - 4.4.2 - UDC START?

I'm installing the new firmware but i had an issue with odin...
I flashed again 4.4.2 but in download mode, the last line you can see " UDC START" in colour red... Is this normal? I think the phone works good, but i don't know why put on this...
Anyone have this new line??

I have the same problem with a N9005 I guess it was Hong Kong version for the kanjis in the back, but is stuck in odin mode with the UDC START line

UDC Start info.
Ok gent's little more knowledge about "udc start" I am guessing that the problem became clear as you installed 4.4.2 KK.
So did I and came across UDC Start the second time I booted into download mode.
As I played around i became aware that the "UDC Start" mode locks the download loader to certain criteria. This would be 4.4.2 KK,
so anything under 4.4.2 will get a MASSIVE RED FAIL. That including the CWR/TWRP recoveries and ROOT files.
So just to specify, yes phone is now locked/bricked to 4.4.2 KK software only.
Therefore I would please like some help to get the udc start away!? If anyone can help.
If I shared some light to the darkness please say thanks.:good:

Try this out:
Worked for me on a Hong Kong 16GB N9005 which was stuck on the 'Samsung Galaxy Note 3' screen after getting a 'Invalid: ext4 image' or 'Repartioning failed' errors while installing 4.4.2 OFFICIAL (Single File ROM) via Odin.
Binary: Custom
Knox: 0x1
Method:​
In Odin mode
1. Flash the latest cf-autoroot (Kitkat support) [http://download.chainfire.eu/352/CF-...x-smn9005.zip]
2. Flash the Chenglu's latest CWM - 6.0.4.6 (the one that supports KitKat) http://forum.xda-developers.com/show....php?t=2454079
Download Sweet Rom and place it in ExtSDcard (http://forum.xda-developers.com/show....php?t=2487425)
I tried external sd-card with various format and could not install the ROM. After format my SD Card to FAT32, the ROM can be installed.
On Device
1. Boot in to Recovery mode by Volume up + Home + Power
2. Wipe Factory reset / Dalvik Cache
3. Format /System (under "mount and storage" menu) [IMPORTANT STEP]
4. Install Rom from SD Card
5. Say your prayer. You'll need it. (The installation could take sometimes. If the device screen shows Samsung boot animation, you're half way there)

How is that going to take away the udc start?

I have UDC Start in Odin/Download mode... It hasn't affected my flashing of custom ROMs nor Stock, everyone on KK has it.

Ok, but why if i try to install a previous version of TW rom 4.3 i get a massive fail?
But all the rest works?
Thanx in regards.

FdeKlerk said:
Ok, but why if i try to install a previous version of TW rom 4.3 i get a massive fail?
But all the rest works?
Thanx in regards.
Click to expand...
Click to collapse
Because you are locked into the new Bootloader (NA6) and it's unable to downgrade

So I am guessing there is no way to downgrade the boot-loader without unlocking it?

FdeKlerk said:
So I am guessing there is no way to downgrade the boot-loader without unlocking it?
Click to expand...
Click to collapse
There's no way full stop. Samsung have blocked downgrades within the bootloader itself.

Wow now that's some sort of a problem.
My 4.4.2 works but i love xposed modules to make everything transparent and as of yet kitkat does not support that.
And now i a stuck on 4.4.2..
But thanx for the assist.:good:

Same Problem with E330s
ManuH8 said:
I'm installing the new firmware but i had an issue with odin...
I flashed again 4.4.2 but in download mode, the last line you can see " UDC START" in colour red... Is this normal? I think the phone works good, but i don't know why put on this...
Anyone have this new line??
Click to expand...
Click to collapse
Hi. I have a unrooted SHV-E330 (I9506 to some) I was running the unrooted firmware and updating with Kies up until yesterday when the update to came up. I ran it as with every other update however on self rebooting the phone now goes to ODIN MODE (in red) and UDC Start (in red) i'm a root virgin and was happy with the phone running as it was AnTU TU score 36118 with the Korean bloatware running in the background. From what I have picked up after 4.3 firmware update to 4.4.2 there is no going back. I tired to root with earlier versions of firmware but get fail every time. I Picked up a zip SKT-E330SKSUCNA7 wich goes as far as checking the MD5 file successfully in Odin 3 v3.09. everywhere I look on the web it states the com box should be yellow however mine is blue.
After MD5 successful I get leave CS. I click start I get 'Get PIT for mapping. There id no PIT partion followed by a red box and the'FAIL!' box with 'all threads completed Failed 1.
I have never rooted a phone and a buff mentioned that I will not regret it. I figure thart i'm doing something wrong as there was no PIT file with the firmware.
On first trying a firmware recovery in Kies because the phone is stuck In ODIN MODE it will not recognise the phone even though the USB drivers are installed.
If their is a person out there that could talk me through rooting trough the stuck ODIN MODE I would appreciate contact.
I gather that I have no choice but to try ODIN MODE on phone as that's where the phone is stuck. Removing battery etc has been tried to death.

summan971 said:
Hi. I have a unrooted SHV-E330 (I9506 to some) I was running the unrooted firmware and updating with Kies up until yesterday when the update to came up. I ran it as with every other update however on self rebooting the phone now goes to ODIN MODE (in red) and UDC Start (in red) i'm a root virgin and was happy with the phone running as it was AnTU TU score 36118 with the Korean bloatware running in the background. From what I have picked up after 4.3 firmware update to 4.4.2 there is no going back. I tired to root with earlier versions of firmware but get fail every time. I Picked up a zip SKT-E330SKSUCNA7 wich goes as far as checking the MD5 file successfully in Odin 3 v3.09. everywhere I look on the web it states the com box should be yellow however mine is blue.
After MD5 successful I get leave CS. I click start I get 'Get PIT for mapping. There id no PIT partion followed by a red box and the'FAIL!' box with 'all threads completed Failed 1.
I have never rooted a phone and a buff mentioned that I will not regret it. I figure thart i'm doing something wrong as there was no PIT file with the firmware.
On first trying a firmware recovery in Kies because the phone is stuck In ODIN MODE it will not recognise the phone even though the USB drivers are installed.
If their is a person out there that could talk me through rooting trough the stuck ODIN MODE I would appreciate contact.
I gather that I have no choice but to try ODIN MODE on phone as that's where the phone is stuck. Removing battery etc has been tried to death.
Click to expand...
Click to collapse
Your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 'Re-partition' box in odin while flashing. Though I don't really think it will help, because your single file ROM most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
PS- You are in the wrong forums.

[COLOR=[/COLOR]
feralfire said:
your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 're-partition' box in odin while flashing. Though i don't really think it will help, because your single file rom most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
Ps- you are in the wrong forums.
Click to expand...
Click to collapse
do not tick re-partition without having a pit file, you will get a brick.
Feralfire, you just broke the first law of flashing with ODIN... If you don't know what to do then don't say anything...

Thanks for caring XDA developers - i fixed it
FeralFire said:
Your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 'Re-partition' box in odin while flashing. Though I don't really think it will help, because your single file ROM most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
PS- You are in the wrong forums.
Click to expand...
Click to collapse
Hey thanks for the response the same day I managed to fix the problem a hour ago after 24 hours of banging my head on a wall.
I uninstalled all software including Odin remembering that ODIN MODE was the only option. most of the Boot Operating system was in Korean.
I followed a you tube guide from another root and noticed that although ODIN MODE and UDC start are new (according to other forums) that the other information insinuated that the screen I was looking at was also the download mode.
I reinstalled Kies and rather than asking me for the emergency recovery code it reset and was asking for the Model and serial number. After which it stated it could not recover the device only reinstall the stock firmware. I selected OK. the phone came back to life and reinstalled all data from cloud.
now on 4.4.2 and still thinking about rooting
however I must warn anyone that comes across the unlocker website that states its mod allows for E330S root. that clockwork mod does not cater for E330S.

ultramag69 said:
[COLOR=[/COLOR]
do not tick re-partition without having a pit file, you will get a brick.
Feralfire, you just broke the first law of flashing with ODIN... If you don't know what to do then don't say anything...
Click to expand...
Click to collapse
Au contraire, I have done a lot of research on pit file and played around a lot. Check out my threads.
If you tick re-partition without having a pit, it just gives you an error. Maybe in the olden days, it might have been an issue (I haven't always been a Samsung guy), but definitely not now.

FeralFire said:
Au contraire, I have done a lot of research on pit file and played around a lot. Check out my threads.
If you tick re-partition without having a pit, it just gives you an error. Maybe in the olden days, it might have been an issue (I haven't always been a Samsung guy), but definitely not now.
Click to expand...
Click to collapse
If so, then make sure they know which version of ODIN to use as this is the fastest way to kill a phone I know...
Right from the very first this was a cardinal sin but then you didn't have a phone anymore or much sympathy either... But to tell a noob to do this was in effect saying "put your phone in front of a steamroller, it'll be ok after its gone over it a couple of times"...

ultramag69 said:
If so, then make sure they know which version of ODIN to use as this is the fastest way to kill a phone I know...
Right from the very first this was a cardinal sin but then you didn't have a phone anymore or much sympathy either... But to tell a noob to do this was in effect saying "put your phone in front of a steamroller, it'll be ok after its gone over it a couple of times"...
Click to expand...
Click to collapse
He was using 3.09. Don't overcomplicate things.
But anyway, I apologize for making people put their phones in front of 20 ton vehicles.

re Pit File
FeralFire said:
Your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 'Re-partition' box in odin while flashing. Though I don't really think it will help, because your single file ROM most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
PS- You are in the wrong forums.
Click to expand...
Click to collapse
I found this KS01LTE_KOR_SKT_32G.pit and ran it in Odin running download mode and it worked. It appears there are several Korean versions of the right ROM and unless the right rom is used flash in odin does not work.
I'm starting to sound like i know what i'm talking about!

summan971 said:
I found this KS01LTE_KOR_SKT_32G.pit and ran it in Odin running download mode and it worked. It appears there are several Korean versions of the right ROM and unless the right rom is used flash in odin does not work.
I'm starting to sound like i know what i'm talking about!
Click to expand...
Click to collapse
The different ROMs must have different pits. That would explain why only some specific ones work.
Anyway, congratulations.

Flash problem? PIT? Bricked

Hi all,
Over the weekend my phone died in my hands, it was on charge (low battery), turned off and wouldn't turn on again. It just displays the Samsung Galaxy Note logo and never gets passed that.
I tried to get into recovery CWM is installed) and I get MMC: mmc_read fail and Moviand Checksum Confirmation Fail.
I've tried to upload a PIT as Odin reports that there is no PIT partition - I'm using a few .pits I've found on the forum and am trying to use these (I'll attach one) and also using the ROM from SamMobile - I believe this is the correct one. My sim is Everything Everywhere but the phone is unlocked so I picked the United Kingdom one. N9005XXUGNG1_N9005OXAGNJ3_N9005XXUGNG1_HOME.tar
However when I add the PIT to Odin and the tar to "PDA" in Odin I get "There is no PIT partition":
and on the screen itself in Download Mode gives these errors:
MMC: mmc_read fail
ODIN: flash read failure
SECURE CHECK FAIL: PIT
What am I doing wrong here? Could the hardware have failed... I'm not even that bothered about the phone itself, I just really want to try and get the data off it - but don't think there is a way to do this without booting into a ROM or at least recovery to use ADB.
Any help would be appreciated!

I know how you feel
oli356 said:
Hi all,
Over the weekend my phone died in my hands, it was on charge (low battery), turned off and wouldn't turn on again. It just displays the Samsung Galaxy Note logo and never gets passed that.
I tried to get into recovery CWM is installed) and I get MMC: mmc_read fail and Moviand Checksum Confirmation Fail.
I've tried to upload a PIT as Odin reports that there is no PIT partition - I'm using a few .pits I've found on the forum and am trying to use these (I'll attach one) and also using the ROM from SamMobile - I believe this is the correct one. My sim is Everything Everywhere but the phone is unlocked so I picked the United Kingdom one. N9005XXUGNG1_N9005OXAGNJ3_N9005XXUGNG1_HOME.tar
However when I add the PIT to Odin and the tar to "PDA" in Odin I get "There is no PIT partition":
and on the screen itself in Recovery Mode gives these errors:
MMC: mmc_read fail
ODIN: flash read failure
SECURE CHECK FAIL: PIT
What am I doing wrong here? Could the hardware have failed... I'm not even that bothered about the phone itself, I just really want to try and get the data off it - but don't think there is a way to do this without booting into a ROM or at least recovery to use ADB.
Any help would be appreciated!
Click to expand...
Click to collapse
Hi Oli,
I've had the same issue a few months ago on my pretty much brand new N3, Canadian. I tried a few "PIT" files as well, with no success! My solution, can't recommend to you, was to install i.e. Slimkat ROM or CM11. I'm never concerned about data partition as I can always drop my MP3s once I'm able to boot into the OS. All important ROMs, Gapps and Apps are on EXT SD card .
So, that was my last resort to bring the N3 back to life. I have flashed a few TW based ROMs after, and it was all well.
But honestly, (someone else confirm this) you can "dirty" flash AOSP based ROM without wiping data partition. In other words when you think about what I did, that's what fixed the problem. I wish you nothing but good luck!
Are you even able to get to CWM recovery point? I do NOT remember if mine was broken, TWRP, that is.
Kind regards,
Sonny B.

Hi Sonny B
Unfortunately I can't boot into CWM recovery as I get this:
MMC: mmc_read fail and Moviand Checksum Confirmation Fail.
As far as I know though right CM11/Slimkat can't be installed from Odin so I would need to be in TWRP or CWM which I can't get to
I guess I need to know why I can't push the PIT file from Odin... if this works then hopefully I can install CWM recovery and get somewhere.
Thanks

My, My...
oli356 said:
Hi Sonny B
Unfortunately I can't boot into CWM recovery as I get this:
MMC: mmc_read fail and Moviand Checksum Confirmation Fail.
As far as I know though right CM11/Slimkat can't be installed from Odin so I would need to be in TWRP or CWM which I can't get to
I guess I need to know why I can't push the PIT file from Odin... if this works then hopefully I can install CWM recovery and get somewhere.
Thanks
Click to expand...
Click to collapse
Oli, oli...
If I could just remember what I've done in my case. I don't think I ever received that many "serious" error messages when my phone was down. I honestly think that my recovery was not broken, therefore I was able to install custom ROM, when original stock ROM was not working for me!
I'll definitely keep my eye on this thread. Don't give up please! I hope seasoned kanger can chime in here with a solution.
Good luck,
Sonny B.

sonny_b_bih said:
Oli, oli...
If I could just remember what I've done in my case. I don't think I ever received that many "serious" error messages when my phone was down. I honestly think that my recovery was not broken, therefore I was able to install custom ROM, when original stock ROM was not working for me!
I'll definitely keep my eye on this thread. Don't give up please! I hope seasoned kanger can chime in here with a solution.
Good luck,
Sonny B.
Click to expand...
Click to collapse
Given up for now - just getting no where and out of ideas on how to get this to work.
Can't flash a ROM because no PIT is found but then I can't re-partition with the PIT either =/

After trying more PIT files and ROMS from different sources I have well and truly given up. I've requested the phone to be recycle so at least I can get some money for it

I used to the same problem this summer you should try reflashing a stock rom with odin

o-ellinas said:
I used to the same problem this summer you should try reflashing a stock rom with odin
Click to expand...
Click to collapse
Tried a few now from Samsmobile and other sites but just get the message about no PIT partition.

http://www.galaxynote3update.com/fi...-the-unbrick-and-recovery-guide-just-for-you/
Check this out

Thanks but its unfortunately just the same as every other help guide They all seem to suggest that if you can get into download mode then it's possible to fix the phone but after trying so many different stock ROMs from different sources and using the PIT file.. it's just not happy.
Reluctant to recycle the phone though based on the fact that I keep reading that it can be fixed...

Samsung Galaxy J3 2016 Firmware hidden.img stuck

Hello there,
I recently tried to get Android 10 onto my old phone. But i already got stuck on trying to root it. First I could not install new firmware because of FAP lock.
Then when I tried to get around the lock, I tried to root the phone with this tutorial. But Odin failed at hidden.img. Several times. And now I am stuck with "Firmware upgrade encountered an issue Select recovery mode in Kies".
I tried flashing with deleted hidden.img - it does not work. When I add an .md5 extension, Odin says binary invalid. When I remove the ".md5", Odin just crashes.
Any ideas?
If it is somehow important: I once rooted this device, but for some update or app, idk, i went back to normal, I dont really remember. I use Windows 10.
Thanks

tHr4sh3R said:
Hello there,
I recently tried to get Android 10 onto my old phone. But i already got stuck on trying to root it. First I could not install new firmware because of FAP lock.
Then when I tried to get around the lock, I tried to root the phone with this tutorial. But Odin failed at hidden.img. Several times. And now I am stuck with "Firmware upgrade encountered an issue Select recovery mode in Kies".
I tried flashing with deleted hidden.img - it does not work. When I add an .md5 extension, Odin says binary invalid. When I remove the ".md5", Odin just crashes.
Any ideas?
If it is somehow important: I once rooted this device, but for some update or app, idk, i went back to normal, I dont really remember. I use Windows 10.
Thanks
Click to expand...
Click to collapse
there is no Android 10 available for this phone

2gg1 said:
there is no Android 10 available for this phone
Click to expand...
Click to collapse
Well thank you, but that not helping with the issue that i cannot flash my phone with stock rom via odin.

tHr4sh3R said:
Well thank you, but that not helping with the issue that i cannot flash my phone with stock rom via odin.
Click to expand...
Click to collapse
So you have download the samsung drivers? Unzipped the file with result of a .md5 file? connected your phone to the pc with download mode? And then putted the file on the AP section? And clicked start?
Everything i just mentioned (except the .md5) can you find on HighOnAndroid website. Try to get the odin from there.
Please reply if it worked

2gg1 said:
So you have download the samsung drivers? Unzipped the file with result of a .md5 file? connected your phone to the pc with download mode? And then putted the file on the AP section? And clicked start?
Everything i just mentioned (except the .md5) can you find on HighOnAndroid website. Try to get the odin from there.
Please reply if it worked
Click to expand...
Click to collapse
Well yes, I already did all you described, but did not get it from HighOnAndroid (I also tried, but the "samsung drivers" are Malware which is blocked by Windows, so...).
I know how to flash a phone. It just does not work because of some weird Error with the hidden.img. I also saw a ton of other people trying to flash their phone with this Error, but their solutions do not work. So I need someone with another solution.

tHr4sh3R said:
Well yes, I already did all you described, but did not get it from HighOnAndroid (I also tried, but the "samsung drivers" are Malware which is blocked by Windows, so...).
I know how to flash a phone. It just does not work because of some weird Error with the hidden.img. I also saw a ton of other people trying to flash their phone with this Error, but their solutions do not work. So I need someone with another solution.
Click to expand...
Click to collapse
Try get the samsung drivers from samsungs official website

I once again tried it with these drivers. No change.
I just want to tell you, that I am no idiot and I know how to flash a phone. It just is a very specific problem, that occurs a lot apparently: https://www.youtube.com/results?search_query=flash+galaxy+hidden.img+stuck
The problem is, that the solutions posted on Youtube and other places do. not. work. As I explained in my starting post.