Dear all,
I am so disappointed that my AT&T HTC One is not working right now.
It was my first time doing rooting and flashing a ROM, and I thought it would be as easy as doing jailbreak on iPhone.
For some reason, I just did not backup my phone.
Here is what happened:
1. I went to HTC official site to get my phone rooted, and it went well, I assume.
2. Then I found out that titanium backup told me my device was not rooted properly.
3. I was too confused to figure out what I should do, so I went for a Chinese software.
It says that I can be rooted and unlocked within one click.
4. So I used the software and it worked.
5. I realized my phone was still s-on, and someone commented that flashing some ROM would make it s-off.
6. I went for this "one click" software again... and it destroyed everything...
7. In the beginning, my phone would stop at the One logo. Then, I used boot starter or whatever it called to install recovery?
8. In the end, the phone won't boot. It shows the HTC logo and becomes black screen.
9. My computer cannot detect my phone as well. Yes, I have tried every option in boot menu.
What can I do right now?
Please? Anyone?
Thank you all...
Can you boot into the boot loader menu?
With phone powered off hold down the power button and volume down button at the same time, phone should load a menu with a mostly white screen and different rows of text.
If you can get a picture of the info on that screen it would be helpful.
Sent from my HTC One using xda app-developers app
htc logo stuck on screen
FanDroid09 said:
Can you boot into the boot loader menu?
With phone powered off hold down the power button and volume down button at the same time, phone should load a menu with a mostly white screen and different rows of text.
If you can get a picture of the info on that screen it would be helpful.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
i have the same problem and its just stays on the htc logo,no down button and power dont work.even let the battery drain and charged to press volume down and power and it still just stays at the htc logo.
Related
i just got my dell streak and so far when i press the start button i see the dell logo and then the screen just hangs there (black) until i remove the battery. I tried to charge the battery up to full but i since i do not see a battery charging indicator i really dont know what to do with it. help
everything is stock, i dont even know if its GB or not since i havent been able to start it up It's a rogers phone though
Tried a factory reset
Sent from my Dell Streak using xda premium
yeah i tried that. i also went into fastboot and it says on the bottom "default nv checked #2" and i cannot click on the fastboot option. When i press the volume rocker up or down the screen goes dark and then comes back in a little bit saying that the "screen calibration FAILED"
i did however succeed one time in getting the screen calibration to "pass" and then i was able to press the fastboot option. From there i used the DSC installer "flash" exe and it updated the phone. Then after the reboot i was able to see the lock screen but unable to press any buttons.
im figuring
1) the touch screen is defective, hence iam unable to press anything and thus the screen calibration keeps failing
2) the connect to the touch screen is broken or lose and i might need to open'her up to see
3) fack it, ill just tell rogers to send a replacement.
So far ive done step 3 but since its the weekend, i felt like tinkering.
Hi everybody,
I decided to change my wallpaper on my phone and the app seemingly crashed to the point where the power button won't turn the screen on. Plugging the power in will power the screen on, but an error comes up saying that Go Launcher is experiencing problems (force close, wait, etc). Regardless of what I hit, I'm forced to unlock my phone as usual, but it doesn't unlock. I'm stuck staring at a black screen...can't get to settings, notification bar, anything. Help please?
helloterence said:
Hi everybody,
I decided to change my wallpaper on my phone and the app seemingly crashed to the point where the power button won't turn the screen on. Plugging the power in will power the screen on, but an error comes up saying that Go Launcher is experiencing problems (force close, wait, etc). Regardless of what I hit, I'm forced to unlock my phone as usual, but it doesn't unlock. I'm stuck staring at a black screen...can't get to settings, notification bar, anything. Help please?
Click to expand...
Click to collapse
Try getting into stock recovery and factory reset
ICS CM9 X2
Did you try a battery pull?
Sent from my cm7 using XDA
kennyb6 said:
Try getting into stock recovery and factory reset
ICS CM9 X2
Click to expand...
Click to collapse
Ended up having to do this. Thanks.
Hi all..
I have a problem with my DNA. Sometimes, like maybe once every few weeks or so, the touch screen will not respond correctly.
Here's what happens:
1. I turn on the display while the phone is already running. (meaning, I'm not booting up when it happens)
2. I try to slide the unlock widget up but it doesn't respond.
3. I hold the power button, and it says to continue holding it for 3... 2... 1.. seconds. However, at 1 seconds, it never does anything. I've held it for 2 or 3 minutes at times, and no reboot.
4. I swipe randomly around the screen and notice that some of my quick launch icons or the unlock slider bump up momentarily, but not enough to unlock the phone.
5. I continue swiping randomly, with a random number of fingers, and eventually the stars align and the phone is unlocked.
6. Once the phone is unlocked, tons of random touch presses occur. Random apps will open, messaging, etc. Sometimes, it opens the phone app and randomly presses things. It does this at a very, very rapid rate. I usually panic and turn off the display so it stops.
7. I manage to unlock it and hold the power button until the "Reboot/Shutdown/Airplane Mode" window appears and STAYS on the screen long enough for me to tell it to reboot.
8. After it reboots, the problems are gone and the touch screen returns to its proper functionality.
Has anyone had this problem before or know why it's happening? Or what can contribute to it?
Insertcoin rom or any kernel?
It's kernel issue. I have same problem. Flash another kernel fix it
Sent from my HTC Droid DNA using Tapatalk
Huongnv said:
Insertcoin rom or any kernel?
It's kernel issue. I have same problem. Flash another kernel fix it
Sent from my HTC Droid DNA using Tapatalk
Click to expand...
Click to collapse
Forgot to give some info:
I'm on default Rom, not rooted, nothing special.
To fix this problem, should I go ahead and root and install a new Kernal?
Garmy said:
Forgot to give some info:
I'm on default Rom, not rooted, nothing special.
To fix this problem, should I go ahead and root and install a new Kernal?
Click to expand...
Click to collapse
Flash a clean rom
U can use stock img with latest 4.4.2 sense 5.5 official or viper 4.4.2 sense 6
Sent from my HTC Droid DNA using Tapatalk
My screen started doing this, for me it is hardware failure. When you enable "show touches" from developer options, does it show 3-7 ghost touches? Mine is doing this (shattered screen and that is the only side effect, ha)
Sent from my HTC6435LVW using xda app-developers app
--solved--
Okay I need some help to fix my phone because somehow I did something to my phone it really did not like. I will try to keep it as short as possible.
Since last week I was running liquidsmooth nightly LS-KK-v3.2-2014-10-13-umts_spyder on my xt910 and it was running as smooth as it could get.
This morning I decided to simply reboot the phone for no particular reason, battery above 90%, it shut off, it turned back on, showed the motorola logo and then a black screen. nothing else and I have not been able to make it show anything else.
volume+, volume- and power button in every combination, result in the same situation.
on the black screen I can press volume keys to make it vibrate but I am not sure what it actually does.
windows recognizes the device as motorola usb composite device and an MTP XT910, so far so good. Even RSD lite shows it as xt910 and connected though all device properties (IMEI etc.) are N / A and flashing results in "phone could not change to fastboot mode"
I found a similar problem described here: http://forum.xda-developers.com/showthread.php?t=1767469 (especially the last post).
Since the last reboot I installed plants vs zombies 2 and reinstalled google chrome, nothing else has changed.
I can't get into the fastboot menu to select ap fastboot, I tried doing the right steps at the black screen blindly but apparently it is not the same screen.
I am pretty clueless what to try next and I am not even sure if the phone is still being charged when I connect it to the charger.
sooo what to do?
thx a lot
fleity said:
Okay I need some help to fix my phone because somehow I did something to my phone it really did not like. I will try to keep it as short as possible.
Since last week I was running liquidsmooth nightly LS-KK-v3.2-2014-10-13-umts_spyder on my xt910 and it was running as smooth as it could get.
This morning I decided to simply reboot the phone for no particular reason, battery above 90%, it shut off, it turned back on, showed the motorola logo and then a black screen. nothing else and I have not been able to make it show anything else.
volume+, volume- and power button in every combination, result in the same situation.
on the black screen I can press volume keys to make it vibrate but I am not sure what it actually does.
windows recognizes the device as motorola usb composite device and an MTP XT910, so far so good. Even RSD lite shows it as xt910 and connected though all device properties (IMEI etc.) are N / A and flashing results in "phone could not change to fastboot mode"
I found a similar problem described here: http://forum.xda-developers.com/showthread.php?t=1767469 (especially the last post).
Since the last reboot I installed plants vs zombies 2 and reinstalled google chrome, nothing else has changed.
I can't get into the fastboot menu to select ap fastboot, I tried doing the right steps at the black screen blindly but apparently it is not the same screen.
I am pretty clueless what to try next and I am not even sure if the phone is still being charged when I connect it to the charger.
sooo what to do?
thx a lot
Click to expand...
Click to collapse
You have a black screen but the phone isn't really turned off...
When you see that black screen,press and hold the power button until you see the white line flashing for a moment,like on Tv,that means it's turned off.
Immediately after that press all 3 buttons,vol-,vol+ and power button to get into the boot menu and then choose AP Fastboot from there.
Sent from my Razr XT910
interesting, first turning it off by holding power allowed the three-button combo to bring up the fastboot menu. thanks a thousand times.currently flashing sbf image
:highfive: worked
fleity said:
interesting, first turning it off by holding power allowed the three-button combo to bring up the fastboot menu. thanks a thousand times.currently flashing sbf image
:highfive: worked
Click to expand...
Click to collapse
No problem
Sent from my Razr XT910
just a quick thought, is it possible that I provoked the black screen by using liquidsmooth on the system1 slot?
Not likely. Liquid Smooth has been in my #1 slot for quite a while. (Not stock side, just 1st slot on safestrap....)
fleity said:
just a quick thought, is it possible that I provoked the black screen by using liquidsmooth on the system1 slot?
Click to expand...
Click to collapse
very unlikely
So i was just forced to install Lollipop by Sprint. I was having a minor S-Pen issues and Sprints "FIX" was to update me to Android 5.0 Lollipop. Well now I have 500000000 other issue with my phone. Most i can live with, but there are 2 in particular that at driving me absolutely bonkers and I cant fix. I was hoping someone around here would have an idea how to fix it without me having to root, and go back to the previous OS. (The Sprint Root seems a little intimidating and I cant afford to brink my phone even for 20 minutes).
The main issues I am having are regarding the lock screen. I cant get the lock screen to stay open more then 3 or 4 seconds and if I botch my pattern or don't swipe fast enough, the screen will turn itself off. Then I have to turn the screen back on and try and unlock it again. Sometimes the screen even turns off in the middle of trying to unlock it. It is EXTREMELY annoying having to try and unlock my phone 4 or 5 times just to get to the notification screen ...... As for the Notification screen, once i finally am able to get my phone unlocked, then when i try and swipe my notification bar the phone will sometimes turn the screen off as well, then I have to go BACK to trying to unlock the phone and try and do everything faster then 2 jack rabbits banging in order to just get to my notifications. Its become a major problem in that sometimes I just cant get the sequence and speed right for 10 or 15 tries.
Anyone else having these issues or have a fix???
jcohenlv said:
So i was just forced to install Lollipop by Sprint. I was having a minor S-Pen issues and Sprints "FIX" was to update me to Android 5.0 Lollipop. Well now I have 500000000 other issue with my phone. Most i can live with, but there are 2 in particular that at driving me absolutely bonkers and I cant fix. I was hoping someone around here would have an idea how to fix it without me having to root, and go back to the previous OS. (The Sprint Root seems a little intimidating and I cant afford to brink my phone even for 20 minutes).
The main issues I am having are regarding the lock screen. I cant get the lock screen to stay open more then 3 or 4 seconds and if I botch my pattern or don't swipe fast enough, the screen will turn itself off. Then I have to turn the screen back on and try and unlock it again. Sometimes the screen even turns off in the middle of trying to unlock it. It is EXTREMELY annoying having to try and unlock my phone 4 or 5 times just to get to the notification screen ...... As for the Notification screen, once i finally am able to get my phone unlocked, then when i try and swipe my notification bar the phone will sometimes turn the screen off as well, then I have to go BACK to trying to unlock the phone and try and do everything faster then 2 jack rabbits banging in order to just get to my notifications. Its become a major problem in that sometimes I just cant get the sequence and speed right for 10 or 15 tries.
Anyone else having these issues or have a fix???
Click to expand...
Click to collapse
I can't say I had any problems like this. I was running Stock rooted OC5 for a while and had really no problems with it. I didn't have any pattern or pin unlock though, so maybe it would have been different? I would have stayed stock but my Flashaholic took hold and made to start trying out other ROMs.
As for rooting, I have found it very easy to root this phone. I haven't had a problem either using auto-root or flashing superSU.
Factory reset is easy.
w7excursion said:
Factory reset is easy.
Click to expand...
Click to collapse
before a factory reset, you might try doing a wipe of the cache partition.
turn your phone off
press and hold, Volume up + home key + power until you see the blue booting to recovery mode message
wait for recovery mode to display (the menu will show after the green robot)
use the volume rocker to move down to wipe cache partition and press the power button to select it.
now select the yes line and press power
now reboot your phone and see if that helps with the lock screen behavior
good luck
jdelano said:
before a factory reset, you might try doing a wipe of the cache partition.
turn your phone off
press and hold, Volume up + home key + power until you see the blue booting to recovery mode message
wait for recovery mode to display (the menu will show after the green robot)
use the volume rocker to move down to wipe cache partition and press the power button to select it.
now select the yes line and press power
now reboot your phone and see if that helps with the lock screen behavior
good luck
Click to expand...
Click to collapse
This seemed to work so far. Ill keep you posted as I use it more today. Thank you so much
jcohenlv said:
This seemed to work so far. Ill keep you posted as I use it more today. Thank you so much
Click to expand...
Click to collapse
Glad to hear that, I hope it stays that way
You should read more before trying to root