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.
I downloaded Cyanogen Mod through Rom Manager and it restarted my phone but now all it does is bring up the white splash screen for a little while, then restarts into a black screen with white bars. I can get into hboot but none of the commands do anything they just restart to the splash and then back to the black screen.
I have been able to adb into the phone when it is in the black screen and I tried following this tread: http://forum.xda-developers.com/archive/index.php/t-808065.html aka I tried pushing a PB31IMG.zip (from here: http://www.dougpiston.com/files/Recovery/) onto the sdcard, turning it off, taking out the battery and restarting to hboot. But hboot does not find the file, and when I restart it to the black screen the file is gone.
My guess is that when it goes to the black screen it wipes my sdcard, at least I hope it doesn't wipe it sooner because I'm not sure how to work with that. Maybe I am not pushing a good PB31IMG.zip file because I don't really know the difference between them. Maybe I am not renaming it correctly, or my sdcard is not FAT32, because am not actually sure how to check if it is FAT32 but I am assuming it is because that is the standard. I don't really have any other leads, does anyone have any experience with this problem? Is there another way to restore it to factory reset?
Please don't tell me I shouldn't have been doing this because I apparently don't know what I am doing. I am not disputing that, but it is a moot point now. I don't know how people go about learning these things a safer way. Apparently I just suck at it. I am starting to freak out a little because I have been without my phone for a day and half and my husband is a bit pissed because he doesn't want to buy me a new phone and doesn't understand why I would want to hack my phone anyway. I refuse to believe just yet that I have bricked my droid. Please help.
Okay, so, my sdcard wasn't in FAT32 but I fixed that by connecting my sdcard to the computer directly and then put my PB31IMG.zip on while I was there. Now my hboot recognizes that there is a new file and asks me to update and I click yes and then restart and I click yes again.
Unfortunately it still does the same thing, white splash followed by black screen with bars, so I have eliminated one of my possible problems and now either its the wrong PB31IMG.zip file, the file inside is named wrong, or something else that I don't even know about. Does the img file need to be something specific? I do have the android-info.txt file so that isn't the problem. I am running out of ideas...
Have you tried the RUU?
semmes said:
Okay, so, my sdcard wasn't in FAT32 but I fixed that by connecting my sdcard to the computer directly and then put my PB31IMG.zip on while I was there. Now my hboot recognizes that there is a new file and asks me to update and I click yes and then restart and I click yes again.
Unfortunately it still does the same thing, white splash followed by black screen with bars, so I have eliminated one of my possible problems and now either its the wrong PB31IMG.zip file, the file inside is named wrong, or something else that I don't even know about. Does the img file need to be something specific? I do have the android-info.txt file so that isn't the problem. I am running out of ideas...
Click to expand...
Click to collapse
Well... you can get into H-boot so there's still hope...
1) Check to make sure your PB31MG.zip isn't named PB31MG.zip.zip.... but since you said the system finally read it, my guess is that isn't your problem.
2) You said nothing about recovery, can you get into it at all? Well... nevermind... you said everything would just reboot your device.
... When you goto H-boot... can you read off the stats?
More specifically...
S-On or S-off?
Radio number...
H-boot?
I'm not 100% sure, but I'm guessing you WERE already rooted when you attempted to flash a ROM... but attempt a re-root with UnRevoked3... report back?
Thanks so much for replying. I have not had computer access so I am finally able to work on this some more.
I have now been able to get it into the recovery screen from the PB31IMG.zip file. I feel pretty stupid, the reason why it had not worked was that I took the other files off my sdcard when I put the flash PB31IMG.zip file on it. (face-palm) Anyway, now it gives me the option to wipe and factory reset but when I do that and restart I still get the same recovery screen. I tried a couple different PB31IMG.zip files but they are all giving me the same result. I do have adb access still and I tried rebooting it from there but it is the same. I feel like this is progress maybe (hopefully)...
As for the Stats:
S-off
h-boot-0.92.0000
radio-2.15.00.07.28
I know what s-off means, but do the other numbers mean anything to you?
I tried to send it through Unrevoked3 but it gives me the 'Device "/sbin/sh:getprop:not found" is not supported at this time.' error. I am going to see about RUU...
sounds kinda like a non slcd recovery on an slcd dinc.
I had the same problem rooting a friends phone.
Here's how I fixed it.
After trying to flash a Rom through ROM manager, it went to reboot into recovery to finish the job. The thing is, it didn't.
It wen't into a Black screen wioth two white bars. One on each side of the screen., So far, it hasn't looked like it had done anything. So I pulled battery and rebooted. Everything was fine. I went to ROM Manager and instead of installing through the app, I rebooted into recovery.
Black screen and white bars, AGAIN. So I figured I just needed to re-flash Clockwork.
I pulled his battery, and restarted. I flashed Clockwork, and booted into recovery.
IT WORKED!!! No problems since.
RUU worked! I have a fixed phone. I followed this:
www .droidforums.net/forum/droid-incredible-hacks/95406-how-correctly-unroot-incredible. html
in the hboot screen and it is back to factory reset and much happier. Thanks.
[They are not letting me post links so you will have to take out the spaces next to www and html.]
Alright. For starters, xda has been VERY VERY helpful to me over the past few months and I thank everyone who has ever contributed to a question or a discussion I have read. That being said, this is my first post. I watched the newb video, read many forums (both xda and others), google searched, read some more threads, kept reading threads, tried some methods described in some threads, bookmarked some interesting threads for if my phone ever works again, and read some more threads.
I am not saying the answer is not already out there, I am saying I have reached my resourcefulness cap.
Anyway, to the root of the problem: I'm not entirely new to rooting, and am comfortable using recovery and hboot to flash roms. I also had a nandroid backup! for SOME SILLY reason, while in my clockworkmod recovery this morning (maybe slightly due to being half asleep which is why I now recommend being fully awake before entering hboot or recovery or rom manager....etc) I formatted the system on my phone. I THINK.
My phone will now load up to display the bootloader, and go into recovery mode, and flash roms, but when I flash a rom, nothing changes. If I boot my phone up, it will show a notification bar at the top like usual, a stock wallpaper, and that is IT! it will show a message notification and missed call icon since I have them, but the touch screen will not work. The rosie buttons at the bottom do not show up (i.e. phone button or all aps button) no apps appear, no clocks except for in the notification bar... hardkeys have no effect (home button search button menu or back) and volume keys will not work. The lock button will only lock and unlock the screen, not power off or reboot or anything. If plugged in at this point, it is charger only.
So, I can take the micro sd card out and put files on it from my PC via a microsd-usb converter thing...
I have tried putting new roms on the sd and flashing them from recovery, no effect. Tried the RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe program, it always says that my phone has below 30% battery and will not continue (this is not the case as I have two batteries both have been fully charged because the phone will still charge them...)
And I have tried putting PC36IMG.zip files on my sd card to no avail.
I am thinking that the system was wiped because it seems like there is no boot image on the phones internal memory itself. I am currently looking for a way to place a boot image on the sd card to possibly flash it or some sort of update.zip so that my bootloader will ask me to update upon reading it.
Sorry for the long post, and ask any questions I will answer as best I can.
I am posting preemptively to the boot image adventure so that if it does not work, maybe I can have some help finding a solution by then.
I was going to take my evo to the sprint store since it is under warranty but if they go into recovery they will see clockworkmod recovery.
Thanks to all for any form of guidance!
I did just notice in my Bootloader menu (HBOOT-2.10.0001) that it says Supersonice evt2-3 **** S-ON
I don't know how because I thought it was a requirement that it says S-OFF to be rooted and flash roms, but I have definitely flashed roms before and gained su access to applications and such. BUT since it says S-ON would it then be covered by the warranty if it is not rooted?
Thanks again.
I you want to flash a boot image, you can take the boot.img from an RUU for the firmware you are, place it in your adb tools folder, then flash it using the commands:
fastboot flash boot boot.img
fastboot reboot
I'm not sure how to identify what firmware I am. Unless your talking about the Hboot version? and also, I can't place anything in any folder except onto my sd card. I have no access other than that to the phone. On the sd card there are no files except for what I put on there.
...aaand not to mention I don't know what adb is exactly...
Does your phone still go to clockwork when you go to recovery?
Am going to try it right now, but will that work if I cannot tell my phone to allow usb debugging? i remember something about unrevoked needing that to root the phone in the first place. will update as soon as I try it. May not have time right now as I have to leave in about 15 mins. If no reply by 9:45, then I will be back online tomorrow morning. and thanks!
Timeconsumer10 said:
Am going to try it right now, but will that work if I cannot tell my phone to allow usb debugging? i remember something about unrevoked needing that to root the phone in the first place. will update as soon as I try it. May not have time right now as I have to leave in about 15 mins. If no reply by 9:45, then I will be back online tomorrow morning. and thanks!
Click to expand...
Click to collapse
Welcome, but yes, you do need to have had usb debugging enabled, so we'll see how that goes.
SUPER THANKS! S-OFF tool worked perfectly just flashed a rom and now so far so good. Will post tomorrow to let you know if everything works well. So much appreciated =) I would thanks a million times if i could don't know what to do without my evo.
Timeconsumer10 said:
SUPER THANKS! S-OFF tool worked perfectly just flashed a rom and now so far so good. Will post tomorrow to let you know if everything works well. So much appreciated =) I would thanks a million times if i could don't know what to do without my evo.
Click to expand...
Click to collapse
Lol, it'd take you 200,000 days since you can only thank 5 times a day Though glad you're rooted now.
shortydoggg said:
Does your phone still go to clockwork when you go to recovery?
Click to expand...
Click to collapse
Yes it still goes to clockwork because its rooted.. now my screen legitimately does not work in certain areas of the screen (not responding to touch) so I'm going to try and get it stock stock stock unrooted and go for warranty replacement. Any ideas please let me know. Currently trying RUU Supersonic...
So, I got an ERROR [110] message from the RUU package its a file open error... :/ now i dont know what is up. Says I need a complete RUU package. Looking for another one or another option now.
If i boot phone normally now it just goes to a black screen with "htc" in the middle and "!" in a triangle in all four corners. Can't do anything from that screen.
If I boot into bootloader once where it says SHIP S-OFF at the top and instead of recovery and all those options it just says RUU but you cant do anything there... :/ I now, however cannot even get to the bootloader screen.
Could they tell it is rooted?
Maybe I could say I finally decided to do sprints OTA update that I've been denying for a while and this is the result.
Anyone agree disagree?
COCLUSION!
So. Since it has just the HTC logo and four error icons one in each corner... I took it into a sprint repair store. It would not boot into bootloader as a hard reset, so the guys at the store were stumped. They had actually never seen this before =). They asked me if I rooted it and all so I just played dumb. I told em I didn't know what that really was. They kinna explained it and I told em I didn't even have a computer (not a lie actually I sold mine and now use my dads or gfs lol). The logo on the screen was an oooold htc logo from like hero or so. So they just put it in the system as a wont even turn on type of thing and gave me a new phone since I was under warranty =) gonna see if I can live without root juuust for a little bit because work and school are gonna keep me busy for a while. I am certain to return though!
Can't wait to see what the devs can do by then!
Thanks to all for the help!
Hi, I attempted to root my Desire HD yesterday, and it went horribly wrong.
I followed the instructions, and it was all going well, until the process effectively froze. From researching this, I found that where it would appear I had gone wrong was that my SD card was not mounted.
I attempted to restart my phone, but the buttons had no effect, so I removed the USb cable. This took to me to a screen on my phone where it showed some options, which I understand are normally navigated by the volume and power buttons but again, these did nothing. I couldn't turn my phone off, and I was unable to remove the battery, despite following online videos on how to do this... In the end, I left my DHD to run out off battery in the hope that maybe a simple restart would roll back the whole process. When it eventually ran out of battery, I briefly charged it (so as to be able to turn it back on). Whilst charging, the orange LED flashes, then stays on. I then pressed the power button. It now shows the simple "HTC" screen, until it runs out of battery, and again, the buttons have no effect. How do I return to the original state of the phone? There's no warranty on it or anything so I have no qualms about taking it apart if that is required.
Did the screen It took you in have green androids at the bottom thats called h -boot or was it in clockwork mod recovery
It had green androids at the bottom, with I think 3 of them at different angles
Hey dude.
Don't panic.
Follow my instructions here, http://forum.xda-developers.com/showthread.php?p=22306501 and all should be well.
Greg.
Sent from my Desire HD using Tapatalk
Did you have any luck?
Sent from my Touchpad using Tapatalk
No - I've found an image and put it on the mSD card, and it's recognised, but then it goes to the same old screen with all the options...
First of all, does your buttons (volumes and power) work fine in hboot screen?
What it your recovery? The DHD original one or CW re. or other custom re?
From above, if it is the original one, does your DHD unlocked?
The volume and power buttons work fine.
I don't know which PD98 I have, it's one I found online. I want to return back to my standard DHD, not root it.
Yes, it is unlocked.
May I know how you tried to root your phone? And the information in the hboot screen (which have 3 android with different angle) just after the line ***Unlocked*** It should be looks like S-ON / S-OFF
I used the following video: youtube.com/watch?v=zY8TFZ2Owk0
Although I read somewhere to put it in "charge-only" mode, which I reckon is where I went wrong.
There isn't a "unlocked" line as such (but it is unlocked as I did that myself using the codes etc online) but it's S-ON
Dude... it should be a unlocked line if you had unlocked the device... I am saying the HTC dev. unlock.
Had you ever tried to flash the clockwork recovery?
But what I guess is the boot.img broken or at lease sth wrong with it, may I know which step you had starting fail? You can point it with the uTube video(like the process goes well until 3:45 in the video)
---------- Post added at 02:09 AM ---------- Previous post was at 01:58 AM ----------
You can try flashing the newest RUU to solve it (with all data safe). Depends on your luck.
baynesy said:
I used the following video: youtube.com/watch?v=zY8TFZ2Owk0
Although I read somewhere to put it in "charge-only" mode, which I reckon is where I went wrong.
There isn't a "unlocked" line as such (but it is unlocked as I did that myself using the codes etc online) but it's S-ON
Click to expand...
Click to collapse
Yeah it needs to be in charge only mode when you run the hack kit.
As a side note, they should really change (or add more information) to that video as it's not entirely accurate.... I have never had to rename a ROM 'update.zip' for it to work, and you definitely don't need to go into the bootloader each time to get to the recovery. And you need to do more than wipe the cache beforehand.
Hey mate,
Had a similar issue, couldn't use the volume buttons to navigate, however, i let it sit on that screen for about 1-2 minutes, then i was able to use the volume buttons. Not sure why, probably just took a really long time to load up.
Hi... Are you still here?
Brick DHD
Hi, I have similar problem as baynesy with small differences.
I did root my Desire HD too, but in Ace advanced hack kit. I di mSD card as goldcard, next a put PD98IMG.zip (1.32.X) on sdcard. Then I started with root first three steps going well. After succesfully installing root, clockworkmod and first radio start next step flash new radio and here was the problem. Connection with PC fell and flashing was stoped. Now I have only black background without any mark of starting of device. Only orange LED flashes.
I tryed to remove battery and wait 10 minutes but without any succes.
Please can you help me with this problem?
Hello, I know that there have been posts in the past to address this, but I haven't found one yet that has valid links to the files needed.
I was following the instructions in this thread, and the problem occurred when I followed the instructions linked in step 3.
Does anybody know of a location where I can get the files and good instructions for fixing this brick?
If you cant get into hboot, im afraid there isnt anything you can do, the phone is bricked. Does it vibrate or do anything att all.
There is a known issue where flashing a wrong clockworkmod recovery to the wrong screen type can leave the phone functional but without the screen working. That is probably what you were thinking of. If you didnt flash an older version of cwm right before trying to enter hboot to do the ruu, then this is not your issue.
I can get the phone to vibrate like it's turning on by holding the poer button down, but nothing else. I did not flash any new recoveries, I've been on the latest CWM for a while.
Just for anybody else who might need it, I finally found a PB31IMG.zip that works to get back to stock 2.3.4
Link
Thanks
Sent from my Incredible using XDA App
Droid Incerdible 1 vibrate when turned on but black screen
I'm new to the site and maybe this has been answered. But I have a droid incredible rooted. It will charge and the orange light will appear but when I attempt to turn on the phone it will vibrate once but the screen remains black, when connected to a computer and the power the phone on and it vibrates once the computer can detect it.
I do not have any of the files need for the phone on my sd card due to old one being lost so I know I need them, as well as the proper htc sync software. If someone could point me in the right direction that would be awesome
Boostedk said:
I'm new to the site and maybe this has been answered. But I have a droid incredible rooted. It will charge and the orange light will appear but when I attempt to turn on the phone it will vibrate once but the screen remains black, when connected to a computer and the power the phone on and it vibrates once the computer can detect it.
I do not have any of the files need for the phone on my sd card due to old one being lost so I know I need them, as well as the proper htc sync software. If someone could point me in the right direction that would be awesome
Click to expand...
Click to collapse
See the link in cmlusco's sig, above. You should be able to find all the files you need and more there.