Database Info

[q] lg g2 at&t d800 bricked...

(LG G2 AT&T LG-D800) Im in a Major need of help i followed this guide http://forum.xda-developers.com/showthread.php?t=2451696 and did everything successfully until i booted it back up, and it stays on the Lg logo until the battery dies, or i turn it off holding the power button. It still boots into recovery mode but my recovery isn't very obedient because when i touch the screen, it doesn't react. only sometimes, so thats not usable. When i enter download mode, it has this little box saying "download mode" but it doesnt boot up to the firmware update screen. I could easily fix this problem. but the main problem ive encountered is that it won't connect to the pc correctly. it pops up saying "android adb interface" so i have the right drivers installed. but when i use adb shell or adb devices, its no where to be found. I tried to fix it using LG Mobile Support Tool, but when i click on "update recovery" in the top right corner, and type the IMEI it it works until it starts, then it pops up saying "the phone is disconnected to the pc" so the main problem is getting it to connect to the pc i could easily fix it then. Until then, i need someones' help. PLEASE HELP SMART PEOPLE. i gave as much detail as possible. i found a guy with the same problem but, he found a solution, i could do the same but, pc problems... link here http://forum.xda-developers.com/search.php?searchid=266218258

Did you flash the patched kernel after booting into recovery?
Sent from my LG-D800 using xda app-developers app

HTC DesIre 320 Bricked, no boot, only recovery...

Hello, I'm about to giving up,
Something happened to the phone and now it won't boot, it barely show the "ANDROID" logo when it restart itself. I can enter to the recovery menu, it doesn't have clockwork recovery nor twrp, just the basic recovery. So far I tried:
wipe data/factory - didn't work.
wipe cache partition - didn't work
apply update from adb: Adb just work with sideload and that's it, for everything else it shows closed. I tried sending the rom with sideload and it fails every time:
* failed to write data 'protocol fault (couldn't read status): Invalid argument' *
So I took my sdcard and copied the room there, so I tried
apply update from sdcard, it starts and in no time it says:
Installation aborted (APPLY_EXT).
I'm very frustrated right now, nothing works, it seems that the manufacturer did great effort on being the only one who can recover this phone, who appears to be from China, the MTK6582.
Fastboot? it doesn't show the device, it would be my last hope but no, since there is no adb, I cannot call fastboot, and the apply update from adb only work with sideload (yeah, f**k me).
The best course of action would be to throw it to the trash?
Thanks!

Hey, I'm in a similar position to you. However, I went about it with a slightly different route. The chip used in this phone is the MediaTek 6582 (I think?). I downloaded some tools from a thread on here that includes the 320 rom and the necessary software for flashing. I've flashed MediaTek devices before, the Huawei Ascend G610 and G700, both successfully. This one is giving me headaches, the damn device keeps disconnecting. HOWEVER, if you're lucky and you don't have the same problem with disconnecting hardware, you should be able to flash a new rom via the software. It'll take a while though. Also, I don't know what'll happen to your IMEI afterwards, so that's another possible headache (both the G610 and the G700 lost their IMEI info, but I'd taken steps to back them up beforehand so I could just restore them; here, there's no option to backup).
Here's the thread: http://forum.xda-developers.com/android/general/htc-mtk-cpu-flash-files-flashtool-t3114271
Let me know if you need help. I'm screwed in that the damn phone keeps disconnecting. Similar to you, no fastboot either. Plus, no RUU for this HTC. Hell, the internet barely knows this flipping phone.
Cheers, and good luck.
blitz9826
0Camus0 said:
Hello, I'm about to giving up,
Something happened to the phone and now it won't boot, it barely show the "ANDROID" logo when it restart itself. I can enter to the recovery menu, it doesn't have clockwork recovery nor twrp, just the basic recovery. So far I tried:
wipe data/factory - didn't work.
wipe cache partition - didn't work
apply update from adb: Adb just work with sideload and that's it, for everything else it shows closed. I tried sending the rom with sideload and it fails every time:
* failed to write data 'protocol fault (couldn't read status): Invalid argument' *
So I took my sdcard and copied the room there, so I tried
apply update from sdcard, it starts and in no time it says:
Installation aborted (APPLY_EXT).
I'm very frustrated right now, nothing works, it seems that the manufacturer did great effort on being the only one who can recover this phone, who appears to be from China, the MTK6582.
Fastboot? it doesn't show the device, it would be my last hope but no, since there is no adb, I cannot call fastboot, and the apply update from adb only work with sideload (yeah, f**k me).
The best course of action would be to throw it to the trash?
Thanks!
Click to expand...
Click to collapse

Ditto!!!
Hey guys I am having the exact same issue, luckily for me it is my Mrs who done her phone in and not mine . She has the HTC Desire 320, I believe she tried to root it on her own without even asking for advice, I think she used the app Kingo Root, she said she went to remove the root but when she uninstalled the app it didn't remove it. (LOL I told her well perhaps that's because there will be some way of removing it, aside from just uninstalling the app), anyway she proceeded not to care and carried on using her phone as normal for maybe a week or two at most, then about midnight one night, came down and said to me,
"my phone had an update and on restarting I just get a dead android, if you press the power button you get some options so I clicked erase"
Click to expand...
Click to collapse
I was like nice so basically you F***ed it!!!!, and for about 2 weeks now I have been endlessly reading post after post, forum after forum, trying rom after rom, RUU, all kinds of things.
Here is the situation, the phone will boot as far as the HTC logo, it will get stuck in a short loop and reset itself 4/5 times repeating the HTC logo, eventually it will end up at the dead android pic (the android on his back with the red exclaimation mark triangle) with the words 'no command'. From here I can press the power button once to get a list/menu of items (What I assume to be the recovery menu). I can backup data, I can restore the backed up data (both of which do nothing as I guess there is nothing really to back up), There is an option to restore from sd card (which I have tried numerous roms and to no avail have any been successful), I can erase the cache and I can also erase everything and recover, the erase side works fine, I did notice in each of these menu that if you press volume up to activate them and then press the power button once, then the writing dissapears and the android proceeds to have his moving atom type thing in his belly, saying 'erasing..', however even with them completed successfully, it still does not restore.
NOTE!!! If you choose the erase and restore method, once activated with volume up, press the power button to get the spinning atom and erasing... message, when this finishes the phone will reboot, it goes to the htc logo, resets itself, goes to the logo again and then just stays at a black screen (almost like a frozen state, I left it for quite some time and it never changed).
I should also note, which I didn't to begin with, but no matter how long I hold the volume down and power button, there is no such hboot/fast boot menu at all, if you hold the volume down and power button even after it displays the htc logo, the phone just proceeds to endlessly reset and loop through the same process forever.
The only thing I can seem to access with little success, is the ADB CMD prompt through the Android SDK,
Code:
adb devices
will indeed return the device (a set of numbers with the word sideload beside it)
Code:
adb usb
Apart from the odd fluke, this has seemed to fail everytime with either an error about a protocol or an error stating 'closed'
Code:
adb sideload "ROM_FILENAME.ZIP OR .IMG
Occasionally this will throw the protocol error, but generally succeeds and displays the 100% most of the time, however the phone doesn't even try, it just almost instantaniously returns the error message :
Code:
[B][I]Installation Aborted (APPLY_ADB_SIDELOAD)[/I][/B]
NOTE!!! That the android lays on his back with this error, but it only says error below not no command.
I am pretty sure that I already came across a solution very similar to the one you posted above, and I just couldn't get it to recognise the phone, the only way the RUU would work, was by completely removing the battery and plugging in the usb, however without the battery in the phone, it just constantly beeps via usb, so I guess it turns on, then off, then on, then off, forever!!! So the RUU fails everytime, if I leave the battery in and try, the RUU program does nothing whatsoever! So I am at a complete loss with it now.
Cheers
GunnerJnr

Any luck with unbriking the HTC?

Maybe this is the solution, good luck.
Search: How to Unbrick every MTK China Phone ! Preloader / SP Flashtool Fix [HD] on Youtube
Responds please.

http://forum.xda-developers.com/showpost.php?p=64659997&postcount=16

I think that you no tell true because I tried this method with volume keys and nothing. Flash tool still show error. Its impossible to write android without battery. I think really put your phone to rubbish or sell as lcd+digitizer parts I think just we must waiting for new custom rom flashable via stock recovery. 320 is still new model and developers no moke any custom rom. So maybe only HTC service may help, only in HTC Factory peoples know how install android and bootloader on hard bricked device.

lg g4 spirit (H440N) Hutchison Three UK. Please help to flash stock rom.

Please can someone help me to flash the stock rom on my phone - LG spirit 4G (H440n) - Hutchison Three UK?
Reason: Cannot go into settings on phone.
Symptoms: "Unfortunately, settings has stopped"
The icon for "settings" in the application area has changed to "com.android.settings.Settings".
Background: The phone has been well cared for, not a scratch on it, and no dubious apps (that I am aware of) have been installed, and certainly no .apk's have been installed. It has worked for many months without issue. The settings issue seemingly came from nowhere.
The basic stuff that I have tried: Factory reset has been done on the phone. Still cannot access settings, not even in safe mode. I have general use of the phone but cannot change settings.
From then on: I have ran the lg support tool (the alternative - lg bridge, is not relevant to my phone), and ran upgrade recovery. It downloads the kdz which I have made a copy of (H440N10G_00.kdz). It finishes the download, starts the upgrade process, gets to 9%, switches my phone off completely, and prompts me to restart the process. It can't go any further than this using this method. I also have to battery pull to switch the phone back on. Holding the power button for 20 seconds doesn't achieve anything here at this point.
After reading, it seems that I should be able to flash the image using adb and/or fastboot. These are installed on my system, as are the android USB drivers found in the android SDK.
Where I am getting stuck: I can boot into fastboot mode no problem. On the pc "fastboot devices" shows the device no problem, but none of the fastboot commands do anything. They print on my phones screen, but they do nothing at all. The phone installed fine without issue in the device manager. I can also boot into download mode, but the issue in this mode is that it comes up with "boot certification verify" which stays on for a few seconds and then the phone switches off. I am watching the device manager during this, and it doesn't detect or show in the device manager. Consequently "adb devices" on the pc produces nothing, as the phone doesn't stay on long enough to detect.
On my LG G4 spirit (H440n), it's the down-button as plugging usb to get into fastboot, and it's the up-button on plugging usb to get to download mode. This doesn't need checking. I know what i'm doing at least this much. Also, any responses need not mention about changing settings on my phone. It cannot be done! Not even after a factory reset. Not even in safe mode after a factory reset. Accessing settings is the very issue, so any solutions given that involve changing settings will not work, because settings will absolutely not run in any thus-far tried scenario.
Where can I go next, and what can I try? I wish to avoid sending to lg because I need the phone. I have not tried to root this and have no intention of rooting it until my warranty is up.
If there is a solution to this, I aim to keep it tidy for the benefit of others, so I will not be posting this on any other forums, or making duplicate posts. I am asking here, because I believe this to be the best possible forum that could potentially help me (and others) resolve this issue.
I hope you guys can help, so thanks in advance, and if you can't, thanks for looking into it.
Mark

Another brick?

Hello.
I did something wrong while trying to flash TWRP on my pixel 2, I am now stuck at the bootloader, and I cannot boot System or Recovery. While at the bootloader screen, it says Device State : unlocked. If I try to get to download mode, it says "ERROR: Operation Denied". If I try to go into recovery, it says "ERROR: Slot Unbootable: Load Error". If I try "Start", I get the same error message.
Also, adb or fastboot don't seem to be able to "see" the pixel connected to the computer. I believe my cables are good since I was able to flash Magisk and reflash the whole system with them before bricking it.
Can anyone help?
Thanks!

stanelie said:
Hello.
I did something wrong while trying to flash TWRP on my pixel 2, I am now stuck at the bootloader, and I cannot boot System or Recovery. While at the bootloader screen, it says Device State : unlocked. If I try to get to download mode, it says "ERROR: Operation Denied". If I try to go into recovery, it says "ERROR: Slot Unbootable: Load Error". If I try "Start", I get the same error message.
Also, adb or fastboot don't seem to be able to "see" the pixel connected to the computer. I believe my cables are good since I was able to flash Magisk and reflash the whole system with them before bricking it.
Can anyone help?
Thanks!
Click to expand...
Click to collapse
happened to my walleye too , and managed to bring it back to life . check this thread for a possible solution. https://forum.xda-developers.com/pixel-2/help/december-factory-image-to-broken-t3875213

Thanks!
I missed that thread while researching this issue.
I will try these things when I get back from work next week.
Thanks again!

stanelie said:
Thanks!
I missed that thread while researching this issue.
I will try these things when I get back from work next week.
Thanks again!
Click to expand...
Click to collapse
Just as a reference for anyone else who needs the fix and can't be bothered opening another thread.
SOLUTION: At the menu where it is stuck and saying device fail etc, plug in your usb cable to the mobile, press and hold the POWER button for 10 seconds, it will now recognise your phone under fastboot.
Once that is cleared, it's pretty much straightforward flashing latest pixel 2 image via fastboot and problem solved.
sidenote: Issue came with anyone who tried to flash december security updates and above as of what I heard.

I will try that, thanks.

So, several things :
Holding down the power button had no effect other than restarting the boot menu, but Fastboot never became available.
Opening up the phone and disconnecting the battery and reconnecting it made Fastboot available again. This would be in line with other users that let the phone battery discharge completely before regaining fastboot access.
Sidenote : opening up this phone is not for the faint of heart. I managed to damage something on the motherboard doing so (probably a static electricity discharge), the screen ended up displaying gibberish. I was able to salvage my phone by replacing the motherboard. I had ordered a replacement motherboard when I thought all was lost with no fastboot, and I had it on hand. Expensive little sucker...

stanelie said:
Hello.
I did something wrong while trying to flash TWRP on my pixel 2, I am now stuck at the bootloader, and I cannot boot System or Recovery. While at the bootloader screen, it says Device State : unlocked. If I try to get to download mode, it says "ERROR: Operation Denied". If I try to go into recovery, it says "ERROR: Slot Unbootable: Load Error". If I try "Start", I get the same error message.
Also, adb or fastboot don't seem to be able to "see" the pixel connected to the computer. I believe my cables are good since I was able to flash Magisk and reflash the whole system with them before bricking it.
Can anyone help?
Thanks!
Click to expand...
Click to collapse
Same thing happened to me except I never even tried to root. Just pulled the phone out of my pocket, and the little Android dude was belly up. It's showing device locked - and although I had it in Dev. mode from weeks back (thought USB Debugging was enabled) it fails to respond to adb commands, boot-loader mode, etc.
...Looks like Google laid an egg with this one.

Pixel 2 - "ERROR: Slot Unbootable: Load Error"
If you get the above error you will find that you cannot boot into recovery and the phone stays in the bootloader screen each time you try to start the phone. If your bootloader is unlocked you might be able to recover your phone to flash a stock image and revive. My problem started when I tried to restore a nandroid backup after trying out Android Q beta 1. I got the error mentioned above.
Most of the people recommended that I get a replacement from Google support as they had tried everything but it didn't work. Well right here in XDA Pixel 2 forum there is a solution waiting to be used. I am reproducing it from the post titled
"December factory image seems to have broken fastboot enumeration"
Quote
A possible way to resurrect a bricked Pixel 2...
Hey guys, I have just been able to get mine alive. The device started to be recognized (USB/fastboot) after about 10 unsuccessful attempts to start the system: "Start", from bootloader.
So what exactly happened and what I did:
1. Bricked a Pixel 2.
2. It started into bootloader and showed the "slot unbootable" error.
3. The device was not recognized by any of my machines at all, lsusb did not show anything new in the system, and, respectively, fastboot did not see the device.
4. The default option in the bootloader is "Start" if I remember correctly. So I just pressed the power button and did not release it until I noticed a vibration. It were about 10 unsuccessful attempts of system loading before that vibration.
5. Right after that vibration I connected a generic (NONAME) USB-C <-> USB-A cable to both the device and my Linux machine, and fortunately the device was recognized by the system and fastboot was able to detect the device correctly. So I flashed the a factory image, and it went just fine.
Unquote
Let me confirm that this works. I kept the power button down while the phone was connected via USB to the PC for at least 5 mins. During several reboots suddenly I got a beep from the PC which indicated that ADB was working. I flashed a stock image and voila the pixel 2 is back in operation.
Hope this helps several other people who might have this problem.

ashokabs said:
If you get the above error you will find that you cannot boot into recovery and the phone stays in the bootloader screen each time you try to start the phone. If your bootloader is unlocked you might be able to recover your phone to flash a stock image and revive. My problem started when I tried to restore a nandroid backup after trying out Android Q beta 1. I got the error mentioned above.
Most of the people recommended that I get a replacement from Google support as they had tried everything but it didn't work. Well right here in XDA Pixel 2 forum there is a solution waiting to be used. I am reproducing it from the post titled
"December factory image seems to have broken fastboot enumeration"
Quote
A possible way to resurrect a bricked Pixel 2...
Hey guys, I have just been able to get mine alive. The device started to be recognized (USB/fastboot) after about 10 unsuccessful attempts to start the system: "Start", from bootloader.
So what exactly happened and what I did:
1. Bricked a Pixel 2.
2. It started into bootloader and showed the "slot unbootable" error.
3. The device was not recognized by any of my machines at all, lsusb did not show anything new in the system, and, respectively, fastboot did not see the device.
4. The default option in the bootloader is "Start" if I remember correctly. So I just pressed the power button and did not release it until I noticed a vibration. It were about 10 unsuccessful attempts of system loading before that vibration.
5. Right after that vibration I connected a generic (NONAME) USB-C <-> USB-A cable to both the device and my Linux machine, and fortunately the device was recognized by the system and fastboot was able to detect the device correctly. So I flashed the a factory image, and it went just fine.
Unquote
Let me confirm that this works. I kept the power button down while the phone was connected via USB to the PC for at least 5 mins. During several reboots suddenly I got a beep from the PC which indicated that ADB was working. I flashed a stock image and voila the pixel 2 is back in operation.
Hope this helps several other people who might have this problem.
Click to expand...
Click to collapse
I don't even know how to thank you. I almost had a heart attack watching my Pixel bricked. Thanks man!

Save my day! I just keep pressing power button and fastboot response finally!

Can this be done if the device is locked?

_Kalyan said:
I don't even know how to thank you. I almost had a heart attack watching my Pixel bricked. Thanks man!
Click to expand...
Click to collapse
Does ur bootloader locked or unlocked?
---------- Post added at 11:36 AM ---------- Previous post was at 11:36 AM ----------
ashokabs said:
If you get the above error you will find that you cannot boot into recovery and the phone stays in the bootloader screen each time you try to start the phone. If your bootloader is unlocked you might be able to recover your phone to flash a stock image and revive. My problem started when I tried to restore a nandroid backup after trying out Android Q beta 1. I got the error mentioned above.
Most of the people recommended that I get a replacement from Google support as they had tried everything but it didn't work. Well right here in XDA Pixel 2 forum there is a solution waiting to be used. I am reproducing it from the post titled
"December factory image seems to have broken fastboot enumeration"
Quote
A possible way to resurrect a bricked Pixel 2...
Hey guys, I have just been able to get mine alive. The device started to be recognized (USB/fastboot) after about 10 unsuccessful attempts to start the system: "Start", from bootloader.
So what exactly happened and what I did:
1. Bricked a Pixel 2.
2. It started into bootloader and showed the "slot unbootable" error.
3. The device was not recognized by any of my machines at all, lsusb did not show anything new in the system, and, respectively, fastboot did not see the device.
4. The default option in the bootloader is "Start" if I remember correctly. So I just pressed the power button and did not release it until I noticed a vibration. It were about 10 unsuccessful attempts of system loading before that vibration.
5. Right after that vibration I connected a generic (NONAME) USB-C <-> USB-A cable to both the device and my Linux machine, and fortunately the device was recognized by the system and fastboot was able to detect the device correctly. So I flashed the a factory image, and it went just fine.
Unquote
Let me confirm that this works. I kept the power button down while the phone was connected via USB to the PC for at least 5 mins. During several reboots suddenly I got a beep from the PC which indicated that ADB was working. I flashed a stock image and voila the pixel 2 is back in operation.
Hope this helps several other people who might have this problem.
Click to expand...
Click to collapse
Works on bootloader state locked or not?

SoKa1993 said:
Does ur bootloader locked or unlocked?
---------- Post added at 11:36 AM ---------- Previous post was at 11:36 AM ----------
Works on bootloader state locked or not?
Click to expand...
Click to collapse
If the boot loader is locked look for a script for unlocking the bootloader from recovery or bootloader state. I did find it but cannot remember. My bootloader was unlocked so I did not have to use it.

ashokabs said:
Pixel 2 - "ERROR: Slot Unbootable: Load Error"
If you get the above error you will find that you cannot boot into recovery and the phone stays in the bootloader screen each time you try to start the phone. If your bootloader is unlocked you might be able to recover your phone to flash a stock image and revive. My problem started when I tried to restore a nandroid backup after trying out Android Q beta 1. I got the error mentioned above.
Most of the people recommended that I get a replacement from Google support as they had tried everything but it didn't work. Well right here in XDA Pixel 2 forum there is a solution waiting to be used. I am reproducing it from the post titled
"December factory image seems to have broken fastboot enumeration"
Quote
A possible way to resurrect a bricked Pixel 2...
Hey guys, I have just been able to get mine alive. The device started to be recognized (USB/fastboot) after about 10 unsuccessful attempts to start the system: "Start", from bootloader.
So what exactly happened and what I did:
1. Bricked a Pixel 2.
2. It started into bootloader and showed the "slot unbootable" error.
3. The device was not recognized by any of my machines at all, lsusb did not show anything new in the system, and, respectively, fastboot did not see the device.
4. The default option in the bootloader is "Start" if I remember correctly. So I just pressed the power button and did not release it until I noticed a vibration. It were about 10 unsuccessful attempts of system loading before that vibration.
5. Right after that vibration I connected a generic (NONAME) USB-C <-> USB-A cable to both the device and my Linux machine, and fortunately the device was recognized by the system and fastboot was able to detect the device correctly. So I flashed the a factory image, and it went just fine.
Unquote
Let me confirm that this works. I kept the power button down while the phone was connected via USB to the PC for at least 5 mins. During several reboots suddenly I got a beep from the PC which indicated that ADB was working. I flashed a stock image and voila the pixel 2 is back in operation.
Hope this helps several other people who might have this problem.
Click to expand...
Click to collapse
I have same problem. I use Pixel 2 and Fedora. My question is, what i exactly should do? I mean the steps. I didn't get that beep from my laptop. But I got the vibration when I hold the power button when it's not connected to USB. Please Help me.
Sorry my english isn't that good.

Did I just brick my device?

Hey guys!
So basically I will start from the top:
1. Device is Samsung Galaxy Note 10 Lite (SM-N770F) (F/DS if it matters really)
What happened is:
I've wanted to install Android 11 update on my phone - downloaded SamFirm app, searched for correct firmware for my region (I've made sure to select appropriate device and region).
Then I've downloaded Odin (3.14.1), loaded all files correctly - no errors or anything, started the process in Odin and after some time I got an error on the phone - Custom Binary(SUPER) Blocked By OEM Lock.
Now what happens is that I can't do literally anything with my device - it's turned on constantly on the same screen, on the top I can see the above error in red font, while on the center of the screen there is message "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software." - which I of course did, but Smart Switch doesn't even see the device or anything.
I can't turn off the device - while I press power and volume down button, it just goes black for a moment and comes right back up on the same screen no matter what.
Although, I think it's in downloading mode - Odin still sees it correctly (when I plug it in or out I can see changes in Odins screen).
Tried downloading older versions through SamFirm, other versions of Odin, other USB in computer, other cable - no luck at all.
Did I fully bricked the device? Or is it just soft bricked? Is there anything I can do now? Can Samsung center help me? I've tried chatting with them but they just sent me to their facility.
I'd do literally anything to fix this. Please help me, I'm desperate.

If you can get into recovery, i would try factory reset there. Then go to downloadmode and try complete new flash of newest version with csc (not home_csc). But im not sure, wether it is possible to flash with odin if bootloader is not unlocked in this new samsungs. I allways used odin with unlocked bootloader.

can't get into recovery - only thing I see is the above mentioned screen and there is 0 possibility of going anywhere else

priamusx said:
Hey guys!
So basically I will start from the top:
1. Device is Samsung Galaxy Note 10 Lite (SM-N770F) (F/DS if it matters really)
What happened is:
I've wanted to install Android 11 update on my phone - downloaded SamFirm app, searched for correct firmware for my region (I've made sure to select appropriate device and region).
Then I've downloaded Odin (3.14.1), loaded all files correctly - no errors or anything, started the process in Odin and after some time I got an error on the phone - Custom Binary(SUPER) Blocked By OEM Lock.
Now what happens is that I can't do literally anything with my device - it's turned on constantly on the same screen, on the top I can see the above error in red font, while on the center of the screen there is message "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software." - which I of course did, but Smart Switch doesn't even see the device or anything.
I can't turn off the device - while I press power and volume down button, it just goes black for a moment and comes right back up on the same screen no matter what.
Although, I think it's in downloading mode - Odin still sees it correctly (when I plug it in or out I can see changes in Odins screen).
Tried downloading older versions through SamFirm, other versions of Odin, other USB in computer, other cable - no luck at all.
Did I fully bricked the device? Or is it just soft bricked? Is there anything I can do now? Can Samsung center help me? I've tried chatting with them but they just sent me to their facility.
I'd do literally anything to fix this. Please help me, I'm desperate.
Click to expand...
Click to collapse
I experienced similar situation, but in my case, even my phone stuck in download mode screen, ODIN did not detect my phone, even PC wasn't response when plug in USB cable. As same as you say, when I tried to power off, it was power on itself and "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software" message appear on screen.
Then I tried to enter download mode again in download mode screen, by pressing power off, and after screen go black press immediately volume up+down. After that phone enter the download mode screen (again), it was looks like the same, but this time I was able to install firmware. Actually I really dont understand why this method work but you can give a try.

Unfortunately, still no luck.
But I've thought about other thing. Do you think it's possible to use .PIT file and re-partition option in Odin?
From what I've read everywhere this will wipe all partition data (so basically it should wipe every single thing) from the device, so it should be possible to overcome this oem lock, shouldn't it? Or will I just brick the device even further? I'm kinda desperate here as the phone is about 2-3 months so it's as brand new...
Edit: I think I've found another issue here. My device model is SM-N770F/DS so it's a Dual Sim model, while everywhere I only see firmware for SM-N770F so without dual sim. May it cause problems as well? How about the above option with flashin firmware with pit file and wiping partitions?

If you have figured it out by now good for you. If not, that emergency screen you see is nothing to fear. You can flash firmware with Odin from that screen...no worries your not bricked. Just do as you would if the device were in download mode..flash away.

Was your bootloader unlocked?