Symptoms: Over a period of weeks, possibly months, the phone started rebooting itself more and more frequently. Now I have reached the point where my phone bootloops, often at the Note II logo, sometimes it goes on and gets stuck on the ROM's logo for ages then bootloops again. Occasionally after an age (hours) and if I am lucky the ROM may load up but then it soon starts bootlooping again. I also noticed that one time there was some graphical distortion on the ROM's animated logo. TWRP Recovery and Download Mode both work perfectly fine.
What I have done Wiped everything, reinstalled the ROM through recovery which achieved nothing. I then tried a fresh install of the stock ROM with ODIN (update bootloader ticked). Although the ODIN install went fine, I still have exactly the same problem.
What should be my next step? Repartion with PIT?
Well I went ahead and re-partitioned with a PIT file, still no luck. I guess this must be a hardware issue.
makeyourself said:
Well I went ahead and re-partitioned with a PIT file, still no luck. I guess this must be a hardware issue.
Click to expand...
Click to collapse
You have what is known as Sudden Death Syndrome (SDS). In short the eMMC chip has failed. It or the motherboard needs to be replaced.
Flashing PIT will not help
Sorry about that
Check battery , update phone software .go to a repair centre , u may fry it like me .
Sent from my GT-N7100 using XDA-Developers mobile app
Related
Hi there,
I am going crazy over my wife her Note2. Last night it suddenly rebooted itself and got stock on bootscreen. it was in the middle of the night and connected to the charger. I tried to restart, I tried pulling the battery out and then restart, I tried flashing stock rom. Nothing. I can't get into recovery, I can get in download mode but it won't flash anything. It says that it is missing PIT and odin gives a big red FAILED. But when I flash stock ROM with PIT file it won't flash, even after 3 hours nothing happened. What can I do?
It can't damage the PIT partition by itself.
I had the same missing PIT problem on my old Galaxy Player 5.0 because i entered a Motorola partition code in the Terminal Emulator (Don't ask why....LMAO)
Yeah i couldn't fix it and i got a replacement.
Maybe check the symptoms of an Insane chip,some Note 2's have a hardware issue, maybe the Insane chip became "Insane" ? lol
Hi,
This morning I woke up to see my phone seemingly booting up but after a few minutes I realised that it was stuck on the boot screen. I can only assume something hardware or software related messed up while I was sleeping and now after reading a few threads I am very scared that my phone could possibly be bricked.
First up, I updated to 4.3 from 4.1.2 about 3 weeks and it has been running fine albeit a few annoyances at the new firmware Samsung deployed. To get root I had to install philz_touch_5.11.2 recovery through ODIN and then go into my new recovery to install root through Dr Ketan's Multi Tool which seemed to work well with no problems, it was quite flawless through the whole update. But now I guess something has happened to my phone and that has changed. When I saw it was stuck, I thought that it would be possible to just reflash to stock firmware and that would fix it. It was working up until the point ODIN got "cache.img" which failed the install. Now, I exited ODIN since it didn't work and restarted my phone and tried to flash the stock 4.3 ROM again. This time, immediately I got a screen telling me that there was "no PIT partition"
(Look at the attachment for the screen, I am new so no outside links)
and now I am getting the message on my phone after restarting "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I am now downloading Kies to try this but does anyone have any suggestions or solutions?
GoonReb0rn said:
Hi,
This morning I woke up to see my phone seemingly booting up but after a few minutes I realised that it was stuck on the boot screen. I can only assume something hardware or software related messed up while I was sleeping and now after reading a few threads I am very scared that my phone could possibly be bricked.
First up, I updated to 4.3 from 4.1.2 about 3 weeks and it has been running fine albeit a few annoyances at the new firmware Samsung deployed. To get root I had to install philz_touch_5.11.2 recovery through ODIN and then go into my new recovery to install root through Dr Ketan's Multi Tool which seemed to work well with no problems, it was quite flawless through the whole update. But now I guess something has happened to my phone and that has changed. When I saw it was stuck, I thought that it would be possible to just reflash to stock firmware and that would fix it. It was working up until the point ODIN got "cache.img" which failed the install. Now, I exited ODIN since it didn't work and restarted my phone and tried to flash the stock 4.3 ROM again. This time, immediately I got a screen telling me that there was "no PIT partition"
(Look at the attachment for the screen, I am new so no outside links)
and now I am getting the message on my phone after restarting "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I am now downloading Kies to try this but does anyone have any suggestions or solutions?
Click to expand...
Click to collapse
Update: I spent the past two days trying to solve this and I'm at a standstill in progress. It seems that my phone was one that suffered SDS with a corrupt eMMC chip so I've lost both my firmware and recovery but I can still get into Download mode. It also seems like I have lost my PIT table and I am just completely unable to flash the PIT file back to the phone for some reason. Does anyone have any ideas on how I could just factory reset my phone or reinstall my partition table so that i can get a simple recovery installed? Please help
Exact same issue!
I know exactly what you are going through!
My phone did the exact same thing back in June. It downloaded the firmware update over wifi, then when it went to install, it restarted to the boot logo, and went no further. I had left it for a number of hours, so time doesn't seem to make any difference.
I've been working on it since the end of July, and haven't been able to find a solution yet.
dkinniburgh said:
I know exactly what you are going through!
My phone did the exact same thing back in June. It downloaded the firmware update over wifi, then when it went to install, it restarted to the boot logo, and went no further. I had left it for a number of hours, so time doesn't seem to make any difference.
I've been working on it since the end of July, and haven't been able to find a solution yet.
Click to expand...
Click to collapse
Yeah, it doesn't seem like time would fix it, so frustrating. Right now I am getting the glass of my Note replaced (it has a slight crack) which apparently voids my warranty when I went into my carrier to organise a replacement. After it's repaired I will take it to another store and try to get it sent off to Samsung, hopefully they are understanding about it and will honour their warranty end as I do believe it was SDS so it would be their fault for using faulty eMMC chips. The only thing I wish I could do it just start over, flash the PIT file so I can just install CWM to see if any of my files are still there. I just want some peace of mind and it seems impossible at this point. I guess it is impossible to flash a PIT when the storage chip is corrupt, sucks to lose all my messages and data, just wish I had a backup in place but it is a good learning experience for the next time I have a functioning phone.
GoonReb0rn said:
Yeah, it doesn't seem like time would fix it, so frustrating. Right now I am getting the glass of my Note replaced (it has a slight crack) which apparently voids my warranty when I went into my carrier to organise a replacement. After it's repaired I will take it to another store and try to get it sent off to Samsung, hopefully they are understanding about it and will honour their warranty end as I do believe it was SDS so it would be their fault for using faulty eMMC chips. The only thing I wish I could do it just start over, flash the PIT file so I can just install CWM to see if any of my files are still there. I just want some peace of mind and it seems impossible at this point. I guess it is impossible to flash a PIT when the storage chip is corrupt, sucks to lose all my messages and data, just wish I had a backup in place but it is a good learning experience for the next time I have a functioning phone.
Click to expand...
Click to collapse
I was lucky having most of my info already backed up. I also had just upgraded another line, so I had a new phone to work with. It just sucks having to switch everything over to a new phone, reloading all the apps etc.
Hello,
My gf s4 mini is having some strange problems.
First it suddenly shutted down and doesn't give any signs of live, so I maked debrick sdcard and it booted, showing that there is something wrong with mmc.
Tried to flash with odin, but it failed... so left it for some time. When i tried another time it booted and showed s4 mini boot logo, so i wanted to flash it with stock firmware.
Progress bar is moving to end, Odin display: PASS! and then it is rebooting and not booting.
I tried booting recovery, and it shows twrp and rebooting about 5sec after showing twrp logo.
So i repeated this process and it still shows twrp logo...
I haven't seen something like this, so there is my question:
Is there something I can do, cause i read lots of threads and nothing works?
I guess it is dead mmc chip, but maybe i'm wrong and there is some solution.
Thanks in advance!
refresh
Maybe you can try jtag. But if your phone's warranty still continues, I recommend you give it Samsung service
Sorry for my bad English
Sent from my GT-I9190 using Tapatalk
Hi everyone I'm hoping someone can help. My note 7 had the boot loop. I was stuck in recovery mode and had DM verity and failed to set up dirty target errors. Smart switch wouldn't recognise my phone to do an emergency firmware recovery. I tried to reflash firmware using Odin and had no joy. Kept trying and eventually got it to flash. It died right at the end of the flash and I got a green screen saying the firmware failed to install and to do an emergency firmware recovery. At least now smart switch found my phone so I did the recovery. After it had taken hours to download it flashed 100℅ on the pc but when the phone rebooted and I got the little android dude saying installing new firmware. The counter on the phone started going up but jumped to 32% from 25℅ then stopped. Then said erasing rebooted and was back stuck in recovery but with just the DM verity error. If I flash the AP through Odin the exact same thing happens. Fails at 32℅ then does the same. Is there anyone come across anything similar or any suggestions? I I'd really appreciate it thanks.
zanderswigan said:
Hi everyone I'm hoping someone can help. My note 7 had the boot loop. I was stuck in recovery mode and had DM verity and failed to set up dirty target errors. Smart switch wouldn't recognise my phone to do an emergency firmware recovery. I tried to reflash firmware using Odin and had no joy. Kept trying and eventually got it to flash. It died right at the end of the flash and I got a green screen saying the firmware failed to install and to do an emergency firmware recovery. At least now smart switch found my phone so I did the recovery. After it had taken hours to download it flashed 100℅ on the pc but when the phone rebooted and I got the little android dude saying installing new firmware. The counter on the phone started going up but jumped to 32% from 25℅ then stopped. Then said erasing rebooted and was back stuck in recovery but with just the DM verity error. If I flash the AP through Odin the exact same thing happens. Fails at 32℅ then does the same. Is there anyone come across anything similar or any suggestions? I I'd really appreciate it thanks.
Click to expand...
Click to collapse
I'd advise you to take it back to Samsung and enroll for the recall. Regardless of the combustible battery, This is one of the primary reasons why they initiated the recall. This cannot be resolved even at Samsung service centre. So call Samsung and hand it over to them for recall.
I had the same issue. Couldn't recover.
Yup the recall is the perfect opportunity to save yourself from disaster.
Sent from my Nexus 5X using Tapatalk
Yeah that's what I thought. I'm already enrolled but now they say my carriers handling it. Just thought I'd throw it out there just to see if anyone's had the issue with getting stuck at the same percentage each time. I was doing my best to get it running as itll be at least a couple of weeks for a replacement they say. Knowing my carrier it's probably going to be months. May end up just getting something else it's a shame because when it worked it was great but they've done such a terrible job of getting it ready for general release. Thanks anyway bud.
Are you using the original or at least a high quality cable? Have you tried different USB port on PC? Even try a different PC. Also, try a slightly older version of Odin. If any of these make a difference, you at least have an indication that its worthwhile to keep trying.
Sent from my SM-N930T using Tapatalk
Hello and sorry if this is the wrong category...
It's my first time making a thread on xda.
I've been looking for an answer for the past 2 hours, but I still have a bricked phone... As the title says, I can't enter the recovery mode anymore. I tried to do a factory reset (when I could enter the recovery mode) and the phone got stuck at erasing. Now I can't enter the recovery mode anymore. I downloaded a new firmware from sammobile for the SM-G925F. The firmware works since I used it on an other phone and everything worked just fine. The problem is, when I open Odin and add the .tar file to AP, it gets stuck at nand write and sometimes on boot.img. The phone isn't showing that it's downloading anything (it has no progress bar). At this point I have no idea what to do...
Some extra info that could be helpful:
The phone was bootlooping when I got to fix it;
I work in a kind of phone repair store where customers bring their phones for hardware and software repair. I do the software;
I've installed new firmwares on multiple phones and I never had something like this... Normally some time with google and xda could help me to find a working way to fix the problem, but as I said... I've been looking for 2 hours and the problem is still here;
I'm not a pro with Android and phones. I just like to learn new things and I'm still learning.
Could it be a hardware problem?
Can you show me your phone's download mode image to see where could be the problem?
Also, make sure you are flashing latest firmware, if you are downgrading it - than you will get such boot errors.
*Update*
I found out what was wrong. The eMMC chip was broken.