Search the Community
Showing results for tags 'brick'.
-
Summary Older Google Home (gen 1), and Google Home Mini (gen 1) devices appear to have issues with a recent firmware update that's being pushed out to devices. The devices are unable to reboot after the update and will, in most cases, get to the step in the bootup process with 4 white lights turned on and then hang there indefinitely. My thoughts This personally happened to one of my Google Home Mini devices and through my attempts to reboot, factory reset, and even reached out to the Google Home support live chat I was able to learn that the Google engineers are working on the issue but I am unsure if there will be a self-service solution to those that have bricked devices because the device locks up seemingly before they connect to the wifi. The earliest reports of this bricking appear to have happened this past Tuesday (12/05/2023). Unfortunately, while not everyone has confirmed this, it appears that those which have mentioned it do report that they had opted into the Preview Program where our devices could get firmware updates and new features pushed out earlier. While I understand there are risks to opting into a program such as this I do also firmly believe that Google should be responsible enough with a preview program to not push firmware updates to devices that are out of warranty and/or aren't in their list of validation devices for new firmware updates. I'd like to see Google provide a solution to this through sideloading of a new firmware through the micro-usb port (if that's even possible), opt to provide an out-of-warranty replacement ( unlikely) or even provide us early adopters with a discount code to buy a new device. It's an unfortunate situation but something that I don't see Google having no fault in causing. There were many ways they could have prevented this and it doesn't seem that any of them were put into place. Sources Sadly it doesn't look like any traditional news sites have picked up on this as of yet. We just have my own personal experience, responses from chat support, and lots posts in the Google Nest Community support forums. Update below https://www.googlenestcommunity.com/t5/Speakers-and-Displays/Google-Home-stuck-with-4-white-lights/td-p/557532 https://www.googlenestcommunity.com/t5/Speakers-and-Displays/google-home-mini-all-4-lights-on/td-p/555963 https://www.googlenestcommunity.com/t5/Speakers-and-Displays/My-Google-Home-mini-suddenly-died/td-p/557160 Edit: Adding Actual News Sources It appears that smaller tech news sites are starting to report on the issue: https://www.androidauthority.com/google-home-mini-bricked-2-3393591/ https://www.howtogeek.com/google-is-looking-into-bricked-google-home-speakers/
-
I was playing Bloons td 6 with some friends when my pc randomly shut off and when I tried to turn it back on all that happened is the RGB on the ram modules turned on and that’s it. I’m not sure what could be broken. I have some theories but I could really use some help from people more experienced than myself as this was my first build I completed about a year and a half ago.
-
So, I recently updated my phone from Android 11 to 12 in order to try and fix some app compatibilities, and in attempting to restore Magisk and TWRP, I somehow made the phone unbootable. From what I found already, TWRP is just not compatible with Android 12. but now I have a bigger problem (obviously). When I try to boot, I get a screen saying "The current image (boot/recovery) have been destroyed and can not boot". I have used the msm tool before to unbrick this device (when I made a similar mistake in the past, resulting in a boot loop) however, as far as I know, that wipes all data on the device. Does anyone know of a way to fix this without wiping data? or, at least, recovering select files before wiping?
-
I was trying to enable secure boot to be able to upgrade to windows 11 (although that doesn't sound too appealing now that the steam servers dont work for some reason) and it corrupted my BIOS. My PC wouldn't load into anything. The fans would turn on for a few seconds and then turn off again, and loop this indefinitely. After a stressful hour I was able to fix the BIOS by removing the CMOS battery and jumping the CMOS pins and now my pc runs normally again. My question is, though, How come it does this? Why can I not enable secure boot without my BIOS dying? I ended up bricking the BIOS twice because i didn't realise secure boot was the issue, but fixed it both times. Is there a way I can fix this? My specs are: Ryzen 7 2700 Radeon RX 570 16GB DDR4 3200MHz RAM 2TB HDD storage 120GB SSD storage Gigabyte A320m-S2H motherboard Thats all the useful information i can think of -
So I built a bit of a mining setup (it has 2 1060s 3 1070s and 1 rx 580 in it). I had everything running perfectly until today when I set the overclock for everything, msi after burner crashed and then a minute later I got a blue screen saying it needed to restart. Once I turned it on the computer now doesn't register the rx580, it appears on msi after burner with 0 as all of its stats but doesn't show up on task manager. Does anybody have a solution? MSI b450a motherboard 120gb Kingston ssd 4gb 2666mhz ram Ryzen 3 3200g cpu 650w psu for everything except gpus 850w psu for the GPUs
-
Hello technicians! I had this problem when editing Serial Number and UUID of my motherboard because i had to replace it with a new one. Since before it was working well until DMI Edit broke/brick? my motherboard because when after I restarted the pc I never got into the post screen/bios anymore. Appreciate for the help. Thank you! Yes, all my fans are spinning even my GPU fans are spinning. My rams is on active lid, My keyboard used to light and my mouse until i removed gpu and putting it back in it and it never light anymore (Probably a mistake). Specs: MOBO : Asus TUF B450m Plus Gaming OS : Windows 10 Pro x64 (Customized ft. Ghost Spectre) RAM : TForce 16gb 2666Mhz PSU : 700 Watts Carbocs GPU : RX 570 OC ROG 4Gb CPU : Ryzen 5 2600g 2.8Ghz What I Did: 1. Removed CMOS battery for an hour while all cables are unplugged. 2. Removed GPU and used CPU Graphics to turn it on again. 3. Removed my RAMS and I used only 1 in the 2nd slot of RAM. 4. Removed my RAMS and replaced it opposite. 5. Cleaned all my Computer Parts. video-1621695276.mp4
-
Relock bootloader with TWRP installed. Will it Brick?
Arouraios posted a topic in Phones and Tablets
I've found a lot of conflicting information on ze internet. Does anyone here happen to know wether relocking my bootloader with twrp installed can/will brick my phone? I used to run a custom rom and all but now I'm getting the phone ready to be passed on to someone less tech savy who might want to use Google Pay or similar, which requires a locked bootloader due to recent SafetyNet changes. So, is there any way I can keep TWRP installed and still lock it? I am aware that I won't be able to update or flash unless i unlock again. But until then, can I relock it? Or will the reset brick the device? Please don't just post "that's a stupid question, don't lock" without an answer. I know it's not great, but I am asking if anyone has tried this before. -
Hi, I ran into a problem recently, where I tried to flash twrp to my Honor 7 lite. Unfortunately something went wrong and everytime I try to get to recovery or fastboot I end up on this screen: So I decided to flash stock android but can't even get into any recovery or fastboot to flash it, so I don't really know what to do now. Thanks for any help, because I'm getting really desperate now
-
So here's the story. I was moving my GPU up a slot since i was taking out my WiFi card and i had space to put it in, and it would give it better airflow. I turned it on and everything worked fine, and my temps went down by a little too. So i decided to push my luck. I updated my BIOS over the internet. After it updated, everything looked fine. So i turned on XMP and virtualisation, and my computer wouldn't boot to the ASUS logo. I opened up my PC, took out my GPU and re-inserted my CMOS battery to clear my CMOS. Everything worked fine again, until i tried to change any settings. I went to the ASUS Website and downloaded the latest BIOS for my B150M-C from here. But noticed something kinda fishy. When I clicked "see all downloads" i noticed that all of the other BIOS releases have some release notes, even if they're quick ones like "Improve system capability and stability", but the latest version didn't. I still thought something might have happened when I downloaded my BIOS over the internet, and decided to retry the latest BIOS version by flashing it onto my USB stick. I installed the latest BIOS version and it looked like everything worked fine, but i still couldn't enable XMP or Virtualisation. I downloaded the previous version of the bios and I could enable these settings. I think it's a pretty large co-incidence how there were no release notes and the latest version of the BIOS is broken, at the point where it feel kind of sketchy. I looked around other BIOS versions for the B150M-A and the B150M-K and i couldn't find any BIOS versions without any release notes. So here's what I think: ASUS made a very careless mistake and made it possible to easily softbrick your system with a bad BIOS, and didn't add any release notes. ASUS intentionally broke the BIOS version. It's a very budget motherboard for budget skylake CPUs and may be in a lot of pre-builts. In the manual it talks about a disk about "Antivirus software (OEM Version)". People who aren't to great with computers might update their BIOS and change settings in their BIOS based on google searches. They find out that they accidentally soft-bricked their system and might not know that they can clear their CMOS. This is more likely with a board like this as it's nowhere near enthusiast level and is very cheap, meaning people who don't know much about computers are more likely to get a budget pre-built with a mobo like this, or have a friend build it etc. They might think that their computer is broken, meaning that they might get a new one and asus gets more money for people getting their parts? Number 2 is highly unlikely but considering how sketchy this feels it just might be true. Or maybe i'm just very paranoid. I'm curious to see what you think. -
Hello peeps. My Poco F3 got hard bricked after update froze (was doing clean install of stable EU rom). Phone won't boot into any mode, and won't appear on pc. I've tried sorting the Test Pins 50 different ways and it still doesn't get picked up by the pc. Qualcomm Drivers are installed. Device is connected with working data transfer USB cable. It definitely is getting charge cause Battery and CPU are hotter than the rest of the phone. I'm at complete loss, I have no idea what I'm doing wrong or if I screwed up my phone that bad that EDL also doesn't work. Thanks for any help!
-
FYI: firmware 1.0.34.0 bricking Microsoft Surface Go 1's
Blue Bill posted a topic in Troubleshooting
Seems Microsoft has been pushing out a Windows firmware update for the Surface Go series of tablets. This firmware version 1.0.34.0 was released end of May 2022 and is causing many Surface Go 4G 64GB eMMC machines to no longer boot from the internal eMMC with a "No bootable device" error. According to this thread, Microsoft appears to know there is an issue but has done nothing to fix it aside from sending in your device for a replacement for $250. Surface Go uefi version is 1.0.34 and No Bootable Device error - Microsoft Community A Reddit thread (9) URGENT NOTICE: Surface Go 1 UEFI firmware 1.0.34.0 update is bugged. "No Bootable Device" : Surface (reddit.com) And a single article Surface Go, pay attention to firmware 1.0.34: more than someone is in serious trouble - Real Mi Central Not sure what it takes to get the wheels greased at Microsoft, but they are "bricking" lots of Surface Go 1 baselines. If you have a baseline Surface Go 1 skip this firmware if it's not too late. Bill from Canada -
I own a Fitbit Versa 2 and around St Patrick's day, 2022 I updated the device from the Fitbit app as it was suggesting there was a new version. A few days following the update I noticed my sleeping data wasn't being tracked and that my heart rate was constantly reading 77 and not changing. I then tried power cycling the device and eventually resetting to factory defaults, and every suggestion I could find from googling the issue and looking at people who were reporting similar issues but nothing worked and now the heart rate is just reading nothing. During this i also noticed that I wasn't the only one having this issue, I have seen dozens of posts with usually a more then 3 people saying they also had their versa 2 devices heart rate function stop working after the most recent update, and some people had their devices brick entirely after updating not allowing the device to go beyond the initial startup logo. Along with the posts of people having the same issue being high in number, so were the number of people very angry as Fitbit was just responding with generic suggestions like "Go to settings and turn on the heartbeat function", and "try this specific steps to restart or reset the device". Fitbit has a 1 year warranty for its products except in Europe where 2 years is the requirement by law, and given that the Versa 2 launched in the Summer of 2019 and its successor arrived a year later in the Summer of 2020 i think it's fair to say that majority of Versa 2 holders are outside their warranty period. I don't really have a problem with the 1 year warranty, but from every person I've seen post about this issue and myself included all Fitbit had to say in response was "Did you try restarting it?", then after that they go right to warranty where I would bet that majority of people are outside their 1 year and they then say they can't cover it under warranty and give a code for 35% off a Fitbit device on their store. I've asked if they have any plans to attempt a fix by rolling out a new update but I haven't heard back on this yet. I had the device for 2.5 years without any issue and following that update the main feature of the device no longer works. I don't know if this is planned obsolescence or mere incompetence but either one is disgraceful. I would recommend staying away from Fitbit products if you care about e-waste or having a company brick your device and then claim "We can't do anything to fix this as its outside warranty" despite that the only reason its broke is an unnecessary update they pushed out. Below is a link to one of the forum posts and I've attached my correspondence with customer support. https://community.fitbit.com/t5/Other-Versa-Smartwatches/Versa-Sudden-Malfunction/m-p/5118251#M268554
-
i needed to secure erase my ssd and i used parted magic ,i took it two minutes to erase and it said the stauts is finished but stuck in that for an hour ,i had to hard reset the PC and now the ssd is gone and not showing either in the bios or parted magic ,please what i can do ?
-
Ok, So my laptop is the MSI GE62 6QF, and it comes with a 150 watt power brick. I have a unlocked gpu vbios and my core is overclocked +212 mhz, memory +595mhz, and a +75mv, and it's stable. So my problem is that according to MSI's Dragon gaming center, I am peaking at a 208 watt power draw (Not consistently). It's not draining my battery so all the power is coming from the power brick. Please note that I have been using the overclock for a while now and there doesn't seem to be an issue, and the power brick doesn't get hot or anything. Do I have an issue? Also for all the fools about to tell me what an idiot I am for overclocking my laptop that much, A) it's stable & B) it's cool (75 degrees celcius) And C) It's my laptop I do what I want.
-
So my Keyboard (Deck Hassium Pro) has been acting up so i went to their site downloaded the correct firmware and their utility and picked the correct firmware picked they keyboard and it said reset failed and Global full, now its an unrecognised usb device that doesnt work the retailer said if its faulty theyll replace it but if its a firmware issue ill pay for shipping so i dont wanna waste their time and my money someone help me please <3
-
Hi, Just been using a new streaming service on my mobile. But have encounted issues when streaming through the desktop App on my pc. Due to the Foxtel Go app isnt supported on my smart tv. The only solution Ive come up with is to manually download the apk file and install it. But Im scared that it may brick my smart tv.
-
Model: GS73VR 6RF (Stealth Pro 4k) CPU: i7 6700HQ GPU: GTX 1060 / 6GDD5 Panel: 17.3" 3840x2160 ips RAM: DDR4 2x8GB HDD: 1TB+256GB SSD OS: Win10 The laptop suddenly turned off in the middle of my sister's work,and doesn't power back on even when plugged in. Was looking into RMA in northern ireland but closest we found on Msi's website was some place in the UK that required it to be posted in. She bought the laptop in singapore and left the box there,so i'm not to sure how she's going to be able to ship it there in time. She's stressed out about finished her work in time,so i'm just wondering if there's anything that can be done to get through the RMA faster ,reviving it from the dead or if there's a RMA center in Belfast,Northern ireland. She can't access the battery,its under the "warrenty void if remove" sticker She doesn't have a voltmeter or a ampere meter to measure voltage or amps
-
So i bricked my phone (S7 Edge) by taking out the sim card tray while the always on display was on. Now it doesn't respond to power, screen, or the buttons.... HALP (gonna wait 4 the battery to die, I'll see what happens)
-
So...I messed up. Something in me thought using Upscale to put my phone at 1440p and I didn't realize that it doesn't use Substrate, so rebooting doesn't remove it. Basically, I put my phone in 1440p and rebooted, so now A) I can't Touch ID into my phone, B) can't see anything, and C) now have clinical depression. I have the PP Jailbreak, so how do I fix this? i cant login to press "Trust" on my phone, as that is what I need to do to activate iTools, iFunBox, iExplorer, etc. because if I try pressing on the screen when I guess at the passcode screen, I can't press any numbers that are not in the center, so I cannot press 1, 3, 4, 6, 7, and 9, along with the backspace key.
-
I don’t know why, but I honestly really don’t feel like I’m liking my Moto Z as time went on. First of all, this was more or less a phone that I got to replace my recalled Note 7. At the time I got it, I was pleasantly surprised. The screen was nice, the camera didn’t seem to be that bad and it performed splendidly on Android Marshmallow. Heck, the Motomods also seemed quite cool and the battery life wasn’t so bad. Then Nougat hit. Nougat wasn’t bad on its own. But when my OTA arrived, it bricked the phone and showed the ominous “Your device has failed verification and may not work properly”. I called up support and they told me that they are unable to do anything because it wasn’t purchased in the same country (even though it is the same model and runs on the same regional firmware). Reluctantly, I resorted to unlocking the bootloader, permanently voiding my warranty in the process, and resorted to learning how to flash a factory image to get it back up and running. With that settled, I went on to flash Nougat, and it wasn’t roses. The phone got very hot easily, battery life tanked and it very easily throttled, to the point where even pressing the home button took 10 seconds to register. I flashed newer firmware and even swapped kernels and changed governers to help make it more bearable, but it never performed like it would on Marshmallow. I also grew less fond of the Motomods. I currently have the Mophie mod and it was uncomfortable to hold the phone caseless as it got very hot on the sides and needed to remove the pack to make it cool down. Honestly, I question why I got it in the first place. Guess I got suckered into the modular hype that I now realize that I ended up trading a fair bit of usability for that. Guess I’m going to get a new phone sometime in 2018.
-
Ok I'm planning to change my Mobo for a Crosshair VI HERO ( Currently I'm using Gigabyte Gaming 5 ) but now I'm bit worried. What's all these Auto BIOS Update and Bricking the board I'm hearing about all over the internet ?? People claiming that, one day all sudden when they turning on their PC the BIOS is automatically updating and end up bricking their boards ? ( No they didn't turn off the PC, it just brick itself )
-
About a year and a half ago I built two system with the very same components for very light office and browsing workloads, which were based on a I3-6100 and a AsRock H170 Pro4. I used a VS450 Corsair power supply at the time. They were working perfectly for about 6 months, then one of the two systems started to have a strange problem: it did post and I could enter BIOS without issues, but once it started loading Windows 10 (before asking for the password) it always got stuck there forever. At the time, I tried a lot of things expecially for reinstalling the OS (Tried different OS versions, even older windows editions, different hard drives and SSDs..) and they never worked. So in the end I changed both the motherboard and PSU and it got working again perfectly (after another clean install). Using the PSU on a different system or the motherboard with a different PSU made these two actually work flawlessly. So I forgot about that and moved on. Now a year later, the other system has the very same problem and it starts to look way too strange than it already was and I really would like to find the cause of that issue. Any suggestion?
-
Hi. I thought about attaching a couple of magnet stripes to the back of the board/shelf under the TV and then hot-gluing small metal stripes to the power bricks that are used by devices that are stored there. Is it safe to have it like that, or can this type of magnetic interference harm a power supply brick? Thanks.
-
Heads up guys, the Crosshair VI's new 7002 BIOS will cause a soft brick upon updating if you're coming from a BIOS older than 6903. This includes versions 6808 and 6401. So if you want to update for Ryzen 3000 support and you're on a BIOS older than 6903, you'll need to sequentially update to 7002. Eg 6401 -> 6808, 6808 -> 6903, 6903 -> 7002 If you have already attempted a "jump flash" and got a soft brick, the USB flashback feature may or may not work. The ASUS ROG forums had some posts mentioning the BIOS flashback button not working (basically full bricks) after the update. My own Crosshair VI was able to restore back to 6401 after the 7002 soft brick, but results may vary. Hope this prevents some headaches and stops you guys from buying new boards. -
So I have went completely nuts when it has come to building my first gaming pc. It is stupidly expensive and I believe I have bought bad parts in terms of cooling or utilising my GPUs to its full potential. Any advice on which parts I should switch to fully utilise my GPU. I don't mind the slight bottleneck with my cpu and GPU its mostly the motherboard I'm afraid of. CPU: i5 9600k GPU: Msi rtx 2080 ti gaming trio motherboard: msi z390 - a pro ram: 2x 8gb corsair vengeance 3200mhz power supply: corsair Corsair VS650 650 W Active PFC 80 PLUS Certified Power Supply Unit case: EMPIRE GAMING - WarFare PC Gaming unit - Black - Red LED: USB 3.0, 3 x 120 mm LED Fans, Smoked transparent side panel - ATX/mATX/mITX fan: Cooler Master Hyper 212 EVO CPU Cooling System storage: m.2 Samsung monitor: Asus rog yes I know I'm a noob.
.thumb.gif.1b5395b31b6674b36f965263eca150b2.gif)
