Database Users

[Q] Galaxy S4 Hard Bricked (I think)

Hi
I have a bit of an issue with my phone and hoping someone can help me out.
History
My phone screen has cracked and a repair centre showed me it is most likely due to my battery blowing out, so as my phone is still under warranty I have arranged for it to be returned to O2 to be repaired. However as I had it rooted and have had multiple ROMs installed, my counter is at 7, so needed to reset this and get the O2 stock ROM back on.
What I've done
I used Triangle Away to reset the counter, but this didn't seem to work, I chose the option to reset the counter, phone would reboot but not into Download mode, just straight back up to OS.
Used latest version of ODIN to flash the O2 stock firmware, this failed and phone switched off. Would not power back on.
Spent 4 hours with phone not able to power on in any way.
Eventually found the sofware referenced on Samersh(apologies) post re: recovery of phone, this allowed the phone to flash via USB and get me back to Download mode. I can then use ODIN to flash sotck firmware with a PIT file, this shows as succesfull, but on completion phone switches off and wont power back on.
I can repeat these steps over and over again, but each time ODIN flashes succesfully, but at the end phone powers off and wont power back on.
Can anybody shed any light on what I need to do to get my phone recovered, or have I lost it forever?
I appreciate any and all help you guys can give me as I am at a complete loss as to what to do.
Regards
grabrail

Buy a new battery. If your battery indeed blew out, then it's damaged. That's why you can't boot anymore.

Lennyz1988 said:
Buy a new battery. If your battery indeed blew out, then it's damaged. That's why you can't boot anymore.
Click to expand...
Click to collapse
The battery still works as I can boot after flashing with Legijas software, but only to download mode. After flashing with ROM it then reverts to a "Dead" status until flashing with Legijas software again.

Ok, then it's not your battery.
Flashing roms with a damaged battery is still not very smart.

Lennyz1988 said:
Ok, then it's not your battery.
Flashing roms with a damaged battery is still not very smart.
Click to expand...
Click to collapse
I know but to get a warranty repair and replacement battery I dont have much choice

It could be the battery. Try a new one.
Sent from my GT-I9505 using XDA Premium HD app

Obagleyfreer said:
It could be the battery. Try a new one.
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
Tried a new battery last night from a brand new i9505, no joy.
I have found a shop that may be able to J-TAG it for me so fingers crossed it will be ok.

Power won't turn on after flashing Alliance ROM. HELP PLEASE!!

So I had Alliance ROM on my phone to begin with and I downloaded this http://www.alliance-rom.com/communit...able-nd7.9054/ and installed it in safestrap recovery mode. After the file was finished installing the phone turned off. (I thought it was going to restart and well that never happened, The phone doesn't even turn on. I've taken the battery out and tried to power it on, I've tried taking the SIM and SDCard out and turning it on. I've left it plugged in and charging and tried turning it on, I'v plugged it into a computer and tried it that way. Nothing that I have tried has worked. If anyone can please help me get this working I would HIGHLY APPRECIATE IT!! I use this phone for work and to keep in touch with my Daughter. Thank you ahead of time for any ideas that may or may not work.

First thing, the link you posted doesn't work. There's dots in the middle. Second, if it won't even boot to the Galaxy S5 screen before the boot animation that could be one of two things. A. It installed a custom boot loader not meant for your device that could be fixed if you could boot to download mode, which you can't. Or b. your phone is physically broken and you'd need to take it to Verizon to get fixed. Right now it's probably the second, but I have little clue as to the ROM you installed.

This has been pretty much answered for you in your other thread. You put a rom meant for note 2 on your S5 , probably not going to be fixable. But your ONLY chance is to get the phone into Download mode. Then odin a stock S5 ROM. No longer any need to panic you have brick so...At this point remain calm and move slowly so you don't make another mistake hope you get lucky.

[Q] Jiayu S3 semi-hard brick (NOT BY FLASHING), help needed

Hi all,
Yesterday my Jiayu S3 crashed and rebooted, after setting an alarm clock and using the Spotify app. However, it did not reboot into the OS as usual. It did not even show the Jiayu logo, but the phone vibrated (sign that it's booting), screen turned on, phone turned off again, repeating this cycle over and over (not the traditional bootloop as I know it). I was running a rom based on the original rom, with some slight modifications. This rom was running stable for more than a week. I know my way around Android, and am used to switching roms, flashing etc.
Right away, I checked the following things:
- Battery removal didn't help (I did not forget to put it in again ofcourse )
- Phone doesn't go into it's charging cycle when charger is connected
- I do NOT have access to recovery
- I can, however, access the boot menu (Volume up + power key, options: Normal boot, recovery, fastboot)
- I can get into fastboot mode (haven't tested ADB yet), that's the only thing that's still working
I tried to flash the original firmware using SP flashtool, and I am still able to upload firmware on the phone! I am sure that I'm using the correct ROM, and tried different PC's and drivers. Got a few succesful flashes, but still bootlooping.
I also had the idea that my battery was empty (didn't charge it overnight), and measured the battery at 3.52 V. So it was pretty empty but not that empty that it doesn't boot. In an effort to charge the phone, I left it bootlooping for an hour or so, and later on it turned out that it only drained the battery further, 2.99 V.
I didn't want to kill this battery so I did use 2 other batteries from an old Jiayu G4, which appear to work if you turn them around and hold them against the pins (note: I knew what I was doing here ). After a lot of Googling, and seeing a lot of generic "how to fix any brick" stuff I was not able to revive my phone again.
I still believe (and hope) that the error is on the software side of the phone. All the partitions should be ok and in working order according to SP flashtool.
Now this is where my knowledge stops and where (hopefully) your help comes in. What can be corrupted that I haven't checked yet? Do you guys have any suggestions to revive this "high-end" phone again? Once again, it did not happen because of bad flashing or something like that, it happened randomly when I was using the phone normally. I tried to be as accurate as possible (long story), but if there are any questions I'm happy to answer them.
Any suggestion is welcome!
Thanks in advance.

Bump..
Anyone?

bump

system update, fully bricked

I've been using the stock rom on my phone for years, until after one update my wifi went incredibly choppy, so I tried rooting and LineageOS but experienced lots of other issues, so I reverted to the original stock rom.
I've stuck with 6.0 for over a year, unrooted, unspoilt, but I was constantly pestered with update notifications.
I accidentally hit 'Yes, I'm in' the other day and it downloaded the update, and the pestering went next level insane.
I'd hit dismiss and 5 seconds later - DO YOU WANT TO INSTALL THE UPDATE? It would reappear a minute later.
So I finally caved and just said yes, curious whether or not my wifi would suffer, figuring it might have been a bad update that caused my wifi issues which has since been fixed.
I installed the first update, which brought me to 6.0.1 I think, and then I installed the update to 7.0.
And then my phone died completely.
The only sign of life is when I plug it into the PC, the charging light blinks, but I don't even see a battery charging screen.
The screen has stayed black since, can't reboot into any mode.
What now?

https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016

hedgehog90 said:
I've been using the stock rom on my phone for years, until after one update my wifi went incredibly choppy, so I tried rooting and LineageOS but experienced lots of other issues, so I reverted to the original stock rom.
I've stuck with 6.0 for over a year, unrooted, unspoilt, but I was constantly pestered with update notifications.
I accidentally hit 'Yes, I'm in' the other day and it downloaded the update, and the pestering went next level insane.
I'd hit dismiss and 5 seconds later - DO YOU WANT TO INSTALL THE UPDATE? It would reappear a minute later.
So I finally caved and just said yes, curious whether or not my wifi would suffer, figuring it might have been a bad update that caused my wifi issues which has since been fixed.
I installed the first update, which brought me to 6.0.1 I think, and then I installed the update to 7.0.
And then my phone died completely.
The only sign of life is when I plug it into the PC, the charging light blinks, but I don't even see a battery charging screen.
The screen has stayed black since, can't reboot into any mode.
What now?
Click to expand...
Click to collapse
Does it vibrate or any other indication that the phone is trying to boot? Will it charge? needs to be at least 40% to recover. USB to ADB and see if the phone is recognized on a PC. Could be hard bricked ... there is one other mode that some phones use where the screen is black and the only way to talk to it is through a flashing tool. I apologize that I cannot recall the name of that mode but considering that Lenovo developed this phone it wouldnt surprise me if it was just in that mode, waiting for a boot load update of some kind. A lenovo flash program might be worth a try.

milesius said:
Does it vibrate or any other indication that the phone is trying to boot? Will it charge? needs to be at least 40% to recover. USB to ADB and see if the phone is recognized on a PC. Could be hard bricked ... there is one other mode that some phones use where the screen is black and the only way to talk to it is through a flashing tool. I apologize that I cannot recall the name of that mode but considering that Lenovo developed this phone it wouldnt surprise me if it was just in that mode, waiting for a boot load update of some kind. A lenovo flash program might be worth a try.
Click to expand...
Click to collapse
I eventually fixed it using adb following a set of unbricking instructions on XDA.
Sorry for not updating the thread.

SM-N910F no Boot, constant restarting!

Hello,
The phone was updated to latest available firmware. This is when the problems started.. First off it would turn off after about two minutes and get quite hot, so I replaced the battery.
After battery replacement, it worked OK for a few days, then started getting hot again.. So i pulled battery and left to cool.
Now the phone does not boot at all, constantly rebooting, even when plugging in the charger. Screen flashes with battery charge symbol then reboots. I can however get into Download Mode..
This is what i receive;
ODIN MODE (HIGH SPEED)
PRODUCT NAME:SM-N910F
CURRENT BINARY: Custom
SYSTEM STATUS: Official
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0x1 (4)
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1
SECURE DOWNLOAD : ENABLE
UDC START
I have no idea why it says Current Binary - Custom.. As far as I know the phone is Stock and I bought it new.
Hope someone can help me please!
Thanks!

*Update*
Played around with it this morning, managed to flash an older ROM in Download Mode... but upon reboot... stuck in bootloop
Any input how to get the phone working again please?
Much appreciated!

Bootlooping after flash the stock rom is to be expected sometimes.
What you have to do in that case, is boot in recovery (stock recovery) and perform a factory reset, then wipe user data and in the end REBOOT SYSTEM.
That may be caused by old data still in your phone, that prevent your phone from booting up.
I would also try and change my charger and cable, in case something in wrong there (apart from the batter) and the phone cannt charge it properly.
Even better, if you could use an external charger to charge your battery and then put battery back to it, just to make sure there is not something wrong in the charging process.
Have you tried to charge your phone, while be on RECOVERY? That could also help.
So, in conclusion
Make sure your battery is charged
Boot in stock recovery, factory reset and wipe data
reboot system.
Good luck

logosA said:
Bootlooping after flash the stock rom is to be expected sometimes.
What you have to do in that case, is boot in recovery (stock recovery) and perform a factory reset, then wipe user data and in the end REBOOT SYSTEM.
That may be caused by old data still in your phone, that prevent your phone from booting up.
I would also try and change my charger and cable, in case something in wrong there (apart from the batter) and the phone cannt charge it properly.
Even better, if you could use an external charger to charge your battery and then put battery back to it, just to make sure there is not something wrong in the charging process.
Have you tried to charge your phone, while be on RECOVERY? That could also help.
So, in conclusion
Make sure your battery is charged
Boot in stock recovery, factory reset and wipe data
reboot system.
Good luck
Click to expand...
Click to collapse
I flashed the Stock Firmware but upon reboot just back to bootloop... The only operation i can do is VOL Down + HOME + POWER to Download Mode
I am unable VOL UP + HOME + POWER.. it just reboots the phone!
Also battery does not seem to be charging while in the phone, because it turns itself on and then stuck in loop! so frustrating!
any more help appreciated?
Thanks !!

I have now managed to flash a Stock 4.4.4 firmware with Auto Reboot, F. Reset Time and NAND Erase All ticked... Still no joy!
Once the firmware is installed the phone reboots then back to bootloop

iamserver2016 said:
I have now managed to flash a Stock 4.4.4 firmware with Auto Reboot, F. Reset Time and NAND Erase All ticked... Still no joy!
Once the firmware is installed the phone reboots then back to bootloop
Click to expand...
Click to collapse
look what you have to do:
download this (windows ) application and install it on your windows pc.
This is the application that will allow you to search and download the latest stock rom for your phone.
It connect to Samsung servers and in very little time you will have a new stock rom on your pc.
choose samfirm 3.06
extract it on a folder on your PC and run samfirm.exe
in the opening menu type
SM-N910F(or T/V/W etc your phones model)
REGION..... xxx (your region code)
these 2 you can find in a sticker under your battery if you open the phone and take off the battery, if you already dont know that
tick '' BINARY NATURE''
(If you dont tick BINARY...'' you will get the whole stock rom in one file xxxx.tar.md5 to flash it in the oding using the AP tab)
CHECK UPDATES>DOWNLOAD
THIS WAY YOU WILL GET THE LATEST STOCK ROM FOR YOUR PHONE/REGION
Binary nature means the rom split in 4 files
1. BL- bootloader
2.AP - rom
3. CP - modem
4. CSC - Customer support code(region/country)
This is what a stock rom is consist of
this kind of rom is also called REPAIR ROM, because you can use it to repair your phone.
If you look in odin you will find exactly these 4 entries.
So you can put each in the appropriate box and flash them all and so have a stock rom.
UNtick autoreboot, tick NAND ERASE ALL
push start
Wait until rom flashes and ODIN SAYS COMPLETED
take off your battery and wait 2-3 seconds.
Put it back in and press and hold power+ volume UP + home
Wait untill see samsung logo appears but not let go buttons
AFTER Samsung logo goes and come again, let the buttons.
You will boot to stock recovery.
Navigate with volume buttons and perform FACTORY RESET and then Wipe user data
Then REBOOT SYSTEM.
PS make sure you have oding == or newer than 3.13.3
take it from here:
https://odindownloader.com/download/odin3-v3-13-3
*****DONT LAUGH ON THIS
before do all the above
TAKE OFF THE BACK COVER OF YOUR PHONE , your sdcard, your battery and sim
Put your phone in a zip bag and put it in your freezer for 5 minutes
Take it off the freezer, put battery and sim card on it and do what I have wrote above
Hopefully it will solve your problem and everything will go as we all wish to.

logosA said:
look what you have to do:
download this (windows ) application and install it on your windows pc.
This is the application that will allow you to search and download the latest stock rom for your phone.
It connect to Samsung servers and in very little time you will have a new stock rom on your pc.
choose samfirm 3.06
extract it on a folder on your PC and run samfirm.exe
in the opening menu type
SM-N910F(or T/V/W etc your phones model)
REGION..... xxx (your region code)
these 2 you can find in a sticker under your battery if you open the phone and take off the battery, if you already dont know that
tick '' BINARY NATURE''
(If you dont tick BINARY...'' you will get the whole stock rom in one file xxxx.tar.md5 to flash it in the oding using the AP tab)
CHECK UPDATES>DOWNLOAD
THIS WAY YOU WILL GET THE LATEST STOCK ROM FOR YOUR PHONE/REGION
Binary nature means the rom split in 4 files
1. BL- bootloader
2.AP - rom
3. CP - modem
4. CSC - Customer support code(region/country)
This is what a stock rom is consist of
this kind of rom is also called REPAIR ROM, because you can use it to repair your phone.
If you look in odin you will find exactly these 4 entries.
So you can put each in the appropriate box and flash them all and so have a stock rom.
UNtick autoreboot, tick NAND ERASE ALL
push start
Wait until rom flashes and ODIN SAYS COMPLETED
take off your battery and wait 2-3 seconds.
Put it back in and press and hold power+ volume UP + home
Wait untill see samsung logo appears but not let go buttons
AFTER Samsung logo goes and come again, let the buttons.
You will boot to stock recovery.
Navigate with volume buttons and perform FACTORY RESET and then Wipe user data
Then REBOOT SYSTEM.
PS make sure you have oding == or newer than 3.13.3
take it from here:
https://odindownloader.com/download/odin3-v3-13-3
*****DONT LAUGH ON THIS
before do all the above
TAKE OFF THE BACK COVER OF YOUR PHONE , your sdcard, your battery and sim
Put your phone in a zip bag and put it in your freezer for 5 minutes
Take it off the freezer, put battery and sim card on it and do what I have wrote above
Hopefully it will solve your problem and everything will go as we all wish to.
Click to expand...
Click to collapse
Thank you for your instructions and reply!! Unfortunately, this has not solved my issues with the phone. I am reluctant to try the freezer method tbh lol.
I might buy a new motherboard.

iamserver2016 said:
Thank you for your instructions and reply!! Unfortunately, this has not solved my issues with the phone. I am reluctant to try the freezer method tbh lol.
I might buy a new motherboard.
Click to expand...
Click to collapse
yes, I thought so.
I have been there you know.
I strangled almost a year trying to fix my damaged Note 4 (910f) which had the emmc bug.
Finally, although I did manage to flash arom (many actually), the only thing that solve the problem was to replace my motherboard.
Take look to some extremely actions, until motherboard replace, just to have an idea what we are talking about.
Its hard, its not 100% effective, but since your phone is still managing to even power up and go to recovery, or download mode, its not that damaged my mine was.
Also keep in mind, this is temporary, eventually, emmc will be complete damage(depending of the use), so motherboard will be to permanent solution only
Good luck my friend
https://forum.xda-developers.com/no...ebrick-img-t3488114/post71178231#post71178231
https://forum.xda-developers.com/note-4/help/note-4-freezing-restarting-t3348821
https://forum.xda-developers.com/no...ebrick-img-t3488114/post71184710#post71184710

logosA said:
yes, I thought so.
I have been there you know.
I strangled almost a year trying to fix my damaged Note 4 (910f) which had the emmc bug.
Finally, although I did manage to flash arom (many actually), the only thing that solve the problem was to replace my motherboard.
Take look to some extremely actions, until motherboard replace, just to have an idea what we are talking about.
Its hard, its not 100% effective, but since your phone is still managing to even power up and go to recovery, or download mode, its not that damaged my mine was.
Also keep in mind, this is temporary, eventually, emmc will be complete damage(depending of the use), so motherboard will be to permanent solution only
Good luck my friend
https://forum.xda-developers.com/no...ebrick-img-t3488114/post71178231#post71178231
https://forum.xda-developers.com/note-4/help/note-4-freezing-restarting-t3348821
https://forum.xda-developers.com/no...ebrick-img-t3488114/post71184710#post71184710
Click to expand...
Click to collapse
Thanks for replying again and with all the help/knowledge! :good: much appreciated!!
I am currently trying the freezer method but only with battery? Does it have to be full device?
Next stop, new motherboard... I feel defeated.
Thanks!

iamserver2016 said:
Thanks for replying again and with all the help/knowledge! :good: much appreciated!!
I am currently trying the freezer method but only with battery? Does it have to be full device?
Next stop, new motherboard... I feel defeated.
Thanks!
Click to expand...
Click to collapse
you have to freeze the phone.
Not battery, not sim card, not sdcard.
The thing is that in Note 4, CPU and emmc are one under the other, so overheating of the CPU, trying to flash the emmc, is making their contacts lose, so flashing is failing.
Keeping the phone cold, dont let that happen and eventually(maybe), flashing and booting up, which is the most heat producing process, completes and then phone can continue easier.
As I have already told you, this is a big MAYBE and not a final solution.
Changing the motherboard will be.
Took me 15 days to manage to boot it up for the first time.
Manage to keep it with broken motherboard almost a year, then one day, I saw smoke coming out of the usb when charging it. That was the end.
New board and charging port has made my Note 4 like new.