Related
I was working fine, enjoying my new HTC One S with CM9 rom installed. Well the battery life wasnt the best on it, and i didnt install the custom kernel. So I looked for the custom kernel download(on my phone, not on my computer) and i found a .zip file. Well I thought that you could just download the kernel straight to my phone and open it up with "Rom Manager" which i did, it than said i needed to reboot the phone in recovery to continue the installation, so I did... it took me to recovery "to continue the installation" well than I looked away, looked backed down and it was black.... and i have tried powering up, booting into boot loader, booting into recover, and nothing... its just BLACK! nothing works, its literally useless ATM. I really messed up, is there anyway to fix this? Thanks in advanced!
----EDIT----
I think I accidentally flashed the kernel like i would normally flash a rom.... cause i downloaded the .zip file(directly to my phone, not using a computer), than i tapped the download and it asked me if i wanted to open it up with rom manager, so i did. and i think rom manager thought i was flashing a rom, when i wasnt, it was a kernel.... am i screwed? or is there anyway out of this?
Do you know the exact kernel you flashed--where did it come from
Some you need to extract and push
Assume you just tried to boot into bootloader thru phone buttons
Does your pc recognize your phone when plugged in, if so can you open a command window and try to access phone as in adb devices then adb reboot bootloader
assuming you are familiar with sdk adb/fastboot comands
otherwise i don't know what else to say--may be bad--sorry
Came from an XDA thread
Here is where it came from: http://forum.xda-developers.com/showthread.php?t=1708676 from "sun90" (half way down the page "CM9 KERNEL remix edition.zip - [Click for QR Code] (5.53 MB, 9 views) ")
i downloaded that straight to my phone and opened it up with Rom Manager, which i think the app took it as a rom, and installed it like a rom even though it was not a rom. I just tried to access it through adb, it comes up with no devices my PC does recognize it when i plug it in though...
Ive tried to get into bootloader tons of times, it just stays black... :'(
Thanks for your answer!
You flashed a galaxy s2 kernel on your one s? why would you ever think that was a smart thing to do?
Looking at the updater script in that zip it seems it wipes some partitions, the partitions on a SGS2 and the ONE S are different, so if that script accidentally wiped say the hboot partition, or some other critical-for-boot partition, you have a fully bricked phone.
For any devs that may know what partitions are what on the One S, the script wiped
mmcblk0p7, and wrote a zimage to mmcblk0p5
---EDIT---
Normally this is a cwm flashable zip on the Samsung Galaxy S II, which is why rom manager flashed it, as it met all the requirements, the only issue is, it was not made for the ONE S and probably overwrote some important things.
I tried for hours and hours to fix the same issue on a friend's One S (same symptoms, not same cause) to no avail. I tried QPST and telnet and a ridiculous amount of things. Had to bring it to the store and get a new one.
Good luck, but I don't believe there's anything you can do to fix it.
Just answered your question in the help thread, Didnt see this thread too !
Im afraid its not looking good, I think your best bet would be to call your provider and blame it on an OTA update.
And hope for the best
Alright, thanks for the help!
Well it looks like i bricked my phone than.... I thought that CM9 was only on the One S, so I just looked for the CM9 kernel, which obviously was for the sg2, i feel like such a dumb ass now! haha well thanks for all the help guys! ill be heading to the t-mobile store today to blame it on a OTA:]
yeah, others wont agree with what your about to do but........
just act like a complete noob, dont mention anything about software / firmware / ROMs / bootloader etc ect
just say your phone made a noise, you selected update and it died lol
good luck--I know it is heartbreaking
not sure of your situation with carrier, but you could go thru Retention if needed
Hi peeps.
i'm very new to all this but sort of know the basics
i'm running on Axiom now but tried to flash cm10 but after install i got a black screen so had to do a restore.
Today i just flashed venom and after the instal process is done, i hear the start up music but nothing on the screen.
I have had 3 other roms on my phone and never had a problem!
these are the steps i do
download rom - place on sd
put phone in recovery
reset factory
reset cache
install from sd
when it finish's reboot
blank screen.
Am i missing something?
Any help would be great and i can't post on the thread because i'm a noob with less than 10 and dont want to spam my way to the 10 :silly:
you are missing a lot, like reading the OP page and following install instructions
you missed separate flash of boot image and wiping system plus data and caches
i wipe system 3x to be safe
rugmankc said:
you are missing a lot, like reading the OP page and following install instructions
you missed separate flash of boot image and wiping system plus data and caches
i wipe system 3x to be safe
Click to expand...
Click to collapse
Thanks but i think that is now the least of my problems!
I used Goomanager and installed CM10, When I did it i installed teamwin recovery. It started to do a lot of strange things, when it finally rebooted i got a load of errors "phone is not working" nearly every 10 seconds?
it will not connect via usb, i discovered the the SD was not mounted.
I tried to mount the SD but it doesnt work, so i rebooted to recovery and tried to mount there but its coming up with - error unable to mount? ive tried everything but no joy
please please help
Thanks:crying:
see if this is your situation
http://forum.xda-developers.com/showthread.php?t=1630459
can you connect phone to pc and use fastboot commands
rugmankc said:
see if this is your situation
http://forum.xda-developers.com/showthread.php?t=1630459
can you connect phone to pc and use fastboot commands
Click to expand...
Click to collapse
I've got a mac
not sure what fastboot is.
I'll check out the link, and thank you very much for trying to help:good:
sorry i do know what fastboot is, yes can get in to it. but ive gone from CWM to teamwin recovery if i go in to the recovery section but that wont let me do anything because the mount. cant even load the phone up
I don't know Mac commands
My idea is to install htc drivers and set up fastboot/adb on pc--the info can be found in dev section on rooting
then open a command window and and boot into fastboot and flash a new recovery, maybe stock per the link, clear storage and try to get mounted
how did you unlock bootloader--
you will need to do alot of reading on adb/fastboot and flashing roms--first step is to have backups of rom and sdcard
since i don't the Mac commands to do fastboot, someone else will chime in at some point
you can alos go to the noob section in Q&A and resubmit your issue
someone will work you thru this, but in meantime study up on android sdk/fastboot/adb. a necessity to get out of these problems
you are not bricked, just need the info and right steps to get back on track
rugmankc said:
I don't know Mac commands
My idea is to install htc drivers and set up fastboot/adb on pc--the info can be found in dev section on rooting
then open a command window and and boot into fastboot and flash a new recovery, maybe stock per the link, clear storage and try to get mounted
how did you unlock bootloader--
you will need to do alot of reading on adb/fastboot and flashing roms--first step is to have backups of rom and sdcard
since i don't the Mac commands to do fastboot, someone else will chime in at some point
you can alos go to the noob section in Q&A and resubmit your issue
someone will work you thru this, but in meantime study up on android sdk/fastboot/adb. a necessity to get out of these problems
you are not bricked, just need the info and right steps to get back on track
Click to expand...
Click to collapse
im going to use someone elses alp top with windows. i'll ytry the all in one thing because thats how i rooted it in the first place. thanks for helping it means alot
good luck on it
Hey folks I'm looking for ideas to unbrick my OPO which is permanently stuck in a boot loop. It all began last Friday while flashing the lastest CM nightly and gapps. The flash executed successfully then entered a boot loop that refuses to be resolved. I've tried formatting and wiping all pertinent partitions including /persistent, fastboot flashing different version stock images, different radios... I don't know what else to try short of j-tag to rectify. Any and all advice appreciated. TIA
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Feb. 18th, 2016 Edit:
Well I'm happy to announce that after nearly 5 months of trying different tactics I was finally able to get my handset up and running this weekend.
The technique I used was to first flash the new official Oxygen OS following the directions from the oneplus forums. From there I was able to boot-up for the first time in months, but had no connectivity. I went to settings and saw I had no IMEI showing. Realizing this, I tried using the technique Heisenberg suggested below in this thread, but again I had no success.
Then I tried the instructions in this thread (which I had tried previously with no success) http://forum.xda-developers.com/oneplus-one/general/guide-efs-partitions-how-to-lost-t3307793 and viola! I got my radio back. It took me several attempts to get bluetooth and wifi back working, with rebooting in between, but alas I was able to get all fully functioning again.
Then I re-rooted and reinstalled TWRP (unofficial 3.0), backed up everything (including firmware and EFS partitions), then proceeded to flash the latest CM snapshot, then eventually the latest CM-12.1 unofficial CAF Sultanxda that I'm now happily running!!!
Thanks again to everyone who posted trying to help me get my handset working again. Now I have two fully functioning OPO's and am very happy!!!
Odysseus1962 said:
Hey folks I'm looking for ideas to unbrick my OPO which is permanently stuck in a boot loop. It all began last Friday while flashing the lastest CM nightly and gapps. The flash executed successfully then entered a boot loop that refuses to be resolved. I've tried formatting and wiping all pertinent partitions including /persistent, fastboot flashing different version stock images, different radios... I don't know what else to try short of j-tag to rectify. Any and all advice appreciated. TIA
Click to expand...
Click to collapse
You might have a corrupt persist partition. Download this:
https://drive.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/view?usp=docslist_api
Then:
Code:
fastboot erase persist
fastboot flash persist persist.img
Heisenberg said:
You might have a corrupt persist partition. Download this:
https://drive.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/view?usp=docslist_api
Then:
Code:
fastboot erase persist
fastboot flash persist persist.img
Click to expand...
Click to collapse
Thanks it's greatly appreciated. I had tried this earlier with a download from another link, but tried again with your persist.img and unfortunately, it too didn't work.
This scenario that I'm currently experiencing is eerily like a common problem we had with the HD2, where over time and use NAND cells would get "stuck" and go bad. If the bad cells were located in the portion of the NAND allocated for the /system partition an unresolvable boot loop would result. To work around this developers added tools to HD2 recoveries that would allow reordering and resizing partitions so the /system partition would wholly reside in a contiguous healthy part of the NAND.
I'm wondering now if the hundreds of times I've flashed my beloved OPO has taken its toll, and created a similar situation where bad NAND cells now reside within the boundaries of my /system partition?
Anyone familiar or aware of any tools I can use from either recovery or fastboot that would allow checking the integrity of the NAND to determine if this is indeed the cause of my current dilemma or rule it out?
Again, any help or suggestions would be greatly appreciated. TIA
Odysseus1962 said:
Thanks it's greatly appreciated. I had tried this earlier with a download from another link, but tried again with your persist.img and unfortunately, it too didn't work.
This scenario that I'm currently experiencing is eerily like a common problem we had with the HD2, where over time and use NAND cells would get "stuck" and go bad. If the bad cells were located in the portion of the NAND allocated for the /system partition an unresolvable boot loop would result. To work around this developers added tools to HD2 recoveries that would allow reordering and resizing partitions so the /system partition would wholly reside in a contiguous healthy part of the NAND.
I'm wondering now if the hundreds of times I've flashed my beloved OPO has taken its toll, and created a similar situation where bad NAND cells now reside within the boundaries of my /system partition?
Anyone familiar or aware of any tools I can use from either recovery or fastboot that would allow checking the integrity of the NAND to determine if this is indeed the cause of my current dilemma or rule it out?
Again, any help or suggestions would be greatly appreciated. TIA
Click to expand...
Click to collapse
If that is the case it's the first time I've heard of it happening on this device. TWRP may have a feature like that but I'm not sure. Other than that I'm unaware of any tools of this nature.
Heisenberg said:
If that is the case it's the first time I've heard of it happening on this device. TWRP may have a feature like that but I'm not sure. Other than that I'm unaware of any tools of this nature.
Click to expand...
Click to collapse
Thanks again for responding. I'm just at my wit's end with this and out of ideas, which is why I even suggested the hypothesis in my previous post. Fortunately, I have another OPO backup, so I still have a phone, but it too is problematic. Whenever the capacitive buttons are activated I experience phantom touches of the menu button, and usually at the most inopportune time. OPO customer service is nonexistent and have insisted since I received the defective device that my problems are firmware related and refuse to investigate further. Nearly a year later and numerous updates the problem is still unresolved, which is why I took the device out of service and made it my spare.
Now with my daily driver malfunctioning I'm nearly ready to throw in the towel and give up on Oneplus altogether and get another device from a more reputable manufacturer. They've sent me several OP2 invites, that I've declined using. My horrible customer service experience with them and now two faulty devices leads me to never want to purchase their products again, no matter how affordable or feature packed they may be.
Anyhow, as previously posted, if anyone has ideas to resolve my boot loop, please chime in. TIA
Is it possible that my boot looping is being caused by a corrupt iemi partition? If so, I never backed it up, but have the number readily available from the packaging my OPO shipped in. I also have my backup OPO that I'm currently using, is it possible to clone that partition?
Any ideas on how to recover or clone my from my other device would be greatly appreciated. Basically anything to help get my daily driver back up and running would be a heaven send. TIA
Odysseus1962 said:
Is it possible that my boot looping is being caused by a corrupt iemi partition? If so, I never backed it up, but have the number readily available from the packaging my OPO shipped in. I also have my backup OPO that I'm currently using, is it possible to clone that partition?
Any ideas on how to recover or clone my from my other device would be greatly appreciated. Basically anything to help get my daily driver back up and running would be a heaven send. TIA
Click to expand...
Click to collapse
A corrupt EFS partition doesn't cause this to happen, the phone will still boot but will have no network because it has no baseband and no IMEI.
Still trying to resovle. I refuse to give up!
I'm still looking for help in resolving this bootloop issue. I refuse to give up as long as there is the slightest hope of getting it back up and working.
Being a longtime Linux user I know that by default there must be some type of logs generated in the boot-up process. I'm thinking that perhaps if I can extract the log(s) and post them maybe someone can point me in the right direction towards resolving this issue. I've noticed that after flashing back the stock recovery there is a section which contains several logs. Which do I need, where do they reside, how can I extract them from my device, and how should I repost (them) here so they can be properly deciphered? TIA
Why don't you hard brick your phone and unbrick it by flashing ColorOS ? Not joking .. You can try that .. anyhow you're facing a soft brick ..
Tried flashing with twrp 2.8.6 build instead of 2.8.7?
Sanjiv Kumar said:
Why don't you hard brick your phone and unbrick it by flashing ColorOS ? Not joking .. You can try that .. anyhow you're facing a soft brick ..
Click to expand...
Click to collapse
I thought about this as a possible solution, but the "hard unbricking guide" only contains solutions to use with various versions of Windows. Unfortunately, I have no access to a Windows computer (at least one that someone would allow me to use for the purpose of unbricking). I run Linux on my laptop and desktop, specifically Gentoo Linux ~AMD64. I haven't run Windows on any of my machines for over a decade. For the extremely rare instances where I need to use a Windows application I run it on WINE in Linux.
If someone knows how to run the ColorOS unbricking procedure on Linux, I'd be happy to try it out.
NoobInToto said:
Tried flashing with twrp 2.8.6 build instead of 2.8.7?
Click to expand...
Click to collapse
This device was already running TWRP-2.8.6 prior to getting stuck in the bootloop. Since then I've tried every version above 2.8.4, I've tried Phil's, and CWM and both the CyanogenOS and CM recoveries. All with the same result.
Bumb to bring back up this thread, now that I've resolved my problems. Hopefully it will help someone else who may be having similar issues.
Hell! I meant to say HELLO ! But probably "hell" is context appropriate too!
I bought a BOOST specific Samsung SIII this week and rooted it. I used ODIN 3.04 and TWRP then Chainfire's SuperSU and PhilzTouch with SUCCESS.
(It's Jan 2017 by the way).
But afterwards, like when I was done installing all my usual post-root utilities, I was fooling around in TWRP and wiped the dalvik cache. I am now stuck in a bowl of BOOTLOOPS and all I can do is either boot to TWRP and flip to different utility screens in TWRP, or boot into DOWNLOAD MODE (fully functional: able to download from ODIN I mean), or power-up and BOOTLOOP with the Boost LOGO coming on before it reboots.
What have I done! Where can I get a stock image for this phone? So far I haven't found one anywhere on the net.
I have tried to use KIES 2, KIES 3 and Smartswitch to enter my model and IMEI (using the HEX # behind battery for IMEI).
I then bought ANOTHER SIII cheap. Rooted that one and used Smartswitch to back it up. I won't screw this one up but I don't believe I screwed the first one up either, just need stock. But the new phone is NOT OA3 (I had no way to know this when I ordered it from Amazon lol)
I would really appreciate --I mean tremendously appreciate--any one who had time for a couple back-and-forth messages to intervene and advise!
follow-up
I realise that wiping the dalvik cache may not have caused the issues I am having. When I was in TWRP mode I may have done something else--can't remember--I have neurological problems besides being a newbie. I just feel pretty sure that if I can ODIN an .iso tar of boost kitkat for this SPH-L710T all will be well but hell I know less than nothing and hate myself for not know what I did
vlaxonia said:
Hell! I meant to say HELLO ! But probably "hell" is context appropriate too!
I bought a BOOST specific Samsung SIII this week and rooted it. I used ODIN 3.04 and TWRP then Chainfire's SuperSU and PhilzTouch with SUCCESS.
(It's Jan 2017 by the way).
But afterwards, like when I was done installing all my usual post-root utilities, I was fooling around in TWRP and wiped the dalvik cache. I am now stuck in a bowl of BOOTLOOPS and all I can do is either boot to TWRP and flip to different utility screens in TWRP, or boot into DOWNLOAD MODE (fully functional: able to download from ODIN I mean), or power-up and BOOTLOOP with the Boost LOGO coming on before it reboots.
What have I done! Where can I get a stock image for this phone? So far I haven't found one anywhere on the net.
I have tried to use KIES 2, KIES 3 and Smartswitch to enter my model and IMEI (using the HEX # behind battery for IMEI).
I then bought ANOTHER SIII cheap. Rooted that one and used Smartswitch to back it up. I won't screw this one up but I don't believe I screwed the first one up either, just need stock. But the new phone is NOT OA3 (I had no way to know this when I ordered it from Amazon lol)
I would really appreciate --I mean tremendously appreciate--any one who had time for a couple back-and-forth messages to intervene and advise!
Click to expand...
Click to collapse
Greetings and welcome to assist. Have you tried kies/smartswitch emergency firmware recovery ? This should return your phone to stock. You could also use twrp to flash another rom from here
https://forum.xda-developers.com/galaxy-s3-sprint/development
Good Luck
Sawdoctor
Hey thanks for your reply
When I put Smartswitch on my computer, it couldn't identify the broken SIII (unknown device error).
(Smartswitch DID identify the other functional Boost SIII )
It's crazy that it boots all the way to the Boost logo screen then reboots. What is happening?
Is there any chance you can walk me through some steps--I am having trouble finding functional mirrors to things and I'm not sure if I should just give up--I don't give up easily but, being inexperienced in this realm, feel foolish in the event the bootloop is a permanent, irremediable error. Then anyone else comes here will see the original thread title and feel heartened.
I seem to need a stock image for OA3 L710T. I see loads for L710 but then the radio won't turn on, according to what I have gathered.
Hi everyone,
I'm a little in trouble and I'd need some help 'cause I'm getting an headache.
I temporary have to use a Galaxy S Duos 2, and given its really old OS I tried to flash it with something more recent. Problem is, there is something weird in the device preventing me to flash it.
In short, I'm stuck on two problems:
1) All the resources I've tried are either for the GT-S7580, kylepro, single SIM or for the GT-S7582, kyleprods, dual sim. Guess what? Mine is a GT-S7582, kylepro, dual sim. What the hell?
2) All the roms I've tried fail during the installation 'cause of an error on the sha1 of the system folder. I've tried everything, wiped the folders in the suggested order, restored the file system...nada.
So, any idea what's going on, and how to get out of this situation? I'd absolutely need to make the device work, but I'm clueless. I've even thought to reinstall the stock rom, but I've got no idea which version is the correct one for my device version.
Uh, just to add as much info as I can: I'm using Odin3 v3.12.10 and TWRP 3.2.1-0-kylepro
Help, please?
Well, exactly like last time I posted and asked for some help, I got totally ignored. Luckily, after a while yesterday I've done some thinking and I've found the possibile cause of the problem, tried and...yes, it worked; posting here in case someone else would ever find itself stuck on something similar in the future.
In short, the root of the problem is that for whatever reason the phone was thinking to be a kylepro instead of a kyleprods. I tried to correct the build.prop file, but there is no chance to do it from inside TWRP so I ended up tweaking the updater-script file. The procedure is explained on line in different sites, I cannot give a link as the forum system does not allow me to do it.
you can post the link with a minor mentioned edit, would be helpful for others who might face the same in future
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. :/