[EVO 4G Q&A, Help & Troubleshooting] achtagon:
Hi,

My EVO was happily rooted under 2.1 using the Fresh ROMs and adb commands since I got it, and I recently rushed into 2.2 and may have screwed myself. I know people throw around the term 'BRICK' but I'm worried I'm stuck until I either bring this to sprint (it's been RUUd to newest stock and doesn't work) or wait for people to better crack .93.

I'm a linux server admin and have experience with things like putting Linux on a PS3 and building Hackintoshes, so I'm real comfortable getting into bootloaders and fixing permissions and flashing stuff (even if the manufacturer frowns upon it :). But I think I'm stuck after letting the damn .93 enter the equation and getting USB disabled - here are the symptoms:

USB Debugging is dead so no ADB possible. Fastboot USB and Hboot USB works (but no flashing from there - 'REMOTE NOT ALLOWED' because of .93 and S-ON.) I've tried on Win7 64, XP, OSX, and Ubuntu and it worked before I broke it. I do have the SDK drivers loaded (so it shows as Android Bootloader in device manager during fastboot usb screen) but have also tried HTC Sync drivers. Yes, USB debugging is on and it's set to 'charge only'. The device manager shows 'Qualcom CDMA Device' three times. I can see 'uart disabled' in the fastboot oem boot so I'm quite sure it's been toggled off somehow.

The phone boots normally to a stock unrooted RUU of 2.2 and locks up after about a minute and restarts. So, anything I can try within android must be accomplished in this one minute, then it shuts down and reboots. I've tried turning off all services in a rush, and airplane mode to kill the radios and it won't stop it from crashing. I've stared at CatLogger set to error and nothing is major ... but it's not rooted at this point so i can't flash from within android, run ROM Manager, or run connectbot su to fix the USB. Everything works perfectly for this one minute - network, sd, etc.

So my options for getting into the phone are: PC36IMG.zip on SDCard through reader (fails unless hboot = .93, can't roll back), update.zip on SDCard (recovery can't be written), connectbot (non root, and only a minute at a time), and limited fastboot usb commands.

I've spent hours trying to flash anything with the above options and have failed.

The sequence that got me here was (stupid?):

When I got my 2.1 phone I did: geekfor.me/faq/how-to-root-your-evo-4g/

Then updated with new Fresh ROMS to the 2.2 pre-release. I flashed the radios too. Everything worked besides 4G and I was itching for an update ...

Then I tried to download the newest Stock Fresh Evo 3.2.0.0 and install it and did a total wipe of the system from the stock Bootloader trying to 'wipe first' - instead of a cache wipe from a custom recovery or factory reset in the OS. At this point I reinstalled an older PC36IMG.zip to be able to boot, but I lost USB and SDcard at this point.

So I then STUPIDLY got the Sprint 2.2 update through the phone - thinking it would fix the USB and SD card, and to see if the 4G was working in the stock 2.2, since it didn't work in the preview Fresh 2.2 rom. And I thought I could always roll back, or that there'd be some way out. (I fixed sd with fastboot oem enableqxdm 0, but the USB fix steps I found need root and connectbot)

Well, it put the damn .93 on. I would be fine if it was just stock for now since everything is working - but only for a minute! then reboot, reboot, reboot.

I've tried a few RUUs but can only apply the newest one successfully, (others fail because it's trying to apply .76 bootloader and fails with 'wrong bootloader') I've done the RUU a number of times and factory reset the hell out of everything.

Is anyone else having the reboot problem? Could it really be a hardware issue? Why is it rebooting?

Do I just have to wait for people to break the .93 with a new tactic?

Does anything below look out of place?

Here is my bootloader menu:

SUPERSONIC EVT2-2 SHIP S-ON

HBOOT-0.93.0000

MICROP-041F

TOUCH PANEL-ATMEL224_16ab

RADIO-2.15.00.07.28

July 23 2010, 16:41:47

Here is the fastboot OEM boot output:

INFOTAG:Ramdisk OK

INFOTAG:smi ok, size = 0

INFOTAG:hwid 0x0

INFOTAG:skuid 0x23301

INFOTAG:hero panel = 0x1

INFOTAG:engineerid = 0x0

INFOMCP dual-die

INFOMCP dual-die

INFOTAG:mono-die = 0x0

INFODevice CID is not super CID

INFOCID is SPCS_001

INFOsetting->cid::SPCS_001

INFOserial number: HT05SHL14545

INFOcommandline from head: no_console_suspend=1

INFOcommand line length =480

INFOactive commandline: board_supersonic.disable_uart3=1 board_s

INFOupersonic.usb_h2w_sw=1 board_supersonic.disable_sdcard=0 dia

INFOg.enabled=0 board_supersonic.debug_uart=0 smisize=0 userdata

INFO_sel=0 androidboot.emmc=false androidboot.baseband=2.15.00.

INFO07.28 androidboot.cid=SPCS_001 androidboot.batt_poweron=die_

INFObattery androidboot.carrier=COMMON androidboot.mid=PC3610000

INFO androidboot.keycaps=qwerty androidboot.mode=normal androidb

INFOoot.serialno=HT05SHL14545 androidboot.bootloader=0.93.0000 n

INFOo_console_suspend=1

INFOaARM_Partion[0].name=wimax

INFOaARM_Partion[1].name=misc

INFOaARM_Partion[2].name=recovery

INFOaARM_Partion[3].name=boot

INFOaARM_Partion[4].name=system

INFOaARM_Partion[5].name=cache

INFOaARM_Partion[6].name=userdata

INFOpartition number=7

INFOValid partition num=7

INFOmpu_nand_acpu_rw D3E 2000

INFODelay 99998(us) for dpram command before goto AMSS...

INFOjump_to_kernel: machine_id(2433), tags_addr(0x20000100), ker

INFOnel_addr(0x20008000)

INFO-------------------hboot boot time:326240 msec

FAILED (status read failed (Too many links))

finished. total time: 5.127s

THANKS!!!! I'd love to get my phone back!