Root Boot Loop

[salty_bit]

I'm sure somebody else has had a documented similar problem, but I've followed every lead I thought was even possibly related and still have come up with nothing. For background, this phone has seen a lot of modification and this particular happening comes from the earpiece not working (I suspected it was software).

My Ally is stuck in a boot loop -- it cuts out in the middle of the Verizon animation and begins again. I can access the recovery menu (RA-aloha-v1.2.4) and through it adb, but I've formatted data, boot, cache, dalvik-cache and then flashed all of the following individually:

d7a550d683e54732bcb55eff24ada704  cwmr_3.0.1.0.zip
e2a609c66dd1c1047674ec869655912d  Recovery_Ace_v3.2.0.0.zip
23950bb3e134ba9a7cd6aa914b85df0a  recovery-clockwork-3.0.0.5-bravo.zip
ec86ca76aeffacf95a7266995fc9afe5  signed_ally_V8_stock.zip
ee5705d3c64b6428019fea4d5fe4223f  signed_clockwork_to_RA_aloha.zip
b5537d53c2d765a5342d3095cc388d63  signed_clockwork_to_Stock_Recovery.zip
66068832919cb6090247724a953ef757  Stock V6.zip
b3069b350626dd03671f84f0dd0d163d  velocity_0.2_release.zip

I'm noticing also that the adb shell doesn't list a /boot directory.

Can someone point me in the right direction? I just want a working phone.

 

[Valkerie]

Were you on Android 2.2 before you flashed any of those?

 

[salty_bit]

Sort of -- I remember the install would always fail, and prompt shortly thereafter.

 

[cr5315]

If you were on 2.2 when this started, flashing Velocity 0.2 is a bad idea. 2.1 roms do not work when you start on 2.2. I think your going to have to go back completely to stock and then re-root. You can use the unbrick guide that death2all110 posted, or you can go to the Ally IRC and get real time help on this. The link is in my sig.

 

[salty_bit]

Thanks so much for your help.

 

[scary alien]

Thread moved to the all-things-root sub-forum.

Cheers!

 

[bit_salty]

For closure, I was able to flash Frunisher (the cheesy one with Punisher boot animations, etc) -- that was the only one that worked.

As a side note, and just in case somebody else happens upon it, this whole thing came a about because I thought something software-side was causing problems with my earpiece (couldn't hear people in phone calls). This was not the case, and worked around it by buying a cheap $30 Bluetooth dongle. Oh well.