restoring a TWRP backup is successful, but on boot the phone locks up with this error.
dm-verity device corrupted
"kernel_restart"
it will not continue. i still have TWRP installed. but cannot restore.
i tried running the following commands with no change
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
any ideas?
mlkemac said:
restoring a TWRP backup is successful, but on boot the phone locks up with this error.
dm-verity device corrupted
"kernel_restart"
it will not continue. i still have TWRP installed. but cannot restore.
i tried running the following commands with no change
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
any ideas?
Click to expand...
Click to collapse
Can you boot TWRP still? If so, restore Data ONLY, flash full OOS zip version the backup is from, twrp installer, reboot twrp, flash full OOS zip again, TWRP installer, reboot twrp again, flash magisk and other mods you have/had/want. If you can't access twrp, use fastboot ROM to restore your phone.
Related
Hello! I've tried to root my phone (Moto G XT1541 Europe 1GB) but failed. I got an error when trying to flash the custom recovery. Unfortunately, it has overwritten the stock recovery and it didn't install. So, now I have a phone without recovery and I can't do a factory reset because of that (I think).
So, this is my question: how can I re install the default Android 6.0 recovery mode for my phone?
Also, my phone boots automatically on bootloader mode and I can't re-lock the bootloader because I can't flash anymore either; I got an error because the pre flash validation failed when trying to flash with adb fastboot, but this is minimal issues that doesn't really bother me, but they could be helpful and if someone knows how to get rid of them, I want to know!
I hope someone will help me!
Azyreal said:
Hello! I've tried to root my phone (Moto G XT1541 Europe 1GB) but failed. I got an error when trying to flash the custom recovery. Unfortunately, it has overwritten the stock recovery and it didn't install. So, now I have a phone without recovery and I can't do a factory reset because of that (I think).
So, this is my question: how can I re install the default Android 6.0 recovery mode for my phone?
Also, my phone boots automatically on bootloader mode and I can't re-lock the bootloader because I can't flash anymore either; I got an error because the pre flash validation failed when trying to flash with adb fastboot, but this is minimal issues that doesn't really bother me, but they could be helpful and if someone knows how to get rid of them, I want to know!
I hope someone will help me!
Click to expand...
Click to collapse
The bootloader cannot be relocked in the Moto G 2015, the best you can do is hide the warning screen. Find the stock image and fastboot flash the recovery from there, or better yet, flash the entire image so you are in a known working state
If you are in Pre-Flash validation, you do not have the correct image for your device... I suggest you post in the "How to flash factory images" thread about returning to stock, if it is possible. You MUST factory default before flashing factory images, if you can't, try 'fastboot erase userdata' and try again.
Flash latest twrp via fastboot and reboot into recovery ,
don't reboot into system,
reboot into recovery manually, then you can enter twrp recovery and can flash supersu 2.62.3.
when you just reboot after flash twrp and reboot system erase custom recovery and save stock recovery, so don't enter fastboot reboot, enter fastboot reboot recovery after flash recovery via pc.
Rename twrp recovery as only twrp in fastboot folder in your pc , not as twrp.img,
But cmd as fastboot flash recovery twrp.img , then no errors ( are you unlocked bootloader ?)
acejavelin said:
The bootloader cannot be relocked in the Moto G 2015, the best you can do is hide the warning screen. Find the stock image and fastboot flash the recovery from there, or better yet, flash the entire image so you are in a known working state
If you are in Pre-Flash validation, you do not have the correct image for your device... I suggest you post in the "How to flash factory images" thread about returning to stock, if it is possible. You MUST factory default before flashing factory images, if you can't, try 'fastboot erase userdata' and try again.
Click to expand...
Click to collapse
drmuruga said:
Flash latest twrp via fastboot and reboot into recovery ,
don't reboot into system,
reboot into recovery manually, then you can enter twrp recovery and can flash supersu 2.62.3.
when you just reboot after flash twrp and reboot system erase custom recovery and save stock recovery, so don't enter fastboot reboot, enter fastboot reboot recovery after flash recovery via pc.
Rename twrp recovery as only twrp in fastboot folder in your pc , not as twrp.img,
But cmd as fastboot flash recovery twrp.img , then no errors ( are you unlocked bootloader ?)
Click to expand...
Click to collapse
Hey! Thank you! I've been able to flash the TWRP recovery and now I can do a factory reset (and also send sms, which I couldn't do anymore for some reason).
I still have the issue where the bootloader screen appears everytime I turn my phone on, and I still can't re lock my device because I can't flash anything either. I've recovered all of my data, so I think I'm going to stick with that for a moment but maybe I'll try what you said some day.
Again, really thank you for helping me!
drmuruga said:
Flash latest twrp via fastboot and reboot into recovery ,
don't reboot into system, reboot into recovery manually, then you can enter twrp recovery and can flash supersu 2.62.3.
when you just reboot after flash twrp and reboot system erase custom recovery and save stock recovery, so don't enter fastboot reboot, enter fastboot reboot recovery after flash recovery via pc.
Click to expand...
Click to collapse
Now I understand why my flashing TWRP did not take. I simply rebooted to system and still have stock recovery installed. I was successful booting twrp via fastboot and successfully flashed supersu 2.62.3. Is this step in listed in any faq? I must have missed it.
So after flashing TWRP, do you then power down device prior to manually booting to recovery?
MrTooPhone said:
Now I understand why my flashing TWRP did not take. I simply rebooted to system and still have stock recovery installed. I was successful booting twrp via fastboot and successfully flashed supersu 2.62.3. Is this step in listed in any faq? I must have missed it.
So after flashing TWRP, do you then power down device prior to manually booting to recovery?
Click to expand...
Click to collapse
Don't power down, already you are in fastboot mode, you can just enter recovery from that. I forget the reference, but i will search and post.
---------- Post added at 04:41 PM ---------- Previous post was at 04:18 PM ----------
I get this from twrp official page
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
In our phone press simultaneously volume down + power button to enter recovery.
I was running stock OOS with Android 8.1 with the normal TWRP and Magisk working. When the OOS 9 got out, I installed the full OTA through TWRP (dirty flash) and everything went perfectly, with no problems whatsoever, but I lost TWRP and Magisk, of course.
Now in Android 9 I can't seem to reinstall TWRP (I'm trying with the latest bluespark): I can boot TWRP from fastboot and install Magisk, everything is fine, Magisk works great. However, when I try to install the TWRP zip (through the fastboot loaded TWRP), the phone freezes at the bootloader warning and doesn't boot (and I have to reinstall the full OTA zip to get the phone working again). Or, some other times, it reboots always to the recovery and never to the OS. Any ideas on how to solve this? Thanks in advance.
What version of bluespark are you using ?? v2
Glsoto said:
What version of bluespark are you using ?? v2
Click to expand...
Click to collapse
9.85v2
first fastboot boot twrp.img, the install twrp.zip , reboot recovery and then magisk..
I also tried to fastboot boot blu_spark twrp V2 IMG.... This ended in a black screen. I used the latest official twrp without a problem on pie.
Glsoto said:
first fastboot boot twrp.img, the install twrp.zip , reboot recovery and then magisk..
Click to expand...
Click to collapse
Thanks! Did it in that exact order and now everything works. I was forgetting to reboot the recovery before installing Magisk.
don't flash magisk on the temporary TWRP
Hexyl said:
I also tried to fastboot boot blu_spark twrp V2 IMG.... This ended in a black screen. I used the latest official twrp without a problem on pie.
Click to expand...
Click to collapse
Cuz of kernel panic. When you boot into twrp after fastboot command - unplag your cable from pc when the command is done, then disable mtp, connect to pc and re-enable mtp.
Dont forget to click thanks
And yeah, use blu spark's TWRP, not official one
Came here from google.
Glsoto said:
first fastboot boot twrp.img, the install twrp.zip , reboot recovery and then magisk..
Click to expand...
Click to collapse
This procedure didn't work for me, for some reason "fastboot boot twrp.img" was leading to black screen.
What worked for me was
1) Boot to fastboot
2) fastboot flash twrpXXX.img
3) Without rebooting, select recovery from fastboot's bootloader menu
4) If you are able to boot in twrp this time, then flash blu spark twrp.
5) Reboot
6) Try to reboot in recovery as usual
If all worked well, you should see twrp recovery.
Cheers.
Alekcander said:
Came here from google.
This procedure didn't work for me, for some reason "fastboot boot twrp.img" was leading to black screen.
What worked for me was
1) Boot to fastboot
2) fastboot flash twrpXXX.img
3) Without rebooting, select recovery from fastboot's bootloader menu
4) If you are able to boot in twrp this time, then flash blu spark twrp.
5) Reboot
6) Try to reboot in recovery as usual
If all worked well, you should see twrp recovery.
Cheers.
Click to expand...
Click to collapse
Hi
I have same problem ... after installing twrp i have black scream. twrp doesnt boot
I trying to use this method but cmd give me ]
C:\Android>fastboot flash twrp-3.3.1-x_blu_spark_v9.101_op6.img
unknown partition 'twrp-3.3.1-x_blu_spark_v9.101_op6.img'
error: cannot determine image filename for 'twrp-3.3.1-x_blu_spark_v9.101_op6.img'
I have restored phone with msn download
OnePlus is again unlocked
I have this problem sins i tried to install magisk and after reboot my op doesn't boot to OS with crash error
any ideas ?
jasiorr said:
Hi
I have same problem ... after installing twrp i have black scream. twrp doesnt boot
I trying to use this method but cmd give me ]
C:\Android>fastboot flash twrp-3.3.1-x_blu_spark_v9.101_op6.img
unknown partition 'twrp-3.3.1-x_blu_spark_v9.101_op6.img'
error: cannot determine image filename for 'twrp-3.3.1-x_blu_spark_v9.101_op6.img'
I have restored phone with msn download
OnePlus is again unlocked
I have this problem sins i tried to install magisk and after reboot my op doesn't boot to OS with crash error
any ideas ?
Click to expand...
Click to collapse
You need to Fastboot boot twrp. Img
jasiorr said:
Hi
I have same problem ... after installing twrp i have black scream. twrp doesnt boot
I trying to use this method but cmd give me ]
C:\Android>fastboot flash twrp-3.3.1-x_blu_spark_v9.101_op6.img
unknown partition 'twrp-3.3.1-x_blu_spark_v9.101_op6.img'
error: cannot determine image filename for 'twrp-3.3.1-x_blu_spark_v9.101_op6.img'
I have restored phone with msn download
OnePlus is again unlocked
I have this problem sins i tried to install magisk and after reboot my op doesn't boot to OS with crash error
any ideas ?
Click to expand...
Click to collapse
yldlj said:
You need to Fastboot boot twrp. Img
Click to expand...
Click to collapse
Alekcander said:
Came here from google.
This procedure didn't work for me, for some reason "fastboot boot twrp.img" was leading to black screen.
What worked for me was
1) Boot to fastboot
2) fastboot flash twrpXXX.img
3) Without rebooting, select recovery from fastboot's bootloader menu
4) If you are able to boot in twrp this time, then flash blu spark twrp.
5) Reboot
6) Try to reboot in recovery as usual
If all worked well, you should see twrp recovery.
Cheers.
Click to expand...
Click to collapse
I have the same problem as Alekcander
When I try to use command ,, fastboot boot twrp-xxx.img nothing happens. I mean mobile restart as always but there is only black screen and notification diode shine white ...
Also Alekcander method doesn't work:
C:\Android>fastboot flash twrp-3.3.1-x_blu_spark_v9.101_op6.img
unknown partition 'twrp-3.3.1-x_blu_spark_v9.101_op6.img'
error: cannot determine image filename for 'twrp-3.3.1-x_blu_spark_v9.101_op6.img'
I tried official twrp and is the same , I tried to disconnect from usb when mobile is restarting also nothing ...
so again ... I have restored phone with msn download -> unlock bootloader...
i have this issue sins i tried to install magisk and after reboot my OP6 doesn't boot to OS and give crash error
any other ideas ?
Solved I have to update system to more recently version. Why twrp doesn't work with oxygen is 5.1.5 ?
Bootloop to fastboot after being on dp3, and restoring carbon. I tried fastboot boot twrp.img, but it fails....I also tried fastboot flash it, it does, but still reboots to fastboot. Any suggestions?
I assume you had TWRP installed when this condition occurred, and trying to boot TWRP just sent you to fastboot?
What was the exact error message when trying to fastboot boot TWRP?
suzook said:
Bootloop to fastboot after being on dp3, and restoring carbon. I tried fastboot boot twrp.img, but it fails....I also tried fastboot flash it, it does, but still reboots to fastboot. Any suggestions?
Click to expand...
Click to collapse
try this one
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
had the same problem and it helped
redpoint73 said:
I assume you had TWRP installed when this condition occurred, and trying to boot TWRP just sent you to fastboot?
What was the exact error message when trying to fastboot boot TWRP?
Click to expand...
Click to collapse
It sends the file...then I get a remote error. I tried fastboot flash too. It completed, but still boots to fastboot. Guess msm tool is needed. This phone is a pita.
I cannot get twrp to boot.....Phone refuses to boot it. WTF???
Have you tried this specifically?
Code:
fastboot flash boot recoveryname.img
I was stuck in fastboot yesterday after doing a TWRP restore. The issue was I did a backup and restore including boot and system/vendor.
My thread from a few days ago: https://forum.xda-developers.com/oneplus-7-pro/help/please-help-fastboot-boot-loop-twrp-t3949952
i.Design said:
Have you tried this specifically?
Code:
fastboot flash boot recoveryname.img
I was stuck in fastboot yesterday after doing a TWRP restore. The issue was I did a backup and restore including boot and system/vendor.
My thread from a few days ago: https://forum.xda-developers.com/oneplus-7-pro/help/please-help-fastboot-boot-loop-twrp-t3949952
Click to expand...
Click to collapse
LOL...Um, yes.
Use the All-In-One Tool and flash a fastboot firmware zip (you can find downloads in the software itself). After flashing your back on OOS and can use fastboot to boot TWRP again, then install or restore your rom
Hi everybody,
I tried to update my OOS to Android Q while keeping magisk, there was probably a module not compatible that I forgot to remove before and I could not access the interface after rebooting.
Trying to restore the stock boot.img with fastboot, now I am stuck on the "Boot Loader is unlocked" warning page and the phone refuses to boot.
I tried to wipe everything using fastboot -w but still can't boot normally, if anyone can help me solve this please, I would be grateful.
Regards.
Try flashing the unofficial TWRP for Q from here
You can follow that guide but don't install Magisk, then after successful boot, try flashing Magisk uninstaller in TWRP.
Can try flashing android 10 boot.img from #2 link.
this happened to me. It was because I had the usb pluged. If you take the usb out it will boot. Or at least mine worked that way.
What I did was completely restoring the device by flashing a fastboot ROM then updating to Q again. SO I've lost all my data.
Do you know any way I can root android Q actually ?
https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213
danecr7 said:
Hi everybody,
I tried to update my OOS to Android Q while keeping magisk, there was probably a module not compatible that I forgot to remove before and I could not access the interface after rebooting.
Trying to restore the stock boot.img with fastboot, now I am stuck on the "Boot Loader is unlocked" warning page and the phone refuses to boot.
I tried to wipe everything using fastboot -w but still can't boot normally, if anyone can help me solve this please, I would be grateful.
Regards.
Click to expand...
Click to collapse
If you have access to fastboot then you can flash twrp and do below steps exactly else you will stuck at bootloader warning message
Reboot to fastboot mode. Flash TWRP img using the following command--> Oneplus blocked fastboot boot command
Code:
fastboot flash boot twrp-******.img
From fastboot mode, reboot directly to recovery mode. Now you have a working TWRP. (If you already have Magisk earlier, flash Magisk uninstaller now before proceeding to the next steps)
In TWRP, flash the stock boot image in boot partition. Don't reboot .
Flash TWRP installer zip then reboot to recovery. You now have a fully working TWRP in OOS 10. . Don't reboot .
Flash Magisk v20.1. Reboot to system.
Bricked my OP8T (unlocked bootloader, rooted) in a failed OS update attempt. I'm pretty sure I was running OS 11.0.8.12, attempted updating to 11.0.11.11 following Magisk OTA update instructions to keep root. It seemed to mess up as when I viewed OS info, 11.0.8.12 was still listed, but then phone calling, wifi, audio all were broken. So I then attempted the local upgrade option, which didn't work at all. After rebooting, found myself in Qualcomm crash boot, but was able to still get to fastboot using Vol Up + Vol Down + Power key combination.
I've attempted switching active boot slots and that didn't fix anything. My slot a seems to have considerable issues so been trying to reflash images to b slot. I've extracted all images from payload.bin from both 11.0.8.12 and 11.0.11.11. I also have magisk patched boot images for both versions of OS's on my PC. When I've attempted flashing 11.0.11.11 system image, I get errors regarding can't resize partition, not enough space. I've tried 'Fastboot delete-logical-partition product', but still received same error. So I've thought, I'll just reflash the 11.0.8.12 images and try to get my phone back to bootable.
I've ran the following commands to attempt to get back to bootable phone:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot bootloader
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot--disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot bootloader
Issue is now that whenever I attempt to reboot the phone, it automatically boots back into fastboot :/ I've attempted wiping the cache too in hopes it would help but no dice.
Curious if there is a way to recover the phone without wiping my data partition. I've got most apps and settings backed up but it's still a hassle I'd prefer to avoid. Would it be possible to boot into TWRP using 'fastboot boot twrp.img' to pull the user data partition to local pc? Then wipe the phone and install fresh OS? I've heard that twrp can't decrypt the user data partition for stock OP Roms?
TWRP have always been able to decrypt user data for stock OOS roms. The latest twrp version can even flash OOS rom (thanks to a patch by a helpful community member).
If I where you I would try to boot latest TWRP and see if that can decrypt the data (do not freak out if it can't there might still be a way to save the data).
If it can decrypt data I would perform a backup of the data partition and then copy your whole internal sd over to your computer just to be safe.
After that I would try to flash the latest OOS ota in TWRP and see if that fixes it. If not you can try to format data and reboot. If that fixes it you can just restore your data backup. If that don't work I would use the MSM tool and then unlock bootloader and restore data backup.
If TWRP are unable to decrypt the data I would sideload the OOS ota in TWRP and see if that fixes it (it did for me when I had a similar problem). If not your data is lost and you might need to use MSM tool.
I would wait to install magisk until I made sure everything boots without it.
Qnorsten said:
TWRP have always been able to decrypt user data for stock OOS roms. The latest twrp version can even flash OOS rom (thanks to a patch by a helpful community member).
If I where you I would try to boot latest TWRP and see if that can decrypt the data (do not freak out if it can't there might still be a way to save the data).
If it can decrypt data I would perform a backup of the data partition and then copy your whole internal sd over to your computer just to be safe.
After that I would try to flash the latest OOS ota in TWRP and see if that fixes it. If not you can try to format data and reboot. If that fixes it you can just restore your data backup. If that don't work I would use the MSM tool and then unlock bootloader and restore data backup.
If TWRP are unable to decrypt the data I would sideload the OOS ota in TWRP and see if that fixes it (it did for me when I had a similar problem). If not your data is lost and you might need to use MSM tool.
I would wait to install magisk until I made sure everything boots without it.
Click to expand...
Click to collapse
Unfortunately I wasn't able to get TWRP to decrypt my data :/ Tried using TWRP with stock boot image flashed as well as with magisk patched boot image.
Tried using the following guide here to see if I could make it happen while saving my data but was unsuccessful. Ah well, glad I use Swift Backup and SMS Backup & Restore. Should make restoring phone to prior state a bit easier, but still a little pain in the butt.
I'm pretty sure I've run into issues in the past with upgrades on OnePlus and new versions not being able to decrypt previously encrypted user data. Hence why I was resistant to upgrading for the last 5 months. Hopefully the upgrade to the december update goes a little smoother.
Appreciate the advice/guidance @Qnorsten!
Sorry to hear that didn't help. I never had any problems with any updates, except when I was messing around with TWRP and that was my own fault.
Older OOS versions can't decrypt data from newer versions but if you flash a newer one it should work.
Have you tried sideloading the latest full OOS ota zip in TWRP?