What i think happened: I was trying to push boot loader files into my Kindle Fire HD 7" and *whoops* forgot to unplug my phone from the USB cord where it was charging merrily away. Since then I have gotten it to turn on a small handful of times - the most recent was after a 3 day wait for the battery to discharge and then it decided to accept a charge, worked for around 20 hours and then locked up again. Since that point it has been unresponsive.
I'm thinking that these boot loader files may have overwritten primary-boot and possibly secondary-boot sectors and sometimes the secondary-boot backup partition catches, and sometimes it doesn't.
I know what you all are thinking, and the guys I'm deployed with tell me the same thing - send it in as an insurance claim and get a new one. Well screw that, especially if I can get it done myself. I've also read that this is a possible hard-brick ( i don't think so since I can get something from it, sometimes ) and in need of a RIFF box to get this done properly.
At our last port, I was in the XDA-DEV chat room on snoonet and someone mentioned that the aboot.img may be disfigured or completely screwed, but being in port, I was fairly drunk and didn't save the log from that chat like I should have, does this sound right?
Can anyone give me any guidance as to what is going on with my phone and how to fix it? I have a stock Samsung ROM image on the way out here shipped from the states, but that's about a week away, at least. Will this be enough to fix it? Is there anything I can do to get my phone back operational in the mean time?
Thanks in advance.