|
||||
Re: Let the Flaming Begin!! But It is bad.
I was going to say to do a bunch of stuff, but you already did everything I had in mind.
And you DEFINITELY have done your work. Its seems very strange that a BSOD would cause your phone to poop. Do you have insurance? I'm not one to condone fraud, but perhaps you could... 'lose' it, and pay $50 for a new one? If you were flashing, I'm assuming you've already backed up your contacts, files etc. to your SD card.
__________________
|
|
||||
Re: Let the Flaming Begin!! But It is bad.
Yeah, I keep a constant revolving backup of all contacts and messages. because im flashing this thing about once every two weeks trying out new things...
What really gets my goat is, that this is what I do for a living right now.. I work for a local wireless Store and my job is to carrier/flash phones and repair phones.. and when I say carrier/flash, im not talking about just a prl copy, I mean seem edits, editing the NV and so on to get mms and wap/brew etc working.. So this isnt my first rodeo, but for the life of me I cant figure out how to get out of this one... and there is a lot of info on here and xda, but nobody seems to be in the exact prediciment that im in... If I only knew a way for format the phone, and find a way to reflash the original bootloader, I could probably load the original stock oem on this thing and call it done... but without being able to get phone to boot through the radio error and go into the o/s i cant use activesync so Im stuck with oli2.4 Thanx for the reply though..... P.s. I do have insurance,, and I dont think it would be fraud if I called them and told them I pooched the phone... thats what insurance is for... I would want to be honest.. But nonetheless, I have a brand new Sprint Mogul at work that just came in to sell, and what I will probably do , is call insurance on my phone, get a new one from alltel, then keep it in the box in the closet, and flash the new sprint mogul over to alltel and do an esn swap to it through alltel and use it,, that way I have a backup... Last edited by midiology; 03-11-2008 at 09:59 AM. |
|
||||
Re: Let the Flaming Begin!! But It is bad.
Well,, just wanted to update... this my friend is what you could possibly document at the first truly BRICKED titan...
found a thread where 1... count them 1 other person had the same symptoms that i had over at xda,, and this person was able to pull it out and get the os to boot,,, so I proceeded to follow the directions, and halfway through the process the phone went black, my computer made the little hardware disconnect sound... my hind end puckered up and bam,, dead as a doorknob.... wouldnt boot, wouldnt even turn on,,, Pulled the battery,, replaced the battery,, plugged it into the wall,, and nothing ,, finally got a steady red light,, so I thought that maybe the battery was too low to give amber light/boot left it plugged in for a few hours even though when i started the process the phone was fully charged,,,, never changed.... I plugged it back into the computer and the computer found the qualcomm chipset,, modem/diag ports I decided to run qpst to poke around and see what was going on,, qpst reported the connected device as being "qcd-xxx(download)" wheras normally it would report it as the actual qualcomm msm chip,, nontheless the software was unable to communicate with device as there was no phone present... after some research (from a russian site mind you) qcd-xxx(download) means that in most cases bad sectors of memory had been written and was basically corrupted to the point that it couldnt be read at all... similar to the way you loose all the information on a hard disk when the boot sector gets pooched,, so I opened up one of my cdma proggies and dumped the nv and flash,, when viewing them with my hex editor,, it was basically all 0's ,, and big chunks of emptiness with the word error splashed throughout... so basically its dead,, I even tried running raw commands to the phone, and tried using qxdm to atleast try to peek and poke a little, and the computer sees the communications port/modem,, and the modem has access to the nv but either it cant read the nv properly, or the nv is totally wasted.. no bootstrap, nothing... here is where we move into the brady bunch lesson learned pep talk... 1. I am a very seasoned and certified network engineer and computer technician. 2. I currently work for a wireless company repairing and carrier/flashing phones 3. I have done probably more rom tweaking and updating on my phones than I have kissed my wife in the last few years and yet its dead,,, dead i tell you... lol so the moral of the story is ,,, If i can screw it up,,, anybody can screw it up, so please be careful what you do,, think it through, read everything you can before you do it,, that dont mean just read the instructions someone posted then run off and flash it... that means read the next 3 to 4 pages then do a search for more pages.. because you want to see if anybody else had issues before you dive right in,,, backup,, backup,, backup,, get qpst if you have to and back up all your settings with it,, then use something to back up your pim etc,,, and for Gods sake have a game plan, know all the basics of what your doing.. make sure your battery is over 50% charged,, and the computer that your going to be flashing from needs to be clean, virus free, and STABLE. The computer problem is what started all this for me in the first place.. But all is well,,, I have 2 more just like it at the shop.. brand new in the box,, and I get to keep one for myself if i want and use the other one as a company phone... what a kind boss i have.. Plus im going bite the bullet,, and call insurance tell them truthfully that I screwed up the phone, and pay the deduct and get another one for a backup... Last edited by midiology; 03-11-2008 at 11:41 PM. |
|
||||
Re: Let the Flaming Begin!! But It is bad.
There is an "I'm desperate" way to write to the phone over at xda. Its through mtty.exe. I used to be very good at it, but do not remember anymore. you can manually install an os file, tell the phone in which sectors to store it, everything. BUT, you need to be able to connect to the PC. I know the battery light came on...if you can get Windows to make that connect sound when you plug it in it COULD work
__________________
|
|
||||
Re: Let the Flaming Begin!! But It is bad.
not trying to be the bearer of bad news, but if you let sprint know you messed up the phone by trying to flash a rom or trying to upload some kind of new software, it WON'T be covered in the insurance.. if we do anything like that with our phone it completely voids the insurance policy and they won't replace it, you would be better off "losing it"
__________________
i hate idiots... seriously
samsung 640A --> motorola Q --> sprint touch --> now doin it big with the touch pro... oh so sexy lol |
|
||||
Re: Let the Flaming Begin!! But It is bad.
Quote:
|
|
||||
Re: Let the Flaming Begin!! But It is bad.
You know whats really cool in a situation like this?
if you cut a usb cable and plug it into your phone, then touch 2 of the wires to a 12 volt battery,, then put the phone in the microwave for 3 seconds.... this successfully pops the rectifying diode that protects the phone from voltage spikes and reverse polarity,,, thus killing any abillity to connect to the phone ever again,, and the microwave causes enough electromagnetic fluctuations to fry/garble the eeprom/nvram thus getting rid of any option to jtag to the phone through service solder pads to read memory... tada Last edited by midiology; 04-06-2008 at 10:40 AM. |
|
||||
Re: Let the Flaming Begin!! But It is bad.
Quote:
|
|
||||
Re: Let the Flaming Begin!! But It is bad.
This info should probably be stickied for those who need to return a bricked / semibricked phone. I've already copied and saved to my desktop. Thanks Midiology. I hope I never have to use it but you never know....
|
|
|
|