[Q] Help With Motorola Droid Milestone X on C Spire - Bricked - Droid X General

I bricked my phone by using the wrong SBF. Like a DA, I didn't pay attn and used a SBF for verizon. However, my carrier is C Spire.
I am stuck at this:
Bootloader
30.04
Err: A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Can anyone point me to the correct SBF for C Spire to resolve this? Any help is much appreciated.

You're going to have to take it back to c spire and do a warranty return or you can send it to Motorola and they'll send you a new one back unless you're phone came with android version 2.2. If it came with 2.3.5 there's nothing you can do. Try this sbf file if it came with 2.2 http://www.filesonic.com/file/1301534444/SHADO_X6_3.2.6_SHADOW_BP_C_02.06.00R_AP_BP_Flex_21_signed_secure_cell_south_1ff_P3_USERBLD.sbf.gz

Thanks. I thought I may have to do the warranty exchange.
The link you attached is not working. Can you re-post it?
Again Thanks

jamcnew said:
Thanks. I thought I may have to do the warranty exchange.
The link you attached is not working. Can you re-post it?
Again Thanks
Click to expand...
Click to collapse
none of the sbf files would work for me, i was preloaded with 2.2. every time it resulted in the above referenced information exactly. there has to be a way to do it. i wish that i had a spare milestone x that i could mess with for testing. but after bricking 2 phones i am not willing to try it with my personal phone anymore.
edit: i can't remember, can you get to recovery?

ngholson said:
none of the sbf files would work for me, i was preloaded with 2.2. every time it resulted in the above referenced information exactly. there has to be a way to do it. i wish that i had a spare milestone x that i could mess with for testing. but after bricking 2 phones i am not willing to try it with my personal phone anymore.
edit: i can't remember, can you get to recovery?
Click to expand...
Click to collapse
No, I can't get beyond the Boot loader screen.

jamcnew said:
No, I can't get beyond the Boot loader screen.
Click to expand...
Click to collapse
my advice, before admitting defeat and taking it in for warranty, i would try every damn sbf i could find and use every method you can find. whats the worst that will happen? you brick it? too late. if you can get it to boot again somehow there is hope. try the same method over and over again. keep trying everything you can. THEN report back here and let the rest of us know =D

I've been working on this since Friday. The only sbf I've come across for C Spire is SHADO_X6_3.2.6_SHADOW_BP_C_02.06.00R_AP_BP_Flex_21_signed_secure_cell_south_1ff_P3_USERBLD.sbf.gz
I've yanked the battery, tried every imaginable button combo but that damned thing is stubborn. I'll probably go and do a warranty exchange later in the afternoon today. But if anyone here can point me to another sbf for C Spire, I'll try it out before I take it in. The one above is the only one I've been able to find.
I guess being on a small regional carrier makes it a little harder to get these things.

Thanks for the responses. I've warranty exchanged it now.
The replacement is on 2.2.2. Should I leave it alone or get the OTA update? I would like to put Cyanogenmod 7.1 on it.

Leave it alone. You can't run cyanogenmod nightlys on 2.3 because the nightlys are using froyo. If you do update you'll have to find the RC of cyanogenmod to put on it because it uses 2.3.7

Related

DX Completely Bricked, SBF Wont Help

OK, so i SBF'ed to 2.1, pulled the battery when it was done, then applied the OTA update to 2.2. Worked fine, then i rooted, but was having problems with the market. All apps showed up, but i had this huge list of items waiting to be downloaded and it didnt budge for hours. So i manually downloaded DX Bootstrapper from the market and tried to install the Tranquility rom. I didnt mount the system the first time i tried to install the Tranquility rom so i went back to do it, but this time i did a factory reset, and wiped the cache, then mounted the system and installed the zip. Then i was stuck on an Endless loop of the Tranquility logo. Attempted an SBF restore back to 2.1, and this time it just failed. Now the phone only turns on to the programming screen and i get this message:
Bootloader
30.03
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Transfer Mode:
USB
Should i just go back to Verizon, not sure if they have this in stock, and not sure what questions they will raise when they see this screen.
Well according to a birdman twitter post:
_mrbirdman_
do not flash back to 2.1 sbf after 2.2 0ta, keys/signature check has changed, if you go to 2.2OTA say goodbye to 2.1 forever....
and then he proceeded to say...
_mrbirdman_
Please retweet, everyones about to wake up! DO NOT DOWNGRADE TO 2.1 SBF FROM THE 2.2 OTA, YOU WILL BE BRICKED! UNTILL WE GET A 2.2 SBF LEAK
So until they leak a 2.2 SBF I don't think anything you can do. =(
They've got a thread over at droidforums with a number of people w/ the same problems too.
I got the same problem Now waiting for leaked 2.2 SBF :|
wow, im screwed.
if i tell verizon that i performed an SBF, will they refuse to replace my phone since i took it upon myself to try to service my phone on my own?
GoldenCyn said:
if i tell verizon that i performed an SBF, will they refuse to replace my phone since i took it upon myself to try to service my phone on my own?
Click to expand...
Click to collapse
i would tell them you were doing the ota it failed then just play dumb. It almost always works.
now the problem is that there are none in stock so im either gonna have to wait for a 2.2 SBF, or a replacement from verizon (and only god knows how long that will take).
I can't believe Motorola. For a company that is just barely getting their feet back on the ground after years of crappy phones - they sure not how to stick it to the consumer. I know we are just small percentage, BUT THAT'S THE POINT. Leaving it unlocked (aka no eFuse, etc.) would not really effect them much.
went to the store today, and they ordered a phone for me and it will be at my house tomorrow before 3pm by fedex. yay!
Even worse...p3droid warned that tranquility was meant to be applied over deodexed systems and the ota is not deodexed...yet.
Sent from my DROIDX using XDA App
GoldenCyn said:
went to the store today, and they ordered a phone for me and it will be at my house tomorrow before 3pm by fedex. yay!
Click to expand...
Click to collapse
That's kind of crazy when you think about it....intentionally brick your phone = get a new (though probably refurbished) phone.
I suppose it would be just about impossible for verizon to determine if the phone was bricked from their update or someone that tried to sbf but gone wrong.
Sent from my DROIDX using XDA App
hello first sorry my english,now let me see if i understaood....i was affreasid about updarte to oficial froyo ota....i am using a leaked froyo with some theme...and deleted some stock apps with root explorer...now my question is if i flash my droid with sbf file and gop back to stock 2.1 and wipe data and everything start over you know....than i upgrade to ota froyo....in this step i will be good??? with no bricked phone???? now my second question can i root this ota...and my last question is it worth since i alrady am in froyo with root with theme??? thanks i hope u undertand my englis hahaha bye and thanks in advance...
denpad2010 said:
hello first sorry my english,now let me see if i understaood....i was affreasid about updarte to oficial froyo ota....i am using a leaked froyo with some theme...and deleted some stock apps with root explorer...now my question is if i flash my droid with sbf file and gop back to stock 2.1 and wipe data and everything start over you know....than i upgrade to ota froyo....in this step i will be good??? with no bricked phone???? now my second question can i root this ota...and my last question is it worth since i alrady am in froyo with root with theme??? thanks i hope u undertand my englis hahaha bye and thanks in advance...
Click to expand...
Click to collapse
Yeah, that's the way to do it. sbf to 2.1 > ota > root.
But the only thinig I see that makes it worth it is if you have bad reception on your phone. OTA has new baseband version, which might help. Other than that, I don't really see any advantages.
As always, modder beware
Personally, I think Motorola will drop the anal attitude of locking down hardware in due time. Probably getting significant downplay from it. The number of people bricking the phones might be higher than other types? I don't know. Of course, only time will tell.
As for the OTAU. It's nice and buttery for an official release imo.
meshdub said:
Yeah, that's the way to do it. sbf to 2.1 > ota > root.
But the only thinig I see that makes it worth it is if you have bad reception on your phone. OTA has new baseband version, which might help. Other than that, I don't really see any advantages.
Click to expand...
Click to collapse
Ok thanks I think I stay with my leaked froyo
You are the reason Motorola has chosen to lock these devices down. It's awful that you bricked your phone through impatience, carelessness, or imprudence, but you shouldn't expect a free replacement because you couldn't follow directions or misunderstood them. These are probably low on stock because of all the consumers like you who did this. When you think about it, you take the one you initially bought out of circulation and then the replacement which you feel that you are owed. Maybe Motorola made enough, but since you bricked yours, another customer has to wait a week longer to get their first one. Thanks for that. If you are going to attempt these modifications you need to make sure you can handle it or have deep pockets.
Motorola locks these phones down for one reason "Verizon" or whatever carrier the phone is on. Motorola doesn't care if we are root or not but if Verizon says "jump" they say "how high". the better they lock it down the more the carrier likes them.
if we have root and can do things like get free wifi tether Motorola doesn't care they have already sold the phone but Verizon does because it takes from their pockets.
not Moto's fault.
iDroidNow said:
Motorola locks these phones down for one reason "Verizon" or whatever carrier the phone is on. Motorola doesn't care if we are root or not but if Verizon says "jump" they say "how high". the better they lock it down the more the carrier likes them.
if we have root and can do things like get free wifi tether Motorola doesn't care they have already sold the phone but Verizon does because it takes from their pockets.
not Moto's fault.
Click to expand...
Click to collapse
This not true, all I'm hearing is fanboyism. What about the Backflip or the Cliq? If you root the Backflip or the Cliq you will lose your manufacturer's warranty not the carrier's warranty. It Motorola's fault not anyone else. Even on the Motorola website they call it illegal when talking about rooting the Cliq, and rooting Android in general. You will your manufacturer's warranty if you root a Motorola Android even if it's on, Verizon, At&t, and or T-Mobile. The carrier's have nothing to do with this.

Bricked DX-Bootloader Error

Has anyone ever seen the following:
Bootloader
30.04
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Please let me know.
dude.... read up on it. welcome to the world of root... check our My Droid World for step by step instructions on how to fix..
Ya, you probably used the wrong SBF. 30.04 bootloader needs 2.3.320 full SBF and 2.3.340 patches. All at my Droid world
You have bricked your phone beyond repair. Not even verizon can fix it. If you're still covered under warranty, you could take it in and they'd just give you a new one. It worked for me.
Sent from my DROIDX using XDA App
I had this same problem. You can fix this with RSD Lite4.8 and redownloading your drivers. Just read thru the forums for instructions. I believe its a TBH file...
gzsmooth said:
I had this same problem. You can fix this with RSD Lite4.8 and redownloading your drivers. Just read thru the forums for instructions. I believe its a TBH file...
Click to expand...
Click to collapse
can u tell me more ive been bricked the same way for over a week... diff err code... tried flashing every sbf i could find and nothing.. can u tell me where to find those step by step directions and the right sbf files .... than you
let me do some digging around for ya
thanks i appreciate it ... god dam if u could find something to get me up and running again it would be so appreciated... can only find zip files and there no good to me at trhis time...
Since Im a new member I cant post a link to another forum. But if you can PM me Ill give you the link to step by step instructions
athack...
Shoot me your email address and I will send over the files. It took me a while of trying different sbf's but i found the right one.
Go to Droid Forums and look up "team black hat does it again" in forum search. go to that and go to 2nd page, look at maderschramm and he has a link for step by step instructions. Hope this helps. Im just a noob myself
thanjks email is [email protected]
god i hope this works... believe me ive been up nights flashing trying all diff things.. if u guys could helom it would be fantastic
Jmoney47 said:
You have bricked your phone beyond repair. Not even verizon can fix it. If you're still covered under warranty, you could take it in and they'd just give you a new one. It worked for me.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
It's people like you that keep our boot loaders locked. TBH has had .320 full and .340
system only sbf files posted for quite some time. If people would spend twenty minutes on google rather than returning phones maybe, just maybe motorola would ease up on the lock down. Know the risks and solutions before you root. More importantly own your mistakes.
I did do google search you idiot. This happened to me before the sbf I needed was released so I just got another phone
Jmoney47 said:
I did do google search you idiot. This happened to me before the sbf I needed was released so I just got another phone
Click to expand...
Click to collapse
You posted this extremely poor suggestion TODAY for a person having the issue TODAY. Maybe silence or the now available sbf solutions would have been better. Sorry I didn't gleen the fact yours was months ago...my apologies.
yes I think you tried to load the wrong file, explain what you are trying to do.
Droid-Xer said:
Ya, you probably used the wrong SBF. 30.04 bootloader needs 2.3.320 full SBF and 2.3.340 patches. All at my Droid world
Click to expand...
Click to collapse
He is using the wrong file, I've done this before same error. simple fix!
athack said:
thanks i appreciate it ... god dam if u could find something to get me up and running again it would be so appreciated... can only find zip files and there no good to me at trhis time...
Click to expand...
Click to collapse
With that kind of talk I hope your DX is beyond repair. Grow up and wash your mouth out. Very offensive language there.
wow, you al a little cranky! lol...
Droid-Xer said:
Ya, you probably used the wrong SBF. 30.04 bootloader needs 2.3.320 full SBF and 2.3.340 patches. All at my Droid world
Click to expand...
Click to collapse
This is the right answer, it happened to me as well. Just download the correct sbf and start the process again. Problem solved !

bricked? I need some help

Hi i just recently bought a motorola droid x. It had 2.1 android on it. So i uploaded the 2.2 spl file thorugh rsdlite. I just found out the bootloader version is 12.03. Now i tried flashing 2.1 and 2.2 both. after it says manually restart the phone. i restart it and it gets stuck on motorola screen. i tried clearing cache and factory reset it keeps getting stuck at the motorola screen. can somone please help me out here :/. Please help asap
Not sure about the bootloader as 12.03 . When I had 2.1 the bootloader was 30.01, then it changed as updates for 2.2 and finally 2.2.1 . Now the bootloader is 30.04 .
Do a little more research before flashing this, but the newest official built for a SBF file is 2.3.340. You can find it by google. This will change your bootloader to 30.04 and bring you up to date.
Good luck.
What OS are you using?
+1 on the bootloader. That is an odd one, unless that phone didn't originate in the U.S. I think the chinese x had a bootloader of 80.something.
I would start here however:
http://1kds.net/SBF-Page.php
Sent from my DROIDX
Well the battery died while i was trying to run it again. And it wont charge so i just used the splice wire trick. Ill get back to u guys on tht one., either way i tried googling the bL but nothing came up
Sent from my HTC Glacier using XDA App
Well upon further research i found out it was a preproduction droid x :/... i can not find the sbf for it anywhere. Can anyone please help me with this? I'd really appreciate it
bump ^ anyone able to help regarding this please?
are you using the full sbf? not system only sbf
I am not positive, but you should still be able to use the 2.3.340 full sbf to get up to date. You just can't use an sbf to go backwards.
Sent from my DROIDX
im downloading the files right now, but i dont think the boot loader gets updated when i try i tried once already but its worth another shot or as many as it takes :/
Full sbf didnt work its a pre-production phone
Sent from my HTC Glacier using XDA App
god i hate this 5 minute anti spam rule...

Alltel milestone x

Looking for the sbf for this in case of needing to go stock would really appreciate some help
Sent from my DROIDX using Tapatalk
mikeew83 said:
Looking for the sbf for this in case of needing to go stock would really appreciate some help
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Here is your link
SBF flash for Alltel MB809 - Milestone X
SHADO_X6_3.1.39_SHADOW_BP_C_02.06.00R_AP_BP_Flex_20_signed_secure_alltel_1ff_P3_USERBLD.sbf.gz
http://www.fileserve.com/file/sAXdN...20_signed_secure_alltel_1ff_P3_USERBLD.sbf.gz
Compression MD5 - 8E155E9189BE6E619CB2E46C7718BF1E
SBF MD5 - 9C67A33735D0ED84155034FB36797C83
holy crap! you don't know how long I have been waiting for this and I don't think it would ever come!!! how did you get this!?
Ty so much is this tested
Sent from my DROIDX using Tapatalk
yes it does work but it changes the build number to AWCC which I have no idea what that means, the build I had on it before was RETAIL
EDIT:
Just realized that this is for the AWCC Alltel, unfortunately for me I am on the alltel which Is still being switched to VERIZON. Phone still works though.
ive tried this an i just get error when flashing
krause11 said:
ive tried this an i just get error when flashing
Click to expand...
Click to collapse
it would help to know what error. lol
Milestone SBF on Droid X
I have a rooted Droid X that I flashed to alltel's network, however certian things like 3G and MMS were not working so I thought I would try to flash the alltel SBF to the phone and it worked! Kinda...it just isn't booting...I think it just needs to be wiped and SBF flashed again but I'm not sure. Either way now I'm stuck with a phone that I can't boot. Any ideas?
I figured it out...just needed to get into recovery by booting with home button and pressing the search button and wiping...after that I did another wipe and now everything is working perfectly, I think...still have to check the MMS but 3G is working like a champ!
just wanted to leave some important info concerning "STANDALONE GPS"
on my MB810`s i am not activated and have the BLUE TRIANGLE in notification bar with my stock OTA FROYO 2.2.340 or my OTA GB 4.5.596 on both my DX`s
you can not get STANDALONE GPS working if you have VZW and no activation!!!
i flashed to this alltel SBF from above and i have STANDALONE GPS and alot less bloatware from verizon
so we are running android 2.2.1....
is there no GB for this MB809?
i know this is an old thread but i know google tends to lead people to this thread so i needed to post. found out today alltel updated their activation number and therfor or atleast in my area this sbf will not let my activate my phone due to the built in old one. if anyone has any solutions please post it even if this thread is old. im also active in the droidxforums i know many people are eventually going to run into this problem as well.
thanks
thore022 said:
i know this is an old thread but i know google tends to lead people to this thread so i needed to post. found out today alltel updated their activation number and therfor or atleast in my area this sbf will not let my activate my phone due to the built in old one. if anyone has any solutions please post it even if this thread is old. im also active in the droidxforums i know many people are eventually going to run into this problem as well.
thanks
Click to expand...
Click to collapse
what change? what the new way?
No, there hasn't been a Gingerbread release for the Milestone X that the regional carriers use. Hopefully it'll come.
So what's a guy supposed to do to get a DroidX to work on Alltel?
Just flash the Alltel SBF and everything will work just fine. Make sure you don't try to SBF back to 2.2 once you get the 2.3.5 update or it will brick your phone.
Anyone know is there is a Verizon software version that will also leave a brick if you try to SBF to Alltel? I have an X that someone wants me to flash but i'm scared to screw their phone up. It has the 2.3.3 version.
please help need milestone x altell sbf file most of the links are dead.
rob151200 said:
please help need milestone x altell sbf file most of the links are dead.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=22450891&postcount=21

[Q] 2.3.4 sbf for D2 or R2D2

Hello,
I bricked my phone trying to downgrade from the 2.3.4 update to my R2D2. (I knew better, but what can I say?) I currently need a stock Verizon 2.3.4 sbf for either Droid 2 or (preferrably) the R2D2 to flash back to. I have a spare phone I will run to my office tomorrow to use for now, but I really want to unbrick by beloved R2D2...
The official ROMI'm looking for is 4.5.622.A957.Verizon.en.US
****SOLUTION POSTED AT THE END*****
The sbf has been leaked, and is available:
Here:
http://sbf.droid-developers.org/
and Here:
goo.gl/9SdIy
JerrytheGreat said:
Hello,
I bricked my phone trying to downgrade from the 2.3.4 update to my R2D2. (I knew better, but what can I say?) I currently need a stock Verizon 2.3.4 sbf for either Droid 2 or (preferrably) the R2D2 to flash back to. I have a spare phone I will run to my office tomorrow to use for now, but I really want to unbrick by beloved R2D2...
The official ROMI'm looking for is 4.5.622.A957.Verizon.en.US
Click to expand...
Click to collapse
I think I'm in the same boat.
Hey guys I can upload a .sbf later tonight.
Sent from my DROID2 using xda premium
Where did you get it?
Not to be unappreciative, but I understand that the 2.3.4 sbf for the Droid 2 R2D2 wont be available until it gets leaked from VZW, and that it doesn't even exist yet for the Droid 2--do you have a way to get it?
If you do, you'll be my hero!!
jtg
JerrytheGreat said:
Not to be unappreciative, but I understand that the 2.3.4 sbf for the Droid 2 R2D2 wont be available until it gets leaked from VZW, and that it doesn't even exist yet for the Droid 2--do you have a way to get it?
If you do, you'll be my hero!!
jtg
Click to expand...
Click to collapse
I have the gingerbread sbf for the droid2
Gingerbread 2.3.3 will not work-MUST be 2.3.4
Thanks for the offer, but the Gingerbread 2.3.3 floating around the Internet will not work- the SBF MUST be 2.3.4, what was just realeased as an OTA 1 week or so ago.
Now, if someone stumbles across this thread, please note you CANNOT "downgrade" the R2D2 after the 2.3.4 OTA, as Verizon also updated the bootloader. If you try to downgrade to 2.3.3, you will brick the phone until the 2.3.4 sbf gets leaked.
From what I have seen, I am one of 3 people to create bricked R2D2s trying this, now waiting for a 2.3.4 leak to bring his/her phone back from the dead.
If you are indeed looking for the VZW 2.3.3 sbf, stockroms.net has it.
-jtg
same, identical problem!!!!
Amazing what can be found if you scan down maybe 10 posts or so from your own =P
http://forum.xda-developers.com/showthread.php?t=1566481
MissionImprobable said:
Amazing what can be found if you scan down maybe 10 posts or so from your own =P
http://forum.xda-developers.com/showthread.php?t=1566481
Click to expand...
Click to collapse
Thats 2.3.3
Not 2.3.4
So it's actually not amazing.
Still no movement on this?
My bricked R2D2 is looking very sad, sitting with no battery in it on the side of my desk...
JerrytheGreat said:
Still no movement on this?
My bricked R2D2 is looking very sad, sitting with no battery in it on the side of my desk...
Click to expand...
Click to collapse
sadly i do believe my r2d2 has suffered the same fate as yours.. ive tried updatubg with both of the available from
stockroms . net/ file/ Droid2/ Droid2R2D2
Bootloader
D2.37
Err:A5,70,70,00,1F thou ive had several variations
MEM_MAP Blank
Service Req'd
Battery OK
OK to program
Connect USB Data Cable
this is what i get when i connect it.. it acts like its flashing but never does.... when it reboots it goes right back to the loader with same mem_map blank error
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x00D237
Ok since no one is answering Ill say this.
You CANNOT SBF back. The 2.3.4 update changes your bootloader. None of the SBFs will work anymore once you update. This was told the day it was released. You will also lose Root ability.
Sorry but until someone can overcome the bootloader or the current SBF is leaked you peeps are stuck.
chasehammer said:
Ok since no one is answering Ill say this.
You CANNOT SBF back. The 2.3.4 update changes your bootloader. None of the SBFs will work anymore once you update. This was told the day it was released. You will also lose Root ability.
Sorry but until someone can overcome the bootloader or the current SBF is leaked you peeps are stuck.
Click to expand...
Click to collapse
Thank you, Captain Obvious, for restating the subject of this thread..
Not trying to be an ass, just wondering why you installed the update knowing that you would lose root and couldn't SBF back.
MissionImprobable said:
Not trying to be an ass, just wondering why you installed the update knowing that you would lose root and couldn't SBF back.
Click to expand...
Click to collapse
A. My batt life and stability tanked after the update, and I was fed up
B. Didn't think it through
C. I thought I could easily download the most recent sbf and reflash-but didnt check first to see its wasn't available.
D. I have a spare phone, so knew if I bricked it, I would be OK
E. I'm not shocked or mad, I'm already married, so enough told-you-so's
Same problem
Why doesn't Verizon just release the sbf? Whats their reason for not releasing it, Those bastards!!
korydak1lla said:
Why doesn't Verizon just release the sbf? Whats their reason for not releasing it, Those bastards!!
Click to expand...
Click to collapse
Ummmmm they dont want people to be able to root their phones.
Don't expect the sbf anytime soon as the Droid 2 is dead and pretty much nobody cares about it. :/
That's why I love me some MIUI. Also why Moto is on the bottom of my list for future upgrades. Sony is looking dead sexy about now.
Please Keep an Eye Peeled--Lots of People need this
Well this thread and about 4 others all drill down to the same issue.
We are all looking for a leaked 2.3.4 sbf for Verizon Droid2 or R2D2. Please all you people in the know keep your eyes peeled for a leak, and post the second it appears (if ever).
jtg

Categories

Resources