Oneplus 3T bricked in OEM unlock? - OnePlus 3T Questions & Answers

Hello all
After 1 year I decided to root my Oneplus 3T, I've downloaded the adb files and the OP drivers.
I've plugged my OP3T and runned fastboot oem unlock, the phone started the unlocking process and after some minutes, PUFFF, it turned off. The battery was 95% when I started the rooting process. What happened?
I really don't know because them fastboot command is simple and it was not supposed turn the phone down, nor brick it.
Any help? I really don't know what to do! Thanks

Have you tried holding down the power button for more than 30s?

thes3usa said:
Have you tried holding down the power button for more than 30s?
Click to expand...
Click to collapse
Now I am a little ashamed for this thread. Thank you.
Anyway, for further knowledge, for some reason the cable was preventing the phone to turn on, I simply removed the cable and it went alive.

DoNotKnowRoot said:
Now I am a little ashamed for this thread. Thank you.
Anyway, for further knowledge, for some reason the cable was preventing the phone to turn on, I simply removed the cable and it went alive.
Click to expand...
Click to collapse
I would suggest you replacing the cable, it might cause a short circuit on the phone, which may be dangerous on a long-term usage.

Related

[Q] HTC One Switched off and Won't turn on

Hi all,
I have purchased a HTC One while in US a month ago from AT&T. I am now in India and the device worked perfectly fine until two weeks ago, it switched off automatically.
I tried a lot of combinations mentioned in the forums and also contacted the customer service (both in US and India) and they requested me to try holding the Power and both Volume buttons at the same time for 2 minutes. I did this for 10 minutes and it won't work.
When I connect the phone to Wall socket charger, the LED won't lit up. When connected to my laptop, the windows O/S makes the connected sound but nothing happens.
I really appreciate any help in this matter. Thanks in advance.
Kind regards,
Krishna Menon.
bkmenon said:
Hi all,
I have purchased a HTC One while in US a month ago from AT&T. I am now in India and the device worked perfectly fine until two weeks ago, it switched off automatically.
I tried a lot of combinations mentioned in the forums and also contacted the customer service (both in US and India) and they requested me to try holding the Power and both Volume buttons at the same time for 2 minutes. I did this for 10 minutes and it won't work.
When I connect the phone to Wall socket charger, the LED won't lit up. When connected to my laptop, the windows O/S makes the connected sound but nothing happens.
I really appreciate any help in this matter. Thanks in advance.
Kind regards,
Krishna Menon.
Click to expand...
Click to collapse
Press and hold the power+volume down buttons. Once the home and back button lights start flashing, keep the power+volume down buttons pressed and plug it into your pc.. It'll connect and install necessary drivers and your phone lights will stop flashing, and it will eventually boot up in hboot.
It may take a few tries
Ps: Always use the thanks button
Sent from my iPod touch using Tapatalk
n1234d said:
Press and hold the power+volume down buttons. Once the home and back button lights start flashing, keep the power+volume down buttons pressed and plug it into your pc.. It'll connect and install necessary drivers and your phone lights will stop flashing, and it will eventually boot up in hboot.
It may take a few tries
Ps: Always use the thanks button
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
Nothing happens when I press and hold the power+volume down buttons. I held it for 10 minutes. When I connect the phone to computer, it was detected as qhsusb_dload. When I searched about this issue on net, many posts say the phone is bricked and can't do anything about it.
Anyone help me how to unbrick my phone? Appreciate the help.
Thanks & regards,
Krishna Menon.
bkmenon said:
Nothing happens when I press and hold the power+volume down buttons. I held it for 10 minutes. When I connect the phone to computer, it was detected as qhsusb_dload. When I searched about this issue on net, many posts say the phone is bricked and can't do anything about it.
Anyone help me how to unbrick my phone? Appreciate the help.
Thanks & regards,
Krishna Menon.
Click to expand...
Click to collapse
Take a look at this: http://forum.xda-developers.com/showthread.php?t=2481211
nkk71 said:
Take a look at this: http://forum.xda-developers.com/showthread.php?t=2481211
Click to expand...
Click to collapse
Hi nkk71,
I tried this method without any success. When I contacted the HTC global support, the support person did mention this method. I tried holding the power + volume up + volume down buttons continuously for 15 minutes and nothing happened (my fingers hurt afterwards, #on a lighter note)
bkmenon said:
Hi nkk71,
I tried this method without any success. When I contacted the HTC global support, the support person did mention this method. I tried holding the power + volume up + volume down buttons continuously for 15 minutes and nothing happened (my fingers hurt afterwards, #on a lighter note)
Click to expand...
Click to collapse
Unfortunately "qhsusb" is usually a hard brick and needs a motherboard replacement
for one (or two?) people, the phone miraculously came back on for no apparent reason (if memory serves, for one guys it came back when the alarm rang the next morning), but other than that it's usually considered a hard brick, and needs hardware fix.
nkk71 said:
Unfortunately "qhsusb" is usually a hard brick and needs a motherboard replacement
for one (or two?) people, the phone miraculously came back on for no apparent reason (if memory serves, for one guys it came back when the alarm rang the next morning), but other than that it's usually considered a hard brick, and needs hardware fix.
Click to expand...
Click to collapse
Thanks nkk71 for this quick response. It's very unfortunate that my phone requires mother board replacement.
I loved the phone a lot. Now, I have to shell around 15K I believe.
bkmenon said:
Thanks nkk71 for this quick response. It's very unfortunate that my phone requires mother board replacement.
I loved the phone a lot. Now, I have to shell around 15K I believe.
Click to expand...
Click to collapse
No warranty? Sorry mate
you could leave it in the charger for a full day, and see if it comes back to life, and power it completely off while charging, not just the screen off.
nkk71 said:
No warranty? Sorry mate
you could leave it in the charger for a full day, and see if it comes back to life, and power it completely off while charging, not just the screen off.
Click to expand...
Click to collapse
I bought this from one of my US friends and now in India and I wasn't able to properly contact him. Lesson Learned for life. Not to purchase without proper documents.
I have put the phone charged for straight four days without removing in the wall socket. Nothing.
nkk71 said:
No warranty? Sorry mate
you could leave it in the charger for a full day, and see if it comes back to life, and power it completely off while charging, not just the screen off.
Click to expand...
Click to collapse
So I've been reading around, and came across QPST, and some guys have unbricked a hard brick using this tool. Is it possible to somehow make it work for the One?
n1234d said:
So I've been reading around, and came across QPST, and some guys have unbricked a hard brick using this tool. Is it possible to somehow make it work for the One?
Click to expand...
Click to collapse
Don't know what QPST is but i do remember there was a tool a while back for other phones to fix the Qualcom_HUSB mode, but I don't think it was ever updated for the One.
nkk71 said:
Don't know what QPST is but i do remember there was a tool a while back for other phones to fix the Qualcom_HUSB mode, but I don't think it was ever updated for the One.
Click to expand...
Click to collapse
Found these
http://forum.xda-developers.com/showthread.php?t=2208289
http://forum.xda-developers.com/showthread.php?p=31964712
http://forum.xda-developers.com/showthread.php?t=2136738
http://forum.xda-developers.com/showthread.php?t=2208289
n1234d said:
Found these
http://forum.xda-developers.com/showthread.php?t=2208289
http://forum.xda-developers.com/showthread.php?p=31964712
http://forum.xda-developers.com/showthread.php?t=2136738
http://forum.xda-developers.com/showthread.php?t=2208289
Click to expand...
Click to collapse
I'll take a closer look later, but if it was available/working for the HTC One, then i'm sure someone would have mentioned it by now.
n1234d said:
Found these
http://forum.xda-developers.com/showthread.php?t=2208289
http://forum.xda-developers.com/showthread.php?p=31964712
http://forum.xda-developers.com/showthread.php?t=2136738
http://forum.xda-developers.com/showthread.php?t=2208289
Click to expand...
Click to collapse
I followed the steps mentioned in one of the posts on QPST; but as my phone was not detected, the COM port was stated as Not Available in the QPST configuration s/w. Don't know what else to do.
I thought I would add to this thread an obvious step that sometimes gets forgotten.
I assume you attempted to charge your device in multiple sources: wall outlet, computer, etc.
I suggest you try some more, ideally varying cables and power adapters.
I experienced too many times - and even once with the one - the same exact brick you're describing and most of the times, the only solution was the above: find a combination to charge the device when its battery is completely depleted as in this situation they're more picky as to the source of power
Sent from my HTC One using Tapatalk

Switched to Dalvik from ART on Moto G 2014 and now phone will not power on.

Got a Moto G 2014 from WIND Mobile last week. Allowed updates to go through, finished at 4.4.4. Switched to ART assuming it would improve performance. It did not, and I had an issue where every time I boot up it would optimize every app. This made bootup take about 10 minutes. I decided to troubleshoot I would switch back to Dalvik. Began switch to Dalvik with 80% remaining battery. During the runtime switch, it booted up fine. I decided to power it off and then back on again and watch the bootup process as a test just to make sure everything was now fine.
Now, it doesn't respond when I try to power it on. No backlight, nothing on screen, no vibrate, nothing. Holding power and volume down does nothing. Holding power for 120 seconds (something I read online) does nothing.
I would appreciate any help I can get with this from anyone who has faced this issue.
Hold power and vol down to power up in bootloader mode and do a factory reset
danieliop said:
Hold power and vol down to power up in bootloader mode and do a factory reset
Click to expand...
Click to collapse
Holding power and volume down does not respond either. I've tried holding both down for as long as 120 seconds and no luck.
Oh, damn. Plugging the USB does something?
danieliop said:
Oh, damn. Plugging the USB does something?
Click to expand...
Click to collapse
Plugging into USB also has no response. It used to vibrate and display a battery status screen immediately after being plugged in. But now, I plug it in and nothing at all.
matt0401 said:
Plugging into USB also has no response. It used to vibrate and display a battery status screen immediately after being plugged in. But now, I plug it in and nothing at all.
Click to expand...
Click to collapse
That's really weird. Try to get it replaced, as it seems to be dead.
matt0401 said:
Plugging into USB also has no response. It used to vibrate and display a battery status screen immediately after being plugged in. But now, I plug it in and nothing at all.
Click to expand...
Click to collapse
Yeah that's my next step. Doesn't give me a lot of confidence in this phone. I think anyone planning on trying ART before the Android 5.0 update should beware. Make sure they've backed up their important data and are able to return their phone for replacement, because what triggered this bricking for me was switching back from ART to Dalvik. I made no changes to the bootloader, ROM, etc. This was completely stock.
Thanks for replying!
Re-Flash!
matt0401 said:
Got a Moto G 2014 from WIND Mobile last week. Allowed updates to go through, finished at 4.4.4. Switched to ART assuming it would improve performance. It did not, and I had an issue where every time I boot up it would optimize every app. This made bootup take about 10 minutes. I decided to troubleshoot I would switch back to Dalvik. Began switch to Dalvik with 80% remaining battery. During the runtime switch, it booted up fine. I decided to power it off and then back on again and watch the bootup process as a test just to make sure everything was now fine.
Now, it doesn't respond when I try to power it on. No backlight, nothing on screen, no vibrate, nothing. Holding power and volume down does nothing. Holding power for 120 seconds (something I read online) does nothing.
I would appreciate any help I can get with this from anyone who has faced this issue.
Click to expand...
Click to collapse
I believe you're gonna have to re-flash your device. Are you able to enter the boot loader? if yes, then re-flash the device with Stock firmware using ADB. Search the forums for instructions or reply and I'll post them myself. Do post your Device Model also.
KrishnaSagar said:
I believe you're gonna have to re-flash your device. Are you able to enter the boot loader? if yes, then re-flash the device with Stock firmware using ADB. Search the forums for instructions or reply and I'll post them myself. Do post your Device Model also.
Click to expand...
Click to collapse
It's actually already completely stock. I made no changes to it, besides enabling developer options and changing the runtime to ART (and then back to Dalvik). Model number is XT1064.
matt0401 said:
It's actually already completely stock. I made no changes to it.
Click to expand...
Click to collapse
I know, but since it ain't booting up, you have to re-flash the stock firmware.
KrishnaSagar said:
I know, but since it ain't booting up, you have to re-flash the stock firmware.
Click to expand...
Click to collapse
Sorry about the confusion, that does make sense. By accessing the boot loader, are you referring to the menu you reach when you hold power and volume down as you power on the phone? If not, what do you mean by accessing the boot loader?
Yep
matt0401 said:
Sorry about the confusion, that does make sense. By accessing the boot loader, are you referring to the menu you reach when you hold power and volume down as you power on the phone? If not, what do you mean by accessing the boot loader?
Click to expand...
Click to collapse
Yes. Thats the boot loader menu.
KrishnaSagar said:
Yes. Thats the boot loader menu.
Click to expand...
Click to collapse
Okay. So I have no access to that at all. Power and volume down doesn't do anything. Windows seems to recognize it somehow, I hear the device-plugged-in sound, but the device manager doesn't seem to show it listed. I'm guessing I don't have any options left for fixing this, so I'm going to bring it back and see if I can get it replaced on the spot or begin an RMA process.
Try this! All credit goes to Falcon G
matt0401 said:
Okay. So I have no access to that at all. Power and volume down doesn't do anything. Windows seems to recognize it somehow, I hear the device-plugged-in sound, but the device manager doesn't seem to show it listed. I'm guessing I don't have any options left for fixing this, so I'm going to bring it back and see if I can get it replaced on the spot or begin an RMA process.
Click to expand...
Click to collapse
This may just be your lucky day! Falcon G has posted a guide on how to unbrick Hard Bricked devices.
Follow this guide: http://forum.xda-developers.com/mot...rick-hard-bricked-moto-g-2nd-gen-5-0-t2966010
Cheerio!!
First connect your charger to phone and leave it for 2-3 hr may be your battery is dead. Same thing happen to a member of my whatsapp group now his phone is perfect
KrishnaSagar said:
This may just be your lucky day! Falcon G has posted a guide on how to unbrick Hard Bricked devices.
Follow this guide: http://forum.xda-developers.com/mot...rick-hard-bricked-moto-g-2nd-gen-5-0-t2966010
Cheerio!!
Click to expand...
Click to collapse
vikasb32 said:
First connect your charger to phone and leave it for 2-3 hr may be your battery is dead. Same thing happen to a member of my whatsapp group now his phone is perfect
Click to expand...
Click to collapse
For anyone interested in some followup, I went to WIND to see if it could be replaced. They refused to replace it, because there were a few scuff marks around the edge from when I dropped it the night I got it. I went home and called Motorola tech support to look into an RMA. They had me go through the troubleshooting steps. This involved me plugging it back into the charger (now it's been unplugged from my charger all day because I brought it with me for returning). Looks like leaving it unplugged for a while to let the battery discharge did the trick. This time, when I plugged it into the charger, the white LED came on, and I got the white screen with the battery indicator. It was fine.
Here's hoping I don't run into that again.

[Q] Unlocking bootloader hard bricked my moto x

So....
I think I hard bricked my 1st gen moto x. I was in the process of unlocking the bootloader using motorolla's guide and everything was going fine. i had the "unlock..." (or "unlocked..." i forget what it actually said) showing on my screen and just out of habit, i hit the power button as i put the phone down.
now, nothing.
nothing at all. no recovery mode, no nothing. does anyone have any suggestions? i've tried holding down power and vol down for 5 min. i've tried pushing random buttons. i've tried praying to the motorolla gods.
Is your phone the developer edition?
Sent from my Samsung Galaxy Tab 4 8" model using Tapatalk
gullbert said:
So....
I think I hard bricked my 1st gen moto x. I was in the process of unlocking the bootloader using motorolla's guide and everything was going fine. i had the "unlock..." (or "unlocked..." i forget what it actually said) showing on my screen and just out of habit, i hit the power button as i put the phone down.
now, nothing.
nothing at all. no recovery mode, no nothing. does anyone have any suggestions? i've tried holding down power and vol down for 5 min. i've tried pushing random buttons. i've tried praying to the motorolla gods.
Click to expand...
Click to collapse
Press and hold the volume down button simultaneously with the power button for about 5 seconds then release. Can you get into bootloader mode?
JulesJam said:
Press and hold the volume down button simultaneously with the power button for about 5 seconds then release. Can you get into bootloader mode?
Click to expand...
Click to collapse
I've tried that several times. Definitely can't get into bootloader mode.
plugin to charger.... what do you see
sumon511 said:
plugin to charger.... what do you see
Click to expand...
Click to collapse
absolutely nothing.
Hold the power button as well as both the volume buttons all together.
Does it do?
gullbert said:
absolutely nothing.
Click to expand...
Click to collapse
in that case,are you sure your charger/data cable is ok? also try connecting it to your computer with cable.do you see any device in computer? if its complete dead,then i see no hope
gullbert said:
absolutely nothing.
Click to expand...
Click to collapse
This sounds like a hardware failure, maybe a battery failure or a charging port failure. Like someone else suggested, try a different charger and see what happens.
Is it still under warranty?
JulesJam said:
This sounds like a hardware failure, maybe a battery failure or a charging port failure. Like someone else suggested, try a different charger and see what happens.
Is it still under warranty?
Click to expand...
Click to collapse
His warranty is void unless it's a dev edition
adity said:
His warranty is void unless it's a dev edition
Click to expand...
Click to collapse
Depends on the state - in many states in the US, a manufacturer cannot void a warranty if the product failure/defect has nothing to do with why the manufacturer wants to void the warranty.
Since unlocking a bootloader has nothing to do with a battery failure, in those states where the law is as I stated above, Motorola cannot void the warranty. Now the average Joe may not know this and may not know how to sue Motorola if they won't honor the warranty, but if you do know this and do know how to file a small claims case against Motorola, then you would win in those states.
So it is not across the board true that you void your warranty if you unlock your bootloader and don't have a dev ed. It depends on the state and what is wrong with your phone.
Happened once to my Galaxy Nexus, solved with Odin. I don't know if there's such thing for Motorola devices :/
Odin can reconize the phone when powered off, that's why it worked.
i had no fastboot, recovery or battery icon when plugged to charger
JulesJam said:
Press and hold the volume down button simultaneously with the power button for about 5 seconds then release. Can you get into bootloader mode?
Click to expand...
Click to collapse
I had this exact same thing happen today, but I pressed power because the phone was hung there for a minute when I know it takes 1 second.
Nothing, Its like there is no battery it it. Damnit
Lamarrotems said:
I had this exact same thing happen today, but I pressed power because the phone was hung there for a minute when I know it takes 1 second.
Nothing, Its like there is no battery it it. Damnit
Click to expand...
Click to collapse
Keep it plugged in, if it is totally drained, it will not turn on for a while until it gets charged to a safe level. Then after awhile on the charger, try to get into bootloader mode.
JulesJam said:
Keep it plugged in, if it is totally drained, it will not turn on for a while until it gets charged to a safe level. Then after awhile on the charger, try to get into bootloader mode.
Click to expand...
Click to collapse
Unfortunately I have been charging it for a day now and nothing. I think I need to try that RDS lite fix or moto x flasher tool. Only problem is I don't have a windows computer with admin access, so trying to borrow one.
Lamarrotems said:
Unfortunately I have been charging it for a day now and nothing. I think I need to try that RDS lite fix or moto x flasher tool. Only problem is I don't have a windows computer with admin access, so trying to borrow one.
Click to expand...
Click to collapse
Anyone had any experience with RDSLite or MotoFlasher? Haven't been able to get either to work, been trying for a couple hours. Any hlep would be GREATLY Appreciated - I am a poor grad student!
Younex said:
Happened once to my Galaxy Nexus, solved with Odin. I don't know if there's such thing for Motorola devices :/
Odin can reconize the phone when powered off, that's why it worked.
i had no fastboot, recovery or battery icon when plugged to charger
Click to expand...
Click to collapse
That is the first to.e hearing Odin being used on a nexus. That is interesting. I always thought odin was for Samsung only.
Travisdroidx2 said:
That is the first to.e hearing Odin being used on a nexus. That is interesting. I always thought odin was for Samsung only.
Click to expand...
Click to collapse
Samsung made at least one of the past nexus devices. -> http://en.wikipedia.org/wiki/Galaxy_Nexus
KidJoe said:
Samsung made at least one of the past nexus devices. -> http://en.wikipedia.org/wiki/Galaxy_Nexus
Click to expand...
Click to collapse
Good point. I have the old gnex. I just always used fastboot. Never read about anyone using Odin the whole time I used it. Always learn something new!
Same thing just happened to me. It was displaying blue "unlock..." then just froze. Absolutely nothing, just a black screen. Can't get into any bootloader or recovery. I really hope this phone is not totally screwed now. Any of you guys have any luck?

Phone won't power on, enter recovery mode, or enter fastboot mode

Google play, chrome, and other apps were randomly crashing one day, think it might've been related to google update. Decided to try and flash a stock image with nexus toolkit. It got to checking fastboot connectivity which failed, then I tried to turn on my phone and it won't work. Won't enter fastboot or recovery mode either. Is there anything I can do?
Your biggest mistake was in relying on Wugfresh without understanding the underlying fastboot and adb commands.
If you have no bootloader, no recovery and no OS, you have no phone. So do you have a bootloader?
Strephon Alkhalikoi said:
Your biggest mistake was in relying on Wugfresh without understanding the underlying fastboot and adb commands.
If you have no bootloader, no recovery and no OS, you have no phone. So do you have a bootloader?
Click to expand...
Click to collapse
I don't know what wugfresh is, is it another name for nexus toolkit?
How do I know if I have a bootloader? The phone was rooted so I believe I had an unlocked bootloader if that's what you mean.
Firion Hope said:
I don't know what wugfresh is, is it another name for nexus toolkit?
How do I know if I have a bootloader? The phone was rooted so I believe I had an unlocked bootloader if that's what you mean.
Click to expand...
Click to collapse
If your phone won't power on, its probably bricked to the max. Meaning that the Google Logo does not show up.
If you charge your phone, it should be receiving power. First thing I would do is to plug your phone into a wall charger with a micro USB to see if it charges. If it charges, you can then try holding down the power button + volume down to turn on the phone and wait to see if the bootloader shows up.
Gysper said:
If your phone won't power on, its probably bricked to the max. Meaning that the Google Logo does not show up.
If you charge your phone, it should be receiving power. First thing I would do is to plug your phone into a wall charger with a micro USB to see if it charges. If it charges, you can then try holding down the power button + volume down to turn on the phone and wait to see if the bootloader shows up.
Click to expand...
Click to collapse
Nothing happens sadly
If it isn't able to be fixed by me, could it be fixed by a phone repair specialist? And any idea what caused it to break so I don't do it again? Though I guess in general I'll just avoid rooting my device in the future.
@Firion Hope: Wugfresh is the author of the Nexus Toolkit. As you're finding out, toolkits are bad things when you don't know what you're doing. If something does go wrong, you have no frame of reference to help you fix it: no logs, no error messages, no nothing. This also means there is no way to tell what caused the problem in the first place so you can avoid it in the future.
The best way to prevent something like this from happening again is knowledge. Reading forum posts, blogs, Google's own webpages, or even watching videos of other people rooting a device will help provide some of that knowledge; the rest will come with experience. With knowledge of what you're doing, if you do decide you want to try rooting a device in the future you can be prepared to solve a problem if it occurs.
If the device cannot be revived by you, a person with the right hardware could potentially revive the device. However, the people who can do this are often sketchy types who will use that hardware to do illegal things. Thus we can't really discuss it here.
https://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518/page1
How to fix a hard brick.
What you're describing *could* be due to a ancient battery with charge issues.
Try plugging the phone into your computer's usb port to charge (at low power) for maybe an hour. Then unplug and plug in again. If the green led lights up, it's now charging the battery. Give it awhile and when you push the power button you should get the basic battery charging display. Once that happens, it should turn on.
You should now be able to charge normally.
Once you can boot normally, boot into bootloader, scroll through until you find bootloader logs then press and hold the power button until the phone reboots (~7 sec). Now fully charge the phone.
That process will buy you some time...maybe. you should get the battery replaced.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

S10 hard bricked (yes, actually)

UPDATE - Turns out the motherboard was dead. Apparently it's a problem that's been going around S10s lately
Left my S10 on the table over the night. Woke up this morning and nothing's responding. After 5 years of developer experience, I believe this device is hard bricked.
Tried force restarting
Recovery mode (bixby+power+volume up) doesn't work at all
Power button, and any other combination of power button, volume buttons, and bixby buttons does not work at all. No sign of life
Plugged it into computer and I see no devices in device manager, even with correct drivers
ADB and fastboot search does not find anything
Tried charging it with all sorts of chargers, with no sign of life
Because of this, I believe my device to be completely bricked (in which case, the only option is warranty and replace). I think it's a motherboard issue - not a battery issue, as it doesn't work even when plugged in. Am I missing something here?
What scares me is that I literally did nothing to it, and all of a sudden it bricks. I can't even flash stock firmware as my computer won't recognize it.
Try holding volume down and bixby button and then plug in the usb to a computer.
Oh no, you brick, you buy!!!!
Player04 said:
Try holding volume down and bixby button and then plug in the usb to a computer.
Click to expand...
Click to collapse
matthewclso said:
Power button, and any other combination of power button, volume buttons, and bixby buttons does not work at all. No sign of life
Plugged it into computer and I see no devices in device manager, even with correct drivers
Click to expand...
Click to collapse
Tried that already.
Player04 said:
Oh no, you brick, you buy!!!!
Click to expand...
Click to collapse
As for the warranty, Samsung does replace all devices as long as the fault was not on the user. Per Samsung's warranty policy, all devices are covered for one year for issues such as this.
matthewclso said:
Tried that already.
As for the warranty, Samsung does replace all devices as long as the fault was not on the user. Per Samsung's warranty policy, all devices are covered for one year for issues such as this.
Click to expand...
Click to collapse
If i may ask, which version of the S10 is this.
Player04 said:
Try holding volume down and bixby button and then plug in the usb to a computer.
Oh no, you brick, you buy!!!!
Click to expand...
Click to collapse

Categories

Resources