Related
Hi there, I hard bricked my Tab S 8.4. No reaction to anything I did (key combinations, let it charge for hours, stuff like that). Don't know how it happened but it just crashed to death shortly after installing an inofficial Lolloipop build from here. I don't think a ROM can make a device not turn on at all. My money is on hardware failure.
Anyway, brought it in for repairs (willing to pay since I knowingly voided the warranty). Got the call yesterday. They said the software had been tampered with and they can't repair it. I objected that the software won't break the hardware but no dice. They won't even do it for cold hard cash.
BUT: To see the 'illegal' software they HAD to get the thing to turn on . And if they got it to turn on somehow, so can I. Or... am I completely wrong there and they have some magic fairy dust?
Any ideas on how I could accomplish what the repair guys could obviously do? There is no important data or anything on it so I'd be happy with Odin mode, CWM or whatever.
dancress said:
Hi there, I hard bricked my Tab S 8.4. No reaction to anything I did (key combinations, let it charge for hours, stuff like that). Don't know how it happened but it just crashed to death shortly after installing an inofficial Lolloipop build from here. I don't think a ROM can make a device not turn on at all. My money is on hardware failure.
Anyway, brought it in for repairs (willing to pay since I knowingly voided the warranty). Got the call yesterday. They said the software had been tampered with and they can't repair it. I objected that the software won't break the hardware but no dice. They won't even do it for cold hard cash.
BUT: To see the 'illegal' software they HAD to get the thing to turn on . And if they got it to turn on somehow, so can I. Or... am I completely wrong there and they have some magic fairy dust?
Any ideas on how I could accomplish what the repair guys could obviously do? There is no important data or anything on it so I'd be happy with Odin mode, CWM or whatever.
Click to expand...
Click to collapse
I kindof had the same problem, but got mine repaired.
May I ask where you send it to for repairs? Was it Samsung or a local repair shop that told you they could not fix it?
And did they send it back to you? Kindof weird they won't fix your device after you say you are willing to pay for it.
Depending on where you live, Samsung covers a lot of 'problems' in the first year of the standaard warranty.
As for turning on the device..
What options have you tried yet?
If you connect the tablet with usb to your pc and turn it on, does it get recognized?
And if so, as what?
But if your screen doesn't turn on, you're probably going to need repairs anyway.
shifter7 said:
I kindof had the same problem, but got mine repaired.
May I ask where you send it to for repairs? Was it Samsung or a local repair shop that told you they could not fix it?
And did they send it back to you? Kindof weird they won't fix your device after you say you are willing to pay for it.
Depending on where you live, Samsung covers a lot of 'problems' in the first year of the standaard warranty.
As for turning on the device..
What options have you tried yet?
If you connect the tablet with usb to your pc and turn it on, does it get recognized?
And if so, as what?
But if your screen doesn't turn on, you're probably going to need repairs anyway.
Click to expand...
Click to collapse
Over here you bring it back to the shop where you bought it. They will try the simplest solutions in house but usually send it back to the manufacturer. I think the information came from Samsung directly. Another theory I have is a simple lie. They tried it in house, nothing came up, some clever guy screamed 'CYANOGEN!' and they all high fived (I have a vivid imagination )
As for turning it on: tried everything. It's not only the screen, it did nothing at all. No signs of life whatsoever. Of course the PC wouldn't recognize it since it was turned off.
I'll pick it up tonight. Maybe whatever they did to see the software tampering stuck and it will at least go into Odin mode. I can work from there.
dancress said:
Over here you bring it back to the shop where you bought it. They will try the simplest solutions in house but usually send it back to the manufacturer. I think the information came from Samsung directly. Another theory I have is a simple lie. They tried it in house, nothing came up, some clever guy screamed 'CYANOGEN!' and they all high fived (I have a vivid imagination )
Click to expand...
Click to collapse
I lolled
But it you think it came from Samsung directly, then I would advise you to contact Samsung.
Here is a link from an article where it states that Samsung covers bricked devices, but only the first time. (Dutch article, GTranslated english)
I have no idea if this also counts for where you live though.
https://translate.google.com/transl...er-garantie-repareren.html&edit-text=&act=url
dancress said:
As for turning it on: tried everything. It's not only the screen, it did nothing at all. No signs of life whatsoever. Of course the PC wouldn't recognize it since it was turned off.
I'll pick it up tonight. Maybe whatever they did to see the software tampering stuck and it will at least go into Odin mode. I can work from there.
Click to expand...
Click to collapse
Okay.. well.. that sucks.
Don't forget to ask for some of that magic dust they used
shifter7 said:
I lolled
But it you think it came from Samsung directly, then I would advise you to contact Samsung.
Here is a link from an article where it states that Samsung covers bricked devices, but only the first time. (Dutch article, GTranslated english)
I have no idea if this also counts for where you live though.
https://translate.google.com/transl...er-garantie-repareren.html&edit-text=&act=url
Okay.. well.. that sucks.
Don't forget to ask for some of that magic dust they used
Click to expand...
Click to collapse
Magic dust it was. Got it back, dead. Came home a minute ago, put it on the charger. Lo and behold, the battery appears. Device turns on too, boots Lollipop goodness. 0 per cent battery but hey. Whatever they did, they obviously did NOT realize they solved the whole problem with just their diagnostic :laugh:
Thread can be locked if the PTB deem it necessary.
dancress said:
Magic dust it was. Got it back, dead. Came home a minute ago, put it on the charger. Lo and behold, the battery appears. Device turns on too, boots Lollipop goodness. 0 per cent battery but hey. Whatever they did, they obviously did NOT realize they solved the whole problem with just their diagnostic :laugh:
Thread can be locked if the PTB deem it necessary.
Click to expand...
Click to collapse
I'm laughing so hard right now :laugh::laugh::laugh::laugh::laugh::laugh:
dancress said:
Magic dust it was. Got it back, dead. Came home a minute ago, put it on the charger. Lo and behold, the battery appears. Device turns on too, boots Lollipop goodness. 0 per cent battery but hey. Whatever they did, they obviously did NOT realize they solved the whole problem with just their diagnostic :laugh:
Thread can be locked if the PTB deem it necessary.
Click to expand...
Click to collapse
It simply reset itself after the battery completely died. Black screen and no response doesn't mean the device is off.
As soon as they switched it on they would have seen knox had been tripped.
Sort of did you a favour by telling you it wasn't bricked.
I had the same sort of problem i connected my tab to my laptop and used the recovery mode key combination then my tab came back to life
---------- Post added at 04:29 PM ---------- Previous post was at 04:29 PM ----------
Sorry download mode not recovery mode
Comforts me while ROM developing that the only reported case of a hardbrick was here - and the battery just died.
I got a text message from a friend around an hour ago. I had my phone on charge at the time and it was about 25% charged. I started typing a reply when the screen froze, went black and the boot screen came on - classic crash and reboot, right. But when the boot screen came up, it only stayed on for a couple of seconds and then went off again and the phone has been completely dead since. Well I tried holding the power button for about 30 seconds and nothing happened. So I tried Vol Up+Pwr and the phone vibrated and the boot screen appeared for a split second and went off again and the phone has been dead ever since. I've had it on charge for about 40 minutes but no joy.
This doesn't seem to be the classic bootloop issue from what I know about it. So can anyone help me out with how I could revive it?
Does your device show up as 9008 Qualcomm if you connect it to your computer?
-gloim- said:
Does your device show up as 9008 Qualcomm if you connect it to your computer?
Click to expand...
Click to collapse
In Device Manager, under ports it does show as "Qualcomm HS-USB QDLoader 9008 (COM5). Now you're gonna tell me its f**ked, right?
I can fix it contact me [emoji39]
Try this here: https://forum.xda-developers.com/g4/development/unbrick-lg-g4-h815-9008-qualcomm-t3452853
-gloim- said:
Try this here: https://forum.xda-developers.com/g4/development/unbrick-lg-g4-h815-9008-qualcomm-t3452853
Click to expand...
Click to collapse
Cheers Gloim. I'll give this a try.
An update to what has been happening - I left the phone with the battery removed overnight. I came down this morning, put the battery in and tried turning it on. The boot screen came up, along with the blue led, which is hopeful as there were no led's last night. The boot screen stayed on the screen maybe 15 seconds before the phone turned off again. I removed/replaced the battery, turned it on, same thing. So I tried booting into download mode (hold Vol UP button, insert usb cable and hold Vol Up until Firmware Update screen.), but the phone started booting up normally. A bit into the boot animation, it rebooted again. So I tried a normal bootup and it got to the lock screen, where it rebooted again after about 15 seconds again. I booted normally again, lockscreen again. This time it refused to turn on again.
So it appears all may not be lost.
I said pm me i give solution
dev8987.tiwari said:
I said pm me i give solution
Click to expand...
Click to collapse
Yeah, I was giving the other "solution" a try before contacting you. Don't worry, I'll probably be giving you a shout soon.
dev8987.tiwari said:
I said pm me i give solution
Click to expand...
Click to collapse
why pm? isn't the idea of the forum to share this kind of solutions?
mickrick said:
Yeah, I was giving the other "solution" a try before contacting you. Don't worry, I'll probably be giving you a shout soon.
Click to expand...
Click to collapse
any news? It happened to me just a couple of hours ago, was reading some news, the the screen went black with 2 lines on top white and blue, took off the battery put it back on, it started booting but the LG animation hanged up, took the battery of again, and it never turned back on, tried charging the battery for some time, tried removing battery and pluging the charger to see if the screen waked up with the battery logo, tried vol up + pwr, vol down +pwr, it does not even vibrate : S
magatsu82 said:
why pm? isn't the idea of the forum to share this kind of solutions?
any news? It happened to me just a couple of hours ago, was reading some news, the the screen went black with 2 lines on top white and blue, took off the battery put it back on, it started booting but the LG animation hanged up, took the battery of again, and it never turned back on, tried charging the battery for some time, tried removing battery and pluging the charger to see if the screen waked up with the battery logo, tried vol up + pwr, vol down +pwr, it does not even vibrate : S
Click to expand...
Click to collapse
Ok bro but it voids forum. Rules are you going to pay for that
---------- Post added at 05:05 PM ---------- Previous post was at 05:04 PM ----------
But still i will provide a written solution to you all when im free
-gloim- said:
Does your device show up as 9008 Qualcomm if you connect it to your computer?
Click to expand...
Click to collapse
I'm experiencing the exact same issue. Not the bootloop error, phone just went off and it may or may not power up. Currently it's stuck on the LG splashscreen. Not being recognised by my PC, is there no hope?
Edit: Now recognised by the PC. I'll check the other thread.
magatsu82 said:
any news? It happened to me just a couple of hours ago, was reading some news, the the screen went black with 2 lines on top white and blue, took off the battery put it back on, it started booting but the LG animation hanged up, took the battery of again, and it never turned back on, tried charging the battery for some time, tried removing battery and pluging the charger to see if the screen waked up with the battery logo, tried vol up + pwr, vol down +pwr, it does not even vibrate : S
Click to expand...
Click to collapse
No joy at all. I do know its the very common CPU/EMMC problem as I put the phone in the freezer for 15 minutes (in a freezer bag of course) and it booted up, but froze almost immediately and turned off again.
I contacted LG who rang me the following day asking for details and the caller said it is definitely a hardware issue, and if I send proof of purchase showing it was bought from a retailer it would be repaired free of charge. I bought mine from an ebay seller, which I told him, and he said if its an ebay company and not a private sale, it was ok. But if bought from a private seller, its considered 2nd hand and warranty is void, even if it was still sealed in its box, which I think is a bit harsh. Anyway, I thought I had bought mine from a private seller, but it turns out it was an ebay shop. I forwarded the proof of purchase and seller details on Friday and I've just received a call to say they are accepting it for a repair only. Which is less than ideal but they could've just said no I suppose. So when I get it back I'll sell it and buy something with a similar spec instead. Its the best phone I've used up till now.
Ok try ILAPO fix by disabling the2 cores and your phone will be on
mickrick said:
No joy at all. I do know its the very common CPU/EMMC problem as I put the phone in the freezer for 15 minutes (in a freezer bag of course) and it booted up, but froze almost immediately and turned off again.
I contacted LG who rang me the following day asking for details and the caller said it is definitely a hardware issue, and if I send proof of purchase showing it was bought from a retailer it would be repaired free of charge. I bought mine from an ebay seller, which I told him, and he said if its an ebay company and not a private sale, it was ok. But if bought from a private seller, its considered 2nd hand and warranty is void, even if it was still sealed in its box, which I think is a bit harsh. Anyway, I thought I had bought mine from a private seller, but it turns out it was an ebay shop. I forwarded the proof of purchase and seller details on Friday and I've just received a call to say they are accepting it for a repair only. Which is less than ideal but they could've just said no I suppose. So when I get it back I'll sell it and buy something with a similar spec instead. Its the best phone I've used up till now.
Click to expand...
Click to collapse
Was it still in warranty? Mine only came with the 12 month LG warranty. I bought it in November 2015, so it's out of warranty. I did log a repair with LG and they tried to call me but I missed the call, they sent me an SMS earlier but their offices are closed today. Wondering whether they would consider an out of warranty repair as it's 509 serial number and they were known to be faulty.
tharweb said:
Was it still in warranty? Mine only came with the 12 month LG warranty. I bought it in November 2015, so it's out of warranty. I did log a repair with LG and they tried to call me but I missed the call, they sent me an SMS earlier but their offices are closed today. Wondering whether they would consider an out of warranty repair as it's 509 serial number and they were known to be faulty.
Click to expand...
Click to collapse
I bought mine at the end of December 2015 and I read on their website that there is a 24 month hardware only warranty on the H815. They accepted it for a repair only under warranty, so I'm pretty sure there is an extended warranty period due to these hardware problems. They have accepted that it is an inherent problem so they would be legally bound to offer some sort of extension to the original warranty.
The only problem I can see now is them seeing the bootloader is unlocked and a custom recovery installed. But there was a legal ruling made in the UK several months ago in a case taken by a Samsung customer, that unlocking and rooting a phone is not a breach of warranty where a claim is made for a totally unconnected fault, ie an inherent hardware fault. But if the phone was rooted and overclocked causing cpu or ram damage, or bricked due to flashing an unsupported rom, for example, that would be a breach of warranty. But I get the feeling they would use any excuse to get out of honouring the warranty.
I just hope I get it back soon though. I'm using my old quadcore mediatek N9500 Chinese phone in the meantime and it's driving me mad. I don't remember it being this slow and laggy when I first got it
mickrick said:
I bought mine at the end of December 2015 and I read on their website that there is a 24 month hardware only warranty on the H815. They accepted it for a repair only under warranty, so I'm pretty sure there is an extended warranty period due to these hardware problems. They have accepted that it is an inherent problem so they would be legally bound to offer some sort of extension to the original warranty.
Click to expand...
Click to collapse
Interesting thanks. The web site shows 12 months for me? I will definitely give them a call then and see what they say. Good luck with yours.
Just a quick update, I rang LG this afternoon. I was asked a few questions, where I'd purchased from etc., then the agent started to book the repair in. I stopped her to ask whether it would be done under warranty, and she said, yes of course, your warranty is still current. So despite their web site indicating it had a 12 month warranty, it is 2 years. What a relief!
Sent from my Nexus 6P using Tapatalk
Any solution with unlocked bootloader ?
gamzekal said:
Any solution with unlocked bootloader ?
Click to expand...
Click to collapse
It goes either way some claim since its hardware failure there still warantying some of them even with unlocked bl. A lot of cases after return people having to update their device id with lg to get a new unlock .bin. Which means theyre honering unlocked bls too
gamzekal said:
Any solution with unlocked bootloader ?
Click to expand...
Click to collapse
TheMadScientist420 said:
It goes either way some claim since its hardware failure there still warantying some of them even with unlocked bl. A lot of cases after return people having to update their device id with lg to get a new unlock .bin. Which means theyre honering unlocked bls too
Click to expand...
Click to collapse
Mine was picked up on Wednesday last week and delivered back today. 7 day turnaround, not too bad at all. I think they put a new board in it though. It's still marshmallow but it has been returned to O2 branding and the bootloader locked. My existing unlock.bin won't work with it either.
Hi, I have a Galaxy S20 Ultra 512GB from T-Mobile. I have an issue that manifested itself a couple of hours ago, and have never encountered anything like it.
My S20 seems to be shutting itself off every time it boots fully and I have no idea how to fix it. I have tried safe mode, clearing cache, etc. Nothing has fixed it so far.
Is there anyone that could guide me in the right direction to potentially fix this, or do I have an expensive paperweight?
Edit: I have tried factory resetting as well now, and that did nothing to fix the issue. It gets part of the way through setup, then reboots again. Maybe I could be directed to try flashing the latest update file?
Edit #2: I was able to figure out how to fix the issue entirely and no longer require help, unless the issue crops up again.
Edit #3: I have no idea what's causing the issue but it's back. Phone shuts off after some time of use, I have no idea what to do at this point...
In case the issue persists after a factory reset and not using a backup to restore the phone I would suppose that the unit is defective and return it, if possible. If return is not possible, you could try and have Samsung repair it as it must be covered under some warranty, as it is brand new.
corwin_amber said:
In case the issue persists after a factory reset and not using a backup to restore the phone I would suppose that the unit is defective and return it, if possible. If return is not possible, you could try and have Samsung repair it as it must be covered under some warranty, as it is brand new.
Click to expand...
Click to collapse
Yeah... I tried to get into contact with T-Force to have T-Mobile send me a replacement as I am still financing the phone, but it looks like they don't even have it in stock and mistakenly are trying to send me a downgrade S20+ variant instead... Looks like I have a very expensive paperweight on my hands.
As for Samsung, all they were able to offer me at this point was to take it to a service center but with the pandemic limiting everyone to be able to work or go outside I don't think I can even do that at this point.
Nathaniel9001 said:
As for Samsung, all they were able to offer me at this point was to take it to a service center but with the pandemic limiting everyone to be able to work or go outside I don't think I can even do that at this point.
Click to expand...
Click to collapse
In EU Samsung offer courier pickup for repairs ... ask Samsung again if you can send your faulty handset in for repair
Nathaniel9001 said:
Hi, I have a Galaxy S20 Ultra 512GB from T-Mobile. I have an issue that manifested itself a couple of hours ago, and have never encountered anything like it.
My S20 seems to be shutting itself off every time it boots fully and I have no idea how to fix it. I have tried safe mode, clearing cache, etc. Nothing has fixed it so far.
Is there anyone that could guide me in the right direction to potentially fix this, or do I have an expensive paperweight?
Edit: I have tried factory resetting as well now, and that did nothing to fix the issue. It gets part of the way through setup, then reboots again. Maybe I could be directed to try flashing the latest update file?
Edit #2: I was able to figure out how to fix the issue entirely and no longer require help, unless the issue crops up again.
Edit #3: I have no idea what's causing the issue but it's back. Phone shuts off after some time of use, I have no idea what to do at this point...
Click to expand...
Click to collapse
It doesn't say what you tried to do to fix this - so if you haven't already -- I suggest downloading the most recent firmware (via Frija) and then flash in Odin. Don't use the HOME CSC - use the other one, this will force you to wipe data when it first boots up - when finished, it will boot up and you can set it up like a new phone.
If you don't already have it, you can download FRIJA here: https://forum.xda-developers.com/s10-plus/how-to/tool-frija-samsung-firmware-downloader-t3910594
Be sure to use the most recent patched Odin - https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
If this doesn't work, then it is most likely a hardware issue - but try this first to be sure.
Hope this helps.
Geekser said:
It doesn't say what you tried to do to fix this - so if you haven't already -- I suggest downloading the most recent firmware (via Frija) and then flash in Odin. Don't use the HOME CSC - use the other one, this will force you to wipe data when it first boots up - when finished, it will boot up and you can set it up like a new phone.
If you don't already have it, you can download FRIJA here: https://forum.xda-developers.com/s10-plus/how-to/tool-frija-samsung-firmware-downloader-t3910594
Be sure to use the most recent patched Odin - https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
If this doesn't work, then it is most likely a hardware issue - but try this first to be sure.
Hope this helps.
Click to expand...
Click to collapse
Hi, I tried exactly this process and the issue came back after a few minutes of using the phone along with a bit of graphical corruption when trying to use the phone. I'm guessing it's definitely a hardware issue. That's too bad though, I tried to get a replacement through T-Mobile and they have none in stock, I guess I'll see if I can get Samsung to replace it.
Good luck!
Geekser said:
Good luck!
Click to expand...
Click to collapse
Thank you! It's been a week now and I made a ticket with Samsung to have the phone repaired the same day I posted about it. I finally received my repaired phone, it turns out there was indeed a bad SoC on the motherboard and they went ahead and replaced the board, so I got to keep the phone I bought. It's too bad I couldn't recover my data, although I don't feel too bad about it anymore.
Mods feel free to close the thread, as this has been solved.
Nathaniel9001 said:
Thank you! It's been a week now and I made a ticket with Samsung to have the phone repaired the same day I posted about it. I finally received my repaired phone, it turns out there was indeed a bad SoC on the motherboard and they went ahead and replaced the board, so I got to keep the phone I bought. It's too bad I couldn't recover my data, although I don't feel too bad about it anymore.
Mods feel free to close the thread, as this has been solved.
Click to expand...
Click to collapse
Glad to hear it all worked out for the best. Hope you enjoy your phone!
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.
I'm kinda screwed here and I really really need some help.
So I basically rooted my Pixel 6 Pro just out of boredom and wanted to tweak some stuff with the rooted version. In the end, I decided that it wasn't worth rooting as most things i can do i could already do on stock like customization and other things. Anyway long story short I've tried to Use the google flash recovery tool I wasn't looking where i was clicking and ended up flashing 12 by accident It *Was on 13 at the time* had it got near to the end but it kept booting me to this one section called "fastbootd" I hit factory reset and from there it done the reset and now the phone no longer starts or doesn't even displays the charging percentage.
I've plugged it into a computer nothing pops up no noise from my computer to say it has connected.
I've also tried to use power + down for 30 seconds - didn't do nothing.
Has anyone got out of this issue? Is this a Hard Brick?
I've plugged it into a charger and will see what happens tomorrow. I genuinely think its the battery has fully drained.
Cause I've ran out of ideas to try things and I need your expertise on this guys.
Your help will really be appreciated.
Tombo12 said:
I'm kinda screwed here and I really really need some help.
So I basically rooted my Pixel 6 Pro just out of boredom and wanted to tweak some stuff with the rooted version. In the end, I decided that it wasn't worth rooting as most things i can do i could already do on stock like customization and other things. Anyway long story short I've tried to Use the google flash recovery tool I wasn't looking where i was clicking and ended up flashing 12 by accident It *Was on 13 at the time* had it got near to the end but it kept booting me to this one section called "fastbootd" I hit factory reset and from there it done the reset and now the phone no longer starts or doesn't even displays the charging percentage.
I've plugged it into a computer nothing pops up no noise from my computer to say it has connected.
I've also tried to use power + down for 30 seconds - didn't do nothing.
Has anyone got out of this issue? Is this a Hard Brick?
I've plugged it into a charger and will see what happens tomorrow. I genuinely think its the battery has fully drained.
Cause I've ran out of ideas to try things and I need your expertise on this guys.
Your help will really be appreciated.
Click to expand...
Click to collapse
I assume you didn't flash, at the minimum , the A13 bootloader to both slots or sideload the OTA after updating to A13 before doing this? If not, sounds like your device may have reverted to the A12 slot and ended up a brick due to the new ARB/eFuse shenanigans. The symptoms you describe are what happens when this occurs.
Luckily, it sounds like Google has been good at replacing devices that have encountered this so I would RMA it.
Lughnasadh said:
I assume you didn't flash, at the minimum , the A13 bootloader to both slots or sideload the OTA after updating to A13 before doing this? If not, sounds like your device may have reverted to the A12 slot and ended up a brick due to the new ARB/eFuse shenanigans. The symptoms you describe are what happens when this occurs.
Luckily, it sounds like Google has been good at replacing devices that have encountered this so I would RMA it.
Click to expand...
Click to collapse
Ahhh I'm from the UK. I only got the phone just a month ago too and now this has happened. I checked on the their Uk site i can take it to a local mobile carrier and they've stated that they will do the repair next day. I might just do that tomorrow if not then I'll speak to Google.
Tombo12 said:
Ahhh I'm from the UK. I only got the phone just a month ago too and now this has happened. I checked on the their Uk site i can take it to a local mobile carrier and they've stated that they will do the repair next day. I might just do that tomorrow if not then I'll speak to Google.
Click to expand...
Click to collapse
Good luck! Let us know how things go.
roirraW edor ehT said:
Good luck! Let us know how things go.
Click to expand...
Click to collapse
Some News for everyone!
So I spoke to Google and they was fine about it phone not working went through some troubleshooting tricks neither of the options worked. The rep on the phone gave me two options Send it into Google for a repair and they'll send me over a replacement 6 Pro whilst its being worked on. If they can't fix it they'll let me keep the phone but if all is well with the phone then I'll need to return it back otherwise I'll get charged for it.
The second option is sending it in for a repair at a local authorized repair center. Luckily there is one 10-15 minutes away from me but the annoying thing is all bookings are available during my working hours but the place has 5* reviews and can get the phone repaired within the same day.
So I might just go for my second option tbh seems alot more convenient and less hassle of having to send a phone away to Google and wait 10 days for a repair which can be done within a day by a repair center that is less than 10 mins away from me and has all parts available to hand out.
Btw the repair center near me is called Ismash. There's one nearby me in London.
Awesome news! There are at least a handful of other users who have reported getting bricked since Android 13 came out August 15th, and I believe all of them reported good news from Google for repairs, but I don't have any idea if any of them were in the UK, so glad it's going to work out there too.
Tombo12 said:
Some News for everyone!
So I spoke to Google and they was fine about it phone not working went through some troubleshooting tricks neither of the options worked. The rep on the phone gave me two options Send it into Google for a repair and they'll send me over a replacement 6 Pro whilst its being worked on. If they can't fix it they'll let me keep the phone but if all is well with the phone then I'll need to return it back otherwise I'll get charged for it.
The second option is sending it in for a repair at a local authorized repair center. Luckily there is one 10-15 minutes away from me but the annoying thing is all bookings are available during my working hours but the place has 5* reviews and can get the phone repaired within the same day.
So I might just go for my second option tbh seems alot more convenient and less hassle of having to send a phone away to Google and wait 10 days for a repair which can be done within a day by a repair center that is less than 10 mins away from me and has all parts available to hand out.
Btw the repair center near me is called Ismash. There's one nearby me in London.
Click to expand...
Click to collapse
Great to hear! If you end up taking it to the repair shop, please let us know what repairs they did (I'm guessing replacing the motherboard) and what they said was wrong with it (e.g. If it was an eFuse problem). Thanks and good luck!
Lughnasadh said:
Great to hear! If you end up taking it to the repair shop, please let us know what repairs they did (I'm guessing replacing the motherboard) and what they said was wrong with it (e.g. If it was an eFuse problem). Thanks and good luck!
Click to expand...
Click to collapse
i am also very curious if it actually needs a motherplace replacement or simply a reflash using a JTAG (or similar specialized tool) to get it out of the bricked state.
Tombo12 said:
I'm kinda screwed here and I really really need some help.
So I basically rooted my Pixel 6 Pro just out of boredom and wanted to tweak some stuff with the rooted version. In the end, I decided that it wasn't worth rooting as most things i can do i could already do on stock like customization and other things. Anyway long story short I've tried to Use the google flash recovery tool I wasn't looking where i was clicking and ended up flashing 12 by accident It *Was on 13 at the time* had it got near to the end but it kept booting me to this one section called "fastbootd" I hit factory reset and from there it done the reset and now the phone no longer starts or doesn't even displays the charging percentage.
I've plugged it into a computer nothing pops up no noise from my computer to say it has connected.
I've also tried to use power + down for 30 seconds - didn't do nothing.
Has anyone got out of this issue? Is this a Hard Brick?
I've plugged it into a charger and will see what happens tomorrow. I genuinely think its the battery has fully drained.
Cause I've ran out of ideas to try things and I need your expertise on this guys.
Your help will really be appreciated.
Click to expand...
Click to collapse
My 6 pro did this last weekend, when I was rooted I decided to flash a file to change the font and I missed the part it would work on 13 as long I deleted a certain file for the lock screen, it boot looped a few times, apparently it tried to load from slot B where android 12 was still flashed, and it hard bricked, no button combo would work, completely bricked, it was fully charged when this happen, so I RMA`d with google and my old device is suppsoed to be delivered to Texas today, then hopefully tomorrow my if I`m lucky that my replacement gets shipped.
2015Ducatimulti said:
My 6 pro did this last weekend, when I was rooted I decided to flash a file to change the font and I missed the part it would work on 13 as long I deleted a certain file for the lock screen, it boot looped a few times, apparently it tried to load from slot B where android 12 was still flashed, and it hard bricked, no button combo would work, completely bricked, it was fully charged when this happen, so I RMA`d with google and my old device is suppsoed to be delivered to Texas today, then hopefully tomorrow my if I`m lucky that my replacement gets shipped.
Click to expand...
Click to collapse
Great. If you try again to be on the safe side, download this app and install font manager
GitHub - Fox2Code/FoxMagiskModuleManager: A module manager for Magisk because the official app dropped support for it
A module manager for Magisk because the official app dropped support for it - GitHub - Fox2Code/FoxMagiskModuleManager: A module manager for Magisk because the official app dropped support for it
github.com
Just use termux and type
Code:
su -c manage_fonts
Tbh I'm not 100% it works on A13, but I tried it on the a13 beta and it worked.
verszipo said:
i am also very curious if it actually needs a motherplace replacement or simply a reflash using a JTAG (or similar specialized tool) to get it out of the bricked state.
Click to expand...
Click to collapse
I can almost 100% guarantee that they fix it through the USB port. When its going into the bricked mode, it is no doubt going into a special recovery mode that isn't documented publicly.
96carboard said:
I can almost 100% guarantee that they fix it through the USB port. When its going into the bricked mode, it is no doubt going into a special recovery mode that isn't documented publicly.
Click to expand...
Click to collapse
bro any idea how to alive again with usb port even hard brick and show only usb serial port
Any update? I have the same issue, anti-rollback has caused my phone to become soft bricked and experiences WebView crashes, along with other problems.
Lughnasadh said:
I assume you didn't flash, at the minimum , the A13 bootloader to both slots or sideload the OTA after updating to A13 before doing this? If not, sounds like your device may have reverted to the A12 slot and ended up a brick due to the new ARB/eFuse shenanigans. The symptoms you describe are what happens when this occurs.
Luckily, it sounds like Google has been good at replacing devices that have encountered this so I would RMA it.
Click to expand...
Click to collapse
What does RMA stand for??
liammmmnnnn said:
What does RMA stand for??
Click to expand...
Click to collapse
Return Merchandise Authorization.
Tombo12 said:
I'm kinda screwed here and I really really need some help.
So I basically rooted my Pixel 6 Pro just out of boredom and wanted to tweak some stuff with the rooted version. In the end, I decided that it wasn't worth rooting as most things i can do i could already do on stock like customization and other things. Anyway long story short I've tried to Use the google flash recovery tool I wasn't looking where i was clicking and ended up flashing 12 by accident It *Was on 13 at the time* had it got near to the end but it kept booting me to this one section called "fastbootd" I hit factory reset and from there it done the reset and now the phone no longer starts or doesn't even displays the charging percentage.
I've plugged it into a computer nothing pops up no noise from my computer to say it has connected.
I've also tried to use power + down for 30 seconds - didn't do nothing.
Has anyone got out of this issue? Is this a Hard Brick?
I've plugged it into a charger and will see what happens tomorrow. I genuinely think its the battery has fully drained.
Cause I've ran out of ideas to try things and I need your expertise on this guys.
Your help will really be appreciated.
Click to expand...
Click to collapse
When I bricked my device, I had to hold power + down or up, I don't remember, for like two minutes straight while it was connected to my pc, try