The culprit seems to be magisk. I restored the stock boot images through the magisk manager app. And rebooted the devices. But it's not rebooting and stuck in bootloop. I do not have twrp and ADB is not authorised. ( But I have enabled usb debugging and the phone is OEM unlocked.)
How do I get out of bootloop?:crying:
Flash full ROM via fastboot. ADB should not be required for this.
Related
Hi,
Yesterday my WileyFox Spark+ came in, which is still equipped with COS13.0.1, based on Android 6.0.1.
When I tried rooting the phone, I got stuck at the point of using TWRP for flashing SuperSU.zip.
Until then, I had succesfully followed the following process:
-Enabled 'OEM Bootloader allowed to be unlocked' in Developer Options
-Installed USB drivers and such on PC
-Enabled USB debugging, apps from unknown sources, ADB install unsigned apps allowed etc.
-Unlocked bootloader like this in CMD:
fastboot devices (my phone showed up)
fastboot flashing unlock
I pressed volume up button (yes)
I selected boot mode fastboot
-Flashed TWRP Recovery to phone like this in CMD:
fastboot flash recovery twrp3100.img
-I booted into TWRP recovery
A lot of folders and some files were present there, but almost all folders were 'empty'. I couldn't reach my SC-Card with SuperSU.zip on it.
TWRP even said no OS was installed when I wanted to reboot to retry.
I was confused for a while, only to discover the OS was still there after booting into System.
I tried to flash SuperSU from ADB, but that also didn't work. I issued the following commands in CMD:
adb reboot recovery
(ticked adb sideload in TWRP +wipe dalvik & cache)
adb sideload supersu279.zip
TWRP said it executed succesfully, but failed to access /data and /cache.
It was at this point that I discovered the phone was encrypted already from the box. I had never considered this as an option.
It's weird though, because I have heard that flashing SuperSU from ADB should work even with an encrypted phone.
Now the interwebs and WileyFox themselves say Encryption is disabled when you factory reset the phone. So I did that, but it just booted into TWRP with the same circumstances.
Few folders, almost all empty. SD-card not visible.
I tried sideloading SuperSU again, but without result.
Any idea how i should progress further? 'Cause I have run out of ideas..
Is it possible to flash SuperSU via fastboot or anything?
I have found a LineageOS 13 ROM for my phone, but it's a .zip so I don't think I can use it.
Anyway, any help would be greatly appreciated!
Cheers.
NB: I don't care about encryption, i'd rather have it gone, but whatever option is best for rooting this thing will work fine for me.
Hi all,
I just updated to the latest beta with Android Q, everything is fine except one thing. I successfully re-enabled Magisk with a patched boot image, and all was fine.
However when I flashed a module (despite it saying it was compatible with Q), my phone desicided not to boot anymore.
If I fastboot flash the unpatched boot image, of course it works, but I don't have root access anymore.
If I re-flash the patched boot image, it stays stuck to the boot animation.
Since I'm on Q, I have no TWRP recovery, so impossible to flash the magisk uninstaller zip.
What could I try ?
My options are now either to erase data and start fresh, which is a lot of trouble for such a small problem, or to wait for a TWRP release.
Any other suggestion would be very welcome
Thanks!
Edit: Managed to solve it. Little how-to, in case someone else has the issue :
On the PC, relaunch your adb daemon in root mode by typing
Code:
adb kill-server
and then
Code:
adb root
Now reboot your phone into Fastboot and plug it in the PC
Flash the patched boot image by typing
Code:
fastboot flash boot oos_10_ob1_patched_boot.img
and start the phone
While it's attempting to boot (it is stuck on the animation because of the problematic module), type
Code:
adb shell
then in the shell, type
Code:
magisk --remove-modules
The phone should reboot, and complete this boot sequence normally. You can then go into Magisk Manager and reflash magisk (direct install) and start over
Thanks for this. Keeping this as reference. I believe this works only if you've enabled USB Debugging in your phone and granted it access to your PC, right?
As the title says, my OnePlus 7 Pro now only boots to the Bootloader and it isn't detected by Fastboot on my PC. I recently extracted a boot.img from the latest (10.3.8) OOS firmware, patched it with magisk, then flashed in TWRP and booted to system. I realized I forgot to reinstall TWRP so I flashed its installer in Magisk Manager then directly installed Magisk. This may be the reason why I can't boot anymore... I most likely can use EDL and MSM to restore (hadn't tried it yet), but I rather save that as a last resort since I really don't want to wipe my device. I've already tried installing a bunch of adb and oem drivers to no avail. Is there a way to use EDL to boot a twrp.img, perhaps?
Well turns out it was a driver issue. Installed proper drivers and got fastboot to work again. Booted TWRP and dirty flashed stock firmware, TWRP and Magisk.
A while ago i installed Lineage OS onto my OP7Pro without issue. I am now trying to go back to the stock OP OS.
I seem to have completely wiped the storage and now I just get "Qualcomm Crashdump Mode dm-verity device corrupted force dump kernal_restart".
I installed twrp on my PC and managed to boot the phone into twrp, I then pushed the twrp-installer.zip to the phone using adb, and then using the phone installed the zip, however when the phone reboots it just goes straight back to the Qualcomm Crashdump screen.
I have tried:
fastboot boot twrp.img (sucessfully boots phone into twrp)
adb sideload twrp-installer-3.5.2_9-0-guacamole.zip (adb confirmed sucessfull but then I can not find the file on the phone)
adb push twrp-installer-3.5.2_9-0-guacamole.zip /sdcard/ (when I go the install on twrp the file is there and I can install it)
But after reboot it's just straight back to Qualcomm Crashdump.
I tried msm and that didn't work, it would not detect the device.
Can anyone please help??
Try:
fastboot --set-active=other
Then fastboot boot TWRP.img
Install any ROM.zip or stockOOS.zip reboot to fastboot, boot TWRP and flash magisk.
If that doesn't work try again with msmtool, remember press both volume buttons for 5 seconds and connect USB cable(still pressing volume buttons) and your device should be detected
IthinkIfckedmyphone said:
A while ago i installed Lineage OS onto my OP7Pro without issue. I am now trying to go back to the stock OP OS.
I seem to have completely wiped the storage and now I just get "Qualcomm Crashdump Mode dm-verity device corrupted force dump kernal_restart".
I installed twrp on my PC and managed to boot the phone into twrp, I then pushed the twrp-installer.zip to the phone using adb, and then using the phone installed the zip, however when the phone reboots it just goes straight back to the Qualcomm Crashdump screen.
I have tried:
fastboot boot twrp.img (sucessfully boots phone into twrp)
adb sideload twrp-installer-3.5.2_9-0-guacamole.zip (adb confirmed sucessfull but then I can not find the file on the phone)
adb push twrp-installer-3.5.2_9-0-guacamole.zip /sdcard/ (when I go the install on twrp the file is there and I can install it)
But after reboot it's just straight back to Qualcomm Crashdump.
I tried msm and that didn't work, it would not detect the device.
Can anyone please help??
Click to expand...
Click to collapse
have you tried the 3.4 mauronofrio TWRP? maybe if you can get it to boot use it to flash oos 10.3.8 then update to 11 after
OnePlus 8T KB2003 running lineage-20.0-20230105-nightly with Magisk 25.2 patched boot image.
Yesterday I installed latest OTA lineage-20.0-20230112-nightly, patched boot.img through Magisk to inactive slot before OTA reboot, rebooted and now I am in a bootloop.
I was about to flash original lineage boot.img from payload_dumper through flashboot, and I find neither fastboot nor adb work at all. My device is not recognised on adb or fastboot when I plug in the usb-c cable.
I checked platform-tools version and google adb drivers to be updated (reinstalled from 15-second ADB installer), swapped usb-c cable, changed host usb port... but no outcome.
I tried adb/fastboot devices pluging another android 13 phone, and everything works. So I discarded drivers, cable and port.
I plugged my turned off OnePlus with the same cable and port, and it charges. So I discarded usb port from OnePlus.
The only thing that gets me thinking is that I did not enabled usb debugging mode in lineageos 20 (as I did in lineageos19 and maybe the option was set to default after the update), but now I cannot check as it does not boot to system.
I guess there is no way to enable it from fastboot/recovery mode, or to change active slot to b (I am currently in a, and in b I could reboot normally), as I cannot fastboot this device (fastboot --set-active=b)
Any idea? Data factory would not help as I would be unable to adb push rom and gapps.
Thanks in advance as I am pretty lost.
The usb debugging setting in developer options only lets you use ADB commands while booted in android.
It shouldn't influence ADB or fastboot from working in recovery or fastboot mode.
Note: ADB doesn't work in the root of recovery you would have to go to “Advanced” -> “Enable ADB” to use it from recovery.
If fastboot isn't working in fastboot mode you can try using fastboot from recovery.
For this you can go to the recovery and then “Advanced” -> “Enter fastboot”.
It shouldn't be the newest OTA lineage-20.0-20230112-nightly at least as i'm currently running it including Magisk without any problems. I am running the newest F.15 firmware instead of F.13 firmware though.
Also I installed magisk by sideloading it after renaming the .apk to .zip which keeps magisk installed through Addon.d like gapps. So i didn't use the inactive slot installation. (Not sure if you can sideload it after first boot)
Vipe838 said:
The usb debugging setting in developer options only lets you use ADB commands while booted in android.
It shouldn't influence ADB or fastboot from working in recovery or fastboot mode.
Note: ADB doesn't work in the root of recovery you would have to go to “Advanced” -> “Enable ADB” to use it from recovery.
If fastboot isn't working in fastboot mode you can try using fastboot from recovery.
For this you can go to the recovery and then “Advanced” -> “Enter fastboot”.
It shouldn't be the newest OTA lineage-20.0-20230112-nightly at least as i'm currently running it including Magisk without any problems. I am running the newest F.15 firmware instead of F.13 firmware though.
Also I installed magisk by sideloading it after renaming the .apk to .zip which keeps magisk installed through Addon.d like gapps. So i didn't use the inactive slot installation. (Not sure if you can sideload it after first boot)
Click to expand...
Click to collapse
Wow, thank you so much!
I could connect with fastbootd (from recovery, Advanced --> Enter Fastboot), could flash boot.img and got it to boot.
Thank you again.