Develop Bugs

[Q] Today's update soft-bricked my phone

Hello. Last week I got impatient with the fact that I could not write to my sd card under the newest versions of Android (thanks, Google!), so I rooted my phone with a (supposedly) unobstrusive ROM as described here: http://forum.xda-developers.com/showthread.php?t=2143479.
And today, after installing the baseband update, my phone will no longer boot. The screen just goes dark after saying Samsung Galaxy Note II.
I tried reinstalling the root, I tried installing a custom ROM, I tried resetting to factory and clearing the cache. Nothing has worked.
I really would like to have my phone back Does anyone have any suggetions?

OTA update
pstuart82 said:
Hello. Last week I got impatient with the fact that I could not write to my sd card under the newest versions of Android (thanks, Google!), so I rooted my phone with a (supposedly) unobstrusive ROM as described here: http://forum.xda-developers.com/showthread.php?t=2143479.
And today, after installing the baseband update, my phone will no longer boot. The screen just goes dark after saying Samsung Galaxy Note II.
I tried reinstalling the root, I tried installing a custom ROM, I tried resetting to factory and clearing the cache. Nothing has worked.
I really would like to have my phone back Does anyone have any suggetions?
Click to expand...
Click to collapse
Try Kies software (samsung), let me know if this works for you.

azRisky said:
Try Kies software (samsung), let me know if this works for you.
Click to expand...
Click to collapse
I only backed up some of my applications. I am not sure this will work but I will try when I get home.
If anyone else has any ideas, I would still appreciate to hear them. I need the phone for business reasons, so I need to purchase another tonight if I am not able to fix this one.
FWIW, at one point I noticed that the phone still made my speakers crackle when I put it near them, so it was transmitting *something*. The screen is blank though.

azRisky said:
Try Kies software (samsung), let me know if this works for you.
Click to expand...
Click to collapse
I'm in his exact same boat. Rooted about a month ago, the update soft bricked my phone. I've tried everything from flashing rom after rom to trying to recover in Kies.
No dice, when you try to recover in Kies, it won't recognize your device, it just saying Connecting until it asks you to reboot your device.
Any help is greatly appreciated. Been triyng to fix this for 18 hours so far
If you need any info to help just tell me I'll provide everything.
Some info:
In download mode, this is displayed;
ODIN MODE
PRODUCT NAME: SGH-I317
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 1
RP SWREV: A3

tplaistow said:
I'm in his exact same boat. Rooted about a month ago, the update soft bricked my phone. I've tried everything from flashing rom after rom to trying to recover in Kies.
No dice, when you try to recover in Kies, it won't recognize your device, it just saying Connecting until it asks you to reboot your device.
Any help is greatly appreciated. Been triyng to fix this for 18 hours so far
If you need any info to help just tell me I'll provide everything.
Some info:
In download mode, this is displayed;
ODIN MODE
PRODUCT NAME: SGH-I317
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 1
RP SWREV: A3
Click to expand...
Click to collapse
Your specs are EXACTLY the same as mine. I am getting the dreaded SW Rev. Invalid Magic string when I try to flash from Kies. I am currently downloading a 4.4.2 ROM from d-h.st to try to fix it; I will keep you updated.
Side rant: If you're a tiny website like d-h.st, probably not a good idea to force the user to type in their credit card by hand. Seriously, I was all ready to throw money at the screen and get this stupid thing over with, but like heck if I'm going to type my credentials into that kind of site.

Just curious guys but have you all tried flashing stock rom back to the phone using odin?

jaybeerange said:
Just curious guys but have you all tried flashing stock rom back to the phone using odin?
Click to expand...
Click to collapse
jaybeerange- this will not work because Samsung Kies tries to restore to version 4.1.2, but the boot loader disallows it because it's too old.
If you have a 4.4.2 sitting around, by all means, let us know. I've been trying to download from d-h.st, but rumor has it that it will fail.
I am literally out of options.

Yeah the one from dhst is the one im talking about. I dont know why it wouldnt work. If I remember right it doesn't contain the bootloader so that shouldnt be a problem. The bootloader just wont allow itself to revert to an older version but its a 4.4.2 rom so it should work
---------- Post added at 03:23 AM ---------- Previous post was at 03:13 AM ----------
Just to be clear you know that when I say odin I mean the odin application and not kies right?

This OTA update bricked mine as well. Don't install this if your rooted!!!

I was able to take the update and im rooted and running custom recovery. Only thing I can think of that might be different is that I never took the official ota update. I flashed a stock 4.4.2 rom in recovery so im still on the 4.3 bootloader

Sweet mother of Zeus, I downloaded the 4.4.2 ROM off d-h.st, flashed it in Odin, and unbricked my phone.
Instructions for everyone else:
* Download Android 4.4.2 stock here: http://d-h.st/8HG. FYI, don't bother buying a subscription to the site to speed up the download unless you're doing it to thank the owners. Membership WON'T DO ANYTHING to help your speed. You'll just have to wait ~4 hours.
* Flash with Odin 3.0.7.
If anyone who has rights wants to post in this thread, it might be helpful.
I plan to set up a torrent tonight for anyone who wants to download it without the long wait.

Here is the magnet link: magnet:?xt=urn:btih:03336f24f4d6b9e86ca608d7766287edc7cd5d73&dn=I317-ODIN-UCUCNE5-Stock-No-Recovery.zip&tr=udp%3A%2F%2Ftracker.publicbt.com%3A80
By all means download, but PLEASE seed if you do. I am allocating a lot of bandwidth but I can only upload so much!
PS. If you're worried about the reliability of the torrent, d-h.st provides an md5 sum that you can use to check the file after you've downloaded it.

Exactly what the guy said about flashing the stock rom is right. However, since my phone didn't have enough space, it didn't reset my phone. Maybe it works if you go into download mode (power, volume up and home) and then reboot it works. Have rebooted it twice since then and it still works. Everything is just how i had it before the update, but with the update.

no seeds for the torrent?

xCAVEMANx said:
no seeds for the torrent?
Click to expand...
Click to collapse
I don't know what to tell you. Three people have already downloaded it from me (unfortunately, none is seeding).

pstuart82 said:
I don't know what to tell you. Three people have already downloaded it from me (unfortunately, none is seeding).
Click to expand...
Click to collapse
I think the technical term in torrent speak is leeches. So your torrent has zero seeders, zero peers, and 3 leeches.

ATT update
Rule #1 of OTA. No root and stock completely.
This link here shows you every file that the OTA checks for and many other things before it does anything.
https://www.androidfilehost.com/?fid=95784891001611244
If something does not match, it craps out.
I'm downloading the Zen's ODIN NE5 from dev-host now. They must have fixed issues because it's flying.
I should have it in 10-15 minutes. I have uploaded a version that I had to androidhost, but I'm waiting to hear from Zen if he's ok with me posting a mirror.
And I need to make sure that what I'm downloading and what I have uploaded in the same. But like I said looks like Dev-Host is working better, or at least better than it has been the past couple of days.

xCAVEMANx said:
I think the technical term in torrent speak is leeches. So your torrent has zero seeders, zero peers, and 3 leeches.
Click to expand...
Click to collapse
It wouldn't be so bad if I hadn't explicitly asked people to seed. Anyway, there's pne seeder: me. Interestingly, I tried to attach to it with uTorrent, and I can't connect to the host. So maybe there's something wrong with my torrent server. If you want, PM me and I will sign in to Windows and seed from there.

Had exact same issue and flashed the boot loader and now my phone works great!
here is the link: http://d-h.st/qDY
Have a good one guys

Had a lot of hope for this, but I'm now getting one step further in my loop (I see the ATT logo spinning then it just hangs).
Any ideas?

Failed root attempt left tablet at the Samsung screen

I have been searching the forum and google and have been unable to reach a solution yet.
I am not a noob, but i am not an expert either so use small words ha.
I have a Samsung Galaxy Tab 3 10.1 5210 with the most recent OTA update.
Last night I attempted to root my device using this:
androidxda (DOT) com/root-samsung-galaxy-tab-3-10-1-gt-p5210
It claimed successful and my device started to reboot and hung up at the Samsung GALAXY TAB 3 screen. I am unable to get to recovery mode on the device. Only able to go to download mode. I have tried several options but have been unable to find a way to flash it successfully. The flashes i have tried downloading were all in .zip and that obviously isn't able to be used in Odin. I have researched how to convert the files into a .tar but I don't have linux. Can someone please help me because I need my tablet. I know it can be saved but I can't seem to locate the answers. I am also getting concerned that it is unable to charge the battery being in the condition it is in now so I am trying to conserve the battery on the tablet until it is absolutely needed. Thanks.

cameron72 said:
I have been searching the forum and google and have been unable to reach a solution yet.
I am not a noob, but i am not an expert either so use small words ha.
I have a Samsung Galaxy Tab 3 10.1 5210 with the most recent OTA update.
Last night I attempted to root my device using this:
androidxda (DOT) com/root-samsung-galaxy-tab-3-10-1-gt-p5210
It claimed successful and my device started to reboot and hung up at the Samsung GALAXY TAB 3 screen. I am unable to get to recovery mode on the device. Only able to go to download mode. I have tried several options but have been unable to find a way to flash it successfully. The flashes i have tried downloading were all in .zip and that obviously isn't able to be used in Odin. I have researched how to convert the files into a .tar but I don't have linux. Can someone please help me because I need my tablet. I know it can be saved but I can't seem to locate the answers. I am also getting concerned that it is unable to charge the battery being in the condition it is in now so I am trying to conserve the battery on the tablet until it is absolutely needed. Thanks.
Click to expand...
Click to collapse
First of all - Welcome to xda
Your tab is soft bricked, something has gone wrong with your system files... Honestly it seems like you know enough to get it done, but are struggling a bit with the file formats. You are correct in saying that Odin won't use zip files, but you shouldn't have to convert anything to tar or download linux! If you extract the zip files, you should find a .tar or .tar.md5 file (inside the zip file) that Odin can use, put it in the PDA mode box, etc etc... If your downloads don't have the correct files inside them, try THIS thread.
Let me know if you get it sorted :good:

bob23bk said:
First of all - Welcome to xda
Your tab is soft bricked, something has gone wrong with your system files... Honestly it seems like you know enough to get it done, but are struggling a bit with the file formats. You are correct in saying that Odin won't use zip files, but you shouldn't have to convert anything to tar or download linux! If you extract the zip files, you should find a .tar or .tar.md5 file (inside the zip file) that Odin can use, put it in the PDA mode box, etc etc... If your downloads don't have the correct files inside them, try THIS thread.
Let me know if you get it sorted :good:
Click to expand...
Click to collapse
I had already tried the method and file in the forum you linked me to. It failed almost instantly. That's when I turned everything off and tossed it all to the back seat of my work truck before it got thrown at the windshield. I keep seeing people saying they have trwp or whatever. I don't even know what that is haven't researched that. Is it something i need as well?
I've never successfully rooted a Samsung device. I used to do this stuff a lot back with the droid x with Linux and everything was pretty simple. Does Samsung change their bootloader with each update like Motorola did then? I was wondering that when trying to install a firmware of a previous version that maybe that was the problem.
All I wanted root for was to just tweak some things and be happy. It has turned into a nightmare.

C,
hi,
the consistent/common thread of this problem is/seems to be taking the ota and trying unverified/gimmicky
root methods.
there are recoveries for the gt-p52xx in the tab 10.1 forum
the majority of samsung devices root as follows;
if a custom recovery exist, flash it.
then download recent or latest version of chainfire's supersu update zip, reboot to recovery
backup your rom first, then flash supersu, if everything goes well, once you have set up your stock rom with root in place
make a new backup.
samsung ota's are death incarnate, reject them.
goto the tab 10 forum and get busy ! you said it yourself, you're not a noob, you know the drill. :good:
m

moonbutt74 said:
C,
hi,
the consistent/common thread of this problem is/seems to be taking the ota and trying unverified/gimmicky
root methods.
there are recoveries for the gt-p52xx in the tab 10.1 forum
the majority of samsung devices root as follows;
if a custom recovery exist, flash it.
then download recent or latest version of chainfire's supersu update zip, reboot to recovery
backup your rom first, then flash supersu, if everything goes well, once you have set up your stock rom with root in place
make a new backup.
samsung ota's are death incarnate, reject them.
goto the tab 10 forum and get busy ! you said it yourself, you're not a noob, you know the drill. :good:
m
Click to expand...
Click to collapse
I have tried the recoveries in the forum and it failed seconds after starting.
I don't do this stuff regularly as I don't hardly have the time. I haven't done anything of this nature in years so I'm well out of the loop on things..

cameron72 said:
I have tried the recoveries in the forum and it failed seconds after starting.
I don't do this stuff regularly as I don't hardly have the time. I haven't done anything of this nature in years so I'm well out of the loop on things..
Click to expand...
Click to collapse
okay, hmm, when you say it fails, do you mean odin fails to flash and if so what is the reason/ouput ?
or do you mean that you are now in a recovery bootloop ?
note- though i go the full route of packing recovery.img's for odin flashing, the md5 checksum always seems to
come up as invalid, the working "remedy" is to remove the .md5 extension from the "odin-flashable-recovery".tar.md5 file
by renaming the file to "odin-flashable-recovery".tar
odin will no longer attempt the checksum verification but the recovery file will flash.
make sure you have samsung-usb-drivers for windows installed. on the main page of my devhost archive [link is in my signature]
you will find the tools you need. the possible problem is that the ota you installed may have overwritten your bootloader, for that i don't
have a reliable fix, so if anything make sure you also have the stock recovery ready to go as well as supersu update zip
already downloaded onto your device for rooting.
after you flash the custom recovery [with auto-restart in odin disabled] run the flash and wait for the res-ok message, give it another second or two then disconnect the tab and force reboot to recovery, home,vol-up and power, once in recovery make a full backup, then flash supersu zip and reboot, if you do go into recovery loop, force reboot to odin mode, home,vol-down and power, follow the on screen instruction, now reconnect your tab to pc and use odin to flash back stock recovery.
m

Okay guys I appreciate the help. I finally got it. I tried the method on Zachisimo's post on unbricking and finally got it installed.
After it installed, it left me with a bootloop and I was actually able to go into recovery mode this time and do a factory data reset and wipe cache then everything went well. I am a happy dude now.
Going to attempt rooting it again and does anyone have any suggestions on what ROM to install? I have never used any custom ROM's before so that is a new area for me. Feeling more confident knowing how to save it from the dead. :good::good::good:

cameron72 said:
Okay guys I appreciate the help. I finally got it. I tried the method on Zachisimo's post on unbricking and finally got it installed.
After it installed, it left me with a bootloop and I was actually able to go into recovery mode this time and do a factory data reset and wipe cache then everything went well. I am a happy dude now.
Going to attempt rooting it again and does anyone have any suggestions on what ROM to install? I have never used any custom ROM's before so that is a new area for me. Feeling more confident knowing how to save it from the dead. :good::good::good:
Click to expand...
Click to collapse
Hi,
Alright !'m glad you got it working, as to roms , all available roms currently are stock modifications , I use cag-rom, there's also pimp-droid
both kitkat.
m

moonbutt74 said:
Hi,
Alright !'m glad you got it working, as to roms , all available roms currently are stock modifications , I use cag-rom, there's also pimp-droid
both kitkat.
m
Click to expand...
Click to collapse
If you use it then thats what i shall try. First i gotta find a root, then I have seen many people recommend philz recovery, and then the rom?
question why does Restl3ss say wait 10minutes after installing a rom before doing anything?

cameron72 said:
If you use it then thats what i shall try. First i gotta find a root, then I have seen many people recommend philz recovery, and then the rom?
question why does Restl3ss say wait 10minutes after installing a rom before doing anything?
Click to expand...
Click to collapse
for root look up supersu update zip
ask Restl3ss :silly:
m

cameron72 said:
Okay guys I appreciate the help. I finally got it. I tried the method on Zachisimo's post on unbricking and finally got it installed.
After it installed, it left me with a bootloop and I was actually able to go into recovery mode this time and do a factory data reset and wipe cache then everything went well. I am a happy dude now.
Going to attempt rooting it again and does anyone have any suggestions on what ROM to install? I have never used any custom ROM's before so that is a new area for me. Feeling more confident knowing how to save it from the dead. :good::good::good:
Click to expand...
Click to collapse
Glad it worked out, recovering from brick does set you free from the stress induced by the disclaimers imo :silly:

5.1.1 OTA update not working

My phone is running the BOG5 5.0.1 software and it is a retail edition.
I recieved a notification on my device prompting me that a new update is available (finally! 5.1.1!) I tap "download now", the download eventually finishes and it proceeds to install.
My phone boots into recovery, "installing update" and very shortly after I see the droid triage error and below it says "error!" and then my phone reboots. When I unlock my phone it says, "Sorry, there was a problem updating your SAMSUNG SM-N910V. No changes were made."
I looked under software update in settings and it says "software not updated to N910VVRU2BOK3" and the error code is 410.
I also notice that when I go into recovery it says "dm-verity verification failed...."
I looked in Kies to see if the update was available there, and of course it wasn't. And I can't find the ROM anywhere as of yet to flash with ODIN.
I would appreciate all of the help I can get.
Thank you.

traceestarr said:
My phone is running the BOG5 5.0.1 software and it is a retail edition.
I recieved a notification on my device prompting me that a new update is available (finally! 5.1.1!) I tap "download now", the download eventually finishes and it proceeds to install.
My phone boots into recovery, "installing update" and very shortly after I see the droid triage error and below it says "error!" and then my phone reboots. When I unlock my phone it says, "Sorry, there was a problem updating your SAMSUNG SM-N910V. No changes were made."
I looked under software update in settings and it says "software not updated to N910VVRU2BOK3" and the error code is 410.
I also notice that when I go into recovery it says "dm-verity verification failed...."
I looked in Kies to see if the update was available there, and of course it wasn't. And I can't find the ROM anywhere as of yet to flash with ODIN.
I would appreciate all of the help I can get.
Thank you.
Click to expand...
Click to collapse
I'm having the exact same issue and symptoms, have you made any progress with this? If I find a solution I'll share here too. I've tried Kies and VZW Software Upgrade Assistant, neither finds the update, but I can get it on my retail VZ Note 4, just won't successfully install.

Keiller said:
I'm having the exact same issue and symptoms, have you made any progress with this? If I find a solution I'll share here too. I've tried Kies and VZW Software Upgrade Assistant, neither finds the update, but I can get it on my retail VZ Note 4, just won't successfully install.
Click to expand...
Click to collapse
Thank you for your feedback. I wonder if it has to do with a corrupt software build on our devices. I ordered my phone in November of last year and it came with BOG5 on it. I'm going to see about flashing stock BOG5 completely fresh on the phone and see if that corrects the issue.

traceestarr said:
Thank you for your feedback. I wonder if it has to do with a corrupt software build on our devices. I ordered my phone in November of last year and it came with BOG5 on it. I'm going to see about flashing stock BOG5 completely fresh on the phone and see if that corrects the issue.
Click to expand...
Click to collapse
I have similar issue ,i don't have a update yet showing on my device so i await for it to show up. Please let us know if flashing it makes the difference.

traceestarr said:
Thank you for your feedback. I wonder if it has to do with a corrupt software build on our devices. I ordered my phone in November of last year and it came with BOG5 on it. I'm going to see about flashing stock BOG5 completely fresh on the phone and see if that corrects the issue.
Click to expand...
Click to collapse
Sounds like something worth trying, I'll watch for an update on how it goes for you. Thanks!

I have found a solution (albeit requires a full wipe, which is worth having 5.1.1 for me)
Firstly, I attempted flashing the "stock restore" file in odin and resulted in an error, I then tried the full firmware instead (mind you for BOG5, if you're having problems on your current version I'd suggest using your current build) with success, proceed with a data wipe in recovery and noticed that the "dm-verity verification failed...." message is now gone and now that bottom area of the screen has information about applying Multi-CSC.
Restart the phone, set up as normal and go straight for the software update. My phone downloaded and installed the update perfectly! For safety just boot into recovery and do a full wipe again, and there you have it!
The stock firmwares for RETAIL SM-N910V are here: http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937

traceestarr said:
I have found a solution (albeit requires a full wipe, which is worth having 5.1.1 for me)
Firstly, I attempted flashing the "stock restore" file in odin and resulted in an error, I then tried the full firmware instead (mind you for BOG5, if you're having problems on your current version I'd suggest using your current build) with success, proceed with a data wipe in recovery and noticed that the "dm-verity verification failed...." message is now gone and now that bottom area of the screen has information about applying Multi-CSC.
Restart the phone, set up as normal and go straight for the software update. My phone downloaded and installed the update perfectly! For safety just boot into recovery and do a full wipe again, and there you have it!
The stock firmwares for RETAIL SM-N910V are here: http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937
Click to expand...
Click to collapse
Thank you for reporting back with what worked for you. I've tried following the same steps you took, but after flashing the full BOG5 firmware and doing a data wipe and then doing basic setup on my phone, the OTA is still failing, Error Code: 404. I'll try again, but so far no success. Still stuck on the buggy 5.0.1, the version where you can't flash back to 4.4.4....

Keiller said:
Thank you for reporting back with what worked for you. I've tried following the same steps you took, but after flashing the full BOG5 firmware and doing a data wipe and then doing basic setup on my phone, the OTA is still failing, Error Code: 404. I'll try again, but so far no success. Still stuck on the buggy 5.0.1, the version where you can't flash back to 4.4.4....
Click to expand...
Click to collapse
I am sorry to hear that this didn't work for you. But it appears we're both getting different error codes. Does your recovery display issues with dm-verity failing? I think this was part of my problem in the first place.

traceestarr said:
I am sorry to hear that this didn't work for you. But it appears we're both getting different error codes. Does your recovery display issues with dm-verity failing? I think this was part of my problem in the first place.
Click to expand...
Click to collapse
You're right, I thought I had seen that message earlier in the week while trying to get the OTA for 5.1.1 to work, but I didn't write it down. Your description of symptoms matched mine so well I figured it had to be the same issue or something so similar that running through the same process would work for me too.
I may take the phone into Verizon to show them the update fail and see if they are willing to do anything for me....
Glad you got yours up and running, but I am just a little bit jealous

Keiller said:
You're right, I thought I had seen that message earlier in the week while trying to get the OTA for 5.1.1 to work, but I didn't write it down. Your description of symptoms matched mine so well I figured it had to be the same issue or something so similar that running through the same process would work for me too.
I may take the phone into Verizon to show them the update fail and see if they are willing to do anything for me....
Glad you got yours up and running, but I am just a little bit jealous
Click to expand...
Click to collapse
I've found that most times the OTA update fails prior to rebooting to install the update and I get the 404 error I reported earlier. However, when it does make it to the point of doing the OTA update after reboot, after that fails, I get the same 410 error you reported, see attached, and I also the dm-verity fail message in recovery. Then after using Odin to install BOG5, the verity fail disappears, replaced by a Multi-CSC message, I do a complete data wipe/factory reset, set up my basic google account and try the OTA, which fails every time. But once the dm-verity fail is gone, I can try doing an update from external storage, which I've tried with the BOK3 5.1.1 zip file posted here: http://forum.xda-developers.com/not...id-5-1-1-according-to-website-t3290683/page20 However, this still fails to load.
At this point I'm pretty convinced that I some other issue with my phone. I found elsewhere that someone was able to take their phone into Best Buy and have them flash the 5.1.1 update for them via Kies. That is probably my next step.
But I wanted to share what I've tried in case anyone else is experiencing the same dead end or in the off chance that someone has found a solution.
Sure would love to see the full 5.1.1 BOK3 tar.md5 sometime before Marshmallow hits, pretty sure using Odin to install the update that way would work....

traceestarr said:
I am sorry to hear that this didn't work for you. But it appears we're both getting different error codes. Does your recovery display issues with dm-verity failing? I think this was part of my problem in the first place.
Click to expand...
Click to collapse
The full OTA for 5.1.1 was posted and I was able to update using Odin, following the instructions on this post: http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
Just wanted to update this post with the solution which finally worked for me.

BootLoop problems

Hi, I currently have a Samsung Galaxy S7 Active and while updating, it went into a bootloop. I cant boot into recovery, odin fails to flash the stock rom, and all I get when booting is:
SAMSUNG
Galaxy S7 Active
Powered By
android
screen. It doesn't even go to that, all it does is boots into recovery. I don't want to send it out for repairs (Mostly because I am broke).
If also, may I get answers from people that own one and been in this problem before and/or people that know how to repair this issue.
Also, I can only use the Stock Recovery.
Thanks, Nysean01'
Edit: I have also been to this. It was no help what so ever and got me deeper to this point in the post.
Edit 2: I have a backup phone and that one is currently working. I still wanna keep using my newer one.

which rom/version was you on?
which you trying to get to?
which ones have you tried in odin?
are you loading all the files ?
does it say it completes successfully ?

miniminus said:
which rom/version was you on?
which you trying to get to?
which ones have you tried in odin?
are you loading all the files ?
does it say it completes successfully ?
Click to expand...
Click to collapse
7.0
Not trying to change
Yes, I'm loading all the files
Nope. It says in red, FAIL.

then i would guess that the file is currupt, or maybe the cable is dodge...
but which version was you on before (QB2) and which you tried so far ? (QD4 ?)

miniminus said:
then i would guess that the file is currupt, or maybe the cable is dodge...
but which version was you on before (QB2) and which you tried so far ? (QD4 ?)
Click to expand...
Click to collapse
I was running the latest version of everything. 7.0 for phone, 10 for computer, and a mod odin.

Try a different Odin package, an older stock ROM and a different cable.

Which ones would you recommend?

Odin 3.12.4 and PI2, that is the earliest on BL2, try that, and if it works you should be able to OTA back up.

Mark as closed. I took it to the store, and even they said that they cant do nothing about it. So, Since I had the warranty (didn't know, was a hand me down), Samsung is sending me a new phone.

I have the same problem, got stuck on Nand writel. Already try different odin versions, I was on the last stock room, the problem was that I heva virus and had to do a hard reset, but when I finish got stuck on google verification, after try a lot of times I decided to fls stock room, but I fail.
What I can do it?

Unable to Flash due to multiple issues on S9

Hi
I have a Samsung Galaxy S9 (SM-G960F) Exynos, branded under Australian Optus and have been trying to load the latest Lineage Rom onto it but have ran into a multitude of issues. I'm going to list all of the things I've done and the Errors I've recieved
Developer Tools Enabled -> OEM Unlock Enabled (Forced Wipe) -> Developer Tools Enabled -> OEM Already Enabled -> USB Debugging Enabled -> ADB Tools installed and enabled (Computer trusted)
From Heimdall I tried flashing Lineages own bootloader from their website. I ended up getting the error "Failed to Receive Session End Confirmation"
My phone would also display the message "Only Official Released Binaries Are Allowed To Be Flashed"
I was also told RMM State played a part in this and if it was Prenormal, it wouldn't work. I went to check and sure enough, my phones RMM State was Prenormal
Despite this, I tried sideloading the packages anyway because I was told that just because it said that message, didn't mean it failed. Those ended up also failing, telling me the installation was aborted because of a validity error
From there, I was told to use Odin. That failed. I ended up switching to TWRPs bootloader instead and that also failed
After that I tried Flashing the Stock Android 10 Rom but that didn't solve any of the issues
I also tried downgrading to Android 8 Oreo to see if I could load everything from there but got the error SW REV CK FAIL
Dr Ketons Guide did not work as I was unable to Flash TWRP so I couldn't follow that route
I have the no Verity File downloaded but no way to apply it. Same with Magisk and Magisk Manager
Does anyone know what I can possibly do to try and get these things loaded onto my phone. I really would like to get them working as my main sim card is Vodafone so I'm unable to use it with this phone. Flashing the Stock unbranded XSA rom didn't seem to fix this issue either. The phone isn't under any contract or warranty, however I have no idea if its locked or unlocked.
Thanks

if you are in the prenormal state that means you can't modify your phone for like a week, just wait for the time. then it should work
by reading what you did, I didn't see anything wrong. it's just the prenormal thing that you have to wait for 7 days
edit: also forgot to mention if you failed to modify the phone after the prenormal state ends, you might need another 7 days to be able to modify your phone again

B1nz said:
if you are in the prenormal state that means you can't modify your phone for like a week, just wait for the time. then it should work
by reading what you did, I didn't see anything wrong. it's just the prenormal thing that you have to wait for 7 days
edit: also forgot to mention if you failed to modify the phone after the prenormal state ends, you might need another 7 days to be able to modify your phone again
Click to expand...
Click to collapse
So I waited 7 Days and its still prenormal. What should I do now. I tried flashing anyway to see if it was just a visual thing but it still failed. The phone was on for the whole 7 days.

CrashSpyro said:
So I waited 7 Days and its still prenormal. What should I do now. I tried flashing anyway to see if it was just a visual thing but it still failed. The phone was on for the whole 7 days.
Click to expand...
Click to collapse
I don't know it will work or not, have you try to flash the lastest stock firmware, do the initial first android setup (just skip everything), once you finish the setup go to download mode then try to flash the twrp through odin.
I used that method everytime I failed at flashing new rom. Hope it's also works for you, since my phone is also came from Australia

B1nz said:
I don't know it will work or not, have you try to flash the lastest stock firmware, do the initial first android setup (just skip everything), once you finish the setup go to download mode then try to flash the twrp through odin.
I used that method everytime I failed at flashing new rom. Hope it's also works for you, since my phone is also came from Australia
Click to expand...
Click to collapse
Unfortunately I have already tried that and it ended up not working