This morning I've just received the February 2019 security update, I've downloaded it but when the installation starts then it fails. Any idea why this happens?
Somebody has the same issue?
Thanks
Restart, connect charger and start again when above 60%.
Sent from my Mi A2 Lite using Tapatalk
locovibe said:
Restart, connect charger and start again when above 60%.
Click to expand...
Click to collapse
I'm going to try and then I'll let you know.
Thank you very much!
locovibe said:
Restart, connect charger and start again when above 60%.
Sent from my Mi A2 Lite using Tapatalk
Click to expand...
Click to collapse
Not work for me. Since January I have this problem.
Xmata said:
Not work for me. Since January I have this problem.
Click to expand...
Click to collapse
You need to reflash whole rom with miflasher and unlock bootloader.
Some people solved the issue by stopping the download, turning on mobile data and resuming download on mobile data. Don't forget to turn off your WiFi. Try this before flashing the stock rom again and losing all your data.
Check the log and reflash touched partitions
konan82 said:
This morning I've just received the February 2019 security update, I've downloaded it but when the installation starts then it fails. Any idea why this happens?
Somebody has the same issue?
Thanks
Click to expand...
Click to collapse
I had the same even after reflashing (fastboot flash boot boot.img) of boot image: I do use Magisk. I checked what is happening during the failing update by
adb logcat -e update_engine
It will report you where and what is failing.
In my case it was complaining on system checksum:
02-20 10:06:56.298 2188 2188 I update_engine: [0220/100656.298722:INFO:delta_performer.cc(386)] Applying 4096 operations to partition "system"
02-20 10:06:56.409 2188 2188 E update_engine: [0220/100656.408950:ERROR:delta_performer.cc(990)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
So I reflashed system and the update went on well.
Thus you need a computer with adb and fastboot available and stock image from http://en.miui.com/download-354.html of the same version as currently installed.
yakovpol said:
I had the same even after reflashing (fastboot flash boot boot.img) of boot image: I do use Magisk. I checked what is happening during the failing update by
adb logcat | grep update_engine (under Linux)
It will report you where and what is failing.
In my case it was complaining on system checksum:
02-20 10:06:56.298 2188 2188 I update_engine: [0220/100656.298722:INFO:delta_performer.cc(386)] Applying 4096 operations to partition "system"
02-20 10:06:56.409 2188 2188 E update_engine: [0220/100656.408950:ERROR:delta_performer.cc(990)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
So I reflashed system and the update went on well.
Thus you need a computer with adb and fastboot available and stock image from http://en.miui.com/download-354.html of the same version as currently installed.
Click to expand...
Click to collapse
Does this format all data?
wenna.speedy said:
You need to reflash whole rom with miflasher and unlock bootloader.
Click to expand...
Click to collapse
Unlock of bootloader will format all partitions and erase all my data, right?
konan82 said:
Unlock of bootloader will format all partitions and erase all my data, right?
Click to expand...
Click to collapse
reflashing rom lock your bootloader. it will erase your data.
unlocking bootloader via adb erase your data again.
if you have rooted phone you can't use OTA
Finally i have also got feb security update after a long waiting period.
IO13 said:
if you have rooted phone you can't use OTA
Click to expand...
Click to collapse
No my phone isn't rooted. I'm still with locked bootloader
marstonpear said:
Some people solved the issue by stopping the download, turning on mobile data and resuming download on mobile data. Don't forget to turn off your WiFi. Try this before flashing the stock rom again and losing all your data.
Click to expand...
Click to collapse
I've tried to download the entire update without WiFi, using mobile data but nothing to do
IO13 said:
if you have rooted phone you can't use OTA
Click to expand...
Click to collapse
Of course you can,
read this:
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
I followed the instructions and updated my phone.
I had no problems
konan82 said:
Does this format all data?
Click to expand...
Click to collapse
Of course, not.
Reflashing of boot or system partition doesn't touch you data partition.
---------- Post added at 07:21 PM ---------- Previous post was at 07:04 PM ----------
wenna.speedy said:
reflashing rom lock your bootloader. it will erase your data.
unlocking bootloader via adb erase your data again.
Click to expand...
Click to collapse
It depends how you reflash. Some scripts provided with the stock ROM do contain bootloader lock command. Some do erase data. The performing actions follow from script names. If you are not sure, open a script and check the commands inside.
In a case you have a problem with the OTA update, it is unlikely connected to your data partition. So no need in reflashing it/reflashing entire phone and loosing your data.
---------- Post added at 07:31 PM ---------- Previous post was at 07:21 PM ----------
konan82 said:
Unlock of bootloader will format all partitions and erase all my data, right?
Click to expand...
Click to collapse
There is a way to unlock bootloader on this phone without loosing data, see https://forum.xda-developers.com/mi-a2-lite/how-to/guide-how-to-unlock-bootloader-erasing-t3878453
You do not have to unlock bootloader if you want to flash stock ROM images.
Something interesting
I've had done something interesting recently. I'm not a "pro" user, just a normal. I couldn't install the February update through OTA, every time the install failed.
I had download from the new dump post the full rom. (Sorry i'm a new user and i can't url posting)
k4sh44 said:
Here is the zip file with all images.
But as i told already, i wasn't able to boot with fastboot command the boot.img i extracted.
Click to expand...
Click to collapse
I have saved all my datas in my phone, then in the pc unzip all the files what i downloaded and installed the new rom with this method in fastboot mode.
HoangP05 said:
These are image files that are extracted from the payload of the android P OTA:
Warning: You will erase all of your data
Code:
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash rpm_a rpm.img
fastboot flash rpm_b rpm.img
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash mdtp_a mdtp.img
fastboot flash mdtp_b mdtp.img
fastboot flash aboot_a aboot.img
fastboot flash aboot_b aboot.img
fastboot flash sbl1_a sbl1.img
fastboot flash sbl1_b sbl1.img
Run the code and then factory reset in recovery, and you will have android P.
Click to expand...
Click to collapse
After that when my phone first rebooted, the most interesting thing was for me, all of my files and apps were in my phone, anything lost, and everything is working. I don't understand why, the new rom works good, and no need restoring.
Only the magisk wasn't good. With the magisk manager I had made a patched boot img file from the full rom files. Then I booted the new patched boot img with fastboot, and then the magisk is perfect too. (but in magisk everything had to reinstalling)
yakovpol said:
I had the same even after reflashing (fastboot flash boot boot.img) of boot image: I do use Magisk. I checked what is happening during the failing update by
adb logcat | grep update_engine (under Linux)
It will report you where and what is failing.
In my case it was complaining on system checksum:
02-20 10:06:56.298 2188 2188 I update_engine: [0220/100656.298722:INFO:delta_performer.cc(386)] Applying 4096 operations to partition "system"
02-20 10:06:56.409 2188 2188 E update_engine: [0220/100656.408950:ERROR:delta_performer.cc(990)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
So I reflashed system and the update went on well.
Thus you need a computer with adb and fastboot available and stock image from http://en.miui.com/download-354.html of the same version as currently installed.
Click to expand...
Click to collapse
Do you think a factory reset (done from the attached image) without flashing the Rom could fix the problem?
I had same problem. Something broke when I used Adaway adblocker.
Unlocking OEM with volume down button didn't work.
And than I downloaded this image http://bigota.d.miui.com/V10.0.3.0....0.PDLMIXM_20190114.0000.00_9.0_e8d8d4a6d0.tgz
This is January image.
All other images here are for months before. 10.0.3 is Jan, 10.0.2 is Dec and so on
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Unzipped with 7zip this image
_________________________________________
step 1: install adb and fastboot. ( On windows follow this link https://forum.xda-developers.com/sho....php?t=2588979 )
enable the developer menu on your phone (launch settings, go to system->"about phone" and press repeately on build number)
from the developer options ( launch settings, go to system->"about phone"->developer options ) enable adb and allow bootloader unlock
connect the phone to your PC and give adb permissions to your PC. here I used in cmd
Code:
adb devices
so it would ask for permission from PC
turn off the phone
reboot by pressing power + vol down
_________________________________________
Then with adb in recovery I used:
Code:
fastboot oem unlock
then i repeated step 1, becouse of factory reset with unlocking oem
Code:
fastboot getvar current-slot
if i got A i used A in next string, if B, i used B, where ? is used
Code:
fastboot flash boot_? boot.img
Code:
fastboot flash system_? system.img
Code:
fastboot oem lock
Rebooted phone and
then I updated, and everything worked as it should.
konan82 said:
Do you think a factory reset (done from the attached image) without flashing the Rom could fix the problem?
Click to expand...
Click to collapse
No, it will not: Data partition is not being checked during the update process.
What you can do:
(a) try to find out the reason why the update is failing. It is as simple as starting adb logcat during the update and watching through strings containing update_engine for "error" or "fail" words. Then you will know for sure what is wrong in your phone.
or
(b) reflash your current android version with flash_all_except_storage.bat (if you are under Windows) or flash_all_except_storage.sh (if you are under Linux) script which are part of the whole package http://bigota.d.miui.com/V10.0.3.0....0.PDLMIXM_20190114.0000.00_9.0_e8d8d4a6d0.tgz
Most likely you will be able to download and perform the update after this.
or
(c) wait for a few hours: Xiaomi must grant a download link for February 10.0.4.0 version at http://en.miui.com/download-354.html and then do what is in (b) option above with the newer version. You will get updated system right away. Or at your own risk use a dump of this version that someone has already provided (find the link above in the same forum).
Wish you success.
Related
Can anyone pls tell me where I can download stock rom for (lenovo) p2 preferable in zip format . And is there any unbricking tutorial .
I want this too...? if anyone can help...
I have found the stock ROM, I bricked my device in the rooting process, and am unable to flash the complete stock image, because the device reports "unable to flash bootloader on unlocked device"
itsjustbilly said:
I have found the stock ROM, I bricked my device in the rooting process, and am unable to flash the complete stock image, because the device reports "unable to flash bootloader on unlocked device"
Click to expand...
Click to collapse
Hi, because you should not flash bootloader.
you can try those 2 solutions:
the fast one, it should work. The flashall command flash every.img files he find in the fastboot directory. So try to remove the bootlader.img and execute the flashall command.
the manual one (longer one):
Put only the recovery.img, boot.img, and the system.img files ( you should have something like 13 , named "systemchunk0/12.img") in your fastboot directory and flash with fastboot ( the command is always the same: fastboot flash recovery recovery.img, fastboot flash boot boot.img, and for every single part of system.img you should flash like "fastboot flash systemchunk0(until 12).img " so you flash flash 13 times the system with avery 13 parts .
Sorry for my english i hope you solved that
itsjustbilly said:
I have found the stock ROM, I bricked my device in the rooting process, and am unable to flash the complete stock image, because the device reports "unable to flash bootloader on unlocked device"
Click to expand...
Click to collapse
Then share it no
I'll post links when I get to my computer, but they're not Cwm flash able zips, they are fast boot files that you flash from DOS on a pc
---------- Post added at 09:39 AM ---------- Previous post was at 09:37 AM ----------
aleleo87 said:
Hi, because you should not flash bootloader.
you can try those 2 solutions:
the fast one, it should work. The flashall command flash every.img files he find in the fastboot directory. So try to remove the bootlader.img and execute the flashall command.
the manual one (longer one):
Put only the recovery.img, boot.img, and the system.img files ( you should have something like 13 , named "systemchunk0/12.img") in your fastboot directory and flash with fastboot ( the command is always the same: fastboot flash recovery recovery.img, fastboot flash boot boot.img, and for every single part of system.img you should flash like "fastboot flash systemchunk0(until 12).img " so you flash flash 13 times the system with avery 13 parts .
Sorry for my english i hope you solved that
Click to expand...
Click to collapse
I did try this, but I still have no signal because the modem file is part of the bootloader, and no modem means no mobile signal
itsjustbilly said:
I'll post links when I get to my computer, but they're not Cwm flash able zips, they are fast boot files that you flash from DOS on a pc
---------- Post added at 09:39 AM ---------- Previous post was at 09:37 AM ----------
I did try this, but I still have no signal because the modem file is part of the bootloader, and no modem means no mobile signal
Click to expand...
Click to collapse
Ah ok i didnt understand that you have this modem issue. I don't kno how to help you...you phone is bricked so you can test few solutions without more risks .
before flash the original recovery , boot and system by fastboot, you can try to install TWRP again and flash only the bootloader from TWRP (should support .zip and .img files). Then you turn the phone in fastboot mode and flash other stuff .
Taken from post 4 of the TWRP page on lenovo P2 forum
smaranramesh said:
Then share it no
Click to expand...
Click to collapse
Factory Images & Systemless Mode
Q: I messed up help me?!
So you screwed up and didn't follow Rule Number One in the IT-Handbook?
Which is: Always create a backup before working on a system?
Download the Factory State Images. Which are all flashable with fastboot: https://goo.gl/JTCwKj
Place the files you want replaced into the "Minimal ADB & Fastboot" installation directory and start it's shell:
If you want to flash back the stock image. Simply run:
Code:
Code:
fastboot flashall
You can also replace all partitions if required.
itsjustbilly said:
Download the Factory State Images. Which are all flashable with fastboot: https://goo.gl/JTCwKj
Click to expand...
Click to collapse
Thanks, I was on P2a42_S038...TMO (T-Mobile, checking OTA update = you are using latest software) flashed this P2a42_S048_ and got OTA info to download latest ROM P2a42_S062_170117_ROW (103MB) :good:
veimus said:
Thanks, I was on P2a42_S038...TMO (T-Mobile, checking OTA update = you are using latest software) flashed this P2a42_S048_ and got OTA info to download latest ROM P2a42_S062_170117_ROW (103MB) :good:
Click to expand...
Click to collapse
Witaj. Mozesz napisać jak wgrałeś czysty soft do Lenovo p2. Tez mam rom z t.mobile a nigdzie nie ma poradnika jak wgrać czysty soft.Pozdrawiam
itsjustbilly said:
Taken from post 4 of the TWRP page on lenovo P2 forum
Factory Images & Systemless Mode
Q: I messed up help me?!
So you screwed up and didn't follow Rule Number One in the IT-Handbook?
Which is: Always create a backup before working on a system?
Download the Factory State Images. Which are all flashable with fastboot: https://goo.gl/JTCwKj
Place the files you want replaced into the "Minimal ADB & Fastboot" installation directory and start it's shell:
If you want to flash back the stock image. Simply run:
Code:
Code:
fastboot flashall
You can also replace all partitions if required.
Click to expand...
Click to collapse
Is there an alternative download link? What is Mega? I want to avoid these third party download utility if I can...
I put the following into a BAT file and placed it into ADB / Fastboot directory:
Code:
fastboot flash partition gpt_both0.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash system systemchunk0.img
fastboot flash system systemchunk1.img
fastboot flash system systemchunk2.img
fastboot flash system systemchunk3.img
fastboot flash system systemchunk4.img
fastboot flash system systemchunk5.img
fastboot flash system systemchunk6.img
fastboot flash system systemchunk7.img
fastboot flash system systemchunk8.img
fastboot flash system systemchunk9.img
fastboot flash system systemchunk10.img
fastboot flash system systemchunk11.img
fastboot flash system systemchunk12.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
pause
Extract all the files listed in the BAT file or simply extract the entire archive to ADB / Fastboot and launch the BAT file.
Does this work?? @Undesirable
the above post
Oh yeah, it unbricked me and put me back to stock so I could get OTA updates for Nougat. You need the archive posted earlier in the thread though.
@Undesirable Nice and elegant solution man! Typing all this stuff was so annoying.
For those who need an alternative download source, I offer this magnet link:
Code:
magnet:?xt=urn:btih:ef05ea3af4da8a0cbb137c10621942f3ae16d46f&dn=P2a42_S048_161111_ROW_fastboot.7z
It's slow unless lots of people help to seed it.
Is it possible to flash this firmware 2a42_S048_161111_ROW_fastboot.7z on the P2c72 with firmware build number: V3.5_1652_5.1342.1_ST_p2c72 ???
I bought this phone 4GB Ram/64GB from china, but I want to put the international firmware on it.
Thanks!
itsjustbilly said:
Taken from post 4 of the TWRP page on lenovo P2 forum
Factory Images & Systemless Mode
Q: I messed up help me?!
So you screwed up and didn't follow Rule Number One in the IT-Handbook?
Which is: Always create a backup before working on a system?
Download the Factory State Images. Which are all flashable with fastboot: https://goo.gl/JTCwKj
Place the files you want replaced into the "Minimal ADB & Fastboot" installation directory and start it's shell:
If you want to flash back the stock image. Simply run:
Code:
Code:
fastboot flashall
You can also replace all partitions if required.
Click to expand...
Click to collapse
how can I replace my data partition? It's not getting formatted due to an encryption error
If fastboot erase userdata doesn't work, then use TWRP to change user data file system to EXT4 then change it back to F2FS again.
Need help...
I flashed back the stock ROM (due to encryption error in custom 7.0 ROM) using fastboot commands, but my SIGNAL WON'T WORK after I started d phone . I've tried reflashing the stock firmware (and also custom ROMs) but my phone won't detect the signal. "About phone" settings show unknown baseband and IMEI... how to get it back
---------- Post added at 08:58 AM ---------- Previous post was at 08:06 AM ----------
I've flashed 'ROW' variant of stock ROM. Is there a different version for Indian variant?
Good news, motorola anounced the July update for the Motorola One Vision in his blog.
https://support.motorola.com/rola/e...family/motorola-one-vision/documents/MS141417
This update includes the july 1 security update
I don't know the delay but today in August 1 the update is available
I got my device in May and already recieved the June update, so it's not the first for me.
But I believe one vision was released later (June) for some regions.
luisjoseb said:
Good news, motorola publishied the first update for the Motorola One Vision in his blog.
https://support.motorola.com/rola/e...family/motorola-one-vision/documents/MS141417
This update includes the july 1 security update
I will update the post when this come to the device!!!
Click to expand...
Click to collapse
Do you know if this update solve the bootloop caused by enable fingerprint along with developer option ?
AndresOrue said:
Do you know if this update solve the bootloop caused by enable fingerprint along with developer option ?
Click to expand...
Click to collapse
Awaiting the update. But I don't think what you have described is the actual issue. I have fingerprint and developer options enabled and the device works just fine.
From what I have read, the issue is fingerprint + changing the default USB configuration. Isn't it?
baunthiyal said:
Awaiting the update. But I don't think what you have described is the actual issue. I have fingerprint and developer options enabled and the device works just fine.
From what I have read, the issue is fingerprint + changing the default USB configuration. Isn't it?
Click to expand...
Click to collapse
I changed that setting the first time and the phone enter in a bootloop and because I had to reset everything, I didn't try again . In this moment, I have developer option enable and the fingerprint disable.
AndresOrue said:
I changed that setting the first time and the phone enter in a bootloop and because i had to reset everything, I didn't try again . In this moment i have developer option enable and the fingerprint disable.
Click to expand...
Click to collapse
Here's my journey with Vision as of now -
1. Got this phone last week
2. Added fingerprints
3. Updated to PSA29.137-17
4. Enabled developer options
5. Changed all animation rates in developer options to 0.5
I'm not sure you should try steps 1-4. But personally, I didn't have the issue you have described.
baunthiyal said:
Here's my journey with Vision as of now -
1. Got this phone last week
2. Added fingerprints
3. Updated to PSA29.137-17
4. Enabled developer options
5. Changed all animation rates in developer options to 0.5
I'm not sure you should try steps 1-4. But personally, I didn't have the issue you have described.
Click to expand...
Click to collapse
Thanks mate. I enabled fingerprint and developer option and it works. Seems that the problem was what You said, enable fingerprint and changing the default USB configuration.
i just installed this update and after i checked the app for new android update it told me:
integrity system corrupted
You will not be able to get any future updates.
Go to the store and official rom will be installed
Something like this .. Do you see this aswell?
I have bought my one vision the day it became available in my country, June 3rd, I have April's security patch and nothing to update, is there any other security patch available?
ᕙ(⇀‸↼)ᕗ said:
i just installed this update and after i checked the app for new android update it told me:
integrity system corrupted
You will not be able to get any future updates.
Go to the store and official rom will be installed
Something like this .. Do you see this aswell?
Click to expand...
Click to collapse
This is normal with bootloader unlocked.
View attachment 4793287
xt1970-3 touch not working
i got a xt1970-3 from customer and touch is not working, i tried to flash with fastboot " XT1970-3_KANE_RETEU_9.0_PSA29.137-17_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml" the same version in phone, i flashed logo.bin, boot.img, system.img_sparsechunk.0, system.img_sparsechunk.1, system.img_sparsechunk.2, system.img_sparsechunk.2, system.img_sparsechunk.3, system.img_sparsechunk.4, system.img_sparsechunk.5, system.img_sparsechunk.6, system.img_sparsechunk.7, system.img_sparsechunk.8, system.img_sparsechunk.9, system.img_sparsechunk.10, system_other.img_sparsechunk.0, system_other.img_sparsechunk.1, system_other.img_sparsechunk.2,
and now phone in bootloop mode, please i want to known how to flash this again
rizni said:
i got a xt1970-3 from customer and touch is not working, i tried to flash with fastboot " XT1970-3_KANE_RETEU_9.0_PSA29.137-17_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml" the same version in phone, i flashed logo.bin, boot.img, system.img_sparsechunk.0, system.img_sparsechunk.1, system.img_sparsechunk.2, system.img_sparsechunk.2, system.img_sparsechunk.3, system.img_sparsechunk.4, system.img_sparsechunk.5, system.img_sparsechunk.6, system.img_sparsechunk.7, system.img_sparsechunk.8, system.img_sparsechunk.9, system.img_sparsechunk.10, system_other.img_sparsechunk.0, system_other.img_sparsechunk.1, system_other.img_sparsechunk.2,
and now phone in bootloop mode, please i want to known how to flash this again
Click to expand...
Click to collapse
This is how I flash full firmware without wiping userdata.
Code:
fastboot flash pit diskmap.pit
fastboot flash fwbl1 fwbl1.nbl1.bin
fastboot flash ldfw_a ldfw.bin
fastboot flash ldfw_b ldfw.bin
fastboot flash keystorage_a keystorage.bin
fastboot flash keystorage_b keystorage.bin
fastboot flash bootloader_a bootloader.bin
fastboot flash bootloader_b bootloader.bin
fastboot flash modem_a modem.bin
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash logo_a logo.bin
fastboot flash dtbo_a dtbo.img
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.10
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash system_b system_other.img_sparsechunk.1
fastboot flash system_b system_other.img_sparsechunk.2
fastboot fastboot flash vendor_a vendor.img
If you want to wipe userdata you could just add "fastboot erase userdata" at the end.
If that won't work it's probably broken digitizer or something.
thank you for quick guide, the phone is on now but the touch not working, it must be something to do with hardware
thank you
luisjoseb said:
Good news, motorola anounced the July update for the Motorola One Vision in his blog.
https://support.motorola.com/rola/e...family/motorola-one-vision/documents/MS141417
This update includes the july 1 security update
I don't know the delay but today in August 1 the update is available
Click to expand...
Click to collapse
I got the update yesterday
wtf
tys0n said:
This is normal with bootloader unlocked.
View attachment 4793287
Click to expand...
Click to collapse
I just noticed that new update is out.. so I tried click to update and woala it works.
OEM unlocked..
So with bootloader unlocked you are still able to get updates..
ᕙ(⇀‸↼)ᕗ said:
I just noticed that new update is out.. so I tried click to update and woala it works.
OEM unlocked..
So with bootloader unlocked you are still able to get updates..
Click to expand...
Click to collapse
There is no update for me
And Google Duo not work
ed.shevsky said:
There is no update for me
And Google Duo not work
Click to expand...
Click to collapse
i dont use duo, but i tried to root it and failed.. so i flashed stock boot.img
then tried to update
Maybe that flashed boot.img helped it or IDK.
you can try it- find your firmware
download it - extract it- find boot.img- place it in your home folder
use fastboot (instal adb tools and drivers ) with command (fastboot flash boot boot.img)
your phone must be in download mode - (power off, then press power and volume down button)
Is it avaible for your country?
ᕙ(⇀‸↼)ᕗ said:
i dont use duo, but i tried to root it and failed.. so i flashed stock boot.img
then tried to update
Maybe that flashed boot.img helped it or IDK.
you can try it- find your firmware
download it - extract it- find boot.img- place it in your home folder
use fastboot (instal adb tools and drivers ) with command (fastboot flash boot boot.img)
your phone must be in download mode - (power off, then press power and volume down button)
Is it avaible for your country?
Click to expand...
Click to collapse
Sorry, my fault. My phone is locked, so I don't need to flash boot.img
May be you know a method to force OTA update?
And about Google Duo. The program stop working after Play Market version updated. Once I fix it by factory reset. But I don't want do it every time
ᕙ(⇀‸↼)ᕗ said:
I just noticed that new update is out.. so I tried click to update and woala it works.
OEM unlocked..
So with bootloader unlocked you are still able to get updates..
Click to expand...
Click to collapse
Ok nice. Still didn't work for me but I'm flashing it with fastboot now instead.
ᕙ(⇀‸↼)ᕗ said:
i dont use duo, but i tried to root it and failed.. so i flashed stock boot.img
then tried to update
Maybe that flashed boot.img helped it or IDK.
you can try it- find your firmware
download it - extract it- find boot.img- place it in your home folder
use fastboot (instal adb tools and drivers ) with command (fastboot flash boot boot.img)
your phone must be in download mode - (power off, then press power and volume down button)
Is it avaible for your country?
Click to expand...
Click to collapse
Did you also get error about "too many links" when trying to flash magisk patched boot?
Disclaimer :
Code:
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Your warranty will be void if you tamper with any part of your device / software.
Download :
OnePlus7TOxygen_14.I.05_OTA_fastboot
Code:
ro.vendor.build.date=Wed Sep 25 21:54:29 CST 2019
ro.vendor.build.date.utc=1569419669
ro.vendor.build.fingerprint=OnePlus/OnePlus7T/OnePlus7T:10/QKQ1.190716.003/1909250940:user/release-keys
ro.vendor.build.id=QKQ1.190716.003
ro.vendor.build.tags=release-keys
ro.vendor.build.type=user
ro.vendor.build.version.incremental=1909250940
ro.vendor.build.version.release=10
ro.vendor.build.version.sdk=29
ro.product.vendor.brand=OnePlus
ro.product.vendor.device=OnePlus7T
ro.product.vendor.manufacturer=OnePlus
ro.product.vendor.name=OnePlus7T
Fastboot Commands :
Code:
fastboot flash aop_a aop.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash logo_a logo.img
fastboot flash logo_b logo.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash storsec_a storsec.img
fastboot flash storsec_b storsec.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
Credits :
jamflux
Regards,
acervenky
reserved
Thanks very much for this.
.
Is there any solution for root ?
I am not able to root using magisk patched boot.img
.
Magisk beta stucking at bootloader warning info at boot.
Magisk canary giving Qualcomm crash dump error on boot.
RohanAJoshi said:
Thanks very much for this.
.
Is there any solution for root ?
I am not able to root using magisk patched boot.img
.
Magisk beta stucking at bootloader warning info at boot.
Magisk canary giving Qualcomm crash dump error on boot.
Click to expand...
Click to collapse
Download the attachment, and flash it using this command :
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
This should help you with the image patched using beta.
Regards,
acervenky
acervenky said:
Download the attachment, and flash it using this command :
This should help you with the image patched using beta.
Regards,
acervenky
Click to expand...
Click to collapse
OK, I will try this and report you back soon.
acervenky said:
Download the attachment, and flash it using this command :
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
This should help you with the image patched using beta.
Regards,
acervenky
Click to expand...
Click to collapse
tried this, not working.
same as before, with magisk beta patched, phone stuck at bootloader unlock warning.
.
steps i did
flashed vbmeta as you said.
flashed patched boot.
reboot.
.
my doubt is :
in your fist post, for plashing vbmeta, you used _a & _b
but in this command, its only vbemeta, not a or b
RohanAJoshi said:
tried this, not working.
same as before, with magisk beta patched, phone stuck at bootloader unlock warning.
.
steps i did
flashed vbmeta as you said.
flashed patched boot.
reboot.
.
my doubt is :
in your fist post, for plashing vbmeta, you used _a & _b
but in this command, its only vbemeta, not a or b
Click to expand...
Click to collapse
Managed to compile a kernel with avb flag disabled and vbmeta removed, download it from this link, please note that they're unpatched and there may be bugs if oneplus messed up something in the source code.
Please patch it with beta and canary, report if it works!
Regards,
acervenky
acervenky said:
Managed to compile a kernel with avb flag disabled and vbmeta removed, download it from this link, please note that they're unpatched and there may be bugs if oneplus messed up something in the source code.
Please patch it with beta and canary, report if it works!
Regards,
acervenky
Click to expand...
Click to collapse
which file should i dowload ?
stock or mod ?
RohanAJoshi said:
which file should i dowload ?
stock or mod ?
Click to expand...
Click to collapse
Mod, I've uploaded the stock incase you face any problems and need to revert!
Regards,
acervenky
acervenky said:
Mod, I've uploaded the stock incase you face any problems and need to revert!
Regards,
acervenky
Click to expand...
Click to collapse
that mod.img is going through bootloader warning screen, its boot looping further on boot animation.
did not tried patched magisk of mod file.
I thought 1st try plain if it booting or not, if not booting clean file, magisk mod wont boot.
RohanAJoshi said:
that mod.img is going through bootloader warning screen, its boot looping further on boot animation.
did not tried patched magisk of mod file.
I thought 1st try plain if it booting or not, if not booting clean file, magisk mod wont boot.
Click to expand...
Click to collapse
Same issue here, the mod.img file bootloops after warning of bootloader. Please help! The stock image brings me back to the qualcomm crashdump mode.
Another issue, while flashing the fastboot images initially, for system and vendor files, the following was displayed.
“Invalid sparse file format at header magi
sending sparse system_a (775469 KB)...
OKAY [ 17.955s]
writing ‘system_a’...
FAILED (remote: Partition not found)
finished. total time: 17.971s”
The same displays for system_b, vendor_a and vendor_b. I’ve tried SYSTEM_a, System_a, System_A, SYSTEM_A but to no avail. Do you think this might be the cause of the Qualcomm crash dump mode?
How2Kritin said:
Same issue here, the mod.img file bootloops after warning of bootloader. Please help! The stock image brings me back to the qualcomm crashdump mode.
Another issue, while flashing the fastboot images initially, for system and vendor files, the following was displayed.
“Invalid sparse file format at header magi
sending sparse system_a (775469 KB)...
OKAY [ 17.955s]
writing ‘system_a’...
FAILED (remote: Partition not found)
finished. total time: 17.971s”
The same displays for system_b, vendor_a and vendor_b. I’ve tried SYSTEM_a, System_a, System_A, SYSTEM_A but to no avail. Do you think this might be the cause of the Qualcomm crash dump mode?
Click to expand...
Click to collapse
It's not possible to flash it properly
Read the following reply from @mauronofrio
"actually is not possible, the oneplus 7t is using the new /super partition and on op7t is not possible to flash a full stock rom from fastboot, but you can flash all partitions except system, vendor, product (The 3 partitions that contains the rom), he should boot in twrp to try to restore his device, maybe i can help a bit, but it's something really new and i think the oneplus 7t is the first one that is supporting this"
cultofluna said:
It's not possible to flash it properly
Read the following reply from @mauronofrio
"actually is not possible, the oneplus 7t is using the new /super partition and on op7t is not possible to flash a full stock rom from fastboot, but you can flash all partitions except system, vendor, product (The 3 partitions that contains the rom), he should boot in twrp to try to restore his device, maybe i can help a bit, but it's something really new and i think the oneplus 7t is the first one that is supporting this"
Click to expand...
Click to collapse
Interesting! So the backup and restore vendor, system won't work via twrp?
Anyone tried manually flashing Magisk via twrp?
Regards,
acervenky
acervenky said:
Interesting! So the backup and restore vendor, system won't work via twrp?
Anyone tried manually flashing Magisk via twrp?
Regards,
acervenky
Click to expand...
Click to collapse
I did, initially but it said that the /system, /vendor and /product partitions couldn’t be mounted. When I tried to restore I got stuck in the fastboot mode. After that, I’ve used your file and got stuck with the qualcomm crashdump mode.
FIXED
Final update: Mauronofrio has helped me out and fixed everything for me, a huge thanks to him. My device is in perfect condition now. Thanks a lot to everyone who tried to help too!
I wonder, if a T-Mobile 7T is unlocked can we use this method to install the international firmware on it?
Is this for EU Model?
Hot-Proton said:
Is this for EU Model?
Click to expand...
Click to collapse
No, Global!
Regards,
acervenky
Ok that is bad. Wait for EU Version.
for T-Mobile no, I messed up mine, it boots but no wifi and data. I did a remote session with oneplus but they can't fix it, they don't have the firmware for the tmobile version, unless if someone has already patched the MSM, but sadly nothing yet
---------- Post added at 07:50 AM ---------- Previous post was at 07:48 AM ----------
How2Kritin said:
Final update: Mauronofrio has helped me out and fixed everything for me, a huge thanks to him. My device is in perfect condition now. Thanks a lot to everyone who tried to help too!
Click to expand...
Click to collapse
how did you reach out to him, just wanna know if there's a fix for my wifi and data no connections, T-Mobile unlock bootloader, tried flashing the modem from here but no effect and when I tried deleting it, sim card cannot be detected
Our old twrp have been great compared to nothing but it isn't exactly fully working and freezes a lot on splash screen.
Thanks to @Stricted and @deadman96385 we now have a more functional twrp.
Support for A/B slots.
ADB working.
No need to flash full firmware. Just flash the vbmeta_patch.img and boot twrp.
!!BOOTLOADER MUST BE UNLOCKED!!
YOUR DATA WILL BE WIPED!!
Code:
fastboot flash vbmeta vbmeta_patch.img
fastboot boot twrp-3.3.1-test3.img
Now that we booted to TWRP it's time to format data.
Go to wipe -> format data -> type yes.
"Permanent" install of TWRP (optional):
Copy "twrp-3.3.1-test3.img" to your device.
Boot "twrp-3.3.1-test3.img" from fastboot and go to advanced settings.
Use the option to install recovery ramdisk. In the "file manager" you pick the "twrp-3.3.1-test3.img"
This will extract the twrp ramdisk and install it to your boot.img.
When it's done, tap the "fix recovery bootloop" in advanced settings so that it won't reboot to recovery instead of system..
Since this replaces the ramdisk in boot.img you'll have to reflash magisk afterwards if you want root.
This must be done every time you update your boot.img.
-------------------------------------------------------------------------------------------------------------------------------------------------------
# ROOT:
-----------
# First time:
# Method 1: Root, forced encryption disabled. Full access to data from twrp:
Flash Magisk and Disable_Dm-Verity_ForceEncrypt.zip.
# Method 2: Root only. Device still encrypted and won't be able to decrypt / mount data in twrp.
Magisk modules through Magisk manager still works:
Flash only Magisk.
----------------------------------------------------------------------------------------------------
# Fastboot flash update without loosing root or data:
----------------------------------------------------------------------------------------
# Already rooted with encryption disabled:
Extract the firmware zip to your adb/fastboot folder.
You already have the patched vbmeta flashed so just remove the stock vbmeta.img from the folder after extraction to avoid flashing it by mistake.
Flash full firmware without wipe. (Use cmds from below. Save as .bat to make it more simple.)
Boot twrp and then install it, fix recovery bootloop.
Reboot recovery, flash Magisk and Disable_Dm-Verity_ForceEncrypt.zip.
Boot system.
Code:
echo off
echo - UPDATE AND PRESERV ROOT -
fastboot flash pit diskmap.pit
fastboot flash fwbl1 fwbl1.img
fastboot flash ldfw_a ldfw.img
fastboot flash ldfw_b ldfw.img
fastboot flash keystorage_a keystorage.img
fastboot flash keystorage_b keystorage.img
fastboot flash bootloader_a bootloader.img
fastboot flash bootloader_b bootloader.img
fastboot flash modem_a modem.bin
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash logo_a logo.bin
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.10
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash system_b system_other.img_sparsechunk.1
fastboot flash system_b system_other.img_sparsechunk.2
fastboot flash vendor_a vendor.img
fastboot reboot bootloader
pause 10
fastboot boot twrp-3.3.1-test3.img
echo TWRP is booting..
echo - install recovery ramdisk, fix bootloop, flash magisk & dm-verity zip.
echo - alternatively flash only magisk and Disable_Dm-Verity_ForceEncrypt.zip if you want to keep stock recovery.
pause
# Already rooted with device still encrypted:
Flash firmware update, except vbmeta.
Boot twrp and flash Magisk with adb sideload.
(alternative method: boot twrp and flash magisk patched boot.img)
Download TWRP: https://images.stricted.net/test/troika/twrp-3.3.1-test3.img
Download Magisk: https://github.com/topjohnwu/Magisk/releases
Download vbmeta_patch.img & Disable_Dm-Verity_ForceEncrypt.zip attached below.
PLEASE, DON't QUOTE THE WHOLE OP.
Great guide @tys0n and thank you to @Stricted and @deadman96385 for his work !
tys0n said:
Code:
fastboot flash vbmeta vbmeta_patch.img
fastboot boot twrp-3.3.1-test3.img
Click to expand...
Click to collapse
My Vision is already unlocked and rooted by the old TWRP method. Should I just do this step so I can update to the new TWRP, and then I can follow "encryption disabled" steps to update to a new firmware?
I suppose I can't enable encryption anymore without resetting data.
daekdroom said:
My Vision is already unlocked and rooted by the old TWRP method. Should I just do this step so I can update to the new TWRP, and then I can follow "encryption disabled" steps to update to a new firmware?
I suppose I can't enable encryption anymore without resetting data.
Click to expand...
Click to collapse
You're right. You can't switch between encrypted / non encrypted without a reset.
This update method have been working for me with the old twrp as well, but this new build is much better and more stable that I see no reason not to switch to the new one.
Actually, I think it may be better to first fastboot flash the new firmware (except vbmeta) so that you have a "clean" boot.img to start with if you're planning to use the install recovery ramdisk. At least if you have the old one installed already.
That's how I switched and I've had no problems.
Worked to my, Thnx
Good afternoon,
I'm trying to "patch" the TWRP as you indicate at the beginning of the first post.
When you say:
"For permanent install, use the" flash recovery ramdisk "option in twrp advanced settings"
What file do I have to flash?
Regards
gonzo1963 said:
Good afternoon,
I'm trying to "patch" the TWRP as you indicate at the beginning of the first post.
When you say:
"For permanent install, use the" flash recovery ramdisk "option in twrp advanced settings"
What file do I have to flash?
Regards
Click to expand...
Click to collapse
Sorry, I could have been more clear about this step in the description.
Copy "twrp-3.3.1-test3.img" to your device.
Boot "twrp-3.3.1-test3.img" from fastboot, go to advanced settings.
There's an option to install recovery ramdisk. In the "file manager" you pick the "twrp-3.3.1-test3.img"
This will extract the twrp ramdisk and install it to your boot.img.
When it's done, tap the "fix recovery bootloop" in advanced settings.
Since this replaces the ramdisk in boot.img you'll have to reflash magisk afterwards if you want root.
tys0n said:
Sorry, I could have been more clear about this step in the description.
Copy "twrp-3.3.1-test3.img" to your device.
Boot "twrp-3.3.1-test3.img" from fastboot, go to advanced settings.
There's an option to install recovery ramdisk. In the "file manager" you pick the "twrp-3.3.1-test3.img"
This will extract the twrp ramdisk and install it to your boot.img.
When it's done, tap the "fix recovery bootloop" in advanced settings.
Since this replaces the ramdisk in boot.img you'll have to reflash magisk afterwards if you want root.
Click to expand...
Click to collapse
Good evening,
One last question:
Currently I have permanently installed the TWRP.
Is it also necessary to do these last steps that you have added?
Regards
Enviado desde mi unknown mediante Tapatalk
gonzo1963 said:
Good evening,
One last question:
Currently I have permanently installed the TWRP.
Is it also necessary to do these last steps that you have added?
Regards
Enviado desde mi unknown mediante Tapatalk
Click to expand...
Click to collapse
Good afternoon,
Any answer?
Regards
Enviado desde mi unknown mediante Tapatalk
Bootloop
Dude, my phone was encrypted and unrooted. I flashed vbmeta then booted into twrp. Then I flashed twrp using the ramdisk method, then I clicked to patch the recovery loop, then I flashed Magisk then I flashed the Disable DM Verity. Now I'm stuck in a recovery loop. The phone turns on, then android one screen, then reboots then goes to twrp...
What did I do wrong / miss?
"Then I flashed twrp using the ramdisk method, then I clicked to patch the recovery loop."
Agter this restart the phone in recovery mode and then continue as explained.
Sorry in bad english
First of all, @tys0n thank you very much for your work. I got this phone for work, but since an unrooted Android device is almost useless to me, this is very much appreciated. Just a few annotations from my side, maybe they help someone.
1. Permanent TWRP install didn't work for me. TWRP was installed sucessfully but just like the dude above me, it would not boot to system, even after appying the bootloop fix. I had to reflash to fix this, so better be careful here!
2. I didnt want to lose encryption, so i chose method 2 for rooting. This works fine, but still I had to wipe data in the first place. Otherwise it would again not boot to system, but at least this time it told me that wiping would possibly fix this. However, after wiping encryption IS active. Maybe I did something wrong here but I don't know... Chosing method 1 seems to be the more straightforward option here.
3. Despite these issues, flashing updates seems to work just fine as described described in the OP, preserving data and root. I have only tried this once, from QSA30.62-24-6 to QSA30.62-33, which is currently the most recent patchlevel for RETEU devices. I even got the "successfully updated" notification afterwards, as if it was an OTA update
Preceptor said:
Dude, my phone was encrypted and unrooted. I flashed vbmeta then booted into twrp. Then I flashed twrp using the ramdisk method, then I clicked to patch the recovery loop, then I flashed Magisk then I flashed the Disable DM Verity. Now I'm stuck in a recovery loop. The phone turns on, then android one screen, then reboots then goes to twrp...
What did I do wrong / miss?
Click to expand...
Click to collapse
same here !
sennator said:
First of all, @tys0n thank you very much for your work. I got this phone for work, but since an unrooted Android device is almost useless to me, this is very much appreciated. Just a few annotations from my side, maybe they help someone.
1. Permanent TWRP install didn't work for me. TWRP was installed sucessfully but just like the dude above me, it would not boot to system, even after appying the bootloop fix. I had to reflash to fix this, so better be careful here!
2. I didnt want to lose encryption, so i chose method 2 for rooting. This works fine, but still I had to wipe data in the first place. Otherwise it would again not boot to system, but at least this time it told me that wiping would possibly fix this. However, after wiping encryption IS active. Maybe I did something wrong here but I don't know... Chosing method 1 seems to be the more straightforward option here.
3. Despite these issues, flashing updates seems to work just fine as described described in the OP, preserving data and root. I have only tried this once, from QSA30.62-24-6 to QSA30.62-33, which is currently the most recent patchlevel for RETEU devices. I even got the "successfully updated" notification afterwards, as if it was an OTA update
Click to expand...
Click to collapse
Hi. Yes, you're right. After flashing the patched vbmeta we need to format data. I've made it more clear in OP now.
Thanks for pointing it out.
kArLiN_dRaKE_MX said:
same here !
Click to expand...
Click to collapse
Format data in twrp
It doesn't work for me (XT1970-1).
I did the process according to information method 2.
the system boots normally.
however magisk is not 'GREEN' like two pieces of information.
How is it going without ROOT, how do I put ROOT?
have another process after this information?
Thank you.
It worked.
I performed the process again.
and everything went well.
Thanks to everyone involved. :good:
gambiarraweb1 said:
It doesn't work for me (XT1970-1).
I did the process according to information method 2.
the system boots normally.
however magisk is not 'GREEN' like two pieces of information.
How is it going without ROOT, how do I put ROOT?
have another process after this information?
Thank you.
Click to expand...
Click to collapse
Just a quick question, when I have TWRP and root I can't pass the SafetyNet check, right?
Hello all. When I click on Internal storage, there are folders with names like "a16sgyx462" and so on, so I am not able to install TWRP permanently. Can somebody help me with this?
simije97 said:
Hello all. When I click on Internal storage, there are folders with names like "a16sgyx462" and so on, so I am not able to install TWRP permanently. Can somebody help me with this?
Click to expand...
Click to collapse
You probably have Data encrypted. You need to execute Format Data in TWRP.
Has anyone used the official TWRP version? I've been thinking of transitioning from the older, unofficial, TWRP to that, but I haven't found any comment about it at all.
I was rooted with Magisk 25.2 fine. I followed the OTA update intructions (uninstall, update, install to the other partition etc). When Magisk rebooted my phone I got a messae that says
QUALCOM CrashDump Mode
-------------------------------
dm-verity device corrupted
verity_ctr
I can reboot back into my other partition, and I have a version of the OS that's pre-OTA, but I've lost root there. I can switch between partitions and go from the Qualcom CrashDump to my working non-rooted OS.
How do I get from either of these places to a rooted version of the OTA update?
I'd suggest waiting for the next OTA and do it again.
However, I don't understand why you did the uninstall, update, install to the other partition etc part. I usually just do the following steps:
Install OTA (do NOT reboot yet)
Install Magisk in the other partition
Reboot
So far it has worked for me for each update.
Ecna said:
I was rooted with Magisk 25.2 fine. I followed the OTA update intructions (uninstall, update, install to the other partition etc). When Magisk rebooted my phone I got a messae that says
QUALCOM CrashDump Mode
-------------------------------
dm-verity device corrupted
verity_ctr
I can reboot back into my other partition, and I have a version of the OS that's pre-OTA, but I've lost root there. I can switch between partitions and go from the Qualcom CrashDump to my working non-rooted OS.
How do I get from either of these places to a rooted version of the OTA update?
Click to expand...
Click to collapse
You may be able to copy your good partitions (a or b, whichever works) to the other one. So they'll both be loaded with working stock firmware. Then take the OTA and drop in a magisk patched boot image after OTA is good
Appreciative said:
You may be able to copy your good partitions (a or b, whichever works) to the other one. So they'll both be loaded with working stock firmware. Then take the OTA and drop in a magisk patched boot image after OTA is good
Click to expand...
Click to collapse
How would I copy my good partition to the broken one?
viktak said:
I'd suggest waiting for the next OTA and do it again.
Click to expand...
Click to collapse
The current OTA is still pending, and I don't have root anymore, so waiting won't get me anywhere.
However, I don't understand why you did the uninstall, update, install to the other partition etc part.
Click to expand...
Click to collapse
I just followed the Magisk instructions here:
https://topjohnwu.github.io/Magisk/ota.html
Ecna said:
How would I copy my good partition to the broken one?
Click to expand...
Click to collapse
While on Slot_A Flash copypartitions.zip??
Sorry for the noob question but how do I do "While on Slot_A Flash copypartitions.zip" I cant find the copypartitions.zip please help thanks
forum.xda-developers.com
[SLOT A/B devices] Universal A/B-cloner
I DO NOT TAKE RESPONSIBILITY FOR YOUR DEVICE BREAKING THIS /WILL/ COPY YOUR BOOTLOADER FROM ONE SLOT TO ANOTHER IF YOU DO THAT WITH A BOOTLOADER THAT IS OLDER THAN THE SLOT YOURE OVERWRITING YOUR DEVICE MIGHT BRICK Ok, thats over with INFO...
forum.xda-developers.com
Something like these, or manually. Be sure to figure out which partition (a or b) is currently good and working so you don't copy the wrong way. If you do copy the wrong direction, you may have to msm
Appreciative said:
While on Slot_A Flash copypartitions.zip??
Sorry for the noob question but how do I do "While on Slot_A Flash copypartitions.zip" I cant find the copypartitions.zip please help thanks
forum.xda-developers.com
[SLOT A/B devices] Universal A/B-cloner
I DO NOT TAKE RESPONSIBILITY FOR YOUR DEVICE BREAKING THIS /WILL/ COPY YOUR BOOTLOADER FROM ONE SLOT TO ANOTHER IF YOU DO THAT WITH A BOOTLOADER THAT IS OLDER THAN THE SLOT YOURE OVERWRITING YOUR DEVICE MIGHT BRICK Ok, thats over with INFO...
forum.xda-developers.com
Something like these, or manually. Be sure to figure out which partition (a or b) is currently good and working so you don't copy the wrong way. If you do copy the wrong direction, you may have to msm
Click to expand...
Click to collapse
Thank you, I'll dig into these links!
I got similar problem, solved by disabling dm-verify manually. You can try extract vbmeta.img from rom package using payload_dumper, then use fastboot to disable dm-verify.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I'm having this same problem, but to fix it I need to switch back to the "good" slot and boot my phone normally to fix it. However after booting my phone into fastboot, I'm unable to run the appropriate command:
Code:
fastboot --set-active=a
fastboot: unknown option -- set-active=a
Do I have the wrong version of fastboot installed on my PC? How can the rest of fastboot work but not this specific command?
sumfahg said:
I'm having this same problem, but to fix it I need to switch back to the "good" slot and boot my phone normally to fix it. However after booting my phone into fastboot, I'm unable to run the appropriate command:
Code:
fastboot --set-active=a
fastboot: unknown option -- set-active=a
Do I have the wrong version of fastboot installed on my PC? How can the rest of fastboot work but not this specific command?
Click to expand...
Click to collapse
Make sure you have the latest full platform tools and not the minimum platform tools, or if you are on a windows PC try the fastboot enhanced version
TheGhost1951 said:
Make sure you have the latest full platform tools and not the minimum platform tools, or if you are on a windows PC try the fastboot enhanced version
Click to expand...
Click to collapse
I am on Windows, where can I download fastboot enhanced?
sumfahg said:
I am on Windows, where can I download fastboot enhanced?
Click to expand...
Click to collapse
There is an xda threads on it. Just search xda forums for fastboot enhanced.
sumfahg said:
I am on Windows, where can I download fastboot enhanced?
Click to expand...
Click to collapse
You could try:
fastboot set_active other
Or
fastboot set_active a
Or
fastboot -a (this is in the documentation but I have never tried it, nor see it online often)
zjhjack123 said:
I got similar problem, solved by disabling dm-verify manually. You can try extract vbmeta.img from rom package using payload_dumper, then use fastboot to disable dm-verify.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Spent some time trying to do this. fastboot said Rewriting, Sending, writing, Finished. All OKAY. No error messages in there. But when I rebooted into the other partition I got the same dm-verity crash dump.
Ecna said:
Spent some time trying to do this. fastboot said Rewriting, Sending, writing, Finished. All OKAY. No error messages in there. But when I rebooted into the other partition I got the same dm-verity crash dump.
Click to expand...
Click to collapse
I dug a bit further and tried these as well:
Code:
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system_a vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor_a vbmeta_vendor.img
Whenever I try to boot to the a partition, I just loop back into fastboot mode. The b partition still works though.
Appreciative said:
You could try:
fastboot set_active other
Or
fastboot set_active a
Or
fastboot -a (this is in the documentation but I have never tried it, nor see it online often)
Click to expand...
Click to collapse
Fastboot --set-active=a or b which ever you need in bootloader mode
Ecna said:
I dug a bit further and tried these as well:
Code:
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system_a vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor_a vbmeta_vendor.img
Whenever I try to boot to the a partition, I just loop back into fastboot mode. The b partition still works though.
Click to expand...
Click to collapse
Maybe you could try set-active a (if a slot is the bad rom) first, reboot into fastboot again and then use fastboot to flash vbmeta with disable verity parameter.
Or you could try to boot into good rom, and flash full update package using local update instead of ota, then see if it can boot into updated rom.
zjhjack123 said:
Maybe you could try set-active a (if a slot is the bad rom) first, reboot into fastboot again and then use fastboot to flash vbmeta with disable verity parameter.
Or you could try to boot into good rom, and flash full update package using local update instead of ota, then see if it can boot into updated rom.
Click to expand...
Click to collapse
I did switch the active slot to a, just cause that seemed like a good idea.
How do I only flash the update package to the A slot? I thought it went to both by default?
Ecna said:
I did switch the active slot to a, just cause that seemed like a good idea.
How do I only flash the update package to the A slot? I thought it went to both by default?
Click to expand...
Click to collapse
When you flash tom in the system, it only update the firmware in another slot. So if your current good rom is in slot b, you can just boot into slot b and apply system update via local update, the updated rom will be in slot a.
Ecna said:
I did switch the active slot to a, just cause that seemed like a good idea.
How do I only flash the update package to the A slot? I thought it went to both by default?
Click to expand...
Click to collapse
If you have the images:
fastboot flash system_a system_a.img
fastboot flash system_b system_b.img
it's also possible to pull the whole partitions down with msm tool (press f8, select partitions and readback, files go to c:\) or using dd.
If not, #19 above