elderlypunk
New Member
- Joined
- Apr 23, 2011
- Messages
- 25
- Reaction score
- 0
Hi,
The title says it all... I'm pretty ept with tech and droid but I absolutely fumbled and dropped my poor trusty OG droid into a tub... (Trying to show my wife some dumb funny video I found... doh...)
Anyhow, I was running (quite snappily) LGB 1.6 and things were going well. The dunking was lightning-quick... I obviously fumbled, but instantly freaked out and snatched the phone out, yanked the battery, dried if off and threw it in a bag of rice (I know, lame...) overnight... The next day I got on the forums and saw the "drying done right" amazing tut... I have done all that: alcohol, silica, air, etc.... But now I may be at the end....
After a week of treatments, I powered her up and got the "Bootloader 2c.6c" ready-to-program message... I thought that was a good sign and tried to use RSD Lite 4.9 with brandy new moto drivers from the motorola website (on my xp laptop) to try and flash back to something salvagable and get going again... No dice... No matter what I do RSD conks out at "Switching to BP pass through mode" and the AP and BP Motorola flash devices dissapear at that exact moment. RSD Lite shows fail due to the BP passthrough problem, but the phone still thinks it is updating... For way over an hour... The only thing I can do is a batt pull... That gives me the "corrupt code" bootloader error, and no access to recovery...
I can flash SPRecovery onto the poor beast, and can use that to restore to clockworkmod, but no matter how I try to install my nandroid backup (or other roms) which all appear successful, I keep ending up with "Bootloader 2c.6c" ready-to-go when I try to boot.
I saw another post saying that a similar problem was because bootloader 2c.6c was out of date and that 2c.7c is needed, but the "9046f5a3ec09.signed-voles-ota-45394.zip" which was recommended throws an error about "build.date" being less than a given integer when I try to install it.
Basically almost all the "update.zip" stock Verizon stuff I try to install gives a build-date error in SPRecovery and Clockworkmod, and everything except "recovery-only" type SBFs die in RSD with "BP pass through mode" errors".
At this point I assume I cooked something but fierce in my poor phone, but since I have no insurance my only options are: 1. ["What, Verizon store people? The water indicator is red? I have no idea?! Hurr Huur! I need another phone! *pray* ] or 2. [ buying an old droid on the inter-tubes]; or 3. [fix it (lol, I know...)]
I figured I would solicit advice, or ideas, or prayers that the wizened D1 community might have... Any and all is appreciated. My lame last-ditch hope is the "old bootloader" thing I mentioned, but I do not have much hope, or any idea of how to fix that.... If anything, a theory about what part of my poor D1 I fried would be entertaining and appreciated... I figure the "BP flash" thing has something to do with the baseband, but what does a dum-dum Droid-drowner know? Obviously not much... Anyways, any comments are appreciated... Thank you!
The title says it all... I'm pretty ept with tech and droid but I absolutely fumbled and dropped my poor trusty OG droid into a tub... (Trying to show my wife some dumb funny video I found... doh...)
Anyhow, I was running (quite snappily) LGB 1.6 and things were going well. The dunking was lightning-quick... I obviously fumbled, but instantly freaked out and snatched the phone out, yanked the battery, dried if off and threw it in a bag of rice (I know, lame...) overnight... The next day I got on the forums and saw the "drying done right" amazing tut... I have done all that: alcohol, silica, air, etc.... But now I may be at the end....
After a week of treatments, I powered her up and got the "Bootloader 2c.6c" ready-to-program message... I thought that was a good sign and tried to use RSD Lite 4.9 with brandy new moto drivers from the motorola website (on my xp laptop) to try and flash back to something salvagable and get going again... No dice... No matter what I do RSD conks out at "Switching to BP pass through mode" and the AP and BP Motorola flash devices dissapear at that exact moment. RSD Lite shows fail due to the BP passthrough problem, but the phone still thinks it is updating... For way over an hour... The only thing I can do is a batt pull... That gives me the "corrupt code" bootloader error, and no access to recovery...
I can flash SPRecovery onto the poor beast, and can use that to restore to clockworkmod, but no matter how I try to install my nandroid backup (or other roms) which all appear successful, I keep ending up with "Bootloader 2c.6c" ready-to-go when I try to boot.
I saw another post saying that a similar problem was because bootloader 2c.6c was out of date and that 2c.7c is needed, but the "9046f5a3ec09.signed-voles-ota-45394.zip" which was recommended throws an error about "build.date" being less than a given integer when I try to install it.
Basically almost all the "update.zip" stock Verizon stuff I try to install gives a build-date error in SPRecovery and Clockworkmod, and everything except "recovery-only" type SBFs die in RSD with "BP pass through mode" errors".
At this point I assume I cooked something but fierce in my poor phone, but since I have no insurance my only options are: 1. ["What, Verizon store people? The water indicator is red? I have no idea?! Hurr Huur! I need another phone! *pray* ] or 2. [ buying an old droid on the inter-tubes]; or 3. [fix it (lol, I know...)]
I figured I would solicit advice, or ideas, or prayers that the wizened D1 community might have... Any and all is appreciated. My lame last-ditch hope is the "old bootloader" thing I mentioned, but I do not have much hope, or any idea of how to fix that.... If anything, a theory about what part of my poor D1 I fried would be entertaining and appreciated... I figure the "BP flash" thing has something to do with the baseband, but what does a dum-dum Droid-drowner know? Obviously not much... Anyways, any comments are appreciated... Thank you!