Related
Hey guys,
Running ILWT CM7. Flashed about two weeks ago. My phone has been working fine except for the past few days where it's been constantly freezing, requiring a battery-out and turn on, and rebooting on it's own.
Last time it froze, I removed the battery and turned back on, and it got to the "htc" logo and froze. After ~25minutes, I took the battery out and tried again.
Phone seems completely dead, won't respond to power on, volume down and power on, no lights come on when charger cable is plugged in. When USB cable is plugged in and no buttons or anything on the phone is pressed, my laptop attempts to install drivers.
Tried leaving battery out for 30minutes and trying again, but no luck.
Any suggestions?
Cheers!
Stuck in RUU mode?
Kaph said:
Hey guys,
...
Last time it froze, I removed the battery and turned back on, and it got to the "htc" logo and froze. ...
Phone seems completely dead ... When USB cable is plugged in and no buttons or anything on the phone is pressed, my laptop attempts to install drivers.
... Any suggestions?
Cheers!
Click to expand...
Click to collapse
Looks like your phone is stuck in RUU mode.
In RUU mode you see the silver "HTC" logo as long as your phone is connected to your computer with an USB data cable. No charging lights will show in this mode.
You can use the following command to boot your phone to Android:
Code:
fastboot oem boot
When that does not work, because your partition table or system partition might be corrupted, then you would have to use the correct RUU (Rom Update Utility) for your phone to get it back to a working state.
When you have a bricked internal memory chip (emmc) than nothing will work properly to restore your phone to normal working conditions.
In the case you have an engineering HBOOT you could boot a ROM from SD card, but that is a far shot.
Best regards,
Catherall
catherall said:
Looks like your phone is stuck in RUU mode.
In RUU mode you see the silver "HTC" logo as long as your phone is connected to your computer with an USB data cable. No charging lights will show in this mode.
You can use the following command to boot your phone to Android:
Code:
fastboot oem boot
When that does not work, because your partition table or system partition might be corrupted, then you would have to use the correct RUU (Rom Update Utility) for your phone to get it back to a working state.
When you have a bricked internal memory chip (emmc) than nothing will work properly to restore your phone to normal working conditions.
In the case you have an engineering HBOOT you could boot a ROM from SD card, but that is a far shot.
Best regards,
Catherall
Click to expand...
Click to collapse
Thanks for the help
When plugged in with the USB cable -> computer, I still get no response from the phone itself. Screen doesn't turn on, still seems dead. My laptop still says "Installing device driver software" to no avail, and phone is still dead. No lights, screen is off, nada. As though it was powered-off.
ADB Devices lists nothing, and fastboot oem boot hangs on <waiting for device>.
Am I out of luck? I could send the phone off for repair, but as I'm rooted I think warranty is void.
Remarks
Kaph said:
Thanks for the help
My laptop still says "Installing device driver software" to no avail, and phone is still dead
ADB Devices lists nothing, and fastboot oem boot hangs on <waiting for device>.
Am I out of luck? I could send the phone off for repair, but as I'm rooted I think warranty is void.
Click to expand...
Click to collapse
Windows seems to need a driver installation for using fastboot. Did you try to automaticall install device driver software? Have you installed HTC sync on your Windows computer?
When your device does not respond at all, and even refuses to connect in fastboot, then nobody can tell that you have been rooted.
Best regards,
Catherall
Sounds like your EMMC is fried, as of now I don't think there's a solution other than sending it back. Many say HTC accept and fix it even though it is s-off
Sent from my HTC Vision using XDA
did you get this worked out? i had a similar problem, ended up booting into fastboot by holding the trackpad and the power button, then just selected reboot and my phone powered on like nothing had happened, i was running the same rom.
Hey, did you alreasy tourned your phone to the fastboot mode?
Or does your device still have a black screen during boot?
I rooted this phone and when I was done trying S-OFF, phone would not respond to anything. It would only blink the orange notification light when I pressed Power and Vol+, or it would stay steady green with both Vol keys and Power. But the phone screen would never turn on. So after trying for hours to figure it out. I finally took the battery off, plugged the phone held pressed the power button and then put the battery in place the phone finally turned on and it worked. I turned the phone off again and it was doing the same issue. So I did the same step but this time with power and vol- to get in the bootloader and changed the hboot version to Desire Z. After that phone works perfectly, turns on and off with out any issues.
I did have to try the trick a couple of times idk why but it would work once in a while not everytime i tried it. Hope this helps anyone who also ends up with a similar issue.
Hey guys, I just inherited a non-functioning gnex. The previous owner said the phone was working fine until it fell of a ledge whilst in a bag. There is no obvious physical damage to the phone chassis or screen.
When I try to power on the phone, it vibrates once but nothing further seems to happen and the screen stays black. Several minutes later though, it starts making some of the android system noises seemingly at a random. If I press either of the volume buttons, it makes the standard volume up or volume down ringer noise. But nothing else really happens other than a continuation of some of the system noises. Sometimes it seems to load a media file or a game once the phone has been powered on with the battery in. When connected to a windows machine, the device mounts and the contents of the phone are uncorrupted.
I've tried different combinations of the power buttons+volume rockers to get into recovery or fastboot, but so far no luck.
I've also tried the OMAP flash but can't get the computer to recognize the phone as a omap4460 for more than a couple of seconds. I've tried the Samsung drivers and the universal naked driver.
The only thing I haven't tried is ODIN (which I'm assuming won't work without being able to enter fastboot or recovery?), which might be last act of desperation before giving up. I'll update accordingly.
Any other suggestions would be greatly appreciated.
I think you have a damaged screen.
try to put phone in odin mode, pull battery out, reinsert it, press volume down with power button for 3 seconds, connect to pc, open odin, see if odin recognize your phone.
Yep it sound like everything is working except for screen. You can try to open it to disconnect and reconnect the screen: http://www.ifixit.com/Teardown/Samsung+Galaxy+Nexus+Teardown/7182/1 (not sure exactly how) if it doesn't work you can order a replacement screen (eBay or such) and do it yourself (expensive and not easy) or give it to a repair shop (expensive but easy).
Sounds like it's a damaged LCD, not cheap...
I'd buy it off you if its the vz nexus (For parts.)
Thanks guys, I suspect it's the screen also. I haven't gotten around to Odin yet but that will likely be my final attempt at trying to revive the phone.
If it is just screen damage though, would that prevent me from entering recovery mode?
I should've probably already mentioned that this the international version of the gnex (i9250m from Bell Canada), so no LTE.
horseycraze said:
Thanks guys, I suspect it's the screen also. I haven't gotten around to Odin yet but that will likely be my final attempt at trying to revive the phone.
If it is just screen damage though, would that prevent me from entering recovery mode?
I should've probably already mentioned that this the international version of the gnex (i9250m from Bell Canada), so no LTE.
Click to expand...
Click to collapse
I'd recommend fastboot. Same thing, less steps, though you will need adb...
(If its available for your model, if not odin would be your only choice. )
Odin has a few more steps...
Long story short you wouldn't know if the screen is dead sadly, with out a replacement, best of luck!
Any insight on how to get into ADB or fastboot? As stated in the OP, the power button combos don't work. Furthermore, I don't have a way of enabling debugging mode.
I still haven't tried Odin, I won't have access to a windows pc for a few more days. I'll update accordingly.
Getting into fastboot is very easy:
Turn off. Since you can't see anything pull battery and reinsert to make sure.
Press volume up, volume down and power at the same time for few seconds.
You feel a vibration like it does on every boot.
That's it, you are in fastboot mode.
To verify, plug into computer and type fastboot devices
If it writes something like this:
0149BD34ABCDABCD fastboot
then you are in fastboot mode.
If it doesn't work, check the drivers. Remember that you need to install the drivers once for every mode (in Windows). fastboot? drivers. MTP? drivers. ADB? drivers. ADB in custom recovery? drivers. Download mode? drivers. OMAPFlash? drivers again. And different modes have different drivers too.
Hello guys,
I am new here and thats my first post, please tell me when I do something wrong. But I think this is the best forum to ask :
I had a well-functioning HTC One X. But at once it doesn´t start and stuck in the HTC bootlogo. I googled it and after many days I try to unlock the bootloader. The bootloader starts only after many trys and then shows a red field "battery level is too low to flash"(connected to PC). The red led doesn´t lights up. I leave it in the bootloader and after many hours it starts normally (bootloader still locked). I set the phone back to factory settings (not in the bootloader). I used it like every day, but after hours when I switch to the normal menü it was stucked for 5 seconds and then the screen become black and it wont restart. I buy accumulator for the phone and exchange it (I have a little bit "hardware skills"). I connected it with loading cable to the socket (not the PC!). The red LED flashes for a second and then happens nothing. After many trys the bootloader shows up (connected to my PC) and I googled for almost hours to find a solution. "I have to install a custom ROM". I unlocked the bootloader with the programm "One X All-In-One Kit v2.3". I don´t know why but I shut the phone down. I try to start the phone or the bootloader but it doesn´t work. I try it now for weeks but it is dead (but I´m very sure the problem that it doesn´t starts is not due to the unlocked bootloader, because it is the same problem with the "not starting" like the time before I unlocked it). But the strange thing is... and now comes the important part... when I connect the phone with my PC the PC make the "USB connected"-sound and says that there is a unrecognized device connected. And when I try to start the bootloader the PC makes the "USB disconnected"-sound and a second later the "device-driver software not installed"-sound (I hope you know what I mean) and when I keep trying to start the bootloader it happens again and again the same. I tried almost everything, I use a loading.bat file but it can´t detect the phone (you know "unrecognized device"). Is it the accumulator ? Is the hardware dead ? Or what is the problem ?
I hope you understand this text (I´m sixteen and from germany). If you don´t please ask me every question you have. I really hope you can help me with my really long-term problem.
Thanks for every question, reply, solution or improvement proposal for me
XilentMe
So, what i have deduced is that
1. You are stuck on fastboot with low battery.
2. Your PC does not recognize your device.
For this purpose, first download and install the htc usb drivers. These should work: http://forum.xda-developers.com/showthread.php?t=2211791
Then visit this thread: http://forum.xda-developers.com/showthread.php?t=1658084
follow the instructions, once your phone is charged enough, unlock the bootloader, flash a custom recovery, boot into recovery and let it charge for a while, then flash a new rom.
Dont forget to press the Thanks button if i helped
Okay thanks for your proposal, but the problem is now that I can´t boot into bootloader, the phone does nothing. No reaction, no charging LED, no normal boot, no bootloader...absolutely nothing. Only when I connect the HTC to the PC the PC make the "USB-device connected" sound, as if you connect a USB-stick to your PC, but nothing else happens.
Any ideas or similar problems ?
XilentMe
So try to charge via pc. Leave for some time connected to pc and try to power up.
Hey,
I tried it, but it didn´t work. Nothing happens, only the "plug off-sound" when I want to start the bootloader via volume down+power button, while it is connected to the PC. I have no idea what to do.
XilentMe
So i was using my phone and decided to restart it after updating my adaway files but my phone never turned back on. The two press the power button screens did not show up either. I tried to uses the MSMdownload tool since i thought my phone was somehow bricked but that didnt work either, it just kept restarting the download process after everything was completed. my computer makes a sound when its connected and it connects correctly as a quallcomm 9008 device but even after all this nothing is working. has anyone experienced something like this or does anyone have any advice?
did you try to long press both power button and vol up ...you should feel a vibration...
maybe it's not turned of maybe it's error causing the screen to be off... also is there any heat?
Which method of the unbrick tool did you use? First or second? If the first, then maybe you should give the second also a try.
Sent from my ONEPLUS A3003 using Tapatalk
I've tried everything and I used th me second method yet nothing happened. I can see my phone get recognized by the computer and get listed on the MSN device list yet nothing happens after it finishes the process. After the green line shows up telling me that it's completed everything the process restarts writhing a few minutes unless I unplug it. No vibration no nothing the phone just died on me after I restarted it .
Try doing MSM on a different PC with all drivers installed , hope it helps
Try to repeat flashing again, there is no other way. Use method 2only. Extract tool again and try flash.
When I was used Xperia Z1, I bricked my phone with a soft brick. So I installed driver in my PC and flash Kernel though FASTBOOT(ADB) either it's not show Device in my PC (I show just "Unknown Device").
After that my phone can connect to my PC again (Now It shown C9303 or something that meant it know it's a phone).
So I can flash by Flashtools again. Soft brick is not scary as Hard brick, you'll find some way to bring it back easily.
Hope this help!
PS. Bricked Phone is WEAK in Battery, always connect it with charger.
Hello,
I've got a water damaged OP3 (it was in a pool for about 1min). Now after a few days having it in a pot of rice and cleaning the logic board with 100% isopropanol it finally woke up when pressing power button.
My problem now: It just shows up with a Linux Logo (a small Tux in the middle of the screen) and then turns off after 3 seconds. If I connect it with a charger, the screen persists for the moment.
When pressing + holding volume up button, windows recognizes it as "unknown usb device" and screen stays black.
I only need to access the flash to rescue some of my recent (of course not backed up) data.
What do you suggest? Could I try the unbrick the phone or do these symptons point to a irreversible hardware damage?
Is there a way to read the flash without flashing (or with flashing a minimum set of) stock image?
best regards and thanks in advance!
Contact a software technician
juuz said:
hello,
i've got a water damaged op3 (it was in a pool for about 1min). Now after a few days having it in a pot of rice and cleaning the logic board with 100% isopropanol it finally woke up when pressing power button.
My problem now: It just shows up with a linux logo (a small tux in the middle of the screen) and then turns off after 3 seconds. If i connect it with a charger, the screen persists for the moment.
When pressing + holding volume up button, windows recognizes it as "unknown usb device" and screen stays black.
I only need to access the flash to rescue some of my recent (of course not backed up) data.
What do you suggest? Could i try the unbrick the phone or do these symptons point to a irreversible hardware damage?
Is there a way to read the flash without flashing (or with flashing a minimum set of) stock image?
Best regards and thanks in advance!
Click to expand...
Click to collapse
you better avoid doing experiments on op3. Symptoms you have mentioned in your thread, tells that your has been flashed (don't have usb drivers,no os,no firmware). I have faced same problem with my letv le 1s. It is a software problem. Your phone is totally empty. So do contact with any software technician, he uses sp flash tool to wake up the device. Download sp flash tool and follow procedure. If sp flash tool is detecting your device then it means your device hardware is fine.
juuz said:
Hello,
I've got a water damaged OP3 (it was in a pool for about 1min). Now after a few days having it in a pot of rice and cleaning the logic board with 100% isopropanol it finally woke up when pressing power button.
My problem now: It just shows up with a Linux Logo (a small Tux in the middle of the screen) and then turns off after 3 seconds. If I connect it with a charger, the screen persists for the moment.
When pressing + holding volume up button, windows recognizes it as "unknown usb device" and screen stays black.
I only need to access the flash to rescue some of my recent (of course not backed up) data.
What do you suggest? Could I try the unbrick the phone or do these symptons point to a irreversible hardware damage?
Is there a way to read the flash without flashing (or with flashing a minimum set of) stock image?
best regards and thanks in advance!
Click to expand...
Click to collapse
Have you installed the necessary drivers in Windows for the phone to show up as Qualcom HS-USB..........Loader9008? Otherwise your phone will not be recognised when you do volume press for 10 seconds and connect. Even if it is recognised in this "service" mode, you may be able to unbrick/restore your phone but in the process, the entire phone would be wiped clean. (I know since I have done it).
tnsmani said:
Have you installed the necessary drivers in Windows for the phone to show up as Qualcom HS-USB..........Loader9008? Otherwise your phone will not be recognised when you do volume press for 10 seconds and connect. Even if it is recognised in this "service" mode, you may be able to unbrick/restore your phone but in the process, the entire phone would be wiped clean. (I know since I have done it).
Click to expand...
Click to collapse
I've tried to get the phone into EDL Mode (Qualcomm chip), but had no success, phone vibrates and windows recognizes an "unknown usb device" (pressed Volume Up and connected to USB, phone was definitely turned off). But I am not able to get the device recognized as "QHSUSB_BULK" which - afaik - is the prerequisite to install the Qualcomm USB Driver und go on with the unbrick procedure..
I hope anyone got some idea how to get the phone back to life..
juuz said:
I've tried to get the phone into EDL Mode (Qualcomm chip), but had no success, phone vibrates and windows recognizes an "unknown usb device" (pressed Volume Up and connected to USB, phone was definitely turned off). But I am not able to get the device recognized as "QHSUSB_BULK" which - afaik - is the prerequisite to install the Qualcomm USB Driver und go on with the unbrick procedure..
I hope anyone got some idea how to get the phone back to life..
Click to expand...
Click to collapse
Your understanding of the unbrick steps is not correct. Initially the phone will not show up at all or may show up as unknown or something else. It is only when you install the EDL mode drivers and then hold the power button down for 40 seconds and the hold down the volume up button for 10 seconds and connect to PC, will it show up in the EDL mode. Ofcourse you will have to disable the driver signature verification before installing the drivers.
Read the Unbrick Guide again and install the drivers before trying to connect.
tnsmani said:
Your understanding of the unbrick steps is not correct. Initially the phone will not show up at all or may show up as unknown or something else. It is only when you install the EDL mode drivers and then hold the power button down for 40 seconds and the hold down the volume up button for 10 seconds and connect to PC, will it show up in the EDL mode. Ofcourse you will have to disable the driver signature verification before installing the drivers.
Read the Unbrick Guide again and install the drivers before trying to connect.
Click to expand...
Click to collapse
Thanks so far, but being a software developer myself I am not a totally beginner. I followed the guide, also read it twice etc.. Also tried another USB cable including the original Oneplus cable.
When plugging it in while pressing Volume Up my Linux laptop reports this:
Code:
[40474.458362] usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
[40475.426231] usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
[40475.426354] usb usb3-port2: attempt power cycle
[40476.710061] usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
[40477.677934] usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
[40477.678051] usb usb3-port2: unable to enumerate USB device
On my windows machine the device manager reports "Windows has stopped the device because it has reported problems. (Code 43)".
Any suggestions? It seems that the device has lost all firmware etc. and there is no EDL left on the device.
EDIT:
With holding Vol(-) and Power I could get rid of the Tux Penguin and enter fastboot and recovery of the phone.. NAND seems to be okay, can decrypt my internal storage.. The USB port doesn't work in recovery (same error like I had with the EDL mode, unknown device)..
I hope I can now charge the battery a bit and recovery my data...
Thanks so far guys..
juuz said:
Thanks so far, but being a software developer myself I am not a totally beginner. I followed the guide, also read it twice etc.. Also tried another USB cable including the original Oneplus cable.
When plugging it in while pressing Volume Up my Linux laptop reports this:
Code:
[40474.458362] usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
[40475.426231] usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
[40475.426354] usb usb3-port2: attempt power cycle
[40476.710061] usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
[40477.677934] usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
[40477.678051] usb usb3-port2: unable to enumerate USB device
On my windows machine the device manager reports "Windows has stopped the device because it has reported problems. (Code 43)".
Any suggestions? It seems that the device has lost all firmware etc. and there is no EDL left on the device.
EDIT:
With holding Vol(-) and Power I could get rid of the Tux Penguin and enter fastboot and recovery of the phone.. NAND seems to be okay, can decrypt my internal storage.. The USB port doesn't work in recovery (same error like I had with the EDL mode, unknown device)..
I hope I can now charge the battery a bit and recovery my data...
Thanks so far guys..
Click to expand...
Click to collapse
Sorry if I had sounded condescending, but I had no way of knowing your level of expertise.
Best of luck for restoring your phone or for saving the data.
tnsmani said:
Sorry if I had sounded condescending, but I had no way of knowing your level of expertise.
Best of luck for restoring your phone or for saving the data.
Click to expand...
Click to collapse
No need to worry.. Of course, you couldn't know and there are a lot of people asking dump questions..
My phone is back a life, I guess the data transfer via USB is not working anymore, charging works although I needed to take my Oneplus One's battery (identical connector, just need to take care of the pin layout [+/-]) because my OP3 battery is pretty low and I don't know if I can reactivate it.. It has about 3,4V at the moment and charges very slow..
Finally, if anyone else faces this issue and can't boot his phone:
Try different button combinations and keep holding the buttons several seconds/minutes..