I've seen this happen over and over, actually it just happened to me again after going Happy Gilmore on some system edits. The typical reaction is to change kernel, restore a backup, etc. Here's a way that works without changing anything.
Wait 30 seconds after the message appears
Click close and then verify, by turning screen on and off, that the device is not frozen.
Open the battery door and take the battery out for 3 seconds
Replace the battery and cover
Hold volume down and press power, keeping the volume key pressed.
Select recovery using volume down, and press power.
Use volume down to scroll to Advanced
Press power to select.
Repeat selection process for wipe dalvik-cache, followed by fix permissions
Press back to return to the main menu, where reboot device should be selected.
Press power to reboot
Thank your Android device for complying.
This seems like a long process when written out, but this prevents the usual "how do I..." and "what order did you..."
All you did was check for kernel lock up, battery pull, reboot recovery, clear dalvik, fix permissions, and reboot.
Sent from my ADR6400L using Tapatalk
Thanks twisted. His is very useful info.
When they ask, and they DO ask, I simply tell them its one BAMF!
Wish I knew this earlier! Had to chat with Samsung support, who suggested I buy only Samsung OEM products (including Samsung sd card)and call them back. Did -- which meant more money, factory reset, reinstalling my 211 apps, and after installing Amazon AppStore, the problem started again. After pulling the battery, it usually worked, but who needs that! Ended uninstalling Amazon AppStore. Doesn't do it anymore. Now, I just use Google Play, but your solution would've been MUCH easier! Gonna keep it in mind if I have more issues. Thanked you.
From my Samsung Galaxy Note I717 on T-Mobile network
I'm assuming the above steps works on any phone (my sgs i9000) ?
I have just encountered that problem today, twice to be precise & so I can manage..
I'm wondering if it has to do with flashing zip file today (low storage notification zip file)
alright i fixed it on my phone. i did a full wipe. tell me if i need to explain how to do this. reflashed the ROM and gapps. when i went through the setup the first time there was an option to restore from google. it was checked by default. i left it checked. same problem... system process not responding... wiped and started over and reflashed ROM and gapps. unchecked restore google and it didnt come back. phone hasnt crashed since. the problem lies within the wifi passwords restore. the problem started when i was trying to start wifi. i dont know where to report the bug or i would. good luck and any questions? just quote this so i get an email and ill try to explain if this didnt make sense. hope it helped. if it did consider buying my buddy a beer who is a dev and needs a new computer. http://johntriger-development.yolasite.com/
[email protected] said:
alright i fixed it on my phone. i did a full wipe. tell me if i need to explain how to do this. reflashed the ROM and gapps. when i went through the setup the first time there was an option to restore from google. it was checked by default. i left it checked. same problem... system process not responding... wiped and started over and reflashed ROM and gapps. unchecked restore google and it didnt come back. phone hasnt crashed since. the problem lies within the wifi passwords restore. the problem started when i was trying to start wifi. i dont know where to report the bug or i would. good luck and any questions? just quote this so i get an email and ill try to explain if this didnt make sense. hope it helped. if it did consider buying my buddy a beer who is a dev and needs a new computer. http://johntriger-development.yolasite.com/
Click to expand...
Click to collapse
Yes it all makes sense.. (I'm experiencing problems with wifi..I "do not" want Google to restore my old/previous wifi password..
So should I untick restore Google..??
wifi was working brilliant before and now says "authenticate problem"
Sent from my blazing SGS-i9000 using Tapatalk 2
twistedumbrella said:
I've seen this happen over and over, actually it just happened to me again after going Happy Gilmore on some system edits. The typical reaction is to change kernel, restore a backup, etc. Here's a way that works without changing anything.
Wait 30 seconds after the message appears
Click close and then verify, by turning screen on and off, that the device is not frozen.
Open the battery door and take the battery out for 3 seconds
Replace the battery and cover
Hold volume down and press power, keeping the volume key pressed.
Select recovery using volume down, and press power.
Use volume down to scroll to Advanced
Press power to select.
Repeat selection process for wipe dalvik-cache, followed by fix permissions
Press back to return to the main menu, where reboot device should be selected.
Press power to reboot
Thank your Android device for complying.
This seems like a long process when written out, but this prevents the usual "how do I..." and "what order did you..."
All you did was check for kernel lock up, battery pull, reboot recovery, clear dalvik, fix permissions, and reboot.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
holy smokes
it worked on my samsung gt-i9003
thanks :good:
Great information!!
Thank you!
RBarnett09 said:
Great information!!
Thank you!
Click to expand...
Click to collapse
The OP instructions should read "volume up" (to boot into recovery mode).. Pressing volume down boots into download mode.. lol
Sent from my blazing SGS i9000 using Tapatalk 2
Roots said:
The OP instructions should read "volume up" (to boot into recovery mode).. Pressing volume down boots into download mode.. lol
Sent from my blazing SGS i9000 using Tapatalk 2
Click to expand...
Click to collapse
volume down gets the htc phones where they need to be, considering this is the thunderbolt forum, the info is correct
Sent from my ADR6400L using xda app-developers app
androidsupra said:
volume down gets the htc phones where they need to be, considering this is the thunderbolt forum, the info is correct
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
You beat me to saying it. Lol.
Sent from my ADR6400L using xda premium
rubicon86 said:
holy smokes
it worked on my samsung gt-i9003
thanks :good:
Click to expand...
Click to collapse
holy smokes :cyclops: they still talk like that in Hoboken
sam.balia1012 said:
holy smokes :cyclops: they still talk like that in Hoboken
Click to expand...
Click to collapse
Holy smokes you resurrected a really old thread ::cyclops::
Sent from my ADR6400L using Tapatalk 2
It seems that the dead are rising around here quite a bit. If it's the first sign of a zombie apocalypse, I'm going to wal-mart, they have food AND ammo. Lol
quickdraw86 said:
It seems that the dead are rising around here quite a bit. If it's the first sign of a zombie apocalypse, I'm going to wal-mart, they have food AND ammo. Lol
Click to expand...
Click to collapse
You're right about the food part but ammo is hard to come by here lately haha.
Sent from my ADR6400L using Tapatalk 2
quickdraw86 said:
It seems that the dead are rising around here quite a bit. If it's the first sign of a zombie apocalypse, I'm going to wal-mart, they have food AND ammo. Lol
Click to expand...
Click to collapse
what ammo?
THE day it comes in it leaves the shelves.... "Gun Control"
.. have to wait another week just for another shipment to come in
Roots said:
The OP instructions should read "volume up" (to boot into recovery mode).. Pressing volume down boots into download mode.. lol
Sent from my blazing SGS i9000 using Tapatalk 2
Click to expand...
Click to collapse
Just to be clear, it is volume down. Unless you are holding the phone upside-down.
I know that this is an old thread, but the problem still appears, and perhaps the following will be a clue for people who care about this problem:
I have it on various versions of 6.x running on a virtualbox VM, where the host is Windows 10 and for the moment the host only has 4GB of RAM, so I only gave 1GB to the VM. The thing is: i can make the problem go away just by giving the VM 1500MB of RAM.
I believe that what this "solution" and the darling one of this thread have in common is that they are ways to deal with a machine which doesn't have (quite) enough RAM -- is that accurate?
One practical consequence is that if you do all the clean-up suggested earlier, and that works, but the problem comes back too soon, you might do better to install more memory or do something that will use less memory PERMANENTLY., not just until the cache fills up again.
I have 16GB on order, and once it's here, i will allocate 4GB to the VM. If you don't see any edit here, it's because I'm too busy having fun with my running "Process system" (sic) to post here .
Related
What's up xda forums.had a couple of concerns with my phone. my nexus s stock running 2.3.2 rooted and unlocked. Here are some of my issues so far
While driving and on the phone, sometimes the call drops after making a nasty sound and stays stuck on the hanging up screen and I can't make or receive a call till I reboot.
When turning the phone off sometimes and turning back on, the screen hangs for a while and 4 seconds later ill feel the phone vibrate 2-3 times and go back to normal in which its not lagging.
When opening my gallery the phone takes about 5 seconds to show me my thumbnails of my photos.it does this every time. Also when I take pictures it takes about 10 seconds to see the photo I took. When talking on the phone I drop alot of.calls or I hear the person sound like a chipmunk lol.
Is my phone messed up? Is the stock rom messed up? I flashed a stock image thru clockwork after I tried a alpha cm7build. Was it corrupted or is my phone a pos. My nexus one never gave me this many problems.
Any help would be great
Sent from my Nexus S using XDA App
No one has had these problems?
thejedimex said:
No one has had these problems?
Click to expand...
Click to collapse
Well, yeah, most of your problems have been mentioned by someone here at one point or another. Some of them have workarounds, some are waiting for fixes from Google.
I think if you try a few searches with the search button in this and the General section you'll find already lengthy discussions on most of those issues.
These problems started after you flashed back to stock?
Try clearing caches and reflash I guess.
Sent from my Nexus S using XDA App
Hostile89 said:
These problems started after you flashed back to stock?
Try clearing caches and reflash I guess.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Maybe even a fastboot oem unlock again to force a TOTAL WIPE of the phone. Be careful, sdcard contents are wiped too.
distortedloop said:
Well, yeah, most of your problems have been mentioned by someone here at one point or another. Some of them have workarounds, some are waiting for fixes from Google.
I think if you try a few searches with the search button in this and the General section you'll find already lengthy discussions on most of those issues.
Click to expand...
Click to collapse
The only major issue I've had only happened once, and it happened for the first time yesterday: Without me touching the back button it started flashing and going back through the app I was in at great speed. It was rather frustrating but its only ever happened the one time.
What some people forget is that the Nexus One also had a lot of problems apon release,
All was ironed out by google
JD
distortedloop said:
Maybe even a fastboot oem unlock again to force a TOTAL WIPE of the phone. Be careful, sdcard contents are wiped too.
Click to expand...
Click to collapse
Im gonna try this right now. thanks for your help
I was able to make one of the problems repeat.. seems cause of the case i have everytime i hit the power button my thumb seems to hold down the volume rocker right in the middle. i then unlock the phone while its still tying to catch up from something.. cause 4 seconds later it will vibrate 2-3 times and the phone is back to reg speed.. there something wrong with my rom or can ya make this happen too?
Yup I get most of these issues too, it really spoils the experience. Next time I'm not gonna get a google phone straight upon release, it's really not worth the hassle. Also does anyone have problems with the wifi? Mine is horribly weak its a joke, struggles with wifi from my bedroom which my laptop and old Iphone 2g handled fine
Sent from my Nexus S using XDA App
Hey there, first post of the forum but long time follower. i was running paranoid android on my phone (new JB update with butter) and i got stuck when one day while using it, it fell into the notorious boot loop. it wouldnt enter download mode either so i ended up buying a jig that came in the mail today.....and now the phone will go into download mode for 3 seconds and loop over and over.....
please i really need this phone, if theres any way around it, it needs to be posted in this thread ASAP
TY
fckingtrippy said:
Hey there, first post of the forum but long time follower. i was running paranoid android on my phone (new JB update with butter) and i got stuck when one day while using it, it fell into the notorious boot loop. it wouldnt enter download mode either so i ended up buying a jig that came in the mail today.....and now the phone will go into download mode for 3 seconds and loop over and over.....
please i really need this phone, if theres any way around it, it needs to be posted in this thread ASAP
TY
Click to expand...
Click to collapse
If you pull out the battery and put it back did the phone automatically turn on by itself then keep rebooting?
Did you try 3 combo buttons to enter recovery vol up+dn and power then release power button but keep holding vol up+dn to enter recovery mod.
If the phone still keep bootlooping then it something wrong with Power button and may you need to replace that.
xxxSuperserieSxxx said:
If you pull out the battery and put it back did the phone automatically turn on by itself then keep rebooting?
Did you try 3 combo buttons to enter recovery vol up+dn and power then release power button but keep holding vol up+dn to enter recovery mod.
If the phone still keep bootlooping then it something with Power button and may you need to replace that.
Click to expand...
Click to collapse
yup turns on by itself and reboots constantly. 3 combo for recovery dont work.
fckingtrippy said:
yup turns on by itself and reboots constantly. 3 combo for recovery dont work.
Click to expand...
Click to collapse
Then something wrong with your Power buttons hardware need replacement for that.
:victory:
xxxSuperserieSxxx said:
Then something wrong with your Power buttons hardware need replacement for that.
Click to expand...
Click to collapse
:victory::victory::victory::victory::victory::victory::victory::victory::victory::victory:
so its not bricked
doesn't sound bricked but it could be tricky to fix. first you have to isolate any hardware problem with the volume or power buttons. maybe pull it apart and clean it. if the usb port is intact it should be salvageable.
one question.... would you sell it? i can always use a backup.
Sounds like power button...but like.dani said...you are not yet in the clear :/
But here's what worked for others:
Rapidly pressing/mashing power button
Taken it apart and blowing the power button area with air compressor
Paying $30 and sending it into some company to fix it
Sent from my HTC PH39100 using Tapatalk 2
I can help you. PM me tomorrow and I'll walk you thru it.
We should make a sticky thread for this issue!
http://www.youtube.com/watch?v=1WS5I0SpL6c
how to take it apart
Don't take it apart! Geez qk, lol.
Sent from my SGH-i997 using Tapatalk 2
EXPERIMENT said:
Don't take it apart! Geez qk, lol.
Sent from my SGH-i997 using Tapatalk 2
Click to expand...
Click to collapse
qkster said:
Click to expand...
Click to collapse
Did his infuse fixed?
Sent from my SGH-I997 using xda premium
xxxSuperserieSxxx said:
Did his infuse fixed?
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
We talked in PM but we have yet to get our meeting to fix it. I get the impression he's not in that big of a hurry...I don't know.
Maybe I'll just do a tutorial video to explain the steps...when I get some freetime.
If there is anyone else experiencing this issue you may PM me and I can try to help you if you'd like.
EXPERIMENT said:
We talked in PM but we have yet to get our meeting to fix it. I get the impression he's not in that big of a hurry...I don't know.
Maybe I'll just do a tutorial video to explain the steps...when I get some freetime.
If there is anyone else experiencing this issue you may PM me and I can try to help you if you'd like.
Click to expand...
Click to collapse
Highly appreciate sir if we have video tutorial I owned 3 infuses (me wife and son) my son's phone has this problem i talk to technician and he told it was power button hardware need replacement so I send it to their shop via usps and waiting for shipment back.
Sent from my Samsung Infuse 4G using XDA Premium
What exactly does the 'jig' do? Cause my infuse won't go into DL mode either
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
xxxSuperserieSxxx said:
Highly appreciate sir if we have video tutorial I owned 3 infuses (me wife and son) my son's phone has this problem i talk to technician and he told it was power button hardware need replacement so I send it to their shop via usps and waiting for shipment back.
Sent from my Samsung Infuse 4G using XDA Premium
Click to expand...
Click to collapse
OK. I'll try to get one done. Have a lot on my plate currently, plus my wife just got in an accident this morning so thats got me a little preoccupied. But as soon as I can I'll do one.
EXPERIMENT said:
OK. I'll try to get one done. Have a lot on my plate currently, plus my wife just got in an accident this morning so thats got me a little preoccupied. But as soon as I can I'll do one.
Click to expand...
Click to collapse
All the best wishes for your wife... all else can wait.
Regards.
Thank you, yeah everyone is fine. It could have been really bad. Almost a head on at 50mph. Some douche swerved into her lane and his mirror clipped her driver side window busting it out and breaking our mirror. Then when she pulled over, he just kept on going...
Pretty lame. But fortunately everyone is safe. She had 3 of our kids with her.
Recovery Bootloop Fix
fckingtrippy said:
Hey there, first post of the forum but long time follower. i was running paranoid android on my phone (new JB update with butter) and i got stuck when one day while using it, it fell into the notorious boot loop. it wouldnt enter download mode either so i ended up buying a jig that came in the mail today.....and now the phone will go into download mode for 3 seconds and loop over and over.....
please i really need this phone, if theres any way around it, it needs to be posted in this thread ASAP
TY
Click to expand...
Click to collapse
Alright well I don't know if this issue ever got resolved, we did speak but only once in PM but no follow up.
So I was going to make a video of the steps I took the first time I experienced this, where the install failed, phone would reboot back into recovering then the Android guy would fall over and it would reboot again back into recovery and repeating the process infinitely.
So the video I was gonna make explained some pretty indepth steps I took...and I have to admit I haven't wanted to make the vid because I didn't want to go thru the process again especially since I've been working on themes and wanted my phone up and running.
So. Here is something for you to try if you ever run into this problem
( I just had it happen again, and discovered this right before setting up the camera to do the before avoided video, lol )
Anyway it worked for me.
When it starts to recovery bootloop, 3 finger hold (power, vol up, vol down) keep holding while Samsung appears.
Continue to hold, Samsung will disappear, then when it reappears a second time release the buttons and you should enter recovery without a bootloop.
Then flash a different rom than the one that obviously gave you a bad flash.
Hope that helps some of you
X
I was on the phone earlier for a fair bit, when I hung up I noticed the battery at 4%. Got home little bit later and when I checked my phone again it was off, I hit the power button so it began to power on, and I them plugged it into AC charger right away while booting up. A couple of minutes later and I noticed it was still on the "One" boot screen (on a sense ROM at the moment, ViperXL 2.1.1). Tried holding power to reboot and it did the same thing.
Figured I leave it plugged in for a little bit, maybe battery was just really low. After about 30 minutes or so it was plugged in, still on the same screen (couldn't power it off it would just reboot). Tried to reboot again, and got stuck on the same screen. This time however I noticed the phone was quite hot, though it seems to be cooling down slightly since I've unplugged it, but not 100% sure.
What could be the issue/any ideas? I haven't flashed anything in over a week, last being ViperXL 2.1.1 and BeastMode Kernel 3.0. First time dealing with potential boot issues as I am always very careful when flashing. Any help is appreciated!
Try reading threads before you post. You may have read a thread that said don't post questions in General. There is a Q&A forum for this.
Anyways, try erasing the caches and rebooting.
Myrder said:
Try reading threads before you post. You may have read a thread that said don't post questions in General. There is a Q&A forum for this.
Anyways, try erasing the caches and rebooting.
Click to expand...
Click to collapse
Yeah I was thinking this might not be the right place but wasn't totally sure, I apologize.
I was having trouble getting it to boot into the bootloader as well, forgot to mention that originally, holding volume down and power wasn't working. However after not sure how many attempts I did get it somehow. Perhaps I was holding the buttons down incorrectly, I think I let go of power early the time it worked? Not sure. After a straight system reboot from recovery did not work, I tried wiping cache's as you said and it booted fine! Much thanks.
Again apologies from rushing to make a thread, just got kind of frustrated with not being able to boot into even the bootloader or just power it down for awhile, for seemingly no reason. Someone can delete this thread if they'd like. Thank you though!
maybe your phone doesnt like the overclock. not all phones can handle high overclocks and some cant work with ANY overclock. i would try letting the phone charge and flashing the stock boot.img
Songlambr37 said:
Who else in the world still use the manly Dell Venue?
who can help us upgrade it to 4.0?
Click to expand...
Click to collapse
I think you're lost
Songlambr37 said:
Who else in the world still use the manly Dell Venue?
who can help us upgrade it to 4.0?
Click to expand...
Click to collapse
Wtf,.. This is second thread I've seen that in,..
WR
Sent by WR's One XL
Chrysis said:
I was having trouble getting it to boot into the bootloader as well, forgot to mention that originally, holding volume down and power wasn't working. However after not sure how many attempts I did get it somehow. Perhaps I was holding the buttons down incorrectly, I think I let go of power early the time it worked? Not sure.
Click to expand...
Click to collapse
Almost always a matter of pilot error (as long as you have a charge light coming on, it should go to hboot no problem). Correct way is to hold vol down rocker, don't let it go, then press the power button for 3 seconds or so. Release the power button (but keep holding vol down). Don't let go of vol down until the hboot screen comes up.
If the screen is on, you can do the same as above, with the only change being: holding the power button down for 5 seconds or so until the capacitive buttons flash, then release the power button.
WarRaven said:
Wtf,.. This is second thread I've seen that in,..
WR
Sent by WR's One XL
Click to expand...
Click to collapse
I'm on it.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my Galaxy Note (i717), using XDA Premium.
Chrysis said:
Yeah I was thinking this might not be the right place but wasn't totally sure, I apologize.
I was having trouble getting it to boot into the bootloader as well, forgot to mention that originally, holding volume down and power wasn't working. However after not sure how many attempts I did get it somehow. Perhaps I was holding the buttons down incorrectly, I think I let go of power early the time it worked? Not sure.
Click to expand...
Click to collapse
Future reference to boot into.downloader...
-lock screen like you would be putting phone in pocket
-hold power + vol down unroll screen goes off
-let go of POWER BUTTON ONLY right after screen goes off and continue holding vol down.
You'll boot into downloader just fine.
Sent from my HTC One XL cellular device over clocked to 1.9Ghz
Sorry to resurrect a slightly old thread, but was there any solution to this? My phone just died last night and won't start back up. It just stays stuck on the loading screen. I went into recovery and deleted the caches just in case, but it hasn't fixed anything. I have a nandroid backup from a weeks ago that I can just if I have to, but I'd prefer not to since I'd lose the app data.
Any ideas?
Valohtar said:
Sorry to resurrect a slightly old thread, but was there any solution to this? My phone just died last night and won't start back up. It just stays stuck on the loading screen. I went into recovery and deleted the caches just in case, but it hasn't fixed anything. I have a nandroid backup from a weeks ago that I can just if I have to, but I'd prefer not to since I'd lose the app data.
Any ideas?
Click to expand...
Click to collapse
Reading the thread says wiping caches worked for the OP.
Sent from my One X using xda app-developers app
Ah right missed that. Didn't work for me unfortunately. Would re-flashing the ROM without wiping work?
Valohtar said:
Ah right missed that. Didn't work for me unfortunately. Would re-flashing the ROM without wiping work?
Click to expand...
Click to collapse
That was going to be my next suggestion. Its your best bet if you don't want to lose all of your app data.
Sent from my One X using xda app-developers app
I am not rooted on this phone I am on stock 100% I have done nothing with this phone since purchased.. I did not try to install anything on this phone that could have caused this. But yesterday it just started on this bootloop. The screen just shows the T-mobile sidekick 4g logo then to black and over and over .... I have pulled the battery put it back in and it immediately bootloops. I don't even have to power on . It even bootloops with the charger plugged in the battery symbol bootloops. I tried to put the device into bootloader (pwr vol up/dwn) to do a factory reset. but the bootloader screen just flashes on for a second and then it goes right back into the bootloop.
It appears as if this is bricked but how is that possible on a stock device? I called t-mobile and they could not help. All they wanted to do is sell me a new phone.
Please help
Use heimdall n hold the volume buttons n enable flash bootlaoders
Sent from my SGH-T959V using xda app-developers app
@karose465 How old is the phone? If less than a year (doubtful), it should still be under warranty. Or you may be eligible for upgrade pricing: Fore example, "Customers with a Classic plan (two-year contract) are eligible for our lowest upgrade price on a new phone when at least 22 months have passed since their last phone upgrade. A new two-year contract is required to take advantage of best upgrade pricing. Of course, you can always upgrade a phone at any time, regardless of how many months have passed since your contract began."
For more info on Heimdall, just Google Heimdall Android.
Anyone with a sidekick contract ends earliest next march..
karose465 said:
I am not rooted on this phone I am on stock 100% I have done nothing with this phone since purchased.. I did not try to install anything on this phone that could have caused this. But yesterday it just started on this bootloop. The screen just shows the T-mobile sidekick 4g logo then to black and over and over .... I have pulled the battery put it back in and it immediately bootloops. I don't even have to power on . It even bootloops with the charger plugged in the battery symbol bootloops. I tried to put the device into bootloader (pwr vol up/dwn) to do a factory reset. but the bootloader screen just flashes on for a second and then it goes right back into the bootloop.
It appears as if this is bricked but how is that possible on a stock device? I called t-mobile and they could not help. All they wanted to do is sell me a new phone.
Please help
Click to expand...
Click to collapse
Try Odin...choose repartition and you're golden. This is someone that has bricked his phone many, many times. Odin will give you the original stock Froyo.
RicAndroid said:
Try Odin...choose repartition and you're golden. This is someone that has bricked his phone many, many times. Odin will give you the original stock Froyo.
Click to expand...
Click to collapse
I think for him and myself, the biggest problem is being unable to get the phone to stay in download mode. For some reason, the battery won't charge and the phone itself continously turns off and on when plugged in. So the charge isn't holding, therefore nothing will stay on/open.
Im having the same problem. I have searched everywere and cannot find an answer that will fix it. If anyone can please help us fix this issue.
Sent from my MyTouch 4G using xda premium
gamingwiz said:
Im having the same problem. I have searched everywere and cannot find an answer that will fix it. If anyone can please help us fix this issue.
Sent from my MyTouch 4G using xda premium
Click to expand...
Click to collapse
I did some forum searching and found this. Hope it helps.
http://forum.xda-developers.com/showthread.php?t=1477838
Thanks ill check into that
Sent from my HTC Glacier using xda premium
karose465 said:
I am not rooted on this phone I am on stock 100% I have done nothing with this phone since purchased.. I did not try to install anything on this phone that could have caused this. But yesterday it just started on this bootloop. The screen just shows the T-mobile sidekick 4g logo then to black and over and over .... I have pulled the battery put it back in and it immediately bootloops. I don't even have to power on . It even bootloops with the charger plugged in the battery symbol bootloops. I tried to put the device into bootloader (pwr vol up/dwn) to do a factory reset. but the bootloader screen just flashes on for a second and then it goes right back into the bootloop.
It appears as if this is bricked but how is that possible on a stock device? I called t-mobile and they could not help. All they wanted to do is sell me a new phone.
Please help
Click to expand...
Click to collapse
Hmm here is a link with for the ODIN and also provides some pretty cool roms that you might like to try.
http://forum.xda-developers.com/showthread.php?t=1538576
---------- Post added at 04:33 PM ---------- Previous post was at 03:41 PM ----------
karose465 said:
I am not rooted on this phone I am on stock 100% I have done nothing with this phone since purchased.. I did not try to install anything on this phone that could have caused this. But yesterday it just started on this bootloop. The screen just shows the T-mobile sidekick 4g logo then to black and over and over .... I have pulled the battery put it back in and it immediately bootloops. I don't even have to power on . It even bootloops with the charger plugged in the battery symbol bootloops. I tried to put the device into bootloader (pwr vol up/dwn) to do a factory reset. but the bootloader screen just flashes on for a second and then it goes right back into the bootloop.
It appears as if this is bricked but how is that possible on a stock device? I called t-mobile and they could not help. All they wanted to do is sell me a new phone.
Please help
Click to expand...
Click to collapse
Hmm here is a link with for the ODIN and also provides some pretty cool roms that you might like to try.
http://forum.xda-developers.com/showthread.php?t=1538576
Took the phone apart, put everything back. Still no luck
Sent from my HTC Glacier using xda premium
EpicLordPhone said:
Took the phone apart, put everything back. Still no luck
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Dead thread but this is your answer - Your power button is shot. Need to have a new one put on. I know your problem has been fixed / replaced but for others still searching for answers...you need a power button repair.
Power Button Repair relating to Boot Loop
MythEdge said:
Dead thread but this is your answer - Your power button is shot. Need to have a new one put on. I know your problem has been fixed / replaced but for others still searching for answers...you need a power button repair.
Click to expand...
Click to collapse
my Sidekick 4G is very old and just now went into bootloop... i googled the word and came across this forum.
As quoted above by previous poster that a power button repair was needed... I figured that I had nothing to lose, it being so old, I smashed the crap out of the Sidekick 4G on its power button. Lo and Behold, it booted into the system successfully.
SO... if no one has any qualms about smashing the crap out of their power button... give it a shot. It worked for me.
MythEdge said:
Dead thread but this is your answer - Your power button is shot. Need to have a new one put on. I know your problem has been fixed / replaced but for others still searching for answers...you need a power button repair.
Click to expand...
Click to collapse
Thanks for the info, but is there anyway I could turn it on without the power button?
Sent from my Amazon Kindle Fire2 using xda app-developers app
EpicLordPhone said:
Thanks for the info, but is there anyway I could turn it on without the power button?
Sent from my Amazon Kindle Fire2 using xda app-developers app
Click to expand...
Click to collapse
I don't believe so ?
You can switch the power button to like the track pad or something but you need to edit the phones ettings somehow
Sent from my SGH-T839 using xda app-developers app
immorality said:
I don't believe so ?
You can switch the power button to like the track pad or something but you need to edit the phones ettings somehow
Sent from my SGH-T839 using xda app-developers app
Click to expand...
Click to collapse
Hmmm thanks, I might just try that!
Sent from my Amazon Kindle Fire2 using xda app-developers app
Mines stuck in a boot loop too.
I don't know if my Sidekicks problem is related to this or not. I rooted it and flashed it over to Glorious Overdose v5 on May 22nd this year and it's been running great. At least it was until last Friday, Sep 13. I was having trouble connecting to the WiFi at my house so I rebooted the phone. When it started to come back up a female voice started saying, "VooDoo lagfix has been disabled." "Converting /data and /system partitions." "Conversion time estimated 10 minutes."
I let it do it's thing and that's all it's been doing all weekend. I can get into recovery mode, I've tried restoring the phone from my backup with no success. I've even tried running through the process of setting up GOv5 again and it says it's successful, but the phone never boots up. It just stays in the same blasted bootloop and saying the same things over and over again about VooDoo. I've checked the VooDoo logs and there is an error file for the 13th and the logs following say "conversion." Can someone point me in the right direction as to what I can do to get my phone working again? Everything I've tried to research so far hasn't worked.
v5 hold both volume button, the track button and power button. Should put you into recovery mode. If not, you will have to put phone into download mode. You do this by taking out battery, then pluging into computer. When you reinsert battery hold volume down and power, if I remember correctly, and your download screen should come up. From your cp manually unroot it. Then it should be fixed, and just reroot it. I hope this was helpful
Sent from my SGH-T839 using xda app-developers app
No idea what I'm doing, precisely, but...
MythEdge said:
Dead thread but this is your answer - Your power button is shot. Need to have a new one put on. I know your problem has been fixed / replaced but for others still searching for answers...you need a power button repair.
Click to expand...
Click to collapse
Hey, MythEdge. I'm not sure if you get notifications here or anything, but I registered to this site specifically to thank you; my phone ( Sidekick 4G, like OP ) bricked, and I smashed it against the table a few times ( you know, delicately... ) and it resurrected.
So thank you, sir; you were precisely correct. It worked on both of my phones, which had the exact same problem.
Just, wow. Thank you.
LathyrusRoots said:
Hey, MythEdge. I'm not sure if you get notifications here or anything, but I registered to this site specifically to thank you; my phone ( Sidekick 4G, like OP ) bricked, and I smashed it against the table a few times ( you know, delicately... ) and it resurrected.
So thank you, sir; you were precisely correct. It worked on both of my phones, which had the exact same problem.
Just, wow. Thank you.
Click to expand...
Click to collapse
And almost a year later I log in and see this. Your most welcome. I haven't been working on phones for awhile but if I remember right, some models can be powered on by plugging the phone into a power source and when the phone vibrates or has a sign of life unplugging the unit. Some cables don't work and sometimes doing this via a computer can power up a device. Other than that, the other more dangerous way is to short out the pins on the bottom of the unit. I don't remember the pins but you can google a charge port diagram to help. I don't recommend doing this unless you have absolutely no other choice. Incidentally, this is why a phone will power itself on when a battery is put in and no other button is touched. The port is wet and corrosion has caused a link on the power pin and believe its pin 3. A simple cleaning with 90%+ rubbing alcohol solution will fix if cleaned quick enough.
Out of nowhere my power button magically no longer works. Kind of a huge deal since I use my phone for work a TON. At first I thought it was the ROM but then I rebooted into recovery and discovered it doesn't work in there either...... but by some sort of miracle though my phone magically boots itself up when I swap batteries in it....
I am rooted and running Beans 20.
Any help/ideas would be greatly appreciated!!
Sent from my SCH-I535 using Tapatalk 2
You can get an app called button savior from Google play that allows you to create on screen keys to turn off your screen.
Various xposed modules allow you to remap your physical keys. If you don't know about the xposed framework I highly suggest looking into it.
Furthermore I believe some custom roms have key mapping built in.
Sent from my QMV7A using Tapatalk
ImUnderTheBed said:
You can get an app called button savior from Google play that allows you to create on screen keys to turn off your screen.
Various xposed modules allow you to remap your physical keys. If you don't know about the xposed framework I highly suggest looking into it.
Furthermore I believe some custom roms have key mapping built in.
Sent from my QMV7A using Tapatalk
Click to expand...
Click to collapse
Yes I already got an app that will shut my screen off and lock it but what happens when my phone stops magically booting up all by itself??
Then I'm screwed.
:crying::crying:
flooritnfly said:
Yes I already got an app that will shut my screen off and lock it but what happens when my phone stops magically booting up all by itself??
Then I'm screwed.
:crying::crying:
Click to expand...
Click to collapse
Mine started doing the same thing.
flooritnfly said:
Out of nowhere my power button magically no longer works. Kind of a huge deal since I use my phone for work a TON. At first I thought it was the ROM but then I rebooted into recovery and discovered it doesn't work in there either...... but by some sort of miracle though my phone magically boots itself up when I swap batteries in it....
I am rooted and running Beans 20.
Any help/ideas would be greatly appreciated!!
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
My power button just started malfunctioning too. I'm on Odin barebones 4.1.2 stock and the problem persists.
It sounds like a lot of people are getting this problem. If you use that knowledge to your advantage, I've heard people convince Samsung it's a manufacturing problem and got it repaired outside of Warranty. The power button itself is sautered onto the motherboard, so unless you really trust a mobile repair company, best option is work directly with Samsung.
That being said, I'm going to look for an Xposed Framework module that can remap the power button.
I looked for one, didn't really find what I was looking for... selling mine on ebay now to pay for my new phone...
Sent from my HTC6525LVW using xda app-developers app
Wow. My power button just stopped working also.
My phone is stock.
I did replace the glass myself a couple months ago and it's been working fine until about a week ago. Was wondering if that had anything to do with it.
Interesting to see I'm not the only one having issues.
Kind of timely now that the S5 is coming out this week.
usho said:
Wow. My power button just stopped working also.
My phone is stock.
I did replace the glass myself a couple months ago and it's been working fine until about a week ago. Was wondering if that had anything to do with it.
Interesting to see I'm not the only one having issues.
Kind of timely now that the S5 is coming out this week.
Click to expand...
Click to collapse
This is happening to a lot of people. I'm sure the s4 will start having this problem followed by the s5 after a year and some months. Im done with samsung phones until they start using different parts. Actually thinking about the next nexus phone and hack a msata drive into it with a custom vacume formed case. The only reason I haven't owned one is because of the storage limitation. I think a 200+ gigabyte msata strapped to the back would fix that problem.
tmettler5 said:
Mine started doing the same thing.
Click to expand...
Click to collapse
sweeds said:
My power button just started malfunctioning too. I'm on Odin barebones 4.1.2 stock and the problem persists.
It sounds like a lot of people are getting this problem. If you use that knowledge to your advantage, I've heard people convince Samsung it's a manufacturing problem and got it repaired outside of Warranty. The power button itself is sautered onto the motherboard, so unless you really trust a mobile repair company, best option is work directly with Samsung.
That being said, I'm going to look for an Xposed Framework module that can remap the power button.
Click to expand...
Click to collapse
usho said:
Wow. My power button just stopped working also.
My phone is stock.
I did replace the glass myself a couple months ago and it's been working fine until about a week ago. Was wondering if that had anything to do with it.
Interesting to see I'm not the only one having issues.
Kind of timely now that the S5 is coming out this week.
Click to expand...
Click to collapse
Hey guys, mine originally starting messing up on Saturday, and then Sat night and all day Sun is was fine, and now it is doing it again. I even installed a new rom and it is still doing it so now I am convinced it is purely physical and not rom-related. What are you guys going to do?
I have the Wireless Phone Protection for my phone and am thinking about using that to my advantage to get a new device....question is I've never done it before. If I say I have a physical problem with my phone then won't Verizon want it returned? That will make me have to unroot it and bring it back to out of box state which is a big headache. What if I just say I lost it or it got stolen? Am I better off going that route?
EDIT: Also forgot to mention that along with these power button issues my S3 also will not reboot on its own. If I select Reboot (be it from the power button menu, notification pulldown, etc) it will just shut off and not reboot.....but if I yank the battery and put it back in it will then reboot to recovery. Same deal if I do a normal reboot, haven to yank and replace battery. You guys having these issues too?
So a couple of days ago my power button started acting wonkie as well. I would push it and it basically acted sticky. I would push once but it would register twice or as a long press. Either turning the screen on and off or bring up the reboot menu. So I did the xposed button remapping. Worked pretty well, but if I restarted the phone it would do a weird haptic feedback thing every couple of seconds before finally booting up.
So I wasn't satisfied with just living with it being a hardware issue. So I downloaded latest cleanrom to flash from cm11. I rebooted recovery and now it just vibrates every couple of seconds. Would not make it to twrp. It will get to cm Samsung boot screen but then just goes back to vibrating black screen. I took out battery and popped out power button but same results.
Any suggestions? Think power button can be fixed by repair shop or is it time to go back to my trusty droid incredible until I can upgrade.
Sent from my Nexus 7 using xda app-developers app
luland said:
So a couple of days ago my power button started acting wonkie as well. I would push it and it basically acted sticky. I would push once but it would register twice or as a long press. Either turning the screen on and off or bring up the reboot menu. So I did the xposed button remapping. Worked pretty well, but if I restarted the phone it would do a weird haptic feedback thing every couple of seconds before finally booting up.
So I wasn't satisfied with just living with it being a hardware issue. So I downloaded latest cleanrom to flash from cm11. I rebooted recovery and now it just vibrates every couple of seconds. Would not make it to twrp. It will get to cm Samsung boot screen but then just goes back to vibrating black screen. I took out battery and popped out power button but same results.
Any suggestions? Think power button can be fixed by repair shop or is it time to go back to my trusty droid incredible until I can upgrade.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
It can be fixed. There is also a way of temporarily making the power button work but I don't feel like explaining it again. If you do some searching there are at least 20 threads that have the temp fix in it.
ThePagel said:
It can be fixed. There is also a way of temporarily making the power button work but I don't feel like explaining it again. If you do some searching there are at least 20 threads that have the temp fix in it.
Click to expand...
Click to collapse
Link to the temp fix please?
Sent from my SCH-I535 using Tapatalk