Hi. My Galaxy S recently became unresponsive. I plan to root it and then flash a ROM, hopefully to fix this issue and upgrade it. The problem is that a few seconds after booting it becomes unresponsive and goes through a cycle repeating vibrations: one short vibration followed by a pause then three consecutive short vibrations, then a pause, and does so until it drains the battery. All the while the phone is unusable in anyway. This is an AT&T phone with no changes since purchase. Any advice on how to proceed? Thank you all in advance.
binnaeus said:
Hi. My Galaxy S recently became unresponsive. I plan to root it and then flash a ROM, hopefully to fix this issue and upgrade it. The problem is that a few seconds after booting it becomes unresponsive and goes through a cycle repeating vibrations: one short vibration followed by a pause then three consecutive short vibrations, then a pause, and does so until it drains the battery. All the while the phone is unusable in anyway. This is an AT&T phone with no changes since purchase. Any advice on how to proceed? Thank you all in advance.
Click to expand...
Click to collapse
Are you using a external sd card? If so, try booting without it.
If it's not the case, are you able to connect your phone to your pc? Backup your stuff? From there, you could boot in recovery and factory reset (this will wipe your device).
In any case, backing up your stuff would be priority atm.
BWolf56 said:
Are you using a external sd card? If so, try booting without it.
If it's not the case, are you able to connect your phone to your pc? Backup your stuff? From there, you could boot in recovery and factory reset (this will wipe your device).
In any case, backing up your stuff would be priority atm.
Click to expand...
Click to collapse
Thank you BWolf56 for the reply. No external SD. Will be attempting the recovery. I'm wondering if the vibration pattern is some kind of an error message that can be interpreted.
binnaeus said:
Thank you BWolf56 for the reply. No external SD. Will be attempting the recovery. I'm wondering if the vibration pattern is some kind of an error message that can be interpreted.
Click to expand...
Click to collapse
If you're on a stock, it's usually something that got corrupted so a wipe/factory reset can fix it. The vibration is most likely the phone letting you know if turning off (ever noticed that when you're turning it off, it vibrates to "confirm").
BWolf56 said:
If you're on a stock, it's usually something that got corrupted so a wipe/factory reset can fix it. The vibration is most likely the phone letting you know if turning off (ever noticed that when you're turning it off, it vibrates to "confirm").
Click to expand...
Click to collapse
Thanks for the follow up, it seems to have worked, although the vibrations are different from those you get right after the phone starts up, the ones I experienced were continuous and drained up the battery every time.
Related
Ever since i manually updated to frf91 sometimes when i try to wake my phone my screen freezes an i can't unlock it also when i try to power my phone back on it will vibrate 7 times an it wont come on. I guts take the battery out an put it back it to get my phone to turn back on. I've never had this problem until i manually updated my phone. I did a factory reset an it helped for a while but the problems come back. Has anyone had this problem an does anyone know how i can fix this? I'd really appreciate any help i can get
Help please
Is the bootloader unlocked?
this seems to be a common issue with FRF91, although most people's phones will unfreeze after a minute or two, does your backlight turn on and off when you press the power button?
Jep4444 said:
this seems to be a common issue with FRF91, although most people's phones will unfreeze after a minute or two, does your backlight turn on and off when you press the power button?
Click to expand...
Click to collapse
whether it unfreezes after a minute or two depends on what it's doing..there have been many times where i have to pull battery...........
rensky said:
whether it unfreezes after a minute or two depends on what it's doing..there have been many times where i have to pull battery...........
Click to expand...
Click to collapse
ya i have had to as well but most of the time it wakes just fine
No my bootloader is not unlocked an yea the backlight will come on but it won't unlock. Ive never tried waitin a min to see if it fixes itself i just usually pull the battery when it happens an sometimes when i try to turn my phone back on it does the 7 vibrating thing. Like i said before it never happened until frf91
I have an app called AutoKiller installed. It tweaks the Android system's inner memory management routines. it was set to something other than default. I changed it back to default, and haven't had a problem since. if you have this installed, maybe try and switch it to default settings.
Sounds like a data issue. A factory reset only wipes user data, You must wipe in recovery to wipe rom data. Also make sure you have the correct radio for the build especially coming from lower build. If that's the issue flash radio first to support the build. Then flash the rom.
Sent from my Nexus One using XDA App
How do u wipe in recovery? Yea im a newb lol
Also if i wipe in recovery will i still be on 2.2 or will i have to update to it again?
And now I'm boot looping won't go past n color startup animation wth
Sent from my Cyanogen Mod EVO using Tapatalk
I had that problem on my NC when it was rooted. Luckily I had another problem that let me get out by the 8 times reset manual method. Mine would occasionally update itself back to version 1.0.0. When it did that I managed to reset it & now a new NC is on its way to replace this one.
This probably won't help solve the issue but at least it lets you know you're not alone.
Mine boot looped and I did the full 8X reboot thing and then the 3 button data reset. All of that puts you back to "out-of-the-box" stock. You can then redo the autonooter rooting procedure.
Can't get out
I am stuck in a boot loop and cant get out.
First it was stuck on the droid boot animation from the auto config. After I put the autonooter card back in it started looping the rooted boot animation.
Did the 3 button thing and that forced an update but went back to bootlooping the rooted animation.
Then did the 8X reboots manually and that also forced the down arrow update, but then it still bootloops.
I tried getting in from PuTTy (as admin) but it never connects. Do I just use port 22? (to 192.168.2.2 with Data and username as root?)
adb doesn't work... going to bed now and will try again tomorrow after work.
What i had to do to resolve my issue was that was to do the 8x reset to trigger the factory reset of the OS and then do the 3 button reset of the user data. In my case it was a self tweaked issue with an app permisson. If I remember right the key combo is Power+VolUp+"n" key. Try this and let us know.
Sent from my NookColor using XDA App
Bigger Issues.... First Brick?
Nate731 said:
What i had to do to resolve my issue was that was to do the 8x reset to trigger the factory reset of the OS and then do the 3 button reset of the user data. In my case it was a self tweaked issue with an app permisson. If I remember right the key combo is Power+VolUp+"n" key. Try this and let us know.
Sent from my NookColor using XDA App
Click to expand...
Click to collapse
So ... I left my Nook in what I thought was an "OFF" state last night, only to bring it to work and find it says "Battery too low to Power on" "Please wait 15 minutes and try again"
I think... no worries... plug it in and let 'er sit for an hour.... an hour passes and I'm still getting the same screen.
Is this better or worse? let me see...
1) if it stays like this, I can return/exchange it at B&N and they won't be able to verify that it was rooted due to non-bootiness
2) If it eventually boots, I will have to try to get it out of bootloop.
3) If it comes to life and I can't get it out of bootloop, I will drain the battery again and go back to #1.
Any thoughts besides this current train?
sort of working?
OK....
so after charging on USB port (all I have at work today as I forgot the base to the charger), it will bootloop again... yay!
problem is... the bootloops take too much juice and won't allow me to fail 8 reboots. I can't even charge it up enough since I'm on USB charging and it keeps trying to turn itself on.
2 Options i see:
1) Go home and charge it on the wall and see if that helps
2) Discharge it to death and return within my 30 days (X-mas gift)
Doubt this will work, but have you tried putting in an autonooter sdcard and then plug it into the usb? If it tries to boot maybe it will boot from that sdcard?
Boot from the Froyo SD card, then fix /rom/devconf/BootCnt from ADB.
Cal you never mentioned if you cleared the user data... Did you?
Nate731 said:
Cal you never mentioned if you cleared the user data... Did you?
Click to expand...
Click to collapse
If you mean the 3 button reset? Yes.
If not... I did not because I'm not aware of it. (couldn't through the UI of course)
cal3thousand said:
If you mean the 3 button reset? Yes.
If not... I did not because I'm not aware of it. (couldn't through the UI of course)
Click to expand...
Click to collapse
Try Geezer's tip but do this:
Do three button reset WITH the autonooter card in there.
Got it working
Finally got it working after creating a Nookie Froyo card and booting off of that.
Then I reinstalled ADB on my work computer and reset the BootCnt file to 8...
that successfully restored /system and then the 3 finger trick actually gave an option to wipe.
Now to start over.
New Question: How likely is this hardware related and should I be looking to replace it before my 30 days is up>?
I ran into the same problem, trying the same solution - any luck the second time?
JasonBunting said:
I ran into the same problem, trying the same solution - any luck the second time?
Click to expand...
Click to collapse
My Nook has been great since the fix. But I also needed to use a program to turn off Wifi when I turn the display off.
I did it all from my Nookie...
confused?!
I was wondering how you fixed this..i have read everywhere, but nothing...im stuck in the nook co screen. This happened right after i plugged my nook to charge after my battery was drained...thnks
Today my 4X encountered a strange problem: It shut down itself (I thought the battery was empty and charged it), and after restarting it just shuts down immediately. It shows the lockscreen saying "no SIM" and then shuts down. Anyone know a solution to fix this? I suppose a factory reset might do it, but I don't have a backup now and would like to keep my data.
muellersmattes said:
Today my 4X encountered a strange problem: It shut down itself (I thought the battery was empty and charged it), and after restarting it just shuts down immediately. It shows the lockscreen saying "no SIM" and then shuts down. Anyone know a solution to fix this? I suppose a factory reset might do it, but I don't have a backup now and would like to keep my data.
Click to expand...
Click to collapse
If it is the SIM then try a different SIM, or put a folded piece of paper between the holder and the SIM - I always do that with phones just to make sure it keeps good contact at all times.
Other than that, no real idea mate - sorry
I think it should also work without a SIM. But as said, it just shows the lockscreen for ~2 seconds and then shuts down. I have tried without a sim, it's the same. I'll try with a different one, but I suppose that won't help much. I think i'll also try a kdz reflash, but i'll have to set up my father's PC to do so. Just thought maybe someone knows a quick solution.
Alright, i've just done a kdz reflash - same situation. Is there a way to adb pull the /data/data from any of the other modes (recovery, Emergency etc.?)
muellersmattes said:
Alright, i've just done a kdz reflash - same situation. Is there a way to adb pull the /data/data from any of the other modes (recovery, Emergency etc.?)
Click to expand...
Click to collapse
Weird... Reflash use to replace all files and stock settings unless you have some app avoiding them to run... Reflash don't delete installed apps most part of the time. If you have frozen apps they'll remain frozen. Did you factory reset before reflash?
Sent from my LG-P880 using xda app-developers app
RuedasLocas said:
Weird... Reflash use to replace all files and stock settings unless you have some app avoiding them to run... Reflash don't delete installed apps most part of the time. If you have frozen apps they'll remain frozen. Did you factory reset before reflash?
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
No, as said i wanted to try everything before doing a factory reset (don't have a recent backup because Ubuntu won't recognize the MTP mode properly). I have restarted the phone many times before without that strange behaviour and didn't freeze anything since then. I just can't tell where the problem comes from. BTW, the SIM is recognised now (after the reflash), but still shutting down.
muellersmattes said:
No, as said i wanted to try everything before doing a factory reset (don't have a recent backup because Ubuntu won't recognize the MTP mode properly). I have restarted the phone many times before without that strange behaviour and didn't freeze anything since then. I just can't tell where the problem comes from. BTW, the SIM is recognised now (after the reflash), but still shutting down.
Click to expand...
Click to collapse
You notice some over heat, you try to use it without SD card, it keeps rebooting when charger is connected?...
Cause appart of hardware malfunction, I can't see any other reason... of course we don't know if the system file is corrupted or not...
If the phone is ON time enough, you can copy the data files/ folders to your SD card, after save them all you can factory reset...
Wait for better help cause I have no idea... sorry
RuedasLocas said:
You notice some over heat, you try to use it without SD card, it keeps rebooting when charger is connected?...
Cause appart of hardware malfunction, I can't see any other reason... of course we don't know if the system file is corrupted or not...
If the phone is ON time enough, you can copy the data files/ folders to your SD card, after save them all you can factory reset...
Wait for better help cause I have no idea... sorry
Click to expand...
Click to collapse
It's not because of heat, the phone is really cool. It just stays on for a second or so, just enough to see the lockscreen or the "Enter PIN" screen and then it shuts down. It's like the battery was empty, but it's charged. It even shows the charged battery symbol. Guess I'll have to do a factory reset and lose my data. As root is gone, I also can't boot to the bootstrap recovery (with this method) to backup there. Should have done that before doing a reflash...
muellersmattes said:
It's not because of heat, the phone is really cool. It just stays on for a second or so, just enough to see the lockscreen or the "Enter PIN" screen and then it shuts down. It's like the battery was empty, but it's charged. It even shows the charged battery symbol. Guess I'll have to do a factory reset and lose my data. As root is gone, I also can't boot to the bootstrap recovery (with this method) to backup there. Should have done that before doing a reflash...
Click to expand...
Click to collapse
You can try to downgrade before factory reset... some apps won't work but, maybe the phone just don't turn OFF and you'll be able to save your data.
So downgrading didn't work either. I'll use the LG Support Tool to upgrade and factory reset now (with data loss). That should hopefully fix it.
Well, the LG Support tool also didn't fix it. Data is lost now, so I can freely do whatever I want
I've tried to get into the "low-level mode" (http://forum.xda-developers.com/showpost.php?p=35524491&postcount=11), but no success. Can someone point me into the right direction and on how to press those buttons? I've tried several combinations, but they all didn't work out - either the battery symbol appeared or the phone booted to recovery or to the "do not touch cable notice" mode.
As far as I understand I should do the following steps:
1) Remove the battery and USB cable
2) Insert the battery and plug in the cable. The phone vibrates once, then shows the LG logo, then shows a battery symbol and then turns off the screen.
3) Press Vol+ and power and hold it. The battery logo shows again. There is a sound indicating that some device is connected to Windows. The screen turns off and there is a sound indicating that the device is disconnected from Windows. Let go off the buttons.
4) Press the buttons again until there is a sound indicating that a device is connected to Windows. Let go off the buttons. The screen should remain off.
Is this correct? What am I doing wrong? Do I have to wait at some point for some action? As said, all I ever got was the "battery symbol" again (for a few seconds).
muellersmattes said:
Well, the LG Support tool also didn't fix it. Data is lost now, so I can freely do whatever I want
I've tried to get into the "low-level mode" (http://forum.xda-developers.com/showpost.php?p=35524491&postcount=11), but no success. Can someone point me into the right direction and on how to press those buttons? I've tried several combinations, but they all didn't work out - either the battery symbol appeared or the phone booted to recovery or to the "do not touch cable notice" mode.
As far as I understand I should do the following steps:
1) Remove the battery and USB cable
2) Insert the battery and plug in the cable. The phone vibrates once, then shows the LG logo, then shows a battery symbol and then turns off the screen.
3) Press Vol+ and power and hold it. The battery logo shows again. There is a sound indicating that some device is connected to Windows. The screen turns off and there is a sound indicating that the device is disconnected from Windows. Let go off the buttons.
4) Press the buttons again until there is a sound indicating that a device is connected to Windows. Let go off the buttons. The screen should remain off.
Is this correct? What am I doing wrong? Do I have to wait at some point for some action? As said, all I ever got was the "battery symbol" again (for a few seconds).
Click to expand...
Click to collapse
Once that data is gone, just reflash the phone.
My advice, like always is, downgrade, factory reset, upgrade , root, factory reset.
hope you don't tell me that you have problems with flash method...
I have tried that. Flashed v10a, wiped data in recovery, upgraded to v10h via LG Support Tool. Still shutting down. I thought the emergency recovery might fix it but I cant get the emergency mode to work. I'll call the LG support tomorrow and hope they'll bring me a new phone.
Gesendet von meinem ASUS Transformer Pad TF300TG mit Tapatalk 2
muellersmattes said:
I have tried that. Flashed v10a, wiped data in recovery, upgraded to v10h via LG Support Tool. Still shutting down. I thought the emergency recovery might fix it but I cant get the emergency mode to work. I'll call the LG support tomorrow and hope they'll bring me a new phone.
Gesendet von meinem ASUS Transformer Pad TF300TG mit Tapatalk 2
Click to expand...
Click to collapse
If when you're flashing, you use "web upgrade" instead of normal upgrade, it will upgrade with LG Tool, official firmware, what it means that is the same than the emergency recovery that you're trying to use.
The difference is that you don't need to use IMEI. The detection is automatic.
RuedasLocas said:
If when you're flashing, you use "web upgrade" instead of normal upgrade, it will upgrade with LG Tool, official firmware, what it means that is the same than the emergency recovery that you're trying to use.
The difference is that you don't need to use IMEI. The detection is automatic.
Click to expand...
Click to collapse
Thanks, I thought the Emergency Recovery was still different. So no chance to fix this now. LG's support won't work on Christmas, so three more days stuck with it.
I got the phone back today. Put the battery in, started, and... it shut down. AGAIN. They were supposed to fix that! Anyone near me who has a spare battery for testing? After all that might be faulty.
muellersmattes said:
I got the phone back today. Put the battery in, started, and... it shut down. AGAIN. They were supposed to fix that! Anyone near me who has a spare battery for testing? After all that might be faulty.
Click to expand...
Click to collapse
It goes down when charger is connected?
Yes, it does. And it recognises the battery as full, that's why I don't suppose it's because of that. But one never knows.
mines done it a couple times recently too! just living with it till the update!
Problem solved. A new battery did the trick. But I still don't know why it would shut down with the old one.
Sorry for the repetition in the title but that's what happens.
If I switch off the phone, when I switch on is fine.
If I RESTART the phone, a few seconds after the lock screen appears it restarts again. This can go on up to 10 times, the a notification of a system error appears asking to report to HTC.
I thought it was a problem with the low battery, as the first time it happened my battery was low. But then it happened again with full battery.
This is getting quit annoying. I have not tried a factory reset yet as I haven't had much spare time lately...
Any fix for this?
algiogia said:
Sorry for the repetition in the title but that's what happens.
If I switch off the phone, when I switch on is fine.
If I RESTART the phone, a few seconds after the lock screen appears it restarts again. This can go on up to 10 times, the a notification of a system error appears asking to report to HTC.
I thought it was a problem with the low battery, as the first time it happened my battery was low. But then it happened again with full battery.
This is getting quit annoying. I have not tried a factory reset yet as I haven't had much spare time lately...
Any fix for this?
Click to expand...
Click to collapse
well first thing to try will be a factory reset! backup your files and try it.
I have a Moto G6 XT1925-5 (64GB version) which doesn't want to start up. It's all totally stock, been updated to Android Pie.
It gets as far as the boot animation, and does that for about 2 minutes, then it boot loops and starts all over again. When it bootloops it gets stuck at the first Moto logo screen (not the animated one) for about 3 minutes before carrying on to the boot animation...
This happened once or twice before, we left it overnight and eventually it started up normally. But it's now been five days and it still hasn't started.
I'm not very experienced with Android hacking/modding, etc but willing to try anything. I managed to get into recovery mode and at the top it says (I presume this indicates the firmware version):
motorola/ali_retail/ali
9/PPSS29.55-37-7-6/16c5a7
Unfortunately USB debugging is not enabled. Is there anything that we can do to recover the data that was on the phone before we wipe it - or is there another method we can try to get it to start up? I saw there's a command adb logcat which looks like it might be useful to diagnose the problem but that also requires USB debugging.
Thanks in advance for any suggestions
There is no chance for you to recover your data in this mode.
WoKoschekk said:
There is no chance for you to recover your data in this mode.
Click to expand...
Click to collapse
Thanks for getting back to me so quickly.
There are several other modes available from the bootloader BP Tools, QCOM, etc but I can't work out how any of them are supposed to work.
One question - on the recovery menu, there is an option 'Mount /system'.
I pressed it and it says at the bottom /system mounted, but then there don't seem to be any obvious ways to access anything.
Is there a way to use this to access OS/kernel logs which might give a clue as to what is going wrong?
Thanks again
Step by step...
The first level of the system, which is accessible for you, is called bootloader menu (fastboot menu). From here you can boot into recovery, system, bootloader itself and some other options you mentioned in your post.
None of these options would help you to solve your problem. These are developer's options.
This level is more or less a one way data connection. The main advantage of this menu is to flash single partitions of your device. But there is no way to get a data output of any partition.
In recovery menu you find the options to wipe your data and to mount /system. Mounting /system won't help you, too. This partition doesn't store anything of personal data. It's read only and not writable for anyone. To be honest, nobody knows exactly the meaning of it in this context. Also you won't access any logs from here.
Generally you can't access the system logs. These informations are only buffered data which is cleared with every reboot. The error message of e.g. the kernel log produced by your system when having a bootloop, is only accessible while your device is looping/freezing. The next reboot erases the logs. They aren't stored somewhere on your device. Even for developers it's very tricky to view the log in such cases.
But what would you do if you get the reason for looping? You are not able to access any system partition. You need root user permissions for that. But rooting your phone will erase all data.
Apart from all that your data is encrypted and remains encrypted until you unlock your screen by fingerprint, PIN or password. No chance to get any useful data as a "third person" outside. It would take several years to decrypt it without the matching key for it.
Thanks so much for this detailed explanation, I really appreciate that you took the trouble to answer the questions in detail and explain what the various options are for.
phone5774 said:
Thanks so much for this detailed explanation, I really appreciate that you took the trouble to answer the questions in detail and explain what the various options are for.
Click to expand...
Click to collapse
No problem!
Maybe you'll find some of your personal data in your Google Drive account...
How the story ended
Thought I'd come back and post in case it's useful for anyone else:-
Due to a religious festival, we left the phone switched off for three days. After the festival ended, we switched it on, and immediately it did the same thing that it had been doing all along (spend a long time on the initial boot screen then a while on the boot animation before boot looping). Bizarrely even though it had been off it did not prompt for the PIN code.
We then held the power button as though to turn it off (but for some reason, throughout the usual power button never actually turn the phone off, it always attempted to restart immediately) and then next time it came on it asked for the PIN and started up normally!
So all in all that was a grand total of 9 days after the problem first happened. Very inconvenient not to be able to use it for 9 days, but it's now working again. We haven't dared to try to restart it since!
Some closing thoughts:
The storage is very full (99%), we wonder if that had something to do with this problem
We have now enabled USB debugging and bootloader unlocking to make recovery easier in future
phone5774 said:
Thought I'd come back and post in case it's useful for anyone else:-
Due to a religious festival, we left the phone switched off for three days. After the festival ended, we switched it on, and immediately it did the same thing that it had been doing all along (spend a long time on the initial boot screen then a while on the boot animation before boot looping). Bizarrely even though it had been off it did not prompt for the PIN code.
We then held the power button as though to turn it off (but for some reason, throughout the usual power button never actually turn the phone off, it always attempted to restart immediately) and then next time it came on it asked for the PIN and started up normally!
So all in all that was a grand total of 9 days after the problem first happened. Very inconvenient not to be able to use it for 9 days, but it's now working again. We haven't dared to try to restart it since!
Some closing thoughts:
The storage is very full (99%), we wonder if that had something to do with this problem
We have now enabled USB debugging and bootloader unlocking to make recovery easier in future
Click to expand...
Click to collapse
When I read this last post, I immediately think of a sticky power button, because if you keep holding the power button after the phone has booted it will turn off again, and start up again. And it would also explain the weird behavior you just described of not turning off but rebooting straight away. I'd say: see if you are able to clean de button with a very thin needle or a crafts- or surgical knife around the edges, is might just solve your problem...
mcremco said:
When I read this last post, I immediately think of a sticky power button...
Click to expand...
Click to collapse
Thanks for that suggestion. Interesting, not something I'd thought of.
For now the phone is working perfectly, provided that have to restart it (i.e. we make sure not to shut it down or let the battery run out) but I'll definitely bear this in mind if the issue happens again.
The power button is working normally to turn the screen on or off meanwhile.
Thanks again for your input which is really appreciated.
First time trying to restart after the above
Since posting the above messages the phone has been kept on all the time and not restarted.
Today for the first time we accidentally let the battery run out and the phone shut itself down.
We nervously plugged it in and tried to switch it back on... and it started properly first time, so perhaps the underlying problem was simply that the storage somehow got too full (in the meanwhile we have transferred many photos and other media to the computer and deleted them off the phone to free up space).
Posting this in case it helps someone else experiencing a similar problem.