So I've searched here AND the entire net for a fix for this but I cannot find it anywhere. I'm decently experienced in the area of androids, flashing, and rooting and currently own a rooted Moto G Play running a debloated stock rom with Xposed installed as my main device (besides the point but just so you know my level of experience.)
I was recently given a HTC Desire 526 and was told by the giver that she couldn't turn it on. So obviously my first thought was to try to enter bootloader mode. I charged the device and held the volume up and power keys to enter bootloader, and it was successful, but still no image on the screen, mind you there is zero visible damage on the phone screen or water damage on the inside so I'm guessing it can't be that the screen is broken physically. I confirmed that it was in bootloader by running fastboot and it is listed under devices when I run "fastboot devices." Vibration works and it occasionally outputs sound so I know the phone turns on (at least). I'm completely new to HTC devices and when i try to do almost anything involving flashing with fastboot I get the s-on error. Adb isn't available as I know that developer options, and furthermore, usb debugging has not been enabled on this device at all in the past.
Can I hard reset with just hardware keys (vol up, vol down, and power)? Everything online says yes and then the instructions go on to explain how to reset via the on screen bootloader menu navigation, that of which I can't see nor navigate with a black screen (I know these "solutions" to this problem make no sense considering I asked about a device with a screen that won't turn on, very frustrating haha.) If not, does anyone have any suggestions on what I could do to get the screen to work? Not sure if this matters but it is a verizon phone. Any info is appreciated as I'm coming to my last leg trying to get this going. So annoying feeling it vibrate and hearing sounds because I feel like it is definitely fixable without replacing the screen but I'm not 100% sure. Thanks.
Edit: My only solution is to see if someone who owns this device (currently I know no one with this device) can direct me on what to push, when, to reset without my screen, so I can navigate through that phone or through pictures of it.
This post can be deleted. Still don't know the cause but it turned on and all is well now. Now I'm just searching for a proper root method!
Related
Yesterday I rooted my HTC Droid Incredible (AMOLED). Following that I installed Cyanogen Mod 7, Build 30. The rom was running perfectly until earlier today. Half way through the day, at a point at which I'm sure I still had battery power, the screen no longer functions. Restarting is responsive, but still leaves a blank screen. The same goes with the method of holding the volume down key and the power button.
How may I restore function to my phone, whether it be unrooting or however else? Whatever the method, how can it be done without a visual onscreen?
Less important but still of interest, what is the likely cause that transformed the phone from one working to bricked so randomly?
Thank you.
Did you drop it or get it wet?
Sent from my Incredible using XDA App
Were you ever able to use ADB before this happened? If so, then can you try it now. If you can at least see something, you could give that a try and try some trouble-shooting from within. I'd guess that if something serious happened to the actual screen or interface to it, that it might show up as a hardware error in the log. (#logcat, dmesg, ).
Have you yanked the sdcard and mounted it on a PC? (if you can, you might be able to save the content, reformat 'fat32' and maybe for starters just try to restart it with the blank reformatted card. If that works, well, you're OK.
Do you think it is booting fully, but just not able to output to the LCD or do you think it is only doing the first stage and dropping into the recovery screen? Was this thing overclocked? If so, have you tried a 'safe boot' yet (which disables anything past a vanilla startup like setcpu type things)? (instructions are around XDA somewhere).
Without seeing.. I suppose you can put a standard image on the phone (as in RMA) if you get the 'timing' down for when to push buttons, (assuming that is still doable).
Alright, so here is what's going on.
I had my alarm go off earlier today, got up, unplugged my phone like normal. I swiped off the notifications I didn't care about like a tapatalk message etc. I noticed that Google Current's automatically updated. I'm sure that's no huge deal.
I locked the screen and went about my day. I tried to swipe to unlock, and the phone freezes and reboots. The phone is responsive until you unlock it, then it just freezes and reboots.
Tried safe mode once, and it worked fine. I then turned it off, and tried normally booting again, same freezing and rebooting. So I went to go back to safe mode, and now safe mode is doing the same thing, which means that a factory reset is now out of the question.
What the hell man.
Specs:
- Samsung Galaxy Nexus
- All stock apps except added Facebook and Tapatalk
- Jellybean 4.2.2 software I believe. I'd double check if I could.
- Still locked and unrooted
Any ideas on where to go from here? No warranty, so any ideas would help
It turns on, goes to lock screen. Then freezes when I try to get anywhere from that lock screen. Even on safe mode.
Then it will reboot automatically after about 30 seconds.
I should note I received a text in this time, and thought maybe just pulling the notification bar down and going straight to the text would work. The notification bar works, but when I hit the text, it froze the same way.
This must be some sort of self check or some Android process crashing. But I can't utilize safe mode to fix it.
Any ideas on what to do? I know there are threads with this problem, but this involves an unrooted phone, of which I have seen no threads, or threads with answers. I am not experienced with getting too far into Android, so just a direction to go, or something to try when I get home would be awesome. (At work currently)
The only options I have right now are the options upon booting with the volume down, which are Start - Restart bootloader - Recovery Mode and Turn off. In this screen, here is my info:
FASTBOOT MODE
PRODUCT NAME - tuna
VARIANT - maguro 16GB
HW VERSION - 9
BOOTLOADER VERSION - PRIMELA03
BASEBAND VERSION I9250UGLL1
CARRIER INFO - NONE
SERIAL NUMBER - xxxxxxx
SIGNING - production
LOCK STATE - LOCKED
In recovery mode, I see a dead android guy with a red triangle and an exclamation mark in it.
I realize you guys probably get a lot of dumb questions so I tried unloading all the information I could. My replies will be 5 minutes apart, as I'm new and I see that's a restriction on being here.
Thanks in advance
You can try unlock the bootloader (it'll erase your data so be careful) and then try flashing the oficial google image via fastboot and see if it solves it.
EDIT: in that screen of red triangle press up and power at the same time to show the options. There you can do a factory reset to see if it solves it. No need to unlock the bootloader that way.
Daedalus93 said:
You can try unlock the bootloader (it'll erase your data so be careful) and then try flashing the oficial google image via fastboot and see if it solves it.
EDIT: in that screen of red triangle press up and power at the same time to show the options. There you can do a factory reset to see if it solves it. No need to unlock the bootloader that way.
Click to expand...
Click to collapse
Got it. It works now, but curious, is this a common occurrance? I have no idea what caused it, which worries me. But it seems to be working fine.
Wasn't worried about data loss, I haven't had the phone for too long yet. I plan on just installing the minimum apps. The point of me not unlocking it was to avoid issues, but I had more luck with unlocking it than leaving it locked.
That said, I wasn't aware you had to hold the vol up and power button to get to the options from the dead Android screen. That was an oversight on my part when I was looking up for data.
Words cannot explain how thankful I am, so thank you
Moderators can close this thread if needed.
slipstreamconversion said:
Got it. It works now, but curious, is this a common occurrance? I have no idea what caused it, which worries me. But it seems to be working fine.
Wasn't worried about data loss, I haven't had the phone for too long yet. I plan on just installing the minimum apps. The point of me not unlocking it was to avoid issues, but I had more luck with unlocking it than leaving it locked.
That said, I wasn't aware you had to hold the vol up and power button to get to the options from the dead Android screen. That was an oversight on my part when I was looking up for data.
Words cannot explain how thankful I am, so thank you
Moderators can close this thread if needed.
Click to expand...
Click to collapse
No problem everything should work as intended now. What happened was a bit strange indeed. It it happens again with everything in stock then there is a possibility that it is faulty hardware and you should replace it. Maybe it was some configuration bug and nothing extreme
Daedalus93 said:
No problem everything should work as intended now. What happened was a bit strange indeed. It it happens again with everything in stock then there is a possibility that it is faulty hardware and you should replace it. Maybe it was some configuration bug and nothing extreme
Click to expand...
Click to collapse
Fauly hardware can cause this issue? I baby this phone, has yet to be dropped (let's admit, it's inevitable), the only thing it's seen is three drops of water that fell off my sunroof onto it. I immediately grabbed my phone and wiped it off, but it was all on the screen, not in the speaker or anything.
Either way, I'll keep an eye on it. Thanks again
slipstreamconversion said:
Fauly hardware can cause this issue? I baby this phone, has yet to be dropped (let's admit, it's inevitable), the only thing it's seen is three drops of water that fell off my sunroof onto it. I immediately grabbed my phone and wiped it off, but it was all on the screen, not in the speaker or anything.
Either way, I'll keep an eye on it. Thanks again
Click to expand...
Click to collapse
Yes. My phone recently was stuck on a bootloop and I've already sent it for repair. Yeah drops are never good
No problem
Bought this phone off the electronic bay, arrived totally fine, no signs of any damage, worked just fine. Upgraded it with the sony OTA updates to 4.1 and then the screen started acting a little funny. Sometimes when hitting the unlock button it would just light up the backlight. Then a few days later it stopped ever doing anything besides lighting up the backlight. Then it progressed to doing what I show in the video.
It still plays alert tones when i get messages or calls, but obviously the phone is totally unusable, but charges up fine.
any ideas what is going on here? Called Sony for a repair, but I was unaware they just charge a flat $185 irregardless of what the problem is...ridiculous.
foofiebeast said:
Bought this phone off the electronic bay, arrived totally fine, no signs of any damage, worked just fine. Upgraded it with the sony OTA updates to 4.1 and then the screen started acting a little funny. Sometimes when hitting the unlock button it would just light up the backlight. Then a few days later it stopped ever doing anything besides lighting up the backlight. Then it progressed to doing what I show in the video.
It still plays alert tones when i get messages or calls, but obviously the phone is totally unusable, but charges up fine.
any ideas what is going on here? Called Sony for a repair, but I was unaware they just charge a flat $185 irregardless of what the problem is...ridiculous.
Click to expand...
Click to collapse
Hi,
The best way to rule out any software problems would be to flash the latest 6.2.B.1.96 ftf using Flashtool. So, first make sure that the phone has enough charge, then press and hold the volume up+power combination until you get three vibrations. Then press and hold the volume down key and simultaneously connect the USB cable when Flashtool prompts you to. Once the flashing is complete, disconnect your phone and turn it on normally.
Regards,
abcdjdj
Sent from my LT26i using xda app-developers app
I already flashed back to stock just using the sony bridge app. It seemed to work fine (nothing showed up on the screen the entire time). After the phone boots up I can hear notification sounds as it gets all my texts and voicemails/whatever else. But otherwise it still does what is shown in the video below:
here is the video again, not sure if it worked last time:
http://www.youtube.com/watch?v=jbrpsWburMw
foofiebeast said:
I already flashed back to stock just using the sony bridge app. It seemed to work fine (nothing showed up on the screen the entire time). After the phone boots up I can hear notification sounds as it gets all my texts and voicemails/whatever else. But otherwise it still does what is shown in the video below:
here is the video again, not sure if it worked last time:
http://www.youtube.com/watch?v=jbrpsWburMw
Click to expand...
Click to collapse
What bug u reported is the bug of .200 and .211 official bug.. Its fixed in .96fw.. Wipe everything when u flash .96fw... So there won't be any problems..
sudhindrakv said:
What bug u reported is the bug of .200 and .211 official bug.. Its fixed in .96fw.. Wipe everything when u flash .96fw... So there won't be any problems..
Click to expand...
Click to collapse
Well there is a slight problem.
The phone does not have an unlocked bootloader yet, so I can't use flashtool. It has been flashed back to stock using the method I mentioned above. I have just finished installing ADB because (bear with me please) there is no way to turn the phone into fastboot mode without turning it off (I cannot currently turn it off because I can't see what is happening on the screen and don't remember how this phone works when you hold down the lock key to turn it off). I can perform a hard reset, but no way to just get it to turn off entirely.
So I thought I could use adb to shut it down, but adb won't work unless I have debugging enabled, which again I can't do unless I could basically just blindly navigate the menu to those buttons.
Although if I wait until the phone is fully dead then I can hopefully get it into fastboot mode, but that only gives me one chance. Plus it has a full charge right now, so that's going to be awhile.
Any suggestions?
I can get it in to fast boot if I'm quick, but I still can't enable debugging beforehand so its semi worthless.
I've been trying to watch videos to see where the button placement is to navigate through the menu to blindly enable debugging, but I can't seem to figure it out. It also doesn't help that I have no idea what version of android is now on the phone. I used the mac sony bridge app to restore the phone, but i'm not sure if that set it back to stock stock, or what version of android it set it to.
I am also now even more confused because I connected the phone to the computer and when I browsed it, all the pictures I took were still there...which should have been wiped when I restored it with sony bridge...
figured out it was 4.1 and watched review videos until i found one that showed the menu layout (although now I realize google images would have been more helpful).
Now going to see if I can get the bootloader unlocked.
I still feel like flashing 6.2.B.1.96 isn't going to do anything, because I assume that is what the sony bridge app flashed to it. Also I don't see where you are talking about that the issue I am having was a known issue, if you could point me in that direction that would be very helpful.
EDIT: Actually I'm not sure I enabled debugging after all, as when I do adb devices, no device is listed as running, just a blank space. Though I'm still not convinced doing the above would do anything, as it is basically what I have already done, just with flash tool as opposed to the official sony route.
Anyone have any ideas? I got a torx 6 and opened the phone, checked the connection between the motherboard and phone and it is fine. Screen is still having same issue.
I would be happy to just buy a replacement part for it, but i have no idea what part is messing up. Is it the display (the touch works fine) or is it the motherboard (it seems weird that it would be this because the phone functions completely normally, I even accidentally answered a call yesterday).
If i was to try and replace the LCD (or whatever it is) would I have to replace the digitizer as well? At which point it would make more sense to just sell the phone for parts I suppose.
You can use the flash tool by bin4ry with a locked bootloader. Not sure if you're past that stage though.
Sent from my LT26i using xda app-developers app
dkconor said:
You can use the flash tool by bin4ry with a locked bootloader. Not sure if you're past that stage though.
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
I'll go ahead and try that out, but is there really much of a point do you think? Considering I've technically flashed the phone back to stock using the official software, why would it be any different doing it this way?
I am asking honestly btw, not trying to sound rude. I'm thinking it is more of a hardware failure, i just have no idea what part exactly is failing.
The phone itself works totally 100% fine, the touch works totally 100% fine, the only thing that is not happening is the data getting to the screen and displaying. The screen just flashes white for a second and then fades out (as you can see in the youtube link). Or it flashes a solid block of white at the top in the middle and faded white the rest of the way down and then it slowly all fades out (or disappears immedaitely if i press the lock button. The buttons all work fine (physical and touch) and i can navigate around the phone, albeit totally blindly.
This is really frustrating, and I'm pretty disappointed to see how sony had no interest at all in helping me resolve this situation.
Flashtool works with lock and unlocked bootloader
XDAプレミアムを使用 して私のLT28hから送ら れてきた
UchihaDareNial said:
Flashtool works with lock and unlocked bootloader
XDAプレミアムを使用 して私のLT28hから送ら れてきた
Click to expand...
Click to collapse
....right i know, but why does that matter. Why would reflashing my phone help at all at this point. Did you even read my post?
Listen to us
Alright so you came to this thread for...help
We have told you numerous times to flash using this tool (dev host link):
http://d-h.st/Kb8
install the flashtool created by Binary (sorry for username spelling error)
Download the ftf
https://docs.google.com/file/d/0B18FXPCopQhkeXNoWGVWbzlRaG8/edit?pli=1
now USING FLASHTOOL (link 1)
FLASH the FTF (link 2)
A clean flash. This flash is different from the flash that Sony will provide you for obvious reasons.
Using this method will COMPLETELY remove any doubt whether the issue is regarding software or hardware. Then you dont have to "think" whether the issue is hardware related or software related.
Sorry if i sounded rude but i had a hard time comprehending why you would not use the advice given by i believe 2 different indiviuals on a questions and answers thread.
424aca said:
Alright so you came to this thread for...help
We have told you numerous times to flash using this tool (dev host link):
http://d-h.st/Kb8
install the flashtool created by Binary (sorry for username spelling error)
Download the ftf
https://docs.google.com/file/d/0B18FXPCopQhkeXNoWGVWbzlRaG8/edit?pli=1
now USING FLASHTOOL (link 1)
FLASH the FTF (link 2)
A clean flash. This flash is different from the flash that Sony will provide you for obvious reasons.
Using this method will COMPLETELY remove any doubt whether the issue is regarding software or hardware. Then you dont have to "think" whether the issue is hardware related or software related.
Sorry if i sounded rude but i had a hard time comprehending why you would not use the advice given by i believe 2 different indiviuals on a questions and answers thread.
Click to expand...
Click to collapse
Hi,
because I could not follow the advice from the first user because the bootloader is locked. The second person gave me the advice, but honestly it seemed like pretty pointless advice. I don't understand how it is "obviously different" if it is literally flashing the same firmware (at least the first advice was that). I don't think it's that strange to ask why it would be any different.
To me it sounds like I had a broken window in my house and I asked someone how to fix it. I bought the replacement glass from store A and it didn't fit. I asked for help and someone pointed me to the exact same item at store B and said that surely it would work. Do you understand why this could be confusing? I feel like about half the time people give help on XDA it is very general and people are just looking for "thanks"...
I'll definitely try this though if you think there's a chance that it might work out differently. I'll try and get it set up tonight, thanks for the encouragement, I understand I probably sound stupid, just trying to figure out what to do.
Also, I assume this flash tool won't work if USB debugging isn't enabled. As I've said in previous posts, I can click things just fine, but because I can't see what I am doing, I don't have way of knowing where to click on the menu.
Does anyone have their phone set up with this version of android still. If you could take screen shots of each click to make to get to the dubugging box (and if there is a confirmation box) i would greatly appreciate it. I only had the phone for a week before this randomly happened, so I hadn't thought to enable debugging yet, as I hadn't even thought about custom firmware yet.
EDIT: Or even just a picture of what the screen that comes up when you long press to shut the phone down. I have no way of turning off this phone right now without just waiting for it to run out of battery.
Holding down the power button for a long time does nothing, holding vol up and power restarts it, but I need a way to turn it off. If i hold the power button for like a second so instead of locking it, the menu comes up, I just can't seem to find the freakin button for power off.
(please remember I can see nothing on the screen, it is just blank).
flashtool does not need debugging when you doing the actual flashing
to turn off the phone
SIMULTANEOUSLY hold down
Power+ Vol up + Vol Down (AT THE SAME TIME)
wait for about maybe less than 25 seconds and you will experience THREE short consecutive vibrations
at this time...the phone is off
then you can begin the flashtool method
Hi everyone,
first off, I've spend days now trying to find a fix. If I've missed anything, I'm sorry, it wasn't for lack of trying.
Here's the situation: I have acquired an HTC One X earlier this year which has worked quite flawlessly. I went ahead and unlocked the bootloader and installed a custom recovery. However, since I handed the phone off to my not-so-techy sister I did not use a custom ROM, and after the HTC update failed with the custom recovery I reversed that as well. The device should now be stock everything with unlocked bootloader.
After a few months my sister encountered heavy problems, though. She described them as battery related (wouldn't turn on correctly) and eventually she moved to a new phone. Now I have gotten the device back and I am trying to fix it. After charging it I managed to have it boot once. However, I but it to the side and wanted it to load some more. Ever since then the screen doesn't come on. The charging LED seems to work fine (eventually switched from red to green, too, indicating that the device is fully charged) and the button backlight still works, too. Most significantly though, the device is recognized as MTP device in Windows: I can access all the data in the storage without problems.
I have read that there is an issue with the HTC One X and the display connector so eventually I went ahead and took the device apart. It's lying in front of me now in pieces, but I still couldn't get the screen to come alive. The obvious conclusion would be to buy a new screen but the device doesn't feel like it's worth the investment. Besides, I would like to know for sure that it's the screen before I do anything.
So I turn to you guys and ask if you have any idea how I could access the phone via my computer. I tried to boot it up in bootloader mode but due to the strange standby methods HTC is using and not seeing anything on the screen I haven't been able to do that yet: Whenever I connect my USB cable it's recognized as MTP device, not ADB. Debugging seems to be deactivated so that doesn't seem to be an option. Does anyone have any idea how I could get the phone to talk to my computer (i.e. get into the bootloader or ADB screencast for sure)? With my Galaxy S I could simply plug in this dummy micro USB and would be sure to end up in download mode.
Any help is appreciated!
tl;dr: HTC One X screen is dead but LEDs work, is recognized as MTP device. How to make it talk to the computer?
Thanks,
rien
Alright, sometimes just posting stuff like this helps already. I was now finally able to get the phone into fastboot (apparently) and it's reacting to the fastboot commands. I suppose the next step is to load CWM and connect via adb. This way I can at least do a factory reset.
Does anyone have any ideas regarding the original issue with the screen? Especially since it does seem to work occasionally. And doesn't show any fragments...
Can I enable USB debug mode from within the recovery to work in the system?
Hey guys.
I am posting this particular issue because while I could find something similar to this issue (recovering from a bootloop for this very device), I couldn't find much in case your screen remained black afterwards.
I know why the bootloop took place (or at least I'm almost sure I know why):
-Via dr.fone, I chose the root option. This is a naïve move, as I know that one-click rooting options basically never work. Well, I know this now at least. However, the root never happened, as my device didn't even have OEM activated (there are some issues happening in this regard with lenovo). The program just couldn't continue, telling me that my phone wasn't registered in the data base or something like that. I was honestly just messing around because I didn't have OEM access, just wanted to see what error would pop up.
-The bootloop happened the day after, about 16 hours later. It also happened randomly, while the phone was idle without being connected to the PC. The screen was black, but I knew it was bootlooped because it would vibrate consistently every 10 seconds or so.
-If I pressed the Up+down+power buttons simultaneously, the blue LED in the top right corner would light up and a very long vibration would happen. There's a thread on this issue already, and adding a new firmware solved this.
-I tried to solve this by using ADB to add the stock firmware again. The bootloop stopped after this and the phone would charge. It didn't while bootlooping.
-I tried to factory reset and nothing happened. Except that my USB debugging option is now turned off, which makes things harder because I can't find a way to turn it on without having access to my phone.
I was wondering if there'd be a solution for this very situation. It's also worth noting that my screen is basically shattered, but I don't think it's an LCD issue because these two things happened at the same time. I find it too much of a coincidence.
Do you guys know what could be going on? I also wiped the cache data, even though my phone was factory reset just to give it a shot.
I very much appreciate your attention.
PS: this is literally only the display and the touch screen. Even the fingerprint sensor works.
Did you unlocked bootloader before root ?
Shreyash01 said:
Did you unlocked bootloader before root ?
Click to expand...
Click to collapse
No, the root didn't even take place. I tried to unlock the bootloader, but the Lenovo servers are down for that. So my bootloader is not unlocked.
I think that is the reason..
Your bootloader is not unlocked. You must have to ask someone before doing..
I think costumer care is the only option.