Database Develop

Softbricked AT&T Galaxy S5

I purchased a soft bricked sm-g900a phone off of Ebay with the idea of using Odin to reflash and recover the phone. Since the phone was purchased soft bricked I do not have a history on what firmware was running on the phone or what the previous owner flashed that may have caused the phone not to boot to the OS or into recovery. I am assuming the previous owner was on 5.0 and tried to downgrade and ran into problems.
Short description of the current state of the phone:
1. Phone will boot into Odin Mode and can be flashed using Odin.
2. Phone will start to boot to recovery but sticks at "Recovery Booting. . . ." and reboots after about 30 seconds
3. Phone boots to Samsung logo and reboots after about 30 seconds.
What works:
Using Odin I can flash the following without errors: After flashing the phone exhibits the behavior above.
G900A_OC4_Stock_Kernel.tar.md5,
G900A_OA1_Stock_Kernel.tar.md5
G900A_OC4_Stock_Modem.tar.md5,
G900A_OC4_Stock_Partitions.tar.md5
G900AUCU3BOC4_OneClick..exe - reboots to recovery and "Recovery Booting. . . ."
I can flash SM-G900A_pit.pit with Odin 3.07 but not 3.09 or 3.10.
What does not work.
Tried flashing G900A_Downgrade_to_NCE.tar.md5 - Odin reports error
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Auth)
Phone reports errors
SYS REV CHECK FAIL :Refer 2> Binary 1
SECURE CHECK FAIL : System
Tried flashing SM-G900A 4.4.2 G900AUCU1ANCE Firmware - AP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 in AP slot
Same errors as above .
Tried to use Kies to recover the phone. It goes through the process of recovering with 4.4.2 and crashes about the same place flashing wit Odin does.
I assume if I could get into recovery to do a factory wipe I would be able to get the phone to boot. I have read multiple forum posts and blogs on getting the bricked phone to work where most recommend flashing G900A_Downgrade_to_NCE.tar.md5 and then if you can't get into recovery to flash either G900A_OC4_Stock_Kernel.tar.md5 or G900A_OA1_Stock_Kernel.tar.md5 and then you should be able to get into recovery. This of course has not worked for me.
Does anyone have any idea how I might go about getting this phone to boot into recovery? Also is it possible to have the local AT&T store re flash 5.0 on the phone.
I know it is a risk buying soft bricked phones but I sure would not like to have an expensive paper weight.

Bogiemaker said:
I purchased a soft bricked sm-g900a phone off of Ebay with the idea of using Odin to reflash and recover the phone. Since the phone was purchased soft bricked I do not have a history on what firmware was running on the phone or what the previous owner flashed that may have caused the phone not to boot to the OS or into recovery. I am assuming the previous owner was on 5.0 and tried to downgrade and ran into problems.
Short description of the current state of the phone:
1. Phone will boot into Odin Mode and can be flashed using Odin.
2. Phone will start to boot to recovery but sticks at "Recovery Booting. . . ." and reboots after about 30 seconds
3. Phone boots to Samsung logo and reboots after about 30 seconds.
What works:
Using Odin I can flash the following without errors: After flashing the phone exhibits the behavior above.
G900A_OC4_Stock_Kernel.tar.md5,
G900A_OA1_Stock_Kernel.tar.md5
G900A_OC4_Stock_Modem.tar.md5,
G900A_OC4_Stock_Partitions.tar.md5
G900AUCU3BOC4_OneClick..exe - reboots to recovery and "Recovery Booting. . . ."
I can flash SM-G900A_pit.pit with Odin 3.07 but not 3.09 or 3.10.
What does not work.
Tried flashing G900A_Downgrade_to_NCE.tar.md5 - Odin reports error
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Auth)
Phone reports errors
SYS REV CHECK FAIL :Refer 2> Binary 1
SECURE CHECK FAIL : System
Tried flashing SM-G900A 4.4.2 G900AUCU1ANCE Firmware - AP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 in AP slot
Same errors as above .
Tried to use Kies to recover the phone. It goes through the process of recovering with 4.4.2 and crashes about the same place flashing wit Odin does.
I assume if I could get into recovery to do a factory wipe I would be able to get the phone to boot. I have read multiple forum posts and blogs on getting the bricked phone to work where most recommend flashing G900A_Downgrade_to_NCE.tar.md5 and then if you can't get into recovery to flash either G900A_OC4_Stock_Kernel.tar.md5 or G900A_OA1_Stock_Kernel.tar.md5 and then you should be able to get into recovery. This of course has not worked for me.
Does anyone have any idea how I might go about getting this phone to boot into recovery? Also is it possible to have the local AT&T store re flash 5.0 on the phone.
I know it is a risk buying soft bricked phones but I sure would not like to have an expensive paper weight.
Click to expand...
Click to collapse
Its hard to tell what version it was on previously since recovery wont even boot, but from how its acting i'd say it was on LP and bricked for a KK flash, so you flashing NCE(Kitkat) is doing zilch. Seeing as there is no option for you to root, and im assuming you arent interested in that anyway, i would just take it to bestbuy or the att store and get them to reflash it, just say you got it off ebay and it was like that.
Sent from my Tw5ted SM-G900A using Tapatalk

I took the phone to BestBuy and the guy there flashed it with 5.0.1 with the same results. Boots to the Recovery Booting. . . . screen for about 30 seconds and then reboots. My daughter is taking it to an AT&T repair center to see if they have any better luck.

Have you tried flashing the boot image?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app

Boot image. Not sure which file you are talking about.
Could you give me a little more information or a link to the file?

Re: Softbricked AT&T Galaxy S5
If you have the oc4 update zip, in the zip should be a boot image, create an md5 tar file from it then flash in AP. If that doesn't work, you flashed a bad kernel and may have to use jtag to fully recover. Or bring it to a repair facility to have them do it.

My daughter took the phone to an AT&T repair center and they also could not successfully flash the phone. The only OC4 update i have found is the G900AUCU3BOC4_OneClick..exe update and I do not believe I can extract the boot image from that update. Is there another source of the OC4 update available where I could obtain the boot image.
Thanks for the help everyone.

I'll look for the DL link. But if they tried flashing it, and it didn't work. You may be SOL.

Bogiemaker said:
I purchased a soft bricked sm-g900a phone off of Ebay with the idea of using Odin to reflash and recover the phone. Since the phone was purchased soft bricked I do not have a history on what firmware was running on the phone or what the previous owner flashed that may have caused the phone not to boot to the OS or into recovery. I am assuming the previous owner was on 5.0 and tried to downgrade and ran into problems.
Short description of the current state of the phone:
1. Phone will boot into Odin Mode and can be flashed using Odin.
2. Phone will start to boot to recovery but sticks at "Recovery Booting. . . ." and reboots after about 30 seconds
3. Phone boots to Samsung logo and reboots after about 30 seconds.
What works:
Using Odin I can flash the following without errors: After flashing the phone exhibits the behavior above.
G900A_OC4_Stock_Kernel.tar.md5,
G900A_OA1_Stock_Kernel.tar.md5
G900A_OC4_Stock_Modem.tar.md5,
G900A_OC4_Stock_Partitions.tar.md5
G900AUCU3BOC4_OneClick..exe - reboots to recovery and "Recovery Booting. . . ."
I can flash SM-G900A_pit.pit with Odin 3.07 but not 3.09 or 3.10.
What does not work.
Tried flashing G900A_Downgrade_to_NCE.tar.md5 - Odin reports error
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Auth)
Phone reports errors
SYS REV CHECK FAIL :Refer 2> Binary 1
SECURE CHECK FAIL : System
Tried flashing SM-G900A 4.4.2 G900AUCU1ANCE Firmware - AP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 in AP slot
Same errors as above .
Tried to use Kies to recover the phone. It goes through the process of recovering with 4.4.2 and crashes about the same place flashing wit Odin does.
I assume if I could get into recovery to do a factory wipe I would be able to get the phone to boot. I have read multiple forum posts and blogs on getting the bricked phone to work where most recommend flashing G900A_Downgrade_to_NCE.tar.md5 and then if you can't get into recovery to flash either G900A_OC4_Stock_Kernel.tar.md5 or G900A_OA1_Stock_Kernel.tar.md5 and then you should be able to get into recovery. This of course has not worked for me.
Does anyone have any idea how I might go about getting this phone to boot into recovery? Also is it possible to have the local AT&T store re flash 5.0 on the phone.
I know it is a risk buying soft bricked phones but I sure would not like to have an expensive paper weight.
Click to expand...
Click to collapse
Hello! OP...are you still around?
Did you ever recover this phone?
I was in the same situation...maybe worse...and I was finally able to recover it.
Please let me know what happened with yours?
THANKS!

jebep said:
Hello! OP...are you still around?
Did you ever recover this phone?
I was in the same situation...maybe worse...and I was finally able to recover it.
Please let me know what happened with yours?
THANKS!
Click to expand...
Click to collapse
How did you recover yours?

How to solve dm-verity verification failed/need to check drk first on samsung devices

Recently, I ran into the same problem and decided to check the interwebs for a solution which turns out to be pretty simple.
To solve the issue;
1. Download official firmware for your device from sammobile
2. Extract your firmware files from the TAR. (delete ext .md5 from file name, then open with 7zip/winrar. unzip)
3. Repack your firmware AFTER deleting cache.img. Instructions
4. Flash the repackaged firmware via ODIN
That's it!

Muthumbi said:
Recently, I ran into the same problem and decided to check the interwebs for a solution which turns out to be pretty simple.
To solve the issue;
1. Download official firmware for your device from sammobile
2. Extract your firmware files from the TAR. (delete ext .md5 from file name, then open with 7zip/winrar. unzip)
3. Repack your firmware AFTER deleting cache.img. Instructions
4. Flash the repackaged firmware via ODIN
That's it!
Click to expand...
Click to collapse
I tried this it failed frp lock

Muthumbi said:
Recently, I ran into the same problem and decided to check the interwebs for a solution which turns out to be pretty simple.
To solve the issue;
1. Download official firmware for your device from sammobile
2. Extract your firmware files from the TAR. (delete ext .md5 from file name, then open with 7zip/winrar. unzip)
3. Repack your firmware AFTER deleting cache.img. Instructions
4. Flash the repackaged firmware via ODIN
That's it!
Click to expand...
Click to collapse
Muthumbi: thank you so much, you are a genius. My n9208 was stuck at Samsung logo forever, no matter what I did, what stock firmware I flash through odin or through Kies, it just couldn't boot, I almost lost my hope. When entered recovery, only thing I noticed was the dm-verity failure, and I tried your way to solve the dm-verity problem only in the dim hope to change something........guess what, it booted, and booted very quickly!!!!, you saved my note 5!, massive thank you:good::good::good:

Now only one problem: rebooted into system, then entered stock recovery and did factory reset, dm-verity failure happened again. Any definitive solution other than re-flash stock firmware without cache.img? Much appreciated.

Normmo said:
Muthumbi: thank you so much, you are a genius. My n9208 was stuck at Samsung logo forever, no matter what I did, what stock firmware I flash through odin or through Kies, it just couldn't boot, I almost lost my hope. When entered recovery, only thing I noticed was the dm-verity failure, and I tried your way to solve the dm-verity problem only in the dim hope to change something........guess what, it booted, and booted very quickly!!!!, you saved my note 5!, massive thank you:good::good::good:
Click to expand...
Click to collapse
Download this file and flash it via odin after fleshing any stock ROM. Tell me how it goes

HoodPhonez said:
I tried this it failed frp lock
Click to expand...
Click to collapse
Does your phone boot up?

Muthumbi said:
Does your phone boot up?
Click to expand...
Click to collapse
No just stay on samsung logo.

HoodPhonez said:
No just stay on samsung logo.
Click to expand...
Click to collapse
yes it did boot up, but the recovery still shows Dm-verity failure after factory reset. thanks Muthumbi.

HoodPhonez said:
No just stay on samsung logo.
Click to expand...
Click to collapse
You might have to look for a way to undo FAP lock

Normmo said:
yes it did boot up, but the recovery still shows Dm-verity failure after factory reset. thanks Muthumbi.
Click to expand...
Click to collapse
Kindly send me a private message with exact details. I will get back to you in a while

HoodPhonez said:
No just stay on samsung logo.
Click to expand...
Click to collapse
You'll need to undo FRP lock first

How? I searched can't find a way

Muthumbi said:
Recently, I ran into the same problem and decided to check the interwebs for a solution which turns out to be pretty simple.
To solve the issue;
1. Download official firmware for your device from sammobile
2. Extract your firmware files from the TAR. (delete ext .md5 from file name, then open with 7zip/winrar. unzip)
3. Repack your firmware AFTER deleting cache.img. Instructions
4. Flash the repackaged firmware via ODIN
That's it!
Click to expand...
Click to collapse
Please do video I cant do it :good: , I'm a few days without Cell Phones

yyyyyyyyyyyyyyyyyes man it work thnks:laugh:

my problem solved with this file:
Code:
https://www.androidfilehost.com/?fid=24052804347784115
G920f

G928C...boots to wifi turning on, gets stuck there for a bit then reboots. If i do factory reset, it gets stuck at the boot logo permanently. if i get into recovery again, i get the dm-verity error. any ideas. cant root coz the FRP lock is on.

I had this problem and solved it by flashing Galaxy S6 marshmallow Kernel (check if it's compatible with your device e.g. I have a G920F). Then do a erase data/clear cache/reboot.

Your DRK is damaged. If you will extract the boot.img and system.img from the stock firmware then convert them each to .tar.md5 and flash the system.img then the boot.img it will boot like normal. If you ever update or reset the device it will stick back on the Samsung splash screen until you flash them again. I can repair your DRK as a permanent fix, but it can only be repaired via UART cable which means it cannot be redirected and repaired remotely. You are more than welcome to ship your phone to my business and I will repair the DRK and return it to you, but you must pay return shipping.

"furious99, you were right, though i hadn't seen your message, i noticed the marshmallow update for iraq for the G928C had been released, downloaded it and flashed the phone. It has been working since. I did a factory reset and it was still fine. so that is the solution.

Muthumbi said:
Recently, I ran into the same problem and decided to check the interwebs for a solution which turns out to be pretty simple.
To solve the issue;
1. Download official firmware for your device from sammobile
2. Extract your firmware files from the TAR. (delete ext .md5 from file name, then open with 7zip/winrar. unzip)
3. Repack your firmware AFTER deleting cache.img. Instructions
4. Flash the repackaged firmware via ODIN
That's it!
Click to expand...
Click to collapse
This is only a temporary solution. If you update the firmware or factory reset the phone it will go back to being stuck on the Samsung logo. It can only be permanently fixed via a hardware solution atm.

recovery bootloop with N910T

Hello all developers
the problem start when my friend ask me to fix his mobile
the first look to the mobile is
when i click power on it's show Samsung logo with this word at the left top( recovery booting ... )then reboot after 2 seconds at-least
i have download the latest official Rom 5.1.1 from sammobile
N910TUVU2DOK2_N910TTMB2DOK2_N910TUVU2DOK2_HOME
after flash with odin i remember that is must complete the installation after first reboot with android logo but there is nothing happened !! its always reboot with the same word ( recovery rebooting )
I have tired to flash many Roms
Many BL
Many Modem
try to flash PIT File and the same
try Emergency with Kies and nothing changed
Kies give me this information when i put the model
PDA : OK2 / CSC : OK2 / PHONE : OK2 (TMB)
the all info about this mobile :
Model : SM-N910T
S/N : RF8FC131QYY 14.12
IMEI : 356095064430028
when i enter Odin Mode thats appear
ODIN MODE (HIGH SPEED)
PRODUCT NAME : SM-910t
CURRENT BINARY : SAMSUNG OFFICIAL
SYSTEM STATUS : CUSTOM
REACTIVATION LOCK : OFF
KNOX WARRANTY VOID : 0x1 (4)
QUALCOMM SECUREBOOT : ENABLE (CBS)
RP SWREV : S1, T1 , R1 , A2 , P1
SECURE DOWNLOAD : ENABLE
UDC START
please help me to fix it with any rom ... I can't go recovery mode but i can go download mode with ODIN

Any help please

i have the same issue but im on verizon. Also kies doesnt recognize my phone and I can't get to recovery. Any help would be appreciated. otherwise i just have an expensive paperweight.

Download n910t pit file and flash the pit file with the firmware. Make sure repartiton is checked. And let it reboot without pulling the the usb out.. the first thing it always does after odin to stock is reboot to recovery....are you getting any errors when you try to flash the firmware? Download this firmware. It is untouched full stock wipes everything
https://mega.nz/#!asRzgCYb!f8ssb_v6zDxYJ8_u1ygzpothj1arjRmMdM_opGz8QO0

Had the same issue i tried all kinds of roms stock and custom nothing seemed to work bought a new battery didnt make a diff now my phone is dead

noob4598 said:
Download n910t pit file and flash the pit file with the firmware. Make sure repartiton is checked. And let it reboot without pulling the the usb out.. the first thing it always does after odin to stock is reboot to recovery....are you getting any errors when you try to flash the firmware? Download this firmware. It is untouched full stock wipes everything
https://mega.nz/#!asRzgCYb!f8ssb_v6zDxYJ8_u1ygzpothj1arjRmMdM_opGz8QO0
Click to expand...
Click to collapse
Can you share PIT file for 910t? My phone is just keep bootcycle no matter what I do with ODIN, and try to flash ROM after ODIN, it bombs out, and boot cycle...
Thanks.

I am stuck with the same thing
any help would be great I am some what of a noob to this

Anyone had luck solving this problem?

noob4598 said:
Download n910t pit file and flash the pit file with the firmware. Make sure repartiton is checked. And let it reboot without pulling the the usb out.. the first thing it always does after odin to stock is reboot to recovery....are you getting any errors when you try to flash the firmware? Download this firmware. It is untouched full stock wipes everything
https://mega.nz/#!asRzgCYb!f8ssb_v6zDxYJ8_u1ygzpothj1arjRmMdM_opGz8QO0
Click to expand...
Click to collapse
Link plz

waleedy said:
Link plz
Click to expand...
Click to collapse
I'm having the same problem. I'm not getting any errors, and I found and flashed the PIT file with the stock firmware. Still no boot. It just sits on the boot up screen. No recovery, no battery icon...no nothing.

Plzzz note 9 bricked efs

I try to use sam fix tool to get my baseband (unknown) and sim cad imei fixed
i use the tool and choose baseband fix it boot into donwload mode and flash something
after that my note 9 stuck bootloop
i flashed stock frimware using odin and didnt work
i flashed combination file and also got bootloop
i can go to download mode
but whatever i do my phone stuck bootloop
plz need help plz guys
BUT I MADE A EFS BACKUB USING SCRIPT CMD IT CREAT A FLASH FILE CAN BE FLASHED USING ODIN VIA AP
BUT I CAN ACCESS IT RIGHT NOW BECASE I HAVE IT IN MY WORK
IS THAT ABLE TO HELP ME FIX THE PROBLEME[/COLOR]

Make you post readable for everyone using the dark theme and you might get more response.
What exactly did you flash with Odin and what happened, other than it didn't work?

willhemmens said:
Make you post readable for everyone using the dark theme and you might get more response.
What exactly did you flash with Odin and what happened, other than it didn't work?
Click to expand...
Click to collapse
I used a tool to fix baseband the tool reboot my phone into download mode and flash something
i try to boot my phone it get bootloop i try flash stock rom still bootloop
i flashed combination file still bootloop
i think the tool did something to efs partition

Did you complete a backup with TWRP?

willhemmens said:
did you complete a backup with twrp?
Click to expand...
Click to collapse
no i didint flash twrp my device not rooted

devil499 said:
no i didint flash twrp my device not rooted
Click to expand...
Click to collapse
You shouldn't have used any tool.
You could have easily recovered your unknown baseband by simply flashing your stock firmware.
Retry flashing the Stock firmware. But this time, do a wipe cache partition, wipe data/factory reset in recovery mode first.
Use the latest stock firmware that is available for your country/CSC.
If you can find a pit file, include that in odin flash with the stock firmware. Put a checkmark on the "repartition" option.
It's normal for the device to take 5-10 minutes or more during the initial boot.
Sent from my SM-N960F using Tapatalk

Good luck dude when the mention above most really suck having a bricked note 9

jaylence said:
You shouldn't have used any tool.
You could have easily recovered your unknown baseband by simply flashing your stock firmware.
Retry flashing the Stock firmware. But this time, do a wipe cache partition, wipe data/factory reset in recovery mode first.
Use the latest stock firmware that is available for your country/CSC.
If you can find a pit file, include that in odin flash with the stock firmware. Put a checkmark on the "repartition" option.
It's normal for the device to take 5-10 minutes or more during the initial boot.
Sent from my SM-N960F using Tapatalk
Click to expand...
Click to collapse
i have done that but didnt worked
plz help me
i didint find pit file for my device
n960f

HtcOnekid said:
Good luck dude when the mention above most really suck having a bricked note 9
Click to expand...
Click to collapse
i found this post https://forum.xda-developers.com/ga...ide-fix-n950f-efs-failed-to-mount-dm-t3831184
i beg you can you plz help understand it
Extract Stock firmware AP file (rename .md5 to .tar)
this i cant understand wich should i rename or what i do
Rename dqmdbg.img to efs.img (or smallest image must be smaller than 8000 KB). Extract Dqmdbg.img.lz4 so it’s just “Dqmdbg.img” and then rename it to efs.img and put that one in a tar. Other option is downloading a file that’s already made this way if your bootloader is binary 4, Saves you trouble of extracting / renaming: http://www.mediafire.com/file/589wuc...f/efs.tar/file (if you download this file just move onto number 3)
Add file new efs.img into tar archive.
Flash tar as AP file in odin + download mode
Reboot download mode
Flash Combination with odin + nand erase option on Edit: suggest you to flash stock rom first and oem unlock, don't need to wait for 7 days if imei is 0000 skip combination step
Device Should boot into Factory binary
Use IME to restore imei using *#06# (or imei 0000 in stock rom) Edit: This step is not required if efs backup is restored successful
Your device should have dm-verify failed in recovery due to drk error
Continue drk bypass for dm verify error below to continue

willhemmens said:
Make you post readable for everyone using the dark theme and you might get more response.
What exactly did you flash with Odin and what happened, other than it didn't work?
Click to expand...
Click to collapse
What? I'm using desktop. Is there a different view on mobile?

Bricked Note 9 due to efs
devil499 said:
I try to use sam fix tool to get my baseband (unknown) and sim cad imei fixed
i use the tool and choose baseband fix it boot into donwload mode and flash something
after that my note 9 stuck bootloop
i flashed stock frimware using odin and didnt work
i flashed combination file and also got bootloop
i can go to download mode
but whatever i do my phone stuck bootloop
plz need help plz guys
BUT I MADE A EFS BACKUB USING SCRIPT CMD IT CREAT A FLASH FILE CAN BE FLASHED USING ODIN VIA AP
BUT I CAN ACCESS IT RIGHT NOW BECASE I HAVE IT IN MY WORK
IS THAT ABLE TO HELP ME FIX THE PROBLEME[/COLOR]
Click to expand...
Click to collapse
I have the same problem with my note 9. Im looking if anyone can provide me with efs file of N960F Binary 3 so i can get it unbricked again.
I found this website but it has efs files for binary 1 and 2 not 3. Will it still work if i use binary 2 efs?
//frpdone.com/efs-mdm-samsung/
Did u find a solution?

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.