Database Info

No screen (black) but has sound MIUI update

Hi, I'm new here so don't know if i'm posting this in the right place but here it goes... Ok i gave my HTC Inspire to a friend to install the MIUI ROM to it. Afterwards it was running smoothly and had no problems with it. A few days later my Inspire notified me that it had an update to the ROM. At first i wasn't sure to install it because it is a custom ROM and not the default one, but did the update anyways through the phone. Again, the phone worked normal all day, but at some point the screen started glitching untill it turned completly off.
The one strange thing is that the phone seems to function normally because when charged and "turned on" i can hear the sounds and notifications(like email, text and app notifiactions). Also when i connect it to my computer, it recognizes the device.
That happened about three days ago and I have not been able to discover what really is the problem and how to fix it. If there's anyone that could help me i would REALLY appreciate it.
Thanks in advance,
Marialo

most likely was a bad update.
You should boot into recovery and reinstall miui everything should be back.
Keep in mind the devs have to set miui for each device, chances are you updated to the wrong base.

That's what i thought but can't boot into recovery because i can't see the screen... Any advice on that?

Btw, thks for the quick response

Try shutting off the phone completely and booting into your bootloader the old fashioned way by holding down the volume down key, press power, and release volume down once you see the bootloader screen.
If your screen doesn't work during that, you may have a hardware problem on your hands.

Ok thanks; will try that then.

marialo said:
Ok thanks; will try that then.
Click to expand...
Click to collapse
or while the phone's on, if you have ADB installed - open a cmd prompt and navigate to where ADB is and type "adb reboot recovery"

Yup try what they said that should work. If not ruu the ruin and really root
sent from the dark obelisk

Ok, tried with the volume and power button, but nothing happened. Thanks for the advice, but I'm kind of new with all this and don't really know how to do the other stuff that you guys told me to do... :S Should I get someone that knows a bit more or is it something that i could do with a little info. from the internet?

anudist said:
Try shutting off the phone completely and booting into your bootloader the old fashioned way by holding down the volume down key, press power, and release volume down once you see the bootloader screen.
If your screen doesn't work during that, you may have a hardware problem on your hands.
Click to expand...
Click to collapse
I don't know if you would know but... If it were hardware problems; you think I could claim that to htc? Since the phone hasn't had any accidents or anything... :/

marialo said:
I don't know if you would know but... If it were hardware problems; you think I could claim that to htc? Since the phone hasn't had any accidents or anything... :/
Click to expand...
Click to collapse
If its rooted warranty won't cover this. Get the ruu (stock exe) from the HTC support site and run it. If the phone still has a black screen after its been returned to stock then the problem is hardware related
sent from the dark obelisk

[Q] HTC ONE S Bricked

Hey Guys,
a friend of mine just bricked his HTC-OneS and I'm here to help him get it back to life
He installed the latest PacMan Rom and everything was awesome.
All over sudden the Phone didn't boot up anymore.
It can be charged via USB, so maybe one can do something over USB
Windows-PC doesn't recognize the Phone he says...
As far as I remember its an HTC One s ville c2 (is there anything like this)
Due to the Fact that I'm a Motorola User, I have no idea where to start trying to recover his Phone...
Please Help me do it

do you know how to use some adb/fastboot commands? run fastboot oem getcid in the bootloader.
hold down volume down and power to go into the bootloader.

I would try to get into the bootloader first. That would provide a gateway to possibly fixing his (or her) phone.

Hope to get into bootloader, will get hands in his phone in monday.
Coming from Motorola i'm used to a factory tool where i can flash official Firmware via PC. Is there anything like this for HTC phones?
If not first thing i would try is flashing a New recovery system via fastboot to have sth to work with. Anyone agree with this plan?
Sent from my XT925 using xda app-developers app

I don't think I've ever seen a tool like that. I think the best bet would be to get into recovery, mount and try to flash a new rom (C2 roms in this case).

esok44 said:
Hope to get into bootloader, will get hands in his phone in monday.
Coming from Motorola i'm used to a factory tool where i can flash official Firmware via PC. Is there anything like this for HTC phones?
If not first thing i would try is flashing a New recovery system via fastboot to have sth to work with. Anyone agree with this plan?
Sent from my XT925 using xda app-developers app
Click to expand...
Click to collapse
Yes, go to androidruu.com, look for villec2 and click on it. The latest RUU should work unless he is carrier branded. Then you will need to use a carrier RUU.

Got hands on his phone and it doesnt do anything...
No bootloader nothing.
Only thing that happens is that it recognizes its on a wallplug...
Sent from my XT925 using xda app-developers app

Anyone got an idea?
The little charging LED is red, is it possible that there is some kind of battery driver missing, so the phone won't charge anymore and the battery is empty?
and is there an option to solve this?

esok44 said:
Anyone got an idea?
The little charging LED is red, is it possible that there is some kind of battery driver missing, so the phone won't charge anymore and the battery is empty?
and is there an option to solve this?
Click to expand...
Click to collapse
Really sounds like it is hard bricked.
I could mention things that you have already most likely tried.
Holding power down for 30 seconds
holding power down for 10 seconds under bright light so the front sensor registers (prevents messing up your phone while in your pocket)
when plugged in computer, does device manager show it as "qhsusb_dload" (bricked)
Hold power down and volume down for 10 seconds. release power button and continue holding volume down.
From replies from manufacturer that people post here, often they replace the battery and (motherboard?) Seems like something happens and a sudden battery discharge messes up the works.

tivofool said:
Really sounds like it is hard bricked.
I could mention things that you have already most likely tried.
Holding power down for 30 seconds
holding power down for 10 seconds under bright light so the front sensor registers (prevents messing up your phone while in your pocket)
when plugged in computer, does device manager show it as "qhsusb_dload" (bricked)
Hold power down and volume down for 10 seconds. release power button and continue holding volume down.
From replies from manufacturer that people post here, often they replace the battery and (motherboard?) Seems like something happens and a sudden battery discharge messes up the works.
Click to expand...
Click to collapse
Thank you for your response
So quick question, due to the fact that the Phone is hard bricked, can i send the Phone back in, and get things fixed, cause the Phone was s-off and rooted before, so warranty is void.
Is there any way they could find out about it? Like a blown fuse or anything?

esok44 said:
Thank you for your response
So quick question, due to the fact that the Phone is hard bricked, can i send the Phone back in, and get things fixed, cause the Phone was s-off and rooted before, so warranty is void.
Is there any way they could find out about it? Like a blown fuse or anything?
Click to expand...
Click to collapse
Your guess is as good as mine. There was one guy who posted here, that they did fix it, and when they sent it back they had turned back on security, or S-on. So they obviously knew and didn't care. One of those ymmv. I kind of doubt he did anything wrong and it is a defect. People post on here with completely stock w/ same symptoms.

tivofool said:
Your guess is as good as mine. There was one guy who posted here, that they did fix it, and when they sent it back they had turned back on security, or S-on. So they obviously knew and didn't care. One of those ymmv. I kind of doubt he did anything wrong and it is a defect. People post on here with completely stock w/ same symptoms.
Click to expand...
Click to collapse
Thank you dude, will give it back to him and tell him, that he should send the phone back, cause it seems like this is a common problem
Greetz Esok

Power button issue

Hey my power button is acting very weird even the slightest touch locks or unlocks the screen or even brings up the power menu. The button itself doesn't appear stuck and and it makes a click when I fully press it. Anyone know how to fix this?
Sent from my SCH-I535 using Tapatalk

jasondhsd said:
Hey my power button is acting very weird even the slightest touch locks or unlocks the screen or even brings up the power menu. The button itself doesn't appear stuck and and it makes a click when I fully press it. Anyone know how to fix this?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
This has happened to several people recently. Mine was still under warranty, verizon sent me replacement :laugh:
Mine was doing it on kitkat, in recovery, and on stock rom

Try this. Worked for me after a weekend of dealing with power button issues.

power button problems/Hardware failure?
so i think i got my phone around october of 2012 and i recently hate it! i loved it..i dropped and broke my first one..clumsy me..but it was innevitable..it worked great..then it was stolen got a replacement..phone i have now..i rooted it was careful about device specific blah blah and i had already fixed a hard brick im not stupid...but then my phone started acting super weird..the screen shut down when it tried working it would be dark green and fuzzy...a weekend later i pulled the sim and out it back in.. (for no reason) .. and my screen worked but my power button didnt work any more my screen wont stay asleep and my power menu continually pops up and it reboots (never completely)...like the power button would be jammed...any help idk if i can still get the root off and use triangle away cause my phone doesnt hardly stay working and when in C.W.M it selects random options usually reboot phone (first option)...is my warranty void will they replace my phone again even rooted...it is a hardware not software failure?
btw
using sch-i535 verizon galaxy s3, d2vzw, runnin pac-man jb 4.3.1 <----wasant when this first happened i restored a backup i was running cm 10.2 (jb 4.2.2)
i loved my galaxy s3 please help me love it again

I've had this problem as well but haven't found a solution yet, I'm going to try smashing it on a table like the above video suggests and see what happens
the weirdest part for me is when I odin back to stock the button works perfectly, like brand new, and then I clean flash any rom (4.2.x & 4.3) and it gradually starts messing up again, usually takes about 4-5 days for it to get to the point where I can't even boot to recovery/download.. luckily using the stock samsung cable allows me to enter and stay in download mode to odin back to stock.. rinse and repeat

LoL yeah here's the fix "smash your phone on the ground, but wait, if it doesn't work just do it harder"
That's the best thing I have ever seen.....
This has happened to me twice now.....I just take the button off and make a widget on my homescreen to lock the phone.... LoL LoL LoL this advice is too funny
"yeah dog just run over your phone wit a forklift, problems will be solved yo."

SlimSnoopOS said:
Try this. Worked for me after a weekend of dealing with power button issues.
Click to expand...
Click to collapse
Thank you so much SlimSnoopOS for posting that video link. Worked perfectly.

[Q] Need help recovering from QPST -URGENT-

Hey guys I need some help asap! I have had my Nexus 5 for about 2 weeks now. I had rooted it and put in cwm recovery. The other day I had switched over art from Dalvik. Later in the day I was using linux deploy from the app store. About an hour after when i was browsing the web the device returned an error stating that the devices memory was full..... I knew there was no way. I powered off the device and that was the last of it. It does not power on in the traditional sense it does not go into recovery it does not go into fastboot and it certainly not the OS. Just a black screen. However it does get recognized as a QHUSB device when connected to a PC after fussing with the drivers adb or fastboot drivers no matter the version do not work the device will appear in device manager as though it is there but running adb devices or fastboot devices returns no devices. After extensive driver version attempts and toold nexus rootkit etc i have found that the slightly responsive driver for anything is the LG AndroidNet Diagnostic driver. Although QPST hangs when trying to download via Sahara and CDMA workshop will connect but it does it fails when trying to read from phone. I know there are tools for devices in the same situation. Is there one for the nexus 5? Or can someone help me recover this bad boy? This version is the google play version and not the t-mobile or sprint variant. HEEELP!!!!!!!!!! Thanks.

Try to turn off your phone. I know it looks like it is turned off but it's not. Press power button about 10secs then release it and then press and hold it with the two volume keys. You should find yourself in the bootloader and there you could flash stock rom back.
If that not works. Connect the phone to the pc. Open up device manager. Press and hols power button and when the qhusb dissapears press and hold both volume keys while you still pressing the power key. You may end up again in qhsusb, try to wait a little bit more with the pressing both volume keys after each try.
I hope it will work, but I know a guy who bricked his device like you with cwm, his phone also appears as qhusb device on the pc and he could not recover.
Tha last thing you can do is send it back to google to recive a replacement device.
Sent from my Nexus 5 using xda app-developers app

Tried it
bitdomo said:
Try to turn off your phone. I know it looks like it is turned off but it's not. Press power button about 10secs then release it and then press and hold it with the two volume keys. You should find yourself in the bootloader and there you could flash stock rom back.
If that not works. Connect the phone to the pc. Open up device manager. Press and hols power button and when the qhusb dissapears press and hold both volume keys while you still pressing the power key. You may end up again in qhsusb, try to wait a little bit more with the pressing both volume keys after each try.
I hope it will work, but I know a guy who bricked his device like you with cwm, his phone also appears as qhusb device on the pc and he could not recover.
Tha last thing you can do is send it back to google to recive a replacement device.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Thank you, I have tried that and it does not work. My fear is that I will not be able to return as I have pulled the battery and have custom software.
I was hoping there was some way to recover when the device is in the LG Android diagnostic mode.

joutcast said:
Thank you, I have tried that and it does not work. My fear is that I will not be able to return as I have pulled the battery and have custom software.
I was hoping there was some way to recover when the device is in the LG Android diagnostic mode.
Click to expand...
Click to collapse
Why did you pull the battery? You could have rma'd it.

jd1639 said:
Why did you pull the battery? You could have rma'd it.
Click to expand...
Click to collapse
Thank you your comment is of help right now....

joutcast said:
Thank you, I have tried that and it does not work. My fear is that I will not be able to return as I have pulled the battery and have custom software.
I was hoping there was some way to recover when the device is in the LG Android diagnostic mode.
Click to expand...
Click to collapse
If there is no traces or signs you removed the battery (like finger prints or damaged back cover) then google will never find out you have custom rom on your device, because they cant turn it on. It does not worth the effort to google to somehow hack the data out from the broken flash chip. What they will do is that they try to turn it on, then they see it is not possible so they flas stock rom through qhusb ans that wipes all the data of your phone and reformat everything. Or maybe unbricking the device does not wort the effort too and google just send you a replacement device.
Sent from my Nexus 5 using xda app-developers app

bitdomo said:
If there is no traces or signs you removed the battery (like finger prints or damaged back cover) then google will never find out you have custom rom on your device, because they cant turn it on. It does not worth the effort to google to somehow hack the data out from the broken flash chip. What they will do is that they try to turn it on, then they see it is not possible so they flas stock rom through qhusb ans that wipes all the data of your phone and reformat everything. Or maybe unbricking the device does not wort the effort too and google just send you a replacement device.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
OK, GREAT that first option they do....DOES ANYONE KNOW HOW TO DO THAT???? I know it can be done on other devices as shown in the link below
http://forum.legija.net/showthread....g-galaxy-S4-(i9505-and-similar)-via-USB-Cable

joutcast said:
OK, GREAT that first option they do....DOES ANYONE KNOW HOW TO DO THAT????
Click to expand...
Click to collapse
You are asking for help with it. To answer your question. It's called jtag and lots of people know how to do it. I'd look for "mobile tech videos". QHUSB is a true brick.
EDIT: Or you could just RMA it. I think that might have been what you where asking to begin with. lol

@joutcast dude it sounds bricked. I'm sure Google will give you another device if you RMA it.
I'm very serious. Im Not being smart about it. I highly doubt Google will do anything to check unless you left obvious traces of it being tampered.
Sent from my Nexus 5 using Tapatalk

You need to JTAG it. It'll cost you about $65 and you'll have a working phone again. I'd check craigslist for JTAG in your area, a lot of people are doing it now.
And stop being so sensitive.

Work the problem and not each other.
Thread Cleaned

_MetalHead_ said:
You need to JTAG it. It'll cost you about $65 and you'll have a working phone again. I'd check craigslist for JTAG in your area, a lot of people are doing it now.
And stop being so sensitive.
Click to expand...
Click to collapse
Sensitivity is what I do best LOL. I went ahead with the RMA route and have been with out a phone for over 15 days. The reason being I am unemployed and could not afford the $450 for an advanced replacement. I still have not heard a peep out of Google as to when I can even think about getting a tracking number from them..... What cracks me up is the fact that if I had done an advanced RMA the hold on my card would of fallen off a long time ago and at that point they still would not have any security on the device. Not only that they have had my phone since Tuesday of this week.

Power button magically stopped working

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