Database Info

[Q] unable to unlock my phone!

so i went to plug in my phone, and the moment i plugged it in the "powering down" window pops up, when the phone powers up my lock-ring is gone, and just my wallpaper is there? i have pulled the battery, booted into recovery, pulled the SD-card, tried calling my phone, then deleted my dalvik cache (thinking it could relate the kernel) but no matter what i cannot get the unlock ring too appear, this has never happened before, any suggestions??
EVO 4g
MikG 2.45

Your Sig says EVO4G . This is the EVO Shift Forum. But from what you've listed, I would say at this point it's reflash time. If you can boot into recovery I'd say just boot into recovery and reflash. I would say that's your best bet.

This has happened to me for Evo Shift 4G. I had to open the keyboard and setup page showed up. What it is is a bad flash due to lack of wipe from data. I noticed once I didn't wipe data the lockscreen never showed up.
Sent from my PG06100 using xda premium

Agreed it is from a bad flash. Also, opening the keyboard will work to unlock the phone. If it's a Shift. But it will not solve the issue. Best thing is a Full Wipe (as you mentioned), and a reflash. Plus I'm not so sure he has a Shift. His Sig says EVO4G. He might have posted int the wrong section.

I've noticed funky things happening when you plug your phone in as it powers down.
Once it cleared everything off all my home screens.

soo i do have an evo 4g, not the shift but my thread was moved by someone else?
anyways.. i solved the problem temporarily, i flashed a new ROM and it worked fine i booted it up got all my contacts back, recovered apps, etc. then i turned it off. turned back on no problems... used for about 2 hours removed some preinstalled stuff i didn't want. phone was being unusually slow, so i restarted it and when it turned back on.. lock screen was gone again

SPARTIZLLS said:
soo i do have an evo 4g, not the shift but my thread was moved by someone else?
anyways.. i solved the problem temporarily, i flashed a new ROM and it worked fine i booted it up got all my contacts back, recovered apps, etc. then i turned it off. turned back on no problems... used for about 2 hours removed some preinstalled stuff i didn't want. phone was being unusually slow, so i restarted it and when it turned back on.. lock screen was gone again
Click to expand...
Click to collapse
gee i wonder what it could be...

SPARTIZLLS said:
soo i do have an evo 4g, not the shift but my thread was moved by someone else?
anyways.. i solved the problem temporarily, i flashed a new ROM and it worked fine i booted it up got all my contacts back, recovered apps, etc. then i turned it off. turned back on no problems... used for about 2 hours removed some preinstalled stuff i didn't want. phone was being unusually slow, so i restarted it and when it turned back on.. lock screen was gone again
Click to expand...
Click to collapse
I would say reflash again. But this time, do not remove anything unless your absolutely certain about what your removing.

Help please! Just installed Android Revoluation HD, now won't turn on?

I have s-off, rooted, was using insertcoin...Just thought I'd install the Revolution ROM. Did the wipe and then installed ROM. EVerything seem to be fine and it rebooted. Then I reinstalled apps through titanium backup.
When I was using the phone to call...after a minute or so...it started to make this long tone sound and everything freezes. It seem to reboot...and back to working again. I thought it was due to some apps still being reinstalled?
In any case, when I made call again...again after a minute or so..it started making that same tone....and it turned off.
Now, it won't respond at all. I tried pulling out battery...no matter what I do...the phone will not turn on.
please help! Is this bricked? I pretty much followed all the steps. I selected stock kernel instead of custom when prompted.

newr said:
I have s-off, rooted, was using insertcoin...Just thought I'd install the Revolution ROM. Did the wipe and then installed ROM. EVerything seem to be fine and it rebooted. Then I reinstalled apps through titanium backup.
When I was using the phone to call...after a minute or so...it started to make this long tone sound and everything freezes. It seem to reboot...and back to working again. I thought it was due to some apps still being reinstalled?
In any case, when I made call again...again after a minute or so..it started making that same tone....and it turned off.
Now, it won't respond at all. I tried pulling out battery...no matter what I do...the phone will not turn on.
please help! Is this bricked? I pretty much followed all the steps. I selected stock kernel instead of custom when prompted.
Click to expand...
Click to collapse
Try to boot with adb.
Sent from my HTC Sensation Z710e using xda premium

Hi...I am trying to install the new SDK package...but I do have the older ADB and when I tried it..it first says ADB sever out of date...then started daemon...and attached list showed nothing?
When I plug the phone in...there's no response from the PC..it won't beep or show anything connected on USB!

I just tried to run adb after installing the latest sdk package. Running adb from the platform-tool directory...the device listed is empty....doesn't seem to be recognizing the phone!
Any other ideas? Is this completely bricked?

I wouldn't call it a brick per se, but this has happened to more Sensations than you may realize. Most people who've reported said they went to bed (phone on or off the charger) and when they wake up, it just won't turn on.
Honestly, I believe it's a random catastrophic hardware issue. I think some Sensations are faulty and have a lower temperature threshold or something, not sure, but what you described seems hardware related.
Edit: Just reread about that tone. A long tone? Although you were on a phone call so it's no guarantee, something like a long speaker tone or a screen spazzing out (I work in electronics) tend to mean something hardware related. Again, not 100% solid, but that's how it usually turns out.
Also, don't believe this happened because you flashed a different rom or something, there is just no way flashing a rom would kill a phone. If that were true, normal software updates or factory resetting could cause the same thing, and they simply don't.

Yes..it could be hardware related? The thing is, if it's bricked...I would think this wouldn't boot into the new ROM at all.. mine booted to the new ROM and I was able to restore all the apps...but all of a sudden while on the phone...I heard this long tone from the phone....then it just turned off.
The problem is, since this is rooted...doesn't it void waranty? Also, I am in Canada using a t-mobile phone I bought from the States...so I can't really bring it back to fix?
Wonder if I could get HTC to fix it?
It basically just died...battery was 100% when I was updating.
Any suggestion of what I should do?

newr said:
Yes..it could be hardware related? The thing is, if it's bricked...I would think this wouldn't boot into the new ROM at all.. mine booted to the new ROM and I was able to restore all the apps...but all of a sudden while on the phone...I heard this long tone from the phone....then it just turned off.
The problem is, since this is rooted...doesn't it void waranty? Also, I am in Canada using a t-mobile phone I bought from the States...so I can't really bring it back to fix?
Wonder if I could get HTC to fix it?
It basically just died...battery was 100% when I was updating.
Any suggestion of what I should do?
Click to expand...
Click to collapse
take off the battery, SD card, SIM card and then put them back again.....try to press power+volume down (even power+volume up & down, all buttons) to see if you can log into the recovery...I don't know if this works but since your phone is almost dead, you won't lose anything to try any method...Do you think so?
If anything you have tried does not enable the phone to work normally again, please try to turn to some body who can check and repair the hardware of your phone for help...It could take a long time to send it back to HTC.....
Hope everything is going well with you.

Nothing works..I've tried taking out Battery..talked with HTC and they tried that with me too...but basically the phone is completely unresponsive. I am just wondering if it's a problem with the ROM or if it's a hardware thing. It seems strange it booted up ok and then had this long beep/tone thing.
There seem to be one other person posted in Q&A experiencing exactly the same thing...he was using revolution 6.6.3 and also had that sound and now it won't turn on!
I have talked to HTC and got a repair ticket...not sure if anyone locally can fix it...just wonder if HTC will have problems with it being rooted and all.

He was running ARHD 6.6.3?! I just downloaded it, now I'm weary to flash O.O

@newr
can you try one thing?
Remove battery ,sdcard, then connect the phone to power outlet using usb then try to power on the phone.?
If it doesn't turn on then remove the back shell too and try to power it on again?
sent from my blazing fast pyramid through sonic waves

Thanks for the suggestion. But again nothing happened. I've tried taking out SD, SIM, battery...with or without cover. Nothing turns the phone on...also no light when charging. It's like the phone is just dead?
There's one other post by someone on the forum that says his phone doesn't turn on..and it seem to happen the exact same way. He said he was running 6.6.3 and then all of a sudden a long beep/tone...then stuck..so turned it off and won't turn on again. Haven't seen any update / resolution there neither!
I am still not sure if it's a ROM problem or if it's a hardware problem. The thing is, the ROM did get installed and was rebooted...in fact, I used Titanium to reinstalled all the apps...unless restoring some data for things like bluetooth settings, desktop etc..causes it...which was fine when I restored it for InsertCoin...I don't understand how a ROM could cause a phone not to turn on at all?
I guess unless there are other ways to fix this..looks like it's sending back to HTC...hopefully they can't fix it neither and just send a different phone since if they turn it on and notice I have it rooted and S-On..they might just blame it on that!

Stock HTC One S got bricked sudenly?

so yesterday my unlocked T-Mobile HTC One S got bricked, before you ask i never touched the ROM of the device, it was pure stock HTC One S with a lot of apps.
basically it entered into a strange loop: first the T-Mobile greeting message appeared and then the HTC One S logo, over and over and over again. the only thing that i could do was to power button + volume down and do a factory reset.
This happened one day after i updated its firmware OTA, and in the same day that i downloaded a free app called AutomateIt.
i'm only upset about the fact that i lost the pictures and vids that i took in the 6 weeks owning it, but i am worried that if it did this once, it could do it again so i need to know if this is something common to Androids, my One S or something else.

Very strange!!!
Root the phone and make a nandroid backup. Stock Rom's sucks!!!
Sent from my HTC One S using xda app-developers app

Warmo said:
so yesterday my unlocked T-Mobile HTC One S got bricked, before you ask i never touched the ROM of the device, it was pure stock HTC One S with a lot of apps.
basically it entered into a strange loop: first the T-Mobile greeting message appeared and then the HTC One S logo, over and over and over again. the only thing that i could do was to power button + volume down and do a factory reset.
This happened one day after i updated its firmware OTA, and in the same day that i downloaded a free app called AutomateIt.
i'm only upset about the fact that i lost the pictures and vids that i took in the 6 weeks owning it, but i am worried that if it did this once, it could do it again so i need to know if this is something common to Androids, my One S or something else.
Click to expand...
Click to collapse
Did you let the phone die? the phone don't like to do that. Get Dropbox or Google+ that will sync your pictures online.

The same happened with my stock htc one s 4.0.4 twice! I figured out that when you have more than 15-20 saved wlans, you have connected to in the past, in your wifi-list your phone ends up in a bootloop. I didn't manage to rescue any data even not with adb.. clearing the cache and so on. probably you used any automatic wifi functionality from automatelt.

-janboy- said:
The same happened with my stock htc one s 4.0.4 twice! I figured out that when you have more than 15-20 saved wlans, you have connected to in the past, in your wifi-list your phone ends up in a bootloop. I didn't manage to rescue any data even not with adb.. clearing the cache and so on. probably you used any automatic wifi functionality from automatelt.
Click to expand...
Click to collapse
now thats interesting, my phone is also 4.0.4, and yes i did have ~20 saved WLAN's, i can't figure how wlan would have any connection to a bootloop, but then again i dont know anything about programming.
so you always delete the wlans once you are done using them? after you found out did it brick again?

Warmo said:
now thats interesting, my phone is also 4.0.4, and yes i did have ~20 saved WLAN's, i can't figure how wlan would have any connection to a bootloop, but then again i dont know anything about programming.
so you always delete the wlans once you are done using them? after you found out did it brick again?
Click to expand...
Click to collapse
yes, I take care that I don't have more than 5-10 in my list. since that it didn't brick again. but a few days ago I had ~10 in my list and it suddenly restarted again while I was in the wifi list screen and I was like pleeeaassse no bootloop! but fortunately it was no bootloop but my whole wifi list was reset. it must be an error in htc's software.. so we can only wait for updates..

I've had this happen with other Android devices, it's generally some rogue app that screws up the device and only a factory reset will clear it. I've never had more than 3 or 4 wifi points saved so can't comment on that as a possible cause.
It's not 'bricked' by the way, just slightly fubar'd

-janboy- said:
The same happened with my stock htc one s 4.0.4 twice! I figured out that when you have more than 15-20 saved wlans, you have connected to in the past, in your wifi-list your phone ends up in a bootloop. I didn't manage to rescue any data even not with adb.. clearing the cache and so on. probably you used any automatic wifi functionality from automatelt.
Click to expand...
Click to collapse
You are not the only one. I also encountered the same thing because of too much wlan connections and the only thing i could do is run into bootloader and restore factory settings, since i don't have a nandroid backup because i'm not rooted.. fortunately i synced my pictures thru dropbox, and a backup of sms in gmail.. but i don't know why it is happening to us, so this issue isn't an individual case..
Sent from my HTC One S4 using xda-developers app

Nexus 5 became a paperweight overnight (help!)

Hello xda, I have a problem!
My Nexus 5 is only six months old and aside from typical Nexus 5 shenanigans (the camera seizing upon lock, requiring a reset) it has worked fine. (though I have been very discontent with this device) Last night I was using my Nexus 5 as usual and I was tired, but too lazy to plug it into the charge port. By morning my phone died as expected, so I plug the charger in and lo-and-behold, it's stuck in boot up.
So naturally I freak the f*** out; I wait. To no avail.
I wait some more. Nix.
It's still f***ing booting.
So I know something's wrong with my phone and I said "f*** it; I'm just going to factory reset it" because knowing my luck, my phone decided to say "f*** you" and kill itself the night prior. (My affinity with technology is poor.)
So I wipe the damn thing.
I boot it up.
Loop. You've got to be kidding me.
I wipe the cache (don't tell me I should have done this first); nada.
I get flustered, chuck the black pice of s*** down the stairs, get desperate, pick it back up, take it to work with me (while it was still booting), I left for work at 12:00PM, it's now 7:04PM, I'm home and it's STILL BOOTING.
So what's a girl to do?
And I'm going to answer the fusillade of questions I know I'm going to get in response to my peril, so before you all premeditate; here's what I've done to my phone:
I rooted it THREE WEEKS AGO with KingRoot to turn off my proximity sensor. Why? Because I Skype and like to use my device at the same time, and Microsoft thought it would be brilliant to have the screen shut off any time something crosses slightly in front of the Nexus 's two stupid sensors, so horizontal use of the device gets thrown out of the window. (if any muppets at Microsoft are reading this, you're f***ing idiots! If I really wanted to turn my screen off to conserve battery power, I would lock the f***ing screen! I don't need YOU nannying me!)
I wasn't able to shut off the proximity sensor with root permissions so I got cheesed and unrooted, then uninstalled the application.
Things have been working perfectly fine. (And yes, my phone has been rebooted in that three week span.)
Up until last night, my phone was working perfectly normal. I did what I usually did.
Listened to music, checked my work schedule, text, watched YouTube videos, played Gameboy games on an emulator, and that's it.
Someone please help me with this phone so I can at least fix it and sell the wretched thing to some muppet for some money to put towards a REAL phone.
Thanks.
~ Ashley
And it finally died, just as I finished writing this.

Ashleyware said:
Hello xda, I have a problem!
My Nexus 5 is only six months old and aside from typical Nexus 5 shenanigans (the camera seizing upon lock, requiring a reset) it has worked fine. (though I have been very discontent with this device) Last night I was using my Nexus 5 as usual and I was tired, but too lazy to plug it into the charge port. By morning my phone died as expected, so I plug the charger in and lo-and-behold, it's stuck in boot up.
So naturally I freak the f*** out; I wait. To no avail.
I wait some more. Nix.
It's still f***ing booting.
So I know something's wrong with my phone and I said "f*** it; I'm just going to factory reset it" because knowing my luck, my phone decided to say "f*** you" and kill itself the night prior. (My affinity with technology is poor.)
So I wipe the damn thing.
I boot it up.
Loop. You've got to be kidding me.
I wipe the cache (don't tell me I should have done this first); nada.
I get flustered, chuck the black pice of s*** down the stairs, get desperate, pick it back up, take it to work with me (while it was still booting), I left for work at 12:00PM, it's now 7:04PM, I'm home and it's STILL BOOTING.
So what's a girl to do?
And I'm going to answer the fusillade of questions I know I'm going to get in response to my peril, so before you all premeditate; here's what I've done to my phone:
I rooted it THREE WEEKS AGO with KingRoot to turn off my proximity sensor. Why? Because I Skype and like to use my device at the same time, and Microsoft thought it would be brilliant to have the screen shut off any time something crosses slightly in front of the Nexus 's two stupid sensors, so horizontal use of the device gets thrown out of the window. (if any muppets at Microsoft are reading this, you're f***ing idiots! If I really wanted to turn my screen off to conserve battery power, I would lock the f***ing screen! I don't need YOU nannying me!)
I wasn't able to shut off the proximity sensor with root permissions so I got cheesed and unrooted, then uninstalled the application.
Things have been working perfectly fine. (And yes, my phone has been rebooted in that three week span.)
Up until last night, my phone was working perfectly normal. I did what I usually did.
Listened to music, checked my work schedule, text, watched YouTube videos, played Gameboy games on an emulator, and that's it.
Someone please help me with this phone so I can at least fix it and sell the wretched thing to some muppet for some money to put towards a REAL phone.
Thanks.
~ Ashley
And it finally died, just as I finished writing this.
Click to expand...
Click to collapse
Since you've already wiped data, have you tried unlocking the bootloader and flashing the Google factory image

I haven't because I can't. I'm on a Macbook and the Nexus 5 drivers aren't compatible with Macs apparently =/

Wait okay, so I misread what I looked at this morning.
So it says I have to flash a new rom to my phone O.K. but every website says I have to turn on USB debugging--how am I supposed to turn on USB debugging to unlock the bootloader if my phone is bricked to begin with? This doesn't make any f***ing sense!
HELP.
Also, my Mac doesn't recognize my device in fastboot mode; what am I supposed to do?!

Try this? It has Mac instructions too.
http://forum.xda-developers.com/showthread.php?t=2513701
Sent from my Nexus 5 using Tapatalk
---------- Post added at 10:12 PM ---------- Previous post was at 10:11 PM ----------
I was able to unlock my bootloader on my Mac with no problems...
Sent from my Nexus 5 using Tapatalk

ldubs said:
Try this? It has Mac instructions too.
http://forum.xda-developers.com/showthread.php?t=2513701
Sent from my Nexus 5 using Tapatalk
---------- Post added at 10:12 PM ---------- Previous post was at 10:11 PM ----------
I was able to unlock my bootloader on my Mac with no problems...
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Don't you understand? I can't enable USB debugging because I can't ACCESS my phone! It's stuck in bootloop! I can't unlock the bootloader to begin with! Unless you know how to unlock the bootloader from the fastboot menu, you saying that you unlocked your bootloader doesn't help me. I tried everything in that thread and nothing works, I tried the terminal bull**** and the only thing that happens as I can get into the folder where the factory rom is, but I can't get it to flash, I can't get anything to happen--I don't know what the hell I'm doing.
Is there a way to start over without all of this stupid bootloader crap?

As far as I know ADB is not active in fastboot, it is not recognized. In fact I just flashed TWRP again with ADB off. You do need the fastboot drivers on your Mac installed correctly but that's no big deal. If you have access to your phone in fastboot it is simply fastboot oem unlock to unlock your bootloader.

PROGRESS REPORT
So last night I stayed up trying to fix my issue, and I've had no success. I've managed to flash back to Kitkat 4.4.4 but as soon as the phone boots into set up, immediately I get the error messages "unfortunately Camera has stopped working", "unfortunately Gallery has stopped working", and "unfortunately Google Playstore has stopped working". After setting up, my phone has NO service! It doesn't even recognize if there's a SIM card even inserted, or if I remove it.
I cannot open Playstore, it immediately crashes and my phone believes that it has no storage now, even though I see 12GB of space free. I tried flashing multiple roms and nothing beyond Kitkat will work, otherwise I get caught in a bootloop.
I tried installing Cyanogen mod and although it worked, I had the same issue--no service, no Playstore no storage.
I tried clearing the cache, the Dalvik and factory resetting several times and nothing works. I just flashed 4.4 and I'm updating it to 4.4.3 as we speak.
Also I think it's worth mentioning that every time I got caught in bootloop after flashing a new rom (and I tried all of them, including Lolipop, which always hangs) that when I boot in Recovery mode it says something along the lines of:
Invalid arguement couldn't mount blahblahblahgeniusspeak
Invalid arguement blahblahblahgeniuspeak
and so on. Does this have something to do with my lack of service, camera not working, Playstore not working and storage not working? I'm desperate people.

Have you got an imei number?,settings/about phone
Usually you just flash factory ROM, extract the file and then the second archive and flash each individual file and it should boot, factory reset and wipe cache to fix storage
I do this on my mac
If you can't do this then you may have a hardware issue
How did you try to turn off proximity sensor. There would be another way to keep screen on while skyping (keep screen on wake lock)

Also it sounds like you flashed custom roms without flashing gapps...
Sent from my Nexus 5 using Tapatalk

Definitely sounds like no gapps.

What's gapps? And I have no IMEI number (unknown), it says my (with my SIM inserted) Network is: Unknown
Mobile Network Type: Unknown
Mobile State is disconnected
Out of Service
Phone number is unknown
IMEI SV is unknown
IMEI is unknown
Not roaming either
What's the second archive? Every guide I used said use the flash-all.script and that's all you have to do, what're all these extra steps? How do I flash gapps, I don't even know what that is; I don't see the file anywhere in the factory image folder.
=/

I flashed again (back to stock; 4.4) and did everything manually instead of using the script, I even flashed the cache.img, recovery.img etc . . . and it's still the same issue. No service. No external storage available. No Google Playstore.
=/
I didn't flash a custom rom, I only flashed the official factory image from Google. Why doesn't anything ****ing work.
Is gapps going to return my storage and service?

Gapps is only for custom ROM. Since your imei etc is unknown seems like you have bad efs partition. I am not 100% sure. May be others can help.
Sent from my Nexus 5 using XDA Free mobile app

Weird sponstaneous reboot

I've just experienced a strange spontaneous reboot. I noticed my Nexus 5 was indicating 'optimizing application n of nn' exactly like what happens with an update. I thought - looks like it's decided to OTA to LMY48M. But no, after 'updating' all the apps it's still on LMY48I. What's going on? I can understand a spontaneous reboot but not one which goes through the process of updating the apps.
Trev

Same here
Well, I don't have a solution for you but it looks like I have the same problem. Mine has been doing the same as you describe for the past 2 or 3 days. In addition I get hard boot loops many times before it finally decides to boot up (accompanied by the apps updating like you describe). It continues to hard boot loop even if I kick it to the bootloader, at least it does a bunch of times and then suddenly stops and seems to work for a little while.
Just FYI I was able to just now initiate a factory reset from the settings menu. It seemed to be working for a while. It took a long time to erase phone but then booted and walked through initial setup. All was well and it was about halfway though restoring apps when it suddenly hard reset and began boot looping again. So I guess it's on to more difficult procedures now.

ccjb100 said:
Well, I don't have a solution for you but it looks like I have the same problem. Mine has been doing the same as you describe for the past 2 or 3 days. In addition I get hard boot loops many times before it finally decides to boot up (accompanied by the apps updating like you describe). It continues to hard boot loop even if I kick it to the bootloader, at least it does a bunch of times and then suddenly stops and seems to work for a little while.
Just FYI I was able to just now initiate a factory reset from the settings menu. It seemed to be working for a while. It took a long time to erase phone but then booted and walked through initial setup. All was well and it was about halfway though restoring apps when it suddenly hard reset and began boot looping again. So I guess it's on to more difficult procedures now.
Click to expand...
Click to collapse
Sounds to me like your power button may be going out buddy
Sent from my Nexus 5 using Tapatalk

crazymonkey05 said:
Sounds to me like your power button may be going out buddy
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I guess time will tell. It was looping very fast though, too fast for just a stuck power button. That also doesn't account for the apps updating as if there was an android update when there was not. At least I don't think so. Button could be in it's way out even so.
To update the OP: I seem to have fixed it, at least so far. Since I was able to eventually get into the bootloader with enough stability to do something (by holding down vol/power, and trying a few times), I was able to to fastboot flash Cyanogen recovery. Rebooting to CM recovery I was able to wipe reset, adb push CM12 and gapps, install.... and try again. Since then I have been stable. I have gotten though a full restore of 70+ apps, and phone currently syncing. I've manually rebooted a few times and it seems ok for the moment. Just thought I'd let you know where I'm at.