For some reason, my perfect working s6 edge decided to stop working. It was working fine until I put it away for like a week due to switching over to a new phone. When I took it back out to put it back it back to factory settings, it came up with "recovery is not seandroid enforcing". Obviously, I did a quick google and realised the issue. I don’t even remember flashing the phone but I have had it more or less since it came out and only recently switched to a new Samsung.
I did the standard thing of putting it in download mode and flashing a stock rom for my version but it just wouldn’t play ball. I tried lots of different stock roms but they all failed in odin. I then stumbled upon TRWP and successfully got that flashed and thought that would be the end of it. But TRWP wouldn’t let me do anything apart from tun the phone off, it wouldn’t let me boot into recovery or download mode which was a pain.
So, I’ve just been trying to scour the internet to see what to do next or if it is bricked and beyond hope
I’ve got a picture of the download mode screen when I did get into it once
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any help would be appreciated
Related
Hi guys, as i said, my girlfriend's galaxy s4 is stucked in a bootloop when she was playing farmville.
The phone is completely stock and with the last firmware.
I cannot enter into recovery, just can go to download mode, in which the phone is perfectly stable (is stable also when is charging on the pc).
I've tried almost everything and one time i was able to boot the device and enter to the home launcher, turn two pages and then bootloop.
Sometimes (two or three) the device stuck on a green screen like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've tried to:
- reflash the stock firmware with odin, i get no problems and the device PASS the installation but the problem isn't resolved.
- remove sd card
- change battery
- play with the power button
I've no idea on how to fix this, why i can enter into download mode and bootloops finish?
A big thanks to everyone.
Probably hardware failure. You can try to flash the rom with .pit file and re-partition as a last resort. If it still wont boot then, then you have hardware failure.
Thanks Lenny, but how is it possible that in download mode the phone is perfectly stable?
Hello!
My Samsung Galaxy S4 (i9505) suddenly crashed while I was playing a game and got into a boot loop. The screen goes all sorts of crazy on boot, so I think it's a hardware problem:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There's also a sweet-spot on the screen just above the Samsung S which makes the screen kaleidoscope a bit more when pressed.
I can occasionally get past the boot screen, but it inevitable crashes and reboots on the Android loading splash. I can't get into recovery mode, but I can get into the Samsung download mode.
I was running a custom ROM (flashed via TWRP), rooted and running Xposed . The ROM was a custom build of vanilla Android 5.1.1 which I found in a ROM thread on here.
I assume some piece of hardware has toasted or come loose. Has anyone seen anything like this before? Might it be repairable?
I look forward to the good news
Thanks!
Edit: I've just re-flashed an old full factory backup of my phone, as per this guide (http://forum.xda-developers.com/showthread.php?t=2317311) and it all worked (warranty bit flag has gone, etc). It hasn't been boot-looping as frequently today, before and after flashing, and the screen has only gone nuts once. It's currently just hanging trying to get into the stock recovery mode.
Looks like a gpu issue.
I was trying to root and mod my spare Galaxy S8 and during the process the battery died... now it is stuck on the boot screen. When it turns on it opens to the custom Samsung boot screen and does not change or boot any further. When I reboot it with the button combination it boots into upload mode. From there I must reboot again. I can still get into download mode and into android recovery mode, but have been unsuccessful at and attempts of flashing with Odin, ADB, or from the SD card. I am completely confused. Any advice will help and be greatly appreciated!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Use modded Odin with the latest firmware which is QL1.
Stop trying to root
I having a similar problem, just that it DID finished updating. Now it's stuck at boot screen even after updating it to the last version available (AQL1). I don't know what else to do....
well I gave up and finally went to Best Buy and spoke with a samsung employee.
I was able to get my phone back in 100% working order! He just used his special scan tool and flashed it the very first time. For FREE!!!!!
Hello guys,
I have a Galaxy S8 in my hand, which tried to update itself yesterday during a car ride via OTA. But the update obviously went wrong, because since then there is only one boat loop left. I once tried to start the recovery mode and trigger a wipe. However, this only causes me to end up in recovery again. If I flash the current firmware via ODIN it works, but I end up in the boot loop again.
Does anyone have an idea?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
noone else with that issue?
With my S8 never unlocked, never flashed i have the same error in recovery.
My phone don't boot loop but after power on, the animation freeze (ring turning) and phone reboot 30s later. after reboot phone is very long to start: more than an minute.
i ask samsung for this problem. they just said "it's an app problem, not an phone problem ! reboot your phone in safe mode"
have you tried to make an full wipe ?
edit: i did'nt see you have an dm-verity error
I dont know what dm-verity is. The phone was never manipulated with other firmware or sth.
Hi guys, my English is bad at first so I'm sorry.
I'm telling the whole story from beginning to end. I have an old Samsung Grand Neo device. I was going to reset this device in recovery mode, but there was a red cross under the Android sign in recovery mode. So I rebooted the device from the power button without looking for the solution. Then, while the device was restarting, the Samsung Grand Neo text came up and when the Samsung screen was coming up, it threw itself back to the Samsung Grand Neo screen and the device did not turn on again. Then I tried to install different software from Odin 4 times, but I could not get any results. (I installed a single file, I also installed the 4-file one, but it didn't work.) Just while doing a detailed research, it said to make the Re-Partition option ticked in Odin's settings. What does this Re-Partition do? I would be very grateful if anyone who has come across this problem or has knowledge of it can help. (The device remains as in the following photo, it is a visual representation.)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}