My note 4 was working fine (with Lollipop) until T-Mobile pushed the MM update. The device now has frequent restarts, random (frequent) freezes to the point that it has become unusable. It sometimes does not even restart unless I take the battery out and press the power button and try again - I have tried replacing the battery, using safe mode, doing a factory reset but the issue persists.
Now, I am getting the below kernel panic screen on bootups (2-3 times):
...
Kernel Panic
KRAIT INFO
Panic caler : ext4_handle_error+0x9c/0xac
Panic Msg :EXT-4-fs (device mmcblk0p26) : panic ext4_da_writepa
Thread : kworker/u8:32:9832
pm88841_rev :0x0
Wait...
Done...
UDC START
KERNEL PANIC UPLOAD MODE
...
Any indicators if it is related to improper install or is it related to any hardware failure - I am out of warranty and have no insurance for the device.
Related
Hi all, i installed the CM11 on my gf's Galaxy s3 (i9300 international version), the problem is that sometimes it randomly reboots and get stuck in an unusual bootloop. It reaches the bootsplash logo and it keeps rebooting, the only solution to get it back to work is to remove the battery for at least 30 seconds and try to turn it on, sometimes it works.
When the bootloop happens i'm not able to enter the recovery mode, because it just turns on and it keeps rebooting, same thing with download mode.
So, i'm new here, but i read about a common issue which is the sudden death syndrome and half-sds, it might be that? I checked and it has the insane chip.
Any advice/idea? It would be better to flash a stock ROM to be safe?
I would backup the whole device, recover initial firmware using kies emergency recovery mode and then start over again.
Had a similar problem but even worse: same bootloop, but no dice on recovery :\
Was unable to reflash or restore old firmware using Odin, Kies was the only thing that worked for me.
Nemed said:
Hi all, i installed the CM11 on my gf's Galaxy s3 (i9300 international version), the problem is that sometimes it randomly reboots and get stuck in an unusual bootloop. It reaches the bootsplash logo and it keeps rebooting, the only solution to get it back to work is to remove the battery for at least 30 seconds and try to turn it on, sometimes it works.
When the bootloop happens i'm not able to enter the recovery mode, because it just turns on and it keeps rebooting, same thing with download mode.
So, i'm new here, but i read about a common issue which is the sudden death syndrome and half-sds, it might be that? I checked and it has the insane chip.
Any advice/idea? It would be better to flash a stock ROM to be safe?
Click to expand...
Click to collapse
Do the reboots occure few seconds after pressing the power button?
I have exactly the same problem and I figured out that my power button is kinda stuck and thus permanently pressed.
This causes the permanent reboot, because holding the power button for a certain amount of time causes a reboot.
Try to push "Vol down"+"Homebutton" instantly after a reboot. If your galaxy enters the download mode (before rebooting again), you have the proof, that it's the fault of the power button due to the fact that pressing the power button would have been necessary.
I hope the fix will be for free under warranty.
At the first moment I also thought it would be the Sudden Death syndrom, but thankfully it's not the case and only the power button has to be fixed.
Togholl said:
Do the reboots occure few seconds after pressing the power button?
Click to expand...
Click to collapse
I don't know, i didn't paid attention to it. Anyway thanks to both of you for the replies, i'll check the power button as soon as possible since i don't have the phone with me right now. If that's not the cause, i think i'll do an emergency recover with kies as suggested by Cy4n1d3.
Now i still have a doubt, CM11 should have the fix for the sudden death syndrome merged into its code right? I'm asking this because if i'm right i could exclude sds as the cause of the problem...
Rebooting is not an SDS symptom, SDS is totally dead -suddenly.
Power button failure is diagnosed by inserting the battery, if it turns on by itself then button contacts are shorted out.
Your problem sounds more like corruption of the cache or dalvik, wipe and reflash your rom or go back to stock to test. Check MD5 of downloads and don't restore anything before you test.
Hi Guys,
I am having trouble with my i9505. When I am trying to boot it gets till the Samsung Logo and then nothing happens. Sometimes it reboots, sometimes the Display stays black. Sometimes it boots to the lockscreen and then reboots.
Here is what I tried to do:
- Factory Reset
- Flashing new Custom Rom
- Flashing Stock Rom via Odin I9505XXUFNB8 & I9505XXUBMGA (rooted and also not rooted)
- Flashing only Modem and Bootloader
- Flashing different Custom Recoverys and Stock Recovery
Sometimes I also can not boot into Recovery. I can always boot into Download Mode.
I already bought a new Battery (no changes). When charging the same behaviour.
ONE MORE THING: Phone always crashes seconds before getting to the lockscreen while booting! Is any hardware triggered in this moment (like a special ram, memory or something???)
So for people like me I want to start a threat concerning the most frequently HARD BRICKS.
I found nothing like this in any other threat so please do not close!
So i have a galaxy s5, was running Cyanogenmod 12
my phone was freezing and rebooting then eventually it was stuck and would only boot into download mode
so i cut my losses and flashed stock 4.2 and 5.1.1 (files from samMobile matched model number) and the problems persist
cleared cache and factory reset multiple times and booting in safe mode doesn't fix anything
the phone freezes on samsung splash screen usually mid animation, sometimes i get to tmobile screen when it freezes.
sometimes it will boot without any problems and work normally for a few seconds then freeze and shut off into the same loop
i have searched and can't find any advice past (flash stock and your good :good: )
oh and knox counter 0X1 (2) so no warranty for this guy.
anyone?
Hi team,
Mobile: samsung-sm-g530h
OS: default lollipop
Problem 1: will work for sometime normally after sometime phone is dead won't boot with power button, had to remove battery, and will start.
Problem 2: I just rooted using Odin was successful but currently it is not booting, Samsung logo comes and then everything is blank(backlit is still there).
Problem 3: mobile is heating abnormally.
My S7 edge had been acting weirdly for a few weeks, things like random restarts once a few days so I didn't pay much attention and over excessively heating up to 50/55 degrees (I usually checked the temperature through CPU_Z), and just a few hours ago I ran into problems like the phone restarting on its own, never getting past the samsung logo on boot, so I did the normal thing everyone else would do and just factory reset the device through recovery mode, a point to add here the device took an absolute age to load into recovery mode, this wasn't a case of bad key combination or anything like that, the device would load this the dmverity tree hash verification thing and sit there for a good 2-3 mins which is unusual, same thing happens with factory reset takes an absolute age and comes back with the following text-:
"E: format_volume: make ext4 failed on /dev/block/platform/155a0000.ufs/by-name/USERDATA with 1(I/O error)
-- Set Factory Reset done...
Data wipe failed."
booting up the device in this state would show up with an error "Device storage corrupt" with a " reset device" button in the bottom of the screen which didn't respond to any touches which was weird as well because holding the power button and then selecting the power off option worked with no issues so it wasn't an issue with the touchscreen.
searching for a solution on google led me to flash a official firmware that I downloaded from updato, just a heads up my device has never been tampered with or had any kind of software modifications this includes flashing any roms or even official firmwares before, so I download the firmware and flashed it as usual this is the firmware that I flashed through odin 3.12.3 firmware version was G935FOJV1DQAV also my device model is SM-G935FD while the firmware I flashed was for SM-G935F but this shouldn't be an issue because when I usually got updates over the air on the device they would be for SM-G935F so if there were any issues with this they should have popped up a long time ago, so everything went smoothly and the phone booted up again as usual, did the initial setup and adding accounts, recovery everything, hooked up the charger and left the phone to download all the necessary stuff through samsung and google cloud recovery, comeback after a few minutes to find that the device just wouldn't respond to the power button or the home button to wake the device up but the led on the phone was flashing in blue color which means I did receive some notifications, so I hard reset the phone by holding down power+volume down key, same issues pop up like before the firmware I flashed getting stuck on the boot samsung logo, went back to recovery to do another factory reset again it keeps freezing on the dm-verity tree hash thing, but this time the factory reset happens properly with no errors, but the device doesn't boot up at all, gets stuck on the samsung logo and the led on top starts flashing in several different colors, just like when you boot up a brand new S7 edge.
As a last ditch effort I try initializing the device through smart switch, everything goes normally but when the flashing process starts it gets stuck on 7% indefinitely, tried everything else but to no avail, tried flashing through odin again but it gets stuck on the same point as smart switch, tried installing the firmware in parts through odin again gets stuck on the same point when flashing AP but other parts get installed without any problems, download mode boots up fine, recovery mode now boots up very slowly with a dm-verity error "E:failed to mount / system (invalid argument).
I have 1 month warranty left on my S7 edge from where I purchased it, I want to send it back for a refund or a replacement but the only thing thats kind of worrying me is that in download mode the knox switch hasn't been tripped still shows 0 (0*000), but shows system status as custom, will this effect my warranty claim if they check my device?
TreekoX said:
My S7 edge had been acting weirdly for a few weeks, things like random restarts once a few days so I didn't pay much attention and over excessively heating up to 50/55 degrees (I usually checked the temperature through CPU_Z), and just a few hours ago I ran into problems like the phone restarting on its own, never getting past the samsung logo on boot, so I did the normal thing everyone else would do and just factory reset the device through recovery mode, a point to add here the device took an absolute age to load into recovery mode, this wasn't a case of bad key combination or anything like that, the device would load this the dmverity tree hash verification thing and sit there for a good 2-3 mins which is unusual, same thing happens with factory reset takes an absolute age and comes back with the following text-:
"E: format_volume: make ext4 failed on /dev/block/platform/155a0000.ufs/by-name/USERDATA with 1(I/O error)
-- Set Factory Reset done...
Data wipe failed."
booting up the device in this state would show up with an error "Device storage corrupt" with a " reset device" button in the bottom of the screen which didn't respond to any touches which was weird as well because holding the power button and then selecting the power off option worked with no issues so it wasn't an issue with the touchscreen.
searching for a solution on google led me to flash a official firmware that I downloaded from updato, just a heads up my device has never been tampered with or had any kind of software modifications this includes flashing any roms or even official firmwares before, so I download the firmware and flashed it as usual this is the firmware that I flashed through odin 3.12.3 firmware version was G935FOJV1DQAV also my device model is SM-G935FD while the firmware I flashed was for SM-G935F but this shouldn't be an issue because when I usually got updates over the air on the device they would be for SM-G935F so if there were any issues with this they should have popped up a long time ago, so everything went smoothly and the phone booted up again as usual, did the initial setup and adding accounts, recovery everything, hooked up the charger and left the phone to download all the necessary stuff through samsung and google cloud recovery, comeback after a few minutes to find that the device just wouldn't respond to the power button or the home button to wake the device up but the led on the phone was flashing in blue color which means I did receive some notifications, so I hard reset the phone by holding down power+volume down key, same issues pop up like before the firmware I flashed getting stuck on the boot samsung logo, went back to recovery to do another factory reset again it keeps freezing on the dm-verity tree hash thing, but this time the factory reset happens properly with no errors, but the device doesn't boot up at all, gets stuck on the samsung logo and the led on top starts flashing in several different colors, just like when you boot up a brand new S7 edge.
As a last ditch effort I try initializing the device through smart switch, everything goes normally but when the flashing process starts it gets stuck on 7% indefinitely, tried everything else but to no avail, tried flashing through odin again but it gets stuck on the same point as smart switch, tried installing the firmware in parts through odin again gets stuck on the same point when flashing AP but other parts get installed without any problems, download mode boots up fine, recovery mode now boots up very slowly with a dm-verity error "E:failed to mount / system (invalid argument).
I have 1 month warranty left on my S7 edge from where I purchased it, I want to send it back for a refund or a replacement but the only thing thats kind of worrying me is that in download mode the knox switch hasn't been tripped still shows 0 (0*000), but shows system status as custom, will this effect my warranty claim if they check my device?
Click to expand...
Click to collapse
Having the same issue. anyone help? did you manage to solve this issue?