Hey,
yesterday i faced a problem i didn't knew of yet. As i mentioned sometimes, i came from an One M7 2 weeks ago as it didn't work the way it should - camera useless and awful battery life. I rooted the M7, had problems with it and so on - just how it is with a rooted phone + custom roms.
However, due to the DRM i didn't root my Z3 yet. Yesterday i took it out my pocket, thought it was a bit warm.. nevermind. It worked. 30 minutes later i pulled it out again, still warm, and screen wouldn't turn on. I reset it (power and vol+ for those who didn't know), tried to boot again.. well, it took several minutes and finally showed me the attached error message. The system performance was really, really low. Everything stuttered, i couldn't even enter my pin. A few forced reboots later i could finally enter my pin and get into my system only to notice that my data partition wasn't doing fine. I had to set language and so on in the initial setup process, apps kept force-closing in seconds. My own apps were still on the device, however when i tried to open WhatsApp there was no data there, i should have gone through the registration process. The phone froze after seconds each time. I tried to enter the fastboot menu (is it called that way?) while booting to just do a factory reset, didn't find the button combination. So finally, after i found home without navigation from no man's land (sure, why doesn't it happen at home anyway..), i managed to boot it, get through settings and initiate a factory reset. Of course, all the apps were deleted then and i could install all apps like LightFlow again. Had to re-enter all the settings i did in those kind of apps, it was kind of annoying.
So, my questions: Why the hell did this happen to my Z3? Not rooted, didn't even think of it. There wasn't a day on the One M7 without flashing anything and it never happened. It wouldn't have been as bad as it was on the Z3, as i HAD root, could have wiped data in TWRP in a matter of seconds and also had backups of my data, which i of course didn't have for my unrooted Z3.
Is it likely to happen again? Can any app do this on a non-rooted phone? I read a bit about the error, that it would be caused by some apps, but not in the extent as it happened on my phone. Most of the times it would just be an annoying error message.
I got a thing in always getting a defective unit, so i hope it isn't happening again on the Z3
Maybe the internal flash is corrupted/failing. I had a similar issue with my HTC One X I went to nap one day and half hour later it shut down, it restarted but boot looped. Eventually it showed no data partition as being mounted and completely died. They replaced the motherboard.
Better contact Sony, maybe you need a replacement.
Mh, actually that's the least thing i want to do.. I'd have to wait for at least 2 weeks to get it back and chances are that they won't do a thing or damage it (bad experiences with my former Razr i). It works just fine after the factory reset, no errors yet. If it should happen again, i'd of course send it in for repair but i think, until then i will use it normally, with more caution and backups of course.
Probably the cleanest solution HERE
Related
I'm running stock S3 software, and I hit a snag this morning where the phone was stuck in a reboot/deadlock cycle. It would come up to the lock screen, and after about 10 seconds, deadlock. I was getting ready to wipe the phone, when I got a call from my wife during the brief "uptime" of the phone, which seemed to break the deadlock.
I was able to get what data I could off of the data partition (photos, etc), but now it remained stuck on the same issue on boot. Anyone ever see this before? I had to factory reset the device to get it back to normal.
mikecico said:
I'm running stock S3 software, and I hit a snag this morning where the phone was stuck in a reboot/deadlock cycle. It would come up to the lock screen, and after about 10 seconds, deadlock. I was getting ready to wipe the phone, when I got a call from my wife during the brief "uptime" of the phone, which seemed to break the deadlock.
I was able to get what data I could off of the data partition (photos, etc), but now it remained stuck on the same issue on boot. Anyone ever see this before? I had to factory reset the device to get it back to normal.
Click to expand...
Click to collapse
I replaced my phone, it was working fine for a few weeks, and now this bull**** is back. It gets up into the Touchwiz UI, then hangs for a while, and then resets the UI. This keeps happening repeatedly. I have to boot into the stock recovery and wipe the phone.
Does anyone out there know of anything like this? Are there incompatible apps with the S3 and touchwiz that can cause this? Anyway to debug it?
Thanks,
Mike
So heres the story....wife has had lg g2 since it came out with 0 issues. About 3 days ago the phone starts doing some crazy ****, flipping through screens by itself, opening and closing apps, deleting things, rebooting, changing system settings. This was after earlier in the day she had downloaded some random games for my son to play (not sure if this was the cause/is at all relevant, just trying to be as detailed as possible).
My first though was that one of the games may have had some virus/malware **** going on, so did a factory reset. The reset was successful, however the issues continued. Next though was to root/unlock/install custom rom. (I have done this to all my phones, with minimal issues, so i felt fairly confident in doing so) So i rooted, installed twrp 2.7.0.0, and flashed this rom - ATT-stock-rooted-D80020K.zip - and all seemed well. Phone booted and behaved normally for the rest of the day (12 hours or so). Plugged in charger, went to sleep.
Next morning, wake up, grab phone, and its showing the LG logo (like when you first power it on). Restart (power button long press) and it boots into TWRP, and i go looking for the rom file to reflash, and its gone. All files are gone. In the file explorer in TWRP, i can see the files,(data, system, boot, and so on) but when i click on them there in nothing in any folder. All downloads gone. Everything.
But i can still get into TWRP, so i thought ok, ill just plug into pc, mount the phone, copy appropriate files, reflash rom, and all will be good. WRONG. I cannot get TWRP to mount the phone, and at this point ive got a pretty expensive paperweight.
All my unlock/flash/root experience has been on HTC devices up to this point, and i have never had an issue like this.
If anybody can advise what to do next, Im listening. Ive exhausted my knowledge on the subject at this point and NEED HELP PLEASE.
Thanks in advance.
Hi, I was sitting down with my nexus on my leg with about 40% battery left when it suddenly turned off and then flicked to the google startup page before going blank. After attempting to turn it on again (to no avail), I resorted to plugging it in, which resulted in the phone looping on the google page then vibrating before repeating. I tried to get it into the bootloader menu, but it appeared and then reverted to the google page after the phone vibrated.
I've tried looking up solutions, but the only plausible situation for me seems to be returning it so the warranty can take over. The only hitch with that being that the bootloader is unlocked (not rooted, just the bootloader). I really am stuck, and do not know what to do. Any help would be greatly appreciated.
I had this one. Factory reset /wiping data was the only thing that fixed it. I assume something went corrupt with my data
Sent from my Nexus 5 using Tapatalk
It seems I got lucky. The phone rebooted properly and went to optimise all the apps as it would after an OTA update. It started up and worked as normal, until I restarted it, after being on for about 3 minutes, it turned itself off again. It rebooted in the same manner again, so I've just taken this time to relock the bootloader (so I can use the warranty if I can find proof of purchase (well, the date more importantly)). Hopefully this was just a little glitch, but I will post again for more advice if it goes wrong again (and I'll try a full factory reset first)
My Nan got a new phone from Tescos Mobile a couple months ago.
From what she's told me it seems like this issue has been around since the time she got it.
The phone will randomly reboot into safe mode, disabling all her non-essential apps, without warning and suddenly.
There appears to be no rhyme or reason for it, the only non-android apps on there are 'Tesco Clubcard', 'Lidl Plus', 'Tesco Mobile' & 'Whatsapp'.
It seems unlikely either one of these apps is causing the phone to reboot into safe mode.
When I last saw her I did a factory reset on the phone to see if that resolved the issue.
It was fine for 2 weeks, but then it started rebooting into safe mode again.
She had not installed any new apps in those 2 weeks... I'm pretty sure she doesn't know how to. All I can think is maybe a system update automatically installed that caused this issue to re-occur.
The phone is currently up to date.
I've told her to return the phone for a replacement, but she went to their help desk she was told it would cost £120 (!!!)
I had a look online and it seems like you can only book returns via Tescos online repair and they won't accept returns in person.
It would be preferable just to fix the issue myself if possible... Is there an internal log I can access to get a hint why as to why it's rebooting into safe mode all the time?
Google has been useless. All I can find are guides on 'how to reboot into safe mode', I have yet to find another instance of someone with this problem, but I'm sure it must be common.
EDIT:
It's just occurred to me... I've never personally experienced it suddenly rebooting into safe mode, and google suggests this is not a thing that commonly happens... is it possible my Nan is triggering this with some kind of 'hidden' user input to reboot into safe mode? (ie, holding down the power button and volume button too long)
The problem I have is with the galaxy z flip 3, it worked just fine inthe morning but after it ran outta juice and I charged it to a certain percentage, it stopped working properly, and got into an infinite boot loop, I tried forcing it to restart by long pressing volume down+power , but it didn't work, then I tried opening the recovery by long pressing on volume up+power and yet it also didn't work (I think that maybe it's because it was trying to boot at the time), so have you guys any solutions , please do help me cuz this phone really is important and with all honestly, isn't even mine XD, I'll be waiting for an answer
Your failsafe options are contact Samsung or do a factory reset (and then potentially contact Samsung).
If you can't boot it to anything, the only real option you have is to flash firmware, which likely won't help without wiping.
Unfortunately, not booting doesn't have a whole lot of options that don't wipe data without being rooted. Even then, you'd need recovery.
I see, then I may consider giving it to samsung, as long as they won't reset it, cuz the only reason why the phone is so important is because of the data, altough, isn't there any other way to acess recovery? Cuz I had this problem with the s10 before and I fixed it somehow (a certain Bixby key combination), but this time it seems there isn't any hidden combination.
Samsung is going to reset it. It's a required first step for them to do any work on it, even if the work has nothing to do with the software. What may help find a way to recover the data is starting with how it got to this point. Did you install anything new, change any important settings, or anything else that could have been a part of the issue? If not and it is an unexplained hardware failure, the data is likely gone already.
If it's something you might have installed or changed, it's possible that putting the phone in safe mode and undoing it may solve the issue and let you boot normally.
Booting into Safe Mode:
Make sure the device is powered off (charging is ok, as long as it is not currently trying to boot)
Hold the side key to power on and continue holding until "SAMSUNG" appears and the device vibrates
Immediately release the side key and begin holding volume down until boot completes
If the device has booted into safe mode, you will see a translucent "Safe Mode" in the bottom left
twistedumbrella said:
Samsung is going to reset it. It's a required first step for them to do any work on it, even if the work has nothing to do with the software. What may help find a way to recover the data is starting with how it got to this point. Did you install anything new, change any important settings, or anything else that could have been a part of the issue? If not and it is an unexplained hardware failure, the data is likely gone already.
If it's something you might have installed or changed, it's possible that putting the phone in safe mode and undoing it may solve the issue and let you boot normally.
Booting into Safe Mode:
Make sure the device is powered off (charging is ok, as long as it is not currently trying to boot)
Hold the side key to power on and continue holding until "SAMSUNG" appears and the device vibrates
Immediately release the side key and begin holding volume down until boot completes
If the device has booted into safe mode, you will see a translucent "Safe Mode" in the bottom left
Click to expand...
Click to collapse
Well I just asked the original owner (my mother), and apparently she doesn't remember downloading anything new into it, and it just went crazy by itself, also something else I wanna note, I tried charging it and it booted into recovery all by itself, I taught it was weird but Still went and wiped the cache and then when I tried restarting it it suddenly ran out of juice once again, also, it's second display shows some weird curruption/bug or glitch-like lines. So based off of this, can you really find the origin of this problem and if there is really any hope of saving it's data XD. Thank you btw, and once again, I'll be waiting for an answer
There are hundreds of reasons it could do that, including a faulty board. Thanks to the removal of physical sdcard support, you'd need to get it to boot into something with at least adb support to pull anything off it. Stock recovery doesn't provide any ways to perform a decent backup, but it sounds like the only option that wouldn't wipe the device didn't work.
I see, alright, thanks a lot, I'll consider resetting it
It may be worth trying to flash firmware first. Go into it knowing it may reset the device or leave you needing to reset it, but it doesn't hurt to try if you run out of safer options.
Same here, same symptoms, happened in front of my wife's and eyes face. We are fairly techy and understand our way around our devices. We also noticed the device crashed then would make it all the way to the home screen launcher and before catching signal the crash would cause a restart at that point I went in and did a cash swipe rebooted right back into recovery by itself then I unplugged the cable and it was acting as if it has a dead battery but when the cable was last plugged in during a couple of crash and then restarts all the way to the home screen I know the battery was at 70 something percent. My next step is going to probably be flashed the current firmware that just released on top of it as a dirty flash and see if I can get it to boot. If not then I'm going to do a hard reset and see if that works. When plugged in it automatically starts exhibiting symptoms as if the buttons are stuck. The devices in the OtterBox and it's fairly brand new I would say mint. Not dirty or any smudges either. all I'm saying is I'm one of those type of technicians that say yeah right when people say it just happened I don't know where but this actually happened I don't know when I was able to witness it. I'll come back and let you guys know what works and what doesn't. (By the way excuse my grammar I was voice typing while driving )
ariveraiv said:
Same here, same symptoms, happened in front of my wife's and eyes face. We are fairly techy and understand our way around our devices. We also noticed the device crashed then would make it all the way to the home screen launcher and before catching signal the crash would cause a restart at that point I went in and did a cash swipe rebooted right back into recovery by itself then I unplugged the cable and it was acting as if it has a dead battery but when the cable was last plugged in during a couple of crash and then restarts all the way to the home screen I know the battery was at 70 something percent. My next step is going to probably be flashed the current firmware that just released on top of it as a dirty flash and see if I can get it to boot. If not then I'm going to do a hard reset and see if that works. When plugged in it automatically starts exhibiting symptoms as if the buttons are stuck. The devices in the OtterBox and it's fairly brand new I would say mint. Not dirty or any smudges either. all I'm saying is I'm one of those type of technicians that say yeah right when people say it just happened I don't know where but this actually happened I don't know when I was able to witness it. I'll come back and let you guys know what works and what doesn't. (By the way excuse my grammar I was voice typing while driving )
Click to expand...
Click to collapse
Hello everyone just a quick update. Once I got home I plugged the device into a Samsung fast charger and Samsung OEM USB type-c cable and realize the device booted all the way to the home screen but register the same battery level as I mentioned above. Device was working as if nothing happened to it. So I updated all the apps on the Galaxy store then updated all the apps left over from the Google Play store, I then proceeded to check for a firmware update because I know the April update just released and installed the update with no issues. Updated the apps that needed to be updated again somehow there's always something and unplug the device from the power cable. Everything was working if no issues about half hour later the device cuts off and does not want to power on. FYI I already had my wife contact T-Mobile and get a warranty replacement we only paid $5.00 so my thoughts and conclusion on what's going on something happened to the battery or it's defective. Btw we only use Samsung OEM cables and equipment at home and in the car while connected through Android auto. it's only working while being plugged in it's not charging all the way even though it's registering it's charge level while the device is on.