Hi.
I recently got a refurbished Evo 3D after my old one's digitizer broke. About 2 days afterwards, I was being stupid and accidentally dropped my phone. The back popped off and the battery came out. Now it shows a dim red light whenever it should be charging (via usb cable into my computer) and refuses to even turn on. However, whenever I plug it in, it makes the sound that windows recognizes that a USB device is plugged in. Is this a sign of hope that I can fix my phone? Please give me any suggestions.
Things I have tried:
-Holding power down (with the volume buttons and camera button etc.)
-Trying to use the command: adb reboot bootloader
-Taking out batter and using a different one from another phone.
-Charging the original battery to full using the spare Evo 3D and then attempting the above.
Before I dropped it I did root the phone and stupidly attempted to install the wrong ROM (used CDMA instead of the other one, can't remember the name off the top of my head, but it's the one used in Rogers phones), but it didn't brick the phone or anything.
One more thing to note is that right after I dropped it and tried to boot it up it made it to the white HTC screen, then turned off.
Hopefully this is enough information, and thanks in advance for any help.
Check out the thread in the dev section about downgrading hboot 1.5 at some point in it, you purposefully brick it to a faint red light. Try to follow instructions from there.
Sent from my PG86100 using xda premium
troublein420 said:
Check out the thread in the dev section about downgrading hboot 1.5 at some point in it, you purposefully brick it to a faint red light. Try to follow instructions from there.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Any other suggestions? I don't have a linux machine, and currently my ISP is not exactly cooperating with my internet connection, so it's extremely slow atm, and as a result will probably take too long to download.
troublein420 said:
Check out the thread in the dev section about downgrading hboot 1.5 at some point in it, you purposefully brick it to a faint red light. Try to follow instructions from there.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Not to just repeat what others have said, but the dim red light truly sounds like what happens when the phone is bricked. If it is, you may be able to save it by following that thread when your ISP cooperates. It is strange though that dropping it would cause it to brick.
If he is on Rogers, he has a GSM phone & can't use the Hboot 1.50 cdma downgrade thread. There are 2 stickied downgrade threads in the Gsm section.
Sent from my PG86100 using Tapatalk
Well you know the old saying once you drop it its over or you could turn it in and get a replacement
Sent from my HTC EVO 3D X515m using xda premium
out of warranty ? =.=
just 2 days after returning
Here's what I would try
Here's what I would try:
1. Take battery out of phone and make sure, 100% sure, the phone is off.
2. Once the phone is 100% powered down pop the battery back in.
3. Now what I would do is hold down power + volume up until the phone comes to HBOOT.
4. If HBOOT doesn't come up, idk. If you have a working nandroid, I would restore from it. If you don't, just select fast boot, then select the option to start up normally (which I forget what it is called...).
-cburk
Related
I have a big problem !!! I had on my phone root s-off ROM Shooter Beats 1,7 and I flashed CWM 4.0.1.-shooteru via fastboot.
BUT when I was in fastboot USB I was thinking that I will try to have root with s-on on the screen on HBOOT. So I used command that I read in unroot section.
fastboot oem fastboot oem writesecureflag 3 and then reboot bootloader and my pfone is off and I cannot turn it on and dont know what to do :-( I am scared
you need to s-off your device again.using cmd
yes, I know, but I cannot turn on the phone.. I cannot do anything
Bricked
Sent from my HTC EVO 3D X515m using XDA App
There is nothing else to do?? :-(
What about warranty? If I cannot get to my phone, HTC cannot know if it doesnt work because of root, right? Do I have a chance?
What about a simple RUU? Just to try, and may it gives you s-on back and hboot and Kernel, so you maybe can boot into fastboot loader
Sent from my HTC EVO 3D X515m using XDA App
I cannot turn my phone on, I cannot go to bootloader, I cannot do anything. But when there is battery there is little red light on and when I remove battery it goes off. It is not blinking it is just permanent weak red colour (it is hardly to see).
When I connect Evo 3D to laptop, there is a sound that something is through USB connected, but the drivers are not regognized (in system there is only something QHUSB_DLOAD)
I was trying cmd and fastboot reboot and it is waiting for device
I was trying adb restart and nothing..
when I try RUU, it cannot find my device
Castellano2 said:
I cannot turn my phone on, I cannot go to bootloader, I cannot do anything. But when there is battery there is little red light on and when I remove battery it goes off. It is not blinking it is just permanent weak red colour (it is hardly to see).
When I connect Evo 3D to laptop, there is a sound that something is through USB connected, but the drivers are not regognized (in system there is only something QHUSB_DLOAD)
I was trying cmd and fastboot reboot and it is waiting for device
I was trying adb restart and nothing..
when I try RUU, it cannot find my device
Click to expand...
Click to collapse
try to use a RUU
If all fails send it back to HTC and say it stopped working overnight
Sent from my HTC EVO 3D X515m using XDA App
Did you have recovery? If you do, the problem you ran into might be an easy one.
1. Plug your phone to a power source (Long press the power button for few seconds and see if the light is on)
2. If the light is on, press the camera button (may be few times if first time doesn't work) and wait.
3. The first two steps should have already taken you into the boot screen. If it doesn't, then sorry.
thre3aces said:
If all fails send it back to HTC and say it stopped working overnight
Sent from my HTC EVO 3D X515m using XDA App
Click to expand...
Click to collapse
Try to push camera, volume up+down and power Buttonand hold it down for a few seconds and see if the phone boots. Then plug in charger and charge it. So you can see if the battery was dead!
Thank you guys for advices but
1, I tried use RUU and as I said it doesnt find my device (there are not drivers anymore)
2, volume plus camera button and so on.. this problem I solved many times.. it was problem with CWM 5.0.2. but I have there 4.0.1. which has no battery bug.
My phone doesnt work and cannot go on.
I googled little bit and find out that people with Desire HD had the same issue and they sent it to service and got new phone. I hope it will be the same I love my phone so muuuuuuch..
I think the problem is that I would need to get drivers for my mobile to get sdk ready.. but :/
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to Q&A
Castellano2 said:
Thank you guys for advices but
1, I tried use RUU and as I said it doesnt find my device (there are not drivers anymore)
2, volume plus camera button and so on.. this problem I solved many times.. it was problem with CWM 5.0.2. but I have there 4.0.1. which has no battery bug.
My phone doesnt work and cannot go on.
I googled little bit and find out that people with Desire HD had the same issue and they sent it to service and got new phone. I hope it will be the same I love my phone so muuuuuuch..
I think the problem is that I would need to get drivers for my mobile to get sdk ready.. but :/
Click to expand...
Click to collapse
bricked...there are a few reports here that did the same procedure and bricked it too.
I really cant understand why people play with those things although they have no idea of what they are risking.
..i mean, you could have been very proud that you got a device which csn achieve s-off. Thousands still dteaming of it.
Why the hell you wanted to went back to son and root?
If you would read through the forums you should have nitice, that you cant flash custom kernels easily - just with flash img gui. And flashing radios is
Is completly not possible with son.
Son makes life so much more painful.
And you still did it...sry tried it
Sent from my HTC EVO 3D X515m using xda premium
j4n87 said:
bricked...there are a few reports here that did the same procedure and bricked it too.
I really cant understand why people play with those things although they have no idea of what they are risking.
..i mean, you could have been very proud that you got a device which csn achieve s-off. Thousands still dteaming of it.
Why the hell you wanted to went back to son and root?
If you would read through the forums you should have nitice, that you cant flash custom kernels easily - just with flash img gui. And flashing radios is
Is completly not possible with son.
Son makes life so much more painful.
And you still did it...sry tried it
Sent from my HTC EVO 3D X515m using xda premium
Click to expand...
Click to collapse
I know, I read through forum and find out that problem with QHUSB_DLOAD is always dead end. You cannot understand why people do that? I read a lot of topic where people have written that I tried to unroot their phone because of warranty and in finally step - whitesecure flag 3 - it bricked. They do it exactly how it was in "manual", so they have just bad luck.
I want to have s-on because my cable conector was wrong and I was afraid when I won´t connect my phone to computer, I cannot remove root and my quarantee will finished.. But I didnt flash stock Rom because I want to give it on sd card and when my usb cable won´t work, I could just reflash to stock ROM from my backup..
Right now my phone is in service..
okay! so I have a S-on amaze 4g. Unlocked bootloader and have clock work recovery, Im also on tmobile. I was running Bulletproof's rom v2.5
so yesterday I was looking at some roms and I came accross mike 1986's android revolution ROM that was based on tmobile's sense 3.6 and android 4.0. I decided to ditch my current ROM and go for mike's ROM instead
Well last night I followed his instructions. Put the PH85IMG, Rom and Super wipe to my phone's SD card. I booted into bootloader and it loaded the PH85IMG but it didnt seem to have done anything so it loaded back to bootloader. I selected "Recovery" and booted into recovery. I deleted my files and cache using clockwork recovery. Then applied the Superwipe zip then installed the ROM. It said it installed the rom and then I proceeded to reboot my amaze 4g. Ok I rebooted my phone and it got stuck on the HTC screen for some quit time WITHOUT THE QUIETLY BRILLIANT. So i decided to redo this all over again. and again the same problem happened. stuck on the HTC logo. so I took out my batterys and went to bed since i wanted to get some shut eye
now this is where my problem comes from. When ever I turn on my phone it wont turn on! i wanted to boot into bootlader but when ever i press on the power button with the volume rocker down it wont start up. So i plug in my USB cable and the LED that indicates charging comes on. and my computer detects the phone... i click on the search capacitive button and the phone disconnects from my computer and it boots into the HTC screen and the screen turns blank
if anyone can help me please help.
come on 43 views and no help
Leave your phone in the charger overnight. See what happens in the morning.
hasoon2000 said:
Leave your phone in the charger overnight. See what happens in the morning.
Click to expand...
Click to collapse
i dont think thats going to work but ill give it a try
Just curious. What version of CWM was installed?
Sent from my HTC_Amaze_4G using Tapatalk 2
So you cant get the the phone to turn on, but u were able to turn it on when it was connected to the computer?
Sent from my NRGized amaze
Via XDA premium
Ok. First don't panic. Can you explain by "I clicked the capactive search button". Have you really try power it on without your computer?
Sent from my HTC_Amaze_4G using XDA
jp2dj1 said:
Ok. First don't panic. Can you explain by "I clicked the capactive search button". Have you really try power it on without your computer?
Sent from my HTC_Amaze_4G using XDA
Click to expand...
Click to collapse
what i mean by that is when i touch the search button (the magnifying glass icon on the far right) when its charging it would boot into the HTC screen then the screen would turn off
aj_2423 said:
So you cant get the the phone to turn on, but u were able to turn it on when it was connected to the computer?
Sent from my NRGized amaze
Via XDA premium
Click to expand...
Click to collapse
i cant get the phone to turn on when its connected to the computer or wall charger
i just noticed that my LED would blink when first charging then it boot into the HTC screen on its own then the screen would turn off or go blank. after that the LED wouldnt come on so i dont know if its still charging since the orange light isnt there
any more help it would be greatly appreciated
I tried the same rom yesterday and it failed for me also. I've seen quite a few fails on it. Mine didn't die like yours, mine just froze on the splash screen. I had to pull the battery and hboot and re install my recovery so I could restore my backup. Does anything happen if you pull the battery and try to get into bootloader?
jimczyz said:
I tried the same rom yesterday and it failed for me also. I've seen quite a few fails on it. Mine didn't die like yours, mine just froze on the splash screen. I had to pull the battery and hboot and re install my recovery so I could restore my backup. Does anything happen if you pull the battery and try to get into bootloader?
Click to expand...
Click to collapse
i cant even get my phone to get into hboot when i press down on the power and volume buttons.
it did work yesterday after i failed... but when i woke up today i cant even get into hboot for some reason.
You might have to get an external charger to charge your battery, or if you know anyone to swap batteries with to charge yours and try theirs to see if it's just a dead battery. Sounds like it might be.
Download the latest RUU for your phone. You said the computer detects the device see if the RUU will see it as well. Hoping that it does just run it and it will flash your phone back to stock stock and you may have to unlock and install clockwork again but if it works you'll have a working phone again good luck chief
Sent from my LG-P999 using Tapatalk 2
I believe the Rom u were trying to flash is for s-off only....I might be wrong though...
Sent from my HTC_Amaze_4G using XDA
If i recall, you were supposed to lock the bootloader before you placed the PH85.img, because it wouldn't recognize the file without it on an S-On device. Also, where you using Xboarder's Clockwork recovery touch? or an older version?
Try this and tell me what happens. Change your phone by your computer USB and turn it on by search button and "HOLD THE DOWN VOL BUTTON AT THE SAME TIME" try it a couple of times.
Sent from my HTC_Amaze_4G using XDA
I think it's a problem with the version of cwm installed, it won't charge the battery right if it dies all the way pull the battery then charge it for about 20 mins then battery pull again and charge for a minute or two and try and turn it on
Sent from my HTC_Amaze_4G using XDA
Thread Moved to Q&A. PM sent to OP.
Sent from my Galaxy Note i717, using XDA Premium.
You don't have to be a farmer to know what sh*t smells like.
WTF, so about 2 hours ago my evo just crapped out. Its S-off running Flex360s 1.72 rom. I was at the store and pulled out my phone, I hit the power button and nothing would happen. When I got home I noticed its stuck at the splash screen with no backlight. Held the power button till it restarted and it would vibrate and bootloop till it eventually get stuck at the splash screen. The whole time the backlight being off. It can go to bootloader but its like frozen and even then the backlight is still off. Too bad I cant pull the battery, also it will not just turn off
Time to plug in USB and run the latest RUU for Jewel?
Sent From My S-OFFed, R00ted, 100% Tricked-Out HTC Evo 4G LTE via XDA Premium!
Similar to mine,,,
boost happy said:
WTF, so about 2 hours ago my evo just crapped out. Its S-off running Flex360s 1.72 rom. I was at the store and pulled out my phone, I hit the power button and nothing would happen. When I got home I noticed its stuck at the splash screen with no backlight. Held the power button till it restarted and it would vibrate and bootloop till it eventually get stuck at the splash screen. The whole time the backlight being off. It can go to bootloader but its like frozen and even then the backlight is still off. Too bad I cant pull the battery, also it will not just turn off
Click to expand...
Click to collapse
Mine bricked itself too...
http://forum.xda-developers.com/showthread.php?t=1800686
michael.stollaire said:
Time to plug in USB and run the latest RUU for Jewel?
Sent From My S-OFFed, R00ted, 100% Tricked-Out HTC Evo 4G LTE via XDA Premium!
Click to expand...
Click to collapse
Already tried. It basically told me to screw myself lol.
EDIT: OK I've had it connected to my computer for awhile trying to communicate through ADB. I have fail, & in another attempt to power it off, I held power down for like 3 mins straight. After releasing power it stayed off, and now I have a charging light!!! In a few I will attempt going into bootloader again
still screwed
boost happy said:
still screwed
Click to expand...
Click to collapse
May sound like a dumb question but did you have it plugged into a car charger before going into the store?
Sent from my EVO using xda premium
mcvoss said:
May sound like a dumb question but did you have it plugged into a car charger before going into the store?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
You are not actually bricked since your device turns on and shows some responsiveness when doing so (i.e. bootloader) My phone is ACTUALLY BRICKED meaning it has no response of any type whatsoever. If you can successfully boot into bootloader then you'd want to select "fastboot" then run the Jewel RUU from your PC. You'll need all the necessary fastboot drivers installed beforehand.
Can't select anything in bootloader. Its unresponsive
boost happy said:
Can't select anything in bootloader. Its unresponsive
Click to expand...
Click to collapse
Smash it, TEP time.
Sent from my EVO using xda premium
shook187 said:
Smash it, TEP time.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
yes, I feel like going out back with the phone and 1911..
I do have TEP and Best Buy black tie. I may go to best buy and see what they will do.. I just hope like hell I dont end up with the new HBOOT
boost happy said:
yes, I feel like going out back with the phone and 1911..
I do have TEP and Best Buy black tie. I may go to best buy and see what they will do.. I just hope like hell I dont end up with the new HBOOT
Click to expand...
Click to collapse
bring it to best buy, you will get a loaner phone for 3 days and then get the new one. whats nice is there people at geek squad dont know how to check if the phone is even rooted, also you get the new one before the people get the broken one.
Hey guys, quite honestly this is just a post-mortem help I felt I would want to chime in with. I just had almost a heart attack last night thinking I bricked my HTC Raider 4G / HTC Holiday / HTC Vivid / HTC Velocity 4G - Whatever you want to call it, it's the same phone. BTW, the captcha on this site and the discrimination towards new users is borderline a war crime
I want to ensure you that if you followed the whole Juopunutbear S-off bootloop / ControlBear method - your phone is NOT BRICKED. Mine wasn't, and I almost gave up on it last night. I ended up trading my HTC Raider 4G with someone for a Samsung Galaxy S III, but I wanted to touch base and just give you a heads up as to what I did (as best my memory serves me).
My situation was as follows:
1) I used the whole S-Off Toolkit By Hasoon2000 - and actually got S-Off (Security Off)
2) I followed to a tee, with all of it's "beer" references and did the whole "wire-trick" see picture below, I had to pull out my lab lamp light to see it and was getting more and more angry as the evening progressed.
3) My phone was stuck in the Juopunutbear S-Off Bootloop (or Boot Loop as some put it)
4) I could get the phone into Recovery/Fastboot (whatever you want to call it.)
Here is what I did to fix it:
1) Get yourself your OEM RUU (This is the Original Equipment Manufacturer Rom Update Utility), I hate acronyms so I will clarify as I go. You can download these at the following link (If you come back to this page a year from now and the links are broken, Google them by the exact file name, I am certain someone out there will keep backups forever. The link below surely has your carrier, e.g. Telstra etc. Follow the instructions and download your RUU for your carrier:
http://www.filefactory.com/f/002b74e0f4775869/
2) Pull the battery out of your HTC Raider / Holiday / Vivid / Velocity
3) Re-insert the battery into the phone
4) Press the volume down button + power and hold until the "Bootloader" or "Recovery" or "HBoot" or "Fastboot" screen comes up - many names for it.
5) Once the screen has come up, click on Fastboot and connect it to your computer. If it detects your computer it will say "Fastboot USB", this is good and it will look like the image at the bottom.
6) Once the phone is connected, run the specific file name for your phone based on carrier from point number 1.
7) Leave the phone plugged in and running, and it will basically flash the phone back to OEM - at least this way you can have a useable phone and will allow you to retreat/regroup and fight another day.
Fastboot USB Photo - Get your phone to look like this by going through the menus, it won't take more than 10 seconds
http://i47.tinypic.com/ru5m55.png
My Lab Setup - With The "Wire Trick" + Lamp and me getting more and more pissed off.
http://i48.tinypic.com/dyng9v.jpg
I hope this helps, I was quite honestly pulling my hair out trying to find out more information/help but it was just almost impossible to find for this phone - I think the reduced user base is partially to blame for this. My previous phone was a Samsung Galaxy S I9000 and I had absolutely no issues with support. I've learned my lesson and devices to back out, I now have a nice Samsung Galaxy S 3. If you need anything - I think you can PM me. P.S. I ran both Virtuous Inquisition ROM as well as Wajee's 1.5 and they were ok - Wajee was a bit better.
All that typing and you didn't even post for the correct device
Sent from my HTC_Amaze_4G using xda app-developers app
You could just have use the controlbear -r command..iirc
Sent from my HTC_Amaze_4G using xda app-developers app
Spastic909 said:
All that typing and you didn't even post for the correct device
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Long night, i'll be moving this. or reposting there.
ce3jay said:
You could just have use the controlbear -r command..iirc
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
I did, it did not help anything. It kept going into the Juopunutbear arrow down screen.
This is still good advice. Just needs minor tweaking for Amaze and you got yourself a deal!
Sent From My HTC Amaze 4G via Someone's Room
Hello friends and thanks for reading. Glad to finally be a part of one of the most highly respectable, trustworthy, and knowledgeable development sites on the Internet. Not an ass kisser, just feel that if you've used a website to fix or mod ALOT of different things that you didn't know how to fully do on your own, and you also learned how and why, you should express some appreciation. I've searched and searched but I'm pretty sure this is one of the more rare bricks. Not one of those did u hold volume down and OMG theres the hboot menu threads lol. So here goes...
Modification Procedure:
JuopunutBear S-Off
Hboot 1.50.5050
Radio 1.09.00.0706
Recovery TWRP v2.2.0
Angry Bean Rom CM 10.1 build 06.07.13
Joe Blow Hacks
Computer rig:
Ubuntu 12.04 x32 & Windows 8 x32 dual boot
Asus A8AE-LE
Amd Athlon 64 3500+
2gb Pc3200
Tools / Testing Equipment:
- 2 identical model Evo's
Model: PG86100
- 2 identical batteries (all working)
- Both phones have had the same exact procedure done
- The other Evo that went through the procedure is still working fine and I use it as my main phone
What it Does / Doesn't do:
- Cant get to hboot
- Cant get to recovery
- With battery in and usb charger plugged in, and not hitting any buttons including power, there is a solid red light that would indicate normal charging. I don't believe it is because the other Evo, after letting the bad one supposedly charge the battery, says the battery is low
- With the usb charger unplugged and a known charged battery placed in the phone and me hitting power once, it vibrates once and the home, menu, back and search light up. Screen shows absolutely nothing. holding volume up down and power in this state makes the phone vibrate once and all the lights go out. Then after a second adb sees it again as device offline
- When I boot using either Windows or Ubuntu, the command “adb devices” shows the serial and offline
- When I boot the working Evo using either Windows or Ubuntu, the command “adb devices” shows the serial and device (as it should)
- Adb and fastboot run fine with the working Evo
- Adb is about useless on the dead Evo. Every command = error device offline
Things I tried that failed:
- Volume up + power it vibrates once and the home, menu, back and search light up
- Volume down + power the phone doesn't boot (can't access hboot)
- Charger in the phone first with no battery. Then I held volume up and down and inserted the battery. Phone just goes back to the solid red light and gets hot. Screen shows absolutely nothing
(yes I took my time do to the fact that most problems occur do to a lack of patience and user error :silly:
- Ruu (no fastboot)
- ./brickdetect.sh Device can't be detected. Check connections
I usually got this type of thing in the bag but this time I'm just not getting anywhere. Any and all input would be greatly appreciated. Is there something not right here in this Evo setup that I'm not seeing or in your opinion do u think that the working Evo is in “harms way”? I keep wondering...Thanks
What happened to the phone before it got into its current state? Did this happen while you were doing the S-off procedure?
Sent from my Evo 3D CDMA using xda premium
The Fer-Shiz-Nizzle said:
What happened to the phone before it got into its current state? Did this happen while you were doing the S-off procedure?
Sent from my Evo 3D CDMA using xda premium
Click to expand...
Click to collapse
No thats the thing. I did both Evo procedures at the same time. Same files and everything. S-off went great for both phones. The phone was being used as a dlna client. Right before it "bricked", it was watching The Walking Dead. Would you consider this to be a brick, as i don't want to be misleading people. Theres a lotta posts that throw around bricked and hard bricked like there the same when there not...
Noxus001 said:
No thats the thing. I did both Evo procedures at the same time. Same files and everything. S-off went great for both phones. The phone was being used as a dlna client. Right before it "bricked", it was watching The Walking Dead. Would you consider this to be a brick, as i don't want to be misleading people. Theres a lotta posts that throw around bricked and hard bricked like there the same when there not...
Click to expand...
Click to collapse
I mean ya i know it's bricked lol but should it be defined as hard bricked?...
Is it getting hot around cameras while it's on charger?
If it is your motherboard died
Yes it is. Installed a a known good board inside the dead evo and I'm currently using it to post.
Sent from my Evo V 4G using xda premium
Noxus001 said:
Yes it is. Installed a a known good board inside the dead evo and I'm currently using it to post.
Sent from my Evo V 4G using xda premium
Click to expand...
Click to collapse
So it's all fine now?
Yes all is well. Thanks for all the help
Sent from my Evo V 4G using xda premium
Just a coincidence that the board died?
Noxus001 said:
Yes it is. Installed a a known good board inside the dead evo and I'm currently using it to post.
Sent from my Evo V 4G using xda premium
Click to expand...
Click to collapse
Hi everyone.
So, what do you guys think happened here? Did the motherboard just happen to die, or was its demise hastened by modifying the phone?
Good to read that you solved your problem, though. So, where did you get a replacement board, just off one of the usual sell yours buy someone else's type sites?