Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,741,801 Members 44,127 Now Online
XDA Developers Android and Mobile Development Forum

[Q] Problem Flashing New Rom

Tip us?
 
muttleytm
Old
#11  
Junior Member - OP
Thanks Meter 0
Posts: 28
Join Date: Sep 2013
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...
 
Captain_Throwback
Old
#12  
Captain_Throwback's Avatar
Retired Moderator / Recognized Contributor
Thanks Meter 8757
Posts: 10,155
Join Date: Aug 2008
Location: Bensalem, PA

 
DONATE TO ME
Quote:
Originally Posted by muttleytm View Post
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...
Have you tried using a different recovery, in case that's the issue? DId you also confirm that you got a good download by verifying the MD5?
Device 1: HTC One (M8)/831C | Hardware Version: 0005

Baseband: 1.08.20.0612_4 | PRI: 2.62_003 | PRL: 56019
Recovery: TWRP 2.7.1.0

Device 2: HTC Jewel/PJ75100 (EVO 4G LTE) | Hardware Version: 0003

Baseband: 1.13.11.1105 | PRI: 3.02_003 | PRL: 56018
Recovery: TWRP 2.7.1.0b

Device 3: HTC Shooter/PG86100 (EVO 3D) | Hardware Version: 0002
Baseband: 1.09.00.0108 | PRI: 1.55_003 | PRL: 22100
Recovery: TWRP 2.7.1.0

Device 4: HTC Supersonic/PC36100 (EVO 4G) | Hardware Version: 0004
Baseband: 2.15.00.01.15 | PRI: 2.33_003 | PRL: 40460
Recovery: TWRP 2.7.1.0
 
muttleytm
Old
#13  
Junior Member - OP
Thanks Meter 0
Posts: 28
Join Date: Sep 2013
I've checked the MD5s on all the files I've used.

This is the only recovery I could find that wood work.

I saw some mention of a smelkus version and I tried those but it looks like they all had a ROM built in or something. When I tried them it would say parsing and not get any further.

I looked for a TWRP but couldn't find one for and EVO 4G supersonic on their website. I see you have TWRP 2.7.0.6 and when I do a search of this all I see is an unofficial version for an HTC One.

I didn't find a Clockworkmod when I checked earlier, but, I checked again just now and found recovery-clockwork-touch-5.8.0.1-supersonic.img.

I'll give that a try or maybe you have another suggestion.
 
Captain_Throwback
Old
(Last edited by Captain_Throwback; 22nd April 2014 at 06:35 PM.)
#14  
Captain_Throwback's Avatar
Retired Moderator / Recognized Contributor
Thanks Meter 8757
Posts: 10,155
Join Date: Aug 2008
Location: Bensalem, PA

 
DONATE TO ME
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.
Device 1: HTC One (M8)/831C | Hardware Version: 0005

Baseband: 1.08.20.0612_4 | PRI: 2.62_003 | PRL: 56019
Recovery: TWRP 2.7.1.0

Device 2: HTC Jewel/PJ75100 (EVO 4G LTE) | Hardware Version: 0003

Baseband: 1.13.11.1105 | PRI: 3.02_003 | PRL: 56018
Recovery: TWRP 2.7.1.0b

Device 3: HTC Shooter/PG86100 (EVO 3D) | Hardware Version: 0002
Baseband: 1.09.00.0108 | PRI: 1.55_003 | PRL: 22100
Recovery: TWRP 2.7.1.0

Device 4: HTC Supersonic/PC36100 (EVO 4G) | Hardware Version: 0004
Baseband: 2.15.00.01.15 | PRI: 2.33_003 | PRL: 40460
Recovery: TWRP 2.7.1.0
 
muttleytm
Old
#15  
Junior Member - OP
Thanks Meter 0
Posts: 28
Join Date: Sep 2013
Quote:
Originally Posted by Captain_Throwback View Post
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?
 
Captain_Throwback
Old
#16  
Captain_Throwback's Avatar
Retired Moderator / Recognized Contributor
Thanks Meter 8757
Posts: 10,155
Join Date: Aug 2008
Location: Bensalem, PA

 
DONATE TO ME
Quote:
Originally Posted by muttleytm View Post
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?
The image files are in the zips. Just extract them and you can fastboot flash them. Flashing them through HBOOT only works if the main versions match up.

Actually a logcat might be helpful, if adb is working and you have a computer.
Device 1: HTC One (M8)/831C | Hardware Version: 0005

Baseband: 1.08.20.0612_4 | PRI: 2.62_003 | PRL: 56019
Recovery: TWRP 2.7.1.0

Device 2: HTC Jewel/PJ75100 (EVO 4G LTE) | Hardware Version: 0003

Baseband: 1.13.11.1105 | PRI: 3.02_003 | PRL: 56018
Recovery: TWRP 2.7.1.0b

Device 3: HTC Shooter/PG86100 (EVO 3D) | Hardware Version: 0002
Baseband: 1.09.00.0108 | PRI: 1.55_003 | PRL: 22100
Recovery: TWRP 2.7.1.0

Device 4: HTC Supersonic/PC36100 (EVO 4G) | Hardware Version: 0004
Baseband: 2.15.00.01.15 | PRI: 2.33_003 | PRL: 40460
Recovery: TWRP 2.7.1.0
 
muttleytm
Old
#17  
Junior Member - OP
Thanks Meter 0
Posts: 28
Join Date: Sep 2013
Quote:
Originally Posted by Captain_Throwback View Post
The image files are in the zips. Just extract them and you can fastboot flash them. Flashing them through HBOOT only works if the main versions match up.

Actually a logcat might be helpful, if adb is working and you have a computer.
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?
 
Captain_Throwback
Old
#18  
Captain_Throwback's Avatar
Retired Moderator / Recognized Contributor
Thanks Meter 8757
Posts: 10,155
Join Date: Aug 2008
Location: Bensalem, PA

 
DONATE TO ME
Quote:
Originally Posted by muttleytm View Post
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?
The connection might be your problem. Not sure that a logcat would even show that.
Device 1: HTC One (M8)/831C | Hardware Version: 0005

Baseband: 1.08.20.0612_4 | PRI: 2.62_003 | PRL: 56019
Recovery: TWRP 2.7.1.0

Device 2: HTC Jewel/PJ75100 (EVO 4G LTE) | Hardware Version: 0003

Baseband: 1.13.11.1105 | PRI: 3.02_003 | PRL: 56018
Recovery: TWRP 2.7.1.0b

Device 3: HTC Shooter/PG86100 (EVO 3D) | Hardware Version: 0002
Baseband: 1.09.00.0108 | PRI: 1.55_003 | PRL: 22100
Recovery: TWRP 2.7.1.0

Device 4: HTC Supersonic/PC36100 (EVO 4G) | Hardware Version: 0004
Baseband: 2.15.00.01.15 | PRI: 2.33_003 | PRL: 40460
Recovery: TWRP 2.7.1.0
 
muttleytm
Old
#19  
Junior Member - OP
Thanks Meter 0
Posts: 28
Join Date: Sep 2013
Quote:
Originally Posted by Captain_Throwback View Post
The connection might be your problem. Not sure that a logcat would even show that.
I did fiddle with the connection and the touchscreen didn't respond and did it again. That time it worked. I also saw that the EVOs have a grounding issue that is fixed if you hold it by the back and sides which I was doing at the time.

I am having some trouble with the Google Play Store App now though. I can find the app I want to install and when I press install it doesn't start to download. Have tried it with several apps and they all act the same. I tried clearing the Play Store App cache, data and uninstalled the updates, but, still won't install.

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


TRENDING IN THEMER...