Related
So after what seemed to be the art of bricking my Incredible over the weekend (dead, black screen), I think we have found a fix for it.
This is what we did to bring the phone back to life:
** Please note: Make SURE you have the correct drivers installed. I used the modified Android ones.
1.) Download the Android SDK, and then fire up a command shell in the Tools directory
2.) Boot the Incredible into Recovery:
* Pull battery, then put back in
* Hold Power and Vol Down for 5 seconds
* Wait 20 seconds
* Hit Vol Down once
* Hit Power
* Wait 20 seconds
3.) Check to make sure that ADB can see it by typing adb devices into the command shell you opened earlier
4.) Type adb reboot oem-78 into the command shell. I let the phone sit for a few minutes.
5.) Run the RUU from Shipped-Roms, located here: shipped-roms.com/download.php?category=android&model=Incredible&file=RUU_Incredible_C_Froyo_VERIZON_WWE_3.21.605.1_Radio_2.15.00.07.28_2k4k_NV_1.50_PRL58006_release_143351_signed.exe
Once the RUU finished running, my phone rebooted and my screen is alive!
Downloadding now I hope this works. I already called verizon and the replacement Phone should be here Wed.
let me know if this works for you, i worked with aracheon all last night and then was able to finally break it down and get it working this afternoon, if you need help let me know
Credit to be given where credit is due - I wouldn't have figured this out without Jobehonda's help.
I would not say "bricked" inc, just screen was dead because there were no drivers installed for SLCD. My phone was "OK", when i called my own number, it rings, vibrates etc, just i was not able to see anything.
What i did was just got the stock 2.2 PB31IMG.zip from somewhere around here, and using "timing" in my mind, i just repeated flashing process as usually. The only difference was that i did not see what i was doing. For the first time it failed, but i got lucky after second time, and my phone (scree that is) is back to life.
Now, i just have to root it again using caution this time....
Windows XP doesn't like RUU_Incredible_C_Froyo_VERIZON_WWE_3.21.605.1_Radio_2.15.00.07.28_2k4k_NV_1.50_PRL58006_release_143351_signed.exe file name must rename to anything(.exe) shorter I used RUU.exe
fuzio1963 said:
I would not say "bricked" inc, just screen was dead because there were no drivers installed for SLCD. My phone was "OK", when i called my own number, it rings, vibrates etc, just i was not able to see anything.
What i did was just got the stock 2.2 PB31IMG.zip from somewhere around here, and using "timing" in my mind, i just repeated flashing process as usually. The only difference was that i did not see what i was doing. For the first time it failed, but i got lucky after second time, and my phone (scree that is) is back to life.
Now, i just have to root it again using caution this time....
Click to expand...
Click to collapse
Well, right. But the phone is effectively useless with the screen problem. The big guns are calling it an "SLCD Brick," sooo...
tjamscad said:
Windows XP doesn't like RUU_Incredible_C_Froyo_VERIZON_WWE_3.21.605.1_Radio_2.15.00.07.28_2k4k_NV_1.50_PRL58006_release_143351_signed.exe file name must rename to anything(.exe) shorter I used RUU.exe
Click to expand...
Click to collapse
Depends on where you put it. You should be able to get away with dropping that on the root of your C drive and still keep the long filename.
Fixed It works it really works, Thank you Jobehonda and arache0n
tjamscad said:
Fixed It works it really works, Thank you Jobehonda and arache0n
Click to expand...
Click to collapse
Glad to hear it.
Awesome! Glad it worked for more than just one person!
arache0n said:
Well, right. But the phone is effectively useless with the screen problem. The big guns are calling it an "SLCD Brick," sooo...
QUOTE]
What's your point here?? You said "bricking my Incredible ", soooo......?
FYI, i just rooted my Dinc with unrev....3, got black screen with two white lines, (again). Flashed recovery fix, and all is goooood, this time.
G-night all.
Click to expand...
Click to collapse
the problem aracheon had is we accidently flashed the wrong image file to upgrade back to stock recovery when trying to load the correct flash file it was not working...not sure why. Either way, both seem to fix the problem.
Jobehonda,
I'm stuck with my Black screen SLCD Dinc as well, doing the same mentioned above, and when I tried following your instructions it hasn't worked out for me so far. I can't get past the "adb devices" thing. It tells me "devices not attached" or someting to that effect after running the command. I may be doing something incorrectly... Could you be of assistance? I also posted a comment to your "Droid Incredible is a Pile" post on your site. Looking forward to you helping me bring my Droid back to life...
Thanks!
Nevermind... I fixed my "SLCD Brick"!! I will post details later of how I did it...
tjamscad said:
Downloadding now I hope this works. I already called verizon and the replacement Phone should be here Wed.
Click to expand...
Click to collapse
Well, for what it's worth your replacement phone might be an AMOLED.
A week or two ago I got a replacement for the 3G issue and recieved another AMOLED.
OK, this is, what fixed mine:
-pull battery, then put back in
-hold power + vol down for 5 seconds, nothing happened...
-then hold power down for 5 seconds, got 1 vibration...
-then hold vol up + power for 5 seconds, and to my surprise, screen turned on and only had 1 option: Hboot
-then left the screen up and took my SDcard out (the battery cover was off already) and I went to the following thread (how-to-update-your-droid-incredible-to-leaked-android-2-2); and downloaded the "PB31IMG.zip" file from step 1 and copied it over to my SDcard. Please "google" the thread title above... I'm not allowed to post full links because I'm a new user.
-then I put the SDcard back in, pull the battery, then put back in
-hold power + vol down for 5 seconds
-Boots into hboot and select Bootloader
-PB31IMG.zip will start to install.
**Note** Your phone might reboot to either hboot or recovery after trying to install PB31IMG.ZIP, just get back to hboot and install again, when you get back to hboot you should notice its version .92 and S-OFF is still on, just install PB31IMG.ZIP again and all should be good. I believe at one point after it updates hboot it has to reboot to finish the install, so this might be what you are seeing.
-Finally it will reboot and you should see HTC Screen, Droid voice/Red eye will load, and you will have a fresh new 2.2 Dinc un-rooted. You then can try re-rooting at your own risk!!
I basically used part of jobehonda's instructions, and part of the thread's instructions, combined with my own messing around with my phone to fix my "bricked SLCD" Dinc... I hope this can help others as well as it helped me! ; )
Just one more option to try... What the heck, your droid is already screwed, it can't get worse. Just try this!
BTW, a buddy of mine with a rooted Droid X, also helped me with getting this far for the last 3 days!! He helped me with searching all the droid forums out there and random sites to get answers... Thanks CLIFF!
<---- Jackass
edit
fixed.
I am glad you figured it out, basically for the device to be recognized in adb you need to make sure your definately in recovery, if you follow the steps and count, one one thousand, two one thousand, etc etc you should be able to get it into recovery and recognized by adb.
the other thing is you need to make sure you have the HTC drivers installed prior, otherwise it wont recognize.
Then I shall edit it.
Hi guys, need very quick help from you, as I think I have bricked the phone which suppose to be a Christmas gift for may son. I was trying to revert phone from root and custom rom to stock. I've downloaded older OTA update (one of very first ones with android 2.2) an installed it in bootloader. Phone booted fine, and I went for official update. It showed to me there is update available to android 2.3. I have downloaded it and phone rebooted in to update mode. After progress bar gone to the end it disappeared and phone stayed in that update mode (logo with phone and green arrows shaped it to circle) for nearly half an hour. I though, some thing had to vent wrong so I decided to turn off phone, but power button gave no effect, so I pulled battery out for few seconds. After I have putted it back phone never turned on again. I mean is completely not responding. Pressing power button for even minute doesn't wake it up, it is not possible to go to the bootloader. There is no characteristic vibration when it turns on. Basically it behaves like there is no battery in socket but there is, and it is fully loaded as I charged it before updating. When phone plugged to AC or computer LED is not lighting as well whatsoever.
Please, can any one help with this one? I in rush as phone is a Christmas present for my son who lives in Italy and I supposed to ship this today to make it arrive b4 Christmas. This is why I can not spend to much time on searching forums.
Thank you
Check battery pins
hedeon said:
Hi guys, need very quick help from you, as I think I have bricked the phone which suppose to be a Christmas gift for may son. I was trying to revert phone from root and custom rom to stock. I've downloaded older OTA update (one of very first ones with android 2.2) an installed it in bootloader. Phone booted fine, and I went for official update. It showed to me there is update available to android 2.3. I have downloaded it and phone rebooted in to update mode. After progress bar gone to the end it disappeared and phone stayed in that update mode (logo with phone and green arrows shaped it to circle) for nearly half an hour. I though, some thing had to vent wrong so I decided to turn off phone, but power button gave no effect, so I pulled battery out for few seconds. After I have putted it back phone never turned on again. I mean is completely not responding. Pressing power button for even minute doesn't wake it up, it is not possible to go to the bootloader. There is no characteristic vibration when it turns on. Basically it behaves like there is no battery in socket but there is, and it is fully loaded as I charged it before updating. When phone plugged to AC or computer LED is not lighting as well whatsoever.
Please, can any one help with this one? I in rush as phone is a Christmas present for my son who lives in Italy and I supposed to ship this today to make it arrive b4 Christmas. This is why I can not spend to much time on searching forums.
Thank you
Click to expand...
Click to collapse
After reading what you said i think that you placed battery wrong. Check the pins inside the phone with battery pins.
whiperhack said:
After reading what you said i think that you placed battery wrong. Check the pins inside the phone with battery pins.
Click to expand...
Click to collapse
That was my first idea too but, no m8, battery is placed ok....
Try pressing volume down+power button for a while then leave the power button while still pressing the voulme key. You should boot into the bootloader.
if4ct0r said:
Try pressing volume down+power button for a while then leave the power button while still pressing the voulme key. You should boot into the bootloader.
Click to expand...
Click to collapse
Tried that too, still dead
Try connecting you DHD to the PC.
Download one of these Stock RUU's : http://shipped-roms.com/index.php?category=android&model=Ace
Run the installer from PC. See if it detects the device.
if4ct0r said:
Try connecting you DHD to the PC.
Download one of these Stock RUU's : http://shipped-roms.com/index.php?category=android&model=Ace
Run the installer from PC. See if it detects the device.
Click to expand...
Click to collapse
I understand I should not be worried that all of these RUU's are listed as for model: ACE?
Not at all. 'Ace' is the codename HTC gave to Desire HD/Inspire. Just choose the RUU that fits your location(i.e. WWE stands for WorldWide Edition).
if4ct0r said:
Not at all. 'Ace' is the codename HTC gave to Desire HD/Inspire. Just choose the RUU that fits your location(i.e. WWE stands for WorldWide Edition).
Click to expand...
Click to collapse
OMG! I was previously looking for stock roms and everytime I ended up on that site from your link I was annoyed that someone is giving a wrong link to roms for wrong phone. Silly me!
I am downloading right now.
if4ct0r said:
Try connecting you DHD to the PC.
Download one of these Stock RUU's : http://shipped-roms.com/index.php?category=android&model=Ace
Run the installer from PC. See if it detects the device.
Click to expand...
Click to collapse
No it says phone not connected (error[170])
hedeon said:
No it says phone not connected (error[170])
Click to expand...
Click to collapse
My idea is to double check again the battery position in the socket and if it is ok try to leave it 5 minutes alone on the AC adapter. If this will not give good results, go to the appropriate HTC representative.
when you connected it to your computer... did it ask you to install qload drivers?
if not, go into device manager on your computer, then plug in your phone. If you see an unknown device that shows as qload something or other, then sorry to say, its bricked.
The only way to recover it now is via jtagging or replacing the mainboard (which generally is what they do when you send it in for warranty repair)
whiperhack said:
My idea is to double check again the battery position in the socket and if it is ok try to leave it 5 minutes alone on the AC adapter. If this will not give good results, go to the appropriate HTC representative.
Click to expand...
Click to collapse
Yes, I thought about it as phone behave like it has no power at all. But this is not the case, as I have been flipping that and another battery in every possible position. And I know which one is correct as I can see where pins are in battery pocket. I left it alone under charging and other time with no battery at all hoping that will hard reset phone. No effect at all .
JSLEnterprises said:
when connected to your computer... did it ask you to install qload drivers?
if not, go into device manager on your computer, then plug in your phone. If you see an unknown device that shows as qload something or other, then its bricked, sorry to say
Click to expand...
Click to collapse
I had drivers previously installed. But I am not entirely sure are we talking about same thing as I don't know what QLOAD is. Anyway comp doesn't see any recognised or unrecognised device that could be my phone...
I am not worrying about damn phone as if it is hard bricked tech guys in service will not probably spot that it was rooted. So they will replace, or if not I will go to insurance company. Problem is it takes to much time, I wont make it b4 Christmas.
Thank you guys,
anyone has some other ideas? Please...
desperation bump
Sorry.. It really seems to be beyond software-repair, If it cannot boot in the bootloader or be recognized by PC there's really not much we can do. We need the device to start in some way.
Although one last thing that we haven't tried and can try is to see if it can be accessed via adb or fastboot. (Although I highly doubt it since the RUU also wasn't working).
I've attached the adb and fastboot files required to test that. Extract it, double-click on StartHere.bat and type "fastboot reboot" or "adb reboot". If it returns an error citing device not found then this too has failed.
(This probably wont work.. desperate action)
Another silly thing that might be tried is to try to put your phone on charging via a charger(not USB via PC) and then try to switch it on. Try normal switching, switching on to bootloader(volume down press)...
If these don't work then you really should give it to the repair center.. you're right that they wont probably realise that it was rooted and would probably change the main board.
if4ct0r said:
Sorry.. It really seems to be beyond software-repair, If it cannot boot in the bootloader or be recognized by PC there's really not much we can do. We need the device to start in some way.
Although one last thing that we haven't tried and can try is to see if it can be accessed via adb or fastboot. (Although I highly doubt it since the RUU also wasn't working).
I've attached the adb and fastboot files required to test that. Extract it, double-click on StartHere.bat and type "fastboot reboot" or "adb reboot". If it returns an error citing device not found then this too has failed.
(This probably wont work.. desperate action)
Another silly thing that might be tried is to try to put your phone on charging via a charger(not USB via PC) and then try to switch it on. Try normal switching, switching on to bootloader(volume down press)...
If these don't work then you really should give it to the repair center.. you're right that they wont probably realise that it was rooted and would probably change the main board.
Click to expand...
Click to collapse
Sigh... I got "waiting for device" forever in CMD... As you said, it's dead. Gonna send it to HTC in Monday...
Thank you all, appreciate your time
Hello hedeon,
I have the same experience today, as you state in the first post in this thread.
Did you, and how solve the problem?
Is there people with the same problem? This morning I receive notification about system update for my HTC Desire HD. The rest is exactly same problem from the top of this story = death + death + death.....
The problem is that you PULLED THE BATTERY WHILE UPDATING! Have some paitience. I switched on my DHD after 3 months and it needed updating. Takes around 20 mins to complete update
Sent from my HTC Desire HD A9191 using xda premium
GuyInTheCorner said:
The problem is that you PULLED THE BATTERY WHILE UPDATING! Have some paitience. I switched on my DHD after 3 months and it needed updating. Takes around 20 mins to complete update
Sent from my HTC Desire HD A9191 using xda premium
Click to expand...
Click to collapse
May be, but updating started with downloading, then resetting, and then green line was growing up to 1/3 of total size, and at that size stay more then 20 min. Then I try to to push every button, and every combination of buttons, and after 10 minutes more I had pull battery out.
Was it too impatient ?
What was the Android version before you rooted if you can remember and which tool did you use to root?
From what you wrote earlier, it asked you for a 2.3 update which means you probably flashed a Froyo RUU as stock, to bring the phone back to stock ofc.
However, if your DHD came with stock Gingerbread, flashing a Froyo RUU will most definitely screw the phone. I'm not sure if it's beyond repair atm or not, but if that was the case, even if you didn't mess with the battery, chances are the phone would never boot anyway.
Look into AAHK thread, I think there is a good how to there.
I just wanted to try the latest CM9 after locking bootloader for a return. It unlocked, flashed fine, rebooted a few times. I was going to relock it so I used "reboot to bootloader". It was charging, it shut down and never turned back on. Removing the battery didn't help either. When I connect it to the PC, it recognizes OMAP4400 but doesn't install any drivers. I don't see how it can be bricked as I just rebooted to bootloader. It's been charging for a few hours and I haven't touched it since. I'm going to try the USB Jig soon, any additional help would be greatly appreciated..
If you're unlucky, you've hard-bricked it, somehow...
Try pressing (Just) Volume down + power...
That also gets you into Oding mode...
If that don't work, then sorry... I wouldn't know any other solution. Try the jig, if you want, but it's not put, that it'll work.
Well, best of uck!!
Hope you fix it!
LG familyguy59
Jig doesn't work, volume down+power doesn't, fastboot doesn't. Anything I do to it, it still shows as OMAP4440 in device manager. Even without the battery in. It must be in some kind of special recovery mode, but how the hell does it work with no battery. I'll leave it without battery over night, it's charged for sure so that can't be the problem.
The phone will work plugged in without the battery in under normal conditions, and that it's showing up at all is a good sign.
Have you used fastboot before successfully? You may need to load drivers manually. This thread links a few different options you can try:
http://rootzwiki.com/topic/12013-welcome-to-rootzwiki-editionstep-by-step-oem-unlock-and-root/
freemini said:
Jig doesn't work, volume down+power doesn't, fastboot doesn't. Anything I do to it, it still shows as OMAP4440 in device manager. Even without the battery in. It must be in some kind of special recovery mode, but how the hell does it work with no battery. I'll leave it without battery over night, it's charged for sure so that can't be the problem.
Click to expand...
Click to collapse
My guess is that if it is showing as OMAP, it is a sign that bootloader is not working at all, I've seen some topics of panda boards (that use the same processor) with the same symptons when bootloader was lost...
Yes I did use fast boot successfully before. I just don't see how it could corrupt the bootloader by simply restarting in it.. It doesn't make sense to me at all.
freemini said:
Yes I did use fast boot successfully before. I just don't see how it could corrupt the bootloader by simply restarting in it.. It doesn't make sense to me at all.
Click to expand...
Click to collapse
Well, I have this thought: You last used fastboot (With success), you maybe flashed a ROM, opr something.
You then restartet the phone, whilst it was still updating some internal files.
Maybe, if you did do that (willingly or not), you buggered the bootloader, like that...
familyguy59 said:
Well, I have this thought: You last used fastboot (With success), you maybe flashed a ROM, opr something.
You then restartet the phone, whilst it was still updating some internal files.
Maybe, if you did do that (willingly or not), you buggered the bootloader, like that...
Click to expand...
Click to collapse
It was not syncing or downloading anything, I've been using CM9 for about an hour before choosing reboot to bootloader. The only thing the phone was doing was charging.. I just don't understand how a simple command to reboot in bootloader can screw it up, it just doesn't make sense to me. It seems it's in a loop, Device Manager shows OMAP4440 refreshing about every second. It eventually disappears but if I plug it back in it does it again. I'm guessing the bootloader is gone
freemini said:
It was not syncing or downloading anything, I've been using CM9 for about an hour before choosing reboot to bootloader. The only thing the phone was doing was charging.. I just don't understand how a simple command to reboot in bootloader can screw it up, it just doesn't make sense to me. It seems it's in a loop, Device Manager shows OMAP4440 refreshing about every second. It eventually disappears but if I plug it back in it does it again. I'm guessing the bootloader is gone
Click to expand...
Click to collapse
Well, it may be gone, but OMAP normally means, that there is no firmware present...
This happened to me, whilst flashing a new firmware, onto the Wave, of my Dad...
I'll have a look, inside my Devman, and see, what I can find ^^
familyguy59 said:
Well, it may be gone, but OMAP normally means, that there is no firmware present...
This happened to me, whilst flashing a new firmware, onto the Wave, of my Dad...
I'll have a look, inside my Devman, and see, what I can find ^^
Click to expand...
Click to collapse
Thanks but I sent it back now. I hope they take it, there's a chance they won't obviously.. Let me know if you find anything, but it seemed hopeless to me.
freemini said:
Thanks but I sent it back now. I hope they take it, there's a chance they won't obviously.. Let me know if you find anything, but it seemed hopeless to me.
Click to expand...
Click to collapse
Well, I wish best of luck, in that matter!
I still think, it's an unwanted brick, though...
I've looked, but can't find anything, whilst the phone is booted in Android, so, I'll restart it in a minute, and then have a look ^^
Okay, first of all, I would like to mention that I'm new at all of this.
I brought this phone 2 years ago and 2 months ago I decided I was going to root it. So I switched to CyanogenMod 11 M4 and did everything that was required i.e., unlocking bootloader and flashing a recovery and all that.
Just 2 days ago my phone showed an update available to CyanogenMod 11 M5. So I downloaded it and then the phone took me to my recovery. There I made a backup and flashed the M5.zip file that was downloaded. But when I rebooted my system a popup came saying com.process.phone has stopped unexpectedly. I pressed OK but it was persistent. I had no idea what to do so I booted into recovery and wiped data and then performed a restore of my previous backup that I had taken. Half-way through the backup the phone just switched off and then restarted with the traditional HTC logo and then it switched off again and restarted again and this process kept looping.
I loaded my bootloader and connected the phone via fastboot to my computer and erased the cache and flashed the recovery again. Then wehn I restored it started working normally as it did before.
But the battery was around 20% at that time so I left it to charge overnight. When I woke up the next day it was insanely hot and the LED was constantly red but it wouldnt wake up. So I loaded into recovery to restore it again but it kept on saying "Error mounting /system!"
And then after a few tries it switched off. Now it won't wake up again. Even the LED seems dead.
Has anyone of you ever encountered a similar issue? Any help would be appreciated. I've tried all the button combinations that are recognized by the device but nothing seems to work.
dead battery
i guess its because of corrupt or dead battery
try giving external power or replace battery and try
further you could even try other options like booting cwm
flashing last kernel image found
jhakjhuk1853 said:
i guess its because of corrupt or dead battery
try giving external power or replace battery and try
further you could even try other options like booting cwm
flashing last kernel image found
Click to expand...
Click to collapse
Booting CWM or flashing the last kernel image aren't an option because the device doesn't switch on at all. I cannot access the bootloader.
try changing battery
try changing battery by buying new battery and connecting
or remove battery and charge it with external source i guess u must have heard of jump starting battery
kartikeym309 said:
Booting CWM or flashing the last kernel image aren't an option because the device doesn't switch on at all. I cannot access the bootloader.
Click to expand...
Click to collapse
kartikeym309 said:
Okay, first of all, I would like to mention that I'm new at all of this.
I brought this phone 2 years ago and 2 months ago I decided I was going to root it. So I switched to CyanogenMod 11 M4 and did everything that was required i.e., unlocking bootloader and flashing a recovery and all that.
Just 2 days ago my phone showed an update available to CyanogenMod 11 M5. So I downloaded it and then the phone took me to my recovery. There I made a backup and flashed the M5.zip file that was downloaded. But when I rebooted my system a popup came saying com.process.phone has stopped unexpectedly. I pressed OK but it was persistent. I had no idea what to do so I booted into recovery and wiped data and then performed a restore of my previous backup that I had taken. Half-way through the backup the phone just switched off and then restarted with the traditional HTC logo and then it switched off again and restarted again and this process kept looping.
I loaded my bootloader and connected the phone via fastboot to my computer and erased the cache and flashed the recovery again. Then wehn I restored it started working normally as it did before.
But the battery was around 20% at that time so I left it to charge overnight. When I woke up the next day it was insanely hot and the LED was constantly red but it wouldnt wake up. So I loaded into recovery to restore it again but it kept on saying "Error mounting /system!"
And then after a few tries it switched off. Now it won't wake up again. Even the LED seems dead.
Has anyone of you ever encountered a similar issue? Any help would be appreciated. I've tried all the button combinations that are recognized by the device but nothing seems to work.
Click to expand...
Click to collapse
After the phone updated did u extract and flash boot.img from M5.zip?
convict_moody said:
After the phone updated did u extract and flash boot.img from M5.zip?
Click to expand...
Click to collapse
No, I didn't do that because when I switched over from a CM11 Nightly to CM11 Snapshot M4 I didn't extract and flash the boot image even then and everything was working perfectly. So, I didn't think I would need to.
kartikeym309 said:
No, I didn't do that because when I switched over from a CM11 Nightly to CM11 Snapshot M4 I didn't extract and flash the boot image even then and everything was working perfectly. So, I didn't think I would need to.
Click to expand...
Click to collapse
U should give it a try, since some CM updates triggers the kernel itself so boot.img should be flashed again.
convict_moody said:
U should give it a try, since some CM updates triggers the kernel itself so boot.img should be flashed again.
Click to expand...
Click to collapse
That is the problem. I can't. When I connect it to the PC it just never shoes up and I have no luck getting into the bootloader. Do you know of any reliable unbricking guides? I'm guessing my phone is possibly bricked.
kartikeym309 said:
That is the problem. I can't. When I connect it to the PC it just never shoes up and I have no luck getting into the bootloader. Do you know of any reliable unbricking guides? I'm guessing my phone is possibly bricked.
Click to expand...
Click to collapse
Check the guides in here:
HTC One X Reference
convict_moody said:
Check the guides in here:
HTC One X Reference
Click to expand...
Click to collapse
Nah, nothing is suitable. There are guides on how not to brick your device but nothing to unbrick it. :|
Thanks anyways. It's appreciated.
Another bricked HOX apparently. There seem to be loads of these on the internet. In my case, it can't have to do with custom roms or rooting since I never messed around with stuff like that. I even opened the HOX and checked all cables etc. There is no part that looks damaged or otherwise suspicious.
What can we do? How can we at least get access to the data in the internal memory?
Don't know if this will help, but it might be that it hasn't actually charged properly over night and has drained itself to death.
Try plugging into PC and get to fast boot.
Fastboot = Volume Down + Power Button
Then make a batch file out of this:
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
Click to expand...
Click to collapse
Then run the Batch File
Credit to Floepie for writing the .bat
Wilks3y said:
Don't know if this will help, but it might be that it hasn't actually charged properly over night and has drained itself to death.
Try plugging into PC and get to fast boot.
Fastboot = Volume Down + Power Button
Then make a batch file out of this:
Then run the Batch File
Credit to Floepie for writing the .bat
Click to expand...
Click to collapse
Unfortunately, there's no way this could help. because the HOX is literally dead. There is not even a charging indication when plugged into a PC or the wall charger. And thus it's not recognised by the PC and fastboot won't find it.
Hello. I am having some issues with Nexus 5X and was hoping someone could help possibly fix it, if it's even fixable.
I bought the phone from a used store for pretty cheap On march 5th this year.
Tuesday night i was surfing on google chrome app and all of a sudden the entire thing froze up on screen couldn't get it to do anything what so ever so i tried powering it down and rebooting it. Well i got it to power down but then it went into a constant boot loop where it just kept rebooting to the "Google" screen and then it wouldnt get any further. Eventually it ceased doing that after about 5-10 minutes and then i was unable to get the device to do anything, couldn't even get into the bootloader menu. Battery was at 55% when this all started and phone had been working very good prior. Last night i tried to get it to turn on again and this time i noticed a red flashing light on the bottom speaker. I have seen this one before on other nexus devices so i plugged it in and got the charging screen to come up, i let it charge full and then went to try and start it with no luck of getting it to do anything. Today i have managed to get it to simple Boot to the Google screen but it remains their for a few momments then shuts off and does nothing else, sometimes it goes into a constant repeat of that, i hear it's called a boot loop.
I am not sure what the issue is. What i wanna know is if it's an easy fix or not.
Thanks
**Update***
i was able to get it to finally go into to the bootloader screen, but have no clue what to do here, clicking restart just goes back to the same problems.
If you haven't already tried you could try doing a search for Nexus 5x BLOD or Nexus 5x bootloop of death, this may not be the issue but it will give you something to compare the symptoms your device has. There should also be plenty of info on any workarounds there are available to try and get your device back up and running.
Hope that helps
Ok will do thank you
Following thread https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
installed 4Coreoreo fix, but am having issues getting to to flash boot
Command window stays stuck on < waiting for device > and the phone is doing nothing, just sitting in the Bootloader menu
says fastboot mode
secure boot enabled
device state locked
am i missing something? Am thinking the bootloader is locked
unable to do an oem unlock because i can't get it to boot into the os.
Yep your bootloader is locked and sounds like USB debugging needs to be enabled also if ADB is not finding your device using commands 'adb devices' or 'fastboot devices'.
Have another look through the BLOD threads as from what I remember you may need to cool the device right down to get it to boot to system fully to be able to enable OEM unlocking and USB debugging.
Keep searching, and good luck
Edit: I see you posted in the 4 core thread and got it to boot temporarily and OEM unlocked, just try again and enable usb debugging and you should be on to a winner.
junglism93 said:
Yep your bootloader is locked and sounds like USB debugging needs to be enabled also if ADB is not finding your device using commands 'adb devices' or 'fastboot devices'.
Have another look through the BLOD threads as from what I remember you may need to cool the device right down to get it to boot to system fully to be able to enable OEM unlocking and USB debugging.
Keep searching, and good luck
Edit: I see you posted in the 4 core thread and got it to boot temporarily and OEM unlocked, just try again and enable usb debugging and you should be on to a winner.
Click to expand...
Click to collapse
Ty for the reply, unfortunately even after enabling everything i still can't get fastboot to do anything but < waiting for device >
I think she done, sadly. My nexus 4 has lasted longer then this one, even that phone has its issues tho, like to randomally reboot itself sometimes, others the screen suddenly won't come on (lots of battery life) and it is hard to reboot but usually does. And it's 6 years old lol
Gibson295 said:
Ty for the reply, unfortunately even after enabling everything i still can't get fastboot to do anything but < waiting for device >
I think she done, sadly. My nexus 4 has lasted longer then this one, even that phone has its issues tho, like to randomally reboot itself sometimes, others the screen suddenly won't come on (lots of battery life) and it is hard to reboot but usually does. And it's 6 years old lol
Click to expand...
Click to collapse
No problem, other than trying a different usb port, cables or updating your ADB and fastboot if you haven't already it sounds like it's the end of the road for your 5x.
Leave it in a cupboard for a few days and give it a go another time, you never know. I've still got my Nexus 4, new battery time for mine but it still runs like a charm lol.