Boot Loop - Bricked? :(

[igotsanevo4g]

Uh, i dont think thats possible.

Ill look into it when i get home.

 

[2CupsWithString]

You can grab the images off of the nandroid and flash them directly with fastboot. (should be able to, I never tried).

You'll have to be hboot v0.76 though as newer ones won't allow remote flashing like this.

 

[thanamesjames]

yea, actually i just tried it. it worked for recovery (though still in bootloop) and boot failed.

 

[igotsanevo4g]

^ WAIT? you can boot into recovery now?

 

[thanamesjames]

no sorry, haha, you got excited though! i meant my old recovery flashed properly under fastboot in command prompt.

I wish I could get into recovery!

 

[igotsanevo4g]

awe damn.

 

[2CupsWithString]

Can you try to get back to hboot .76 and flash recovery like three times in a row.

Just something I see from time to time that you can flash it once and use it but it doesn't seem to report back right (my example is in ROM Manager if you manually flash clockworkmod, sometimes rom manager reports the previous version is still there until you flash it again).

I'm just trying to think of different things here.

 

[thanamesjames]

Three times in a row using PC36IMG files? or flashboot commands?
If flashboot commands, do I reset each time, or just do it three times immediately in a row.

 

[2CupsWithString]

Three times in a row using PC36IMG files? or flashboot commands?
If flashboot commands, do I reset each time, or just do it three times immediately in a row.

Fastboot, in a row.

 

[thanamesjames]

haha, alright, I had someone tell me to RUU twice, so I'm gotta drop back down my hboot, haha

 

[thanamesjames]

no go

 

[2CupsWithString]

Alright, try:

fastboot -w
fastboot erase boot
fastboot erase recovery

Reboot your phone after that with fastboot reboot, it should jump right back in to hboot - I want to see if that does indeed happen or if it tries to load something, after that go back in to fastboot and get your boot.img from a good nandroid and type:

fastboot flash boot boot.img

And then after it's flashed type fastboot reboot and see if it takes longer to boot loop.

 

[thanamesjames]

After the erases, It went immediately back into fastboot, not hboot. It did it quickly.

After flashing boot.img, it actually was muchhh slower, and went into a boot loop, instead of fastboot.

 

[2CupsWithString]

After the erases, It went immediately back into fastboot, not hboot. It did it quickly.

After flashing boot.img, it actually was muchhh slower, and went into a boot loop, instead of fastboot.

Awesome, pull system out of the nandroid and:

(this will take some time)

fastboot flash system system.img

(edit)
then

fastboot reboot

and cross your fingers - this won't be a great working system and will have some problems if it even boots at all but we can go back to fastboot and re-flash userdata. I'm just hoping it loads up.

 

[thanamesjames]

ehhhh. edit. my bad, gotta learn how to read.

 

[igotsanevo4g]

whats your hw version btw ?

I have a clean nandroid you could pull the imgs out of if you'd like.

 

[thanamesjames]

I had such high hopes for this too.
Unfortunately it boot looped after the reboot. I grabbed a system.img from back in november... the first backup i made from before i did my root.

I'm unsure of my hw version is, my first line is
SUPERSONIC EVT2-3 ENG S-OFF

 

[2CupsWithString]

I had such high hopes for this too.
Unfortunately it boot looped after the reboot. I grabbed a system.img from back in november... the first backup i made from before i did my root.

I'm unsure of my hw version is, my first line is
SUPERSONIC EVT2-3 ENG S-OFF

You'll have to use the boot.img from that nandroid then as well.

 

[igotsanevo4g]

Try a more recent one that you made with the same hboot number, your partition size may be different?

 

[thanamesjames]

You'll have to use the boot.img from that nandroid then as well.

So just flash boot.img and then reboot? Or should i start over?