Hello,
I tried to Magisk Hide Viper4AndroidFx (Magisk Module version), for the reason that Play Store verification was recognizing it as a vulnerability.
After applying Hide, the phone shut down, and will boot to ROM (Lineage 16 Pie), but soon shut down again.
I can access bootloader (fastboot) and twrp recovery. I've tried flashing SafeMode4Magisk and Magisk Uninstaller, and Core Only Mode but they all end up with an error: 1 /data/ not accessible*. TWRP error 1: Error installing zip file /external_sd/...zip
*Ok, Mount Data, doesn't help.
I'm on LOS 16, and the internal sd is not decrypted correctly - at all - with twrp 3.2.3-42. If there is a newer one, I'd like to know.
So the solution would be to factory reset (?) or wipe clean and start over. But before that I'd like to know what is giving me the error in flashing the files?
I've tried fastboot sideload, adb sideload, twrp flash.
I tried adb shell, to remove magisk, but the contents are encrypted.
SOLVED by blank slate re-install. But the question still remains.
Related
Hi everyone,
I'm trying to install TWRP on a fresh LG G6. I before updated the G6 to the latest available version.
So its currently running Android 8.0.0
Build Number OPR1.170623.032
Software version V20a-EUR-XX
I already unlocked the bootloader. Then I bootet into fastboot and tried to install twrp-3.2.1-0-h870. But after rebooting it with Volume Down + Power Key and reseting the device. I only see the TWRP splash screen after that the phone is booting the normal way up (and is reverting the bootloader).
I then installed (also via fastboot) twrp-3.1.1-0-h870. With this version I'm able to get into TWRP but this version is asking me for the password of the partition to decrypt. I didn't set up any encryption. So i tried "0000" --> no success. I also bootet andoird normaly and then setup a display lock screen with Pin 0000. But this code TWRP also refuses to use.
So I'm a little bit stranded here because I don't know what to do next.
Does anyone have a idea?
Greeting Uwe
You need to skip the password stage then format all. Type yes then it will work fine.
When it asks for password you can skip this stage
If I do so. I get
Formatting Data using make_ext4fs...
YOu may need to reboot recovery to be able tu usw /tada again.
Updating partition details...
Failed to mount '/system' (Device or resource busy)
... done
Click to expand...
Click to collapse
Then I hit reboot and the device is rebooting into Android and starting the first startassistant (so the format finally deleted something )
Then I power off the system and reboot with "Volume Down + Power" and I again only end in Factory reset data dialog
Ok next try same procedure than above. But not reboot into system instead only reboot into recovery --> pushing lineageos and the other zips onto the /sdcard/.
Wiping system, data, cache.
Flashing twrp via twrp, flashing lineageos, flashing gapps, flashing lineageos su package.
Reboot
And I'm greeted by Lineageos. Thanks for your support.
What i did stepwise -
1. Unlocked bootloader of my g5 plus
2. Flashed twrp-3.2.3-1-potter.img via adb
3. Booted to TWRP
4. Wiped to decrypt phone
5*. Booted to system to enable usb debugging, enabled it . Transfered magisk , arrow 9.0 rom , gapps to my internal storage of phone
6. Open bootloader , selected recovery mode and got nothing except error "No Command"
So i cannot flashed anything what i wanted to
What and Where i made the mistake ?
How can i get TWRP back?
Thanks all in advance
Solution
1. Flashed magisk17.1 and lazyflasher
2. Updated magisk manager and got root
3. Installed official TWRP app , granted root and downloaded same TWRP.img from which i decrypted the phone.
4. Flashed twrp fom the official twrp app.
5. No irritating No Command error again
The no command screen is that of the stock recovery (that's a normal screen). From your steps, it seems like you booted to system in step 5 rather than back to recovery. It seems that after flashing TWRP, you may have to boot to recovery to fix TWRP as your recovery (else the stock recovery overwrites TWRP). Afterwards, you should be able to boot as normal with TWRP still present.
Easiest way to recover would be to repeat step 2 and 3. Then reboot to recovery in TWRP and that should retain TWRP. Back up your existing system, then flash the ROM, GApps and magisk as desired.
echo92 said:
The no command screen is that of the stock recovery (that's a normal screen). From your steps, it seems like you booted to system in step 5 rather than back to recovery. It seems that after flashing TWRP, you may have to boot to recovery to fix TWRP as your recovery (else the stock recovery overwrites TWRP). Afterwards, you should be able to boot as normal with TWRP still present.
Easiest way to recover would be to repeat step 2 and 3. Then reboot to recovery in TWRP and that should retain TWRP. Back up your existing system, then flash the ROM, GApps and magisk as desired.
Click to expand...
Click to collapse
Thanks for your answer sir , but it didn't work
What I did again
1.I flashed same twrp from adb
2. Booted to recovery , but this time TWRP didn't asked password and I could see internal storage in twrp but not on my PC
3*.However I took the whole backup of stock nougat and cross check from restore option as there was backup in TWRP folder. I wanted copy that backup to my PC . But PC cannot detect my phone while in recovery
4. So booted to system and my PC detected my phone but there was no backup in TWRP folder.( But around 6gb(backup) of storage was used but I couldn't see it)
5.Again booted to recovery mode but "No Command" showed again .
I tried several times but I keep losing TWRP and couldn't see the backup which I make
Same problem. Resolved by flashing alternately several times twrp-3.2.1-0-potter.img and twrp-3.2.1-1-potter_persist.img and finally updated twrp-3.2.3-1-potter.img
It's because of dm-verity. You have to flash something like magisk or a custom kernel that disables it *before* you reboot into stock.
NZedPred said:
It's because of dm-verity. You have to flash something like magisk or a custom kernel that disables it *before* you reboot into stock.
Click to expand...
Click to collapse
I flashed magisk 17.1 and lazyflasher ,i got magisk and root but cannot install modules may be becoz of f2fs bug . By the way i lost twrp after booting to system again and No command still present in recovery mode . I am frustrated Moto software is just pain in head :silly:
I was using OrangeFox and tried to flash PixelExperience 11 from PixelExperience 10.
The flash went smoothly, but it goes to bootloop after i restart.
So i go back to OrangeFox to format my data and tried to reboot once again to finally get it working.
Then i tried to install magisk but my my recovery has encryption problem.
So i tried to install OrangeFox from ADB sideload but got error message halfway.
Now whenever i tried to reboot into recovery, it just go through the system and reboot just fine.
And to make it worse. Everytime i go to bootloader i just get blank screen and fastboot can't detect it.
My problem is PE 11 is so unstable and some of my apps won't even open.
Now is there any way to fix my recovery or bootloader?
Hi all,
So I was triying to update my Magisk through the recommended direct update method. I got a bootloop. Never had any issues with this update method, Magisk always did a splendid job.
Now my only options are:
1. Flash a custom rom (I don't have any stock Telekom roms)
2. Update Android OS to 8.0 with LG Bridge (my goal is to have a stock rooted android os, that's why I'm doing this)
3. adb reboot, flash the latest twrp recovery (at least that's working)
4. flash the latest Magisks without reboot option, just power off and then turn on. And this is stage where I get a bootloop.
I only have v19.3 saved on my HDD. Flashing that is working just fine, not causing any bootloop. However Fake GPS and Pokémon Go are not working with this version anymore. :/ So I'm kinda chess-mated here because of this Magisk bootloop.
Anyone can help me how can we fix this?
I have bootloops with all Magisk 21.x versions, so I'm stuck with 20.4. Can't you download Magisk 20.4 and install it from TWRP? I don't need SafetyNet, so I have no idea if Magisk 20.4 can still pass the check, but at least it would be newer than Magisk 19.3.
I downloaded the previous 21.0 versions from here https://droidfeats.com/download-magisk-zip/ flashed it and it's working. I also tested the previous versions. Seems like only 21.4 version is affected only, which is the latest stable.
I had the same problem: I had Magisk 21.4 and withing Magisk Manager I tried to update to v. 22.0 because I got an update prompt that asked me to do so. Trusting everything was fine I updated but I got a bootloop. I managed to recover from bootloop and get the latest version of Magisk working in my Huawei Y5 MYA-L13 (Android 6.0). For these steps, it is assumed Magisk v21.4 and Magisk v22.0 ZIP files are stored in your storage. This is the way I did it:
Manage to get into stock recovery mode.
This step was more time-consuming than it should have been... This Huawei model with the bootloader unlocked states at boot: "Press volume key up to 3 seconds to enter recovery to restore your device". It didn't... With Vol+ just restarted the device (no TWRP or stock recovery or download mode...) and pressing Vol- it loaded into the bootloop. It took me some time to guess the right way:
Plug the turned-off device into a USB cable plugged into the computer.
Wait for the device to start into "charging mode" (I made up this... I mean wait until the charging percentage appears).
Turn on the device using the Power Button.
Immediately, press and hold Vol+.
The device will reboot. Press and hold Vol -.
The device will get into the stock recovery mode (EMUI Huawei eRecovery).
Try again if this fails... After a few attempts, you'll get it.
Now the device will be visible to ADB. Verify this in a command prompt with adb devices. Mine was listed as 0123456789ABCDEF recovery.
Use the command adb reboot recovery to get into the real recovery mode. I mean TWRP. (It's still there even if it seemed to be it wasn't).
Flash the version that caused the problem. In my case, I had Magisk v21.4 initially, so I installed this same version ZIP I got from the official Magisk GitHub releases section.
Once finished the installation, if it was successful Reboot. The device should boot normally this time, having installed this version of Magisk and not the new one, of course.
Now proceed to uninstall Magisk 21.4 completely using the ZIP file provided in the above URL (step 4) with TWRP.
Follow the official installation guide in the Custom Recovery section to install Magisk 22.0 (that is: having renamed Magisk-v22.0.apk to Magisk-v22.0.zip previously, use TWRP to install it). Reboot.
Your device should boot normally. You'll find a Magisk app where you'll be able to verify latest Magisk 22.0 was successfully installed!!! DONE.
I hope my guide is useful to someone. If so, please like my post to be aware it was useful. Greetings!
TL;DR
adb reboot recovery
Install Magisk-v21-4.zip. This solves bootloop problem!
Uninstall Magisk using Magisk-uninstaller-20210117.zip
Rename Magisk-v22.0.apk to Magisk-v22.0.zip. Install it using TWRP.
Reboot. You have the latest Magisk version v22.0 installed with no bootloop!!!
I've upgraded from v20.4 to v22 yesterday using the new Magisk app, it all went smoothly.
Hi, I'm on OOS11 and I lost magisk so I booted to TWRP via fastboot but it gave me the error "qualcomm crashdump mode". After that error I wasn't able to boot into the OS. I found out that the twrp I was using is not compatible with OOS11 so I tried again with "fajita_twrp-3.5.2_11-0_test3.img". I was able to enter into TWRP and with no wipes I installed OOS11 + TWRP. The "qualcomm crash.." error is gone but the phone does not boot, it is stuck on a bootloop. When I enter into TWRP in slot B it's asking me for password and I'm able to see my files. When I'm on slot A it's not asking me for password and data seems to be encrypted (folder weird names). Is there a way to solve this without having to reset data?