Related
Hey guys! Need some help.
I've been trying to flash a Android Pie ROM on my device and I have no success.
The problem is, after flashing the rom and TWRP Zip the device reboots twice then boots back into TWRP.
Then all the files on the device has random letters and numbers (i.e. ckjrdh574o0hmdu749y7nv)
Why can't I flash a Android Pie rom successfully?
I am on the latest Android Pie update. (Flashed on both slots)
Here is my steps:
Flash stock rom on both slots
Boot up in stock rom. (no set up, no password, no pin, nothing totally skipped setup)
Place files on device (Rom and twrp.zip)
Reboot into Bootloader
Boot into latest TWRP using fastboot
Once in Twrp, slide slider to allow modification to system parition
Factory reset/wipe data (and all that)
Flash rom (I tried Carbon Rom 7 and lineage os 16)
Flashed twrp zip
reboot
After the system reboots twice I am back in twrp and all the files and folder have numbers and letters as files names.
Any idea as to why this keeps happening?
How can I fix this?
MichaelDrakeMS said:
Hey guys! Need some help.
I've been trying to flash a Android Pie ROM on my device and I have no success.
The problem is, after flashing the rom and TWRP Zip the device reboots twice then boots back into TWRP.
Then all the files on the device has random letters and numbers (i.e. ckjrdh574o0hmdu749y7nv)
Why can't I flash a Android Pie rom successfully?
I am on the latest Android Pie update. (Flashed on both slots)
Here is my steps:
Flash stock rom on both slots
Boot up in stock rom. (no set up, no password, no pin, nothing totally skipped setup)
Place files on device (Rom and twrp.zip)
Reboot into Bootloader
Boot into latest TWRP using fastboot
Once in Twrp, slide slider to allow modification to system parition
Factory reset/wipe data (and all that)
Flash rom (I tried Carbon Rom 7 and lineage os 16)
Flashed twrp zip
reboot
After the system reboots twice I am back in twrp and all the files and folder have numbers and letters as files names.
Any idea as to why this keeps happening?
How can I fix this?
Click to expand...
Click to collapse
Flash stock
finish setup
before doing anything else
MichaelDrakeMS said:
Hey guys! Need some help.
I've been trying to flash a Android Pie ROM on my device and I have no success.
The problem is, after flashing the rom and TWRP Zip the device reboots twice then boots back into TWRP.
Then all the files on the device has random letters and numbers (i.e. ckjrdh574o0hmdu749y7nv)
Why can't I flash a Android Pie rom successfully?
I am on the latest Android Pie update. (Flashed on both slots)
Here is my steps:
Flash stock rom on both slots
Boot up in stock rom. (no set up, no password, no pin, nothing totally skipped setup)
Place files on device (Rom and twrp.zip)
Reboot into Bootloader
Boot into latest TWRP using fastboot
Once in Twrp, slide slider to allow modification to system parition
Factory reset/wipe data (and all that)
Flash rom (I tried Carbon Rom 7 and lineage os 16)
Flashed twrp zip
reboot
After the system reboots twice I am back in twrp and all the files and folder have numbers and letters as files names.
Any idea as to why this keeps happening?
How can I fix this?
Click to expand...
Click to collapse
Not sure if Carbon / Lineage has special install instructions or not, but you can follow the initial 9x setup in the link in my sig, then follow cust Rom installation process.
parakleet said:
Flash stock
finish setup
before doing anything else
Click to expand...
Click to collapse
Yup I did. I just didn't sign in my account or do the security pin/pixel imprint. I skipped everything untill I was at the home/launcher.
Az Biker said:
Not sure if Carbon / Lineage has special install instructions or not, but you can follow the initial 9x setup in the link in my sig, then follow cust Rom installation process.
Click to expand...
Click to collapse
Nothing to special from the norm. I didn't everything the forums told me to do.
Okay definitely, I'll check that out and try those steps.
Also do you think I have a phone that twrp can't decrypt? I remember a while back doing one of the twrp updates that some phones won't decrypt because it used the older encryption method or something like that and TWRP was only able to decrypt then phones using the new method or something like that.
Oh and another question, do you guys think I should root the stock image with magisk then boot into twrp using fastboot and install the room then the twrp.zip?
My question would be do you have other details you might have overlooked? For example, at the end of flashing, TWRP would usually ask whether you want to install their app. Did you install it or did you skip it?
Also, what was your exact procedure in flashing stock rom to both slots? I have also messed around with custom roms and reverted back to stock using the following:
Return to Stock:
Source of this knowledge is Method 2 of this video.
#flashing bootloader to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash bootloader_a bootloader[...].img
fastboot reboot-bootloader
fastboot flash bootloader_b bootloader[...].img
#flashing radio to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash radio_a radio[...].img
fastboot reboot-bootloader
fastboot flash radio_b radio[...].img
#set active slot to B, flash system image
Code:
fastboot --set-active=b
fastboot reboot-bootloader
fastboot --skip-reboot --skip-secondary update image[...].zip
#set active slot to A, flash system image [different command!!!]
Code:
fastboot --set-active=a
fastboot reboot-bootloader
fastboot --skip-reboot update image[...].zip
Now straight from the bootloader, boot into recovery.
Wipe data/factory reset.
Let it reboot back into android.
Then, I followed the install instructions in the twrp thread to get custom recovery back onto my device. (If you want rooted stock android, flash it from twrp and then install the latest magisk manager apk.)
Now just find another custom rom and follow the install directions from that thread.
amartolos said:
My question would be do you have other details you might have overlooked? For example, at the end of flashing, TWRP would usually ask whether you want to install their app. Did you install it or did you skip it?
Also, what was your exact procedure in flashing stock rom to both slots? I have also messed around with custom roms and reverted back to stock using the following:
Return to Stock:
Source of this knowledge is Method 2 of this video.
#flashing bootloader to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash bootloader_a bootloader[...].img
fastboot reboot-bootloader
fastboot flash bootloader_b bootloader[...].img
#flashing radio to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash radio_a radio[...].img
fastboot reboot-bootloader
fastboot flash radio_b radio[...].img
#set active slot to B, flash system image
Code:
fastboot --set-active=b
fastboot reboot-bootloader
fastboot --skip-reboot --skip-secondary update image[...].zip
#set active slot to A, flash system image [different command!!!]
Code:
fastboot --set-active=a
fastboot reboot-bootloader
fastboot --skip-reboot update image[...].zip
Now straight from the bootloader, boot into recovery.
Wipe data/factory reset.
Let it reboot back into android.
Then, I followed the install instructions in the twrp thread to get custom recovery back onto my device. (If you want rooted stock android, flash it from twrp and then install the latest magisk manager apk.)
Now just find another custom rom and follow the install directions from that thread.
Click to expand...
Click to collapse
Now that's all the steps j took to flash the roms.
I do not install twrp app I skip that.
My first methond to flash stock on both slots is set slot to a then flash stock using the flash all bat file in from the stock images (google directions to flashing images)
Then it would reboot. Then I would set to slot b and flash the stock images the same way using the bat file.
Then I found out that wasn't really the best way to do it so I used deuces (I believe that was the users name) bat file to flash the stock images on both slots the correct way and that's what I've been doing since.
But your steps have a different step then what I do. It seems it does the same as deuces bat file however once it's done I just boot straight into stock rom. I dont boot into stock recovery and factory wipe. But I will definitely try that as well.
Finally fixed it!
I flash both slots and followed everyone's directions.
The problem was I wasn't wiping all the things I needed too.
I read in another roms steps to not only do the factory reset thin in TWRP, but to also manually wipe system, data, dalvik/art cache. Then flashed the room and TWRP.zip.
I did this and BOOM, I booted up into the room! Thanks again for everyone's help!
amartolos said:
My question would be do you have other details you might have overlooked? For example, at the end of flashing, TWRP would usually ask whether you want to install their app. Did you install it or did you skip it?
Also, what was your exact procedure in flashing stock rom to both slots? I have also messed around with custom roms and reverted back to stock using the following:
Return to Stock:
Source of this knowledge is Method 2 of this video.
#flashing bootloader to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash bootloader_a bootloader[...].img
fastboot reboot-bootloader
fastboot flash bootloader_b bootloader[...].img
#flashing radio to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash radio_a radio[...].img
fastboot reboot-bootloader
fastboot flash radio_b radio[...].img
#set active slot to B, flash system image
Code:
fastboot --set-active=b
fastboot reboot-bootloader
fastboot --skip-reboot --skip-secondary update image[...].zip
#set active slot to A, flash system image [different command!!!]
Code:
fastboot --set-active=a
fastboot reboot-bootloader
fastboot --skip-reboot update image[...].zip
Now straight from the bootloader, boot into recovery.
Wipe data/factory reset.
Let it reboot back into android.
Then, I followed the install instructions in the twrp thread to get custom recovery back onto my device. (If you want rooted stock android, flash it from twrp and then install the latest magisk manager apk.)
Now just find another custom rom and follow the install directions from that thread.
Click to expand...
Click to collapse
I stumbled across this post after having several issues trying to get my Pixel 2 XL flashed with a custom ROM (constantly resulting in boot-loops), and the steps worked perfectly.
I've ended up running these steps several times today, but I like keeping all of my stock images in sub-folders by release date. I'm not the greatest Powershell guru, but I've written a script that will search sub-directories in a folder for dates, and select the latest date and automatically flash the radio, bootloader, and image from that directory using your steps.
Code:
clear;
# Execution Policy must be adjusted in order to obtain the current executing directory of the script. This is a one-time command that must be run separately.
# Set-ExecutionPolicy RemoteSigned
# To reverse the command set the execution policy to restricted:
# Set-ExecutionPolicy Restricted
# The root directory which contains date sub-folders in the format yyyy-MM-dd representing an extracted OTA zip.
$startingDirectory = split-path -parent $MyInvocation.MyCommand.Definition;
# Alternatively, hard code a starting directory.
# [System.String]$startingDirectory = 'D:\Flashing\Roms\Taimen\Stock\';
[System.String]$targetFolder = (Get-ChildItem $startingDirectory | Select-Object -Property @{Name='Date';Expression = { Get-Date $_.Name -Format 'yyyy-MM-dd' }}, @{Name='FullName';Expression= {$_.FullName}} | Sort Date -Descending | Select -First 1).FullName;
if (-not $targetFolder) {
throw 'No folders are located in directory ''' + $startingDirectory + ''' with the date format yyyy-MM-dd.';
}
[System.String]$bootloader = Get-ChildItem $targetFolder -Name 'bootloader-*.img';
[System.String]$radio = Get-ChildItem $targetFolder -Name 'radio-*.img';
[System.String]$image = Get-ChildItem $targetFolder -Name 'image-*.zip';
# Validate all files have been successfully located.
[System.Collections.Generic.List[System.String]]$messages = [System.Collections.Generic.List[System.String]]::new();
if (-not $bootloader) {
$messages.Add('The bootloader file was not located.');
}
if (-not $radio) {
$messages.Add('The radio file was not located.');
}
if (-not $image) {
$messages.Add('The image file was not located.');
}
if ($messages.Length -gt 0) {
throw 'Unable to locate files in path ''' + $targetFolder + ''':' + [Environment]::NewLine + [System.String]::Join([Environment]::NewLine, $messages);
}
$bootloader = [System.IO.Path]::Combine($targetFolder, $bootloader);
$bootloader;
$radio = [System.IO.Path]::Combine($targetFolder, $radio);
$radio;
$image = [System.IO.Path]::Combine($targetFolder, $image);
$image;
#adb reboot bootloader;
function Reboot-Bootloader {
fastboot reboot-bootloader;
sleep 5;
}
#flashing bootloader to slot A and slot B
'Flashing bootloader to slot A.'
Reboot-Bootloader;
fastboot flash bootloader_a $bootloader;
'Flashing bootloader to slot B.'
Reboot-Bootloader;
fastboot flash bootloader_b $bootloader;
#flashing radio to slot A and slot B
'Flashing radio to slot A.'
Reboot-Bootloader;
fastboot flash radio_a $radio;
'Flashing radio to slot B.'
Reboot-Bootloader;
fastboot flash radio_b $radio;
#set active slot to B, flash system image
'Flashing system image to slot B.'
fastboot --set-active=b;
Reboot-Bootloader;
fastboot --skip-reboot --skip-secondary update $image;
#set active slot to A, flash system image [different command!!!]
'Flashing system image to slot A.'
fastboot --set-active=a;
Reboot-Bootloader;
fastboot --skip-reboot update $image;
Hi there,
I have a problem i was try to root my phone.
Now i dont have access to ADB but only fastboot works.
If i start my phone it goes on fastboot mode, and if i try "fast boot twrp-3.3.0-0-daisy.img" i get the error "device unable to boot Error - mdtp image is corrupted"
Can some one help me out, if tried to download the image again but without success..
You don't need twrp for root?!
I guess you need to get a fast boot ROM and flash it. Don't relock the bootloader. Don't flash data. Just all the other partitions.
Maybe even just flash that partition. My phone has a and b. Should just need to flash the current one.
a1291762 said:
You don't need twrp for root?!
I guess you need to get a fast boot ROM and flash it. Don't relock the bootloader. Don't flash data. Just all the other partitions.
Maybe even just flash that partition. My phone has a and b. Should just need to flash the current one.
Click to expand...
Click to collapse
Sorry im a little bit noob, but how it works:
flastboot flash a?
fastboot flash mdtp_a mdtp.img
That file is in the images folder after you extract the fastboot ROM.
Hi,
while having 15 years of Linux experience, I've just dropped into the same issue on my first hour of Android exploration. Currently no OS is installed and the phone boots into fastboot. Booting into twrp-3.3.1-dees_troy-daisy.img failes also with "Error - mdtp image is corrupted".
I've flashed mdtp.img from V10.0.12.0.PDLMIXM as described, but still I get the same error when booting into twrp-3.3.1-dees_troy-daisy.img . Is there somewere a documentation, how to proceed in such a case?
a1291762 said:
fastboot flash mdtp_a mdtp.img
That file is in the images folder after you extract the fastboot ROM.
Click to expand...
Click to collapse
mj2o said:
Hi,
while having 15 years of Linux experience, I've just dropped into the same issue on my first hour of Android exploration. Currently no OS is installed and the phone boots into fastboot. Booting into twrp-3.3.1-dees_troy-daisy.img failes also with "Error - mdtp image is corrupted".
I've flashed mdtp.img from V10.0.12.0.PDLMIXM as described, but still I get the same error when booting into twrp-3.3.1-dees_troy-daisy.img . Is there somewere a documentation, how to proceed in such a case?
Click to expand...
Click to collapse
No OS installed is maybe cause the last rom that you flashed was not flashed in the right slot or correctly flashed.
Also the fastboot command mentioned here is to flash mdtp in "a" slot but you have to see first which is your active slot and then install it on it.
SubwayChamp said:
Also the fastboot command mentioned here is to flash mdtp in "a" slot but you have to see first which is your active slot and then install it on it.
Click to expand...
Click to collapse
I've searched more for the reason and once got the response: FAILED (remote: partition table doesn't exist)
So it sounds I have to recreate the partition table. I haven't found any fastboot command to request the current partition status.
mj2o said:
I've searched more for the reason and once got the response: FAILED (remote: partition table doesn't exist)
So it sounds I have to recreate the partition table. I haven't found any fastboot command to request the current partition status.
Click to expand...
Click to collapse
I don´t think that exist a command to diagnose status of partitions but I´m sure that if you try to flash on an inactive slot then won´t work, ever an inactive slot will give you a fail.
Check your active slot by typing
Code:
fastboot getvar current-slot
and then flash it on the active slot using "mdtp_a" or "mdtp_b" but ONLY if the active slot is actually with all the system on it it´s mean that if you deleted all your system and any of both are actually with partitions running (no matter that with errors) then won´t work this way as you expect.
I have the same problem, what you have did to fix? please
Hi,
I've downloaded and flashed the factory image from miui.com. This way I have reset all my efforts and started all over. You find there the full rom and a flashing guide for the Xiaomi Mi A2 Lite.
mj2o said:
Hi,
I've downloaded and flashed the factory image from miui.com. This way I have reset all my efforts and started all over. You find there the full rom and a flashing guide for the Xiaomi Mi A2 Lite.
Click to expand...
Click to collapse
hi
same issue here @mj2o: Can you please provide a link to the site in English; it all in Chinese and I cannot read it
Thanks
mj2o said:
Hi,
I've downloaded and flashed the factory image from miui.com. This way I have reset all my efforts and started all over. You find there the full rom and a flashing guide for the Xiaomi Mi A2 Lite.
Click to expand...
Click to collapse
SubwayChamp said:
I don´t think that exist a command to diagnose status of partitions but I´m sure that if you try to flash on an inactive slot then won´t work, ever an inactive slot will give you a fail.
Check your active slot by typing
Code:
fastboot getvar current-slot
and then flash it on the active slot using "mdtp_a" or "mdtp_b" but ONLY if the active slot is actually with all the system on it it´s mean that if you deleted all your system and any of both are actually with partitions running (no matter that with errors) then won´t work this way as you expect.
Click to expand...
Click to collapse
@mj2o;80151263:
Code:
fastboot getvar current-slot
returns -->
Code:
current-slot: INVALID
finished. total time: 0.008s
and
Code:
fastboot flash aboot aboot.img
returns -->
Code:
target reported max download size of 534773760 bytes
sending 'aboot' (1024 KB)...
OKAY [ 0.055s]
writing 'aboot'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.075s
please advise.
BenG7 said:
@mj2o;80151263:
Code:
fastboot getvar current-slot
returns -->
Code:
current-slot: INVALID
finished. total time: 0.008s
and
Code:
fastboot flash aboot aboot.img
returns -->
Code:
target reported max download size of 534773760 bytes
sending 'aboot' (1024 KB)...
OKAY [ 0.055s]
writing 'aboot'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.075s
please advise.
Click to expand...
Click to collapse
Why do you want to flash the bootloader, what is the issue?
Hi @SubwayChamp
I wanted to flash LO16
Did a wpie data -yes format
Then a wipe system as instructed and now im stuck in fast boot.
Device unable to boot. Error - mdtp is corrupted
BenG7 said:
Hi @SubwayChamp
I wanted to flash LO16
Did a wpie data -yes format
Then a wipe system as instructed and now im stuck in fast boot.
Click to expand...
Click to collapse
If your issue is related with mdtp partition then you should to install again this image through fastboot in both slots in order to can boot device again to recovery; use
Code:
fastboot flash mdtp_a mdtp.img
and
Code:
fastboot flash mdtp_b mdtp.img
(you will get the images from any of the full fastboot roms)
From there try again the steps recommended by OP in that thread to get that your device boots on LOS but this is other question concerning only to that thread
Thanks SubwayChamp,
Will try as advised and keep you updated.
I m going to look for the fastboot rom for my daisy.
SubwayChamp said:
If your issue is related with mdtp partition then you should to install again this image through fastboot in both slots in order to can boot device again to recovery; use
Code:
fastboot flash mdtp_a mdtp.img
and
Code:
fastboot flash mdtp_b mdtp.img
(you will get the images from any of the full fastboot roms)
From there try again the steps recommended by OP in that thread to get that your device boots on LOS but this is other question concerning only to that thread
Click to expand...
Click to collapse
@SubwayChamp
dit it and when I
Code:
fastboot reboot
it boots straight back to fastboot.
What next? Mi a2 Lite stuck at Fastboot - No recovery, no nothing! Help ?
Thanks for your help!
[EDIT]
realised I can
Code:
fastboot boot twrp-daisy-3.3.1-0-offain.img
and I can flash the twrp-installer-daisy-3.3.1-0-offain.zip
but if I want to reboot; it says
Code:
No OS installed! Are you sure you wish to reboot?
so I went on with flashing lineageos 16
but at the end of the flash, I get
Code:
Failed to mount '/system' (permission denied)
please advise
BenG7 said:
If your issue is related with mdtp partition then you should to install again this image through fastboot in both slots in order to can boot device again to recovery; use and
@SubwayChamp
dit it and when I
it boots straight back to fastboot.
What next? Mi a2 Lite stuck at Fastboot - No recovery, no nothing! Help ?
Thanks for your help!
Click to expand...
Click to collapse
Your recovery is missed now cause when you flashed LOS was overwritten and device can't boot to system cause some step failed in the process.
If you flashed successfully mdtp images now follow the steps to boot to recovery and then follow those indicated to install LOS.
SubwayChamp said:
Your recovery is missed now cause when you flashed LOS was overwritten and device can't boot to system cause some step failed in the process.
If you flashed successfully mdtp images now follow the steps to boot to recovery and then follow those indicated to install LOS.
Click to expand...
Click to collapse
Thanks; this is what I did:
from TWRP I rebooted to recovery
it took me straight to fastboot again
so I
Code:
fastboot boot twrp-daisy-3.3.1-0-offain.img
again and mounted system partition then I flashed LOS
and the process went fine this time but when I rebooted to the system
it's back to fastboot again!
BenG7 said:
Thanks; this is what I did:
from TWRP I rebooted to recovery
it took me straight to fastboot again
so I
again and mounted system partition then I flashed LOS
and the process went fine this time but when I rebooted to the system
it's back to fastboot again!
Click to expand...
Click to collapse
This is exactly what I tried to tell you: your issue concerning to this thread was solved.
Now you have an issue regarding how to flash and boot to system attempting to install LOS. TWRP is perfectly capable to mount/remount or unmount partitions if needed, no need an action from the user, this is not the reason why you are not booting but the method and steps is discussed more properly in the same thread.
From here you can take one of hese three routes:
- To insist with trying to flash LOS.
- Flash other rom or a previous known working rom.
- Return completely to stock by flashing a full global rom.
Just I could recommend that for the future when you flash a stock rom take a backup of the most important partitions (without userdata) this could avoid that you need to use EDL anymore.
Hello everyone,
I need help to start on flashing g7 play etc. In the old days I flashed phones like galaxy s3, s4, s5 and Note 4, but I'm not an expert in all of this.
Then I changed to iPhone 6s and now I want to come back to Android.
My goal:
de-googled moto g7 play
Android 9/10 -> would prefer 10
if possible -> root
My Device:
moto g7 play - XT1952-1
(bootloader unlocked)
---
Build number:
PPYs29.105-134-7
---
If have read most of the Threads for the g7 play, but at the moment I'm a little scared to brick it.
I have some questions:
1. I copied together for myself a Instruction (at the end of post). Could you tell me if this is OK like this, or do I have to do additional things before start?
2. In my copied instruction, at the point of flashing the GSI (Instruction ROM: -> Step 1)
What does "Dirty flashing your g7 play" mean? Do I have something additional to do, before following the instruction, or is dirty flashing the following instruction of the post?
3. Modded phh -> I have no information about this, could you explain, or give me link?
4. Overlay -> I have no information about this, could you explain, or give me link?
Thanks for your help
---
INSTRUCTION: (it is a quick&dirty instruction)
ROM:
lineage-17.1-20200309-UNOFFICIAL-treble_a64_bvN.img.xz
DTBO:
dtbo.img
(https://drive.google.com/file/d/1pV6-LbNoMG0J8vcyAWN0QWYGx67vxBgT/view?usp=sharing)
---
---
Instruction ROM:
step 1
Dirty flashing your g7 play -> what does that mean, what to do???
step 2
extract the gsi
step 3
put phone in fastboot mode and enter the commands
$ fastboot -w
$ fastboot flash dtbo dtbo.img
$ fastboot flash system [this is where you put your android 10 img]
$ fastboot boot twrp.img
(https://forum.xda-developers.com/g7-play/development/gsi-images-g7-play-t3980807
#1)
------------------------
TWRP:
twrp.img
---
Instruction TWRP:
step 1
Fastboot boot twrp.img
step 2
Copy twrp to your external sdcard, or use adb push twrp.img /tmp/twrp.img
step 3
Go to Advanced > install recovery ramdisk then navigate to tmp or your external sdcard and select the twrp.img you copied
step 4
Use wipe > format > type "yes" to continue then use reboot > recovery from twrp's menus
step 5
Once twrp starts up again, wipe data & system, make sure system is mounted, then flash a GSI. Flash the universal disabler afterwards.
If you get a failed to unmount error, manually mount all partitions and reflash whatever it errored on
step 6
Optional: Flash my modded phh for root. (Install the apk after.) Never use Magisk! It will fail to root, cause a bootloop, or break twrp
FIX navbar on a GSI:
$ adb root
$ adb shell
$ setprop persist.sys.phh.mainkeys 0
$ reboot
(https://forum.xda-developers.com/g7...ery-dirty-ported-twrp-g7-play-t3947205/page41
#403)
------------------------
Modded phh: -> LOS16 & 17
modded-phh-superuser.zip
phh-su.apk
(https://forum.xda-developers.com/showpost.php?p=81503713&postcount=240)
------------------------
Overlay: -> what does that mean???
treble-overlay-moto-g7play.apk.zip
(https://forum.xda-developers.com/g7...ery-dirty-ported-twrp-g7-play-t3947205/page41
#404)
------------------------
@ggg777
First make sure you install the stock OS to both slots, including the bootloader. I forgot to flash bootloader_b, and got stuck in EDL last week. You don't want that to happen and it's not easy to get out of. If you do this first, you will not have to worry about getting bricked.
Use my instructions found here for twrp. Inside the instructions you'll also find a link to my modded phh. Flashing a GSI can be done with twrp or fastboot. You also don't need the dtbo.img anymore since it's embedded inside of twrp. The trickiest part really, is just getting twrp installed. If you're using twrp to install a GSI, wipe system, data, dalvik, then flash the image to system. (You'll get a location prompt.) After installing a GSI, copy the overlay to /vendor/overlay, and set permissions on it to 0644, then reboot. Flash modded phh for root if you're using LOS 16 or 17. I think it's already included in Phh's AOSP builds.
There's also a trick to dual boot your OS. I keep one slot with stock installed, that's debloated and rooted with magisk. The other slot I use for flashing GSIs. Twrp can't restore encrypted data for stock, but you can format /data using "yes" then switch slots and use "reboot recovery" to boot up stock with magisk. To swap back to the GSI, fastboot boot twrp, format data, switch slots from the reboot menu, reboot to recovery. If twrp starts, you changed slots successfully. Then just restore data for lineage and bootup.
Oh by the way, "dirty flashing" is just flashing an OS update without wiping data first. I don't recommend it though. Sometimes bugs from older builds will get carried over. You don't need to do that to install LOS 17 or Android 10. It might've been true at one time, but it isn't now. You can just do your wipes and flash the latest build.
Thanks for your Help
How can I check if both partitions are with stock and bootloader?
Is there a trick to copy a working partition to the oter?
I would flash like it is written in this: [Guide][Channel][Stock]Moto g7 play Factory Firmware Images
(https://forum.xda-developers.com/g7-play/how-to/channel-moto-g7-factory-firmware-images-t3996303)
Would it flash both partitions (if only one is written)?
Thanks for your help
ggg777 said:
Thanks for your Help
How can I check if both partitions are with stock and bootloader?
Is there a trick to copy a working partition to the oter?
I would flash like it is written in this: [Guide][Channel][Stock]Moto g7 play Factory Firmware Images
(https://forum.xda-developers.com/g7-play/how-to/channel-moto-g7-factory-firmware-images-t3996303)
Would it flash both partitions (if only one is written)?
Thanks for your help
Click to expand...
Click to collapse
Typically if you've taken an OTA then you already have both slots filled. You can check with...
Code:
fastboot getvar all
Near the bottom you'll see some slot information. If slot b is active, then you should already be covered. I still think it's best to manually flash both slots though. If you've never updated then slot b is definitely empty. This is what I do...
Code:
fastboot flash boot_a boot.img
fastboot sending image boot_a...
Successful!
Image not signed blah blah something that isn't important...
Hit the up arrow on the keyboard then just change _a to _b
Code:
fastboot flash boot_b boot.img
Same with system, only I run through the list of sparse chunks in one shot, then hit the other slot. Use the big series of sparse chunks (0-7) on both slots. Skip the two that would normally go to system_b.
Code:
fastboot flash system_a system.image_sparsechunk.0
fastboot flash system_a system.image_sparsechunk.1
fastboot flash system_a system.image_sparsechunk.2
etc...
Then on the other side the same way.
Code:
fastboot flash system_b system.image_sparsechunk.0
fastboot flash system_b system.image_sparsechunk.1
fastboot flash system_b system.image_sparsechunk.2
etc...
When you get to oem, do not use oem_other.img, flash oem.img to both slots instead. Basically just make sure you do that with everything. E.g. dsp_b modem_b. I'm sure you get the idea by now.
Hello Spaceminer,
I have little knowledge in working with terminal in debian (I used man fastboot and tried some things like changing slots but this did not work). And then I tried some of these things and was to scared to brick it so I flashed it with RDS Lite (I hate to use Windows ) last night.
With RDS Lite flashing was no problem and I got a OTA, so slots a and b are not empty. After that I used your TWRP-Guide which you linked and it worked
BUT
Then I was trying to flash a GSI (arm32binder64ab):
lineage-17.1-20200309-UNOFFICIAL-treble_a64_bvN.img
Havoc-OS-v3.0-20191226-A64AB-Unofficial.img
system-quack-arm32_binder64-ab-vanilla.img
it completed but failed to boot:
Start Up Failed:
---
AP Fastboot Flash Mode (Secure)
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Fastboot Reason: Fall-through from normal boot mode
No bootalbe A/B slot
Failed to boot Linux, falling back to fastboot
Boot up failed
---
TWRP is always available with:
fastboot -> recovery
Could you please help me to handle this?
I would really love to use this phone de-googled with root permission cause I'm sad of spying on me by Gafa and the moto g7 play (I hate the size of the bigger ones) looks like the perfect model for me
PS: I have some screenshot's if you need
ggg777 said:
Hello Spaceminer,
I have little knowledge in working with terminal in debian (I used man fastboot and tried some things like changing slots but this did not work). And then I tried some of these things and was to scared to brick it so I flashed it with RDS Lite (I hate to use Windows ) last night.
With RDS Lite flashing was no problem and I got a OTA, so slots a and b are not empty. After that I used your TWRP-Guide which you linked and it worked
BUT
Then I was trying to flash a GSI (arm32binder64ab):
lineage-17.1-20200309-UNOFFICIAL-treble_a64_bvN.img
Havoc-OS-v3.0-20191226-A64AB-Unofficial.img
system-quack-arm32_binder64-ab-vanilla.img
it completed but failed to boot:
Start Up Failed:
---
AP Fastboot Flash Mode (Secure)
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Fastboot Reason: Fall-through from normal boot mode
No bootalbe A/B slot
Failed to boot Linux, falling back to fastboot
Boot up failed
---
TWRP is always available with:
fastboot -> recovery
Could you please help me to handle this?
I would really love to use this phone de-googled with root permission cause I'm sad of spying on me by Gafa and the moto g7 play (I hate the size of the bigger ones) looks like the perfect model for me
PS: I have some screenshot's if you need
Click to expand...
Click to collapse
Hey im in a smiliar situation with the G7 Play (XT1952-2)
I have the same goal of running this phone without google..
I would like to install LineageOS with microG (signature spoofing)
Have you been successful with this? Do you have a A-Z list of instructions for a fellow newbie?
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