This is awesome.

Window...update available... Later
And now ?
Later
And now?
Later
And now?
Later
And now?
Later
And now?
Finish my day, do it fucker but tomorrow you need to work

Today ... Bootloop

Mother fucking ☮️ of shit

!rant & story_time
This happend to the startup I was working for at ~2011. I was a junior Android dev, working on a very popular app.
During experiments for a new feature, I discovered that the system AlarmManager has a serious bug - you can set a repeating alarm with interval=0ms. If your app takes more then 1 ms to handle the Intent, then the AlarmManager will start to fill up the intent Queue, with unexpected results to the OS. causing it to slow down, and reboot when it ran out of Ram. Why? my guess was that because the AlarmManager was part of the OS, then any issues caused by it caused the system process to ran out of ram, crashing it, and the whole system with it. the real kicker was that even after a reboot, the AlarmManager still had Intents queued, causing the device to bootloop for a while, untill the queue was cleared. My boss decided to report the problem to google, as this was an issue in the OS. I built an example app, that caused the crash 10-30 seconds after starting, and submitted to Google. Google responded later that day with "not an issue, no one will ever do this".
Well... At this point I decided to review the autoupdate feature in our app, to make sure this will not happen to us. We just released a new feature where a user can set an update schedule option in the app settings - where you could setup a daily, weekly, or hourly update for the app. after reviewing it, It looked good, and the issue was not triggered in the manual QA I did. So, it was all good. And we released an updated version to the store.
After we did an update-install, we discoverd that, there was a provlem reading the previous version SharedPrefs value for the update schdule settings, and the value defaulted to 0...
the result was, our app caused all our users to go into a bootloop, and because the alarm was reset when the devices booted up, the bootloop could only be solved in a factory reset, or removing our app, before the device rebooted, and then waiting a few reboot cycles.
We lost 50 places in the market, and it took us 6 months to get back to where we were.

It was not my fault, but it sucked big time!

*wondered for 4 years how a bootloop looks like*
Nexus: yOU wAnE kNoW wHaT a BoOtLoOp LoOkS LiKe?!

*bootloops itself to shit*

Well I guess that I know what I'll be doing tonight then. Flash that new StatixOS build because the phone shat itself.

*tries to reflash the recovery*
*still bootloops*
*tries to flash the stock OS*
*still fucking bootloops*
*finds a post on XDA saying something about fucked big cores that need to be disabled*

Fucking piece of junk. So not only the battery is shit, but also the CPU is shit, huh. Certified pieces of shit.

*flashes the patched boot.img that disables the big cores*
*phone loads Google logo.. good*
*BOOTLOOPS FUCKING AGAIN*

MJHUIETHNIUBESZPTUIBG ESVGU d

FUCK!!! Fuck you Google, fuck you Nexus, fuck you Huawei, HOW DIFFICULT CAN IT BE TO DESIGN A FUCKING PHONE?!!!

So yeah. Looking for suggestions for a new phone. Anything of which the kernel source is released and of which the battery is halfway decent (unlike this fucking piece of shit) should do.

Oh fucking Huawei.
Fuck you.
Inventory:
- Honor 6x (BLN-L22C675)
- Has EMUI4.1 Marshmallow
- Cousin brother 'A' (has bricking XP!)
- Uncle 'K'
- Has Mac with Windows VM
Goal:
- Stock as LineageOS / AOSP

Procedure (fucking seriously):
- Find XDA link to root H6X
- Go to Huawei page and fill out form
- Receive and use bootloader code
- Find latest TWRP
- Flash latest TWRP
- TWRP not working? Bootloops
- XDA search "H6X boot to recovery"
- Find and try modded TWRP
- TWRP fails, no bootloop
- Find & flash TWRP 3.1.0
- Yay! TWRP works
- Find and download LineageOS and SuperSU
- Flash via TWRP
- Yay! Success.
- Attempt boot
- Boot fails. No idea why
- Go back to TWRP
- TWRP gives shitload of errors
"cannot mount /data, storage etc."
- Feel fucked up
- Notice that userdata partition exists,
but FSTAB doesn't take
- Remembers SuperSU modded boot
image and FSTABS!
- Fuck SuperSU
- Attempt to mod boot image
- Doesn't work (modded successfully
but no change)
- Discover Huawei DLOAD
Installer for "UPDATE.APP" OTAs
Note: Each full OTA is 2+ GB zipped
- Find, download, fail on 4+ OTAs
- Discover "UPDATE.APP Extractor"
Runs on Windows
Note: UPDATE.APP custom format
Different per H6X model
- Uses 'K''s VM to test
- My H6X model does not have
a predefined format
- Process to get format requires
TWRP, which is not working
- FAIL HERE
- Discover "Firmware Finder"
Windows app to find Huawei
firmwares
- Tries 'K''s VM
- Fails with 1 OTA
- Downloads another firmware ZIP
- Unzips and tries to use OTA
- Works?!
- Boots successfully?!
- Seems to have EMUI 5.0 Nougat
- Downloads, flashes TWRP
- TWRP not working AGAIN?
- Go back to XDA page
- Find that TWRP on EMUI 5 - NO
- Find rollbacks for EMUI5 -> EMUI4
- Test, fail 2-4 times (Massive OTAs)
- DLOAD accepts this one?!!!
- I HAVE ORIG AGAIN!!!
- Re-unlock and reflash TWRP
- Realise that ROMs aren't working on
EMUI 4.1; Find TWRPs for EMUI5
- Find and fail with 2-3 OTAs
Note: Had removed old OTAs for
space on Chromebook (32GB)
- In anger, flash one with TWRP
instead of DLOAD (which checks
compatability)
- Works! Same wasn't working with
DLOAD
- Find and flash a custom TWRP
as old one still exists (not wiped in
flash)
- Try flashing LineageOS
- LineageOS stuck in boot
- Try flashing AOSP
- Same
- Try flashing Resurruction Remix
- Same
- Realise that need stock EMUI5
vendor
- Realise that the firmware I installed
wasn't for my device so not working
- FUCK NO MORE LARGE DLs
- Try another custom TWRP
- Begin getting '/cust mounting' errs
- Try reflashing EMUI5 with TWRP
- Doesn't work
- Try DLOADing EMUI5
- Like before, incompatability
- DLOAD EMUI4
- Reunlock and reflash TWRP
- WRITE THIS AS A BREAK
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAARRRRRRRRRRRRRRRRRRRRRRRRGGGGGGGGGGGGGGGGGGGGGGGGGHHHHHHHHHHHHHH

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. 😉

Sent email to my parents this morning telling them to contact me by email since the Pie update broke my One Plus 6 (when I tried to reroot it but got a bootloop and restoring from TWRP screwed it up even more somehow) so restoring it.

First response from my dad: you can use my spare S9...

Yes he has a spare because he got it in a 2 for 1 deal... but I'm thinking uhhh..... It's not like I physically dropped the phone and cracked the screen... (like he did to his late 2 phones)... I'm 99% sure I can restore somehow... Like I did last time (a few months ago)

The new ticket / check-in terminals of the local busses apparently run on linux 😃
(Sorry for the bad pic quality)

!(!(!(!(!(!(!(!rant)))))))
My new HTC smartphone hates me.
First it started to shut down all of the sudden yesterday night, when I was solving quadratic equations on my laptop.
I thought that it might be due to low battery. So I have restarted it. After putting itself into a bootloop for 4 start sequences, it was able to fully start to the page where it told me to enter the security pin to decrypt my files. I also had 30 attempts left. Like a ransomware.

I was like "tf I didn't set anything up".
So I decided to use my first attempt as I had 30 attempts left.
I entered the pin (I can swear that it's correct) and it told me that it has to wipe the /data partition.

I did that. I pressed that button. After waiting for 30 minutes I gave up and rebooted into the bootloader.
Bootloader -> Download Mode -> wipe /data (stock rom + stock recovery btw.)

Some error with "e: mount /cache failed[...]e: mount /data failed"
So, I tried using the adb sideload - no success.
Fastbooted into RUU Mode - HTC keeps rebooting itself into the RUU Mode - no success

Tried to flash the firmware and twrp recovery from Download mode - no success
Then I tried to flash all these things from the sd card - no success

Searched for revolutionary (I know this from my old HTC sensation device).
It wasn't big of any help.

Then someone on xda recommended htcDev (htc's <b>developer-friendly</b> lol site)
I followed every step. Everything seemed to be okay.
I got to the last step.
I needed to get my encrypted token by entering "fastboot oem get_identifier_token" to be able to submit it to HTC, and after they would send me an e-Mail with an .bin file that would let me unlock the bootloader to be able to flash my way through all this headache giving fucking piece of dog shit!

But since I can't back to the phone settings to select the bootloader activation box that would let me get my token... but nah.

FML

------------
Sent by using the devRant web app (:\)

Didn't know this will happen anymore. Windows decided to kill itself and is now in bootloop.
The worst: last git push was two days ago

WTF WINDOWS, I SAID HIBERNATE AND SOMEHOW IT ENTERED INTO A BOOTLOOP WHEN I TURNED BACK ON... AFTER THE THIRD SHIT RESTART HIT GETS PAST IT N SAYS

WINDOWS IS INSTALLING UPDATES...

FIRST WHY.... 2ND FCKIN TELL ME THAT INSTEAD IF JUST SHOWING THE BOOTING SCREEN...

PC just crashed midgame amd started to bootloop afterwards... i guess my 1070 is not so stable :/ not even getting video signal anymore..

Older tech support story, but still a frusterating one.

Sister was running Windows 8.1 (ew) when Microsoft was ramming Windows 10 down everyone's throat.

Her laptop decided to update to Windows 10, and after waiting awhile, she decided to unplug the laptop's battery and power chord.

This did what you expected, corrupted her install, leading to a bootloop. I then got to deal with that to try and recover it.

Once I got into the recovery mode, it wanted her password to restore from a system image, guess what she forgot?

She tried her PIN, and gave up after a few attempts, and I got to reinstall Windows for her.

Lesson learned from this? If you're the IT person of the house, make sure that you have an account on all machines that you may administrate. That way you don't need to deal with this shit.

Finally made my node production server stable enough that I could focus on writing tests*. I start by setting up docker, mocking cognito, preparing the database and everything. Reading up on Node test suites and following a short tut to set up my first unit test. Didn't go smoothly, but it's local and there are no deadlines so who cares. 4 days later, first assert.equal(1+1, 2) passes and I'm happy.

I start writing all sorts of tests, installing everything required into "devDependancies," and getting the joy of having some tests pass on first try with all asserts set up, feels good!

I decide to make a small update to production, so I add a test, run and see it fail, implement the feature, re-run and, it passes!

I push the feature to develop, test it, and it works as intended. Merge that to master and subsequently to one of my ec2 production servers**, and lo and behold, production server is on a bootloop claiming it "Cannot find module `graphql`". But how? I didn't change any production dependencies, and my package lock json is committed so wth?

I google the issue, but can't find anything relevant. The only thing that I could guess was that some dependencies (including graphql) were referenced*** in both, prod and dev, and were omitted when installed on a prod NODE_ENV, but googling that specific issue yielded no results, and I would have thought npm would be clever enough to see that and would always install those dependencies (spoiler: it didn't for me).

With reduced production capacity (having one server down) I decided to npm uninstall all dev dependencies anyway and see what happens. Aaaaand it works.....

So now I have a working production server, but broken local tests, and I'm not sure why npm is behaving like this...

* Yes I see the irony.
** No staging because $$$, also this is a personal project.
*** I am not directly referencing the same thing twice, it's probably a subdependency somewhere.

My Windows 10 VM gloriously just shat itself so badly, it's now stuck in a BSOD bootloop (first time ever I managed to get a BSOD in a fucking virtual machine btw) and I need to reinstall it. So I need to download the newest Win10.iso.

But I'm also currently working on a university assignment that requires me to be connected to the university-network via a VPN that's slower than my 90s ADSL connection (~1Mbps) (see my previous rant). So to download the 4.7GB iso it'd take.... I'm bad at maths, so let's just say fucking AGES.

So I spin up another VM with a bridged network to download my Win10.iso with Gigabit speed to set up another VM.... wonders of modern technology

A Twitter API issue is allowing people to (once again) bootloop iPhones and iPads with the text parser. This was just submitted to Twitter's staff, I don't see anyone talking about it yet. Disable notifications or uninstall and use the mobile site.

when you're struggling to build small sized firmware on your 512Kb IoT Device resulting in bootloop every time... Then you see in the manual, that you have the 4Mb model and you frashed the rom to the wrong memory address for 2 weeks resulting in a bootloop... FML

I just set a admin password for my old dlink dir655.

Oh, you'll need to restart, sure

Now this fucking thing is stuck in a bootloop and I can't get a new one until tomorrow.

Why do I always default to formatting/resetting whenever I have a tech problem...

Android bootloop: reset device, lose all datas and reroot.

Root cause turned out to be need to uninstall Magisk first.

Today: Can't connect Chromecast even after restarting phone and Chromecast. Reset Chromecast completely, configured again fine but then can't connect again.

Root cause: router, router just needed to be restarted...

What was your first AMBITION when you landed a job?

Not really dev related but here it goes:

Decided to update some apps on my phone during lecture. Suddenly android crashes and is stuck in a bootloop. Went to safe mode where "downloaded" apps are disabled but wanted to at least be available via telegram. So I followed a guide to manually convert an app to a system app and tested with some random app that I didn't care for. That worked flawlessly and then decided to proceed with telegram but it said that moving failed but actually the folder was moved. I took the chance and rebooted (again to safe mode) only to find out that now the system ui crashes as soon as it loads, also rendering the safe mode useless.

Great that such things always happen when you don't have access to a trusted machine with adb installed.

Wanted to resize the /system of my Nexus for the Stock gapps with parted.
Deleted bootloader noooooooooo!

Someone an idea to fix this :/