Root Stuck on boot screen

[33mega33]

^This seems very possible to me.

To the OP:
Are you sure when you replaced the screen that you reconnected everything (and correctly)? It could be a little connection linked to the touch screen (digitizer?) that's preventing the touch screen from initializing - which is why the phone is actually booting up, but you can't see anything.

I think that's the first thing to look at. It sounds like the software is working fine.

Yes, after encounting the problem I unistalled the screen and installed back again.
I'm sure the screen is properly installed since it display perfectly in other instances for example the bootloader screen and the update screen (black with HTC logo in the middle)

this is very weird

 

[CapThrowback]

Yes, after encounting the problem I unistalled the screen and installed back again.
I'm sure the screen is properly installed since it display perfectly in other instances for example the bootloader screen and the update screen (black with HTC logo in the middle)

this is very weird

Right, but in all those instances, the touch screen drivers aren't enabled/initialized. It seems related to the touch screen initialization. Especially if the phone is working besides the display.

 

[Mikestony]

Right, but in all those instances, the touch screen drivers aren't enabled/initialized. It seems related to the touch screen initialization. Especially if the phone is working besides the display.

Do you think it is an exercise in futility to try to root and install custom rom?
Or should 33mega play with the ribbon connectors some more? Perhaps get some electronic cleaner and use that on the connections?

 

[CapThrowback]

Do you think it is an exercise in futility to try to root and install custom rom?
Or should 33mega play with the ribbon connectors some more? Perhaps get some electronic cleaner and use that on the connections?

I don't think rooting will be the answer, as I doubt it'll get the display working. However unlocking only requires being in fastboot, so the OP can try that. And installing a custom recovery can also be done via bootloader. Then, maybe we can see if booting into recovery would work.

 

[33mega33]

So should I keep going with the rooting process i mean Im on step 1 of the HTCdev guide

 

[Mikestony]

Gotcha, well, at least 33mega had better luck replacing the glass than I did on a co-workers phone---after replacement, the lcd screen was fudged---as in, colors were all wonky....brought it back to Sprint, and got the phone replaced for about 175 bucks.
Lesson learned for me anyways, I ain't messin with replacing screens no more

 

[Mikestony]

So should I keep going with the rooting process i mean Im on step 1 of the HTCdev guide

In my opinion, nothing will be lost trying...go for it I say

 

[33mega33]

You see Im unlocking the phone and the unlocking screen displays normally. this makes me wonder what "CapThrowback" says, Since every time the screen displays is on an instance where the touch sreen is not needed.

But again Im sure about the conections of the screen, I even tried the old cracked screen yesterday but got the same result.

Anyways i may be worth trying so Ill keep going Im just letting you guys know.

 

[33mega33]

In my opinion, nothing will be lost trying...go for it I say

Well gentlemen I finished unlocking and rooting the phone. Im in step 3 of the HTCdev method. trying to install a custom rom, now I cant get the bootloader screen , the phone stays stuck on the splash screen even when I hold "power on +vol down"

any sugestions?

 

[iowabowtech]

Well gentlemen I finished unlocking and rooting the phone. Im in step 3 of the HTCdev method. trying to install a custom rom, now I cant get the bootloader screen , the phone stays stuck on the splash screen even when I hold "power on +vol down"

any sugestions?

Did you power off the phone or pull the battery before using the volume down + power combo?

 

[33mega33]

Did you power off the phone or pull the battery before using the volume down + power combo?

Actually I pulled out the battery for a while and now I make it trough the bootloader screen . BUT, still I cant use the recover menu . I tried and it does the same as before (stuck on the splash screen)

 

[CapThrowback]

Actually I pulled out the battery for a while and now I make it trough the bootloader screen . BUT, still I cant use the recover menu . I tried and it does the same as before (stuck on the splash screen)

From the folder with adb in it, and with the device connected after you've selected "RECOVERY" from the bootloader menu, type in

adb devices

at the command prompt, and see what it says (if anything).

 

[iowabowtech]

Actually I pulled out the battery for a while and now I make it trough the bootloader screen . BUT, still I cant use the recover menu . I tried and it does the same as before (stuck on the splash screen)

Ok so you you can access the bootloader and the volume key are moving the curser ok. So you are highlighting recovery and then pressing power to enter recovery, does that all sound right?

Also, what method did you use to root? Have you fastboot flashed a custom recovery?

 

[33mega33]

From the folder with adb in it, and with the device connected after you've selected "RECOVERY" from the bootloader menu, type in

adb devices

at the command prompt, and see what it says (if anything).

I just tried right now this is what i got on the CMD screen:

adb server is out of date. Killing...
*daemon started sucessfully *
List of devices attatched
HT17CHL23455 recovery

thats is, the splash screen still displaying on the phone

 

[CapThrowback]

I just tried right now this is what i got on the CMD screen:

adb server is out of date. Killing...
*daemon started sucessfully *
List of devices attatched
HT17CHL23455 recovery

thats is, the splash screen still displaying on the phone

Yup, just as I thought - the device is actually booted into recovery, with adb working, even though the screen isn't displaying it.

Definitely an issue with the display - must be with the touch screen.

 

[iowabowtech]

Yup, just as I thought - the device is actually booted into recovery, with adb working, even though the screen isn't displaying it.

Definitely an issue with the display - must be with the touch screen.

+1. Good thinking with the adb devices command. And that answers my question too, you obviously already have a custom recovery so nevermind that.

 

[33mega33]

Ok so you you can access the bootloader and the volume key are moving the curser ok. So you are highlighting recovery and then pressing power to enter recovery, does that all sound right?

Also, what method did you use to root? Have you fastboot flashed a custom recovery?

yes that sounds right, I used the HTCdev method to root.
I havent been able to see if i got a custom recovery since everytime I try to go there all I got is the splash screen.

 

[33mega33]

Yup, just as I thought - the device is actually booted into recovery, with adb working, even though the screen isn't displaying it.

Definitely an issue with the display - must be with the touch screen.

What you suggest then, you think i should try another screen? , as I stated before I check all the connections and even tried the old cracked screen without having a better result.

 

[iowabowtech]

yes that sounds right, I used the HTCdev method to root.
I havent been able to see if i got a custom recovery since everytime I try to go there all I got is the splash screen.

HTCdev unlocks but you evidently used a root method to get your custom recovery. And you do have one or you wouldn't get a positive response from adb.

So, where did you get the replacement screen? I'm kinda guessing maybe it's not compatible with the onboard display drivers. Just a hunch, could be wrong.

 

[CapThrowback]

What you suggest then, you think i should try another screen? , as I stated before I check all the connections and even tried the old cracked screen without having a better result.

Maybe another screen or digitizer is the answer, I'm not sure. I've never taken my EVO apart, so I'm not really an expert on that. Maybe someone else with more experience with replacing the screen/digitizer can chime in here. Are there any threads around with instructions for replacing them that we might be able to reference?

 

[33mega33]

HTCdev unlocks but you evidently used a root method to get your custom recovery. And you do have one or you wouldn't get a positive response from adb.

So, where did you get the replacement screen? I'm kinda guessing maybe it's not compatible with the onboard display drivers. Just a hunch, could be wrong.

I got it from amazon.. you think the inger screen may have something to be with the problem , Since installing the old touch screen didnt show any improvement..

 

[33mega33]

Maybe another screen or digitizer is the answer, I'm not sure. I've never taken my EVO apart, so I'm not really an expert on that. Maybe someone else with more experience with replacing the screen/digitizer can chime in here. Are there any threads around with instructions for replacing them that we might be able to reference?

Can you explain to me what is the difference between the screen and the digitizer?
I havent check out for problem with the hardware since Ive been working on the software. since I got this situation .

 

[CapThrowback]

Can you explain to me what is the difference between the screen and the digitizer?
I havent check out for problem with the hardware since Ive been working on the software. since I got this situation .

I'm not actually sure. I believe the screen is the glass portion, and the digitizer is essentially the touch screen layer. If you only replaced the screen and not the digitizer, perhaps that's the issue (if those are in fact their actual purposes)?

EDIT: Is this what you replaced - Newegg.com - HTC Evo 4g Replacement Touch Screen Digitizer Lens Part ?

 

[iowabowtech]

Yeah there is the outer screen (essentially a protective cover), then the digitizer, then the actual lcd screen. I would agree that all signs point to the digitizer.

edit: nope I take that back. The digitizer is in fact the outermost layer, then the lcd. So it seems likely that you replaced the right part. Hmmm.

 

[33mega33]

I'm not actually sure. I believe the screen is the glass portion, and the digitizer is essentially the touch screen layer. If you only replaced the screen and not the digitizer, perhaps that's the issue (if those are in fact their actual purposes)?

EDIT: Is this what you replaced ?

well I replaced both (thought It was a complex/only one part)
... Im not sure what to say about the screen(not the touch panel) because as I said before it displays every instance where the touchscreen is not required. I'm starting to think I should start by getting another touch panel