Evo 2.2 and 2.3 force close issues (unrevoked root)

jmac2876

New member
Jun 30, 2011
3
0
0
First I should clarify that I have read though alot of posts on how to root, unroot, update, backdate etc - what to do and what not to do -- and still nothing. I should also disclose that I am no pro, or wiz at this stuff so I may get lost in some of youre responses. Im in the St. Louis Area if that matters, and I hope that someone here can help me since I cant find anything in the forums specific to my instance. I am ultimatetly trying to stay on 2.2 with a stable root for wi-fi tether and thats it - no roms, no superuser controls other then wifi. I need to have the occasional access to the wifi for work.

Initially I did the typical "root for wi-fi tether" using Unrevoked3 (not Unrevoked Forever) on 2.2. This was very stable and worked well for nearly 6 months. Unfortunatly, when GB came out I unknowingly accepted the update without unrooting first. My mistake, and this is the begining of my issues.

After a week or two of issues with the initial release I bailed back to 2.2 using the instructions posted on here for (RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed). Post installation of this RUU my system has the occasional boot loop, force close, and incidental power cycle. If I go into hboot I see that PC36IMG.nbh - no image - wrong image . Also, when I tried to go into recovery the HTC EVO 4G white screen came up, then comes a "triangle exclaimation point" page. So I know there is an issue somewhere - just dont know exactly where.

So after much frustration and many different flashes of different versions of the 3.7 erasing SD and devlic and caches, I still have the same problems. I've now gone back to GB thinking it might be more stable at this point for simple use. Which it seems to be for now but I am still having the occasional system cylcle on and off.

Here is what my info.
Software information
2.3.3
2.15.00.05.02
2.6.35.10.gc0a661b
htc-kernal@and18-2#1
Tue Jun 14
4.24.651.1 CL61076
2.15_003
60680

HBOOT Screen says.
Supersonic EVT3 Ship S-OFF
Hboot 2.16.0001
Radio 2.15.00.05.02
Mar 8 2011

IF I COULD JUST FLASH EVERYTHING BACK TO BLANK AND START ALL OVER AGAIN I WOULD BE HAPPY - Hell, I would even consider putting S-On a smashing the thing and claiming it on insurance just to fix it correctly.
 
First I should clarify that I have read though alot of posts on how to root, unroot, update, backdate etc - what to do and what not to do -- and still nothing. I should also disclose that I am no pro, or wiz at this stuff so I may get lost in some of youre responses. Im in the St. Louis Area if that matters, and I hope that someone here can help me since I cant find anything in the forums specific to my instance. I am ultimatetly trying to stay on 2.2 with a stable root for wi-fi tether and thats it - no roms, no superuser controls other then wifi. I need to have the occasional access to the wifi for work.

Initially I did the typical "root for wi-fi tether" using Unrevoked3 (not Unrevoked Forever) on 2.2. This was very stable and worked well for nearly 6 months. Unfortunatly, when GB came out I unknowingly accepted the update without unrooting first. My mistake, and this is the begining of my issues.

After a week or two of issues with the initial release I bailed back to 2.2 using the instructions posted on here for (RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed). Post installation of this RUU my system has the occasional boot loop, force close, and incidental power cycle. If I go into hboot I see that PC36IMG.nbh - no image - wrong image . Also, when I tried to go into recovery the HTC EVO 4G white screen came up, then comes a "triangle exclaimation point" page. So I know there is an issue somewhere - just dont know exactly where.

So after much frustration and many different flashes of different versions of the 3.7 erasing SD and devlic and caches, I still have the same problems. I've now gone back to GB thinking it might be more stable at this point for simple use. Which it seems to be for now but I am still having the occasional system cylcle on and off.

Here is what my info.
Software information
2.3.3
2.15.00.05.02
2.6.35.10.gc0a661b
htc-kernal@and18-2#1
Tue Jun 14
4.24.651.1 CL61076
2.15_003
60680

HBOOT Screen says.
Supersonic EVT3 Ship S-OFF
Hboot 2.16.0001
Radio 2.15.00.05.02
Mar 8 2011

IF I COULD JUST FLASH EVERYTHING BACK TO BLANK AND START ALL OVER AGAIN I WOULD BE HAPPY - Hell, I would even consider putting S-On a smashing the thing and claiming it on insurance just to fix it correctly.
Also, If anyone thinks if may be easier to simply call me - feel free to PM me and we can get though this alot quicker.
 
Since you have S-OFF all you need to do is install a custom recovery through your hboot and you can flash any rom.

Download the PC36IMG.zip and put it on your sd card. Go into hboot (power off, then hold Volume Down + Power until your white screen with androids pop up) and let it screen for the PC36IMG. When it finds it, it will ask if you want to update and select by pushing Volume up. Once done reboot. Go back into hboot and select recovery and flash away.

Trust me. :)

PC36IMG.zip This is for Amon_RA 2.3
 
*** DISCLAIMER *** Had this thought AFTER I posted below ... Not sure if that PCIMAG36 is H/W version dependent - I've got V002

OK ... So you're wanting to go "back to your future" (sorry, had to) ... There is a possible way fer ya ... The original image is located at PC36IMG.zip - 4shared.com - online file sharing and storage - download and has a MD5 checksum of e52f6ec4f8f5fd6dc251ef19ee19750b

I downloaded this file and the checksum matched ... ALSO, I happen to have a copy of the file as well - also a match ...
(got this info fromo droid demos http://www.thedroiddemos.com/forum/viewtopic.php?f=18&t=7

1) Download it
2) put it on your SD card
3) boot into bootloader - peform steps to flash this ... (will also put on the original bootloader)
4) then do two OTA updates ... should put you to the OS version BEFORE GB.
 
Last edited:
Did you already have root / s-OFF when you did that, or were you on unrooted OTA 2.3.3, flashed back to 2.1, then back to 2.2, and were able to root that way?
 
Did you already have root / s-OFF when you did that, or were you on unrooted OTA 2.3.3, flashed back to 2.1, then back to 2.2, and were able to root that way?

You talk'n to me?? :D

The steps I outlined will effectivly remove root - but will not touch S-OFF/ON... Providing you're S-OFF, you will have a route to re-root if you so desire. To do that:
1) apply a custom recovery ( I use ClockworkMod)
2) flash root

Yes, I'm on "vanilla" GB 2.3.3 but have ClockworkMod recovery and root is flashed.
 
will this work on an unrooted evo? i decided to root a day to late..... trying to find a way to get back to 2.2 dont like all the force close problems with 2.3, please help
 
will this work on an unrooted evo? i decided to root a day to late..... trying to find a way to get back to 2.2 dont like all the force close problems with 2.3, please help

No it will not. Sorry. Key to getting it to work is having S-OFF, which means you had to be rooted first.

Don't worry as a guy on XDA said he thinks he has found an exploit and another dev will be starting some time soon. Not sure how soon really.
 
No it will not. Sorry. Key to getting it to work is having S-OFF, which means you had to be rooted first.

Don't worry as a guy on XDA said he thinks he has found an exploit and another dev will be starting some time soon. Not sure how soon really.
Actually hadn't considered that @SomkeCrawler... Easy test - put the PCIMAG36 on your sd card and boot up into bootloader... If the phone likes it, you're good to go ... If it doesn't (maybe you get the red tirangle of death), reboot and delete the file. But as I mentioned before, I'm also not sure if that IMAGE is H/W dependant ...

Allternately, you could S-OFF, flash that IMAG, S-ON and take OTA ... A lot of work I know ... But should get you to where you want to be.