Database Info

[Q] Nexus S i9020A Bricked due to failing power button - Odin seems the last hope?

Hi everyone,
INTRO:
So the power button on my Nexus S broke. No big deal, I remapped it to the search button and used the volume rocker to wake the device; an option that was embedded in Cyanogenmod9.
Then I upgraded to CM10... since I did that on top of CM9, my volume rocker option was still enabled, but the option is no longer in CM10's GUI.
I had some annoying issue and thought maybe I should wipe my phone; which I did.
Sadly, I realized that my "wake using volume rocker" option was no longer enabled, and there is no GUI to turn it back on.
I then found a .zip package that was supposed to enable the option but, I guess I went too fast, now my phone is stuck on a bootloop.
THE PROBLEM:
Since my power button is broken, I cannot navigate in the fastboot menu to recovery and fix the ROM.
Worst, since the power button is somehow shorted (i.e.: it powers on automatically when I insert the battery) Fastboot is not working properly and my PC never sees my phone, so you can forget about fastboot boot recovery.img
So: boot loop, power button broke, no recovery, no fastboot. =(
I searched quite a bit and found out you could get the Nexus S in download mode and get it to work with ODIN using a USB JIG.
I made myself such a JIG and successfully put the phone in some kind of download mode where my PC sees it, fastboot devices yields nothing *but* ODIN sees the phone!
So a glimmer of hope except for the fact that finding the .tar files for the Nexus S seems impossible...
Thoughts? Suggestion? TIA!
Francis // XC3N

Oh BTW:
-Yes I saw the other posts, but none of them mention the odin files
-Yes, I know fastboot is better; but it's not working and:
-No, I can't see the device on 3 different PCs using 3 different OSes and 3 Different cables when in fastboot mode
I mean by that last line that *nothing* shows in device manager in Win7 or XP and *nothing* shows in lsusb on ubuntu
So unless someone has an idea it looks like Download mode is the only way my PC sees my phone...

My power button done the same thing, I googled around and found a solution that worked for me.
It's somewhere here on xda but I don't got the link, basically everytime I booted into the bootloader I couldn't move the cursor with the volume button because the phone thought I was holding the power button, so I carefully tapped the casing around the power button and rebooted the bootloader and eventually I had control, it took 5-6 attempts to get it going but it did fix the power button for me.
I think it's something to do with the micro switches giving out after a certain number of uses.
Also it started screwing about recently so I just blew into the casing through the power button and it's behaved ever since.
In short, tap it until it works, once you have control of fastboot plug the usb in and your pc should detect it
Hope this helps, Good Luck
Sent from my U20i using xda app-developers app

Muckyfox said:
My power button done the same thing, I googled around and found a solution that worked for me.
It's somewhere here on xda but I don't got the link, basically everytime I booted into the bootloader I couldn't move the cursor with the volume button because the phone thought I was holding the power button, so I carefully tapped the casing around the power button and rebooted the bootloader and eventually I had control, it took 5-6 attempts to get it going but it did fix the power button for me.
Also it started screwing about recently so I just blew into the casing through the power button and it's behaved ever since.
Click to expand...
Click to collapse
Hey MuckyFox thanks for your reply!
Unfortunately, that would've worked back when the power button was flimsy and still working once in a while... I did try the tapping thing but really nothing works... the button seems entirely dead and shorted. I guess at this point I might've to bring it in for repair... if the power button isn't broken then I'll be able to easily fix everything in recovery or fastboot. Sucks because I feel like I'm so close to getting it to work without spending money XD I just can't find the files for odin even though they really do seem to exist.

Allright so I found some odin files which were said to work with the i9020a
I flashed them... at some point it said "RESET!" and then odin no longer saw the device. The device is now not booting at all. FML

So this thread is going to end up like every other similar thread: I went and bought a Galaxy Nexus ;P
For posterity, these are the files you shouldn't flash on i9020A:
BOOTLOADER : Bootloader_I9020XXJK1.tar
PDA : PDA_SOJU_GRH78_85442_SIGNED.tar
PHONE:
CSC : CSC_I9020_EUR.tar

My power button started failing over the last couple of days. First when I would set the phone to standby it would ask me if I wanted to switch off the device, then later on it wouldnt respond at all.
Really weird solution - boot into recovery, factory restore, clear dalvik cache, voila, works good as new! (aside from losing all my settings)
Note, I barely managed to get into recovery. The power button fully stopped working halfway through and I had to take the battery out and try it a couple of times.
Oddly, even during this uber-broken phase, the power button would always switch on the device when fully switched off (not just standby) indicating to me that it wasnt just a physical broken connection.

I've mentioned this before, but a full casing for the phone with all the buttons is around $10 on eBay
Sent from my Nexus S using xda app-developers app

XC3N said:
So this thread is going to end up like every other similar thread: I went and bought a Galaxy Nexus ;P
For posterity, these are the files you shouldn't flash on i9020A:
BOOTLOADER : Bootloader_I9020XXJK1.tar
PDA : PDA_SOJU_GRH78_85442_SIGNED.tar
PHONE:
CSC : CSC_I9020_EUR.tar
Click to expand...
Click to collapse
You need stuff for SOJUA, and just the fact CSC has EUR meaning Europe in it would scare the crap out of me. Possible you just flashed stuff meant for i9020T and not i9020A.

In case anybody comes back here, I'm just gonna drop this in.

[Q] Root Without Power button....

Hi everyone,
I've got a big issue, my nexus S is not rooted and bootloader is still lock. As I said, my power button is broken....I've tryed to install driver from the nexus toolkit(and many others...), it worked but my nexus is reconized as "Acer ADB"...After that, I did "adb reboot bootloader" the nexus get into fastboot, but the computer cannot see it at all..not even in devices manager. When i'm on fastboot, nothing works, volume button and power are not responding(volume normaly work when booting OS).
Please help me !

Anyone?

lamenaceQC said:
Hi everyone,
I've got a big issue, my nexus S is not rooted and bootloader is still lock. As I said, my power button is broken....I've tryed to install driver from the nexus toolkit(and many others...), it worked but my nexus is reconized as "Acer ADB"...After that, I did "adb reboot bootloader" the nexus get into fastboot, but the computer cannot see it at all..not even in devices manager. When i'm on fastboot, nothing works, volume button and power are not responding(volume normaly work when booting OS).
Please help me !
Click to expand...
Click to collapse
Unless you have Gingerbread, you cannot root without your power button.
You can't scroll in fastboot and it doesn't get recognized because the power key is "stuck" on. It's a known issue when the power button fails on the Nexus S. Some people had moderate luck blasting compressed air around the power button, other opening it up and cleaning it with alcohol.

Thanks for answering.. I'll probably try to clean the button, i asked someone who repair Android phone and he told me that there was no fix for this button issue -_- that sound weird...

lamenaceQC said:
Thanks for answering.. I'll probably try to clean the button, i asked someone who repair Android phone and he told me that there was no fix for this button issue -_- that sound weird...
Click to expand...
Click to collapse
There's no easy fix though, it's true. I don't think anyone sourced the power button switch so as to order a few of them and beside it's a SMD component, quite tiny for some inexperienced (and even experienced) people.
If I was certain it was a power switch physical issue, I could likely source the part somewhere or exchange for similar and offer to repair people Nexus S, but my phone is fine and I surely won't take someone else phone to test.

[Q] HTC One S bricked-ish

Hi,
long story short: while trying to install CM on my old one s I first flashed the boot.img as described here: h t t p : / / wiki.cyanogenmod.org/w/Install_CM_for_ville. It appears that the firmware overwrote the custom recovery on a reboot, and when I entered recovery to install CM I got a screen saying "entering recovery..." in pink at the top, htc logo in the middle, and "This build is only intended for development, to not leak from HTC" (something like that) in red at the bottom. Nothing happened.
I shut it down and started it back up, and it went to boot with the same htc logo and red message at the bottom -- and froze there. Only 10+ sec power button restarts it, nothing else helps. Weird enough I noticed that if it's on a cable it won't restart but just stay off, and if it's not connected it will restart immediately, no chance to switch it off.
Here's my biggest problem: my volume rocker is brocken. Up works somewhat, but down is 95% dead. I entered the bootloader through adb before, but since I can't boot the phone anymore I can't get in anymore.
It seems to me like the best solution would be to somehow fix the volume rocker. It's not 100% dead, occasionally I could get a keypress through, so I would just suppose the contacts are a little bad and I could just polish it a little? But the phone seems a pain to take apart.
What would you suggest? Is it too easy to break the whole thing while trying to clean the contacts of the rocker?
Thanks for any help / comments!
compul

why not change the volume button, at gsm service.
It's a good phone.

compul said:
Hi,
long story short: while trying to install CM on my old one s I first flashed the boot.img as described here: h t t p : / / wiki.cyanogenmod.org/w/Install_CM_for_ville. It appears that the firmware overwrote the custom recovery on a reboot, and when I entered recovery to install CM I got a screen saying "entering recovery..." in pink at the top, htc logo in the middle, and "This build is only intended for development, to not leak from HTC" (something like that) in red at the bottom. Nothing happened.
I shut it down and started it back up, and it went to boot with the same htc logo and red message at the bottom -- and froze there. Only 10+ sec power button restarts it, nothing else helps. Weird enough I noticed that if it's on a cable it won't restart but just stay off, and if it's not connected it will restart immediately, no chance to switch it off.
Here's my biggest problem: my volume rocker is brocken. Up works somewhat, but down is 95% dead. I entered the bootloader through adb before, but since I can't boot the phone anymore I can't get in anymore.
It seems to me like the best solution would be to somehow fix the volume rocker. It's not 100% dead, occasionally I could get a keypress through, so I would just suppose the contacts are a little bad and I could just polish it a little? But the phone seems a pain to take apart.
What would you suggest? Is it too easy to break the whole thing while trying to clean the contacts of the rocker?
Thanks for any help / comments!
compul
Click to expand...
Click to collapse
Taking it apart is smth you can do. Ik its hard, i tried but if you're confident its your power button then do it. After you reveal the back of our phone, you can access the buttons
CM11 Powered G-Wonder

null0seven said:
why not change the volume button, at gsm service.
It's a good phone.
Click to expand...
Click to collapse
While that is my last resort, I'd like to avoid it. I do have a working Nexus 5 after all.
TiTAN-O-One said:
Taking it apart is smth you can do. Ik its hard, i tried but if you're confident its your power button then do it. After you reveal the back of our phone, you can access the buttons
CM11 Powered G-Wonder
Click to expand...
Click to collapse
It's the volume rocker, not the power button; and it's been broken for a long time. I'm a little afraid I might rip things apart, but this makes it look outright easy: youtube.com/watch?v=6j25jajIq3g. I'll give it a try.

Solving Power Button ISSUE

Hey guys,
So my brothers Nexus 5 came to an end but i'm determine to recover it (Already Partially Recover)
Backstory:
So initially the power button wasn't working like it couldn't be pressed, and as the device was already off i decided to plug a charger in and it would enter the boot stage but enter a boot loop which further research showed me it was a issue with the powerbutton, So i came to the conclusion to remove + replace the power button so i opened it up, took a look and soldered the broken power button off, with alot of time and effort i managed to remove it and clean it up with the intentions of installing a new powerbutton i bought a fine tip solder tip however it wasn't burning properly as i noticed eventually, in which i was unable to solder a new power button on even with flux, aswell as this i managed to solder it on in which i was convinced it was a decent soldering job as all the points were clearly connected i placed the board into the device (wHICH WAS A MISTAKE) as i should've waited a solid hour, to ensure it was strong, as of this the power button had come off as i was placing the board back in which meant the button was practically scrapped and i was extremely fustrated, so i decided to screw it a put the device back together without the back casings over the board, and i wanted to see if i could bridge the connection whilst the charger was plugged in in which i did and the device booted up.
Main Question:
Now my main question is, i need a workaround for the powerbutton currently i've installed Gravity Screen for him, however it's got a high battery consumption and it's not too reliable so i'm trying to get a solid method.
I've come across a headphone jack that has a button which i can configure to be a power button (Pressy or iKey)
Now that the issue with Locking + Unlocking is solved
How can i power the device back on when it shuts down due to lack of battery as i've sealed the phone back up, He currently runs Android 6.0 MRA58N, My main idea was to Root his Device + get TWRP installed however i was wondering if i could do this without rebooting his device / setting up a method to power his device via ADB however i haven't installed any ADBs etc so far.
My second idea was if i booted the device into fastboot by plugging in in the power cord and holding volume button, with the battery unplugged via the ribbon would it power on the device?
Last question is, i powered the device with the Camera Unplugged via ribbon cables however it's not working as the app just opens and closes without a FC so i was wondering if a reboot would just fix this?
ADDITIONALLY Another method could be rebooting via terminal However i'm unsure on how to use the Terminal / if i need root or not etc.
Thanks!

Contact a kernel dev. He will probably be able to remap the power button, to get it to boot from the charging screen. Or try to disable offline charging alltogether.

playitlouder said:
Contact a kernel dev. He will probably be able to remap the power button, to get it to boot from the charging screen. Or try to disable offline charging alltogether.
Click to expand...
Click to collapse
I'm quite new to the Nexus 5 Area, and infact i don't know any Kernal developers - Is there any chance you could probably help me out and give me some contacts etc.?

Hussain_Salam said:
I'm quite new to the Nexus 5 Area, and infact i don't know any Kernal developers - Is there any chance you could probably help me out and give me some contacts etc.?
Click to expand...
Click to collapse
I dont do much in terms of custom kernels, but post in some kernel threads in the nexus 5 development forums, or contact the creator of the thread via pm. Just look for threads with KERNEL in the name

UPDATE!
playitlouder said:
I dont do much in terms of custom kernels, but post in some kernel threads in the nexus 5 development forums, or contact the creator of the thread via pm. Just look for threads with KERNEL in the name
Click to expand...
Click to collapse
Okay Thank you,
UPDATE:
*I've Overcome the Powerbutton issue as i've ordered Pressy/iKey which should be arriving tomorrow which will lock and unlock my screen
*I'm now trying to figure out another method to power on my device if it shuts down:
One idea was to some how get the device to power on when i plug in a charger maybe by installing TWRP
Or another method was to power it on via an ADB shell on pc Or Something like that
*I'm also trying to reboot the Device however im unsure on how to do so without a power button.

Bootloader exception for SM-G930F

Hello,
Yesterday, while my phone was in idle, it turned off and rebooted on the classic red writing on black screen error.
I realize that there are many bootloader exception topics, but I searched and the only one topic I found was on a polish android forum, which I had to translate and that could not help me.
That because the exceptions may be many but I found that error only once.
The error is:
Code:
Bootloader exception
[RST_STAT = 0x1000000]
Exception: do_handler_sync: DABT_EL1(esr: 0x96000010)
pc: 0x8f0221b4 lr:0x8f022170 sp:0x8f10fe60
Phone is stuck in that screen until the battery dies.
I tried to get into download mode (to flash a new bootloader) but every combination doesn't work, it just turn off the screen and then after 30 seconds - 1 minute it reappears.
I read online that may be a mobo issue.
Is there any way to recover the phone, put it in download mode or at least recover the data there's inside?
Thanks for the support

Also having same issue
Have you managed to find a solution to this? I am having the same issue, and this is the only thread I can find which matches what my phone is doing.
Same as you, I haven't recently done anything to modify the firmware, I woke up this morning to find the exception text, and when rebooting via the Home + Power + Volume Down combination it jumps me straight to the same exception screen with no boot logo.
Hopefully there's some information around that can resolve this, but unfortunately I currently can't find it

Strongo said:
Have you managed to find a solution to this? I am having the same issue, and this is the only thread I can find which matches what my phone is doing.
Same as you, I haven't recently done anything to modify the firmware, I woke up this morning to find the exception text, and when rebooting via the Home + Power + Volume Down combination it jumps me straight to the same exception screen with no boot logo.
Hopefully there's some information around that can resolve this, but unfortunately I currently can't find it
Click to expand...
Click to collapse
No, unfortunately my phone is still stuck on that exception red text (not a single green one like the one i found online).
I bought a cheap USB Jig, trying to force the phone in the download mode but it doesn't work, my guess is that since the phone doesn't actually turn off, it can't "jump-start" on that mode (with the Jig).
Online I found that people just kept pressing the Vol Down + Power + Home and "eventually" (after 100+ tries) the download mode happens, but I doubt that's in my case.
The only solution I could find that could help me in the future is that 1. Phone is dead, eMMC and motherboard cannot start. 2. Since the phone could be (difficultly) tore down, the best bet is that you find a data recovery center (not Samsung since as I found out they don't do data recovery, but they simply change everything giving you a new phone basically or they change the motherboard, so deleting everything) or a data recovery specialist so that you could disassemble the phone, remove the memory, and read the content on a chip reader.
In this case maybe there's a chance to recover the simple data you have (photo, video, music, documents and something else that has a recognizable header) but probably everything else is lost.
I would be more than happy to be proven wrong since I'm not an expert but it's been 2 weeks and I received no answers.

Iztooi said:
Hello,
Yesterday, while my phone was in idle, it turned off and rebooted on the classic red writing on black screen error.
I realize that there are many bootloader exception topics, but I searched and the only one topic I found was on a polish android forum, which I had to translate and that could not help me.
That because the exceptions may be many but I found that error only once.
The error is:
Code:
Bootloader exception
[RST_STAT = 0x1000000]
Exception: do_handler_sync: DABT_EL1(esr: 0x96000010)
pc: 0x8f0221b4 lr:0x8f022170 sp:0x8f10fe60
Phone is stuck in that screen until the battery dies.
I tried to get into download mode (to flash a new bootloader) but every combination doesn't work, it just turn off the screen and then after 30 seconds - 1 minute it reappears.
I read online that may be a mobo issue.
Is there any way to recover the phone, put it in download mode or at least recover the data there's inside?
Thanks for the support
Click to expand...
Click to collapse
Morning.
The way out of this is to flash either the firmware that is on your phone or just the bootloader file (BL) from that firmware. Both options are done via Odin with your phone in download mode. So just to be clear, Download Mode is availble before the phone looks at the boot partition.
So, hold volumedown+home+power (press and hold the power button last in this sequence).
You may notice that your phone won't go into downlaod first time but it should not take more than 3/4 attempts. Do Not release the buttons until Downlaod Mode appears, no matter how many attempts it takes. Keep them pressed the whole time even when it's powering off and on, this is the part people do wrong.

cooltt said:
Morning.
The way out of this is to flash either the firmware that is on your phone or just the bootloader file (BL) from that firmware. Both options are done via Odin with your phone in download mode. So just to be clear, Download Mode is availble before the phone looks at the boot partition.
Click to expand...
Click to collapse
Hello,
The idea was to flash something on my phone to restore it, but download mode isn't available for me
So, hold volumedown+home+power (press and hold the power button last in this sequence).
You may notice that your phone won't go into downlaod first time but it should not take more than 3/4 attempts. Do Not release the buttons until Downlaod Mode appears, no matter how many attempts it takes.
Click to expand...
Click to collapse
That's it.
But even if I keep the combination pressed the phone doesn't enter in download mode. Usually (and I've seen a good amount of videos) if you keep volume down + home + power pressed, the phone boots up, then goes into the bootloader exception, then it reboots, then it goes into the exception and so on until it gets to download mode. That's not my case. I tried to keep them pressed for 10-15 minutes while it was showing the error and there was no more than one "attempt" (it doesn't restart more than one time per combination).
Keep them pressed the whole time even when it's powering off and on, this is the part people do wrong.
Click to expand...
Click to collapse
The fact is that it doesn't power off and on multiple times, but just one time.

Iztooi said:
Hello,
The idea was to flash something on my phone to restore it, but download mode isn't available for me
That's it.
But even if I keep the combination pressed the phone doesn't enter in download mode. Usually (and I've seen a good amount of videos) if you keep volume down + home + power pressed, the phone boots up, then goes into the bootloader exception, then it reboots, then it goes into the exception and so on until it gets to download mode. That's not my case. I tried to keep them pressed for 10-15 minutes while it was showing the error and there was no more than one "attempt" (it doesn't restart more than one time per combination).
The fact is that it doesn't power off and on multiple times, but just one time.
Click to expand...
Click to collapse
I'm this case you'll need to use ADB and side load to flash a new bootloader.

cooltt said:
I'm this case you'll need to use ADB and side load to flash a new bootloader.
Click to expand...
Click to collapse
But how can I use ADB and sideload if 1. the device doesn't go in recovery mode and 2. it's not even recognized with "adb devices" maybe because of the fact that it doesn't go on recovery mode?

Iztooi said:
But how can I use ADB and sideload if 1. the device doesn't go in recovery mode and 2. it's not even recognized with "adb devices" maybe because of the fact that it doesn't go on recovery mode?
Click to expand...
Click to collapse
Ok forget that one for now.
Try the following.
Boot phone so the error appears.
Then just press and hold the Home button only until the Android robot appears on screen.
Now press volume down+home+power and it should after a few seconds reboot into downlaod mode, if it does just repeat the process from the start.

cooltt said:
Ok forget that one for now.
Try the following.
Boot phone so the error appears.
Then just press and hold the Home button only until the Android robot appears on screen.
Now press volume down+home+power and it should after a few seconds reboot into downlaod mode, if it does just repeat the process from the start.
Click to expand...
Click to collapse
I'm guessing my phone is one of the older version. Pressing repeatedly the Home button or holding it should trigger the "forced upload by key pressing" with the android logo (as i've seen in videos and images), but mine doesn't.

Iztooi said:
I'm guessing my phone is one of the older version. Pressing repeatedly the Home button or holding it should trigger the "forced upload by key pressing" with the android logo (as i've seen in videos and images), but mine doesn't.
Click to expand...
Click to collapse
OK, the only sensible conclusion is that your phone has suffered some sort of hardware failure, its isn't unheard of. It'll likely cost you more to diagnose and repair than to buy a new S7 since their really cheap now.
It may be worth just looking to get your data recovered, which will be cheaper.
I'm not a fan of changing the mother board it's messy and the phone will never look perfect.
What country are you in?

cooltt said:
OK, the only sensible conclusion is that your phone has suffered some sort of hardware failure, its isn't unheard of. It'll likely cost you more to diagnose and repair than to buy a new S7 since their really cheap now.
It may be worth just looking to get your data recovered, which will be cheaper.
I'm not a fan of changing the mother board it's messy and the phone will never look perfect.
What country are you in?
Click to expand...
Click to collapse
Italy.
I honestly don't care about the phone, it has not sentimental value or something. Since I read here, on reddit, youtube and online that there were method like keeping pressed the combination, pressing the home button repeatedly or holding, using a jig, and others maybe someone knew what could I do to restore it. The weird thing was that I wasn't flashing anything nor using the phone, so the hardware failure option may be plausible.
The recovery of data (and I tried when I wrote my last post to re-use adb, maybe i was missing something but the phone is "recognized" by the computer but not with "adb devices") is the only solution I can think of, and there's the chip-off method that could at least recover the major data (photos, videos, documents). If there's anything else I'm all ears.

Iztooi said:
Italy.
I honestly don't care about the phone, it has not sentimental value or something. Since I read here, on reddit, youtube and online that there were method like keeping pressed the combination, pressing the home button repeatedly or holding, using a jig, and others maybe someone knew what could I do to restore it. The weird thing was that I wasn't flashing anything nor using the phone, so the hardware failure option may be plausible.
The recovery of data (and I tried when I wrote my last post to re-use adb, maybe i was missing something but the phone is "recognized" by the computer but not with "adb devices") is the only solution I can think of, and there's the chip-off method that could at least recover the major data (photos, videos, documents). If there's anything else I'm all ears.
Click to expand...
Click to collapse
I assume youre in upload mode. Press only power button for 20 seconds

kpwnApps said:
I assume youre in upload mode. Press only power button for 20 seconds
Click to expand...
Click to collapse
Pressing the power button for even a minute doesn't trigger anything. I assume that you're talking about the upload mode activated by holding the home button or pressing it repeatedly, showing the android logo and having adb recognize the device to then flash something or recover something. That is not my case, it doesn't happen to me unfortunately.

Iztooi said:
Pressing the power button for even a minute doesn't trigger anything. I assume that you're talking about the upload mode activated by holding the home button or pressing it repeatedly, showing the android logo and having adb recognize the device to then flash something or recover something. That is not my case, it doesn't happen to me unfortunately.
Click to expand...
Click to collapse
Buy an usb jig they still work for galaxy s7. It might get you out and they are 3-5$ so you got nothing to lose

Iztooi said:
I bought a cheap USB Jig, trying to force the phone in the download mode but it doesn't work, my guess is that since the phone doesn't actually turn off, it can't "jump-start" on that mode (with the Jig).
Online I found that people just kept pressing the Vol Down + Power + Home and "eventually" (after 100+ tries) the download mode happens, but I doubt that's in my case.
Click to expand...
Click to collapse
kpwnApps said:
Buy an usb jig they still work for galaxy s7. It might get you out and they are 3-5$ so you got nothing to lose
Click to expand...
Click to collapse
I already did that, but sadly it didn't work.

Iztooi said:
I already did that, but sadly it didn't work.
Click to expand...
Click to collapse
Then it might be an UFS hardware fault

kpwnApps said:
Then it might be an UFS hardware fault
Click to expand...
Click to collapse
I have the exact same problem. This is the closest thing I could find on the internet I could find regarding diagnosing it. Had to make an account just to reply. I was thinking it was a OS problem for the longest time, but I suspect that it may be a hardware problem after all. My s7 did this to me the morning of Jan 9. Set it down and came back to it, reboot with bootloader error, red text only, no combinations of buttons work etc. I see that two others in the thread had theirs fail around the same time as well.

Just wanted to update, not sure if anyone is still reading this thread. I plugged my s7 onto my old laptop (windows 7). My laptop recognized it and installed 2 drivers. They are:
"SAMSUNG Mobile USB CDC Composite Device"
"SAMSUNG Mobile USB Modem #2"
I've plugged into this old laptop before and transferred files around, so it doesn't seem to make sense to me why it would install these drivers now. It still doesn't show up in "My computer" at all. I believe normally it shows up in "My computer" as an empty folder when charging although I don't recall 100%. Hopefully this might help with diagnosing this problem.

draco18 said:
Just wanted to update, not sure if anyone is still reading this thread. I plugged my s7 onto my old laptop (windows 7). My laptop recognized it and installed 2 drivers. They are:
"SAMSUNG Mobile USB CDC Composite Device"
"SAMSUNG Mobile USB Modem #2"
I've plugged into this old laptop before and transferred files around, so it doesn't seem to make sense to me why it would install these drivers now. It still doesn't show up in "My computer" at all. I believe normally it shows up in "My computer" as an empty folder when charging although I don't recall 100%. Hopefully this might help with diagnosing this problem.
Click to expand...
Click to collapse
Probably it's because when it's in recovery mode, in download mode or this (bootloader) "error mode" it's recognized differently by the computer, to be recognized by ADB and Odin to flash roms and others. Instead when you plug it in when it's on, it's recognized to transfer data, and I believe when you swap MTP (for normal data transfer) and PTP (using the camera) you should also installing different drivers.
Anyway, I noticed too that the device is recognized differently than usual, and differently when rebooting it with the cable plugged in. (Also the name of the device is different when using the 300k tool, in fact my device is recognized as a "Modem")

Iztooi said:
Probably it's because when it's in recovery mode, in download mode or this (bootloader) "error mode" it's recognized differently by the computer, to be recognized by ADB and Odin to flash roms and others. Instead when you plug it in when it's on, it's recognized to transfer data, and I believe when you swap MTP (for normal data transfer) and PTP (using the camera) you should also installing different drivers.
Anyway, I noticed too that the device is recognized differently than usual, and differently when rebooting it with the cable plugged in. (Also the name of the device is different when using the 300k tool, in fact my device is recognized as a "Modem")
Click to expand...
Click to collapse
I was wondering if you installed any apps recently and how full your internal memory was. I believe my phone was around 90% full of the 32GB, had no warning symbol about how full my memory was though. Friend was saying I should of got a warning if my memory was getting near capacity. I installed F-droid recently and used it to download Adaway app. Deleted F-droid and deleted Adaway since I couldn't get Adaway to work. Never rooted my phone. I was curious if you also did anything similar to what my phone did since we're in the same boat. Otherwise the only things we share in common is we set it down and it reboot with this bootloader error.