Develop Bugs

[Q] My Phone Vibrates Continuously as I hold the Power Button to Turn it on

Hello, everyone, I have a problem with my phone.
Before the problem, I was rooted without any custom roms. I have never installed any custom roms on my phone. I have always been stock, but rooted.
This morning, T Mobile pushed an updated to my phone. I did some research (not sure if I did enough) and apparently it was the UVLDE update. So I clicked it, phone restarted in 5 seconds, and restarted in clockwork mod, I believe. It was the screen that allows me to reboot along with some other options and is navigated by pressing up and down on the volume buttons.
I pressed reboot phone and the phone rebooted and worked normally throughout the day.
Now, I wake up (and I am not sure what happened, maybe I accidentally turned the phone off in my sleep) and I attempt to turn the phone on and it vibrates consecutively, on and off, and sometimes the screen blinks.
Is there any way I can fix this issue?
Thanks for your time. I performed a search, but I couldn't find the issue or I couldn't find any keywords.

Mr. Holmes said:
Hello, everyone, I have a problem with my phone.
Before the problem, I was rooted without any custom roms. I have never installed any custom roms on my phone. I have always been stock, but rooted.
This morning, T Mobile pushed an updated to my phone. I did some research (not sure if I did enough) and apparently it was the UVLDE update. So I clicked it, phone restarted in 5 seconds, and restarted in clockwork mod, I believe. It was the screen that allows me to reboot along with some other options and is navigated by pressing up and down on the volume buttons.
I pressed reboot phone and the phone rebooted and worked normally throughout the day.
Now, I wake up (and I am not sure what happened, maybe I accidentally turned the phone off in my sleep) and I attempt to turn the phone on and it vibrates consecutively, on and off, and sometimes the screen blinks.
Is there any way I can fix this issue?
Thanks for your time. I performed a search, but I couldn't find the issue or I couldn't find any keywords.
Click to expand...
Click to collapse
Maybe a brick? And questions go in the questions section for future reference.
Sent from my SGH-T989 using xda premium

Thanks. I'll remember that for the future.
I don't know if it's a brick or not. I haven't tried anything fancy yet. I'm looking for assistance before I go any further, if there is any further place to go.

Mr. Holmes said:
Thanks. I'll remember that for the future.
I don't know if it's a brick or not. I haven't tried anything fancy yet. I'm looking for assistance before I go any further, if there is any further place to go.
Click to expand...
Click to collapse
If you have clockwork mod on your phone and you can get to the clockwork mod menu, go to mounts and storage and plug your phone into your computer and click mount usb storage and copy this rom to your phone.
http://theunlockr.com/2011/11/29/how-to-unroot-the-samsung-galaxy-s-ii-t-mobile-version/
Then go to install zip from sd card and pick the one you just copied to your phone. It'll put you back on stock 2.3.5 hopefully that will work and if it does you will have to re root your device because this zip puts your phone to completely stock and removes the root. Hopefully this works for you it has for me in the past good luck.
Sent from my SGH-T989 using xda premium

Update.
I plugged it in to my computer via the USB.
Apparently, the computer can't recognize itbecause the device has malfunctioned (not sure how accurate that is), but the phone has turned on and I can use it.
I know the problem still, exists, so should I still follow your advice, JPOKeefe's, and go completely back to normal after erasing everything? I have no problem doing that to save my phone.
Modification:
Maybe the battery was just dead... which is why it's 0 % charged and it won't turn on after it was working perfectly before I slept.
If that is the case, then I am prepared to defend my intelligence! I guess it's just some paranoia from the update this morning that didn't actually go through.

Mr. Holmes said:
Update.
In plugged it in to my computer via the USB.
Apparently, the computer can't recognize itbecause the device has malfunctioned (not sure how accurate that is), but the phone has turned on and I can use it.
I know the problem still, exists, so should I still follow your advice, JPOKeefe's, and go completely back to normal after erasing everything? I have no problem doing that to save my phone.
Click to expand...
Click to collapse
Honestly you don't NEED to do it but if your phone is messing up and wont boot maybe you should go back to stock and re root when you read and learn more and feel more comfortable having a root.

Thanks for you quick replies.
I ninja edited my post, by the way. I'll give it a moment to charge and see what happens.
The phone was acting slightly stupid this morning after I attempted that update, so I guess I had to be sure it wasn't something drastic.
I have been comfortable with the root I had. If this phone bricks or blows up, then I have an excuse to get a GS3. Because, you know, I might as well. =p

Mr. Holmes said:
Thanks for you quick replies.
I ninja edited my post, by the way. I'll give it a moment to charge and see what happens.
The phone was acting slightly stupid this morning after I attempted that update, so I guess I had to be sure it wasn't something drastic.
I have been comfortable with the root I had. If this phone bricks or blows up, then I have an excuse to get a GS3. Because, you know, I might as well. =p
Click to expand...
Click to collapse
Just hit the thanks button!
And i have to wait till december for GSIII thats when my contract is up /:

Questions go in the Q&A section

[Q] Strange things followed by brick galaxy nexus.

Phone is Verizon Galaxy Nexus, running the vicious jellybean build that first came out (yeah I was too lazy to install a new ROM when the first Jellybean build I got my hands on worked fine)
Alright so here's the sequence of events,
Last night - phone working just fine
When I went to look at my phone and set an alarm for when I went to sleep I noticed it was powered off. So I tried to power it on and it hanged at the Google logo. It did this for about 20 minutes, and then I pulled the battery and tried again. This time I left it at the Google logo bootscreen over night (plugged in). Note: I'm not sure if it was bootlooping or hanging at this point, I don't remember it vibrating)
I'm awaken in the morning by the sound of my phone vibrating every 10 seconds. I look at my phone and it's at the unlock screen but the only things I can do are emergency call and, strangely, it asks me to enter a password to decrypt my phone. I never encrypted it. I started freaking out, at this point I probably should of started Googling for a default password or something, but in my morning stupor I rebooted the phone and it just bootlooped on me.
I got into CWM recovery, looked for a NANDROID backup but it kept telling me sdcard wasn't mounted, and attempting to mount it failed. I'm not seriously scared.
Reboot back in to CWM recovery to see if anything changes. Nope.
I Google this problem and land on this page. (I guess I can't post links, but it tells me I just have to reflash CWM) I think, "oh, I just have to reflash CWM. Not too hard!
I downloaded the GN toolkit and update to the latest CWM touch.
Attempted to reboot phone - nothing happens. All buttons unresponsive, no battery shows up when trying to charge. My laptop doesn't find it.
More Googling. I land on this page (link removed - GSM forums for legija's .bat unbrick fix thing), so I try plugging in my phone to my laptop without the battery, sure enough I see the OMAP 4460 device attempting to install. I follow the instructions and install the OMAP drivers, but when I plug in my phone it acts as if its being unplugged and replugged back in constantly. It won't stay connected for more than 3 or 4 seconds without reconnecting, so any attempts to try and use the .bat file fail
And so that's where I am. I have my phone plugged in right now incase for some reason it isn't charged, but I'm stuck. I hope I gave enough information for anyone to help me, thanks!

Sleete said:
[*]More Googling. I land on this page (link removed - GSM forums for legija's .bat unbrick fix thing), so I try plugging in my phone to my laptop without the battery, sure enough I see the OMAP 4460 device attempting to install. I follow the instructions and install the OMAP drivers, but when I plug in my phone it acts as if its being unplugged and replugged back in constantly. It won't stay connected for more than 3 or 4 seconds without reconnecting, so any attempts to try and use the .bat file fail[/list]
And so that's where I am. I have my phone plugged in right now incase for some reason it isn't charged, but I'm stuck. I hope I gave enough information for anyone to help me, thanks!
Click to expand...
Click to collapse
some also have had this issue "It won't stay connected for more than 3 or 4 seconds without reconnecting, so any attempts to try and use the .bat file fail"
but no, they've managed to do it in the end, it's just that you have to be ultra-quick
can you still get in fastboot/bootloader? if yes, flash latest twrp (i'm sure it supports encryption); if after flashing twrp it still doesn't work, flash google stock images by following the procedure here

Thought I should update this in case anyone else manages to hard-brick their phone, but I sent it in to Samsung and they replaced the entire mobo under warranty. I think they either didn't care or it was bricked enough where they couldn't tell I rooted it. Also good side effect of fixing the finicky USB port on my phone. Happy ending!

(FIXED) Samsung Galaxy Tab S 8.4 will not fully boot up.

I've had my Samsung Galaxy Tab S 8.4 (SM-T705Y) for just over two years now and it has worked brilliantly beside the odd issue here and there, including the device freezing from time-to-time. Each time that particular freezing issue has happened, I've used the 'Power and Volume Down buttons' technique and it has successfully fixed the issue.
Now, a few days ago, I was using my tablet for normal morning things; music app playing in the background, YouTube opened on the side, using the preinstalled Browser and Google Chrome apps, etc. I am not sure if it was updating any Google or Samsung apps at the time. The screen froze up so I left it for a few minutes, seeing if it would unfreeze. When it didn't, I used the same Power and Volume Down technique, which successfully forced-restarted the tablet. There was a small mistake I made doing this; I was holding down both the Power button and Volume Up button. It took me around thirty seconds to realise why the screen wasn't turning off and switched to the Volume Down button. At the time, both my earphones and the charging cord were connected.
However, upon the loading screen, I noticed that it did not pass the Samsung logo screen with the little explosion of blue circles and just kept replaying the same animation repeatedly. The Application History and Back buttons did not light up and the device did not vibrate as it normally does when it boots up. I repeated the Power-Volume Down technique to see if that would fix the issue. Once again, the tablet rebooted normally but was stuck at the logo screen playing the animation. I tried this same force-restart again, this time without the charger plugged in. No change.
So, I left it running through the animation while doing Google searches through forums and getting into contact with Samsung as to what the issue could be. I'll list down below what my tablet can and can't do at the moment and hopefully someone will have a clue as to what is going on and how to fix it. I will point out now that it was not going through a firmware update at the time, the device is not rooted and nor do I plan on taking that path with it, and I have not made any changes to it that can void the warranty.
It can:
- Recharge (The battery icon will show up if it is force-restarted and the charger is plugged in at the time.)
- Reboot (It's not exactly stuck in a bootloop, more of just the 'explosion' animation replaying over-and-over.)
- Enter Recovery Mode
It cannot:
- Enter Safe Mode
- Be Shut Down without the charger attached (As stated above, the device will only turn off with the Power-Volume Down buttons held for about 30 seconds and that causes the device to restart, not turn off. The only way for it to completely shut down is to have the charger connected and then unplug it after the battery icon appears.)
I have tried removing the SD card and placing it back in, power-cycling it, letting it run on the animation until the battery runs out and then letting it recharge to 100% before turning it on again, connecting it to Samsung Smart Switch (which recognises that there is a Samsung device connected, but not being able to register the device itself), and wiping the Partition Cache (Also note; the Recovery Mode has the 'No Command' sign with the android laying down and the red triangle with the exclamation point above it. Clearing the Partition Cache seemed to go smoothly, however when I chose the 'reboot device now' option, the 'No Command' sign changed to 'Error!' and rebooted the device anyway.) I am now currently trying another technique written on a different website (though since I am a new user, I cannot post up URLs at the moment). So far, plugging in the earphones alone hasn't worked and the device is currently connected to my laptop - which is shut off - and still has the earphones connected, but the animation is the only thing the screen is still showing.
I have important files saved in the internal storage of my Tab S and I do not have them backed up, which is the only issue that's stopping me from just going ahead and doing a Factory Reset as I cannot lose these files.
I am unsure if my Tab S is soft-bricked or if this is another issue entirely and I just missed something that could have already fixed it.
Yes, this is a long and detailed post, but hopefully with these details, someone will be able to help with this issue. If I can restore my Tab S to its condition before the freeze, that would be amazing, but I can definitely settle with only being able to salvage my files from the internal storage and then performing a Factory Reset on it.
Thank you in advance~

It might be a corrupt partition. The way i know involve rooting or the other one might format your device to factory setting.

edan1979 said:
It might be a corrupt partition. The way i know involve rooting or the other one might format your device to factory setting.
Click to expand...
Click to collapse
Really? I might look into that a bit more, thanks! With the second method you mentioned, how likely are the chances of it formatting the device to the factory settings?

AussieMouse said:
Really? I might look into that a bit more, thanks! With the second method you mentioned, how likely are the chances of it formatting the device to the factory settings?
Click to expand...
Click to collapse
download the official firmware and flash it via odin. it usually fix this type of problem. but usually the files on the internal storage/sdcard will be intact. only the data apps will be gone. this will not break your warranty (its already 2 yo device... no more warranty anyway ^_^)

edan1979 said:
download the official firmware and flash it via odin. it usually fix this type of problem. but usually the files on the internal storage/sdcard will be intact. only the data apps will be gone. this will not break your warranty (its already 2 yo device... no more warranty anyway ^_^)
Click to expand...
Click to collapse
Alright, I'll try that and let you know how it goes. Is there any specific website I should download the firmware (4.4.2 KitKat) from? (Yeah, I agree with you there! Still, just to be on the safe side~)

KIT KAT? ok that's old... hahaha... why dont you try MM. I think you can search for it at fw.updato.com probably can see all related firmware there.

edan1979 said:
KIT KAT? ok that's old... hahaha... why dont you try MM. I think you can search for it at fw.updato.com probably can see all related firmware there.
Click to expand...
Click to collapse
Haha Yeah, I'm not too fond of installing software updates due to past experiences~ I'll have a look around.

AussieMouse said:
Haha Yeah, I'm not too fond of installing software updates due to past experiences~ I'll have a look around.
Click to expand...
Click to collapse
MM is ok. I dont have any problem with it.

edan1979 said:
MM is ok. I dont have any problem with it.
Click to expand...
Click to collapse
Thank you so much for your help! I managed to find the KitKat 4.4.2 firmware on SamMobile and flashing it restored everything~

soft bricked from ota update

now, i have no idea if this is the actual definition of "soft bricked"... so ill just tell you my story.
ok... so a quick history... phone was never rooted... ota update in november caused the phone to reboot every time the screen went off. had to install "wakelock app" to make it usable... update in december caused the phone to not be able to turn on. im not sure what happened. started the update, let the phone sit for a little while... when i looked at it again... nothing. it was just dead. no buttons would turn it on. had to get a new phone. note 4 was a private purchase, so no warranty options.
after leaving the battery out for a week, it would turn on but get stuck on verizon screen, get real hot, and every 30 seconds, blip a vibrate and a screen flash.... so... i tried clearing cache, tried a FDR... nothing. so i basically tried what is on this page:
https://forum.xda-developers.com/no...mware-firmware-kernel-modem-recovery-t2942937
with the newest firmware through odin... i unzipped the file, put the phone in download mode, connected it, waited for blue box, browsed to tar.md5 in "ap" box, and hit start when ready. got an error, after a while, i pulled the battery, and now when i turn on in download mode it says "your device didnt update successfully. use the verizon software repair assistant on a computer to repair your device and complete the update"
kies does not recognize my phone... i can't find a software repair assistant. if i try to run odin again, it just gives me "complete(write) operation failed"
hoping i can figure out how to salvage this thing. not super hip to phone software. ive managed to root numerous phones in the past. this is the first time ive had an issue, and its with the first phone i didnt root.
thanks in advance. sorry if this is totally newb level stuff. i just really need help, and get lost real quickly trying to do my own research... but trust me, ive tried.

idiggplants said:
now, i have no idea if this is the actual definition of "soft bricked"... so ill just tell you my story.
ok... so a quick history... phone was never rooted... ota update in november caused the phone to reboot every time the screen went off. had to install "wakelock app" to make it usable... update in december caused the phone to not be able to turn on. im not sure what happened. started the update, let the phone sit for a little while... when i looked at it again... nothing. it was just dead. no buttons would turn it on. had to get a new phone. note 4 was a private purchase, so no warranty options.
after leaving the battery out for a week, it would turn on but get stuck on verizon screen, get real hot, and every 30 seconds, blip a vibrate and a screen flash.... so... i tried clearing cache, tried a FDR... nothing. so i basically tried what is on this page:
https://forum.xda-developers.com/no...mware-firmware-kernel-modem-recovery-t2942937
with the newest firmware through odin... i unzipped the file, put the phone in download mode, connected it, waited for blue box, browsed to tar.md5 in "ap" box, and hit start when ready. got an error, after a while, i pulled the battery, and now when i turn on in download mode it says "your device didnt update successfully. use the verizon software repair assistant on a computer to repair your device and complete the update"
kies does not recognize my phone... i can't find a software repair assistant. if i try to run odin again, it just gives me "complete(write) operation failed"
hoping i can figure out how to salvage this thing. not super hip to phone software. ive managed to root numerous phones in the past. this is the first time ive had an issue, and its with the first phone i didnt root.
thanks in advance. sorry if this is totally newb level stuff. i just really need help, and get lost real quickly trying to do my own research... but trust me, ive tried.
Click to expand...
Click to collapse
do a battery pull to shut off your phone then boot into download mode like normal unzip and flash this ( https://www.androidfilehost.com/?fid=24588232905720219 ) in the ap slot.

do a battery pull to shut off your phone then boot into download mode like normal unzip and flash this , link was here, in the ap slot.
OP, did you try this process listed above and did it fix your problem or did you something else? Thank you.

SPIRITJCC98 said:
do a battery pull to shut off your phone then boot into download mode like normal unzip and flash this , link was here, in the ap slot.
OP, did you try this process listed above and did it fix your problem or did you something else? Thank you.
Click to expand...
Click to collapse
nope, didnt work. was pretty pissed at the time. i had to give up and get a lgv20.

My Nexus 5X just died - question about warranty

Hello everyone,
to this day I was a happy owner of Nexus 5X - it was doing pretty well, I even installed Pure Nexus ROM on this device to make it even better and this is where the trouble begins. Today I was listening to music on my device when it froze. I was like - "yeah, another freeze, I will just reboot my phone". It didn't help. The phone started rebooting, but it froze again and then the screen went black. Forever. Now my device is not responding to any commands, I can not even charge it. I still have few months of warranty left, so this is where my question begins:
is it possible for LG employees to detect that my device was rooted and so to cancel my warranty if the phone is totally dead? I think that the components died.
Thanks for your help. :good:

I had the same thing happen to me 21 days after my warranty expired. They told me the motherboard was bad and it had to be replace, and it was going to cost $72. My device was fully rooted and they made no mention of that when I asked for the full diagnostic report from their technician. I would say it is safe to say they can't tell if it was rooted if you motherboard went out like mine.
- Side note: my phone crashes almost once a day since I've gotten back and had small cracks in the back from where they pried it open. But I can't go without my phone for another 3 weeks again while they fix it.

Razeer123 said:
Hello everyone,
to this day I was a happy owner of Nexus 5X - it was doing pretty well, I even installed Pure Nexus ROM on this device to make it even better and this is where the trouble begins. Today I was listening to music on my device when it froze. I was like - "yeah, another freeze, I will just reboot my phone". It didn't help. The phone started rebooting, but it froze again and then the screen went black. Forever. Now my device is not responding to any commands, I can not even charge it. I still have few months of warranty left, so this is where my question begins:
is it possible for LG employees to detect that my device was rooted and so to cancel my warranty if the phone is totally dead? I think that the components died.
Thanks for your help. :good:
Click to expand...
Click to collapse
Sounds TOO familiar. Like exactly what happened to my first N5X mid-March. I was listening to Spotify, the device's software froze and it never turned on again. I connected it to my PC and I happened to have the dreaded Qualcomm HS-USB QDloader 9008 error (that's what showed up in Device Manager). The only thing I did different and for the first time before that happened was using F2FS. I have no idea if it's related.

theGekkoST said:
I had the same thing happen to me 21 days after my warranty expired. They told me the motherboard was bad and it had to be replace, and it was going to cost $72. My device was fully rooted and they made no mention of that when I asked for the full diagnostic report from their technician. I would say it is safe to say they can't tell if it was rooted if you motherboard went out like mine.
- Side note: my phone crashes almost once a day since I've gotten back and had small cracks in the back from where they pried it open. But I can't go without my phone for another 3 weeks again while they fix it.
Click to expand...
Click to collapse
nirogu325 said:
Sounds TOO familiar. Like exactly what happened to my first N5X mid-March. I was listening to Spotify, the device's software froze and it never turned on again. I connected it to my PC and I happened to have the dreaded Qualcomm HS-USB QDloader 9008 error (that's what showed up in Device Manager). The only thing I did different and for the first time before that happened was using F2FS. I have no idea if it's related.
Click to expand...
Click to collapse
Today the diode started to blink red, I connected Nexus 5X to charger and waited ~30 mins to charge a bit. Then I wanted to flash stock system + recovery and unroot but when booting to recovery device again stopped on Google logo and went black. From this moment no sign of beeing alive. I think I'll wait to this situation to happen again and will try to install stock firmware.

Mine would flash red when the battery was completely drained. I could plug it in and get the battery logo, but if I tried to boot it up; the screen would hit to the Google logo and then just go black. I could wait a day and the red battery light would flash again when I pressed the power button. After a few times of doing this, it wouldn't even charge anymore.

Honestly I seriously doubt they have time to go Sherlock Holmes on your phone and void your warranty. They are most likely going to get your phone see if it boots, if not replace the motherboard and go on.
Not to mention if its not responding to anything at this point what do you have to lose. Send it in and see what happens.

This problem is frequent on the Nexus 5x, V10,V20,G4 and G5, the only issu is to use heat gun on the CPU, these devices will starts normally but the problem will appear again
Envoyé de mon HTC One_M8 en utilisant Tapatalk

Same thing happened to me
Same thing happened to me last night. I tried everything I could think of, I was running the latest stock Nougat version with no root and all of a sudden the device froze. After manually powering it down, I could not get it to boot up again. No LED, battery charging icon on the screen, nothing worked, so as it was still under warranty, I got in touch with someone at Google. They've sent me a replacement device that's set to arrive tomorrow and I am to return the faulty one free of charge. Luckily my Nexus 4 still works otherwise I would've missed several calls today. I suggest you get in touch and see what they say. I know of cases where despite the phone being rooted, if they were running stock the warranty was still applicable. With your device being completely dead, you really have nothing to lose.

Okay, update - I was able to reinstall stock firmware via Nexus Root Toolkit on this device, because I booted it into fastboot and it worked for few minutes. Bootloader is still unlocked - should I wait and lock it (I don't know when will my phone be accessible again, red diode is blessing right now because it boots when it's blinking) or should I send it to repair without worrying?

I would lock it.

Okay, yesterday I flashed stock ROM + unrooted and now I locked bootloader. However the device still seems to have something wrong inside - it shows that the custom OS is installed on my phone. Should I flash again or do you recommend something else?
It shows: "Your device has loaded a different operating system". (Yellow).
How can I get rid of it?

Welcome to the boot kingdom
Envoyé de mon HTC One_M8 en utilisant Tapatalk

Razeer123 said:
Okay, yesterday I flashed stock ROM + unrooted and now I locked bootloader. However the device still seems to have something wrong inside - it shows that the custom OS is installed on my phone. Should I flash again or do you recommend something else?
It shows: "Your device has loaded a different operating system". (Yellow).
How can I get rid of it?
Click to expand...
Click to collapse
Try flashing the latest stock package manually. No toolkits. Sometimes toolkits cause flashing issues.
Sent from my Nexus 5X

nirogu325 said:
Try flashing the latest stock package manually. No toolkits. Sometimes toolkits cause flashing issues.
Sent from my Nexus 5X
Click to expand...
Click to collapse
Thanks for your reply. I succesfully flashed the stock image as you said, but unfortunately I couldn't replace recovery - the phone died and can't boot since yesterday. I'm going to take it to LG service, so keep fingers crossed

Razeer123 said:
Thanks for your reply. I succesfully flashed the stock image as you said, but unfortunately I couldn't replace recovery - the phone died and can't boot since yesterday. I'm going to take it to LG service, so keep fingers crossed
Click to expand...
Click to collapse
No worries, you are in luck.

I tried it with oreo and nougat, but it did not work, it keeps freezing.