Root Infamous Evo Bootloop - A New Incarnation

[batvans46]

k fastboot boot recovery went through this time, but took me to the white htcEVO screen, sat there for a sec, then dark and d-d-d sound. again.

 

[batvans46]

you can try whatever recovery you wish,but id make sure to give amon a try. its an older recovery,but has few frills and basic functionality,making its memory footprint a lil smaller.

i thought you had to be s-off to load a custom recovery?

 

[Rxpert83]

i thought you had to be s-off to load a custom recovery?

Nope, just at least unlocked

 

[ocnbrze]

you can have recovery as long as you are unlocked.

edit: damn those pharmacy ninja's.....there so sneaky!!!!

 

[batvans46]

k. flashed amon using the boot amonrarecovery.img method, new symptom. it booted into the white htcEVO screen but isnt going dark like usual...

 

[Rxpert83]

I just joined this, but have we already tried RUu's

 

[batvans46]

yup

 

[scotty85]

I just joined this, but have we already tried RUu's

in every possible way to apply them,lol

-running .exe
-PC36IMG in hboot
-as an RUU from fastboot

k. flashed amon using the boot amonrarecovery.img method, new symptom. it booted into the white htcEVO screen but isnt going dark like usual...

just to make sure that we are on the same page,after you issued fastboot boot amonrarecovery.img did you get an output that looked like this?

downloading 'boot.img'... OKAY [  1.518s]
                       booting... OKAY [  0.005s]
finished. total time: 1.523s

give the phone a few seconds on the white htcEVO screen and then try adb devices and see if you get a response HTxxxxxxxxx recovery if you do you cant try adb reboot recovery. you can try that a couple times,waiting different lengths of time between each try.maybe it will start sometimes. if you dont get a response,you could still try the fastboot boot amonrarecovery.img command a few times and see if it changes anything.

as a last ditch effort,you can try booting your current boot image,and see if the phone starts. i dont want to get your hopes up too much,as if the phone fails to even boot a recovery,its not likely it will be able to boot the rom. but,we never know,right?

extract rom.zip(7 zip works fine for all older RUUs). take the boot image from it,and place it into the adb/fastboot folder.

use the boot command again,except boot the boot image:

fastboot boot boot.img

keep fingers crossed the the phone turns on. give it a good 20 minutes,as the first boot always takes longer. unfoortunately,since we have ruued,usb debug will not be running in this rom,so adb devices during trying to boot wont yield a response you can pull the battery and try the command a few times if you want.

hate to say it,but its starting to look like a physical hardware issue we wont be able to wiggle our way around

 

[batvans46]

ok so i feel dumb for not checking this before, but it looks like whenever its in one of those "d-d-d" sound states, it shows up under device manager as "qualcomm cdma technologies msm." i've scoured the net looking for drivers for this "device" but can't find anything...

 

[Granite1]

O man, thats bad. Last time I saw an OG evo with this problem, it was unrecoverable.

The LTE can be recovered from Qualcomm Download Mode while rooting, but I've never seen a recovery from this on the OG.

@ Scotty, this couldn't be recovered by sending it out to a Jtag service could it?

 

[ocnbrze]

yeah this does not sound good at all. sorry mn, but i agree with granite in that there is not much you can do at this point other then taking it in to get fixed.......my condolences

 

[scotty85]

ok so i feel dumb for not checking this before, but it looks like whenever its in one of those "d-d-d" sound states, it shows up under device manager as "qualcomm cdma technologies msm." i've scoured the net looking for drivers for this "device" but can't find anything...

yeah,ive never found them either. you find alot of those sites that want to sell you a driver finder that will find them for you but ive never flund an actual download for that mode,and i have no idea what might be possible with it.

@ Scotty, this couldn't be recovered by sending it out to a Jtag service could it?

i dont believe so... while its possible to use a jtag process to write older nand devices,doing so would assume that all hardware was fine,and just a (normally) unwriteable partition was corrupt. on an older mtd device,the only thing(that i can think of) that would keep the device from booting and be fixable via jtag is the bootloader,wich he is able to access... so i dont think its the issue.

you could always call or email josh at MobileTechVideos.COM and ask him what options there are.

 

[batvans46]

Its cool, as much as i hate to give up on a device, seems like this one is going back onto the shelf for when i find a craigslist evo with a busted lcd... maybe a charging port. the internal memory that such affected partitions are on is on the motherboard yeah? so that parts no good...

 

[scotty85]

Sounds like a good plan. Sorry we couldn't find a better solution