It makes the startup sound and the animation starts and forms the yellow EVO 4G on a white background appears, some time goes by, the screen turns black, then the lock bar with time and date shows up on a black background and at the top of the screen you can see the battery charge indicator and the signal strength inicator (I think it makes a sound at this point too), then it goes black. After this it cycles from black screen to yellow EVO 4G/white background and repeat...
I just updated the TWRP listed in my signature for Supersonic to a link to my thread with a fully working TWRP build .
Don't use ClockworkMod. Also, smelkusMOD isn't linked to any particular ROM; it should work fine.
I renamed your TWRP file to PC36IMGG.zip and ran hboot. I didn't check when I started it, but, it was only a couple minutes after your post. It said parsing for quite a long time.
Also when I went to the Smelkus links and they are the same files I had tried earlier where zip files also got stuck at parsing. They all had ROM names associated with them like ReLoaded, AOKP, etc. So I figured they also had a ROM. I did try the smelkus AOKP img file using fastboot and I was able to flash it. I think I recall seeing that custom recoveries have to be installed with fastboot now that I think of it.
Anyway, the phone continues to behave the same as before. It makes a startup sound and gets the to yellow 4G on the white background and stays there for awhile and then goes black. I had it in my pocket or with me in the car for a couple of hours now and I can hear it cycling and every time I checked right after the sound it was the yellow EVO 4G screen. I didn't notice if the lock bar on a black screen showed up as the try with the other recovery app.
I thought I saw that you could make an img file from a zip file, but, I see it only works the other way. If you can provide the img version of your TWRP recovery app I'll try that too.
Is there some log file that might show what is happening?
I got TWRP installed. However, my touch pad is not working. I don't know if that would throw things off when booting up. When I first put it back together after replacing the board this happened and I opened it up and found that the locking mechanism wasn't in the locked position. I put it the way it should be and my touch screen did work the one time I booted up and got the phone running.
I didn't get a chance to take it apart today and take a look at the connection. I should get a chance to look take it apart with no interruptions tomorrow afternoon.
I do have a computer and have adb installed and I have used it in the past. I'm not sure if it will work if the phone isn't booted up since the setting for USB debugging is made from the GUI. Maybe I can connect using USBboot and then use adb?
|Thread Tools||Search this Thread|