Did I just hard brick my phone? - X Play Q&A, Help & Troubleshooting

Hey, I was running Lineage OS 14.1 and then decided to go back to Stock because of network & Bluetooth issues. I flahsed the right stock rom 5.1 , it booted right on, did an OTA but the phone didn't turn on after that.
I tried Vol down + Pwr to boot bootloader, i tried to connect charger, connect to my laptop but the phone is just not responding to anything.

never downgrade it hard bricks, you can't do anything i think unless you have a jtag unit, you did an OTA and apparently it hard bricks the phone if you weren't on stock the whole time

Unfortunately you can downgrade it without problems only with de-bloated roms flashed from twrp

Related

Lenovo A6000 dead after an attempt to flash a ROM

I flashed Resurrection Remix a month ago in my 1GB ram variant, and everything was fine until, one day, when I was operating camera in my phone, the phone blacked out, and restarted, and when the screen showed pattern to unlock, and any attempt to unlock the phone would lead to immediate restart, and then after 4-5 attempts, the phone started to restart in frequent short intervals only showing android logo on the screen.
I decided to flash ROM again but this time stock ROM, but this phone has a great history of not entering into recovery mode no matter what I do. It enters only on its will. So, somehow I again flashed TWRP, and then tried flashing stock rom with QPST tool, but, when flashing finished, the phone as usually restarted, but only again to be stuck in boot loop. I again tried to flash it. But this time, after the full installation, the phone became dead. No matter what I do, the phone doesnt even turn on. No vibration, no lighting of screen, and even its not detecting on connecting to the PC.
What could be the problem? Anything related to hardware? Please help.
I suggest you to bring the phone to the service center
vaddadi9953 said:
I flashed Resurrection Remix a month ago in my 1GB ram variant, and everything was fine until, one day, when I was operating camera in my phone, the phone blacked out, and restarted, and when the screen showed pattern to unlock, and any attempt to unlock the phone would lead to immediate restart, and then after 4-5 attempts, the phone started to restart in frequent short intervals only showing android logo on the screen.
I decided to flash ROM again but this time stock ROM, but this phone has a great history of not entering into recovery mode no matter what I do. It enters only on its will. So, somehow I again flashed TWRP, and then tried flashing stock rom with QPST tool, but, when flashing finished, the phone as usually restarted, but only again to be stuck in boot loop. I again tried to flash it. But this time, after the full installation, the phone became dead. No matter what I do, the phone doesnt even turn on. No vibration, no lighting of screen, and even its not detecting on connecting to the PC.
What could be the problem? Anything related to hardware? Please help.
Click to expand...
Click to collapse
I think its hard bricked
https://forum.xda-developers.com/lenovo-a6000/how-to/guide-hard-brick-lenovo-a6000-t3581892
Use this

Moto g4 plus not booting up

Hey guys i had an invicta os rom . I wanted to go back to stock so i went back using a july 2016 stock firmware. It booted up and worked. Now i received nougat update. I downloaded and installed it. Due to some problem my phone is not booting. It is not even showing battery icon when charging. No response on cliking power and volume buttons for more than 120 seconds. When i connect the charger the indicator led flashes. That is all. What should i do????
Since no response on power and volume buttons i cannot go into bootloader and recovery also. Im suck on a black screen not change in color on charging. Only the led blinks when charger is connected... Pls help
By downgrading to stock Marshmallow from having stock Nougat, and then attempting to update via OTA, you've hard bricked. I warned about this in this post: https://forum.xda-developers.com/showpost.php?p=75033410&postcount=1166 Had you flashed the September 2017 stock ROM you would probably have been okay.
Effectively, by downgrading, you had a Marshmallow based system but a Nougat based bootloader (likely March/June/September 2017). By taking the OTA, you likely attempted to flash the December 2016 firmware update, including the bootloader, which corrupted your newer bootloader. Your device is showing the classic signs of being hard bricked from a corrupted bootloader, and I imagine if you connect your device to your computer, you'll see HS-USB 9008 or similar in Device Manager.
To rescue your device, you can try the blankflash and ROM here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
In future, do not flash older stock ROMs to your device (e.g. Marshmallow or old Nougat firmware), or if you do, do not accept OTA updates. Else the same thing will happen and then the blankflashes may not work, leaving you with an expensive paperweight (or very expensive repair).

S5 SM-901F Bootloop on device with Custom ROM

I flashed the ROM Ressurection Remix onto my phone to get a newer Android version since the model is quite old. Everything worked perfectly for over two years. Then while browsing, my phone crashed and got into a bootloop and restarts after showing the Samsung Logo. After manually removing the battery and putting it back repeatedly it boots up somehow. I couldn't reproduce what was happening back then.
After that it crashes in irregular intervals for no apparent reason and every time I could get it to boot properly by turning off and on for a long period of time.
Now I got the same problem and I wanted to get rid of the bootloop, so I decided to flash it with a new version of Ressurection Remix. I updated TWRP via Odin and had much trouble to get into recovery mode since my phone was crashing at the Samsung logo. As I got into recovery I made a factory reset and flashed the new rom. But as soon as my phone started to reboot after the flashing, it crashes again and the loop starts once again. Again, I searched for another Rom and used LineageOS but the problem persists.
Now I'm out of options, I can't even get into recovery mode by now.
Could anybody help me out?
Kolon22 said:
I flashed the ROM Ressurection Remix onto my phone to get a newer Android version since the model is quite old. Everything worked perfectly for over two years. Then while browsing, my phone crashed and got into a bootloop and restarts after showing the Samsung Logo. After manually removing the battery and putting it back repeatedly it boots up somehow. I couldn't reproduce what was happening back then.
After that it crashes in irregular intervals for no apparent reason and every time I could get it to boot properly by turning off and on for a long period of time.
Now I got the same problem and I wanted to get rid of the bootloop, so I decided to flash it with a new version of Ressurection Remix. I updated TWRP via Odin and had much trouble to get into recovery mode since my phone was crashing at the Samsung logo. As I got into recovery I made a factory reset and flashed the new rom. But as soon as my phone started to reboot after the flashing, it crashes again and the loop starts once again. Again, I searched for another Rom and used LineageOS but the problem persists.
Now I'm out of options, I can't even get into recovery mode by now.
Could anybody help me out?
Click to expand...
Click to collapse
Hey. I have same problem. I can just boot the Phone with bootloader. Anyone have an idea about this?

Stuck in logo after flashing stock. Can't boot into recovery. PC doesn't recognize.

So, I rooted and tried flashing the stock ROM (from Sammobile, same country, same exact model [SM-G950F], I already had the stock ROM and had never flashed anything else to the phone other than root, June security update, my phone had July's) to see if I could fix a problem that couldn't be fixed with any other method I had tried.
Everything in Odin seemed to go well, I got the PASS green box at the end. But then the phone couldn't go pass the Samsung logo when booting up. I left it quite a few minutes, before trying to boot into recovery mode and wiping data. Only to realize that I couldn't boot into recovery mode. In fact, I can't even turn the phone off. No combination of hardware keys works other than power button + bixby + vol down, to get into download mode. But that's of no use, because when I plug my phone into my PC (with the same cable and port I used before to root and flash the firmware into it) it is not recognized by Odin or the PC.
It just has the Samsung logo flashing slowly over and over because I can't turn the device off. By the time the battery dies out I'll most likely have the logo burnt into the display.
I also haven't been able to find any help online. Everyone's suggestion is “boot into recovery and wipe data”, but I can't do that.
Is my phone gone for good?

poco m3 not turning on

ok guys i know there are loads of threads about thois but ive got a slightly differen situation.
my daughter had this phone and then it suddenly tured off and wouldn't turn back on, i managed to get it to boot by disconnecting the battery and plugging it while holding the power down and reconnecting the battery which put me into fastboot then the boot to edl script made the phone boot. i have since unlocked the bootloader and flashed twrp and the reflashed the stock firmware which worked for a few hours but i tried to reboot it and now it wont boot, i can get to twrp but even if i flash the stock firmware it refuses to boot any idea on what i should do to try to get this phone to boot up?
Try to flash a custom rom, as far as i know this problem is caused by a MIUI update.
Joaoovn said:
Try to flash a custom rom, as far as i know this problem is caused by a MIUI update.
Click to expand...
Click to collapse
i have tried to flash a couple but every time i try it fails with error 7 and tried the normal fix but it doesnt help. then anything i do in twrp makes the system unmount and then it cant mount again. the only eay to get to get it to boot again is to take the back off and disconnect the battery and hold the power button down when i reconnect it but ive got no idea why it does this.

Categories

Resources