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&amp;amp;amp;amp;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?
Related
Hello,
I recently tried to flash a stock NE4 Kernel onto my device and this ended up soft bricking it into a boot loop.
I have tried to wipe/factory reset my device already since I was able to get into recovery mode but to no avail.
I have tried to flash the stock ROM onto my device but I get a FAIL! (Auth) error in Odin. Specifically: G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5
At this point I could care less whether or not it's possible to root my AT&T S5 Active, I just want to be able to use it again.
... Please help, I'm super worried I won't be able to get it back.
My Device Model is SM-G870A
qq
JunSoHot said:
qq
Click to expand...
Click to collapse
-_- ... Thaaaaannnks
"Recovery is NOT SEANDROID ENFORCING" after CF-Odin rooting N910T3 run on M6.01
Just got a US Cellular Galaxy Note 4 phone. Did a factory reset and it run perfectly on T Mobile N910T3 Marshmallow 6.01 (stock). Must have been rooted before, but flashed back to stock firmware and unrooted. So I want to get it rooted again.
Without realizing the difference of rooting androids running on Marshmallow and previous versions, I downloaded the latest specific CF-Odin tool for N910T3, run it to root it. Quickly, Odin showed the green "Pass!" But the phone got stuck immediately after that when it proceeded to reboot with this error:
Recovery is NOT SEANDROID ENFORCING
Set Warrenty Bit : recovery
And the Galaxy Note 4 logo.
I removed the battery, waited for many minutes or a day. Power it on or boot to Recovery Mode always get to the above same error, so I cannot wipe data or do factory reset, as some suggested.
From above error screen, hold Volume down+Power+Home, I can easily get to the Download Mode. So I downloaded N910T3UVS2EPE2 (not the latest N910T3UVS2EPG2, as it's too slow from Samsung), but failed to flash it with Odin (3.11.1 or 3.10.6) with or without PC's Antivirus Off. And on the phone I got:
SW REV CHEKC FAIL : [aboot]Fused 2 . Binary 1
[1]eMMC write fail: ABOOT
Wonder if I can flash TWRP with Odin in such a state? Besides, I forgot and didn't install USB drivers for Galaxy Note 4. Could this be the problem? I have USB drivers for Note 2, and it seems the PC communicate normally with this Note 4.
Appreciate very much for any help!
Having the same issue. Can't even get the phone to flash the pit file or the stock software it fails every time.
Think the phone is Toast.
***Update***
Had to do some weird stuff to get it booted and running stock un rooted again. I ODIN flashed TWRP booted into recovery and formatted DATA, then I ODIN flashed the GP2 PIT file along with the newest version of the CF Auto Root at the same time (For some reason this is the only way the PIT flash would not fail, Then I ODIN flashed the [email protected] stock firmware, and it finally booted again. After not being able to boot for 2 weeks. Device is running the setup now.
Update:
I was too scare to take any actions on the phone for almost a week! However, yesterday I only flashed TWRP with Odin and it automatically rebooted back to normal!! Everything seems to be working perfectly again! The only exception when I boot it to recovery mode to TWRP, I still see a flash of the following error message before TWRP:
Recovery is NOT SEANDROID ENFORCING
Set Warrenty Bit : recovery
Some how TWRP can pass the bootloop.
With TWRP I was able to root the phone, thanks to Rootmygalaxy.net, and did some backups.
Wonder if I can get rid of that error message by wiping Cache/data...?
You will get an error on that screen; kernel error or not seandroid enforcing error because it is not Samsung stock being used. There's no getting g around the warning that I'm aware of and it doesn't cause a difference on the phone running stock modified or just going all out and running any other rom.
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 ...
I have a note 4 Canada model N910W8 and I am having the emmc write fial error, no matter which stock firmware I flash with Odin it does not work and cannot be booted into recovery, I tried with PIt without PIT nothing attached is the image showing error on the phone download mode. Please help unbrick my Note 4
https://forum.xda-developers.com/showthread.php?t=3488114
Use the recovery firmware for n910w8.
Load the files in respective slots of odin, select f.time reset and repartition, untick auto reboot.
Flash.
Reporting Via N910G.
yashthemw said:
https://forum.xda-developers.com/showthread.php?t=3488114
Use the recovery firmware for n910w8.
Load the files in respective slots of odin, select f.time reset and repartition, untick auto reboot.
Flash.
Reporting Via N910G.
Click to expand...
Click to collapse
Do I have to use the freezer ? My N910W8 boots into DL mode without any issues, so is the freezer step necessary still?
lambergino said:
Do I have to use the freezer ? My N910W8 boots into DL mode without any issues, so is the freezer step necessary still?
Click to expand...
Click to collapse
Freeze it before flashing the recovery firmware.
Reporting Via N910G.
yashthemw said:
Freeze it before flashing the recovery firmware.
Reporting Via N910G.
Click to expand...
Click to collapse
I have flashed all the portions of the recovery firmware including CSC, it completed successfully in odin, then I pulled the battery out and put back in tried to boot into recovery still did not go... it showed 'installing updates' and then blank. Do I have to reflash the recovery firmware then flash stock firmware via odin after I pull the battery ?
lambergino said:
I have flashed all the portions of the recovery firmware including CSC, it completed successfully in odin, then I pulled the battery out and put back in tried to boot into recovery still did not go... it showed 'installing updates' and then blank. Do I have to reflash the recovery firmware then flash stock firmware via odin after I pull the battery ?
Click to expand...
Click to collapse
The fact is, the emmc trips when the device heats up.
One user, actually kept an ice bag on the device while it was booting. The device booted successfully.
This is actually a hardware brick, which probably can't be fixed with any software.
Reporting Via N910G.
lambergino said:
I have a note 4 Canada model N910W8 and I am having the emmc write fial error, no matter which stock firmware I flash with Odin it does not work and cannot be booted into recovery, I tried with PIt without PIT nothing attached is the image showing error on the phone download mode. Please help unbrick my Note 4
Click to expand...
Click to collapse
I had the same problems. This is a hardware error (emmc = flashmemory). The only solution is to replace you motherboard. I ordered one on aliexpress and replaced it myself with a tutrial found on youtube. Very easy.
My phone is working perfect now.
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.