Hi.
My S3 started acting all weird today. After opening a link from a Facebook post and opened up Chrome, my phone restarted itself and got stuck in a bootloop. I took the battery off and inserted it back and the phone got stuck in the same kind of bootloop. It restarted about 3-5 times and then it booted to Android and opened up a welcome screen (the same which appears after a factory reset), asking Google and Samsung account credentials. I skipped this and at a first glance it seemed my device was factory reset. All the apps and settings were gone and interestingly, storage info says 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"
}
There's definitely something in storage but not showing up.
Another strange thing: On device bootup, the bootup sound is gone missing.
Kernel message log tells "Sound file not found, Shutdown sound will not be start!". I tried to inspect last_kmsg and logcat to find out why it did fall into bootloop but I could figure out nothing.
My last_kmsg can be seen here: View attachment last_kmsg.txt
Device: Samsung Galaxy S III GT-I9300 international, Stock firmware and not rooted.
Android version: 4.1.1
Baseband: I9300XXDLID
Kernel: 3.0.31-319653 [email protected]EP-67 #1
Build: JRO03c.I9300XXDLJ2
A notable thing:
I had an app called TelStop installed. It registers on the tel:// handler in order to prevent exploiting the dialer, so I think my phone was not factory reset via dialer exploit. I consider the link I opened from Facebook post as legit, as it was a pointing to Google's chromeexperiments.com site.
Has anyone else ever experienced something like this? Thank you for your time.
You have corrupt firmware . Backup data and factory reset as first option .
jje
Thanks for your reply. The further I looked into the problem, I too started to suspect that firmware's corrupt. My phone couldn't boot up anymore so I played it safe and sent my phone to get fixed before trying anything regrettable (flashing and failing).
Sent from my Nexus 7 using xda app-developers app
Related
Hello,
I've got a weird problem with my M4
I've got the phone for over 2 years, it's the E2303 version. It worked perfectly normal until at some point it started randomly crashing (Note: the phone wasn't rooted at this point and it had Android 5.0 26.1.A.3.111 (carrier version)). The crash looks like this: the phone freezes for like 2-3 seconds not responding to any input, then the screen goes black, then it boots up normally. However it isn't rare for it to crash like that, then while booting up crash again in the same way, repeat a couple of times. In System incidents it's counted as just 1 incident. I also noticed that sometimes after successfully booting up after crash wi-fi, mobile transfer or airplane mode are switched on/off, not as before the crash.
I thought the problem would go away so I waited a bit, but it kept on crashing. Sometimes it can go for a few days without crashing, sometimes it crashes a few minutes after last crash.
I've tried fixing the phone using PC Companion (it also updated it to 6.0) - didn't help. I've tried flashing a stock 5.0 ROM using Flashtool (same as before: 26.1.A.3.111, but a non-carrier version) - also didn't help. Also I've got the phone rooted by now. I don't know about bootloader, the service menu tells me Bootloader unlock allowed: No, even though I've got the OEM unlocking switched on in the Developer options (I'm not that tech savvy in case of phones and I'm getting lost a little bit).
I've got some screenshots here:
{
"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 hope there is a way to fix this phone, this crashing is starting to get a little annoying...
Any help would be really appreciated
Install twrp. Download latest stock rom. Format phone by wiping cache, system and data in twrp wipe option. Install flashtool and use it to install latest stock rom. Watch a tutorial on youtube How to install latest stock rom through twrp
Suddenly phone got 5-10 fps out of nowhere and not changing back.
Decided to get logcat and see if something interesting came up (this is maybe 40 min after when phone started to be a little more "normal")
It started ok with some warning but soon went to application error and then access denied to files?!
I did not use Instagram(the app crashing) for over 12 hours before.
Now the last picture is running over and over again (same things coming up, like it was looped)
So am I forced to reset and flash from start? Should I be worried about anything?
Thanks in advance!
Edit: it changed to some really worth and (to me) worrying things so a full reset is mandatory when I get home...
{
"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"
}
edici said:
Suddenly phone got 5-10 fps out of nowhere and not changing back.
Decided to get logcat and see if something interesting came up (this is maybe 40 min after when phone started to be a little more "normal")
It started ok with some warning but soon went to application error and then access denied to files?!
I did not use Instagram(the app crashing) for over 12 hours before.
Now the last picture is running over and over again (same things coming up, like it was looped)
So am I forced to reset and flash from start? Should I be worried about anything?
Thanks in advance!
Edit: it changed to some really worth and (to me) worrying things so a full reset is mandatory when I get home...View attachment 5072029View attachment 5072031View attachment 5072033
Click to expand...
Click to collapse
It seems your software has been corrupted somehow. Yes, reflashing your stock firmware should fix this.
Sent from my SM-S767VL using Tapatalk
Well, it's a bit of a long story, so I'll try to be as short as possible.
Last year, and after hours of searching on the internet, I found the solution for "Custom binary blocked by frp lock" on this forum (here and here). Both methods promised to fix the lock without erasing my data, but I decided to try the second one (it consists of reinstalling only the boot image with Odin).
Fortunately it worked for me on the first try, and since this method was not well known on the internet, I decided to make a video tutorial to help those who had the same problem and wanted to keep their data.
The fact is that, unfortunately, this method didn't work for everyone, and in many cases it generated bootloops or black screens of death.
And my question is: does anyone know what could be the cause of this?
I tested it on SM-J710MN and SM-G532M, both running Android Marshmallow, and the bootloops/black screens occurred on devices running Android 6, 7, 8 and (I guess) 9 and 10.
Starting with Android 6 FRP on any such Android device is automatically enabled once a Google account is logged in to a device. The only way to get rid of it is by removing the account from the device into which it has been synced.
jwoegerbauer said:
Starting with Android 6 FRP on any such Android device is automatically enabled once a Google account is logged in to a device. The only way to get rid of it is by removing the account from the device into which it has been synced.
Click to expand...
Click to collapse
Thanks for answering.
Maybe I did not express myself in the correct way, but actually I was referring to the block that does not even allow to boot the device and only shows words in red, as seen in this image.
{
"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"
}
But beyond that my question is about why does the bootloop or black screen happen after flashing the boot.img file? Does it have to do with a different/incompatible version of Android/binary/csc or something like that?
Hey there,
as mentioned in the title my long used Honor 9 started to randomly restart (sometimes multiple times). I can be triggered when opening/closing different apps, browsing through youtube or listening to spotify. Sometimes the phone even restarts after I entered my sim-pin, so I can't use it at all at the moment which is very frustrating. Most of the time, if the phone restarts, it ends up in the eRevovery Mode or the Emergency Backup Mode. There I only have the option to shutdown/restart/backup/reset the phone. I always press restart and with a bit of luck it starts completly normal so I can use it... until it restarts again on its own at some point...
I never had issues with this phone until last week. The last few days those random restarts and boot loops ending in the eRevovery Mode happened very frequently.
Here is some info:
I use this phone since November 2017 with an external 128GB SD-Card
4GB Ram, 64GB internal memory
SD-Card used 100GB/128GB, Internal used 30GB/64GB (so technically there is enough space left)
EMUI 9.1.0.231 (strangely it shows the same version as an "update" sometimes, see picure down below)
In 2019/20 I changed the battery once (old battery was bloated/swallen, no problems occured after the replacement)
My phone is not rooted
... if someone need more informations about my phone: just ask!
What I have already tried to fix the problem:
Downloading "the same version update as already installed" (see picture down below)
Deleting unused apps
SD-Card removed
Cleared System Cache
Using "safe mode"
Doing a factory reset
Unfortenately nothing helped.. Someone has an idea whats the problem and how I can fix it?
Thanks in advance!
Attached Picture: Phone Version
{
"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"
}
UPDATE:
I think I found the issue. I just saw the reviews of the battery I changed in late 2019 (see: here). Nearly every review is stating that this battery is causing the restart problems. This is a little bit strange because I used this battery for like 2 1/2 years and had no problems until early 2022 when I suddenly experienced the same issues.
Has a new battery solved the issue?
I'm currently having the same issue.
Ok, so i got this random Huawei P20Lite right?
Back isnt pealed off, works fine, no damages.
BUT WAIT... About Works Fine... It Wont really boot up into The OS!!!
Somethimes shows this really weired Image when pluged in and charging the phone, or randomly:
A green Screen with a Red Square on Top and a Blue one Down.
{
"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"
}
Not My Picture
It will then boot up and greed you with A:
Again, not my Picture.
Acording to Huawei, You have to Use HiSuite to recover it.
1. Put the Phone into Fast Boot. AND conect to PC
2. Open HiSuite on Your PC and click on Recovery mode or whatever its called.
3. i donk know i forgot.
anyways, i get this nice little message
(In translated, this means That: Your Device doesnt support System Recovery.
Bro wth
Anyways, our phone story doesnt end there...
I tried doing it without the Computer.
using eRecovery!!! not surprising i know...
Still, it was stuck on booting animation trying to enter eRecovery.
According to Huawei, "this message is displayed when a system file is replaced or modified, or the system is manually updated to an unofficial version". They were responding to another user with the same issue as mine.
I think that this is the Issue. Still, the instructions to fix it, dont work. (as tested above.)
Tutorials show the eRecovery method without the PC.
Here are some info i found:
Another Guy having the same issue:
i forgot the link but someone else on XDA Had the same issue.
please help!!!
hello sir did you have any luck resolving this issue (I've purity much looked every were but I had no chance)