Root HTC Evo stuck on screen with 4 triangles and "HTC" in middle!!!!

[Mikestony]

In step 2:

step#2 we need to get a stock rom and stock recovery

did you delete the previous PC36IMG file before running the ruu PC36IMG?

2.delete the previous PC36IMG file from the sd card, if you used the bootloader method mentioned above.

 

[neofitox2]

Yes, I deleted the firs PC36IMG File, and loaded the RUU PC36IMG, the problem is doesn't recognize it and appear the same screen with the 4 triangles.

There is any way I can load the Recovery???

 

[Mikestony]

A custom recovery? Not sure and not sure why you want to do that?
I am befuddled as to why the RUU will not install?

 

[neofitox2]

Sorry I have not respond it before I was on business travel.

I was thinking with a custom Recovery I would be able to load the ROM...

 

[ocnbrze]

I downloaded the RUU mentioned above, and run it, but at the end I get the same error as ymnrad:

-Rvolutionary-
"SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-6.16.1002
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.12.19
Mar 8 2011, 17:02:15

RUU

[1] BOOTLOADER - Bypassed
[2] RADIO_V2 - OK
[3] RADIO_CUST - OK
[4] BOOT - FAIL-PU
[5] RECOVERY - OK
[6] SYSTEM -OK
[7] USERDATA -OK
[8] SPLASH1 -OK
[9] WIMAX -OK
Partition update fail!

I can't start with Recovery, there is anyway to load the Recovery?

ok not really sure if there is much you can do........looks like your partition might have gone bad.....it does happen from time to time.

i'll pm scotty and see if he knows a fix for this. but, i doubt that there is.

 

[scotty85]

Hmm, I would think you need more than that :hmmmm:
Take a look at this thread:
http://androidforums.com/evo-4g-all-things-root/655895-complete-unrooting-guide-evo-4g.html

and scroll down to "Method 2"/ "If you have hboot 6.16.1002, s-off-- follow this guide:"

I think you need to install the hex edited hboot first...

This is the screen before the Android Flasher
https://dl.dropboxusercontent.com/u/4593589/WP_20140604_16_25_57_Pro.jpg

I tried in another computer an I was able to run the Android Flasher, but now it is telling me the Phone have S-ON.

just wanted to interject here... do not by any means install a different hboot. the revolutionary hboot is patched to ignore the security flag,its not a true security off like that provided by unrevoked. this is why the flasher thinks you are s on. its checking the location of the security flag in phone,it does not realize you have a patched hboot.

this hboot is letting you ignore several security checks(main version,signiture,etc) just like a true s off device,so its very beneficial. removing it will leave you s on,and make any more attempts to fix the device difficult at best.

also,the revolutionary hboot is patched for a few extra eng type fastboot commands,so we may have a few extra options.

a couple things you can do:
enter this and paste for us the results(the "?" is part of the command):
fastboot oem ?

also,you can try:
fastboot erase boot

and let us know what errors you get if any. if successful,try running the ruu again.

you might also try a few other ruus. i personally would run one old enuff to allow unrevoked to work... that way we can go ahead and flash the forever patch in recovery,wich will lift the write protections still in place. not sure if this will help or not,but it wont hurt

 

[neofitox2]

I will try that, and let you know.

Thanks!!

 

[neofitox2]

This is what I get with the fastboot oem ?:

(bootloader) command list
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) heap_test
(bootloader) rtask
(bootloader) task
(bootloader) enableqxdm
(bootloader) gencheckpt
OKAY [ 0.012s]
finished. total time: 0.013s

And this is the error I get when tried the fastboot erase boot:
erasing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.005s

Thanks

 

[scotty85]

This is what I get with the fastboot oem ?:

(bootloader) command list
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) heap_test
(bootloader) rtask
(bootloader) task
(bootloader) enableqxdm
(bootloader) gencheckpt
OKAY [ 0.012s]
finished. total time: 0.013s

And this is the error I get when tried the fastboot erase boot:
erasing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.005s

Thanks

wow thats a pretty short list... im also a bit surprised the revolutionary hboot wouldnt let you fastboot erase xxx

haVE YOU Tried running any different ruus?again,id run one that unrevoked will work on,install a recovery,and flash the forever patch. once youre a true s off,we could try installing an eng hboot(i think one exists) and see if we have any extra commands with it.

 

[neofitox2]

I have tried these RUUs, but none of them have worked.
RUU_SuperSonic_GB_Sprint_WWE_4.24.651.1_Radio_2.15.00.05.02_NV_2.15_release_199233_signed
RUU_SuperSonic_GB_Sprint_WWE_4.53.651.1_Radio_2.15.00.0808_NV_2.15_release_209995_signed
RUU_SuperSonic_GB_Sprint_WWE_4.54.651.1_Radio_2.15.00.0808_NV_2.15_release_220182_signed
RUU_SuperSonic_GB_Sprint_WWE_4.67.651.3_Radio_2.15.00.12.19_NV_2.33_release_234563_signed

Do you have any other RUU sugestions?

Thanks!

 

[ocnbrze]

I have tried these RUUs, but none of them have worked.
RUU_SuperSonic_GB_Sprint_WWE_4.24.651.1_Radio_2.15.00.05.02_NV_2.15_release_199233_signed
RUU_SuperSonic_GB_Sprint_WWE_4.53.651.1_Radio_2.15.00.0808_NV_2.15_release_209995_signed
RUU_SuperSonic_GB_Sprint_WWE_4.54.651.1_Radio_2.15.00.0808_NV_2.15_release_220182_signed
RUU_SuperSonic_GB_Sprint_WWE_4.67.651.3_Radio_2.15.00.12.19_NV_2.33_release_234563_signed

Do you have any other RUU sugestions?

Thanks!

ok this is the thing.....the ruu's only work if you have firmware(in this case for this phone radio) that is the same or older then the ruu you are planning to use.

your radio is at 2.15.00.12.19 the one's from previous ota's will not work.....the only way to lower your radios in order to flash a older ruu is to lower your misc partition.

so what scotty is saying is that you need to lower your misc partition and then run a 3.70 ruu which will allow you to root using unrevoked. you basically need the forever patch even though you have s-off already. you will need a custom recovery which is provided when you run unrevoked.

the only thing is, i'm not sure but, i think the unrevoked forever patch is down. i tried to download and it downloaded a file called download and i'm not sure what kind of file it is.....do not remember the site ever doing that.


hey scotty would any unrevoked forever.zip work?

 

[scotty85]

so what scotty is saying is that you need to lower your misc partition and then run a 3.70 ruu which will allow you to root using unrevoked. you basically need the forever patch even though you have s-off already. you will need a custom recovery which is provided when you run unrevoked.

in this case,we do not need to mess with the main version or the misc partition. the revolutionary hboot is ignoring the security checks that the radio wants to do,so all he needs to do is run ruu.

i think he meant that he has tried the below ruus,and that they have not fixed his phone,i dont think he had any issue running them(other than the boot failure).

the only thing is, i'm not sure but, i think the unrevoked forever patch is down. i tried to download and it downloaded a file called download and i'm not sure what kind of file it is.....do not remember the site ever doing that.


hey scotty would any unrevoked forever.zip work?

ive got it downloaded allready,so when we get to that step if we cant get a good download from the site someone can upload it for him.

I have tried these RUUs, but none of them have worked.
RUU_SuperSonic_GB_Sprint_WWE_4.24.651.1_Radio_2.15.00.05.02_NV_2.15_release_199233_signed
RUU_SuperSonic_GB_Sprint_WWE_4.53.651.1_Radio_2.15.00.0808_NV_2.15_release_209995_signed
RUU_SuperSonic_GB_Sprint_WWE_4.54.651.1_Radio_2.15.00.0808_NV_2.15_release_220182_signed
RUU_SuperSonic_GB_Sprint_WWE_4.67.651.3_Radio_2.15.00.12.19_NV_2.33_release_234563_signed

Do you have any other RUU sugestions?

Thanks!

with a bit of poking around,forever supports the following evo basebands:
1.36.00.04.02
1.39.00.04.26
2.05.00.06.10
2.15.00.07.21
2.15.00.07.28
2.15.00.09.01
2.15.00.11.19
so we just need to run an ruu that contains any of them.

looks like this one contains this one contains the last one:
AndroidRUU | The #1 source for Android RUU files

this one contains the one before:
AndroidRUU | The #1 source for Android RUU files

and a third for good luck :
AndroidRUU | The #1 source for Android RUU files

im not sure of the compatibility of the revolutionary hboot(wich is based on the newest for supersonic,the htcdev compatible one) with this older firmware,so i dont know if theres a chance the phone would boot or not.

but at any rate,in a nutshell:
-run one of those RUUs
-install a custom recovery
-use recovery to flash the forever patch

at this point,he should be radio s off,so he can use your sticky directions to remove the revolutionary hboot and run one of the RUUs again.

if we still are getting the boot failure,we can try and dd a boot image in while booted to recovery where adb should work,or we can track down and install the eng hboot,and see what fastboot oem commands are available there. the eng hboot may allow us to wipe or erase the corrupt boot image and allow the ruu to install one.

hope that makes sense

 

[neofitox2]

I'm downloading those RUUs and will let you know the results.

Thanks

 

[neofitox2]

I have tried and none of the 3 RUUs mentioned above worked with my EVO.

Should I throw it against the wall? :shot:

 

[ocnbrze]

I have tried and none of the 3 RUUs mentioned above worked with my EVO.

Should I throw it against the wall? :shot:

Are you getting the same error when trying them?

 

[scotty85]

I have tried and none of the 3 RUUs mentioned above worked with my EVO.

just to make sure were on the same page,we dont really expect the phone to boot after running any of them. the point here is to get you a real s off instead of the revolutionary hboot.

if the ruus ran as above,with success everywhere but boot,do a fastboot getvar all and verify that the baseband has changed to one of the above.

after that,install a recovery and we will scare up a "forever" download for you to flash

edit:
download unrevoked forever from here: http://dinc.does-it.net/Guide_Root_New_Hboot/unrevoked-forever.zip

flash that zip in recovery,just as you would a rom.

(some info on what youre doing here: http://unrevoked.com/rootwiki/doku.php/public/forever )

 

[neofitox2]

I ran the fastboot getvar all and apparently it did change the baseband (this is what I get)

(bootloader) version: 0.5
(bootloader) version-bootloader: 2.10.0001
(bootloader) version-baseband: 2.15.00.11.19
(bootloader) version-cpld: None
(bootloader) version-microp: 041f
(bootloader) version-main: 1.00.000.0
(bootloader) serialno: **mod removed**
(bootloader) imei: **mod removed**
(bootloader) product: supersonic
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PC3610000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3947mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-3b95cc40
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 1
all: Done!
finished. total time: 0.007s

Which Recovery do you recommend me to install?

Thanks

 

[Mikestony]

Just popping in here neofitox2
I removed your imei and serial # for security purposes. Those have no bearing on what Scotty needs
No worrires!

 

[ocnbrze]

amon ra is what i like, but that is up to you.

 

[scotty85]

I ran the fastboot getvar all and apparently it did change the baseband (this is what I get)

(bootloader) version: 0.5
(bootloader) version-bootloader: 2.10.0001
(bootloader) version-baseband: 2.15.00.11.19 <- compatible with forever patch
(bootloader) version-cpld: None
(bootloader) version-microp: 041f
(bootloader) version-main: 1.00.000.0
(bootloader) serialno: **mod removed**
(bootloader) imei: **mod removed**
(bootloader) product: supersonic
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PC3610000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3947mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-3b95cc40
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 1
all: Done!
finished. total time: 0.007s

Which Recovery do you recommend me to install?

Thanks

excellent! you have a compatible baseband,so now just install the recovery and flash the patch.

in the meantime,we will start searching for an eng hboot,fairly certain ive seen one for the evo.

also,i second the recomendation for amon recovery.

edit:
download the eng hboot from here:
http://forum.xda-developers.com/showthread.php?t=752832

the link is still good

 

[neofitox2]

I just tried to install the Recovey, but I'm getting this error:

C:\sdk\platform-tools>fastboot flash recovery recovery-ra-supersonic-4.3-smelkus-reloaded2.img
sending 'recovery' (4198 KB)...
OKAY [ 1.134s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 1.766s

Tried the fastboot oem unlock but didn't work.

Tried the fastboot oem boot the phone boot but it is in a loop with the HTC EVO 4G and the Sprint logo.

This is what i get in the Computer:

Q:\Tobon\Android\adt-bundle-windows-x86-20130219\sdk\platform-tools>fastboot oem boot
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8E07E510
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x27F05
(bootloader) TAG:hero panel = 0x0
(bootloader) TAG:engineerid = 0x0
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is not super CID
(bootloader) CID is SPCS_001
(bootloader) setting->cid::SPCS_001
(bootloader) serial number: XXXXXXXX
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =480
(bootloader) active commandline: board_supersonic.disable_uart3=0 board_s
(bootloader) upersonic.usb_h2w_sw=0 board_supersonic.disable_sdcard=0 dia
(bootloader) g.enabled=0 board_supersonic.debug_uart=0 smisize=0 userdata
(bootloader) _sel=0 androidboot.emmc=false androidboot.baseband=2.15.00.
(bootloader) 11.19 androidboot.cid=SPCS_001 androidboot.batt_poweron=die_
(bootloader) battery androidboot.carrier=COMMON androidboot.mid=PC3610000
(bootloader) androidboot.keycaps=qwerty androidboot.mode=normal androidb
(bootloader) oot.serialno=HT184HL07671 androidboot.bootloader=2.10.0001 n
(bootloader) o_console_suspend=1
(bootloader) aARM_Partion[0].name=wimax
(bootloader) aARM_Partion[1].name=misc
(bootloader) aARM_Partion[2].name=recovery
(bootloader) aARM_Partion[3].name=boot
(bootloader) aARM_Partion[4].name=system
(bootloader) aARM_Partion[5].name=cache
(bootloader) aARM_Partion[6].name=userdata
(bootloader) partition number=7
(bootloader) Valid partition num=7
(bootloader) Delay 99998(us) for dpram command before goto AMSS...
(bootloader) jump_to_kernel: machine_id(2433), tags_addr(0x20000100), ker
(bootloader) nel_addr(0x20008000)
(bootloader) -------------------hboot boot time:376621 msec
FAILED (status read failed (Too many links))
finished. total time: 6.897s

Thanks

 

[scotty85]

What happened to your revolutionary bootloader?

 

[ocnbrze]

What happened to your revolutionary bootloader?

yeah that is weird....hboot is now 2.10.

which ruu did you run?

 

[neofitox2]

I haven't run any other RUU different since I post the fastboot getvar all.

 

[ocnbrze]

I haven't run any other RUU different since I post the fastboot getvar all.

just curious but do you remember what the last ruu you tried?