I recently decided I wanted to go back to using Magisk after about a 6 month pause (I had reverted so I could take a security update and stopped using it last fall).
So I thought I knew what I was doing.
I took the Feb 22 update without Magisk.
I let Magisk App patch the boot.img
I did the fastboot flash boot patched_boot.img and then fastboot reboot
It hung for 30 min or more on the Moto boot screen. So then I panicked an this is where I probably screwed the pooch.
I flashed back to the base boot.img and tried to boot. No go.
I flashed BACK to the patched image and then did the vbmeta disable step. Rebooted. No go.
Finally I booted TWRP for Sophia (3.5) but didn't flash. It will boot TWRP but of course everything is garbled because I've screwed up encryption.
Any way out or should I just bite the bullet and re-flash?
The only thing that I can't recover is my SMS history as I stopped using an SMS backup/forward tool about 2 years ago (sadly now...)
Related
Hi friends,
So here's a thing:
I was trying to update my Nexus 9 to the latest Slimrom build , and I used Chainfire's flashfire app. It didn't work and sent the tablet in a boot loop. But it also wiped my recovery so I couldn't even select my recovery.
So no issues, I used the Wugfresh nexus toolkit to flash it back to stock and unroot. Bootloader is still unlocked, so I just root it again and go ahead and try to install the update using Wugfresh. It works, but says the vendor.img is wrong. So I downloaded the correct vendor.img and tried to flash it, but of course because the tablet is encrypted TWRP asked for a password. I hit cancel and tried to continue, but Wugfresh just hung at that step.
So I tried to manually flash the ROM, but now it gives me a vendor.img error and will not flash anything. Trying to flash anything sends the device in a bootloop.
TLDR; I can restore to stock and root, and also access the bootloader and recovery (TWRP) but can't flash anything without sending the device in a bootloop.
I've currently restored the tablet to stock via wugfresh's tool and rooted. So I'm back at the beginning, except with this vendor.img issue when I'm trying to flash a ROM.
Anyone have any ideas?
Hi everybody,
I got my Swift 2 8 months ago and have finally decided to root it using TWRP. So I unlocked my bootloader and then installed TWRP using the official guide at https://twrp.me/devices/wileyfoxswift2.html. I also wiped my cache and dalvik cache.
However, now I have done this, whenever I try to boot, I receive both the amber and red warnings about corruption and then get stuck in a bootloop on the first black and white boot image.
Please can someone help me get back into android; if possible I would like root but in the end just a working phone.
Thanks.
As far as I know it's a dm-verity issue. There might be several ways to fix it but the only one I know is to flash Magisk from TWRP. I still run version 12 because 13.x won't install for me.
From my expierience, unlocking and locking bootloader will wipe your userdata , so backup! How I root mine is, first unlock through fastboot, than fastboot boot twrp, instead of flashing, flash magisk through twrp, than lock the bootloader again through fastboot. This keeps you from getting messages about corruption and has you rooted. Whenever I need twrp I just boot it instead of flashing it. I also made a backup using twrp, just to keep things safe and easy to restore...
Edit: To get out of bootloop you either do a factory reset or flash the image found in this forum using fastboot update...
You should have a look at this thread: https://forum.xda-developers.com/swift-2/how-to/marmite-wileyfox-ota-nougat-android-7-1-t3654999
I flashed twrp and installed magisk successfully. However I entered magisk and it asked me to update via direct method which I did. Then the phone restarted I got this error... I can boot into download mode but not twrp. What should I do ? Thanks
I fixed it..just reflash firmware using Odin. Bummer now I have to wait 14 days again basically
So i had a hickup with updating magisk to v20.3.
The result was that after a reboot the device got stuck in fastboot mode.
I went to TWRP 3.3.0 recovery and backed up all offered partitions before then attempting to re-flash magisk.
Didn't work out.
Then i heard that if you extract the boot.img from the stock firmware and flash it with fastboot you can get back to a working state where you can install Magisk again.
So i thought.
Now after booting i am greeted by the miui first install wizard and the whole set of apps seems to be gone as well as my settings.
IIRC i only removed the dalvik cache which shouldn't affect this state.
Where in the procedure is the mistake and can i get the old pre-broken update state back? I am afraid something has been lost in the process
selemine said:
So i had a hickup with updating magisk to v20.3.
The result was that after a reboot the device got stuck in fastboot mode.
I went to TWRP 3.3.0 recovery and backed up all offered partitions before then attempting to re-flash magisk.
Didn't work out.
Then i heard that if you extract the boot.img from the stock firmware and flash it with fastboot you can get back to a working state where you can install Magisk again.
So i thought.
Now after booting i am greeted by the miui first install wizard and the whole set of apps seems to be gone as well as my settings.
IIRC i only removed the dalvik cache which shouldn't affect this state.
Where in the procedure is the mistake and can i get the old pre-broken update state back? I am afraid something has been lost in the process
Click to expand...
Click to collapse
Just install the latest stock rom then install recovery and restore all the backed up partitions.
Now install magisk and reboot.
If that doesn't work (u get into fastboot again) then just flash the boot.img file via fastboot and then reboot.
if i restore the backed up partitions and install magisk over it i get back to the non-booting , stuck in fastboot version. So something is wrong in the state of denmark.
selemine said:
if i restore the backed up partitions and install magisk over it i get back to the non-booting , stuck in fastboot version. So something is wrong in the state of denmark.
Click to expand...
Click to collapse
I looked at the /data backup from twrp and it is only 3mb, unless stuff got moved to /system or so, it seems to be gone forever.
Hell , i wil never update magisk again.
selemine said:
I looked at the /data backup from twrp and it is only 3mb, unless stuff got moved to /system or so, it seems to be gone forever.
Hell , i wil never update magisk again.
Click to expand...
Click to collapse
Don't install magisk with the rom, just restore the data, flash the stock boot.img file and then reboot.
After boot uninstall the magisk manager app and reboot to recovery and then flash magisk again.
Hi there,
I ****ed up and I'm now stuck in bootloop with no access to a computer and was wondering if I could do anything to solve my issue.
I've been testing blu spark kernel for months and wanted to go back to stock kernel.
I flashed my backup from FKM (made it with FKM too) and now I'm in bootloop.
My backup was from january build and my phone has been updated to february build since. Is it the reason of the bootloop ?
Anyway, I'm in a bootloop now and I only have an other rooted Pixel 6.
Can I do anything with it ?
I tried Android Flash Tool from Google within Chrome but the download of the rom is always stucked at some point.
I tried magisk adb module but I'm afraid it's not up to date as I'm still in fastboot after I flashed the bootloader and update the image.
Any ideas ?
First try to turn off your phone and then reboot to bootloader. Download factory image and launch flash-all.bat.
Sorry for your datas.
I haven't been able to launch flash-all.sh with termux with the second Pixel 6 I have as the fastboot version from the magisk module is too old.
I don't have a computer to do it.
bobby8921 said:
I haven't been able to launch flash-all.sh with termux with the second Pixel 6 I have as the fastboot version from the magisk module is too old.
I don't have a computer to do it.
Click to expand...
Click to collapse
Get a computer, or at least borrow one so you can restore your device using Google's flash tool. You're not fixing your bootloop without one.