I wanted to solve this problem on my own but after almost 6 hours I just can't figure it out. Its either totally bricked or I'm just missing something simple. I've seen many people complain about this problem but none of them seem to have had the same problem I do. Thing is I was just really starting to love the way I had the phone set up. DAMN!
I used this thread to root: (CF)
http://forum.xda-developers.com/sprint-galaxy-s5/help/q-root-galaxy-s5-sport-sm-860p-t2859473
SPRINT GALAXY S5 SPORT SM-G860P
Android 4.4
I had CW recovery installed
(wish I had more info about the software)
Here's whats happening:
START
(vibrate)
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
(Also on Screen are the logos)
Samsung Galaxy S5 Sport
Powered by Android
This stays on for about 10 seconds.
Then blank screen (2 seconds)
(vibrate)
Screen still blank (2 seconds)
REPEAT (Auto reboot and goes back to start)
Other notes:
Trying to boot into recovery (home+vol up+power) Nothing Happens
Try to power off and nothing happens.
Pulled battery, did the 30 sec and restarted no change.
I have all updated usb drivers.
Odin will not see the device because its not on long enough. (Kies didn't see it either.)
Plug into PC via usb - Nothing Happens, device doesn't even show up because its not on long enough (win 8.1 and 7)
Pull battery to get it to stop, once battery goes back in, it auto starts again.
I TRIED AS MANY SD CARD / BATTERY/USB CABLE/POWER CABLE/BATTERY PULL/BUTTON COMBINATIONS AS I COULD FIND ONLINE AND THEN SOME. No Luck with anything.
I know this isn't a "help desk" I just wanted to give as much info as possible hoping to help you help me!
Please point me in the right direction.
Thanks!
Try to hard-reset your phone. There is a button combination for that., search it over the internet.
Thanks for the reply.
Unfortunately the hard reset combo does nothing. I've tried every button combination that I have been able to find with no luck. Factory reset, hard reset, etc. etc. no luck. I've also searched for a possible "hidden" button underneath the back cover or something of the like...nothing.
hmmmm
At least, it is not hard-bricked. So there is hope.
Have you checked if it is entering the download mode? If not, then try it. You can use this mode to flash file via the PC.
Check this link
It worked! Obviously I didn't search or try as many things as I thought I did. : / I can't thank you enough! wow. Amazing!
Thread closed.
Hello guys, im a total newbie with android/cyanogenmod/recovery etc. so sry for any dumb mistakes.
I have an old Samsung S2 Plus that a friend of mine installed cyanogenmod and some other stuff on some years ago for me.
I think it was Cyanogenmod 12.1 but im not completely sure.
My problem today is that when i boot the phone i get stuck on some bootscreen (the one with the blue cyanogenmod "alien"). Just nothing happens, had it blinking for 1 hour and more just to test it.
I tried getting into any of these recovery modes (searched online for some key combinations), tried a lot of combinations(volume up + power etc. but no recovery is showing up, just always the white samsung galaxy s2 text and the blue alien thingy afterwards. I think back then my friend installed cwrm recovery mode, but again not 100% sure.
Im thankful for every help and sry again for any dumb questions.
No mistake is a dumb mistake, unless youve already made that mistake several times and you repeat it, expecting the outcome to change. The more you mess something up and you fear youve messed up big time, the more you will figure out a way to fix it and gain knowledge.. embrace it..
On most Samsung phones, you have key combinations that are all the same.. very specific how you do it though..
Im going to use keys below, to simplify things a bit
[H] = home button, bottom center of screen
[P] = power button, usually top right edge
= volume up button
[D] = volume down button
If your phone is in boot loop* or not responding to power button, you will first have to completely restart all the system fresh.
* boot loop: an error that cause a device to start to load and at a certain point restarts, and repeats without ever getting past the point of restart
Two ways I know of to manually do it:
- You can take the battery out, and then press and hold power for 30 seconds. Then release power and insert battery.. leaving it in a dead state.. not powering it on, not charging, or even plugged into laptop..
OR
- Press and hold [D] + [P] *ONLY* for 45 secs or until the phone cuts off, careful to not accidentally restart
Once device is in that dead state, use key combos listed below:
..........☆ RECOVERY MODE ☆..........
press and hold
+ [H] + [P]
when the splash logo* appears,
release all of them
*splash logo: the first thing you see when powering on your device. Usually will say like samsung s2 and powered by android. You usually only see it for a few seconds
..........☆ DOWNLOAD OR ODIN MODE ☆..........
press and hold
[D] + [H] + [P]
when you see a blue screen,
quickly release them all.
then it will have instructions
typically to confirm into download mode,
or [D] to cancel and reboot
Straight Talk phones are known to have these taken out, so you cant free the phone from the grasps they have on it..
If those dont work, and your phone isnt straight talk or verizon, you can download these programs to windows OS pc, and they have buttons that will send a call to your device, and put them into download, fastboot, sideload, adb, or even recovery mode.. not all those modes are available on all samsung devices..
ME PERSONALLY, I HAD MOST LUCK WITH "D P TOOLS" AND "WINDROID"
ODIN IS A MUST HAVE IF YOUR GOING TO BE INSTALLING ROMS. ODIN WILL GET YOU BACK TO BONE STOCK FIRMWARE
Stock firmware can be found on multiple sites and here on XDA. Firmware is device specific and android version specific.
Heres a couple of the latest android versions
6.x.x = marshmallow
7.x.x = nougat
8.x.x = oreo
X/// STOCK FIRMWARE LINKS ///X
you would use the model number which can be found under the battery, and android version. since you may not know which one your running. I suggest google search for " your phone model + release date + release specs" that will get you in the ballpark
SAM MOBILE FIRMWARE
https://www.sammobile.com/
UPDATO
http://updato.com/firmware-archive-select-model
X/// ODIN INFO ///X
-- HERE IS A IN DEPTH ODIN TUTORIAL --
https://forum.xda-developers.com/note5/general/guide-odin-flashing-stock-firmwares-t3634256
Thanks to Gr3atGeek for this tutorial
X/// MOBILE TOOLS I MENTIONED ///X
run antivirus!!
-All in one flasher
CANNOT FIND
-D P tools
http://dp-tools.en.lo4d.com/
-Minimal ADB and fastboot
http://minimal-adb-and-fastboot.en.lo4d.com/
-Windroid
1 ) http://windroid-universal-android-toolkit.en.lo4d.com/
2 ) http://windroid-toolkit.en.lo4d.com/
-Android Ultimate
http://android-ultimate-toolbox-pro.en.lo4d.com/
**GENERAL TIPS AND TRICKS**
THESE IVE HAD THE MOST LUCK WITH. IM PRETTY SURE THIS IS THE ACTUAL URLS WHERE I DOWNLOADED ALSO.. NOW SOME WORK WITH THIS PHONE BUT NOT THAT PHONE. SOME WILL WORK WHEN ATTEMPTING TO PUT INTO RECOVERY MODE BUT WONT PUT INTO DOWNLOAD MODE.
**USE OF SOFTWARE HINTS AND SUGGESTIONS*
I HIGHLY SUGGEST NOT TO RUN MORE THAN ONE OF THESE PROGRAMS AT ONCE. SOME USE ADB.EXE AND IVE FOUND MULTIPLE ADB.EXE WILL CAUSE SILENT PROBLEMS.. IF YOUR UNSURE HOW MANY INSTANCES OF ADB.EXE ARE RUNNING, CLICK (CTRL) + (ALT) + (DEL) ALL AT ONCE. THEN CLICK TASK MANAGER. ONCE TASK MANAGER IS LOADED, CLICK THE PROCESSES TAB AND FIND ADB.EXE
** USB TRICKS AND SUGGESTIONS **
USE IF POSSIBLE YOUR ORIGINAL USB CABLE AND DONT USE ONE THAT HAS ANY HINT OF A PROBLEM, USUALLY THE THICKER THE WIRE THE FASTER AND SAFER IT IS.. OEM WORK THE BEST.. AND IF AT ALL POSSIBLE, MINIMIZE THE AMOUNT OF USB PORTS BEING USED TO PREFERABLY JUST THE CHARGER WIRE. SOMETIMES USB 2.0 AND USB 3.0 WILL EFFECT THINGS. DO NOT HAVE MORE THAN ONE PHONE CONNECTED AT A TIME.
GO INTO DEVICE MANAGER AND UPDATE USB DEVICE DRIVERS AND MAKE SURE SAMSUNG DRIVERS ARE UP TO DATE
Hope this has helped.. Sometimes the buttons on a phone will quit working but when you press it, it feels like it worked, made the sound and all.. thats when these programs come in handy.. im guessing you charged your phone until it came on, and when you were trying button combos, the phone was still on. It has to be off first. ADB and fastboot are powerful tools if you know some terminal knowledge, you can also start a shell and usually terminal will tell you if deamon* started successfully or not.. sorry about the mass confusion.. go run around XDA forums just searching and reading and now that youve heard me mention some of the lingo and terms used.. Google search everything.. the resources are there, and i just gave you a good bit of direction.. good luck
*daemon: to be brief, a word that symbolizes a connection between your device and another system
$$ IF IVE HELPED, OR YOU FEEL I MADE AN HONEST ATTEMPT TO HELP, HIT THE THUMBS UP, THATS THE BUTTON FOR "THANKS" HERE IN XDA
IM NOT RESPONSIBLE FOR ANY BROKEN, DAMAGED, OR MYSTERIES THAT HAPPEN TO YOUR DEVICE OR COMPUTER USING ANY INFORMATION OR TOOLS IN THE ABOVE TUTORIAL. BE SAFE
Hey everyone who reads this.
I'd like to start my topic with apologising if I post this in the wrong section.
So, I have a LG Spirit H440N LTE for about 3 years now, maybe a little less. I've always taken good care of it, both physically and in updates / security wise aswell.
My phone has been working flawlessly until the last 2 days. 2 days ago i was charging my phone, and when it vibrated (meaning its 100%) I pulled the cable off, and pressed the power button (power button locks - unlocks the screen) the screen didn't turn on. I was like "wow that's strange" but didn't care much, i just kept pressing the button every 5-6 seconds, nothing.
At that point I pulled the battery out, let it sit for a short time and then put it back, start the phone, I felt the vibration (meaning it's starting up) but no screen, so my first idea was that I need to get a new firmware and completely reinstall my phone, as it seems like it got bricked.. for no reason, by itself ? Strange thing but I accepted it and literally been googling for 9 hours now and I find more and more issues.
After I got LG FlashTool, drivers, and even 3 different firmwares, I wanted to start the phone in download mode to start upgrading, but even though I held down "volume up for 5 seconds and then put the usb cable in" nothing happened, no screen, my PC didn't recognise the phone either.
So I got a little bit mad and pulled the cable out from the phone, I wanted to remove the battery, but out of nowhere the phone suddenly started loading in, screen working completely fine, i could do whatever i want, so my first thing was to do a hard reset. After the hard reset I set up my usual stuff (important apps etc) and I locked the screen so my battery won't go down. Little did I know, I ****ed up again, because ever since that happened, I can't get my screen to work again. I tried everything I could but my PC still doesn't recognise the phone (even after a LOT of drivers being installed), charging the phone doesn't do anything. Regardless if I remove - put back the battery no screen, no screen in download - hard reset mode either, it's just completely black.
I'd like to have some sort of help, because I am just completely out of ideas, I really feel like a firmware change could fix the phone, but if the computer doesn't recognise it, I have no idea what to do.
rawon3 said:
Hey everyone who reads this.
I'd like to start my topic with apologising if I post this in the wrong section.
So, I have a LG Spirit H440N LTE for about 3 years now, maybe a little less. I've always taken good care of it, both physically and in updates / security wise aswell.
My phone has been working flawlessly until the last 2 days. 2 days ago i was charging my phone, and when it vibrated (meaning its 100%) I pulled the cable off, and pressed the power button (power button locks - unlocks the screen) the screen didn't turn on. I was like "wow that's strange" but didn't care much, i just kept pressing the button every 5-6 seconds, nothing.
At that point I pulled the battery out, let it sit for a short time and then put it back, start the phone, I felt the vibration (meaning it's starting up) but no screen, so my first idea was that I need to get a new firmware and completely reinstall my phone, as it seems like it got bricked.. for no reason, by itself ? Strange thing but I accepted it and literally been googling for 9 hours now and I find more and more issues.
After I got LG FlashTool, drivers, and even 3 different firmwares, I wanted to start the phone in download mode to start upgrading, but even though I held down "volume up for 5 seconds and then put the usb cable in" nothing happened, no screen, my PC didn't recognise the phone either.
So I got a little bit mad and pulled the cable out from the phone, I wanted to remove the battery, but out of nowhere the phone suddenly started loading in, screen working completely fine, i could do whatever i want, so my first thing was to do a hard reset. After the hard reset I set up my usual stuff (important apps etc) and I locked the screen so my battery won't go down. Little did I know, I ****ed up again, because ever since that happened, I can't get my screen to work again. I tried everything I could but my PC still doesn't recognise the phone (even after a LOT of drivers being installed), charging the phone doesn't do anything. Regardless if I remove - put back the battery no screen, no screen in download - hard reset mode either, it's just completely black.
I'd like to have some sort of help, because I am just completely out of ideas, I really feel like a firmware change could fix the phone, but if the computer doesn't recognise it, I have no idea what to do.
Click to expand...
Click to collapse
You might be having hardware issues, such as a faulty power button. If you are the type of user that frequently presses the power button to lock/unlock the screen, this leads to excessive wear on the button components, this is why some users prefer to use the "tap to sleep" and "tap to wake" feature, to avoid wearing the power button out. On my LG, this feature is called "KnockOn", it's located in Accessibility settings.
Sent from my LGL84VL using Tapatalk
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.