OTA with Magisk Fails Using Magisk's Suggested Method - Google Pixel Questions & Answers

I followed Magisk's OTA Installation Tips but it was unsuccessful twice. I was running Magsik v16, restored images in Magisk, started the OTA, once it started processing Step 2 of 2 I installed Magisk to the second slot (after OTA). After the OTA finished installing, I rebooted the phone and it rebooted a second time before getting to the unlock screen. Checking Magisk, I found that I was unrooted and couldn't root via Magisk Manager and the OTA install had also failed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I was able to boot to the twrp bootable image and reinstall Magisk v14.3, and repeated the entire process above just to see if it was a fluke, and found myself in the same exact spot - OTA installation failed and I was unrooted again.

Don't try to OTA with any mods it will almost certainly always fail. Just flash factory image without the -w and then mod accordingly after it boots

KittyRgnarok said:
Don't try to OTA with any mods it will almost certainly always fail. Just flash factory image without the -w and then mod accordingly after it boots
Click to expand...
Click to collapse
I don't have any mods. After the first OTA was unsuccessful and I rebooted without root, I retried the standard OTA and it was successful. Then I booted to twrp via adb and successfully installed magisk v14.3 from a thumb drive to regain root. Not sure if there's a better way to regain root, because for this to be successful I have to wipe the sdcard every time.

bobo-the-drunk said:
I don't have any mods. After the first OTA was unsuccessful and I rebooted without root, I retried the standard OTA and it was successful. Then I booted to twrp via adb and successfully installed magisk v14.3 from a thumb drive to regain root. Not sure if there's a better way to regain root, because for this to be successful I have to wipe the sdcard every time.
Click to expand...
Click to collapse
Any particular reason your using 14.3 instead of 16.0?

Can't flash 16.0 from the bootable twrp image. I flash 16.0 once I boot into Android.

bobo-the-drunk said:
Can't flash 16.0 from the bootable twrp image. I flash 16.0 once I boot into Android.
Click to expand...
Click to collapse
I flashed version 16.0 on bootable twrp image today with no issues.

bobo-the-drunk said:
Can't flash 16.0 from the bootable twrp image. I flash 16.0 once I boot into Android.
Click to expand...
Click to collapse
Are you using TWRP 3.2.1-2? I install Magisk 16 after flashing the TWRP zip with a couple reboots in between to make sure everything takes.

mruno said:
Are you using TWRP 3.2.1-2? I install Magisk 16 after flashing the TWRP zip with a couple reboots in between to make sure everything takes.
Click to expand...
Click to collapse
Interesting, can your version unlock storage? I've been using the TWRP bootable from this thread. Based on the filename, I'm betting it's not TWRP 3.2.1-2

bobo-the-drunk said:
Interesting, can your version unlock storage? I've been using the TWRP bootable from this thread. Based on the filename, I'm betting it's not TWRP 3.2.1-2
Click to expand...
Click to collapse
yes it can

mruno said:
yes it can
Click to expand...
Click to collapse
OK, now you've got my attention, but where's the bootable file? All the links I can find are borked.

https://dl.twrp.me/sailfish
get the img to temp flash twrp, then flash the zip in twrp for permanent twrp recovery

mruno said:
https://dl.twrp.me/sailfish
get the img to temp flash twrp, then flash the zip in twrp for permanent twrp recovery
Click to expand...
Click to collapse
Booted to the TWRP bootable, decrypted storage successfully (yay!), (intentionally) didn't unlock system, flashed the TWRP zip, now it only boots to TWRP. I'm guessing I'll need to reflash the April 2018 image?

yea that happens sometimes. extract the boot.img from the april image and reboot to bootloader and then with adb: fastboot flash bootloader bootloader.img
afterwards, flashtwrp img and install twrp zip

Related

Asus Zenfone a601cg not removing twrp recovery

Hello,
earlier i have unlock my device & installed twrp 2.8.6.0., but now when I am trying to install firmware recovery by fastboot flash recovery filename.img writing is successful but after starting the recovery mode phone starts into twrp recovery.
Why i want to remove twrp??? because its not running adb sideload & pc is also not able to detect the device is sideload option
First of all, why do you need to run adb sideload? In twrp, you can use adb push instead and push the files to /sdcard and flash from there. Second of all, did you get that recovery from your stock rom?
RAZERZDAHACKER said:
First of all, why do you need to run adb sideload? In twrp, you can use adb push instead and push the files to /sdcard and flash from there. Second of all, did you get that recovery from your stock rom?
Click to expand...
Click to collapse
Hi,
My Zenfone stuck on boot animation & i tried all the available info such as factory reset & wipe cache but nothing work, so planing to reinstall the same firmware which i installed earlier when the same issue (boot animation) happened & that time i installed firmware through stock recovery via sideload command and successful installed the rom after that i installed twrp for some work & now again i am trying to install the same firmware via twrp its not installing... so i want to install stock recovery again...
pratikdoshi4u said:
Hi,
My Zenfone stuck on boot animation & i tried all the available info such as factory reset & wipe cache but nothing work, so planing to reinstall the same firmware which i installed earlier when the same issue (boot animation) happened & that time i installed firmware through stock recovery via sideload command and successful installed the rom after that i installed twrp for some work & now again i am trying to install the same firmware via twrp its not installing... so i want to install stock recovery again...
Click to expand...
Click to collapse
Check that device is mounted mtp in twrp, then push the files to the sdcard on the device and flash from twrp. Good luck!
RAZERZDAHACKER said:
Check that device is mounted mtp in twrp, then push the files to the sdcard on the device and flash from twrp. Good luck!
Click to expand...
Click to collapse
Not working, please suggest any other way or process
pratikdoshi4u said:
Not working, please suggest any other way or process
Click to expand...
Click to collapse
I need more than just "not working", what's specifically not working?
RAZERZDAHACKER said:
I need more than just "not working", what's specifically not working?
Click to expand...
Click to collapse
Hi,
i have the firmware which i installed earlier in sdcard & tried to install via twrp recovery but now its showing following error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
pratikdoshi4u said:
Hi,
i have the firmware which i installed earlier in sdcard & tried to install via twrp recovery but now its showing following error
Click to expand...
Click to collapse
What android version do you have and which android version is the one you're flashing?
RAZERZDAHACKER said:
What android version do you have and which android version is the one you're flashing?
Click to expand...
Click to collapse
Hello,
The one i earlier installed was "UL-ASUS_T00F-WW-3.24.40.78-user".
But right now its showing 4.4.2 i want to install the same one or higher...
Have you tried reflashing twrp via fastboot?
RAZERZDAHACKER said:
Have you tried reflashing twrp via fastboot?
Click to expand...
Click to collapse
Hi,
Sorry didn't get you, what exactly i have to do.

Rooted Nokia 8 (Unlocked NB1) boot images 00WW_4_84A_SP03 with May'18 Security Patch

Here, presenting you - latest boot image for Nokia 8 ( NB1 ) with May 2018 Security Patch.
To root your phone using Magisk,
1) Enable "USB Debugging"
2) Install MagiskManager
3) Download patched boot image from https://mega.nz/#F!XYJWzDoa!cJYeg40AtGL2jsxYnyByXw ( NB1_00WW_4_84A_SP03 )
3) Run "adb reboot bootloader"
4) Type "fastboot boot NB1_00WW_4_84A_SP03.img" from same folder where downloaded that img file. [ Don't FLASH it. It will break your WiFi !!! ]
5) Let it boot, and then Open MagiskManager --> Install --> Direct Install.
Once install is done, reboot normally. And - voila - you have MagiskRooted NOKIA 8 ( NB1 )
( P.S. - I will try to keep the latest image updated. Though, Wifi is not working on that image, so don't try to flash it in boot_a partition. For future reference, boot_a partition is /dev/block/sda6 and boot_b partition is /dev/block/sda13 )
Hope it helps
More P.S - Thanks to @hikari_calyx for the bootloader unlock and initial helps
Thanks!
I have flashet it and can't use wifi, but it's rooted.
so what do I have to do to make WiFi OK again?
thx!
head66 said:
Thanks!
I have flashet it and can't use wifi, but it's rooted.
so what do I have to do to make WiFi OK again?
thx!
Click to expand...
Click to collapse
Bro, already told - not to flash . You just boot from the kernel using fastboot, then patch your own mobile boot_a partition using MagiskManager, and then reboot back again normally. In that way your Wifi is preserved. Else, boot_a and boot_b partition signing will not match, and so wifi will not work !!
Thx for answer!
i have my sda6 patched with MM and flashed it but wifi not work again.
How do I do that: boot from the kernel using fastboot?
Thanks!
Rather using fastboot flash , use following command
"fastboot boot NB1_00WW_4_84A_SP03.img"
It will boot to that temporary kernel. Then patch your own kernel and get back ur wifi. Though to do that now, you need to revert to your actual kernel 1st.
Hmm my device have SP02 not SP03, its a problem?
And wich file is my orig. kernel in /dev/block/?
sda6 is bootimg only or not?
I have a backup from orig. stock sda6 but not from sda13! This are patched with MM to patched_boot.img and then flashed several times to bootpart_a and _b. But always after no wifi.
ps: I have made several flash attempts with fastboot but all wifi not work.
I want to start a final attempt to flash a complete ROM, but that's complicated.
Or what IMGs do I need to flash exactly from the extracting *nb0?
I tried flashing im recovery mode this *nb0 but it not work, see log:
..............................................................................................
*Apply update from ADB
Now send the package you want to apply to the device with 'adb sideload filename'
Finding update package
Opening update package
Verifying update package
E: Footer is wrong
Update package verification took 0.0s (result 1)
E: Signature verification failed
E: error: 21
..................................................................................................
What else can I try to rescue it?
All works only wifi not. :crying:
fastboot flash boot_a sda6
fastboot flash boot_b sda6
wifi not work again, i'm cryin!
Easy way - update to SP03 . Then just follow the step. Boot_b is not required.
I tried but give error, becouse not wifi or rooted device.
Maybe i can manualy update with fastboot, but have not the file.
Or is it different way?
Maybe if I try to disroote device and lock bootloader again?
I think W/O wifi will not worked.
Any idea?
Maybe can MagiskM help to hide root?
Is it enable for never unlocked phone?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have this problem :|
You should have your device unlocked before trying to boot a modified boot image (unsecure)…..
Topogigi said:
You should have your device unlocked before trying to boot a modified boot image (unsecure)…..
Click to expand...
Click to collapse
how ?
ara1370 said:
how ?
Click to expand...
Click to collapse
Check here
https://forum.xda-developers.com/nokia-8/how-to/nokia-8-unofficial-bootloader-unlock-t3790316
@ bidhata
You have the file 00WW_4_84A_SP03.zip for manual update from recovery mode?
I have SP02, I think the update is successfully.
Thanks!
Really sorry. Looking for same. If can get that, may try to port TWRP.
head66 said:
@ bidhata
You have the file 00WW_4_84A_SP03.zip for manual update from recovery mode?
I have SP02, I think the update is successfully.
Thanks!
Click to expand...
Click to collapse
Lol just do an system update.
HOw to unlock bootloader???
because boot command is not allowed in locked sate
@hikari_calyx is offering a service for USD 5 to unlock the bootloader.
New OTA Update is here, i guess root doesnt stay? New boot img coming so we can root again?
Ranteis said:
New OTA Update is here, i guess root doesnt stay? New boot img coming so we can root again?
Click to expand...
Click to collapse
Already updated here - https://forum.xda-developers.com/nokia-8/development/pre-rooted-boot-image-nokia-nb1-v4-88b-t3798063
Hope it helps.

Installing magisk result in softbrick?

I have OnePlus 7 Pro GM1917 12G ram/256G storage, wiped device and update to OxygenOS android 10.
I have magisk manager APK installed, saying magisk is not installed.
Then I downloaded magisk version 21 .zip from the app, it's placed under "downloads."
I boot into TWRP recovery, then select the magisk.zip to be installed. However this results in the phone only being able to boot into fastboot and not the actual OS.
I have also tried to install magisk using adb sideload and it faces the same issue.
The softbrick can be resolved by flashing TWRP (.zip) again.
Flashing magisk.zip and twrp.zip result in successful boot into OS but magisk is still shown as not installed.
Any ideas on what might be happening here?
Thanks in advance.
meleeb4kr said:
I have OnePlus 7 Pro GM1917 12G ram/256G storage, wiped device and update to OxygenOS android 10.
I have magisk manager APK installed, saying magisk is not installed.
Then I downloaded magisk version 21 .zip from the app, it's placed under "downloads."
I boot into TWRP recovery, then select the magisk.zip to be installed. However this results in the phone only being able to boot into fastboot and not the actual OS.
I have also tried to install magisk using adb sideload and it faces the same issue.
The softbrick can be resolved by flashing TWRP (.zip) again.
Flashing magisk.zip and twrp.zip result in successful boot into OS but magisk is still shown as not installed.
Any ideas on what might be happening here?
Thanks in advance.
Click to expand...
Click to collapse
Flash TWRP THEN Magisk.
Sent from my GM1917 using Tapatalk
krishaun27 said:
Flash TWRP THEN Magisk.
Sent from my GM1917 using Tapatalk
Click to expand...
Click to collapse
That's what I did exactly, before I had this problem.
If I reboot to recovery, I am greeted with teamwin logo instead of the normal recovery mode.
I installed TWRP by using "twrp-3.3.1-70-guacamole-unified-installer-mauronofrio.zip" for OnePlus 7 Pro on Android 10. Then reboot, load recovery, then proceed to try install "Magisk-v20.1.zip" I am hit with the problems stated above.
meleeb4kr said:
That's what I did exactly, before I had this problem.
If I reboot to recovery, I am greeted with teamwin logo instead of the normal recovery mode.
I installed TWRP by using "twrp-3.3.1-70-guacamole-unified-installer-mauronofrio.zip" for OnePlus 7 Pro on Android 10. Then reboot, load recovery, then proceed to try install "Magisk-v20.1.zip" I am hit with the problems stated above.
Click to expand...
Click to collapse
Flash in This order : TWRP installer, Magisk, then a custom kernel (make sure it's for Oxygen OS Android 10).
Sent from my GM1917 using Tapatalk
krishaun27 said:
Flash in This order : TWRP installer, Magisk, then a custom kernel (make sure it's for Oxygen OS Android 10).
Sent from my GM1917 using Tapatalk
Click to expand...
Click to collapse
Installing "Magisk-v20.1.zip" will result in the softbrick stated above.
I am not able to proceed beyond this step.
Also, I do not have a custom kernel yet, running stock after official update to Android 10.
I took a picture of the twrp system log after installing Magisk-v20.1.zip
The commands selected are zip verificaton and inject TWRP after install
https://i.imgur.com/tyUgpRm.jpg
The system results in "magisk is not installed"
meleeb4kr said:
I took a picture of the twrp system log after installing Magisk-v20.1.zip
The commands selected are zip verificaton and inject TWRP after install
https://i.imgur.com/tyUgpRm.jpg
The system results in "magisk is not installed"
Click to expand...
Click to collapse
Uncheck "Zip Signature Verification"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my GM1917 using Tapatalk
krishaun27 said:
Uncheck "Zip Signature Verification" View attachment 4865651
Sent from my GM1917 using Tapatalk
Click to expand...
Click to collapse
Hi,
I tried what you suggested, the phone will still not boot to main OS and only stuck in fastboot mode.
meleeb4kr said:
Hi,
I tried what you suggested, the phone will still not boot to main OS and only stuck in fastboot mode.
Click to expand...
Click to collapse
You need a custom kernel to boot up. BLU SPARK or Elemental or smurf. Or flash a patched (rooted) boot image in fastboot.
Sent from my GM1917 using Tapatalk
krishaun27 said:
You need a custom kernel to boot up. BLU SPARK or Elemental or smurf. Or flash a patched (rooted) boot image in fastboot.
Sent from my GM1917 using Tapatalk
Click to expand...
Click to collapse
Does it not work with the original kernel?
I was using it with the prior update before Android 10, without custom kernel or rom.
meleeb4kr said:
Does it not work with the original kernel?
I was using it with the prior update before Android 10, without custom kernel or rom.
Click to expand...
Click to collapse
No it does not. You need a Patched boot image or a custom kernel which contains a patched and rooted boot image.
Sent from my GM1917 using Tapatalk
krishaun27 said:
No it does not. You need a Patched boot image or a custom kernel which contains a patched and rooted boot image.
Sent from my GM1917 using Tapatalk
Click to expand...
Click to collapse
Can you guide me on how to get this patched stock boot image?
meleeb4kr said:
Can you guide me on how to get this patched stock boot image?
Click to expand...
Click to collapse
All you need to do is get ahold of the OTA update for that version. You can find your version in "about phone" and you can find the files on Google. Then you can use a tool called "payload dumper" to extract the boot.img from the payload.bin inside. (just run it until it says "boot", then wait for some other text to appear and close the window. "boot.img" will be in the output folder) Transfer the boot.img to the phone, use Magisk Manager to patch it, transfer the `magisk_patched.img` back to your computer, boot into fastboot and then `fastboot flash boot magisk_patched.img`.
TWRP will probably be gone. Download the TWRP installer zip from the TWRP website, and use Magisk Manager to flash it. You will have TWRP. Then you must use Magisk to reinstall itself while you still have root access, otherwise Magisk will be gone on reboot and you will need to go through the whole process of flashing the patched boot.img again.
After OTAs, before rebooting, first flash a Magisk module called "TWRP A/B retention module", and then install Magisk to the inactive slot. Then reboot as normal. Your root and TWRP should then stay self-hosting. Magisk should prevent the OS from suppressing TWRP, but this only works if you did not forget to reinstall Magisk. Otherwise you have to start over from square one. I had to do that once.
Soon I'll write a guide post on my experience. It was a very intense 7 hours, but I learned so much in that time...
LoganDark said:
All you need to do is get ahold of the OTA update for that version. You can find your version in "about phone" and you can find the files on Google. Then you can use a tool called "payload dumper" to extract the boot.img from the payload.bin inside. (just run it until it says "boot", then wait for some other text to appear and close the window. "boot.img" will be in the output folder) Transfer the boot.img to the phone, use Magisk Manager to patch it, transfer the `magisk_patched.img` back to your computer, boot into fastboot and then `fastboot flash boot magisk_patched.img`.
TWRP will probably be gone. Download the TWRP installer zip from the TWRP website, and use Magisk Manager to flash it. You will have TWRP. Then you must use Magisk to reinstall itself while you still have root access, otherwise Magisk will be gone on reboot and you will need to go through the whole process of flashing the patched boot.img again.
After OTAs, before rebooting, first flash a Magisk module called "TWRP A/B retention module", and then install Magisk to the inactive slot. Then reboot as normal. Your root and TWRP should then stay self-hosting. Magisk should prevent the OS from suppressing TWRP, but this only works if you did not forget to reinstall Magisk. Otherwise you have to start over from square one. I had to do that once.
Soon I'll write a guide post on my experience. It was a very intense 7 hours, but I learned so much in that time...
Click to expand...
Click to collapse
I just flashed magisk in twrp no boot img patch needed
TheMadScientist said:
I just flashed magisk in twrp no boot img patch needed
Click to expand...
Click to collapse
That may have just patched the boot image from TWRP. My phone wouldn't let me flash TWRP with fastboot, so I had to install Magisk first. YMMV, especially since my device is the crippled T-Mobile variant
LoganDark said:
That may have just patched the boot image from TWRP. My phone wouldn't let me flash TWRP with fastboot, so I had to install Magisk first. YMMV, especially since my device is the crippled T-Mobile variant
Click to expand...
Click to collapse
Mine is too. Lol. Only issues I had with this device was sim unlock. If one follows the method of installing the developer preview they can enable oem unlock then manually update to a stable international version they have full fastboot access. I've been through it all in the last week or so
TheMadScientist said:
Mine is too. Lol. Only issues I had with this device was sim unlock. If one follows the method of installing the developer preview they can enable oem unlock then manually update to a stable international version they have full fastboot access. I've been through it all in the last week or so
Click to expand...
Click to collapse
For me it was 7 hours from first receiving the phone to having it totally pwned with TWRP and Magisk, and that was about 8 hours ago

[Q][RECOVERY][3.4.0-0][kane] Official TWRP & Root for Motorola One Vision

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Root & TWRP 3.4.0 for Android 10.​
Page on the official TWRP website https://twrp.me/motorola/motorolaonevision.html
Installation Instruction
1. Download twrp-3.4.0-0-kane.img and twrp-installer-3.4.0-0-kane.zip TWRP, patched vbmeta.img and Magisk-disable-dm-verity-v20.4.zip (see in the attached files).
2. Copy files:
- twrp-3.4.0-0-kane.img and vbmeta_patch.img to the folder adb with the adb & fastboot drivers;
- twrp-installer-3.4.0-0-kane.zip, Magisk-disable-dm-verity-v20.4.zip on SD Card.
3. Boot the phone in fastboot mode, connect it to a PC and perform the following commands:
Code:
fastboot flash vbmeta C:\adb\vbmeta_patch.img
Code:
fastboot boot C:\adb\twrp-3.4.0-0-kane.img
The phone will load into TWRP.
4. Go to "Install". Click on "Select Storage" button, select Micro SDCard, OK. Install twrp-installer-3.4.0-0-kane.zip.
5. Go to "Wipe" and press Format Data for deencryption. Enter Yes on request. We go to TWRP Main Menu and reboot again in Recovery.
6. Go to "Install". Click on "Select Storage" button, select Micro SDCard, OK. Install Magisk-disable-dm-verity-v20.4.zip.
7. Reboot into the system.
Has anyone succesfully decrypted data when booting TWRP? I've wiped after installing the ZIP and I cannot decrypt data there. I've tried changing device password from PIN to pass, as it requires me to type a password in TWRP, and I still can't decrypt there.
No problems here.
adb fastboot boot twrp_3.4.0-0.img and then flash twrp_3.4.0-0 zip in TWRP.
Havoc OS booting fine.
Gesendet von meinem Phh-Treble vanilla mit Tapatalk
I think something's messed up with my phone by transitioning from the older TWRP to the newer one
Edit: My device fails to fastboot boot twrp after I try reflashing the entire firmware. I think it has something to do with the edited vbmeta file I was using before, because it boots when I flash the patched vbmeta file this TWRP doesn't need.
ilia3367 said:
After almost a year, the official TWRP for Motorola One Vision has finally arrived!
Page on the official TWRP website https://twrp.me/motorola/motorolaonevision.html
Click to expand...
Click to collapse
Good morning,
Currently, I have installed the version you patched, 3.3.1.
Can it be installed from the "unofficial" version: https://forum.xda-developers.com/showthread.php?p=80352223?.
Does it give a problem, or does it work perfectly?
Regards
Enviado desde mi unknown mediante Tapatalk
gonzo1963 said:
Good morning,
Currently, I have installed the version you patched, 3.3.1.
Can it be installed from the "unofficial" version: https://forum.xda-developers.com/showthread.php?p=80352223?.
Does it give a problem, or does it work perfectly?
Regards
Enviado desde mi unknown mediante Tapatalk
Click to expand...
Click to collapse
The official TWRP instructions do not mention it, but you still need the patched vbmeta file for booting TWRP. Also, encryption is not working as of QSAS30.62-24-10 and 62-24-7 ROMs. I ended up going back to this TWRP version https://forum.xda-developers.com/one-vision/how-to/twrp-3-3-1-0-root-updated-kane-troika-t4102839
daekdroom said:
The official TWRP instructions do not mention it, but you still need the patched vbmeta file for booting TWRP. Also, encryption is not working as of QSAS30.62-24-10 and 62-24-7 ROMs. I ended up going back to this TWRP version https://forum.xda-developers.com/one-vision/how-to/twrp-3-3-1-0-root-updated-kane-troika-t4102839
Click to expand...
Click to collapse
Good afternoon,
Has anyone tried to install this TWRP starting from a firmware "no touch" ("clean install")?
Regards
daekdroom said:
Has anyone succesfully decrypted data when booting TWRP? I've wiped after installing the ZIP and I cannot decrypt data there. I've tried changing device password from PIN to pass, as it requires me to type a password in TWRP, and I still can't decrypt there.
Click to expand...
Click to collapse
Decryption may or may not work with different OS releases, it's mentioned in TWRP downloads section of this device.
---------- Post added at 07:16 AM ---------- Previous post was at 07:05 AM ----------
gonzo1963 said:
Good afternoon,
Has anyone tried to install this TWRP starting from a firmware "no touch" ("clean install")?
Regards
Click to expand...
Click to collapse
Yes, from what I heard it doesn't boot through fastboot boot either with patched vbmeta or clean ROM. If you are rooted, you can use magisk module TWRP installer, but after flashing you will loose root access asusual or you can flash recovery ramdisk through existing recovery. Also don't forget unofficial builds.
Nevil Sebastian said:
Decryption may or may not work with different OS releases, it's mentioned in TWRP downloads section of this device.
---------- Post added at 07:16 AM ---------- Previous post was at 07:05 AM ----------
Yes, from what I heard it doesn't boot through fastboot boot either with patched vbmeta or clean ROM. If you are rooted, you can use magisk module TWRP installer, but after flashing you will loose root access asusual or you can flash recovery ramdisk through existing recovery. Also don't forget unofficial builds.
Click to expand...
Click to collapse
Good morning,
From what I understand it doesn't work well in either case, does it?.
So what is it for, is it better to use the old "patched" TWRP: https://forum.xda-developers.com/showthread.php?p=82629961?
Regards
Enviado desde mi unknown mediante Tapatalk
gonzo1963 said:
Good morning,
From what I understand it doesn't work well in either case, does it?.
So what is it for, is it better to use the old "patched" TWRP: https://forum.xda-developers.com/showthread.php?p=82629961?
Regards
Enviado desde mi unknown mediante Tapatalk
Click to expand...
Click to collapse
You can use whichever build you want. We should wait until everything gets solved slowly.
Nevil Sebastian said:
You can use whichever build you want. We should wait until everything gets solved slowly.
Click to expand...
Click to collapse
Good morning,
Thanks for the reply, but ...
This new and official TWRP, does it work 100% or not?
Regards
I did the Instruction to install TWRP and geting Root.
Do I have to unlock my bootloader first before doing this? I just noticed we finally have a custom ROM for the One Vision! This finally makes it worth while to unlock, install TWRP, install a custom ROM and root this thing finally!
alphalog said:
No problems here.
adb fastboot boot twrp_3.4.0-0.img and then flash twrp_3.4.0-0 zip in TWRP.
Havoc OS booting fine.
Gesendet von meinem Phh-Treble vanilla mit Tapatalk
Click to expand...
Click to collapse
[How do you install HavocOS? Is there any ROM source?]
delete this
HourlongTuna5 said:
[How do you install HavocOS? Is there any ROM source?]
Click to expand...
Click to collapse
Havoc-OS GSI
Havoc-OS Generic System Image for all devices
www.pling.com
[email protected]
So which TWRP do you recommend? The latest version (3.4.0-0)? Or the older version (3.3.1-0) ??
tin0o said:
So which TWRP do you recommend? The latest version (3.4.0-0)? Or the older version (3.3.1-0) ??
Click to expand...
Click to collapse
3.4.0-0 (for gsi and stock image)
Download TWRP for kane
Download TWRP Open Recovery for kane
eu.dl.twrp.me
ilia3367 said:
Root & TWRP 3.4.0 for Android 10.​
Page on the official TWRP website https://twrp.me/motorola/motorolaonevision.html
Installation Instruction
1. Download twrp-3.4.0-0-kane.img and twrp-installer-3.4.0-0-kane.zip TWRP, patched vbmeta.img and Magisk-disable-dm-verity-v20.4.zip (see in the attached files).
2. Copy files:
- twrp-3.4.0-0-kane.img and vbmeta_patch.img to the folder adb with the adb & fastboot drivers;
- twrp-installer-3.4.0-0-kane.zip, Magisk-disable-dm-verity-v20.4.zip on SD Card.
3. Boot the phone in fastboot mode, connect it to a PC and perform the following commands:
Code:
fastboot flash vbmeta C:\adb\vbmeta_patch.img
Code:
fastboot boot C:\adb\twrp-3.4.0-0-kane.img
The phone will load into TWRP.
4. Go to "Install". Click on "Select Storage" button, select Micro SDCard, OK. Install twrp-installer-3.4.0-0-kane.zip.
5. Go to "Wipe" and press Format Data for deencryption. Enter Yes on request. We go to TWRP Main Menu and reboot again in Recovery.
6. Go to "Install". Click on "Select Storage" button, select Micro SDCard, OK. Install Magisk-disable-dm-verity-v20.4.zip.
7. Reboot into the system.
Click to expand...
Click to collapse
Hi....
Should i use this method for android 11 ?

Qualcom Crashdump Mode

Hello,
I followed this guide at the part called :
Root OnePlus 8T using Magisk and Install OxygenOS OTA Updates after Rooting
A complete guide to root OnePlus 8T using Magisk, without TWRP recovery. Also, learn how to install OxygenOS OTA updates on rooted OnePlus 8T.
www.thecustomdroid.com
Installing OxygenOS OTA Updates on Rooted OnePlus 8T
Ive download the latest OTA via the Updater up and not from the phone updates becaus eI had XXX magsik rom on my phone. After I finish the phone rebooted to this mode!
The only thing that I can do now id to click vol up and down and phone button to go into fastboot mode an then to recovery mode, but I cant reboot back my phone normally.
Could you please let me know what the current situation means, regrading all the data that is one my phone? can I somehow flash a rom and go back to how it was before? Is root gone?
And if someone call please help me and tell me what I should do next?
Thank you!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think your only way back is to use the MSN TOOL for your Phone Modell.
https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/ <<< Look there that's the Thread for it, good luck and hope you get your Phone to work
I assume your bootloader is unlocked are you able to get into fastboot?
In that case try to extract the latest boot image for your update from the update zip (using payloader dumper) and do fastboot boot boot.img ? That might work
Or you can try to boot some recovery image and see if you can disable xxx module as that might be the problem.
Thisis just some steps you can try before using the msm tool that will wipe your phone
Which version of the rom are you running? Global/NA? IN? EU?
I just had this happen to me. The steps I took to update the OTA and keep Magisk root switched my active slot to b from a. I was able to boot the phone to fastboot mode by holding down both volume buttons and the power button. Then after connecting my phone to my laptop I used fastboot to switch the active slot back to a (fastboot --set-active=a). I was then able to boot the phone. When I booted, it was the prior OS and not the OTA. However, I then went through the steps to load the OTA again. This, of course, wipes out root, but I should be able to get root back using the steps from the following link: https://forum.xda-developers.com/t/guide-oneplus-8t-easy-root-for-all-unlocked-variants.4210775/. Now I just need to figure out how to get 5G on my 8T (which the latest OTA was supposed to solve, but didn't).
rcbjr2 said:
I just had this happen to me. The steps I took to update the OTA and keep Magisk root switched my active slot to b from a. I was able to boot the phone to fastboot mode by holding down both volume buttons and the power button. Then after connecting my phone to my laptop I used fastboot to switch the active slot back to a (fastboot --set-active=a). I was then able to boot the phone. When I booted, it was the prior OS and not the OTA. However, I then went through the steps to load the OTA again. This, of course, wipes out root, but I should be able to get root back using the steps from the following link: https://forum.xda-developers.com/t/guide-oneplus-8t-easy-root-for-all-unlocked-variants.4210775/. Now I just need to figure out how to get 5G on my 8T (which the latest OTA was supposed to solve, but didn't).
Click to expand...
Click to collapse
Hi, Same thing just happened to me after trying to update the software. I booted my phone into fastboot and connected to my PC. But I don't see an option to switch to "set-active=a".
Is this option "set-active=a" supposed to show?
saar17 said:
Hello,
I followed this guide at the part called :
Root OnePlus 8T using Magisk and Install OxygenOS OTA Updates after Rooting
A complete guide to root OnePlus 8T using Magisk, without TWRP recovery. Also, learn how to install OxygenOS OTA updates on rooted OnePlus 8T.
www.thecustomdroid.com
Installing OxygenOS OTA Updates on Rooted OnePlus 8T
Ive download the latest OTA via the Updater up and not from the phone updates becaus eI had XXX magsik rom on my phone. After I finish the phone rebooted to this mode!
The only thing that I can do now id to click vol up and down and phone button to go into fastboot mode an then to recovery mode, but I cant reboot back my phone normally.
Could you please let me know what the current situation means, regrading all the data that is one my phone? can I somehow flash a rom and go back to how it was before? Is root gone?
And if someone call please help me and tell me what I should do next?
Thank you!
View attachment 5214733
Click to expand...
Click to collapse
Hello, this just happed to me. Were you able to fix this?

Categories

Resources