Database Develop

Need help flashing Dok2

Can someone help me out here? I am suffering from the major lagging and freezing with my Note 4 and i contacted Samsung about it. They told me to visit a local Samsung store and they can check out my phone, but i want to be back to stock before taking it in. Last night I tried to Odin back to stock Dok2 for roughly 4 hours and i couldnt get it accomplished. Am i missing something? I tried 3 different versions of Odin and downloaded 2 diffrent copies of the Dok2 firmware, but still no luck. Is there a specific processto follow? I tried factory resetting the phone before odin flashing, I even clean wiped the phone in Odin deleting internal storage as well.
Please help!

Anyone??????

Did you download Odin and DOK2 from sammobile? I was able to flash my phone with the downloads from there. I would double check and make sure you are using the stock samsung USB cable that came with your phone.
I'm having the exact same freezing and lockup issues as you are, by the way.

I dont beleive my odin and firmware came from sammobile, so i will give that a shot. I did make sure to use the samsung usb cable. I guess i need to make sure it was my usb cable and not my wife's S4 cable. Not sure if that makes a difference.

Ok. I still can't odin flash Dok2. I downloaded the new version on Odin from Sammobile and downloaded a copy od Dok2 (full) from a link to Mega. I couldn't get the sammobile link to work.
Any other suggestions?

It's possible that your DOK2 file might be corrupted or something. Try giving this one a shot, http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 to download the firmware. Input your phone model, set region to TMB, place check mark on "auto" box, and place a check mark on the "decrypt automatically" box. Click on "Check Update" and download. Don't worry about the .enc4 extension on the file name, once its done downloading and decrypting you will get a .zip file of the firmware.

I tried downloading the SamFirm program from the link you provided above, but I get an error in the program stating: "Could not load file or assembly "Microsoft.WindowsAPICodePack.Shell. Version= 1.10.0. Maybe this is because I am running Windows 10.

OK, problem solved. I downloaded Kies 3 and was able to restore to DOK2 using it.

Gjohnson7771 said:
OK, problem solved. I downloaded Kies 3 and was able to restore to DOK2 using it.
Click to expand...
Click to collapse
Can you elaborate on this Kies 3, I'm stuck I the same issue and I cant get back to Stock ROM for Note 4

Sure. Kies 3 is the Samsung software for recovery and updates. You should be able to just Google Kies 3 and download.

Gjohnson7771 said:
Sure. Kies 3 is the Samsung software for recovery and updates. You should be able to just Google Kies 3 and download.
Click to expand...
Click to collapse
So use Kies 3 as opposed to using Odin to flash the fw?

That's the only way I was able to flash Dok2 again. I tried at least 20 times in Odin and it failed everytime. I'm still having issues on Dok2, I wish I could flash back to Cod6.

N920F (N920T apparently) stuck in the bootloop. Help me out and have a beer, or two!

Hi there!
So my Note 4 died on my eyes and it was greatly missed. So I decided to buy Note 5 and got one. Old one was running Cyanogenmod for 3 years without a fail.
Did not read about releases in Europe. Apparently there is no m920F. Download mode said it is N920T.
Things I've done:
Installed TWPR (TWRP-3.0.2-1-G928T-N920T) with Odin (Heimdall used for PIT file).
Checked was it installed - reboot. Then bootloop started.
Tried to flash a couple of firmware ROMS thrugh Odin. No luck.
Used ADB to transfer firmware rom downloaded from Sammobile. Tried to flash with TWRP. Got "coulnd't find META-INF/com/google/android/update-binary in the zip file"
Things I haven't done:
No backup.
Did not check OEM unlock.
Did not spend a day reading how to do it properly.
It's been a while since my last encounter with custom roms and installing them. I spent all night trying different things, to no avail.
I appreciate the fact that this is common and quite boring issue, so I'm offering a tenner ing GBP (PayPal transfer) for whoever will make my phone work again

I tried again to flash with TWRP to check for exact error this time. But it turns out, that the file with firmware pushed previously is not there any more.
Firmware downloaded is a read-only zip file, so I can't flash it with Odin either.
Tried adb sideload and got the same error - could not find meta-inf/com/google/android/update-binary.
Any ideas, please?

lukja123 said:
I tried again to flash with TWRP to check for exact error this time. But it turns out, that the file with firmware pushed previously is not there any more.
Firmware downloaded is a read-only zip file, so I can't flash it with Odin either.
Tried adb sideload and got the same error - could not find meta-inf/com/google/android/update-binary.
Any ideas, please?
Click to expand...
Click to collapse
First of all see if ur phone can get into download mode. If YES and since your phone is 920T then download the latest firmware from sammobile. Extract the files inside the folder and flash firmware using ODIN method & try.

maheshhtc said:
First of all see if ur phone can get into download mode. If YES and since your phone is 920T then download the latest firmware from sammobile. Extract the files inside the folder and flash firmware using ODIN method & try.
Click to expand...
Click to collapse
Yes I can get into the download mode.
I read some posts on sammobile and the problem with unziping the zip file might be connected with slow download, resulting in corrupted file.
I'll give it a try after work.
Thanks!

Ok. Better download during night time after 11pm. Those time the internet speed is high. Day time is not good for downloading.
Sent from my [device_name] using XDA-Developers Legacy app

Still no luck with downloading a file that is not corrupted. I managed to unzip it with winzip, but then Odin says the file is corrupted.
I've dowloaded a file from a different website, that unzips normally (previously couldnt unzip - winzip worked though), but it is not one file. There is AP, BL, CP and CSP. Firmware number corresponds with that on the sammobile.
Should I give it a go?

A corrupted file was detected. In order to continue, you must select a valid Odin File - that's what Odin says.
Can this have anything to do with Odin, well really JOdin3 being on MacOs?

pm

lukja123 said:
Hi there!
So my Note 4 died on my eyes and it was greatly missed. So I decided to buy Note 5 and got one. Old one was running Cyanogenmod for 3 years without a fail.
Did not read about releases in Europe. Apparently there is no m920F. Download mode said it is N920T.
Things I've done:
Installed TWPR (TWRP-3.0.2-1-G928T-N920T) with Odin (Heimdall used for PIT file).
Checked was it installed - reboot. Then bootloop started.
Tried to flash a couple of firmware ROMS thrugh Odin. No luck.
Used ADB to transfer firmware rom downloaded from Sammobile. Tried to flash with TWRP. Got "coulnd't find META-INF/com/google/android/update-binary in the zip file"
Things I haven't done:
No backup.
Did not check OEM unlock.
Did not spend a day reading how to do it properly.
It's been a while since my last encounter with custom roms and installing them. I spent all night trying different things, to no avail.
I appreciate the fact that this is common and quite boring issue, so I'm offering a tenner ing GBP (PayPal transfer) for whoever will make my phone work again
Click to expand...
Click to collapse
1. use samsung smart switch software...connect ur ph with pc...click more menu....click on emergency software recovery...hope ur phone get the official firmware for ur phone
2. plz send the pic of back side of ur phone(where the serial no model no displayed on phone)..& the pic of the box of ur phone

only official binaries are allowed to be flashed

Why my samsung s10 exynos shows "only official binaries are allowed to be flashed"after my first reboot after root?
I only use magisk.

Root
[email protected] said:
Why my samsung s10 exynos shows "only official binaries are allowed to be flashed"after my first reboot after root?
I only use magisk.
Click to expand...
Click to collapse
Hi, you did something wrong in the critical part of the rooting process going to guess and say it was the main reboot after odin flash.
Had this issue 3 times, the best would be to follow this root process and READ everything line for line.
You'd be supersized that the smallest thing you've missed may have caused it.
To fix it, download original software for your model and country from SamMobile or any other form - use this software: https://forum.xda-developers.com/galaxy-s9/how-to/tool-frija-samsung-firmware-downloader-t3910584
Remember DO NOT DELETE THE .md5 from the file name after you've extracted it.
Root + TWRP Link: https://forum.xda-developers.com/showpost.php?p=79914231&postcount=125

fdeklerk said:
hi, you did something wrong in the critical part of the rooting process going to guess and say it was the main reboot after odin flash.
Had this issue 3 times, the best would be to follow this root process and read everything line for line.
You'd be supersized that the smallest thing you've missed may have caused it.
To fix it, download original software for your model and country from sammobile or any other form - use this software: https://forum.xda-developers.com/galaxy-s9/how-to/tool-frija-samsung-firmware-downloader-t3910584
remember do not delete the .md5 from the file name after you've extracted it.
Root + twrp link: https://forum.xda-developers.com/showpost.php?p=79914231&postcount=125
Click to expand...
Click to collapse
thank you very much

flash stock rom AP file to fix this issue and remember to flash CSC too

[email protected] said:
Why my samsung s10 exynos shows "only official binaries are allowed to be flashed"after my first reboot after root?
I only use magisk.
Click to expand...
Click to collapse
Something has gone wrong with your rooting, happened to me once.
Press and hold Volume-down, Bixby and Power button, connect phone with USB to PC, wait, release all buttons soon as Download screen appears. Now flash with stock firmware and start rooting from scratch.

FdeKlerk said:
Hi, you did something wrong in the critical part of the rooting process going to guess and say it was the main reboot after odin flash.
Had this issue 3 times, the best would be to follow this root process and READ everything line for line.
You'd be supersized that the smallest thing you've missed may have caused it.
To fix it, download original software for your model and country from SamMobile or any other form - use this software: https://forum.xda-developers.com/galaxy-s9/how-to/tool-frija-samsung-firmware-downloader-t3910584
Remember DO NOT DELETE THE .md5 from the file name after you've extracted it.
Root + TWRP Link: https://forum.xda-developers.com/showpost.php?p=79914231&postcount=125
Click to expand...
Click to collapse
So the same thing happened to me too while rooting my device so I tried to flash my device no matter what I do it won't flash sometimes the Odin gets stuck and sometimes it shows the process failed,I"be been trying to unbrick my phone from a week now but nothing seems to really work,so help if you can,thank you!

surajismarcus said:
So the same thing happened to me too while rooting my device so I tried to flash my device no matter what I do it won't flash sometimes the Odin gets stuck and sometimes it shows the process failed,I"be been trying to unbrick my phone from a week now but nothing seems to really work,so help if you can,thank you!
Click to expand...
Click to collapse
Hi, Ok the best way to do so is to get hold of stock firmware for your device.
Try this: https://forum.xda-developers.com/s10-plus/how-to/tool-frija-samsung-firmware-downloader-t3910594
Then secondly you will need the PIT file of your device !IF YOU BREAK YOUR PHONE IT IS NOT MY RESPONSIBILITY! :https://zfirmware.com/samsung-galaxy-s10-plus-g975-repair-firmware/
Make sure that when you select BL,AP,CP and CSC to leave the .md5 extension on the file, if all 4 loads without any errors and you have the correct PIT file you will be able to boot stock firmware.

In my case i had the same error because i flashed a modded debranded firmware without first flashing the stock AP.
So first, debrand you phone by flashing the stock debranded firmware, then flash the magisk patched version of it.
In other words, always flash the STOCK version of the firmware you want THEN flash the magisk PATCHED version (if you are moving from a version to another one, particularly if CSC is different).

Samsung Tab S2 SM-t813, Can't Restore Stock Firmware

Hello!!! I have Samsung Tab S2 SM-t813, I was running un-official LOS 17.1 but the battery life was bad and bluetooth headphones not working so I decided to go back to Stock.
Used Odin3 3.14 to flash latest FW from Sammobile, AU variant T813XXS2BTK3_T813XSA2BTK1_XSA
I loaded it up with AP option only (it's just one file, not BL, AP, CP and CSC).
Odin seems to flash it just fine and then I get a bluescreen, says it's installing an update, then says it's erasing, then it just sits on the Samsung Logo slowly fading in and out from dull to bright.
I know this is meant to take a long time the first boot but I've been waiting for an hour now.
Any suggestions?

@jonathonsunshine one chance I see is flashing multiple! file stock ROM.
You can get it using samfirm_reborn on a windows PC.
Insert your device type and region plus checking "binary nature" and "decrypt".
That will download a zip file you have to unpack and get the AP, BL aso.
Battery should be fully loaded before flashing.
Good luck.
That's what it looks like for my T820.

In the end, I never got the stock rom going, I flashed twrp-3.5.2_9-0-gts210vewifi.img.tar with Odin 3.14, then followed this guide and installed the Lite Version of Stock Rom https://forum.xda-developers.com/t/rom-7-0-nougat-stock-lite-v8-t713-t813.3746583/

jonathonsunshine said:
In the end, I never got the stock rom going, I flashed twrp-3.5.2_9-0-gts210vewifi.img.tar with Odin 3.14, then followed this guide and installed the Lite Version of Stock Rom https://forum.xda-developers.com/t/rom-7-0-nougat-stock-lite-v8-t713-t813.3746583/
Click to expand...
Click to collapse
So even multiple part stock ROM didn't work?
That's weird.

Trying this for a Galaxy Tab S2 (SM-T713) to no avail. I am able to grab the firmware but, unless I am doing something wrong, Odin doesn't do anything after loading the 3 extracted files and clicking start. Oh well.
EDIT:
I may be using an incorrect cable. Will try again later.
EDIT 2:
Back to stock!

Question Stuck in Download mode after firmware flash

Hi, I need some help flashing my device. Somehow, my device got stuck in a boot loop last night, and I've been having trouble getting it to work again. I think my phone may have reset during an update while in my pocket as I was laying down on the couch last night.
I found my device firmware on sammobile according to the specs listed below. I've downloaded Odin 3.14.4 and have flashed my phone successfully 3 or 4 times at this point, but when it restarts post-flash, it keeps booting into download mode. I can't seem to get it to boot into recovery mode or just turn it off at all anymore. No matter what, it boots straight into download mode.
Does anyone know of a way that I can force it into recovery mode so that I can try restarting it normally? This is my first time flashing a phone, so I have little experience here though I am competent with technology and willing to try further tricks to get it working.
I'm just looking for recommendations and hoping that my phone isn't bricked. I've only owned it for 3 months at this point, so I'm very disappointed.
Thanks in advance for the help, and I'm happy to provide any more information if it helps you come up with any potential solutions.
Specs
Phone: Samsung 21 Ultra
Model: SM-G998U1
PDA: G998U1UES5CVCB
Carrier: XAA
Text on download mode screen:
<!>
partition recovery
Reason avb.slot_verify.c:276: ERROR: recovery: Hash of data does not match digest in descriptor. [2nd]
Calculated Hash of (recovery) : 9C3B9F195F, (VEMETA) : 1C38BF9F7A
Samsung recovery, G998U1UES5CVCB, 50338466R
VBMETA G998U1UES5CVCB, 50341365R

Do you have TWRP installed? Try flushing it. You can also follow Dr. Ketan ROM installation guide, it's very straightforward.

shaharofir said:
Do you have TWRP installed? Try flushing it. You can also follow Dr. Ketan ROM installation guide, it's very straightforward.
Click to expand...
Click to collapse
I don't. I was looking at that post earlier and noticed that it mentioned the G998B/N model. Mine is the G998U1, so I was worried that it wouldn't work or cause more problems. I couldn't find any versions of TWRP that matched my specific model.

your bootloader version is above v1. cannot be unlocked. you need to flash a samsung rom. try redownloading it if you can't boot. and twrp probably won't work either.
you're saying that if you hold the vol up key and power button when the device is off that it won't reboot into recovery at all?

ffuser1 said:
your bootloader version is above v1. cannot be unlocked. you need to flash a samsung rom. try redownloading it if you can't boot. and twrp probably won't work either.
you're saying that if you hold the vol up key and power button when the device is off that it won't reboot into recovery at all?
Click to expand...
Click to collapse
I was actually able to get it to boot into recovery mode this morning. The download mode timed out and the phone shut off which allowed me to finally get into it. I tried redownloading the same rom I got from sammbolie again a few mins ago but still no luck.

Try another firmware with the same BL revision, CVC9 for example

dipotis said:
Hi, I need some help flashing my device. Somehow, my device got stuck in a boot loop last night, and I've been having trouble getting it to work again. I think my phone may have reset during an update while in my pocket as I was laying down on the couch last night.
I found my device firmware on sammobile according to the specs listed below. I've downloaded Odin 3.14.4 and have flashed my phone successfully 3 or 4 times at this point, but when it restarts post-flash, it keeps booting into download mode. I can't seem to get it to boot into recovery mode or just turn it off at all anymore. No matter what, it boots straight into download mode.
Does anyone know of a way that I can force it into recovery mode so that I can try restarting it normally? This is my first time flashing a phone, so I have little experience here though I am competent with technology and willing to try further tricks to get it working.
I'm just looking for recommendations and hoping that my phone isn't bricked. I've only owned it for 3 months at this point, so I'm very disappointed.
Thanks in advance for the help, and I'm happy to provide any more information if it helps you come up with any potential solutions.
Specs
Phone: Samsung 21 Ultra
Model: SM-G998U1
PDA: G998U1UES5CVCB
Carrier: XAA
Text on download mode screen:
<!>
partition recovery
Reason avb.slot_verify.c:276: ERROR: recovery: Hash of data does not match digest in descriptor. [2nd]
Calculated Hash of (recovery) : 9C3B9F195F, (VEMETA) : 1C38BF9F7A
Samsung recovery, G998U1UES5CVCB, 50338466R
VBMETA G998U1UES5CVCB, 50341365R
Click to expand...
Click to collapse
Was your phone carrier branded originally? And you're flashing the u1 firmware so you won't have bloat? Or is it originally an unlocked model? I ask because if it was originally carrier branded and you used the Odin version from the SamMobile site then that may be the reason. U need to use the modded version of Odin that's floating around somewhere. If you need it I can upload it to my drive and let you download that version. I literally just flashed VCB last night and everything worked just fine.

JG96EVO said:
Was your phone carrier branded originally? And you're flashing the u1 firmware so you won't have bloat? Or is it originally an unlocked model? I ask because if it was originally carrier branded and you used the Odin version from the SamMobile site then that may be the reason. U need to use the modded version of Odin that's floating around somewhere. If you need it I can upload it to my drive and let you download that version. I literally just flashed VCB last night and everything worked just fine.
Click to expand...
Click to collapse
No, I bought my phone directly from Samsung, and I bought the unlocked model. I chose the rom from sammobile that looked to be exactly what my phone originally had on it based on the model and PDA/carrier info I found when looking through the recovery logs on the phone when the issue first occurred, before flashing anything onto it. If you think the modded Odin might work, I'd be willing to give it a shot.

I can't tell you the exact differences, but I would flash with the patched odin. it's on xda if you search for it.

No luck so far. I've downloaded the patched Odin software and have tried flashing my device numerous times with the same result. I also tried tried flashing firmware that I found on Frija instead of the firmware I originall downloaded from sammobile to see if anything would be different, and that didn't seem to make a difference.
My best guess (could be wrong) is that it doesn't like the bootloader tied to the firmware I've tried to flash onto the device. I've spent a good while searching firmware that uses the version of the bootloader it wants, but I can't find it anywhere. At this point, I'm all out of ideas, but I appreciate everyone's responses and advice.

So this is what you are saying: You're using patched odin (https://forum.xda-developers.com/attachments/odin3-v3-14-1_3b_patched-zip.5158507/) to flash an official U1 Samsung rom (https://samfw.com/firmware/SM-G998U1/XAA/G998U1UES5CVCB for example) in the AP slot, all other slots are empty, without any odin errors during flash, and are then unable to boot, with partition errors seen in download mode? This is very unusual... flashing in download mode overwrites partitions, including recovery. I would assume if there are no odin errors, then the rom file is not corrupt and the sd card is not damaged. I don't know much about flashing through odin with a locked bootloader, maybe unpatched odin with the above instructions is worth a shot. I'm out of ideas aside from the sd card being damaged or trying unpatched odin if the above instructions with patched odin are resulting in recovery partition errors. I don't think you can access adb in download mode either.

You can extract the CSC file using 7zip. In there you will find the PIT file and you can try flashing it with repartition selected and inserting the PIT file in developers section of Odin.

ffuser1 said:
So this is what you are saying: You're using patched odin (https://forum.xda-developers.com/attachments/odin3-v3-14-1_3b_patched-zip.5158507/) to flash an official U1 Samsung rom (https://samfw.com/firmware/SM-G998U1/XAA/G998U1UES5CVCB for example) in the AP slot, all other slots are empty, without any odin errors during flash, and are then unable to boot, with partition errors seen in download mode? This is very unusual... flashing in download mode overwrites partitions, including recovery. I would assume if there are no odin errors, then the rom file is not corrupt and the sd card is not damaged. I don't know much about flashing through odin with a locked bootloader, maybe unpatched odin with the above instructions is worth a shot. I'm out of ideas aside from the sd card being damaged or trying unpatched odin if the above instructions with patched odin are resulting in recovery partition errors. I don't think you can access adb in download mode either.
Click to expand...
Click to collapse
Interesting. I did not try it with only the AP slot populated. I thought you needed to always flash with the BL, AP, CP, and CSC.

wait, i messed up. if it has all of those files, flash them. my bad. i was thinking about custom roms - sorry about that.

Hey everyone, just wanted to make a final update.
I ended up bringing my phone into ubreakifix after trying just about everything I could, and they were not able to fix it either. They suggested that it might be a hardware issue and recommended sending it to Samsung for repair. I then sent it over to Samsung, and they confirmed that it was an issue with my motherboard. Samsung replaced my motherboard, and the phone is back in action. Since I only had my phone for about 6 months, it was still under warranty.
I appreciate everyone who took their time to provide me with advice. I hope that this post may help someone experiencing a similar issue to mine in the future.