Develop Bugs

[Q] Did I just brick my Galaxy Nexus?

Forgive me if this is the wrong forum for this but today I was just playing a game on phone when it just crashed,
I thought no big deal I'll just reboot so went to reboot, however it just went into a bootloop and would not reboot. Then I thought ok CWR but I could not boot into this. I then decided to use adb mode to flash back to stock. However in this process adb froze and would not respond anymore and kind of had a blue tearing around everything on the screen. I ended up having to pull the battery.
Now however the phone won't respond at all, Won't turn on, won't go into download mode or anything. I can get my computer and laptop to regonize it when I plug it on with no battery but just says searching for driver for OMAP 4440 then fails. I'm pretty sure I have bricked it and am quite sad. Just looking for confirmation.

Its still alive, I'm pretty sure someone with a bit more knowledge will stop by and help you, but it appears to just be a soft brick.
Sent from my Galaxy Nexus using XDA App

Just to possibly give you some hoe look into Odin. When I had my fascinate this was the way to fix things. Being made by Samsung I'm sure it'll be similar. Do some research into that. Just got my nexus two days ago so I'm still fresh
Sent from my Galaxy Nexus using Tapatalk

rctreadaway said:
Just to possibly give you some hoe look into Odin. When I had my fascinate this was the way to fix things.
Click to expand...
Click to collapse
I'm afraid that's a little bit different situation here:
signzero said:
the phone won't respond at all, Won't turn on, won't go into download mode or anything. I can get my computer and laptop to regonize it when I plug it on with no battery but just says searching for driver for OMAP 4440 then fails.
Click to expand...
Click to collapse
Not connected to PC - no ADB, no ODIN. Plus, his phone failed while playing game (under heavy load) which gives me a reason to think it's a hardware fault. I would say last chance is to try USB Jig.

If you can get to the bootloader, you should be able to flash a stock Google image
Sent from my Galaxy Nexus

signzero said:
Forgive me if this is the wrong forum for this but today I was just playing a game on phone when it just crashed,
I thought no big deal I'll just reboot so went to reboot, however it just went into a bootloop and would not reboot. Then I thought ok CWR but I could not boot into this. I then decided to use adb mode to flash back to stock. However in this process adb froze and would not respond anymore and kind of had a blue tearing around everything on the screen. I ended up having to pull the battery.
Now however the phone won't respond at all, Won't turn on, won't go into download mode or anything. I can get my computer and laptop to regonize it when I plug it on with no battery but just says searching for driver for OMAP 4440 then fails. I'm pretty sure I have bricked it and am quite sad. Just looking for confirmation.
Click to expand...
Click to collapse
It's a hard brick, mate...
How to fix?:
take the back cover off your phone!
Remove battery, then plug in via USB (computer)
Leave for 3 hours!!! (With battery still unplugged) This should, in a way, "reset" your phone.
Once the three hours are over, plug in battery, and unplug USB.
Press PWR+VOL Down
Wait untill hpone boots into Odin mode then flashstock firmware from Samsung website.I
If this doesn't work, then I'd send it to Mobile Tech Videos, they kann unbrick it via JTAG...
Let me know if it worked, pleasse
---------- Post added at 04:26 PM ---------- Previous post was at 04:24 PM ----------
MS. said:
I'm afraid that's a little bit different situation here:
Not connected to PC - no ADB, no ODIN. Plus, his phone failed while playing game (under heavy load) which gives me a reason to think it's a hardware fault. I would say last chance is to try USB Jig.
Click to expand...
Click to collapse
He didn't mean playing, as in games. He meant playing around with his phone, root etc....

Thanks for the advice guys, gives me a small amount of hope. I will try leaving it plugged into my computer for 3 hours + and see what happens. Will post back with results.
Otherwise I may try get my hands on a jig. Would it be the same one from the Galaxy SII?

It worked? I'll explain you what happened to me:
I was playing for 2 hours on the game cartoon wars. After that, the phone was a little hot, I went to the desktop and locked the phone. 20 minutes later, I try to unlock the phone and I see the Google logo, and nothing responds. I pulled out the battery several times, tried to enter recovery, fastboot, normal boot. Always freezes. Stock 100%, the mobile has one week.... I think I will have to send it to the SAT....
I have my old HTC magic awaiting me, I gave my galaxy S to my sister...

Brick is such a misused word...

hmm
well if your running with verizon, which i doubt many of you are (prob using the GSM Gnex) you could just as easily bring it to them, lie, and theyll replace your phone. had a droid X, cracked the screen, told verizon it had a hardware fault, and they replaced it with no questions. verizon employees are pretty stupid

jttate04 said:
well if your running with verizon, which i doubt many of you are (prob using the GSM Gnex) you could just as easily bring it to them, lie, and theyll replace your phone. had a droid X, cracked the screen, told verizon it had a hardware fault, and they replaced it with no questions. verizon employees are pretty stupid
Click to expand...
Click to collapse
You are a horrible person and one of the reasons why decent, hardworking people can't have nice things.

So none of the methods suggested have work so looks like I'm going to have to get a Jig and hope that will do the trick otherwise I'm doomed I think.

when you guys say jig do you mean using resistors on the micro usb port to boot like with the old captivate? i still have the resistors mirco usb plug for that phone, it saved me from a hard brick a few times.

familyguy59 said:
He didn't mean playing, as in games. He meant playing around with his phone, root etc....
Click to expand...
Click to collapse
First post says "i was playing a game"...
neotekz said:
when you guys say jig do you mean using resistors on the micro usb port to boot like with the old captivate? i still have the resistors mirco usb plug for that phone, it saved me from a hard brick a few times.
Click to expand...
Click to collapse
Yup.

Nexus' dead, Samsung USA cannot help and am lost

So more than a week ago my phone went into "Downloading Mode" and I had no clue what it was in the first place. I took my battery off and put it back and still didn't work.
After that my phone only went to Downloading or fastboot and so I researched more about all these rooting and unlocking stuff. I downloaded Gnex toolkit because I wanted to go back to stock 4.0.2 again and I did what the program told me (Unlocked my bootloader and downloaded the GSM 4.0.2 factory image and set up fastboot.exe). My phone was recognized by GNEx toolkit and fastboot and I put yes to bring back to stock 4.0.2 but half way through the process it gave me an error (******(Unknown error)) and my phone went off and now it WON'T GO to fastboot or downloading mode. The phone doesn't start and if it did it goes it's stuck on the google but it doesn't show up; it shows up as a messed up green pixeled image.
I called Samsung USA and they said we cannot help you and I got really pissed while talking to them because they cannot help and they said they don't know who could.....then the guy offered to give me Samsung China number which I refused and hung up.
So how to get my phone back from the dead. The computer doesn't recognize it and if it turns on to this green google messed up image it doesn't do anything, it just goes off and comes back on the same screen.
Please help guys. this $680 phone is now a piece of scrap

You're right, Samsung USA is in no way obligated to help you, considering they don't sell the phone here (this should be well known when you buy a "gray market" device). You can't get mad at them about that. Where did you buy it from?
If it sometimes boots you have a chance. Someone more knowledgable than me will be able to give you specifics I'm sure. It may require some kind of USB jig to get it into fastboot mode though.

I bought it from back home Abu Dhabi, UAE but it was imported. The phone is probably made in SK.

martonikaj said:
Someone more knowledgable than me will be able to give you specifics I'm sure. It may require some kind of USB jig to get it into fastboot mode though.
Click to expand...
Click to collapse
Do you know anyone that could actually help me on here?

So holding power and the down volume button doesnt bring to you the Download screen?

No. I cannot access DM or fastboot.

upon plugging in your phone via USB on the computer, does it recognize your device? (does it make the USB noise)

Uh oh. Pixelated droid = fried processor. It needs to be replaced.
I was just wrestling with one of these today - couldn't bring it back to life no matter what I did.

zephiK said:
upon plugging in your phone via USB on the computer, does it recognize your device? (does it make the USB noise)
Click to expand...
Click to collapse
Yes it does and it starts charging.
computer tells me unable to recognize usb

NaeNegriTech said:
Uh oh. Pixelated droid = fried processor. It needs to be replaced.
I was just wrestling with one of these today - couldn't bring it back to life no matter what I did.
Click to expand...
Click to collapse
I am not sure about that. I was only flashing to stock, but when I plug it to the computer first the battery icon on the screen is green but then it goes back to a normal looking icon and charges.

Tried taking it to a phone shop? See if they can come up with any ideas. Otherwise maybe insure it and make a claim possibly depending on terms and conditions
Sent from my Galaxy Nexus using XDA

Try holding down both the Volume Keys while putting in the battery and connecting the USB (which should already be connected to the computer). If that doesn't work, try it again with holding the power button. This was one of the solutions that brought back my Samsung Vibrant from the dead a couple of times. USB Jigs are an option as well, and any Samsung Galaxy S one should work. You can even make one yourself.

hard bricked my phone

Hey Guys, long time reader never posted. I think i may have hard bricked my brand new 5X. I am not new to flashing ROMs I have had great sucess with my old Nexus5 for year (now I have to revert to that phone for now)
I was running Cyanogenmod then decided to try Catalysm. All was wokring fine and then i decide to just reflash to stock. I downloaded the correct factory image went into terminal like usual (linux) executed sudo ./flash-all in the correct folder and it went through the process in about a second then the phone turned off and my terminal screen said waiting for device. After waiting a while i tried turning the phone on got nothing. unplugged the phone tried volume down and power all the regular stuff to make the phone turn on. Plugging it into the charger shows nothing and I cant get into the bootloader.
I have never had an issue like this before I cant figure out flashing stock image would brick my phone? Am i totally screwed with warannty?
Thanks for any help gusy.

Maybe a to simple question.
How long was it ago? Maybe it's stick stuck in the loop with the screen off and maybe you have to wait it out.

If the phone dropped dead they can't even get into it to void your warranty, which I doubt they would do anyway. Let the phone sit for a little bit with it plugged in just so you can relax for a few minutes. Just hold the power button until it turns on. If it won't turn on at all then contact Google for a replacement device.

brick
bobby janow said:
If the phone dropped dead they can't even get into it to void your warranty, which I doubt they would do anyway. Let the phone sit for a little bit with it plugged in just so you can relax for a few minutes. Just hold the power button until it turns on. If it won't turn on at all then contact Google for a replacement device.
Click to expand...
Click to collapse
This just happened about an hour or so ago. Well i was thinking the same thing with the phone looping and no screen but it doesnt feel warm like its on. Also adb devices doesnt list it as on although i would imagine boot looping it would not see the device. Ive tried letting it charge for about a half hour with no luck. should I try letting it sit over night on the charger or off the charger in case its looping and i need it to die eventually?
I just reflashed the stock firmware on my old nexus 5 with no issues, its working fine i did that to make sure it wasnt an error i made.

Interesting, did you check the md5?,
I've never had success with flashall.bat it never worked, I end up extracting the archive and read the commands in flashall.bat and do it manually, worked for me,
When connected to pc does the pc drivers come up and disconnect due to device unplugged?( not sure if it displays on linux

republicano said:
Interesting, did you check the md5?,
I've never had success with flashall.bat it never worked, I end up extracting the archive and read the commands in flashall.bat and do it manually, worked for me,
When connected to pc does the pc drivers come up and disconnect due to device unplugged?,
Click to expand...
Click to collapse
I just figured out what happened. I flashed the nexus 5 flash-all rather then the nexus 5x (wow really dumb mistake). I found the hammerhead folder in the nexus5x folder i flashed from.
Now what?

If you can't get the phone to turn on you're out of luck.

Hey had something simmilar that my phone blank and unresponsive. No turning off. But maybe battery gone empty? try to leave phone longer under changer like for 1-2h or so. ANd the red led should be on showing phone battery gone full empty.

thanks for the help
Czepek said:
Hey had something simmilar that my phone blank and unresponsive. No turning off. But maybe battery gone empty? try to leave phone longer under changer like for 1-2h or so. ANd the red led should be on showing phone battery gone full empty.
Click to expand...
Click to collapse
Yea I am going to leave it for a day to make sure if its boot looping it will shutdown, then I am going to charge it for a day and try to turn it on see where i end up.

kmsgli said:
Yea I am going to leave it for a day to make sure if its boot looping it will shutdown, then I am going to charge it for a day and try to turn it on see where i end up.
Click to expand...
Click to collapse
Also, holding the power button for a few minutes to see if it eventually boots

You need to read the flashall.bat and see what the first commands were, as I think the bootloader maybe the first
Sorry but I doubt it will come back to life, if it bricked at fastboot flash bootloader, then reboot and failed to turn on to flash the rest,
It may need jtag service or you need to find something similar to this post below
forum.xda-developers.com/lg-g2/general/file-unbrick-qualcomm-9006-qhsusb-t3056800

lsusb
republicano said:
You need to read the flashall.bat and see what the first commands were, as I think the bootloader maybe the first
Sorry but I doubt it will come back to life, if it bricked at fastboot flash bootloader, then reboot and failed to turn on to flash the rest,
It may need jtag service or you need to find something similar to this post below
forum.xda-developers.com/lg-g2/general/file-unbrick-qualcomm-9006-qhsusb-t3056800
Click to expand...
Click to collapse
So with my phone plugged into my latop (linux) i run lsub with it plugged in and with it not plugged in and the differnce is this;
Bus 002 Device 031: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
my compuer is recognizing the device somehow but its the wrong name?

kmsgli said:
So with my phone plugged into my latop (linux) i run lsub with it plugged in and with it not plugged in and the differnce is this;
Bus 002 Device 031: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
my compuer is recognizing the device somehow but its the wrong name?
Click to expand...
Click to collapse
Sounds about right, that thread is for lg g2 and was just for display purpose, I not 100% sure if you can go through lg process on lg nexus,
Since the phone is also new I have not found any information on emmc fix.
You will have to go here and see if you can get help, but I think it will be some time till its released/leaked, you may have to pay to get it serviced.sorry about your Christmas present
forum.gsmhosting.com/vbb/f606/

Call Google and get it replaced. They are very good about that stuff.

kmsgli said:
I just figured out what happened. I flashed the nexus 5 flash-all rather then the nexus 5x (wow really dumb mistake). I found the hammerhead folder in the nexus5x folder i flashed from.
Now what?
Click to expand...
Click to collapse
Let Google know what happened, they're usually pretty good with that stuff and will probably let you RMA it. Google generally expects people to root their device, even though damaging the device while doing so is not technically covered under warranty they will probably help you out.
If 1 rep says no, call back and try another one. You can find countless examples online of people in your situation who Google helped out. Good luck!

Thanks guys
Thanks for all the help guys, I really apprecaite it, this site is really a great site full of people who want to help. ( im used to car forums where people call you an idiot any chance they get).
Ill post back if google did in fact help me out I will just wait for monday as I want to make sure if the phone is on for some reason with a weird screenless boot loop it has time to die and I can make sure I cant get it to boot myself.

Great news!! LG has repaired my phone and said they sent it back to me today. I have not confirmed it to be working as its in the mail but was told the phone has been repaired. So all you guys that do this while still under factory warranty can have your phone repaired by LG direct. Don't bother with google they can't repair it.

kmsgli said:
Great news!! LG has repaired my phone and said they sent it back to me today. I have not confirmed it to be working as its in the mail but was told the phone has been repaired. So all you guys that do this while still under factory warranty can have your phone repaired by LG direct. Don't bother with google they can't repair it.
Click to expand...
Click to collapse
So I guess that means it was so damaged even LG's equipment couldn't read any software/firmware details from the phone. Lucky for you. Just curious, what excuse did you give LG to make them think it wasn't caused by a software modification?

That's just it I was 100% honest and told them I accidentally flashed the nexus 5 image rather then the 5x image and bootloader was first on the flashall script. The girl who took the initial call didn't understand what I was saying so she typed exactly what I told her in the notes. I have to assume LG has a facotry cable that can flash the correct bootloader in seconds and the phone is back to new again.
really happy with LG service!!!!!

Really...really bricked OnePlus 3

Hi guys, I would like to share my experience with a bricked OP3, I own my OP3 about 3 months ago, currently I'm running 3.5.3 CB, and zero problems with the device until now.
My younger brother has his OP3 about two months ago, and I don't know what's he thinking but he flashed a CM12 on his OP 3. Really I don't understand why a person could do that, however he really screw the phone. Never return from death.
I've tried all guides and possible solutions for the brick, there is no bootloader, no recovery, no vibration, no anything. The phone is really dead.
The device it's recognized by the pc after installing qualcomm drivers and after pressing power +volume up buttons, like qualcomm 9008, and it gets recognized by the unbrick took (msm download tool v3.0).
And when I start the tool it start to flash anything goes apparently well, green successful message. But phones continue as a expensive brick.
When I plugged the phone like it should be, pressing only volume up and connecting cable it gets correctly recognized like qualcomm 9008, and by the tool, but when I hit start, it give me that saharra communication failed message.
But when I unplugged and connect again and hit power + volume up, gets recognized again but I doesn't have that Sahara error and even its flashed with the tool, but phone continue to be dead.
I've disassembled the phone to see if I can see some simple trouble in the hardware maybe, I tested changing parts with my phone to see if the trouble is in some charging or display or anything like that, but all parts are working well.
Even I've put my motherboard on the dead phone and it works perfectly.
I can give up to leave this phone dead like that but I've tried anything possible so I'm planning selling spare parts.
In my country I don't have any SAT or any place like that to repair the phone.

dannytgt said:
Hi guys, I would like to share my experience with a bricked OP3, I own my OP3 about 3 months ago, currently I'm running 3.5.3 CB, and zero problems with the device until now.
My younger brother has his OP3 about two months ago, and I don't know what's he thinking but he flashed a CM12 on his OP 3. Really I don't understand why a person could do that, however he really screw the phone. Never return from death.
I've tried all guides and possible solutions for the brick, there is no bootloader, no recovery, no vibration, no anything. The phone is really dead.
The device it's recognized by the pc after installing qualcomm drivers and after pressing power +volume up buttons, like qualcomm 9008, and it gets recognized by the unbrick took (msm download tool v3.0).
And when I start the tool it start to flash anything goes apparently well, green successful message. But phones continue as a expensive brick.
When I plugged the phone like it should be, pressing only volume up and connecting cable it gets correctly recognized like qualcomm 9008, and by the tool, but when I hit start, it give me that saharra communication failed message.
But when I unplugged and connect again and hit power + volume up, gets recognized again but I doesn't have that Sahara error and even its flashed with the tool, but phone continue to be dead.
I've disassembled the phone to see if I can see some simple trouble in the hardware maybe, I tested changing parts with my phone to see if the trouble is in some charging or display or anything like that, but all parts are working well.
Even I've put my motherboard on the dead phone and it works perfectly.
I can give up to leave this phone dead like that but I've tried anything possible so I'm planning selling spare parts.
In my country I don't have any SAT or any place like that to repair the phone.
Click to expand...
Click to collapse
Damn that sucks. He probably flashed the wrong rom or something else. You should contact oneplus and see if they can do something about it cuz i reckon your brother's phone still has warranty.

dannytgt said:
Hi guys, I would like to share my experience with a bricked OP3, I own my OP3 about 3 months ago, currently I'm running 3.5.3 CB, and zero problems with the device until now.
My younger brother has his OP3 about two months ago, and I don't know what's he thinking but he flashed a CM12 on his OP 3. Really I don't understand why a person could do that, however he really screw the phone. Never return from death.
I've tried all guides and possible solutions for the brick, there is no bootloader, no recovery, no vibration, no anything. The phone is really dead.
The device it's recognized by the pc after installing qualcomm drivers and after pressing power +volume up buttons, like qualcomm 9008, and it gets recognized by the unbrick took (msm download tool v3.0).
And when I start the tool it start to flash anything goes apparently well, green successful message. But phones continue as a expensive brick.
When I plugged the phone like it should be, pressing only volume up and connecting cable it gets correctly recognized like qualcomm 9008, and by the tool, but when I hit start, it give me that saharra communication failed message.
But when I unplugged and connect again and hit power + volume up, gets recognized again but I doesn't have that Sahara error and even its flashed with the tool, but phone continue to be dead.
I've disassembled the phone to see if I can see some simple trouble in the hardware maybe, I tested changing parts with my phone to see if the trouble is in some charging or display or anything like that, but all parts are working well.
Even I've put my motherboard on the dead phone and it works perfectly.
I can give up to leave this phone dead like that but I've tried anything possible so I'm planning selling spare parts.
In my country I don't have any SAT or any place like that to repair the phone.
Click to expand...
Click to collapse
Really sorry To hear it?? BUT CM12 rom??? ? where he find it....?? if you hard bricked phone.. go to a expart devs shop.. he may be solved your problem

If your phone will not power on oneplus service center person are also not able to check how your phone will dead i think so you can claim the warranty.

CM 12 roms developed for One Plus 2,I don't really now why in the hell he do that, but he did it: https://forums.oneplus.net/threads/cyanogenmod-os-12-1-yog4pas1n0-update-25-08-15.349531/
What do you mean with expert dev shop?
Anyway I didn't think I will find some like that shop, I'm in Buenos Aires, Argentina, and maybe 99% of the cellphones technician didn't know anything about Oneplus 3,that's the reason why I've disassembled by miself.

dannytgt said:
CM 12 roms developed for One Plus 2,I don't really now why in the hell he do that, but he did it: https://forums.oneplus.net/threads/cyanogenmod-os-12-1-yog4pas1n0-update-25-08-15.349531/
What do you mean with expert dev shop?
Anyway I didn't think I will find some like that shop, I'm in Buenos Aires, Argentina, and maybe 99% of the cellphones technician didn't know anything about Oneplus 3,that's the reason why I've disassembled by miself.
Click to expand...
Click to collapse
No wonder why it got bricked xD. You should see if you still have the warranty for your brothers phone. Contact oneplus and see if they can replace the phone.

I contact oneplus and they say me I wanna contact my seller to review warranty, but I bought on "Mercado libre" some trading online place like ebay.
So we are in a really bad situation.

dannytgt said:
I contact oneplus and they say me I wanna contact my seller to review warranty, but I bought on "Mercado libre" some trading online place like ebay.
So we are in a really bad situation.
Click to expand...
Click to collapse
Well ****. Can't you contact the seller that you bought it from? Also your brother should be careful next time he flashes a rom. We all make mistakes, sometimes ppl have to learn it the hard way.

Yes this will be the first phone since 2005 year when I started to flash custom roms on samsung omnia i900, thats really dead, I bring from the death a lot of bricked phones. But this phone is really dead so I think I will start sparing parts, maybe we can recover some of the money invested on the device.

S20 Ultra Bricked (G9880)

Hi guys, i come here searching for help, it was a normal day, i was out with the phone fully working, it was on my pocket, when i get home i see that it's off, tried to turn on and nothing... tried vol- and power to enter download mode and nothing, the screen is always black.
Connected it to my laptop to see if it shows up as a USB device, it sounds like it connected and in "Device Manager" it show as "QUSB_BULK_CID:0412_SN:BA92F870" but ODIN doesn't detect it, so i can't try to install a clean ROM.
I can't take it to samsung as this model is a HONG KONG one and i'm in Chile, they won't apply warranty and legally i had only 3 month in a external shop but i'm on my 5th month, so it's not use to try that way.
A few points about the phone:
Latest firmware: (INSTALLED NATURALLY, I GOT IT FROM SAMSUNG OFFICIALY)
Country/Carrier: Hong Kong
Date: 2020-10-26
Version: 10
PDA: G9880ZHU2BTJ6
CSC :G9880OZS2BTJ6
NEVER EVER tried to install a rom or something on the phone, i was happy with how it works and the battery i got from it.
Now i bought a S20 FE as a momentary replacement because i can't be without a phone for my work... i've read lots and lots of threads on XDA and other places but all of them are about the Note 4, so it's really out of date to try fix it that way, at least 6-8 years old posts.
Anyone here had a similar issue? is it fixable?
Hope someone can help, it really hurts loosing a phone that costs +USD1000
Thanks guys.

Gerstark said:
Hi guys, i come here searching for help, it was a normal day, i was out with the phone fully working, it was on my pocket, when i get home i see that it's off, tried to turn on and nothing... tried vol- and power to enter download mode and nothing, the screen is always black.
Connected it to my laptop to see if it shows up as a USB device, it sounds like it connected and in "Device Manager" it show as "QUSB_BULK_CID:0412_SN:BA92F870" but ODIN doesn't detect it, so i can't try to install a clean ROM.
I can't take it to samsung as this model is a HONG KONG one and i'm in Chile, they won't apply warranty and legally i had only 3 month in a external shop but i'm on my 5th month, so it's not use to try that way.
A few points about the phone:
Latest firmware: (INSTALLED NATURALLY, I GOT IT FROM SAMSUNG OFFICIALY)
Country/Carrier: Hong Kong
Version: 10
CSC :G9880OZS2BTJ6
NEVER EVER tried to install a rom or something on the phone, i was happy with how it works and the battery i got from it.
Now i bought a S20 FE as a momentary replacement because i can't be without a phone for my work... i've read lots and lots of threads on XDA and other places but all of them are about the Note 4, so it's really out of date to try fix it that way, at least 6-8 years old posts.
Anyone here had a similar issue? is it fixable?
Hope someone can help, it really hurts loosing a phone that costs +USD1000
Thanks guys.
Click to expand...
Click to collapse
Aorry to hear that.. did tou try vol up and power to go to recovery?

Gerstark said:
Hi guys, i come here searching for help, it was a normal day, i was out with the phone fully working, it was on my pocket, when i get home i see that it's off, tried to turn on and nothing... tried vol- and power to enter download mode and nothing, the screen is always black.
Connected it to my laptop to see if it shows up as a USB device, it sounds like it connected and in "Device Manager" it show as "QUSB_BULK_CID:0412_SN:BA92F870" but ODIN doesn't detect it, so i can't try to install a clean ROM.
I can't take it to samsung as this model is a HONG KONG one and i'm in Chile, they won't apply warranty and legally i had only 3 month in a external shop but i'm on my 5th month, so it's not use to try that way.
A few points about the phone:
Latest firmware: (INSTALLED NATURALLY, I GOT IT FROM SAMSUNG OFFICIALY)
Country/Carrier: Hong Kong
Date: 2020-10-26
Version: 10
PDA: G9880ZHU2BTJ6
CSC :G9880OZS2BTJ6
NEVER EVER tried to install a rom or something on the phone, i was happy with how it works and the battery i got from it.
Now i bought a S20 FE as a momentary replacement because i can't be without a phone for my work... i've read lots and lots of threads on XDA and other places but all of them are about the Note 4, so it's really out of date to try fix it that way, at least 6-8 years old posts.
Anyone here had a similar issue? is it fixable?
Hope someone can help, it really hurts loosing a phone that costs +USD1000
Thanks guys.
Click to expand...
Click to collapse
The device is powering on and off randomly on it's own, correct? This sounds like a hardware issue, you may have a defect somewhere in the power supply chain. If you have a reputable repair agency nearby, not necessarily Samsung, this would be my first step. Not sure why Odin isn't detecting the device. Here's an article which offers common solutions for this problem.
https://rootmygalaxy.net/fix-odin-not-detecting-samsung-android-phone/
Good luck!

myaslioglu said:
Aorry to hear that.. did tou try vol up and power to go to recovery?
Click to expand...
Click to collapse
Yes, but it doesn't work, screen alway stays on black, i know it's not fully dead because it sounds as a USB driver when connected to my laptop
varcor said:
The device is powering on and off randomly on it's own, correct? This sounds like a hardware issue, you may have a defect somewhere in the power supply chain. If you have a reputable repair agency nearby, not necessarily Samsung, this would be my first step. Not sure why Odin isn't detecting the device. Here's an article which offers common solutions for this problem.
https://rootmygalaxy.net/fix-odin-not-detecting-samsung-android-phone/
Good luck!
Click to expand...
Click to collapse
tomorrow i'll try to take it somewhere, thanks for the link, but i already tried all those tips

I take it you have a Qualcomm cpu? If so you need to install the Qualcomm usb driver, link https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/ or a newer version if available. This should solve the problem in regard of pc connection, usb recognition and most of all reading the internal memory. Please use Google search for mor info and the correct procedure as i never used this myself. Good luck.

gee2012 said:
I take it you have a Qualcomm cpu? If so you need to install the Qualcomm usb driver, link https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/ or a newer version if available. This should solve the problem in regard of pc connection, usb recognition and most of all reading the internal memory. Please use Google search for mor info and the correct procedure as i never used this myself. Good luck.
Click to expand...
Click to collapse
Anything you can find on google i already tried, installing the drivers didn't help either... thanks tho!

Oh hey, its you! We spoke on reddit a few days ago about this problem, sorry to see you haven't been able to fix it.
Have you tried all your USB ports? Or maybe another computer? Worst case scenario there's a solid chance Samsung will repair it either for free if you're lucky or for a price. Even if you bought it from another country there's a possibility the manufacturer's warrant is intact especially because it sounds like you didn't do anything to the phone at all that would've warranted the sudden failure.
Does ADB see it when it's plugged in? If you don't have ADB installed follow this: https://www.xda-developers.com/install-adb-windows-macos-linux, then once installed run "adb devices" from command prompt.