Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Search - "boot loop"
A recruiter called today.
A new job proposal. Higher salary, manage some 5 men team, DevOps buzzwords, cool product, great conditions but then she says "and we're working only in Windows environment".
My ears ringed "only in windows env".. "only windows"... "windooowwssss".
"Nope, thanks, have a good day!" - hung up.18
My wife's phone started having power button issues. Then it broke completely with spastic random presses, causing the phone to boot loop. It's a 3 year old Nexus 5 so I was mostly concerned with backing things up, not rescuing it.
Cleaning didn't work, tapping the switch didn't work. This hack worked.
TL;DR: My devices all hate me and I needed to fix them all.
My Devices really love me.
I rooted my smartphone (LG G5) just yesterday. Everything went fine. Installed TWRP, SuperSU and some nice Apps that utilize root.
Today I was on the go (at CeBIT) and already had the Xposed Installer App on my phone, but didn't attempt installing it yet because I needed my phone for Maps and Messaging and the app had given clear warning about the bricking-potential.
So to the end of the day I get bored, send my last important Messages, installed the Xposed Framework...
... aaaand got stuck in a boot loop.
So I got on my way back home (thanks God I remembered all the trains I needed to take). On the way I had a lot of fun in the Recovery-Terminal and figured that I should be able to fix my phone with no problem at home because the installer made backups (unlike myself).
Coming back home and my pc was still running (should've shut down after installing updates).
The pc behaved odd and I couldn't shut it down properly, which led to cutting the power.
And upon booting my pc I got a ... give it a guess ...
...a bootloop (technically the animation just never ended).
So after I fixed my phone with my spare laptop (just transferred and executed the uninstaller for xposed) I fixed my PC too, which had an old broken dkms-driver.
The odd thing about this is, that this isn't technically a rant. I guess you can confirm that you can't find any swear words.
Because I ENJOYED fixing the devices. I already fixed my pc a couple of times was well as unbricking my rooted phones, so there was fairly little research involved.
I guess I'm now offically twisted.
Now, after my smartphone backups are transferred, I'Ll take my device apart and replace the camera glass which arrived today (and hope, no pray, that my sim card does still work after that)...
... after I blatendly copied a meme to get more attention. 😉3
Wanted to play a new game this WE.
It's quite demanding so decide to boot into Windows, because NVIDIA driver support.
Haven't booted Windows 10 in a month so I start early in the morning to do the updates.
After about 3 hours all Windows and steam updates were installed and I finally start the game.
I play for a couple of hours until suddenly - blue screen
I rebooted and was faced with another blue screen right after the Windows logo. Didn't even reach the login screen.
So here I am with a Windows install that is stuck in a boot - blue screen - boot - system repair - blue screen loop and a shitty gaming WE.
In fact I'm a sinful dev, so that I can't easily decide which one is worst. From indenting with tabs, or using nano instead of vim/emacs, to hardcoding database credentials on server, to many hacks and workarounds I use as actual "fixes" when the deadline is upon me and I've tried all I could. But it always led only to my own regret. For instance, my latest sin was that I prefered Debian over Arch and used proprietary graphic drivers to speed up my new setup. But ended up with a curse from St. Ignucius. (check my last rant)
But my worst sin probably goes to when I was "printf-debugging" some issue for a GSM controller on a raspberry pi. I forgot to remove one little print line and deployed the new "fixed" version. I didn't follow that project after that for like a month or so, when the client posted back the device and said that "it just doesn't work anymore". It seemed that raspbian didn't boot beacause the sd card was curroptted. I dd'ed through the card and I noticed that there are billions of lines of "DEBUG:: reading stream from 192.some.shitty.ip", took almost all over the 32G sdcard. Just as I suddenly remembered the cursed line I just added a month ago, I declared the sd card dead with no hesitation, dunce-commented the line (so the history would remember), implemented a time out for the thread containing it, setup a journald unit for my service and removed the redirection of process output to a log file, found a new sd card and installed everything again, and finally posted back the new "fix" to the client.
Moral: Never comfort yourself for the sins you have commited in the past kids, they certainly will come back to you. And also not to do any io especially write to a file on an SD card with ext fs, in a potentially infinite loop with no timeout.
P.S: I'd posted my last rant just before the new week rant last nigh. I really liked the St. Ignucius meme so decided to create a new one. He's very adorable :)1
WTH.... Did my laptop finally die and enter into a boot loop or is Windows Updating?
Either way FML.... How long should I wait?7
Help, please :D
My girlfriend came to visit me and now her laptop is bricked (boot loop). She has the WIP of fall creators.16
Autodesk + Linux is such a goddamn clusterfuck.
Firstly, they only release RPM builds for Maya, and say that they officially support RHEL and CentOS only.
No support for Debian, Arch, etc. What. The. Fuck.
Fine. Okay. Corporate policy. I can live with that. I use alien to convert the RPMs to DEBs on my ZorinOS installation and then found a script which does the installation for me. Cool.
Installs with a few library fuckups. Okay, no problem. I added the missing library versions (ancient libpng and libtiff). I run it. It throws up with some error involving licensing.
Upon searching it seems that Maya 20-fucking-17 can't handle the "new" consistent device naming system (the one which renames eth0 to enp1s0 or whatever). WHAT THE FUCK. Okay. Found a way to disable that. No effect. It's doing the equivalent of a boot loop with the same error.
Wow. This is the leading player in 3D content creation software :/
(As an aside, I did try to install Fedora 28 but it keeps failing with a TPM error. Yay for Linux distro quirks).1
I HATE SURFACES SO FRICKING MUCH. OK, sure they're decent when they work. But the problem is that half the time our Surfaces here DON'T work. From not connecting to the network, to only one external screen working when docked, to shutting down due to overheating because Microsoft didn't put fans in them, to the battery getting too hot and bulging.... So. Many. Problems. It finally culminated this past weekend when I had to set up a Laptop 3. It already had a local AD profile set up, so I needed to reset it and let it autoprovision. Should be easy. Generally a half-hour or so job. I perform the reset, and it begins reinstalling Windows. Halfway through, it BSOD's with a NO_BOOT_MEDIA error. Great, now it's stuck in a boot loop. Tried several things to fix it. Nothing worked. Oh well, I may as well just do a clean install of Windows. I plug a flash drive into my PC, download the Media Creation Tool, and try to create an image. It goes through the lengthy process of downloading Windows, then begins creating the media. At 68% it just errors out with no explanation. Hmm. Strange. I try again. Same issue. Well, it's 5:15 on a Friday evening. I'm not staying at work. But the user needs this laptop Monday morning. Fine, I'll take it home and work on it over the weekend. At home, I use my personal PC to create a bootable USB drive. No hitches this time. I plug it into the laptop and boot from it. However, once I hit the Windows installation screen the keyboard stops working. The trackpad doesn't work. The touchscreen doesn't work. Weird, none of the other Surfaces had this issue. Fine, I'll use an external keyboard. Except Microsoft is brilliant and only put one USB-A port on the machine. BRILLIANT. Fortunately I have a USB hub so I plug that in. Now I can use a USB keyboard to proceed through Windows installation. However, when I get to the network connection stage no wireless networks come up. At this point I'm beginning to realize that the drivers which work fine when navigating the UEFI somehow don't work during Windows installation. Oh well. I proceed through setup and then install the drivers. But of course the machine hasn't autoprovisioned because it had no internet connection during setup. OK fine, I decide to reset it again. Surely that BSOD was just a fluke. Nope. Happens again. I again proceed through Windows installation and install the drivers. I decide to try a fresh installation *without* resetting first, thinking maybe whatever bug is causing the BSOD is also deleting the drivers. No dice. OK, I go Googling. Turns out this is a common issue. The Laptop 3 uses wonky drivers and the generic Windows installation drivers won't work right. This is ridiculous. Windows is made by Microsoft. Surface is made by Microsoft. And I'm supposed to believe that I can't even install Windows on the machine properly? Oh well, I'll try it. Apparently I need to extract the Laptop 3 drivers, convert the ESD install file to a WIM file, inject the drivers, then split the WIM file since it's now too big to fit on a FAT32 drive. I honestly didn't even expect this to work, but it did. I ran into quite a few more problems with autoprovisioning which required two more reinstallations, but I won't go into detail on that. All in all, I totaled up 9 hours on that laptop over the weekend. Suffice to say our organization is now looking very hard at DELL for our next machines.4
*trying to install arch linux for the first time*
> system goes into a boot loop
> cant get into BIOS
> taking pc apart rn8
Windows Update prompted me to install the 1809 update for Windows 10 recently.
I left the machine for a while and came back to find it frozen at a completely blank screen.
It eventually restarted...and got stuck in a continual loop where the Windows logo would flash for a second and then instantly restart again.
The restart occurred so early in the boot process that I couldn’t even get it into recovery mode or do anything with it to fix it.
So I had no choice but to reinstall Windows from scratch and reinstall and restore all my software and files. Took about 7 hours.
Fed up with f@_#-$&@_ Microsoft bullshit, computer refused to install IIS without a reboot first. Rebooted, got bluescreen with some error like APC_Index mismatch since it was hooked up to an external monitor (this has happened before, but only when booting into Windows, not Ubuntu), god knows why now since it was hooked up to same monitor before reboot and worked just fine. All this because some stupid school related task requires Visual Studio and a web project-solution that takes ages to run/debug which I would rather build and devug through attaching remote debugger to the running IIS-process. Instead I get into a boot-loop when the screen is connected, and when I connect the screen after a normal boot it restarts itself. Why is it always like this? Most of the time is spent just to setup the environment or making Windows work. F#&#_ this and the assignment, goodnight.1
I bought a Samsung Galaxy S7 Edge from my cousin for $450. I then proceeded to root it and everything was fine for a week or so before my phone went into an infinite boot loop after an OTA update.
In the process of trying to fix it, I accidentally flashed a bootloader, unaware that Samsung has the bootloader locked. As a result, I had a completely bricked phone.
I mean legit bricked. No buttons with work and the screen remained shut and I couldn't flash anything over it again to try to repair it. I couldn't even put the phone into recovery mode. I now had the world's most expensive paperweight.
However, I managed to convince Samsung to repair it for me for free! I told them that the phone just stopped responding after an OTA update from them, which isn't so far from the truth.
I only ever had to flash things on the phone to begin with because of their update. Honestly, I wouldn't has had to deal with this problem, and neither would Samsung, if they just didn't lock the damn bootloader! Why are these companies taking away are independent control of our own devices?
Moral of the story: DON'T flash over a locked bootloader EVER or you will end up with a completely brick device, with no solution other than to open it up and replace the motherboard entirely.12
My past 16hours activities
Woke up > destroyed a healthy running environment while trying to setup dual monitor on my manjaro kde > found out the nvidia driver was the culprit the whole the > the whole thing was a PITA > reinstalled the kde with windows dual boot > did the previous task 4/5 times till I felt satisfied ( call be a dumb but it is what it is ) > and now after wasting the whole fucking day I am setting up the environment finally.
Still I'm not sure if I'll be able to finish this shit before 4 am in the morning . It's now 1.26 AM .
Life is an interesting loop of hell .5
Oh, crikey: Windows 10 "Inaccessible boot device". Good old "bootrec /fixboot" didn't work, and any claims that "automatic repair" does anything useful is apparently bollocks.
So for the first time ever, I had to use a restore point to revert the system to where it was before Xamarin was installed. The prime suspect for this cock-up is Intel HAXM, since I don't belive anything else in Xamarin possesses the power to accomplish a boot loop.
The more problems I encounter with Windows the more I have the impression these infested chimps never implemented a real system repair/restoration feature but just faked it with randomized error messages.
Now Windows 10 can't even rollback updates anymore but lands in an infinite boot loop that even a reset to an earlier restoration point won't fix.
And the Windows repair option lists two Windows installations even though there's just one.
Somehow the roles of Linux and Windows have switched nowadays, by now I had to reinstall Win10 5 times on three PCs in the last 12 months.
Windows 8 was shit too but at least it didn't fucking break within a week.3
Just fixed my broken htc one m9 (boot loop after legitimate update) by powering it up month after putting in back to box for future repair. Who to blame? NSA? Android 7? SD Card?
Oh this is fun... PSA: do not upgraade to Android Pie if you want root....
Trying to recover again now that after flashing Magisk i get a boot loop....9
My phone got stuck in funky restart boot loop yesterday. The first 2 restarts was odd but after 3 cycles, I started panicking. Went on my PC, googled for all kinds of button combinations of power button, volume button, back button, and home button to get into fastboot, recovery and safe mode to see if I can clear stuff or at least get backup of my stuff. I also tried taking the battery out. Nothing works, except when I factory reset.
Everything was new again and as it booted up, I have to remember to change my authentication keys in LastPass, my private ssh key in Krypt. But fortunately, Google remembered all my apps and suggested if I wanted to install them again since it recognized my phone was an old phone. Thanks for tracking me Google. And now since its a reset, everything is clean, no cache, cookie, and some of my music files are all gone. Well at least its fast like before.2
So one of my co-workers had issues with his MKP 2010, it wasn't booting up, wasn't charging, basically acting as a brick. He went everywhere around the office asking other to revive it. I was the last person - my duty was to take out the hard drive and trash it.
I asked him if I can keep it, he allowed me to do so.
After a couple of days I got back to it, installed a hard drive, which I had from my friend from a while ago.
- Played around with charger, got it charging
- Boot it up to recovery mode (I was very excited when I saw that globe spinning)
- The Wi-Fi didn't connect, used LAN
- Formatted drive, installed OS
- Got to endless loop of recovery mode
- Found out that the digits on the keyboard type lower line of letters.. :/
- Boot to safe mode - worked
- Endlessly booted to recovery mode as I tried to get to boot menu
- Realized that the left Shift, Control, and Option does not work
- Used external keyboard and got to boot menu
- Still no success with booting to regular mode
- NVRAM reset!!!!
- Booya! It works!
Should I bother and replace the keyboard? I mean it doesn't matter that much, probably will give it to my mother :)1
Fastboot I LOVE U!!!!
Somehow entered into a boot loop after enabling a EdXposed module.
LineageOS recovery sucks, has no terminal so can't disable magisk modules... only can mount system, not data....
So dumped LineageOS's payload.bin and flashed the clean boot.img11
So I've been using Duet on my iPad Pro for a couple years now (lets me use it as an external monitor via Lightning cable) and without issue. Shit, I've been quite happy with it. Then the other day, whilst hooked up to my work laptop, there was a power fluctuation that caused my laptop to stop sending power to connected devices. Which is fine - I have it plugged into a surge protector so these fluctuations shouldn't matter. After a few seconds the laptop resumed normal operation and my connected devices were up and running again.
But the iPad Pro, for some reason, went into an infinite boot loop sequence. It reboots, gets to the white Apple logo, then reboots again.
In the end, after putting the iPad into recovery mode and running Apple's update in iTunes (as they recommend), it proceeds to wipe all my data. Without warning. I lost more than a couple of years of notes, illustrations and photos. All in one fucking swoop.
To be clear, you get 2 options in iTunes when performing a device update:
1. UPDATE - will not mess with your data, will just update the OS (in this case iPadOS)
2. RESTORE - will delete everything, basically a factory reset
I clicked UPDATE. After the first attempt, it still kept bootlooping. So I did it again, I made sure I clicked UPDATE because I had not yet backed up my data. It then proceeds to do a RESTORE even though I clicked UPDATE.
Why, Apple? WHY.
After a solemn weekend lamenting my lost data, I've come a conclusion: fuck you Apple for designing very shitty software. I mean, why can't I access my device data over a cabled connection in the event I can't boot into the OS? If you need some form of authentication to keep out thieves, surely the mutltiple times you ask me to log in with my Apple ID on iTunes upon connecting the damn thing is more than sufficient?! You keep spouting that you have a secure boot chain and shit, surely it can verify a legitimate user using authenticated hardware without having to boot into the device OS?
And on the subject of backing up my data, you really only have 2 manual options here. Either (a) open iTunes, select your device, select the installed app, then selectively download the files onto my system; or (b) do a full device backup. Neither of those procedures is time-efficient nor straightforward. And if you want to do option b wirelessly, it can only be on iCloud. Which is bullshit. And you can't even access the files in the device backup - you can only get to them by restoring to your device. Even MORE bullshit.
Conversely, on my Android phone I can automate backups of individual apps, directories or files to my cloud provider of choice, or even to an external microSD card. I can schedule when the backups happen. I can access my files ANYTIME.
I got the iPad Pro because I wanted the best drawing experience, and Apple Pencil at the time was really the best you could get. But I see now it's not worth compromise of having shitty software. I mean, It's already 2021 but these dated piles of excrement that are iOS and iPadOS still act like it's 2011; they need to be seriously reviewed and re-engineered, because eventually they're going to end up as nothing but all UI fluff to hide these extremely glaring problems.2
So my win10 PC with everything I have on it just got trapped in a boot loop, because I tried to start a VM.
No backup, no rescue DVD, noone here that could help me but myself.
Well I guess that is what I deserve for trying to try out a Linux system.
Luckily my project deadline is 3h away, so I have still time to fix this mess and start working.
Wish me luck guys.4