Heya all,
So my Galaxy Mini started rebooting itself today.. Anybody knows what to do? I can't give much details only that I thought the problem could be the custom rom (CM7, New Experience). I flashed it back to stock, but it's still doing the same thing, sometimes it'll hold out for 30 minutes but sometimes it restarts and I can't even open Whatsapp before it reboots again.
All I can tell the on/off button for locking isn't always working as fast as it should. Could this button be stuck or something like that?
Also warranty is gone, got water damage from like 1.5 year ago.. Maybe that could still have something to do with it.
Thanks in advance,
Sanderth.
Update: I was just viewing a WhatsApp message and it rebooted itself again, please does somebody have any advice on how to fix this?
Bump: Please does anybody know what the problem could be? Today at school I wasn't even able to send a message via WhatsApp
Edit: I'm pretty sure it always happens a few seconds after I pressed the on/off button to lock. I just tried to lock it, got the prompt where you can enable airplane mode and turn the phone off and I clicked the back arrow, after ~5 secs it rebooted, could something be stuck behind this button or could my ROM be bugged?
Edit2: Well I disassembled my phone, probably something was stuck behind my button and fell out or something else was wrong with it.. But the most important thing is: It works like it should again, locking is going smooth now and it really feels as if my phone was better than before XD
Next time I'll open it first before opening a topic on xda, but well.. Hopefully somebody who will ever have the same problem will find this thread and fix it the same way I did
:thumbup:
Sent from my GT-I9300 using xda premium
Well to be honest, it'll stick to randomly rebooting itself once in a while, less than it was before disassembling and putting it back together again though (From 5 times in one hour to max. 3 on a day). But trying this could never mess something up (as long as you know what you are doing.) At least it's possible to use my phone normally again.
For the people that don't know how to disassemble, use this: http://www.formymobile.co.uk/s5570disassembly.php
Disassemble until you've got the battery compartment of, then just assemble again.
Related
Hello people!!
So, here's my problem for today, in that ROM (the Desire2Nexus 1.4 that is) sometimes when i leave my phone in the pocket for sometime it just wont turn back on.
Basically it stays Locked and The power button does not do a thing. The only way to get out of that situation is to take out the battery and reboot it.
Now, the last time it happened to me I tried to call it while it was "Locked", on the other side it seemed like it's calling the nexus normally, but the nexus didn't do anything, it did not ring, did not turn on or anything.
Did anyone here experienced anything like that?
And if this is the wrong place to put this at, Sorry in advance.
Ooh, I guess this is my first post too... yay!!
vovka3 said:
Hello people!!
So, here's my problem for today, in that ROM (the Desire2Nexus 1.4 that is) sometimes when i leave my phone in the pocket for sometime it just wont turn back on.
Basically it stays Locked and The power button does not do a thing. The only way to get out of that situation is to take out the battery and reboot it.
Now, the last time it happened to me I tried to call it while it was "Locked", on the other side it seemed like it's calling the nexus normally, but the nexus didn't do anything, it did not ring, did not turn on or anything.
Did anyone here experienced anything like that?
And if this is the wrong place to put this at, Sorry in advance.
Ooh, I guess this is my first post too... yay!!
Click to expand...
Click to collapse
King had messed something up in the kernel, that was the cause. Try using Evils latest version, with Wildmonks kernals specifically for the ROM. Its really blasing fast.
Hey guys
I tried to search but I haven't found anyone with this particular problem:
Today I had to swap the SIM card on my dad's N1. I must have touched something the wrong way since after doing so, it seems the trackball is constantly being pressed (even though it's not).
Here's some of the consequences of this, that are making me literally freak out:
1. I can't get into recovery (as soon as I do, a click is registered on "Reboot phone).
2. It only boots in safe mode
3. Navigating around the phone is almost impossible, opening up the app drawer immediately launches an app.
By hitting a text input field, I can observe how it's registering clicks really fast (by observing how the whole text field is selected/deselected)
I tried fiddling a bit with the trackball, long pressing it, clicking it, etc, but it's still a no go (long pressing it does register as a long press, but as soon as I let go, the constant clicking continues)
Seeing as how this happens whether or not after the ROM has booted, it looks like this is a hardware problem.
Has anyone run into something like this before? Any ideas on how to fix this myself?
I don't know if sending it to HTC is an option because of two reasons:
1. I live in Costa Rica, don't know if there's HTC support here, or if it'd be safe shipping the phone to the states for a repair.
2. My dad's N1 is rooted, but bootloader hasn't been unlocked. It's running a custom rom. Right now I'm not sure if I can't get it back to stock since I can't even get into recovery.
Please help! Thanks
I had this exact problem for about a day or so it turns out I had got the trackball wet try clicking it and rolling it also try giving it a day or two it might just come back good luck on your nexus
Sent from my Nexus One using XDA App
Turns out you were right!
I left it sitting for a day, turned it on and the problem was still there. I got a hair dryer and used it on the phone for like a minute, turned it on, and all is good now!
Thanks!
Problem has come back and won't go away now... definitely looks like a hardware issue, will call HTC support.
Hey guys,
I could need a bit of help! It's now the third time I'm having this problem, don't ask me why. I've got the feeling that I read the whole forum here, but didn't find anything similiar.
The 1st time I didn't change anything (ok, rooted it, but nothing else)
The 2nd time I overclocked it slightly (~850-900 MHz)
Now I'm using MIUI.
But back to the problem:
I'm unable to use the keyboard, every time I'm sliding open the keyboard (even when it's turned off), it "crashes". The screen stops working or it freezes, the only way to turn it off is taking out the battery.
However, the bigger problem comes now: I'm barely able to restart it. It tries booting, but is restarting all the time or the screen is just turning on (in some angles you see that it is turned on but it's black). After many retries, it starts working, sometimes the bootloop is running 15min or i have to manually restart it 10 times or more. The strange thing is that the keyboard works fine, nevertheless I have to choose between using it opened (taking it with me becomes difficult ) or closed...
...the main problem now is flashing a new Rom, I'm currently trying it through the android sdk and adb, but using the power-button + x is easier
I don't think that I can solve the problem, I sent the device two times back (warranty till may 2012), but maybe someone here knows a bit more. My guess is that one of the sensors is broken, or some parts of the display that should manage the sliding process...
Anyway, thanks for your attention!
Web
If you already have Rom Manager, just click Reboot into Recovery..
inches0 said:
If you already have Rom Manager, just click Reboot into Recovery..
Click to expand...
Click to collapse
Tried to use one a time ago, but it wasn't working right....
However, now I'm not even able to boot it, the screen just flashes and turns off itself before trying to restart a few moments later....guess I lost my Milestone
Sbf back to stock?
taptaptouch said:
Sbf back to stock?
Click to expand...
Click to collapse
the computer isn't finding it anymore...I'll back up the data and try use my warranty... I hope that they don't complain about MIUI...
But I'm still not getting the point, why my mobile had these issues three times, although they "repaired" it twice...and nobody else is having the same problem
Hi, this happend already to me few times so I decided to put it on here.
Sometimes when I pick up my phone and try to unlock it nothing happens, fingerprint and button all the same it looks like it completely Off. Then i have to press few times a button to actually start it and it's booting. There is huge battery loss after it boot up. See image.
I am in Stock 4.0.2 no root just few standard apps installed. Nothing fancy. This happend already few times to me. I left the phone locked and when I want to unlock its dead. Also it is behaving weirdly, when I turn it off manually I just need to press longer a button and it's turning on, but here I need to press it few times to work.
Does it happen to anyone else?
terragady said:
Hi, this happend already to me few times so I decided to put it on here.
Sometimes when I pick up my phone and try to unlock it nothing happens, fingerprint and button all the same it looks like it completely Off. Then i have to press few times a button to actually start it and it's booting. There is huge battery loss after it boot up. See image.
I am in Stock 4.0.2 no root just few standard apps installed. Nothing fancy. This happend already few times to me. I left the phone locked and when I want to unlock its dead. Also it is behaving weirdly, when I turn it off manually I just need to press longer a button and it's turning on, but here I need to press it few times to work.
Does it happen to anyone else?
Click to expand...
Click to collapse
Honestly, there's not enough information to understand exactly why it's happening. You need to get a logcat in the time before the reboot; unfortunately, logcats get erased during a reboot so it might be a little tricky getting it if the reboot is seemingly random. Someone had posted this as a possible way of getting the log:
"Retrieving the logs is tricky, since the log cache gets erased on reboot. If the phone reboots even while sitting on a charger, try running adb logcat continuously (you will need Android SDK and USB drivers installed and configured on your PC.) When the phone reboots, look at the last several pages in the command prompt window for any errors or abnormalities."
Click to expand...
Click to collapse
Otherwise, it's hard for anyone to help. I'm not much help in actually figuring out the issue, but I know if you can get the log, someone else probably can help.
For more information on logcats: Logcat Tutorial
Yeah I was trying to connect it to PC but nothing, so it is turned off. I will try next time to run command when turning on, maybe there will be something but I do not see it working before it gets erased. I was hoping that anyone else is having this problem so it might be rom related. It is completely random so you can;t guess when it happens.
I had it only few times so it's not super annoying but still it is not normal behavior. In addition it is weird that battery went from 55% to 33%, just phone reboot will not drain that much... I hope there is nothing wrong with the phone itself.
terragady said:
Yeah I was trying to connect it to PC but nothing, so it is turned off. I will try next time to run command when turning on, maybe there will be something but I do not see it working before it gets erased. I was hoping that anyone else is having this problem so it might be rom related. It is completely random so you can;t guess when it happens.
I had it only few times so it's not super annoying but still it is not normal behavior. In addition it is weird that battery went from 55% to 33%, just phone reboot will not drain that much... I hope there is nothing wrong with the phone itself.
Click to expand...
Click to collapse
Check in advanced to see if schedule off is on
Nope it's off
Happened to me to on 4.0.2. Rebooted twice a day.
Solution to me was Qualcomm flash back to stock 3.5.1 and uodate from internal to 3.5.4. OTA 4.0.2.
The theard "how to unbrick".
Not one reboot until now in days.
I think I found a culprit responsible for it. It is Hill Climb 2 game which doesn't close properly sometimes and I think it causes some kind of crash in the system. Is it possible?
terragady said:
I think I found a culprit responsible for it. It is Hill Climb 2 game which doesn't close properly sometimes and I think it causes some kind of crash in the system. Is it possible?
Click to expand...
Click to collapse
It's possible. Not necessarily the reason, but it might be. Either uninstall the app or freeze it using Titanium. Greenify might also work, but that allows the app to start itself up and potentially continue the issue. See if that stops the crashes for a couple of days.
The problem is that it doesn't happen often and only when I quit the game and lock the phone immediately after that. I am not sure if that's a reason though, just guessing because it happens after this last time. I will uninstall this game anyway, it's just time eater
Ok, so here is to explain what happened, so you can have a clue what am I talking about.
I bought Galaxy A71 a month ago (give or take), so out of the box it had Android 10. The phone was working flawlessly. Battery life awesome, pictures from camera great, etc. So, few days ago on March 26, 2021, an update to Android 11 came in. I am a tech nerd, I know about phones, rooting, flashing, etc.
So, I saw that I have around 78-80% of the battery so it was enough to download and install Android 11.
Downloading and installing and optimizing apps after went smooth as silk. I usually soft restarting my device after any software update, so I did that after the installation of Android 11 was entirely finished.
But, this is what happen when I restart my phone the normal way. I press and hold the power button, the dialog of Power off, Reset and Airplane mode came out, tapped twice the reset button and phone went restarting and just.... died. I remember that when I soft restarted my phone, the battery was on 72%. So I tried any trick in the books to turn on my phone again like combinations of pressing buttons, then with USB cable, charger, etc, but nothing was responsive. It's like the phone was clinically dead.
My phone is still under warranty and I will probably end up taking it to the T-mobile store, but the point of this thread is to inform others of the situation like mine and see if someone else had the same problem?
Maybe someone will post a solution what to do in situations like this?
If I find any solution, I will update this post with all the details.
You probably done it.But have you plugged it into A computer to see if the computer can detected it?
Essex_Hal said:
You probably done it.But have you plugged it into A computer to see if the computer can detected it?
Click to expand...
Click to collapse
Yes i did, nothing shows in Device Manager. As I said, I tried every possible trick to wake the phone up, but it was unsuccessful.
I end up taking it to the carrier store cuz it is still under warranty. They told me if they can't fix it, they'll probably give me a new one or to wait for Galaxy A72 To arrive in 2 weeks. We'll see what happens.
BorisMKD said:
Yes i did, nothing shows in Device Manager. As I said, I tried every possible trick to wake the phone up, but it was unsuccessful.
I end up taking it to the carrier store cuz it is still under warranty. They told me if they can't fix it, they'll probably give me a new one or to wait for Galaxy A72 To arrive in 2 weeks. We'll see what happens.
Click to expand...
Click to collapse
Least you still have A warranty to help you.
Good luck with it.Hope you don't lose your data if it's still on the phone.
Essex_Hal said:
Least you still have A warranty to help you.
Good luck with it.Hope you don't lose your data if it's still on the phone.
Click to expand...
Click to collapse
They fix it, it said it was software problem, got stuck on rebooting. I get it today (2 weeks later) and it worked. They managed to turn it on but without a factory reset, every app was there, every picture, video, contacts, call history, etc. I don't know how they did it, but they did. So when I got my phone back I tried to restart it normal way, long press of the power button, then tap Restart and again restart. The phone restart it without a problem. I was happy. Then later that day (2 hours ago when I'm writing this, I notice that always on display when i touch the phone screen will show up but doesn't switch off after 10 seconds (I set it up like that), instead it started to blink in intervals like i was touching the screen continuously. Then I did a deep soft reset. You know, when you press Volume down and Power button at the same time and.... got the same problem again. Phone is non functional, none combination of pressing buttons worked, just like i describe it in the OP. Just for information, I did the same on my previous phone Galaxy A7 2018 and never had this problem. I did it on this phone too, never had a problem. Then I remember it that on both phones when i do that and not having problems were running on Android 10. this phone now update it to Android 11 and that buttons combination is probably bricking the phone. It's just a thing I notice. So I am planning to call the official service that fixed the phone how did they do it, so maybe I can do it myself too. I don't want to wait for another 2 and a half weeks.
I am facing the same issue. And I think my warranty is out. Did you get to ask them how can you turn it on yourself!!
I would really appreciate some help here!
BorisMKD said:
Ok, so here is to explain what happened, so you can have a clue what am I talking about.
I bought Galaxy A71 a month ago (give or take), so out of the box it had Android 10. The phone was working flawlessly. Battery life awesome, pictures from camera great, etc. So, few days ago on March 26, 2021, an update to Android 11 came in. I am a tech nerd, I know about phones, rooting, flashing, etc.
So, I saw that I have around 78-80% of the battery so it was enough to download and install Android 11.
Downloading and installing and optimizing apps after went smooth as silk. I usually soft restarting my device after any software update, so I did that after the installation of Android 11 was entirely finished.
But, this is what happen when I restart my phone the normal way. I press and hold the power button, the dialog of Power off, Reset and Airplane mode came out, tapped twice the reset button and phone went restarting and just.... died. I remember that when I soft restarted my phone, the battery was on 72%. So I tried any trick in the books to turn on my phone again like combinations of pressing buttons, then with USB cable, charger, etc, but nothing was responsive. It's like the phone was clinically dead.
My phone is still under warranty and I will probably end up taking it to the T-mobile store, but the point of this thread is to inform others of the situation like mine and see if someone else had the same problem?
Maybe someone will post a solution what to do in situations like this?
If I find any solution, I will update this post with all the details.
Click to expand...
Click to collapse
have same issue too anyways to fix it?