help! phone not getting any power? - Verizon HTC One (M8)

so I installed unicon from the playstore, activated it in xposed, rebooted, applied an icon theme, rebooted again and my phone locked up on the htc screen. I held power off until it shut off and now my phone will not turn on at all. ive held power and volume up, ive held power and volume down, ive held just power... ive plugged the phone into the charger and its not even showing the charge light...any suggestions? im starting to get a little nervous.. ive had plenty of problems w/ my android phones when running custom stuff but never to the point of not even getting the screen to turn on...

Powell730 said:
so I installed unicon from the playstore, activated it in xposed, rebooted, applied an icon theme, rebooted again and my phone locked up on the htc screen. I held power off until it shut off and now my phone will not turn on at all. ive held power and volume up, ive held power and volume down, ive held just power... ive plugged the phone into the charger and its not even showing the charge light...any suggestions? im starting to get a little nervous.. ive had plenty of problems w/ my android phones when running custom stuff but never to the point of not even getting the screen to turn on...
Click to expand...
Click to collapse
Man, these S-OFF M8's are dropping like hot cakes..
I wonder if Verizon is somehow behind this and going to push an OTA to break S-OFF exploit and leaving us screwed with a refurb and no way to root/S-OFF.

Man that sucks .. Sorry man : ( 
 @Andy What could big red have done to be behind this?

Ditto that @andybones . So many threads about bricks lately from very minor things/tweaks. Doesn't make any sense. Something isn't right
Sent from my HTC6525LVW using Tapatalk

andybones said:
Man, these S-OFF M8's are dropping like hot cakes..
I wonder if Verizon is somehow behind this and going to push an OTA to break S-OFF exploit and leaving us screwed with a refurb and no way to root/S-OFF.
Click to expand...
Click to collapse
I got mine to come back on... thankfully before I read your post, otherwise I woulda went into shear panic
If it is something to do with Verizon then pulling my SD Card and SIM Card and it coming on after that makes sense. I tried everything I could think of before that and said well... cant think of anything else so i'll pull the sim and sd card, initially it did nothing, but then I just taped the power button a few times and it kicked on and booted up. inserted the sim card and sd card and all has been fine. im scared to turn it off though.
EDIT: so I took the chance, I wanted to backup after the scare.. everything went fine.. still weary about rebooting but the 1st one went ok.

Powell730 said:
I got mine to come back on... thankfully before I read your post, otherwise I woulda went into shear panic
If it is something to do with Verizon then pulling my SD Card and SIM Card and it coming on after that makes sense. I tried everything I could think of before that and said well... cant think of anything else so i'll pull the sim and sd card, initially it did nothing, but then I just taped the power button a few times and it kicked on and booted up. inserted the sim card and sd card and all has been fine. im scared to turn it off though.
EDIT: so I took the chance, I wanted to backup after the scare.. everything went fine.. still weary about rebooting but the 1st one went ok.
Click to expand...
Click to collapse
So you're saying that removing the Sim card may have let your phone boot? That's f'd up.
Sent from my HTC6525LVW using Tapatalk

wtoj34 said:
So you're saying that removing the Sim card may have let your phone boot? That's f'd up.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Possibly, i obviously have no proof. it may have been a coincidence, but once I removed the sim it booted.
Sent from my HTC6525LVW using XDA Free mobile app

Powell730 said:
Possibly, i obviously have no proof. it may have been a coincidence, but once I removed the sim it booted.
Sent from my HTC6525LVW using XDA Free mobile app
Click to expand...
Click to collapse
There's very little big red could do to surprise me right now. Could someone more knowledgeable on the topic of how Sim cards function and their limit to how they can interact with a phone chime in?
Sent from my HTC6525LVW using Tapatalk
---------- Post added at 06:09 PM ---------- Previous post was at 05:41 PM ----------
I am convinced Verizon is causing these random phones dropping dead. Got me thinking about the xlte. That's gotta communicate directly with the Sim. Could there be something in that? Also gotta bring up the my verizon root perms. I'm completely speculating I have very little knowledge on this territory.
Sent from my HTC6525LVW using Tapatalk

I can chime in - that would never happen. A SIM card is just a memory card.

There's another thread about this same thing. Either in the Verizon M8 forum or the regular M8 forum. Don't remember which one. Anyway, in the end, that person ended up pulling just the sdcard and the phone booted up. Put it back in and it wouldn't boot. He/she then formatted the card on a Windows computer, put it back in and it booted up. Makes me wonder if your problem wasn't due to the sdcard too. You might consider backing up the contents of it on a computer. Just in case.

Related

Help 2 dead inspires within 2 weeks!!

Okay I bought my first Inspire in march for 6 months it was great.. No problems at all... Then 3 weeks ago it died on me.. I plugged it up and no lights or anything came on.. So I did a battery pull.. When I put the battery back in it made 5 or 6 vibrating pulses but that was it... So I called ATT they said battery as bad and sent me a new one.. I got it 3 days later and put it in.. I got the same 5 or 6 pulses.. So now after being without a phone for 4 days I was pissed.. So I drove to ATT they tried diffrent batteries and chargers with no success so they had the warranty dept send me a new one.. I got it 2 weeks ago and now it died just like my first one.. except I left it took apart for 2 days nd now when I plug it up the red LED actually lights up but still all it will do is vibrate..
Also Ive tried doing a hard reset by holding volume down and power for 10 seconds but still dont get any response.. Is there any hope oth than going through warranty again??
---------- Post added at 04:53 AM ---------- Previous post was at 04:19 AM ----------
Little update: Actually I just unplugged it and the LED stays solid red even while not on charge
Have you installed a new app lately that was recent right b4 you get the error. Sounds like your boot sector is becoming corrupt. Or you have insanely bad luck. Unless someone has a better idea
sent from my Inspire 4G running ClearDroid 1.1.51
No I honestly dont use the market alot the last app I installed was like 2 weeks before the first one died.. The app was netflix BTW.. And I did not reinstall it to the new device..
Im calling ATT today to have them send me a new one I guess..
It's possible you received a bad phone. Are you rooting your phone or no? My stepdads just did that and I know its none of the above I set up all his stuff and didn't root him. Just running through possible issues before you have to deal with them more
sent from my Inspire 4G running ClearDroid 1.1.51
Nope neither were ever rooted.. And yeah im kinda worried its going to do it again.. I went 6 months with no problems then all of a sudden 2 die the same way?? I just dont get it
Not saying both phones were bad because it happens sometimes. But usually when it does happen you have to look at the common factors. Since you already tried different batteries and chargers, what about the sd card or sim card? Have you tried to boot phone without either inserted?
I also see you mentoned the netflix app. Is it possible you may have over heated your phone playing videos?
Agoattamer said:
I also see you mentoned the netflix app. Is it possible you may have over heated your phone playing videos?
Click to expand...
Click to collapse
but he didn't install netflix on the second one, so that can't be the common denominator
The Universe is Cracked, The Pandorica will Open, Silence will Fall
Do you have anything setup to run at bootup that could be causing issues.
The Universe is Cracked, The Pandorica will Open, Silence will Fall
Agoattamer said:
Not saying both phones were bad because it happens sometimes. But usually when it does happen you have to look at the common factors. Since you already tried different batteries and chargers, what about the sd card or sim card? Have you tried to boot phone without either inserted?
I also see you mentoned the netflix app. Is it possible you may have over heated your phone playing videos?
Click to expand...
Click to collapse
Well like Capt Nero said I never put netflix on the second phone.. I only had it for 2 weeks so I didnt really get any of my old apps installed..
And I have tried booting with no sim and no SD card but it still wont do anything..
Captain_Nero said:
Do you have anything setup to run at bootup that could be causing issues.
The Universe is Cracked, The Pandorica will Open, Silence will Fall
Click to expand...
Click to collapse
I never set anything up run at boot.. the only thing I could think might have done that would be lookout security but again that never made it to the second phone..
I really dont think I just got 2 bad phones.. Im almost positive it has to be somthing on my end but I just cant figure it out..
Lookout security is known to cause problems with phones on at&t my friend had 4 phones go out with it. Stopped using it no problems on her current phone.
Edit/addition: lookout could be what killed first phone. And then you just got a bum replacement. Or you could have a virus running rampant on your SD card that is killing your boot sector and phone.
sent from my Inspire 4G running ClearDroid 1.1.51
Hiyabuz said:
Lookout security is known to cause problems with phones on at&t my friend had 4 phones go out with it. Stopped using it no problems on her current phone.
Edit/addition: lookout could be what killed first phone. And then you just got a bum replacement. Or you could have a virus running rampant on your SD card that is killing your boot sector and phone.
sent from my Inspire 4G running ClearDroid 1.1.51
Click to expand...
Click to collapse
Never had any issues w/ Lookout.
I es just speaking out of experience of going and arguing with the warranty counter with my friend 4 times. And tx aren't you rooted. Your kernel and Rom could not have any issues like the ota and ATT Rom can have with it.
sent from my Inspire 4G running ClearDroid 1.1.51
Okay well I got my 3rd Inspire in the mail today.. I noticed 2 things.. 1 this one is a different color.. Not the red one but its a darker grey.. Second the red notifaction LED I said the second one had is NOT the regular amber charging LED.. I didnt even notice untill I plugged the new one up..
Ill try to get the light to come back on and take a pic.. Anyone know anything about this second LED???
Oh and im going to format my SD before putting it in the new phone and also not installing lookout.. I cant keep going without a phone

BRICKED after deleting a file !!! HELP PLEASE...

Ok, so I had recently flashed MIUI sense based, I realized it wasn't for me so I restored my backup of TrickDroid 6.1. After doing this I went through and decided to delete some some stuff because my space was getting low (not 5mb low, more like maybe 1/2gb), I went to delete the MIUI v4 2.7.6 file and the phone appeared to go into standby... I tried to wake it up again with no luck. Plugging it into a charger does nothing, no red light; no green light. I'm unable to get into bootloader mode, no matter how long I hold down the "down volume + power" combo or any variation of it.
I need one of the gurus to help please !!!!
maybe post this in general or q&a?
any adb connection? if it's in standby then you may be able to move along to the next step
could just be a SOD (sleep of death)
Sent from my HTC One S using xda premium
calming said:
Ok, so I had recently flashed MIUI sense based, I realized it wasn't for me so I restored my backup of TrickDroid 6.1. After doing this I went through and decided to delete some some stuff because my space was getting low (not 5mb low, more like maybe 1/2gb), I went to delete the MIUI v4 2.7.6 file and the phone appeared to go into standby... I tried to wake it up again with no luck. Plugging it into a charger does nothing, no red light; no green light. I'm unable to get into bootloader mode, no matter how long I hold down the "down volume + power" combo or any variation of it.
I need one of the gurus to help please !!!!
Click to expand...
Click to collapse
Did u try hold the power? It'll reboot?then hold volume down about 10s.it should go to bootloader
2nd Option: use all-in-one tool kit.it has a command to reboot.
And don't post question or help here.read the rule.
Sent from my HTC One S using xda premium
Sorry about posting in this section, I assumed I'd get a quicker response.
I tried the All-In-One Kit thing... doesn't work "error: device not found"
I cannot get the phone to power on at all, no bootloader, no splash screen, nothing recognized by my pc. I get a "QHUSB_DLOAD NO DRIVER FOUND"
Thoughts?
calming said:
Sorry about posting in this section, I assumed I'd get a quicker response.
I tried the All-In-One Kit thing... doesn't work "error: device not found"
I cannot get the phone to power on at all, no bootloader, no splash screen, nothing recognized by my pc. I get a "QHUSB_DLOAD NO DRIVER FOUND"
Thoughts?
Click to expand...
Click to collapse
If it can't boot or use adb command.i think u should contact with HTC for helps,or at least where u buy the mobile. And of couse u still have Warranty.
It may be a hardware problem.We here can only try if it is a software problem.at ur position,the device can't be recognized by Computer/Laptop (before this,it worked well right?),then i think bad luck.
Don't be despair, it'll have some way to solve.
Sent from my HTC One S using xda premium
Sorry to tell you man the same thing just happened to me. I just got a replacement from T-Mobile. You will not get that thing back on. Just call T-Mobile and tell them it won't power on nor will it charge. It's funny because I was adding music to mine when it happened. If it happened the same way mine did then you will notice it was really hot when it shut off. The MDJ kernel overheated the Processor and killed it. Once that happens the device is a useless brick. I'm trading my replacement for another phone because this phone happens to overheat a lot.
Azuske said:
Sorry to tell you man the same thing just happened to me. I just got a replacement from T-Mobile. You will not get that thing back on. Just call T-Mobile and tell them it won't power on nor will it charge. It's funny because I was adding music to mine when it happened. If it happened the same way mine did then you will notice it was really hot when it shut off. The MDJ kernel overheated the Processor and killed it. Once that happens the device is a useless brick. I'm trading my replacement for another phone because this phone happens to overheat a lot.
Click to expand...
Click to collapse
Yup, same here, overheated while using fpse, died suddenly and wouldn't even charge. Tmo overnighted a replacement.
Sent from my HTC VLE_U using Tapatalk 2
Thanks everyone for the help... At least I know what I have going on... Already started re-downloading a buttload of stuff to get back on track. I don't normally backup my Nandroids or my TB files to my PC, maybe I should start.
Going tomorrow to the Tmo store to get the replacement sent overnight.
Thanks again.
Moved To Q&A​
Please post in the correct section.​
this exact thing happened to me twice. i dont get it. is it overheating or whats going on? it happened twice both times i was deleting a very large file 100 mb plus i have to call tmobile in the morning =/
---------- Post added at 08:29 AM ---------- Previous post was at 08:29 AM ----------
no one else knows of anything that might be able to revive my phone?
just read that it is most likely the processor a couple post up. =/ damn. im going to look into trading this phone for another
this has just happenmed to me to. was fully charged thought battery was low after it switched off managed to reboot see battery was full before crapping out completely. wont charge wont recognize in adb. Really dissappointed in my loss of data. i also imported this phone and had it running on att anyone know how good htc warranty service is bc tmobile is a no go for me

[Q] Unpleasantness... Bricked phone?

So, while I'm no expert I'm not new to rooting and flashing. Did it quite a bit on my older Droid Inc 1, and have performed a few on my new SG3.
I have 3 backed up ROMs on my SD, Synergy, Beans and CM10. I was running Synergy and decided to give CM10 another shot to see if I could figure out what was killing NFC. So, flashed it up with ROM Manager (Used Odin previously) and everything went swimmingly. ROM was running, NFC was working, all my apps were reinstalled, no problems.....
Decided to see if I could get Wallet working on this install, so flashed it in, made the changes to build.prop and rebooted.
Heeerreeee's where the trouble started. Part way through the reboot the phone just shut down. Completely. 100%. Dead.
I had 87% battery when I started so it 'shouldn't be a battery problem. No power, no LED when I plug in the charger, no vol-up, home, power to get into recovery.
One interesting thing did happen while I was trying to get the phone up, I removed the battery for a bit, and plugged the USB cable in and got a red charging light. Put the battery back in, light still there. 1 minute later, light goes off and still nothing happening with the phone at all.
Anyone have any ideas beyond all the stuff I've given a shot to?
Will it show up when plugged in on your CPU?
Sent from my Nexus S 4G using xda app-developers app
nexus995743 said:
Will it show up when plugged in on your CPU?
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
Unfortunately not. Only thing that seems to show up is in the device manager, a QHSUSB_DLOAD device that's banged.
Hmmmm
Sent from my Nexus S 4G using xda app-developers app
nexus995743 said:
Hmmmm
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
Well, I called Verizon and they've shipped me a replacement. I guess throwing all my bit and pieces into a new main body should work fine...
Oh no. Another one sending a phone back because of rooting. That's why they lock bootloaders.
Sent from my Galaxy Nexus using xda app-developers app
+1
Have you tried borrowing someone's battery to see if you can also least boot? I have four samsung batteries for the S3 and would consider sending it to you before getting a replacement. I think the cost of a battery is $3 on Amazon.
Sent from my SCH-I535 using xda premium
The reasons were different but i had the same thing happen to me, my phone wouldn't boot, wouldn't show up in the computer. Nothing, i tried my wife's battery, no change there either. I left it on the charger overnight and tried turning it on in the morning and after messing with it it came back on. Haven't had an issue since. Don't know what caused it, the phone just freaked out, turned off and wouldn't turn back on.
You can also try the resistor trick to see if that will bring your phone back. Here is a cheap way to do it.
http://hackaday.com/2012/09/03/saving-a-bricked-phone-with-a-pencil-lead/ Otherwise you can go to radio shack and pick up a resistor.
If Verizon sends you your phone back cause you messed with it, there is a brick repair service for like $60 bucks PM for the link if it comes to that.
Congrats on the new phone
Sent from my Nexus S 4G using xda app-developers app
nexus995743 said:
Congrats on the new phone
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
hehe.. I can't say I was pleased with having to go that route, (can't stand being defeated by electronics) but all in all I can't imagine a simple software change causing the entire unit to just go dead. Not booting properly, or locking up and such, sure... but not just dead.
By this morning I had tried another battery (a friend has an SG3 also) to no effect, but I didn't try leaving it plugged in overnight. I did check the battery with an external charger I have and it was showing fully charged....
So, I'll get a replacement and stay away from CM10 at the very least.
**ihavenewnike - Not sure why you're on an android developers forum really...
Ok, so the new phone got here at about 12:30. Plugged all my stuff into it and it fired right up.
Rooted and unlocked it, put my latest Synergy backup (1 day old) on the SD card and restored it.
Ahhhh... It's just like it never left. :victory:
keno1964 said:
Ok, so the new phone got here at about 12:30. Plugged all my stuff into it and it fired right up.
Rooted and unlocked it, put my latest Synergy backup (1 day old) on the SD card and restored it. . .
Click to expand...
Click to collapse
. . . and then the display went black and it wouldn't power on! What the heck?!
. . .
Oh, sorry: I was just imagining a funny ending to this topic.
- ooofest
ooofest said:
. . . and then the display went black and it wouldn't power on! What the heck?!
. . .
Oh, sorry: I was just imagining a funny ending to this topic.
- ooofest
Click to expand...
Click to collapse
Don't like you.......
Same thing happened to me when I tried to mess with the NFC hack on my SGS III.
What saved me was a USB Jig I happened to have handy when I...accidentally... soft bricked a friend's Samsung Captivate a few months back. The USB Jig is used to put the SGS III into download mode when all else fails that tiny little gadget saves the day.
tekrhino said:
Same thing happened to me when I tried to mess with the NFC hack on my SGS III.
What saved me was a USB Jig I happened to have handy when I...accidentally... soft bricked a friend's Samsung Captivate a few months back. The USB Jig is used to put the SGS III into download mode when all else fails that tiny little gadget saves the day.
Click to expand...
Click to collapse
I have looked into those and will most likely make one very soon. (I think I have everything I'd need, just may need to cobble some resistors together).
Couple of things I noticed throughout this 'process', regarding the CM10 (9-15 nightly) ROM, NFC and google wallet....
At first install of CM10 I noticed that NFC was active and working normally. It could read my tags without issue. After Wallet was installed though, NFC disappeared. It wasn't just disabled, it simply wasn't there any more. It was after noticing this that I decided to reboot, at which point my original problem started.
The reboot never came close to completing though, it shut down before it actually made it to the 'boot' phase, as in, while it was shutting down.
The actual cause of the power off is still a mystery to me, as I can't see a simple app change causing hardware failure.
So you bricked your phone, just like a few of us did yesterday.
What did you call Verizon saying in order for them to send you a new phone?
AB_ said:
So you bricked your phone, just like a few of us did yesterday.
What did you call Verizon saying in order for them to send you a new phone?
Click to expand...
Click to collapse
I told them what happened, just left out a few bits of info.
"I rebooted it, and it never came back on." and that was that.
Nice.
I should have gone that method, but ended up paying for the repair service from MobileTechVideos
A friend has the qhsusb-dload showing up as well.. phone won't turn on.. flashed a bad kernel or rom I forget which.. red light comes on.. that's it.. its a Verizon i535 .. tried the resistor jig and nothing happens.. any ideas to fix?
---------- Post added at 12:03 PM ---------- Previous post was at 11:59 AM ----------
Guess he had aokp rom then flashed neak kernel and that's when it died..

[Q] Sidekick 4g Bootloop Please Help!!!

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.

[Q] Help, 2 problems.

Hello fellow XDA members,
Before I start, I would like to appologize if my English spelling is not perfect.
Ok, Problem 1:
This morning i woke up, and as usual, my phone was still plugged in into the charger. (Acer Liquid E2).
But, the thing that actually woke me up, was the phone constantly re-booting, and making the start-up sound + vibration.
When I took the phone, it was SUPER hot... I have never felt a phone being so hot.
It kinda got me worried...
I have the phone for about 2 weeks now.
What i did, was unplug the phone from the charger, took out the battery and placed them on my marble windowsill, and left it there to cool down for about 15 minutes.
When it was cool again, i placed the battery in the phone, and booted it up.
There was nothing wrong with the phone, but when it booted, it said that it was only charged 16%...
While it had been in the charger for about 7h's straight.
I just charged the phone again, but this time using another charger.
To Be Honest, I used the charger from my old samsung device, and swapped to the charger that came with the Acer phone.
I used the Samsung charger, because it has the same plug + the cable is longer ...
Do you think that this all happened because the samsung charger is not compatible with the acer device?
Or should I bring the phone back to the store, and have them take a look at it?
Ok, Problem 2:
When I try to call someone.
I often need to call 3-4 times...
Sometimes, when I call and the person answers my call, I can not hear them.
But the phone is still calling...
I need to re-call them then, and when the phone is calling, and I head a double beep.. then it will work...
Its really hard to explain..
But when I hear 2 dail beeps at once, then I can make a call,
if I only hear one dial beep, then I am a 100% sure it will not work, and I will need to recall them...
I have never had this problem before.
Could it be the provider? or the phone?
I hope you understand my issues,
And I am hoping that you guys can help me.
PS: if I posted this in the wrong section, please forgive me and move it to the right section on the board.
Thanks for your time,
And I am looking forward to see the replies.
Greetings from Belgium,
Kristiaan D.
Are you running a custom ROM?
Sent from my SGH-T959V using xda app-developers app
mattoaida said:
Are you running a custom ROM?
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
No my friend,
Just android 4.2.1,
Its the stock ROM that came with the phone, but with an update.
Thank you for your reply.
Doing a preliminary search I discovered that it might not be your phone, it might actually be a tower or similar in your area.
What kind of phone do you have? What carrier do you have?
Do you travel away from your home regularly? Do these issues persist when you are away from home?
According to another forum it could be your SIM card or your SD card (if you have either of those)?
According to another forum you may need to consider a factory reset to clear the cache and then reintroduce applications one by one to see if any are actually causing the problem.
I see you are in Belgium so I know some of the above may have no pertinence to your situation.
sergeri said:
Doing a preliminary search I discovered that it might not be your phone, it might actually be a tower or similar in your area.
What kind of phone do you have? What carrier do you have?
Do you travel away from your home regularly? Do these issues persist when you are away from home?
According to another forum it could be your SIM card or your SD card (if you have either of those)?
According to another forum you may need to consider a factory reset to clear the cache and then reintroduce applications one by one to see if any are actually causing the problem.
I see you are in Belgium so I know some of the above may have no pertinence to your situation.
Click to expand...
Click to collapse
My carrier is BASE.
Well, i walk alot...
And these problems happen everywhere that i go...
But to be honest, i never go far away... (max 20km)
I don't think its an app that causes this, because i have had this problem from the first day that i bough the phone.
Thanks for the reply
ikristiaan said:
My carrier is BASE.
Well, i walk alot...
And these problems happen everywhere that i go...
But to be honest, i never go far away... (max 20km)
I don't think its an app that causes this, because i have had this problem from the first day that i bough the phone.
Thanks for the reply
Click to expand...
Click to collapse
@ikristiaan - 20k is more than enough to rule out towers as the cause.
What kind of phone do you have?
Does your phone have an SD card or a SIM card?
To find if the problem is due to charger or phone,connect it to a laptop or pc via USB and let it charge and also if u want to know if it was also not because of network take away the SIM and charge if the problem still present then u should probably take it to store.it happens if you've overclock too.
Sent from my WT19i using xda premium
sergeri said:
@ikristiaan - 20k is more than enough to rule out towers as the cause.
What kind of phone do you have?
Does your phone have an SD card or a SIM card?
Click to expand...
Click to collapse
As mentioned above, i have an Acer Liquid E2.
Yes, the sim card.. thats pretty logical to have right, and yes it also has a SD
nivdeep said:
To find if the problem is due to charger or phone,connect it to a laptop or pc via USB and let it charge and also if u want to know if it was also not because of network take away the SIM and charge if the problem still present then u should probably take it to store.it happens if you've overclock too.
Sent from my WT19i using xda premium
Click to expand...
Click to collapse
It does not get that hot when i charge it using the pc or when i charge it using the charger that came with the phone.
I did not overclock it. It has enough power with its 1.2ghz quad core
thanks for the replies
ikristiaan said:
As mentioned above, i have an Acer Liquid E2.
Yes, the sim card.. thats pretty logical to have right, and yes it also has a SD
It does not get that hot when i charge it using the pc or when i charge it using the charger that came with the phone.
I did not overclock it. It has enough power with its 1.2ghz quad core
thanks for the replies
Click to expand...
Click to collapse
@ikristiaan
1) Try removing the SD card for a few hours to see if it restarts on its own.
2) Try plugging your phone into the charger, then remove the battery. Observe it to see if it restarts.
3) If those do not make a difference remove your SIM card to see if your phone restarts by itself without the SIM.
Report back here with results.
@ikristiaan - Hey, I'm just checking back in to see if you've had any success with any of the trouble-shooting methods above.
I look forward to hearing back!

Categories

Resources