Phone stuck on fastboot after magisk update - Google Pixel 3 XL Questions & Answers

This moring i opened magisk and seeing there was a new version i updated it, all went ok and it asked me to reboot. After rebooting i found my phone stuck on fastboot, is there any way to recover my phone without losing data?

Related

Unbricking a bootloop-ing Nexus 5x without losing data

Hi guys,
Need a bit of help. I was scrolling through Instagram when the phone froze, restarted, and now it just keeps restarting without being able to get past the Google logo. It did get to the colored dots ONCE after powering it down completely from bootloader. I was on stock 7.0 (but August or September security update), stock kernel, but rooted with SuperSU 2.76 and TWRP 3.0.2-1. I just downloaded the factory image and flashed the bootloader, boot, vendor, cache, system (radio is the same), and TWRP 3.0.2-1 and it's doing the exact same thing. I can't even boot into TWRP, it bootloops at the Google logo just the same. EDIT: I was able to get into TWRP once but the phone froze again and rebooted!
I would really like to recover my data partition if at all possible. Please help!
EDIT: I put it in the freezer for half an hour and when I took it out it was able to boot again. Copying my stuff now. Will update when it inevitably breaks again...
EDIT2: Once it warms up it freezes and starts to go into a bootloop again. Damn, most likely a hardware issue.

My devices gets superslow after intalling Magisk

So yesterday I decided to install Magisk, I was on 10.0.3.0 Android Pie stock image with TWRP installed. With the fastboot ROM in Xiaomi's web I created my own patched_boot.img for this version and then I rebooted into fastboot and used
Code:
fastboot boot patched_boot.img
after that, the phone stayed for 3-4 minutes in the fastboot screen and then rebooted. The booting process was superslow, it took almost 10 minutes and when it finally showed me the screen to put my pin, i wasn't able to write it at the moment, since the phone started to freeze. After several minutes of waiting I was able to unlock my device but navigating to the Magisk Manager app to install it directly was a pain in the ass, constant freezes, lots of lag... but with patience I was able eventually to install it. Pressed reboot and the same history, booting process i superslow, theres a lot of lag... Basically unusable at this point, so I decided to restore a backup that I did before installing Magisk and after finishing it, the problem was still there. I was only able to get rid of the lag by flashing the stock ROM again with MiFlash without deleting data. I've also tried upgrading to 10.0.4.0 but it happens the same. Why could it be that booting into the patched_boot.img makes my phone unusable until I reflash it? How can I install Magisk and not getting all of this lag?

Stuck on Boot Logo

Hello,
I recently got around to unlocking the bootloader of my Z2 Play, XT1710-09 model on Android 8.0.0, February 2019 security patch, installing TWRP and rooting.
Now my first problem started when I went back into TWRP to flash a zip only to find out that it asks for a decryption password. I pressed cancelled and swiped to allow modifications but it appeared my storage was encrypted.
I said f**k it and decided to start over and went ahead and did a factory reset from TWRP (Wipe option) but now I'm stuck on the Boot Logo.
I can enter fastboot and recovery, the storage is no longer encrypted as I can see the TWRP folder that it creates there.
I'm currently downloading the December 2018 image and will try to return to stock via fastboot method but before that happens I wanted to know if I can do anything else to solve this.
If you remove encryption without disabling forceencryption, your device will try to reencrypt itself on the next reboot. So maybe you're not stuck but your device is just trying to do that

Phone boots but no display after rooting?

Not my phone, but a friend that rooted their friend's phone.
Goal: Unlock the bootloader and root the Redmi Note 8 Pro (Global)
Steps:
- Unlocked bootloader.
- Flashed TWRP. (it worked & booted)
- Installed Magisk (worked, phone booted with Magisk)
- Update Magisk through the Magisk Manager
This is where the problem occured:
The moment they clicked on Update in Magisk Manager, before the update process could even begin, before the update file would be downloaded, the phone rebooted (vibrated as if it was force rebooted) and the display never came back on.
This makes me believe it was a coincidence and the phone just rebooted on its own anyway.
The phone seemingly appeared to not work, as the display was off and would not turn on, but the phone does actually boot into MIUI and vibrations can be made using the screen.
The phone is detected in ADB according to my friend.
I am unsure whether fastboot or recovery works, but I would assume that if the system boots, fastboot would also work.
We tried looking this up online and we get all sorts of stuff about bricks and whatnot, but nothing about a display not working but the phone booted.
This isn't a brick, as the phone boots, but there is no visual output, not even the Mi logo on startup.
Anyone have a clue?
The user isn't comfortable with messing more with their phone to fix it, but they would like to charge my friend even if the repair ends up free. This is stupid.
Should try fastboot mode and flash the stock boot of the current rom

[SOLVED] Bootloop after flashing IMEI qcn file, caught in vicious circle

/EDIT:
Alright, the thread can be closed. I somehow managed it.
In case someone faces the same issue, I used twrp to dd the sdf files back on the phone which stopped the reboots. After that, just wiped and formatted everything again and reinstalled the ROM.
Hello guys,
I hope you can help me with this issue since I've tried everything I know to fix this problem.
The plan:
Unlocking bootloader, installing TWRP and xiaomi.eu ROM on a new device.
Changing its IMEI with QPTS/QFIL afterwards.
What happened:
Unlocked successfully. Installed TWRP, xiaomi.eu ROM and Magisk.
After pulling the QCN backup and editing the file I pushed it back to the phone what seemed to work.
After rebooting, I noticed that the phone rebooted 5 seconds after showing me the "Enter PIN" screen.
Booted up again and the same thing happened.
I booted into TWRP, wiped and formatted "data", installed the ROM again. The phone started up normally and there was no reboot.
I went back to TWRP and flashed Magisk, the phone crashed again and everytime I boot it up, it immediately reboots after some seconds. Installing Magisk somehow triggers the phone to reboot on its own.
I thought to start over, flashed everything from stock using Mi Flash Tool and the newest China Rom.
After starting up the phone, the issue still exists. This time with this rom there is no difference between installing Magisk or not, the phone always reboots after showing up the miui welcome/setup screen.
Current situation:
The phone boots up Android, reboots after some seconds and goes into fastboot automatically. After the fastboot timeout it again reboots automatically, goes into the OS and crashes again and on and on.
No matter what I do, I can't keep the phone from rebooting.
And since I can't flash Magisk, I have no root.
This means that I can not use root to put the phone into diag mode to restore the original qcn file.
I have backups of the EFS partition and also sdf7/8/9/10 files. I just don't know how to restore them given the current situation.
Thank you very much in advance for your support!
Cheers

Categories

Resources