It looks like you're new here. If you want to get involved, click one of these buttons!
TLDR; updated phone to a newer OS after WPA2 exploit, set over night to update, downloaded Android 7.1.1, phone worked normally the first day until it ran out of battery and the next time it was booted, it got stuck in a bootloop. Phone gets stuck on Axon screen and vibrates as if it is about to open the system, and it gets the phone's brightness preferences and dims the screen, makes a mechanical noise after the vibration and then after a few seconds loops back around and screen becomes bright again
Hello Everybody, I hope all of you are having a good day,
So a week or so ago, the WPA2 Krack news have gotten to me, and I decided that in the best interests of my internet security, I ought to update my OS on my ZTE Axon 7, since I read online that the newer updates fix the WPA2 exploit.
With a quite large amount of battery left, I decided to do the update overnight, so there is less downtime for me. I plugged in the phone into the original ZTE charger (to make sure the battery doesn't run out), and then went to settings and update. Since it was late at night, I don't remember exactly what version of Android I was updating to. It had some launcher logo like the MiFlavor logo or some other weird desktop environment I downloaded a long time ago to use with a Windows 98 theme pack, it had given me some problems before, like I had to choose which desktop environment to use every so often as the phone would ask me "what app do you want to you to launch this"? or something like that.
Nevertheless, I'am not 100% sure, but I think the version of Android that I was updating to was something like 7.1.1 ??? It was late at night and my mind was a little hazy, I usually pay more attention to these things. Anyways, I pressed the update button to download the new OS, and I had just remembered that I needed to set my alarm clock to 7 am (although this was quite redundant). The OS said on the update screen that it would need a "manual restart" or something like that, but I had thought that it would just shut off by itself and then in the morning I'd be able to restart it.
Anyways, skip ahead a few hours, and in the morning, I turned on my phone, and it took a little bit longer to launch, It didn't say anything about the update when I turned it on, as if no update was ever done, nevertheless, it turned on and everything seemed fine. I have a widget installed on my phone called "CoolTool" Which displays Memory usage, CPU usage, and graphs the hardware utilization on a nice transparent surface in the top left hand corner of the screen. CoolTool displayed 100 % CPU usage (which it very rarely gets to) for a few minutes and the phone started to lag. This cleared up in a while. I didn't really like the new system, it seemed more laggy and the user interface how I could swipe up and down to see my notifications was rehauled and I really hated how I had to swipe up all the way through all my notifications in order to have the notifications bar go up. It wasn't too bad, I thought I could get used to it and I did pretty quickly.
Up until when I was at 15% battery, II gave my phone to my dad who checked some of his bank accounts / social media sites that he has on my phone, he was one of the last people to use it before it entered a bootloop. I had the phone lie around near a 3d printer (my homemade prusa i3 MK2) and checked different ways to calibrate my printer. Then my dad had used the phone a little bit more, and then I noticed it had only about 5% battery. I don't remember exactly what led up to this, but the phone ended up on my piano table, and for whatever reason I heard a lot of vibrating noises from far away, much longer and more vibrations than it usually gives off when it shuts off due to low battery.
When I went to eat, I took my portable battery charger that I usually use to charge my phone when I'am far away from an outlet, like when I'am eating, I pretty much always use my Axon when I eat. I had plugged in my charger and I had some weird things happen when it charged, it kind of stopped charging (I think) and then when I tried to turn it on when I thought it had the minimum amount of battery needed to boot, it would say it has too little battery. I'am not sure but it might of started turning on and then shut off while it was booting (although this is really hazy for me, this might of never happened, probably never did). So I sat there and ate my food for about an hour or so and it kept on the Axon screen.
At this point, I knew something was wrong, but I didnt know how to fix it, so I left it on the bootloop for a while and had it run out of battery several times since I didn't know how to turn it off through recovery mode.
**When I turn on my phone, It goes through the ZTE splash screen and loads the golden Axon screen. It loads for a bit, but then it gives a very short vibration like it usually does seconds before displaying the OS and fully loading it on-screen, AND THEN, the Axon letters become dimmed a little bit as the phone loads the OS preferences for 50% brightness like it usually does, SO THE OS IS THERE and it remembers that last time I set the screen brightness to 50%, but then after it gives a vibration and dims, it gives off a very quiet mechanical noise inside the phone as if though something is broken, like a tiny click, sometimes there are two at once and other times there's only one click. (this may though, be attributed to the vibrator motor resetting). This happens about 1.5-2 seconds after the short vibration. It then loads for a few more seconds, and then the Axon splash screen BECOMES BRIGHT AGAIN, as if it loops back again to its previous state and then loads a bit, becomes dimmer, vibrates and creates a mechanical noise again!***