Database Info

[Q] Help - I bricked my phone with latest VZW update

Ok, I have a phone that I purchased used. When my S3 got the Jellybean update in December, I found out it had Clockwork Recovery Mod installed on it. It scared the hell out of me, but I went ahead with the update and it was fine. I am a complete newb to rooting and would never root my phone (I lack the skills). When the update went through in December, I was relieved. For more details on all that, see this thread: http://forum.xda-developers.com/showthread.php?t=2048805
Today's update was a different story. This update appears to have broken my phone.This time, it won't even boot up. It just say "System software not authorized by Verizon Wireless has been found on your phone and go to the nearest Verizon Wireless Store for help." Any suggestions on how to fix this? Am I completely screwed? I have almost no knowledge of rooting, ODIN, etc.

R: [Q] Help - I bricked my phone with latest VZW update
It's not bricked.. you should be able to get in download mode and flash a stock firmware with Odin..
edit: I'll link you the url's to the howto's as soon as I get to my pc
Sent from my GT-I9300 using xda premium

zeroblu3 said:
It's not bricked.. you should be able to get in download mode and flash a stock firmware with Odin..
edit: I'll link you the url's to the howto's as soon as I get to my pc
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
The weirdest thing just happened. Ok, I put in ODIN mode and pressed cancel. Then like 3 minutes later, it just started up all on its own. The update failed of course but the phone is working again. Weird. Was able to turn it off and restart.
I think I may trade this phone back into the same folks who sold it to me. I am clearly not cut out for this.

i'm glad the problem solved by itself
anyway if you still want to attempt to reset the phone to stock here is everything you should need to know :
http://forum.xda-developers.com/showthread.php?t=1762709 (take a look at section 5)
it's really not as hard as it looks...just be aware there is always a chance that something could go wrong....just take your time, read, and only go ahead if you are fully confident and willing to accept the risks...
let us know how it went and don't hesitate to ask for help if you are still in doubt after reading the forum

I hate how I am average Joe with my root knowledge and I could fix your phone without thinking twice.
It surprises me you have an xda account and can not even root and unlock boot loader.
You ask for help then say. Never mind.
Haha whatever works for you at the end of the day.
Sent from club Clean Rom

Soft brick help

Hey guys, I somehow managed to soft brick my verizon GS3 this afternoon. I just need a little help in getting the thing back up and running and possibly an explanation on were I went wrong. I thought I had unlocked the bootloader and then rooted the phone. I managed to install TWRP 2.5.0.0 and do a backup. Then I installed a custom ROM and got the infamous "Software not authorized" message with the yellow triangle.
1st, is it possible to get this far with the bootloader still being locked??
2nd, If I understand correctly, I need to use ODIN to go back to stock and start over. Correct? Or is there another way to salvage this situation. If I have to go back to stock, can someone point me to the latest files? I've found links to a lot of different ones and I don't want to make a bad situation worse. BTW, I can't get into recovery but I can get into ODIN mode.
Any help is greatly appreciated!!

Ok, using ODIN, I was able to get a stock ROM onto the phone and get the thing booted. So essentially I'm back to square 1 and I still didn't figure out what I did wrong the first time around. Bummer Eh?

scheirere said:
Ok, using ODIN, I was able to get a stock ROM onto the phone and get the thing booted. So essentially I'm back to square 1 and I still didn't figure out what I did wrong the first time around. Bummer Eh?
Click to expand...
Click to collapse
Yea, I soft bricked once and was able to boot into recovery by holding volume up, power, and home at the same time while the phone was off. I thanked my lucky stars I had a nandroid backup. I would make sure you unlocked the boot loader properly. When I first started rooting YouTube was great for instructions. I would post a link to a YouTube video but it won't allow me until I have ten posts, I swear some of these rules are retarded. Anyway search in YouTube having visual and audio guide helps a lot. good luck!

Samsung S3 Verizon, might be bricked, dont know what to do URGENT

Hey guys, i was messing around with TWRP to get Marchmallow onto my phone, i when i did something with it whenever i boot my phone it gives me this "System software not authorized by Verizon Wireless has been found on your phone. Please turn of your phone and go to the nearest Verizon Wireless store for help" and on the top left corner of my screen it says in read, "SECURE FAIL: KERNEL"
I dont know what to do, i dont care about getting Marshmallow or recovering my data(already backed up all the things i needed on my computer) I just want to be able to get into my phone and use it like i use too. Please help urgently i need my phone back.
Also, i apologize if this is in the wrong place in your forums, this is my first time using it.

Trafalgar747 said:
Hey guys, i was messing around with TWRP to get Marchmallow onto my phone, i when i did something with it whenever i boot my phone it gives me this "System software not authorized by Verizon Wireless has been found on your phone. Please turn of your phone and go to the nearest Verizon Wireless store for help" and on the top left corner of my screen it says in read, "SECURE FAIL: KERNEL"
I dont know what to do, i dont care about getting Marshmallow or recovering my data(already backed up all the things i needed on my computer) I just want to be able to get into my phone and use it like i use too. Please help urgently i need my phone back.
Also, i apologize if this is in the wrong place in your forums, this is my first time using it.
Click to expand...
Click to collapse
Did you try to install another ROM,it might work out,there are many other ROMs with marshmallow,you should try that or if it doesn't work then use adb to flash a rom

Trafalgar747 said:
Hey guys, i was messing around with TWRP to get Marchmallow onto my phone, i when i did something with it whenever i boot my phone it gives me this "System software not authorized by Verizon Wireless has been found on your phone. Please turn of your phone and go to the nearest Verizon Wireless store for help" and on the top left corner of my screen it says in read, "SECURE FAIL: KERNEL"
I dont know what to do, i dont care about getting Marshmallow or recovering my data(already backed up all the things i needed on my computer) I just want to be able to get into my phone and use it like i use too. Please help urgently i need my phone back.
Also, i apologize if this is in the wrong place in your forums, this is my first time using it.
Click to expand...
Click to collapse
Verizon devices with newer firmware than 4.3 and up have a locked bootloader, you can't flash TWRP or custom ROMs and you can't unlock the bootloader, you also can't downgrade to an older version with unlocked bootloader. You're stuck with locked bootloader, anything you try to get around it will only brick your device.
If you can get to download mode, flash your stock firmware in Odin.
If that doesn't work you may need to use an unbrick.img to boot from sdcard to fix the device.
Or you may need to send it in for a JTAG service.

Droidriven said:
Verizon devices with newer firmware than 4.3 and up have a locked bootloader, you can't flash TWRP or custom ROMs and you can't unlock the bootloader, you also can't downgrade to an older version with unlocked bootloader. You're stuck with locked bootloader, anything you try to get around it will only brick your device.
If you can get to download mode, flash your stock firmware in Odin.
If that doesn't work you may need to use an unbrick.img to boot from sdcard to fix the device.
Or you may need to send it in for a JTAG service.
Click to expand...
Click to collapse
Hey, ive flashed my phone using Odin and i can now access my recovery mode. I am running Android 4.4.2. How can i unlock the bootloader?

Trafalgar747 said:
Hey, ive flashed my phone using Odin and i can now access my recovery mode. I am running Android 4.4.2. How can i unlock the bootloader?
Click to expand...
Click to collapse
Read my post that you quoted again and pay attention to the details and you'll get your answer. If you had paid attention to exactly what I posted then you wouldn't be asking that question.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE

Droidriven said:
Read my post that you quoted again and pay attention to the details and you'll get your answer. If you had paid attention to exactly what I posted then you wouldn't be asking that question.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
"If you can get to download mode, flash your stock firmware in Odin.
If that doesn't work you may need to use an unbrick.img to boot from sdcard to fix the device.
Or you may need to send it in for a JTAG service."
Sorry about that, could you elaborate more on my options? What do you mean by flash my stock firmware in Odin (sorry if thats sounds stupid i dont know about this) And what unbrick.img?

Trafalgar747 said:
"If you can get to download mode, flash your stock firmware in Odin.
If that doesn't work you may need to use an unbrick.img to boot from sdcard to fix the device.
Or you may need to send it in for a JTAG service."
Sorry about that, could you elaborate more on my options? What do you mean by flash my stock firmware in Odin (sorry if thats sounds stupid i dont know about this) And what unbrick.img?
Click to expand...
Click to collapse
You just said you flashed your device with Odin, why are you asking about how to flash your stock firmware, that's what you already did isn't it?
As for the unbrick.img, you need an unbrick.img pulled from a working device with your model number and your same stock android version (4.4.2), then there is a method for using that unbrick.img to boot from sdcard.
This information is here at XDA in the Verizon S3 forum if you take the time to look.
If you don't have sense enough to research your device model before you flash anything custom or if you don't know what you're doing and how to fix things when they go wrong then you should leave your device alone because flying by the seat of your pants and just assuming you can flash whatever you want is only going to cost you a lot of money in the end. You're lucky you didn't hard brick your device, that can't be fixed even by Samsung, if you had done your research you would know that. I suggest you stop where you are and start reading everything you can about the Verizon S3 i535 and what you can and can't do with it.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE

Kyocera Brigadier screen black with back light.

I bought a new Brigadier off ebay. Phone is new and never used. The build date was July 2014 and KK 4.4.2. I should have paid more attention to the numbers. After the KK update my phone boots up but does not show anything after the Kyocera screen. It is black with the back light.
This is what I did. I put my SIM card in the phone to check that I can activate it. Then while I was testing out the phone. It downloaded the first update. I do not remember what the number is. The phone had never been used. It was new. I might be able to look it up for update history on big reds site. I did not do the do the update. After seeing it was done. I turned it off and put the SIM card backing the Turbo. After doing some research on rooting. I found that Kingroot (5.0.4) is best, then found this app I can use to remove Kingroot. Last night I was playing more with the phone and then rooted it too. I rebooted it, hotspot my turbo, downloaded root checker, confirmed root, then undated. Phone is at 80% life. Phone shut off and then I let it do its thing. When I came back, the screen is black with the back light on only. I can touch the screen and feel/hear the vibration. I can soft boot, hard boot, and reboot into stock recovery. I did a factory wipe after I read in how to boot stock recovery. Yes, did nothing. I do know that KK updates can kill your phone. My Droid HD maxx is dead. On that phone, the led light lights green up and the computer does make a sound when connected but does not show it. I have no idea if this has a rsd lite and file to flash. I did not change anything in the system at all. I did not think that Kingroot would mess with my phone if I did the ota. I would then buy this app and remove it. I was waiting for internet to be installed today to further mess with my phone before using it. I do not know how to pull info off my phone.

I know more about Motorola Droid phones. This is phone is new to me. I did do a lot of research out there and mainly on XDA. I have the option to return the phone for a full refund. I would like to see if I can fix the phone before hand. I have till this weekend to send it back.

Claps1775 said:
I bought a new Brigadier off ebay. Phone is new and never used. The build date was July 2014 and KK 4.4.2. I should have paid more attention to the numbers. After the KK update my phone boots up but does not show anything after the Kyocera screen. It is black with the back light.
This is what I did. I put my SIM card in the phone to check that I can activate it. Then while I was testing out the phone. It downloaded the first update. I do not remember what the number is. The phone had never been used. It was new. I might be able to look it up for update history on big reds site. I did not do the do the update. After seeing it was done. I turned it off and put the SIM card backing the Turbo. After doing some research on rooting. I found that Kingroot (5.0.4) is best, then found this app I can use to remove Kingroot. Last night I was playing more with the phone and then rooted it too. I rebooted it, hotspot my turbo, downloaded root checker, confirmed root, then undated. Phone is at 80% life. Phone shut off and then I let it do its thing. When I came back, the screen is black with the back light on only. I can touch the screen and feel/hear the vibration. I can soft boot, hard boot, and reboot into stock recovery. I did a factory wipe after I read in how to boot stock recovery. Yes, did nothing. I do know that KK updates can kill your phone. My Droid HD maxx is dead. On that phone, the led light lights green up and the computer does make a sound when connected but does not show it. I have no idea if this has a rsd lite and file to flash. I did not change anything in the system at all. I did not think that Kingroot would mess with my phone if I did the ota. I would then buy this app and remove it. I was waiting for internet to be installed today to further mess with my phone before using it. I do not know how to pull info off my phone.
Click to expand...
Click to collapse
The update you did was a stock update, correct?
You said the device was rooted and then you did the update, correct?
That's where you screwed up, you can't do stock updates on a rooted device, you have to remove root, have stock recovery and have an unmodified system partition before doing the update.
You should have done the update and THEN rooted the device.
Now just do a Google search for:
"How to unbrick (your model number)"
Sent from my SM-S903VL using Tapatalk

Droidriven said:
The update you did was a stock update, correct?
You said the device was rooted and then you did the update, correct?
That's where you screwed up, you can't do stock updates on a rooted device, you have to remove root, have stock recovery and have an unmodified system partition before doing the update.
You should have done the update and THEN rooted the device.
Now just do a Google search for:
"How to unbrick (your model number)"
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Yes and yes. Okay. I know with droids when I was bootloader locked and rooted. I was fine updating. There was a change on loosing root. It's all about learning. I will try to find out how to unblock my phone. Thank you for the response.

Have you came across the ota .IMG file?

I was able to power my phone off. I connected the phone to my computer, installed the software, and tried the repair part. Failed on downloading. Version on my phone is 1.102VZ.

I found more info on xda refuring to the http://4pda.ru/forum/index.php?showtopic=597313&st=3680 site. I am not able to do anything with my phone now. Cannot get it to boot in recovery or even have my pc see it. The verizon apk sees it where I can still try to repair or update. That is it. I am going to send it back for a full refund and be done with this phone. Cannot spend weeks trying to fix this right now. Thanks all for the help.

Update. I got my phone into Fastboot. I was able to get phone into twrp recovery. How ever, I am not able to find a img I can flash to my phone then I will be able to use my phone. Ones I have found are twrp back ups that I have no clue how to flash. I downloaded Rom_5.1.1_3153LR_Modem_3153LR_E6782 and I hope to see if I can flash it or not in twrp. I still do not understand Android_SDK and how to use it. I am not sure if I can use twrp recovery from the Kyocera Brigadier E6782 Toolkit v1.2 I downloaded from the http://4pda.ru/forum/index.php?showtopic=597313&st=620#entry35662165 or not. All I am doing now is trying and seeing what happens. If anyone knows more please share.

I was able to flash the Rom_5.1.1_3153LR_Modem_3153LR_E6782 and my phone booted up and went into the optimizing but it is in Russian. I am further than I was. Need to find out if this is changeable to English and it all works. Yes, I do know that I will not flash anything than 5.0 now since the bootloader is locked or it can be unlocked with a code. Phone is up and running. I need a 5.1.1 US now.
It is not in Russian. It is in vietnamese. But I still need a clean 5.0 full rom.

Claps1775 said:
Update. I got my phone into Fastboot. I was able to get phone into twrp recovery. How ever, I am not able to find a img I can flash to my phone then I will be able to use my phone. Ones I have found are twrp back ups that I have no clue how to flash. I downloaded Rom_5.1.1_3153LR_Modem_3153LR_E6782 and I hope to see if I can flash it or not in twrp. I still do not understand Android_SDK and how to use it. I am not sure if I can use twrp recovery from the Kyocera Brigadier E6782 Toolkit v1.2 I downloaded from the http://4pda.ru/forum/index.php?showtopic=597313&st=620#entry35662165 or not. All I am doing now is trying and seeing what happens. If anyone knows more please share.
Click to expand...
Click to collapse
You can use the TWRP backups by choosing the restore option in TWRP then selecting the backup file and it will restore the data in the file to your device.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
You can use the TWRP backups by choosing the restore option in TWRP then selecting the backup file and it will restore the data in the file to your device.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I will try that. I have to get it into fastboot and that can take a few tries. The firmware I have on it has no verizon apps. It is a mod by someone. I am going to try original firmware 5.1.1 firmware. Downloading right now. it is a .rar file. Making head way witch is good. I am learning for sure.

I got into fastboot mode. I tried to go into twrp using the Kyocera Brigadier E6782 Toolkit v1.2 as I did before. Now, I am stuck at the Android screen and it will not go into twrp. Ahh.

Claps1775 said:
I got into fastboot mode. I tried to go into twrp using the Kyocera Brigadier E6782 Toolkit v1.2 as I did before. Now, I am stuck at the Android screen and it will not go into twrp. Ahh.
Click to expand...
Click to collapse
That's because of your now locked bootloader, can't use TWRP with locked bootloader.
It's a little late now, you need to slow down, if you had done some searching to see how to use TWRP backups(the information is literally everywhere in every device forum here, it works the same for all devices), you would have been able to restore one of those backups, you'd have the device fixed and you wouldn't have a locked bootloader, that bootloader limits your options now, it leaves you only the option of finding the correct stock firmware.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
That's because of your now locked bootloader, can't use TWRP with locked bootloader.
It's a little late now, you need to slow down, if you had done some searching to see how to use TWRP backups(the information is literally everywhere in every device forum here, it works the same for all devices), you would have been able to restore one of those backups, you'd have the device fixed and you wouldn't have a locked bootloader, that bootloader limits your options now, it leaves you only the option of finding the correct stock firmware.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I never knew it was unlock. On the Android screen it had a 1 at the top left corner and it is still there. I am trying to find the correct firmware and flash it. I am able to see my phone in the adb file I used to flash twrp on my Droids. I have done a lot of research and and the 4pda.ru site. I am sent a lot of pms out to XDA memebers and got nothing back. I have posted a lot and hope someone would replay. I am trying trust me. I flash the wrong one. If I brink the phone, O well. All I can say is I am not trying to give up. Not sure if I can flash a rom or a twrp back up in adb or not. I would like to sit and read up on all of this. Then I could have a better understanding and then may play more.
How can flashing the Rom_5.1.1_3153LR_Modem_3153LR_E6782 even lock the bootloader? Eventhing I read talked about it being locked. It says in the box, Failed (remote: bootimage: incomplete or not signed) when I try to boot it into twrp.

Claps1775 said:
I never knew it was unlock. On the Android screen it had a 1 at the top left corner and it is still there. I am trying to find the correct firmware and flash it. I am able to see my phone in the adb file I used to flash twrp on my Droids. I have done a lot of research and and the 4pda.ru site. I am sent a lot of pms out to XDA memebers and got nothing back. I have posted a lot and hope someone would replay. I am trying trust me. I flash the wrong one. If I brink the phone, O well. All I can say is I am not trying to give up. Not sure if I can flash a rom or a twrp back up in adb or not. I would like to sit and read up on all of this. Then I could have a better understanding and then may play more.
How can flashing the Rom_5.1.1_3153LR_Modem_3153LR_E6782 even lock the bootloader? Eventhing I read talked about it being locked. It says in the box, Failed (remote: bootimage: incomplete or not signed) when I try to boot it into twrp.
Click to expand...
Click to collapse
It locks the bootloader because when you flash the Firmware it upgrades to a different bootloader, one that is locked, it's coded into the firmware, it is intended to verify software signatures at boot, if the signature isn't what it's looking for it won't allow the software to load. Your TWRP, for example won't boot because it doesn't have the right signature, only your stock firmware has the right signature and there isn't a way to fake it. Your only chance of using TWRP is if your bootloader can be unlocked, not all bootloaders can be unlocked. It's a security measure installed by the manufacturer or your carrier to prevent flashing and modding the device, it's pretty effective and has become very common on a lot of devices since KitKat. It was implemented because they got tired of replacing devices due to the user modifying them and screwing them up, modified devices technically void the warranty but if screwed up enough they can't tell it has been modified, thus, they've been replacing devices that they weren't obligated to replace, they know this and are trying to put a stop to it.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
It locks the bootloader because when you flash the Firmware it upgrades to a different bootloader, one that is locked, it's coded into the firmware, it is intended to verify software signatures at boot, if the signature isn't what it's looking for it won't allow the software to load. Your TWRP, for example won't boot because it doesn't have the right signature, only your stock firmware has the right signature and there isn't a way to fake it. Your only chance of using TWRP is if your bootloader can be unlocked, not all bootloaders can be unlocked. It's a security measure installed by the manufacturer or your carrier to prevent flashing and modding the device, it's pretty effective and has become very common on a lot of devices since KitKat. It was implemented because they got tired of replacing devices due to the user modifying them and screwing them up, modified devices technically void the warranty but if screwed up enough they can't tell it has been modified, thus, they've been replacing devices that they weren't obligated to replace, they know this and are trying to put a stop to it.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I messed up a great phone I was looking forward of using. I thought I had it all lined up. I read a lot and thought I understood things. Can it befixed? By Kyocera only I say. I wanted on 5.0 is while I flashed that rom. I did not know it was a custom one. I truly feel bad that I messed up a great phone. I am going to stick with Motorola Droids and HTC for me wife. I am up very late trying to figure this all out. I am going to stick with things I know even though I love a challenge and learning. Thank you for the help, yes, I should have slowed down but everything was going great. Live and learn.

Claps1775 said:
I messed up a great phone I was looking forward of using. I thought I had it all lined up. I read a lot and thought I understood things. Can it befixed? By Kyocera only I say. I wanted on 5.0 is while I flashed that rom. I did not know it was a custom one. I truly feel bad that I messed up a great phone. I am going to stick with Motorola Droids and HTC for me wife. I am up very late trying to figure this all out. I am going to stick with things I know even though I love a challenge and learning. Thank you for the help, yes, I should have slowed down but everything was going great. Live and learn.
Click to expand...
Click to collapse
When some, lose some.
For future reference, when you want to update or modify a device, try doing some research into what NOT to do or what can go wrong with that particular device and how to fix it if it does BEFORE you focus on what CAN be done on that device and before you actually do anything to the device. Cover the bases, ask questions, search for issues others might have had when they modified their device.
Remember, just because something is available for that device, doesn't mean you can use it. Things change from android version to android version and this stock firmware to that stock firmware for a device, such as whether the bootloader is locked or unlocked, among other possible differences that can turn things into a train wreck.
Android devices are all different and are not all done the same. What and how it is done on "this" device is not the same on "that" device.
Sent from my SM-S903VL using Tapatalk

S6 G920F stuck on boot logo

Not sure if my phone is a lost cause and only good as a door stop. My phone at one stage would only display a screen asking me to plug into smart switch to recover the phone so I tried that but smart switch wasn't happening. I downloaded the latest stock rom and installed it successfully via ODIN but now my phone will not get past the boot logo. I can only get into download mode, Any advise on if I can get my phone working again?
Thanks
Andrew

andrew88 said:
Not sure if my phone is a lost cause and only good as a door stop. My phone at one stage would only display a screen asking me to plug into smart switch to recover the phone so I tried that but smart switch wasn't happening. I downloaded the latest stock rom and installed it successfully via ODIN but now my phone will not get past the boot logo. I can only get into download mode, Any advise on if I can get my phone working again?
Thanks
Andrew
Click to expand...
Click to collapse
Bro, I've been there and this is why I made an account on xda to see if my s6 (G-920F) can be fixed in any way. Yesterday I had the same thing as you when I tried to re-flash the phone with its proper, latest stock-ROM (UK/EE Nougat 7.0). Given how it hadn't worked, the update attempt through Odin screaming a big "FAIL!" at me, I was afraid I had bricked it completely, so I proceeded to re-install TWRP with Odin by putting the phone in download mode. I wiped the phone again with TWRP and now I'm not sure what I have to do as I am stuck with the UK Nougat bootloader and nothing else on it.
Before this whole ordeal I had rooted the phone and unlocked the bootloader following some instructions from a Youtube video and successfully installed a nighty build of LineageOS, which was buggy as **** (couldn't answer calls, use data, use the camera and a ****ton of apps were just not working). Dumbly enough, I thought I could just remove it through a wipe and put something else back on it but oh was I wrong.
Right now I'd just want to get my phone back to working (like you), as I am out of a job and need to be able to take phone calls with a normal, working phone.
Sorry I couldn't be of much help, but yeah maybe a first step towards fixing it would be to flash TWRP recovery on it and through the terminal, see what bootloader version you have with the command "getprop ro.bootloader". At least you will know the version of the broken bootloader you're experiencing difficulties with and *hopefully* an actual dev from the forums will entertain themselves in trying to solve this noobish puzzle we've created for ourselves.
Seriously, if there is a dev ready to board this crazy adventure with us, please help.
My namesake or username is pretty much a clue to what got me into this position.

I wish it was that simple for me mate, I cant access the recovery menu, I've tried flashing various recovery options but cant boot into any of them. I'm certain I could fix the phone if I could get to recovery. I'm now leaning towards it being a hardware fault with my phone. As you have access to recovery I think you may have more luck with your phone.
TerribleChoices said:
Bro, I've been there and this is why I made an account on xda to see if my s6 (G-920F) can be fixed in any way. Yesterday I had the same thing as you when I tried to re-flash the phone with its proper, latest stock-ROM (UK/EE Nougat 7.0). Given how it hadn't worked, the update attempt through Odin screaming a big "FAIL!" at me, I was afraid I had bricked it completely, so I proceeded to re-install TWRP with Odin by putting the phone in download mode. I wiped the phone again with TWRP and now I'm not sure what I have to do as I am stuck with the UK Nougat bootloader and nothing else on it.
Before this whole ordeal I had rooted the phone and unlocked the bootloader following some instructions from a Youtube video and successfully installed a nighty build of LineageOS, which was buggy as **** (couldn't answer calls, use data, use the camera and a ****ton of apps were just not working). Dumbly enough, I thought I could just remove it through a wipe and put something else back on it but oh was I wrong.
Right now I'd just want to get my phone back to working (like you), as I am out of a job and need to be able to take phone calls with a normal, working phone.
Sorry I couldn't be of much help, but yeah maybe a first step towards fixing it would be to flash TWRP recovery on it and through the terminal, see what bootloader version you have with the command "getprop ro.bootloader". At least you will know the version of the broken bootloader you're experiencing difficulties with and *hopefully* an actual dev from the forums will entertain themselves in trying to solve this noobish puzzle we've created for ourselves.
Seriously, if there is a dev ready to board this crazy adventure with us, please help.
My namesake or username is pretty much a clue to what got me into this position.
Click to expand...
Click to collapse

andrew88 said:
I wish it was that simple for me mate, I cant access the recovery menu, I've tried flashing various recovery options but cant boot into any of them. I'm certain I could fix the phone if I could get to recovery. I'm now leaning towards it being a hardware fault with my phone. As you have access to recovery I think you may have more luck with your phone.
Click to expand...
Click to collapse
Oh dear.
Yeah it does sound like something got deeply ****ed up in this case. I had the luck to somehow get past the smart switch error when the phone died of low battery. As I attached it to the charger I quickly boot it into download mode before the screen would become a bootloop again and that's where I was able to reinstall the latest version of TWRP recovery. After that, I was able to flash a stock ROM of Nougat that didn't have a ****ed up bootloader like I had. Specifically the one from this thread: https://forum.xda-developers.com/galaxy-s6/help/device-5-binary-3-s6-sm-g920f-t3706025
by forumber2.
It's the Netherlands stock-ROM. Not sure if you're from the US and the carrier would be wrong with that CSC, but it was a good bet for me. I got my phone back to working normally now.
Worst case scenario I'd say see if you have a phone repair shop nearby and ask them an opinion on what could be wrong. I'm just an amateur like you.
Still, I wish you the best of luck with it. Maybe there's still some hope. :/