Yeah I think you need to clarify some things. First of all what recovery version where you using, and what partitions dud you format under them. Also try booting into download mode(volume down and power) and plug your phone into your computer. If a mobile drive gets mounted then your not bricked.
I have zero response from the phone. It will not boot into d/l mode nor recovery. Pressing any button/combination of buttons produces the same result- absolutely nothing, as if I were pressing the buttons with the battery pulled out.
Also why do you speak of the partition structure of the sdcard? It has nothing to do with the phone being bricked! The partition that contains the recovery and the importantant boot information is stored on the phones internal memory. It is the one that gets mounted as the mobile drive in download mode!
In my ignorance as an android noob and generally inexperienced with phone technology I pulled out my SD card, stuck it in a card reader and formatted it clean. Wiped all the partitions off it (of which I found many) and tried to reformat. I did it on a Mac initially and have subsequently used Windows and none of the formatting seems to make the SD card recognizable to the phone for something like attempting a DREAIMG-RC29 recovery.
I haven't been sure if the MOBILE partition was on the sdcard-ext or the internal memory. Sdcard-ext is the mount point for the external sd card according to the Android SDK reading I did. But I tried formatting the external as FAT32, EXT2 and EXT3 and found nothing worked. This is obvious to most of you I'm sure, but formatting the external SD isn't particularly useful or needed, yet it was only after I formatted the the card on the Mac that the phone would no longer boot into anything and effectively became bricked. So seemed like it is part of the equation somewhere for bootloader or something... not the case though?
For reference, I was partitioning mostly to meet the recommendations from here:
Android Simplicity: How-To #6: How to Partition your SDcard
Provide us with some concise details I'd you wanna have any hope of fixing your phone. If not good luck on your own as there is nothing we can do if we don't understand what you did!!
Been trying on my own. I went into QPST and discovered that it is only in Software Download that it finds anything related to a device being attached. No other module will load or read from the phone. So I spent lots of time looking for the right files to use to flash the phone from QPST-- they are .hex files or .qcn or some other such that I just cannot locate anywhere on the web or in the now very large directory of files I have downloaded of various stuff.
This link:
How to unpack and repack NB0 file - Android Wiki helped provide insight into what the different required files/filetypes are that QPST wants to flash out the phone. I have some but not all of the files needed.
So now I am on to fastboot. I'm following this thread:
[HOWTO] (moto-fastboot) Flash a build on an unlocked Atrix - xda-developers trying to figure out exactly what I should do to "./fastboot flash recovery recovery.img" or whatever such I should be trying. I don't know if I need to run "./fastboot oem unlock" first and have it connect/work, if I need to ensure the phone is rooted first, or neither or what ....
So that is where I am at.
As far as the steps I used to produce this fantastic result? I said, I formatted everything I could from CWM 5.xxxx. All the Davik, caches, data, system, etc. Where I think I really produced the bad result was when I went in and formatted the "sdcard" which I now understand to be the internal memory. I also formatted everything else. Upon reboot I could only get into download mode. That was when I had the bright idea to format the external SDcard as stated above. After that---- well, I have the brick I refer to. Functionless. Completely. Save for the fact that when it is attached via USB that USB drivers load it as QHSUSB_DLOAD or some variant. This is as it is recognized in windows under the COM port as I load it. I've tried loading every driver I could find into this device and could not really identify anything useful coming out of it- although I haven't completely ruled it out.
Under OSX, as I tried to fastboot it I was getting an error "ERROR- could not get pipe properties" and it would following up with <waiting for device> over and over... I switched to another USB port and the pipe property error went away but fastboot wouldn't flash or do anything.
So-- anybody have experience with this or another idea what to try?? I called VM and my particular case is peculiar. I bought the phone used. It is a first generation Triumph. The previous owner never activated the phone with VM and bought it from BestBuy. I recently activated it but less than 30 days ago. So, VM says I have to take it to BB to return it but of course it is past the return date at BB. VM says I have to wait until +30 days before they will do a replacement. I informed them about the "what if I bought it longer than 30 days yet only activated recently" and nothing they can/will do.
Thanks y'all (and I've written this post in as little prose as possible- hopefully it is comprehensible.)
