hey everyone!
my phone went a little crazy by randomly shutting off while using cm10 so I decided to restore to a stock non-root nandroid I made around 8 months ago. Everything went well up until the point I rebooted: I unwittingly had set up a text lockscreen password that I had since then forgotten (who remembers passwords from 8 months ago?!). So I went in CWM, did a factory data reset and rebooted. I turned off the screen and turned it back on to BAM! the lockscreen again... And the fracked up thing is that there isnt even a "forgot password" gmail confirmation option thing at the bottom so I'm completely locked out of my phone! Is there anything I can do other than buy that $4 screen lock bypass exploitation app??
Any help would be greatly appreciated!
h2whoa said:
hey everyone!
my phone went a little crazy by randomly shutting off while using cm10 so I decided to restore to a stock non-root nandroid I made around 8 months ago. Everything went well up until the point I rebooted: I unwittingly had set up a text lockscreen password that I had since then forgotten (who remembers passwords from 8 months ago?!). So I went in CWM, did a factory data reset and rebooted. I turned off the screen and turned it back on to BAM! the lockscreen again... And the fracked up thing is that there isnt even a "forgot password" gmail confirmation option thing at the bottom so I'm completely locked out of my phone! Is there anything I can do other than buy that $4 screen lock bypass exploitation app??
Any help would be greatly appreciated!
Click to expand...
Click to collapse
Maybe try another factory reset (sucks I know) and this time after boot go into security settings and turn off the screen lock before your screen turns off. If you just try and change the password you'll be prompted for the old one first. That being said, I haven't used stock in so long I can't promise this will work either.
Those random reboots you got with CM10 were common with older versions and the other variants such as Pacman, Slimbean, etc, but the latest one I haven't had that happen and I've been using it a week. I only say this because stock is just makes this phone crawl IMO.
ArtfulDodger said:
Maybe try another factory reset (sucks I know) and this time after boot go into security settings and turn off the screen lock before your screen turns off. If you just try and change the password you'll be prompted for the old one first. That being said, I haven't used stock in so long I can't promise this will work either.
Those random reboots you got with CM10 were common with older versions and the other variants such as Pacman, Slimbean, etc, but the latest one I haven't had that happen and I've been using it a week. I only say this because stock is just makes this phone crawl IMO.
Click to expand...
Click to collapse
Haha, thanks, not an absolute fix but at least it works. Kinda strange since I read that CWM factory resets wipes out everything including lockscreen passes... And my phone wasn't rebooting, it would just shut off randomly, battery would drain at horrifying speeds (from 99% to 0 after a 7 minute phone call) (I also had the latest ver). I was thinking that I could maybe restore stock rom and send it back to samsung or provider since its still under warranty
EDIT: I'm gonna try Samsung Remote Screen Unlock and see if that works. Plus I just checked my battery: It's as swollen as Rosie O'donnell at Mandarin, which explains the crappy battery life.
h2whoa said:
Haha, thanks, not an absolute fix but at least it works. Kinda strange since I read that CWM factory resets wipes out everything including lockscreen passes... And my phone wasn't rebooting, it would just shut off randomly, battery would drain at horrifying speeds (from 99% to 0 after a 7 minute phone call) (I also had the latest ver). I was thinking that I could maybe restore stock rom and send it back to samsung or provider since its still under warranty
EDIT: I'm gonna try Samsung Remote Screen Unlock and see if that works. Plus I just checked my battery: It's as swollen as Rosie O'donnell at Mandarin, which explains the crappy battery life.
Click to expand...
Click to collapse
If you're rooted you can remove gesture.key using adb shell but I forget where exactly it is. Google it
Sent from my Nexus 7 using xda app-developers app
h2whoa said:
Haha, thanks, not an absolute fix but at least it works. Kinda strange since I read that CWM factory resets wipes out everything including lockscreen passes... And my phone wasn't rebooting, it would just shut off randomly, battery would drain at horrifying speeds (from 99% to 0 after a 7 minute phone call) (I also had the latest ver). I was thinking that I could maybe restore stock rom and send it back to samsung or provider since its still under warranty
EDIT: I'm gonna try Samsung Remote Screen Unlock and see if that works. Plus I just checked my battery: It's as swollen as Rosie O'donnell at Mandarin, which explains the crappy battery life.
Click to expand...
Click to collapse
Hate to hear that and you're not the only one to mention swollen batteries around here lately either. Good luck to you!
theAPANT said:
If you're rooted you can remove gesture.key using adb shell but I forget where exactly it is. Google it
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
yeah... can't root, need this phone to be as stock as can be if I'm to get it replaced (or at least the battery). Btw, Is there a way to possibly remove CWM in case they check recovery?
PS: Totally irrelevant but I keep reading about a CM10.1 rom for this phone; I've searched far and wide but I can't seem to find it! Could anybody point me in the right direction?
h2whoa said:
yeah... can't root, need this phone to be as stock as can be if I'm to get it replaced (or at least the battery). Btw, Is there a way to possibly remove CWM in case they check recovery?
PS: Totally irrelevant but I keep reading about a CM10.1 rom for this phone; I've searched far and wide but I can't seem to find it! Could anybody point me in the right direction?
Click to expand...
Click to collapse
Yes the easiest way to get rid of cwm is to flash the stock file. Go to http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G there are, i believe two methods, one using Odin the other flashing something in recovery. Just read. As for cm10.1 camcory is working on it so is smartguy. Even i compiled it but it doesn't boot all the way. Check insomniaforums.org that is probably where it will be posted
Sent from my Nexus 7 using xda app-developers app
CM10.1 boots fine and runs smooth but not yet ready for release. There is a few broken items in it I believe if I recall but cannot restore it due to limited battery till I get home to verify what was wrong. Be patient and when ready public will know about it.
Sent from my SGH-T679 using xda premium
afwolfpacked said:
CM10.1 boots fine and runs smooth but not yet ready for release. There is a few broken items in it I believe if I recall but cannot restore it due to limited battery till I get home to verify what was wrong. Be patient and when ready public will know about it.
Sent from my SGH-T679 using xda premium
Click to expand...
Click to collapse
Bluetooth and camera dont work. I'm saying my own personal build doesn't boot yet but I'm trying some stuff. Right now I'm working on aokp 4.1.2 to get that fixed all the way, mainly because i like aokp and I'm stuck on 4.2.2
Sent from my Nexus 7 using xda app-developers app
Related
is there anyway to go back to 1.13.516 software? after the update ive been having bluetooth issues....seen here.
after the update i have a major problem......bluetooth resets the wireless radio.......whenever bluetooth is on my radio bars go to a red X then starts back up. The bluetooth also resets......it will do this about every 45 seconds if the bluetootb stays on......anyone else having this problem?.....btw this just started after the update BTW, ive done 3 hard reset hoping that was the issue but it wasnt....verizon CC suggests taking it to a retail store but i had going in there.....any suggestions
Doing a factory should do that as it should reset it to factor rom stored in bootloader. Then ignore the update.
However keep in mind they claim that the update helps fix the screen flicker issues.
Sent from my DROIDX using XDA App
Big Dawg 23 said:
Doing a factory should do that as it should reset it to factor rom stored in bootloader. Then ignore the update.
However keep in mind they claim that the update helps fix the screen flicker issues.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
ive gone 3 hard resets and it does not put it back to the original rom
Only way to do this is to wait for someone to post it, so far I have not been able to locate it, but eventually (hopefully soon enough) someone will post it.
You might try and go into recovery and do a factory reset from there, I was having some other troubles and found that doing it that way helped tremendously.
genesis72 said:
Only way to do this is to wait for someone to post it, so far I have not been able to locate it, but eventually (hopefully soon enough) someone will post it.
You might try and go into recovery and do a factory reset from there, I was having some other troubles and found that doing it that way helped tremendously.
Click to expand...
Click to collapse
Yea i've done a factory wipe....didn't help
I need to do this too. I've only had my X for a short 12 hours, but this update has really hosed things up. I've notice:
- wireless causes imstability: (random reboots,slow response times, system and phone not responding to anything)
- connectivity issues: even in 3G areas web and market fail and need to be restarted. With 1x connectivity txt messages wont go through.
- general instability: screen unresponsive or buttons on screen looking as if they're presses but nothing happens. Cannot wake phone from standby.
Sent from my DROIDX using XDA App
So,i found that it was the exchange sync that was really hurting everything. I changed from push sync to every 15 min. I haven't tried wifi yet. But my battery life and overall speed have improved significantly.
Sent from my DROIDX using XDA App
Big Dawg 23 said:
Doing a factory should do that as it should reset it to factor rom stored in bootloader. Then ignore the update.
However keep in mind they claim that the update helps fix the screen flicker issues.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Factory reset on any android phone does not change the ROM version.
try a different bt headset. i am using an old samsung wep150 and have no.issues at all. the only issue i have is the spacebar will put in a period with no space if i start typing to fast. and i turned all spell check and punctuation features off.
Sent from my DROIDX using the XDA mobile application powered by Tapatalk
yeah try a diff headset
Hey,
I have Verizon droid 3 running up in Canada, and its been working fine...however it recently started having issues with the touchscreen.
Basically the screen works normally 3% now, otherwise it only works when the keyboard is open to just above the first row of keys.
If I touch the screen while the keyboard is fully open it wont respond, but when I go back to the working position it will respond to a touch made while fully open (ie; I pressed ok after typing, it didn't submit until I closed the keyboard to the working position, like a delayed response).
It seems like a software issue, but I already hard reset.....
Any ideas? I don't want to change this phone after only 5 months (no Verizon warranty here!)..
Thanks,
--CP
Sent from my XT883 using xda app-developers app
CrazyPhil said:
Hey,
I have Verizon droid 3 running up in Canada, and its been working fine...however it recently started having issues with the touchscreen.
Basically the screen works normally 3% now, otherwise it only works when the keyboard is open to just above the first row of keys.
If I touch the screen while the keyboard is fully open it wont respond, but when I go back to the working position it will respond to a touch made while fully open (ie; I pressed ok after typing, it didn't submit until I closed the keyboard to the working position, like a delayed response).
It seems like a software issue, but I already hard reset.....
Any ideas? I don't want to change this phone after only 5 months (no Verizon warranty here!)..
Thanks,
--CP
Sent from my XT883 using xda app-developers app
Click to expand...
Click to collapse
Which ROM are you on, stock or a custom one?
Its a long shot, but I have odd touchscreen issues when plugged into cheap power sources (inverters, etc). You may want to check the battery - pop it out for a bit, put it back in, maybe try someone else's, etc...
Sent from my DROID3 using xda app-developers app
Phibernaut said:
Its a long shot, but I have odd touchscreen issues when plugged into cheap power sources (inverters, etc). You may want to check the battery - pop it out for a bit, put it back in, maybe try someone else's, etc...
Sent from my DROID3 using xda app-developers app
Click to expand...
Click to collapse
Haha ya I have odd touchscreen issues when I get to 100% battery and am still plugged in :cyclops:
adamskub said:
Which ROM are you on, stock or a custom one?
Click to expand...
Click to collapse
I believe it's stock-ish, I don't remember what I flashed 5 months ago, think I just changed the radio.img:
57.1.60.XT883.ChinaTelecom.en.CN
XT883
2.3.4
n_16.18.16s
2.6.35.7-g790a33c / [email protected] #1
SLNCT-57.1.60
Thanks,
--CP
CrazyPhil said:
I believe it's stock-ish, I don't remember what I flashed 5 months ago, think I just changed the radio.img:
57.1.60.XT883.ChinaTelecom.en.CN
XT883
2.3.4
n_16.18.16s
2.6.35.7-g790a33c / [email protected] #1
SLNCT-57.1.60
Thanks,
--CP
Click to expand...
Click to collapse
Oh ok, then I'm not really sure. I would, if you want, try and flash right back to complete stock and see if your having the same troubles. If you are then it's almost guaranteed to be a hardware problem. However, if the problem doesn't persist then it could have just been some weird bug or glitch that happened. I've had some weird things happen a week or so after a flash and it was software related.
But all this would be having you do a reflash either through CWM/Safestrap or sbf and then you lose everything you have (Though you can backup & restore apps via Titanium Backup). So if you don't end up reflashing I understand
Also does this happen only at certain times/intervals say when your charging? Hope this helps!
Edit: I looked at the orig post at work and forgot to look at it again. A hard reset should be able to fix it, but you never know. I would recommend a reflash and see what happens. Sorry I can't be more help
I hate you. I read your post yesterday and thought "huh, that's really weird and unfortunate." I woke up today and the same thing is happening to me. I haven't flashed anything since April. It was totally out of the blue.
Mine only works when the screen is slid open bout half a centimeter, not even enough to force the screen to rotate.
Sent from my DROID3 using xda premium
That's exactly what's happening....It's been like this for a week. However, it sometimes works when I left it for the night to charge...or randomly, but full functionality lasts only a few minutes.
has there been any update on this status? im trying to fix a friends with the same problem.
Chaunton said:
has there been any update on this status? im trying to fix a friends with the same problem.
Click to expand...
Click to collapse
I think that is bad luck and your digitizer is stopped working.
ugynok said:
I think that is bad luck and your digitizer is stopped working.
Click to expand...
Click to collapse
I'm in the same train
It's strange.
Yesterday my touchscreen it was completely unresponsive the whole day.
stock rom, everything untouched
i rebooted it a million times. closed or open make no difference.
today, it is working amazingly
what was the difference? nothing at all! it layed on my desk all night
i don't understand how the digitizer can go between perfect condition and not working as it wish.
Hi all I read these forums every night and dont think I have seen anyone that has this issue? (Touchscreen controlling itself)
Sorry about quality I only have 2 hands
I am stock ROM, no root and locked boot loader (I have tried custom ROMs get same issue)
P.S it happens randomly and is fixed for an undetermined amount of time after a reboot
https://www.youtube.com/watch?v=x2wpnIQs6tI&feature=youtube_gdata_player
Sent from my GT-I9300 using xda premium
rosebud said:
Hi all I read these forums every night and dont think I have seen anyone that has this issue? (Touchscreen controlling itself)
Sorry about quality I only have 2 hands
I am stock ROM, no root and locked boot loader (I have tried custom ROMs get same issue)
P.S it happens randomly and is fixed for an undetermined amount of time after a reboot
https://www.youtube.com/watch?v=x2wpnIQs6tI&feature=youtube_gdata_player
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Hmmmmmm it could be a hardware issue, maybe the digitizer wiring is faulty or some contacts on the screen are bad and causing shorting. Ive only ever gotten ghost touches from heat but nothing like what your video shows haha its like its possessed!
Sorry all. I forgot to make the video public. Should work now.
I'm thinking this is a hardware issue. What do you think?
I have turned on developer options and show touch option so when it does it again I will see exactly where its detecting input
Sent from my GT-I9300 using xda premium
Did you get any moisture in it? I was using my Nexus outside and if a snowflake landed on it it would register as a touch. Does tilting it have any effect on the phantom touches?
Sent from my Nexus 7 using Tapatalk HD
If it's plugged in, screen is dirty, and potentially if there is a screen protector on, all of those could potentially cause weirdness.
If none of those things, and a factory reset doesn't fix it, warranty it.
Thanks for your replies, I have been from stock to rooted and back effectively factory resetting twice, but I did reset again last night for good measure. I'm a clean freak when it comes to my tablet, use a lint free cloth on the thing regularly. the video was recorded after picking the device up after a period (whole day) of none use. Since turning on the developer options, sods law it hasn't happened again.. I was hoping it would point out for me where the input is detected. When it first happened it was clicking random things in Facebook.. I thought some app had hijacked my device!, its been happening for weeks.. But until now as it only happens a couple of times a day I have rebooted and shrugged my shoulders.. But as you can imagine it is getting rather irritating.. I'll see how I get on and warranty it if neccesary
Steve
Sent from my Nexus 7 using XDA Premium HD app
rosebud said:
... When it first happened it was clicking random things in Facebook.. I thought some app had hijacked my device!, its been happening for weeks.. But until now as it only happens a couple of times a day I have rebooted and shrugged my shoulders.. But as you can imagine it is getting rather irritating.. I'll see how I get on and warranty it if neccesary ...
Click to expand...
Click to collapse
It has been mentioned here a # of times, descriptive terms varied and there's another youtube video floating here - don't freak out b/c I went thru that myself with the older 16G WiFi model - to the point where I shut down the wireless router, change the IP & LAN address and zipped up the firewall settings tightly just to be sure, and, even turned put the N7 into airplane mode, and checked to make sure that Bluetooth & NFC were not turned ON or left on, etc. (It's like the N7 is running in a Remote Terminal mode when IT used "logmein" to take over our desktop when one of the update patches stalled ...)
Stock Rom was worst for me, 4.1.2 was better vs. 4.2.x but some of the newer custom Rom like "Smooth" were not as crazy as PA, which seemed to be in an endless loop ... I've returned it to local Staples & exchanged it for a (paid upgrade) new 32GB WiFi model - warranty work is definitely indicated (return the device to stock & lock up the bootloader, etc. & do a factory reset to clear everything before boxing it away)
Good luck.
ok so i got my htc one a couple of days ago and it sees to have a serious problem!
Basically the phone goes through stages of random vibrating every few mins to full on constant vibrating like there is a fan or motor buzzing in there. It even does it if the phone is switched off! Ive just had an episode of it vibrating no stop for 10 mins, didnt make a difference when i switched it off or when i factory reset it!
It seems to overheat or something and only stopped doing it after i had just left it for a while. I have tried to speak with htc about it but they were useless and had no suggestions what soever.
I really need some help here, i bought the phone privately and to all intense purposes it seemed like brand new
hpsauce37 said:
ok so i got my htc one a couple of days ago and it sees to have a serious problem!
Basically the phone goes through stages of random vibrating every few mins to full on constant vibrating like there is a fan or motor buzzing in there. It even does it if the phone is switched off! Ive just had an episode of it vibrating no stop for 10 mins, didnt make a difference when i switched it off or when i factory reset it!
It seems to overheat or something and only stopped doing it after i had just left it for a while. I have tried to speak with htc about it but they were useless and had no suggestions what soever.
I really need some help here, i bought the phone privately and to all intense purposes it seemed like brand new
Click to expand...
Click to collapse
SO you CAN NOT exchange the phone?
if not... root your phone and flash different rom that should resolve problem...at least give it a try!
99piotrek said:
SO you CAN NOT exchange the phone?
if not... root your phone and flash different rom that should resolve problem...at least give it a try!
Click to expand...
Click to collapse
No cant exchange it, only option i might have if i cant get the problem ressolved on here would be to send it to htc for repair but can take up to 2 weeks.
when i got the phone it was still on 4.1 and told me update available to 4.2 so i did that. Thats all i have done , apart from unlocking it from 02 using a code.
its almost like on a computer when its being worked hard etc that you here the fan cut in, thats what it seems like except it sounds like the buzz you get when you first start the phone. sometimes it does this just once every few mins or so, other times it will start doing it and not stop...even when switched off.....everything else on the phone seems to work fine
hpsauce37 said:
No cant exchange it, only option i might have if i cant get the problem ressolved on here would be to send it to htc for repair but can take up to 2 weeks.
when i got the phone it was still on 4.1 and told me update available to 4.2 so i did that. Thats all i have done , apart from unlocking it from 02 using a code.
its almost like on a computer when its being worked hard etc that you here the fan cut in, thats what it seems like except it sounds like the buzz you get when you first start the phone. sometimes it does this just once every few mins or so, other times it will start doing it and not stop...even when switched off.....everything else on the phone seems to work fine
Click to expand...
Click to collapse
Did the device get wet at some point? Sounds like a hardware problem if a factory reset didn't solve the problem.
There's a slight chance it could be a real bad app or an issue with the rom. Maybe running a stock RUU for your device if you can find it might help.
Pretty sure it hasent got wet .
Would be happy to put stock Rom back on it but not sure how I go about reflashing it .
Don't know if this normal or not but when I did a factory reset I thought the device would be wiped completely, all my pictures and videos etc however when I set it back up again I found some videos on there still that I had downloaded to the phone off the net.
Maybe it's not wiping itself correctly either?
Sent from my HTC One using xda premium
hpsauce37 said:
Pretty sure it hasent got wet .
Would be happy to put stock Rom back on it but not sure how I go about reflashing it .
Don't know if this normal or not but when I did a factory reset I thought the device would be wiped completely, all my pictures and videos etc however when I set it back up again I found some videos on there still that I had downloaded to the phone off the net.
Maybe it's not wiping itself correctly either?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Resetting the device should wipe everything and bring it to the same condition as new.
Go to settings>>Backup & Reset>>Reset phone>>now check "Erase all data", then tap "OK".
If that doesn't work, try to do a factory reset from the bootloader.
hpsauce37 said:
Pretty sure it hasent got wet .
Would be happy to put stock Rom back on it but not sure how I go about reflashing it .
Don't know if this normal or not but when I did a factory reset I thought the device would be wiped completely, all my pictures and videos etc however when I set it back up again I found some videos on there still that I had downloaded to the phone off the net.
Maybe it's not wiping itself correctly either?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Factory reset will wipe the device but leave the contents of the sdcard untouched which explains why your vids are still there
Appreciate the help guys, thankyou
So, is there any benifit to wiping the device completely over and above what I've done allready?
Today the phone has just done the odd sudden vibration as if you were just booting up, around 5 times in total, nowhere near as bad as last night, don't know why that would be.
Would it be possible to reflash standard firmware?
Is so how would I do it. Phone is completley standard and was in 4.1 prior to the ota update to 4.2, could 4.2 be the problem?
Sent from my HTC One using xda premium
rider5512 said:
Factory reset will wipe the device but leave the contents of the sdcard untouched which explains why your vids are still there
Click to expand...
Click to collapse
IC, but you do have the option to erase the sdcard (storage) from the reset phone menu in settings.
farang4u said:
IC, but you do have the option to erase the sdcard (storage) from the reset phone menu in settings.
Click to expand...
Click to collapse
Yes, I see there is a box to tick to wipe everything.
Think it's worth doing?
Sent from my HTC One using xda premium
hpsauce37 said:
Yes, I see there is a box to tick to wipe everything.
Think it's worth doing?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
I'd try it. You can back up your pics and music on your PC via HTC Sync first.
Ok so I have tried it but no joy
Still getting the random buzzing/vibration for no apparent reason.
Could it be a bug with the update to 4.2.2?
Can I go back to 4.1?
I'm at my witts end with this now
Sent from my HTC One using xda premium
hpsauce37 said:
Ok so I have tried it but no joy
Still getting the random buzzing/vibration for no apparent reason.
Could it be a bug with the update to 4.2.2?
Can I go back to 4.1?
I'm at my witts end with this now
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Don't think it's a bug with 4.2.2 but a hardware issue.
Couple of other things to try ; download "CID Getter" from the play store, run it and find out your device's CID number. Now search on Google or xda for the RUU for your device's CID number. Download the RUU.exe to your pc, connect your phone to the pc and run the RUU.exe. This will bring the phone back to stock 4.1..
Or you can unlock the bootloader and flash another rom. Step by step instructions can be found on xda
Sorry, don't know of any easy solutions.
Sent from my HTC One using xda app-developers app
farang4u said:
Don't think it's a bug with 4.2.2 but a hardware issue.
Couple of other things to try ; download "CID Getter" from the play store, run it and find out your device's CID number. Now search on Google or xda for the RUU for your device's CID number. Download the RUU.exe to your pc, connect your phone to the pc and run the RUU.exe. This will bring the phone back to stock 4.1..
Or you can unlock the bootloader and flash another rom. Step by step instructions can be found on xda
Sorry, don't know of any easy solutions.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
thanks for sticking with me on this :good:
I have just followed a a video on here on how to unlock the bootloader and s-off and root - so now good to go
not sure how i put a new firmware on here now though..going to have to do a bit more reading....
i think to start with ill try downloading standard htc 4.1 rom when i can figure out which one it is and how i put it on and then go from there.
ok so just to update this....
last night i have tried the standard google edition rom on my phone and for the first few hours all seemed fine untill 4am this morning when i was woked by the phone doing its random vibrating thing...it was just sat by the side of my bed on charge
Can only think it must be a hardware issue now...but still dont know what or what is triggering it
hpsauce37 said:
ok so just to update this....
last night i have tried the standard google edition rom on my phone and for the first few hours all seemed fine untill 4am this morning when i was woked by the phone doing its random vibrating thing...it was just sat by the side of my bed on charge
Can only think it must be a hardware issue now...but still dont know what or what is triggering it
Click to expand...
Click to collapse
You tried everything so it's has to be a hardware issue. Maybe the vibration starts when the device gets warm. Sorry we couldn't fix it.
Sent from my HTC One using xda app-developers app
farang4u said:
You tried everything so it's has to be a hardware issue. Maybe the vibration starts when the device gets warm. Sorry we couldn't fix it.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
My HTC one has been doing the same thing. Vibrating randomly even when powered down. Brought it back to Sprint and had them order me a new phone. The only way to stop it from vibrating when powered down was to bang it on a hard surface, then it would stop. Crazy!
Vibrating non stop
My HTC One had been vibrating cotinuously too. I kept slapping the upper part of the phone to stop it from vibrating. However, this worked for the initial few days only. Later, it continued to vibrate continuously without stopping at all ! In the night I left the phone in the other room while it was still vibrating and the next morning the phone wouldn't charge at all! Now the phone is not booting/ charging. It is dead! Any leads?
EDIT: I slapped the upper part again, it suddenly woke up from the dead! It is charging now, the LED is red too!! But it is still continuously vibrating. I have left it to charge as of now, but please help with this vibrating problem. Any ideas?
I've had the same issue with my M7 today.
There were no software updates or any new apps lately.
It all emerged when i was pressing the home button (to exit from some app) and at the same time an incomming call started.
I have tried:
switching it off - did not help
Changing volume setting silent\vibe\sound a couple of times - no effect
Soft reset - no help
Hard reset - no help
Slapping with upper side of the phone against my had - helped for some time, the it started again
Seems like hardware issue.
Currently working solution for me:
Switch off the option "Vibrate on keypress" in Settings ==> Sound & notification
UPD: had to turn off all the vibrations
So far so good. Apparently there is some issue with vibe motor, and it just does not stop. I assume that by disabling that option it is not getting started and thus no constant vibe follows.
UPD 2 Fixed:
Issue reoccurred on hitting the device against my palm.
Had to disassemble it, there are a couple of instructions on youtube, i used plastic cards.
Motor was spinning even with a switched off device. Had to unplug and plug the motor a couple of times and it helped.
Turned on all vibrations in settings, no issues so far.
Hope that helps.
I've recently come across a new issue on my T-mobile Galaxy Note 4 that I haven't seen before. I've been searching online as well and can't seem to find anyone else posting about this problem either. I'm not the best but I have some experience. I've recently rooted and flashed tekxodus hybrid n4 5 1 1 rom on my note 4 through TWRP recovery. It took a few tries but everything worked. After using it for 3 days, I decided to turn it off and hard reboot it which I've done plenty of times before. But this time, upon rebooting it starts up and shows the tmobile logo screen and turns black. Vibrates twice as if you plugged it into the charger but remains black, and stays that way. If i plug it into the charger it shows the green battery screen and charges normally. I can enter twrp recovery and download mode as well. But it just can't get past the logo screen. I've also tried using a different note 4 battery from other videos, clearing the cache, delvik-cache, but nothing seems to work. As earlier mentioned, I can't seem to find any other post with this exact problem so I've come to reddit for help. Thank you in advance for any feedback.
You try flashing backup/ Odin stock?
yah its weird when u reboot through the menu. Just take out battery for like 10 seconds and put it back in
Sent from my SM-N910T3 using Tapatalk
Bruce lee roy said:
You try flashing backup/ Odin stock?
Click to expand...
Click to collapse
Yeah, unfortunately that's what I had to do. I was trying to figure any other option other than having to reflash everything. Thanks for the tip though
ayeitschris said:
yah its weird when u reboot through the menu. Just take out battery for like 10 seconds and put it back in
Sent from my SM-N910T3 using Tapatalk
Click to expand...
Click to collapse
Yeah, I knew since I could still get into TWRP Recovery and download mode I'd still be able to reflash stock roms. After I did, I did notice that the first "T-Mobile" logo screen lasted a bit longer than it did while it was messed up. I'm still not entirely sure what went wrong, but my only guess is that Tekxodus roms incorporate a app called synapse(possibly rom specific). I think I changed options in it which allowed me to overclock the cpu. I did reboot it a number of times after I set that up, but maybe something was stepped on through game editing apps which create/change app data. But it definitely pays to have back-ups to everything. Thanks for the reply too btw
Try flashing another kernel, sounds like that could be the culprit
JonakaJon said:
Yeah, I knew since I could still get into TWRP Recovery and download mode I'd still be able to reflash stock roms. After I did, I did notice that the first "T-Mobile" logo screen lasted a bit longer than it did while it was messed up. I'm still not entirely sure what went wrong, but my only guess is that Tekxodus roms incorporate a app called synapse(possibly rom specific). I think I changed options in it which allowed me to overclock the cpu. I did reboot it a number of times after I set that up, but maybe something was stepped on through game editing apps which create/change app data. But it definitely pays to have back-ups to everything. Thanks for the reply too btw
Click to expand...
Click to collapse