I tried factory reset+cache wipe, smart switch emergency recovery, flashing rom with odin but I'm still getting this inexplicable boot loop that started on its own. Also tried TWRP wipes but those didn't help either. How can I even begin to troubleshoot this or possibly get a fix?
It sounds like you have an issue with the memory chip on your motherboard.
Since all the conventional methods failed, you will need to take to a cell shop that has professional equipment to try and restore it.
If they cannot do it then you need to replace the motherboard through samsung.
Related
noob help!
so i was just charging my phone. then all of a sudden my phone froze.
restarted it, then its just stuck at the htc logo. then the jetplane sound from the at&t intro.
tried doing a hard reset or entering recovery but after it reboots, still gets stuck at the htc logo.
(MORE INFO: im not sure if my phone is still rooted because i restored it my at&ts factory rom,cant change settings for usb debugging coz i ant get inside my phone,i still have my nandroid backups in my memory card from before)
is there anyway i could fix this? thanks in advance.
Try booting into recovery and deleting cache, reboot. If it still gets stuck, then try again, this time deleting user settings. If all else fails, restore your nandroid backup or restore the factory rom. If the problem is the rom, try flashing the RUU.
phone gets stuck at the htc screen when i choose recovery mode. also when i clear data.
tried re-flashing the phone with the stock rom from htc's website. it says its successful but still.. stuck at the htc startup screen.
if u flashed the factory rom back on it, then clockwork is gone is probably gone now. It most definitely is not rooted anymore either. Have you tried to reroot the phone?
rcmmartinez said:
phone gets stuck at the htc screen when i choose recovery mode. also when i clear data.
tried re-flashing the phone with the stock rom from htc's website. it says its successful but still.. stuck at the htc startup screen.
Click to expand...
Click to collapse
That was an un-wise decision to put the stock rom back on. Like stated above. Try a Re-Root. Then flash a CUSTOM ROM to your phone. If this doesn't work. Sounds like you are S.O.L.
A friend has given me his N4 in an attempt to fix it, seemingly the problem was caused with him doing a factory reset. It's possible the battery went flat during.
The phone gets stuck at the boot logo and will not factory reset from recovery mode. I can unlock the phone but any attempt to flash the stock image will result in the phone re-locking itself a few seconds later and the flash then begins to fail. Very odd.
Any ideas where to go next?
Thanks
Sounds like it could be faulty motherboard, bootloader not unlocking properly is a common symptom.
Sounds like bad emmc, hardware issues. You will have to replace the device.
Sent from my Nexus 4 using XDA Free mobile app
Before replacing anything I would suggest to update your recovery and try flashing again
And don't forget to wipe the system partition.
I'm guessing it's called boot loop from research over the past few hours. I switch it on, it loads the logo and phone introduction screen, the screen goes dark, it resets and then repeats. Charges fine, works without charger. I've tried lots from Google results like take out battery, soft and hard reset, recovery boot screen: clear cache, factory reset. I've even tried installing TWRP and rooting via odin which was successful, computer recognised it via USB. I then tried installing a custom ROM and gapps which was also successful but still have boot loop issue.
Possible water damage, if so what part will be faulty?
Piest4r said:
I'm guessing it's called boot loop from research over the past few hours. I switch it on, it loads the logo and phone introduction screen, the screen goes dark, it resets and then repeats. Charges fine, works without charger. I've tried lots from Google results like take out battery, soft and hard reset, recovery boot screen: clear cache, factory reset. I've even tried installing TWRP and rooting via odin which was successful, computer recognised it via USB. I then tried installing a custom ROM and gapps which was also successful but still have boot loop issue.
Possible water damage, if so what part will be faulty?
Click to expand...
Click to collapse
Might as well be the typical emmc failure.
bmwdroid said:
Might as well be the typical emmc failure.
Click to expand...
Click to collapse
Thanks for your response. What is emmc failure and can it be fixed with either software or hardware?
I know I could Google, but I thought I'd open up a conversation.
Piest4r said:
Thanks for your response. What is emmc failure and can it be fixed with either software or hardware?
I know I could Google, but I thought I'd open up a conversation.
Click to expand...
Click to collapse
It's a hardware failure were the soldered pins of chips loose connections to the mainboard.
Several threads discus this for instance here:
https://forum.xda-developers.com/note-4/help/100-fix-galaxy-note-4-emmc-error-random-t3859448
Some say it can be repaired permanently others deny that.
A couple of days ago. I wanted to check my phone in the morning and it started boot looping when I pressed the power button. Then, after a couple of boots it went into the TWRP recovery. I wiped cache/dalvik in hopes of a quick fix but still boots into recovery.
I can also go into the bootloader but the bootloader is completely unresponsive. It just gets stuck on the "barcodes" option, the volume keys do nothing and adb doesn't see my device when it's in the bootloader. I also tried re-flashing the same ROM I'm using(within recovery) to no avail.
I still intended on using this thing for a couple more years (I have a couple of spare OEM batteries and a spare chasis). Really appreciate any help.
Recovery.log from TWRP
Any flash drive can become corrupted.
Boot loops are commonly caused by poorly coded apps like launchers and power management apps.
Rootkits are always suspect with abnormal boot ups and unstable operation when no other cause can be found.
On a stock Android a factory reset or in extreme cases a firmware reflash will resolve it unless it's a hardware failure which is rare*. Be careful what you flash, install and download... always.
*a drop, water exposure or a ESD event when repairing a phone can cause this... sometimes not immediately.
blackhawk said:
On a stock Android a factory reset or in extreme cases a firmware reflash will resolve it unless it's a hardware failure which is rare*. Be careful what you flash, install and download... always.
Click to expand...
Click to collapse
Can I reflash firmware without the download mode working properly?
Sorry, way beyond my skillset...
Hi!
I used my S7 Edge for a couple of years and now I am afraid it may have died on me. As always, backups of f.e. pictures are not up to date.
During the night, it lay on my Qi charger. When I took it in hand, the screen was extremely dark and stuck in the "loading Lineage" screen. I tried to reboot. It was stuck on the "Samsung Galaxy" screen.
I wanted to boot into recovery and wipe the cache and see if it works again. But I can't boot into recovery mode. No matter if I connect it to a USB cable, the button command does not work.
Switching the device off also isn't possible. The only way to switch it off is disconnecting the battery (I have opened it to do so).
The only thing I can do is booting into download mode (so I know my volume up button works...).
Several times the screen was stuck on the "empty battery" symbol - which did not change no matter how long I had it in the charger. I can't really replicate how I got to the battery screen. I installed another battery just to see if if by some magic this would change something, but nothing changed about my issue. No boot possible and no booting into recovery.
I thought to myself: Well, maybe if I reinstall TWRP I can get into Recovery again. But when I try Odin I get the error message: "there is no PIT partition"
I know you will want additional info:
sadly, I cant' say which version of lineage I had running. I would have to look into my phone - which I can't.
I installed Lineage a couple of years ago, the phone was rooted and had TWRP recovery. I changed my USB port and Audio port several months ago.
But everything was running fine - I did not change or do anything recently. It happened overnight.
Do you have any ideas what I can do? I am brooding for two days now over this issue and I am at the end of the line here.
Did my memory just die on me? Is it an unfixable hardware issue?
Or software-related and potentially salvageable?
thanks in advance for anybody that bothers with my problem.
PinkElf said:
Hi!
I used my S7 Edge for a couple of years and now I am afraid it may have died on me. As always, backups of f.e. pictures are not up to date.
During the night, it lay on my Qi charger. When I took it in hand, the screen was extremely dark and stuck in the "loading Lineage" screen. I tried to reboot. It was stuck on the "Samsung Galaxy" screen.
I wanted to boot into recovery and wipe the cache and see if it works again. But I can't boot into recovery mode. No matter if I connect it to a USB cable, the button command does not work.
Switching the device off also isn't possible. The only way to switch it off is disconnecting the battery (I have opened it to do so).
The only thing I can do is booting into download mode (so I know my volume up button works...).
Several times the screen was stuck on the "empty battery" symbol - which did not change no matter how long I had it in the charger. I can't really replicate how I got to the battery screen. I installed another battery just to see if if by some magic this would change something, but nothing changed about my issue. No boot possible and no booting into recovery.
I thought to myself: Well, maybe if I reinstall TWRP I can get into Recovery again. But when I try Odin I get the error message: "there is no PIT partition"
I know you will want additional info:
sadly, I cant' say which version of lineage I had running. I would have to look into my phone - which I can't.
I installed Lineage a couple of years ago, the phone was rooted and had TWRP recovery. I changed my USB port and Audio port several months ago.
But everything was running fine - I did not change or do anything recently. It happened overnight.
Do you have any ideas what I can do? I am brooding for two days now over this issue and I am at the end of the line here.
Did my memory just die on me? Is it an unfixable hardware issue?
Or software-related and potentially salvageable?
thanks in advance for anybody that bothers with my problem.
Click to expand...
Click to collapse
Hi, try to flash the stock firmware otherwise I really don't know :/
I guess I will lose my data when I install stock firmware, don't I?
What I ask myself is: Is the reason for not being able to boot into recovery that my device always thinks my battery is empty?
Is the fact that I can boot into download mode a sign that my memory and/or motherboard is still intact?
PinkElf said:
I guess I will lose my data when I install stock firmware, don't I?
What I ask myself is: Is the reason for not being able to boot into recovery that my device always thinks my battery is empty?
Is the fact that I can boot into download mode a sign that my memory and/or motherboard is still intact?
Click to expand...
Click to collapse
Are you using Lineage OS? If yes, then definitely yes. On my Xiaomi, I couldn't get into fastboot mode or into recovery, I don't know why and somehow I got there, I don't even know how I think I held the power mode for a long time and when the phone turned on I held the volume up button to get into recovery finally succeeded on the umpteenth attempt and from recovery I restarted the phone in fastboot mode and flashed the stock firmware. And yes, being able to boot your phone into fastboot is a good sign. It would be worse if it wasn't possible.
I am still stuck with the problem. I can boot into download mode. I can't find a way to boot into recovery.
Is there anything I can do in download mode?
If I find the lineage version I originally installed on my device, could I install it via ODIN and get my phone back without data loss? I have only ever installed ROMs via TWRP.
Just an idea, but as of now I get the error "could not find PIT partition" anyway while trying to reinstall TWRP.
PinkElf said:
I am still stuck with the problem. I can boot into download mode. I can't find a way to boot into recovery.
Is there anything I can do in download mode?
If I find the lineage version I originally installed on my device, could I install it via ODIN and get my phone back without data loss? I have only ever installed ROMs via TWRP.
Just an idea, but as of now I get the error "could not find PIT partition" anyway while trying to reinstall TWRP.
Click to expand...
Click to collapse
Yes, you can use download mode to install the firmware via Odin. Look
That means giving up hope for my personal data...
But even if I want to do this, I run into the problem, that I can't install anything due to "could not find PIT partition"...