My friend tried to root my device and messed up and my phone boots stuck on samsung logo then turns off can anyone be knid and guide me how to fix this problem thank you:crying:
Can you access recovery mode?
yes
Flash a stock firmware through Odin.
Look up the available firmwares for your region at sammobile.com
Find out how tlyour friend tried to root the phone
If you can access recovery, maybe try flashing the unroot zip.
Or... use odin, you'll get a working phone and all data will be wiped.
I have a att galaxy s5. It's my fiance's. Tried to root it and load a new rom and it got messed up somehow. Only boots to the stock recovery. Tried to use Odin to flash the sammobile nce file but the bootloader is too New for that... We were on oa1. Can anyone help me get out of the doghouse and show me the right file to flash in Odin to get me back to oa1? I think when I was flashing a new rom, the old system got deleted but the New one never got put back. Odin give me a weird message that Ive found out usually means the bootloader is out of date.
Thanks in advance
I have a tab 4 that i rooted with custom rom with odin and i find myself stuck now i tried doing a factory reset thru tablet and because of the custom recovery well it crashed. It is know not loading i need help i now what i need to do, i believe all i have to do is install stock firmware thru pda, but i am having a hard time trying to find the stock firmware somehow i can't find it anywhere. If anyone can link stock firmware for sm 7237p that would be great......
ODIN MODE
PRODUCT NAME: SM-G925A
CURRENT BINARY: SAMSUNG OFFICAL
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK: OFF
SECURE DOWNLOAD: ENABLED
KNOX WARRANTY VOID: 0 (0X0000)
AP SWREV: B: 4 K: 3 S: 3
Good evening,
First time poster long time reader/browser. Before posting this message I have read all other posts/threads in an attempt to fix this issue. Long story short I busted my old Samsung Galaxy S6 Edge SM-G925A AT&T and bought this one used online. The seller never mentioned it was bricked as all pictures posted of it showed it operating and at least booting up. When I received phone I turned it on and it is stuck in a boot loop. I have tried to boot in recovery mode by pressing VOL UP+HOME+POWER button and it does nothing. I am only able to boot into download mode. I have attempted to flash multiple stock firmwares which 3 have been successful and passed in ODIN, however once they pass and the phone reboots it is still stuck in a boot loop. I have been successful in flashing the below firmwares. I do not know anything about the phone besides the IMEI number, S/N, SKU and manufactured date. I do not know what firmware was on the phone originally and do not know what was flashed on phone when I received it (I'm assuming phone was flashed or rooted before due to the above stating SYSTEM STATUS: CUSTOM) Am I stuck with a bricked phone? I've attempted flashes with PIT Files, w/o PIT FILES, with just the AP file, with all 4 BL, AP, CP and CSC files and each time it gets in a bootloop. Can someone please assist me? I've read that sometimes all is needed is to wipe the cache in recovery mode and that would clear bootloop, but I cannot get into recovery mode. Any suggestions. Again, below are what I've flashed successfully but continues to bootloop. Thank you all in advance.
G925AUCS5DPJ1--SUCCESSFUL ODIN FLASH-STILL BOOTLOOP
G925AUCU3BO12--SUCCESSFUL ODIN FLASH-STILL BOOTLOOP
G925AATT3BOJ7--SUCCESSFUL ODIN FLASH-STILL BOOTLOOP
I will say after flashing the DPJ1 files I can no longer flash the BL file for either of the 2 firmwares below it (the AP, CP and CSC files all still flash successful).
I'm just about to give up and shell out the money and buy new phone. Was just hoping someone on here could provide me some advice, some sort of miracle file or a way I can odin flash a tar/md5 file that will wipe my cache/system cache like it would as if you did it in recovery mode.
OH! Also Samsung Smart-Switch will not recognize the phone. I'm able to input the model name and S/N in the emergency software initialization but as soon as I input the S/N and click ok it immediately crashes and closes out Smart-Switch. Thanks Guys!
Paul
You need to find a Marshmallow odin file. The phone has most like;y already been updated to Marshmallow in the past. Once on MM, you cant go back to Lollipop which is what those 3 files you listed are.
Edit, NM....that PJ1 file is marshmallow. Try taking it to Best Buy and having them reflash it with the latest MM file.
Thank you, I will try that. I have tried taking to AT&T but they wouldn't help at all. They said since I'm not AT&T customer then I'd have to go thru Samsung. I'm aggravated. I've been working on this off and on for 3 months now. Thanks again for the reply. I've read a lot of people saying after wiping cache partition and rebooting it fixed bootloop after successful flash.
You said I could go back to Lollipop. If I use anything other than the 3 files I listed Odin will fail with various,
Secure Check fail message. Do you know if anyone has created a Odin file that will successfully wipe the cache partition like it would via system recovery?
Thanks again for the reply.
Any updates on this ? I'm having the same issue with my G925I.
why don't you try to flash the DPK5 update from ODIN in the nougat update thread. that's the latest ODIN file I think
saketkutta said:
why don't you try to flash the DPK5 update from ODIN in the nougat update thread. that's the latest ODIN file I think
Click to expand...
Click to collapse
No matter what I flash , it's always stuck on the s6 edge logo.. And I can't enter any recovery be it stock or custom recovery. All I can do is enter download mode and flash official ROMs but none seem to work.
Thats some unfortunate situation. I don't know what to do. If official roms don't boot then it's permanent brick I think. Any senior devs know what to do?
Sent from my SAMSUNG-SM-T337A using Tapatalk
I am suffering from the similar fate,, its a friend mobile whose stuck on Samsung logo, he tried to fix it with Kies and Smart Switch and it did not workout for him.
The phone does not boot into recovery. I tried flashing G925AUCU1AOCE and G925AUCU3BOJ7 stock firmwares but no luck.
I successfully flashed G925AUCU6EQCF but it is still stuck on Samsung Logo
Any help or suggestion would be welcome
edit 3rd: Ok now I have managed to flash G925AUCS5DPJ1, still it won't boot into recovery and it is looping to Samsung logo
Same for me ... The recovery is not accessible and the phone reboots in a loop, Smart Switch tell me that the S / N does not match the phone model ...
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.