Locking Bootloader - Google Pixel 2 XL Questions & Answers

I searched through threads on here, and the only similar one, there was no solution because OP could not unlock his bootloader.
I unlocked my device, and decided to revert back to stock. I want to retain Android Pay functionality and use Netflix, but do not want to be rooted. I flashed the latest factory images from Google, then locked the bootloader. When i went to boot the device, I was met with an error message saying that it could not find an OS, and I could not proceed from there. If i unlock the bootloader, the device will boot just fine.
Any advice? It's been a long time since i messed around with root etc. Any help would be greatly appreciated.

Flash the factory images to both slots and then lock the bootloader. Use lock_critical as well and see if that helps.

rickysidhu_ said:
Flash the factory images to both slots and then lock the bootloader. Use lock_critical as well and see if that helps.
Click to expand...
Click to collapse
Does using flash all flash to both slots? Pretty sure it says sending to slot a and b in the terminal output. I’ll try doing it manually, but thanks!
Sent from my iPhone using Tapatalk

beats4x said:
Does using flash all flash to both slots? Pretty sure it says sending to slot a and b in the terminal output. I’ll try doing it manually, but thanks!
Click to expand...
Click to collapse
No it doesn't, you have to use the set active command to manually switch slots. I forget the exact command but I'm sure you'll be able to find it with a quick search on XDA/Google.
So the steps would be:
Flash all
Let it boot at least once
Use the set active command to go to the other slot
Flash all again
Let it boot at least once again
Lock the bootloader using both lock and lock_critical
I haven't tried this myself but from researching on my own, these steps seem like the correct way to do things!

rickysidhu_ said:
No it doesn't, you have to use the set active command to manually switch slots. I forget the exact command but I'm sure you'll be able to find it with a quick search on XDA/Google.
So the steps would be:
Flash all
Let it boot at least once
Use the set active command to go to the other slot
Flash all again
Let it boot at least once again
Lock the bootloader using both lock and lock_critical
I haven't tried this myself but from researching on my own, these steps seem like the correct way to do things!
Click to expand...
Click to collapse
This was absolutely it. After doing this, I'm back to normal. Thank you!
As a side note, I also had to update adb/fastboot drivers.

beats4x said:
This was absolutely it. After doing this, I'm back to normal. Thank you!
As a side note, I also had to update adb/fastboot drivers.
Click to expand...
Click to collapse
could you tell me the commands you used to relock the bootloader or thread you used

xringo said:
could you tell me the commands you used to relock the bootloader or thread you used
Click to expand...
Click to collapse
fastboot flashing lock
fastboot flashing lock_critical

TheSt33v said:
fastboot flashing lock
fastboot flashing lock_critical
Click to expand...
Click to collapse
what about switching from a to b

xringo said:
what about switching from a to b
Click to expand...
Click to collapse
fastboot --set-active [a or b depending on which you want]
So if you want b to be active, fastboot --set-active b

rickysidhu_ said:
No it doesn't, you have to use the set active command to manually switch slots. I forget the exact command but I'm sure you'll be able to find it with a quick search on XDA/Google.
So the steps would be:
Flash all
Let it boot at least once
Use the set active command to go to the other slot
Flash all again
Let it boot at least once again
Lock the bootloader using both lock and lock_critical
I haven't tried this myself but from researching on my own, these steps seem like the correct way to do things!
Click to expand...
Click to collapse
I want to create auto process batch with this.
So is it possible to use this steps in this way ?
set active a
Flash all
Let it boot at least once
set active b
Flash all again
Let it boot at least once again
Lock the bootloader using both lock and lock_critical
thanks for your help

XiorgON said:
I want to create auto process batch with this.
So is it possible to use this steps in this way ?
set active a
Flash all
Let it boot at least once
set active b
Flash all again
Let it boot at least once again
Lock the bootloader using both lock and lock_critical
thanks for your help
Click to expand...
Click to collapse
Just modify the flash all bat. To skip reboot. And and you can save yourself some time by not having to boot both of them. Just remember after you fastboot set active slot, to A or B, reboot to Bootloader for it to make the change. Then run your flash all. I don't know if it's really necessary but I do it just in case.

thanks for your help !
is good now what do you think ?
please note that. i want to make batch that will factory restore for returning the phone to google for warranty and relock bootloader
i dont know if i need to set active partition for factory restore or just for the bootloader locking process.
adb reboot bootloader
fastboot --set-active a
fastboot flash bootloader bootloader-taimen-tmz12bb.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-taimen-g8998-00164-1710262031.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-taimen-opm1.171019.021.zip
fastboot reboot-bootloader
fastboot --set-active b
fastboot flash bootloader bootloader-taimen-tmz12bb.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-taimen-g8998-00164-1710262031.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-taimen-opm1.171019.021.zip

XiorgON said:
thanks for your help !
is good now what do you think ?
please note that. i want to make batch ta will factory restore and relock bootloader
i dont know if i need to set active partition for factory restore or just for the bootloader locking process.
adb reboot bootloader
fastboot --set-active a
fastboot flash bootloader bootloader-taimen-tmz12bb.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-taimen-g8998-00164-1710262031.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-taimen-opm1.171019.021.zip
fastboot reboot-bootloader
fastboot --set-active b
fastboot flash bootloader bootloader-taimen-tmz12bb.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-taimen-g8998-00164-1710262031.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-taimen-opm1.171019.021.zip
Click to expand...
Click to collapse
If you clean flash the factory image, that will wipe your phone and return it to stock. Then you can just run the bootloader locking commands. Not sure why you want to make a script to do that, but best of luck to ya :good:

Badger50 said:
If you clean flash the factory image, that will wipe your phone and return it to stock. Then you can just run the bootloader locking commands. Not sure why you want to make a script to do that, but best of luck to ya :good:
Click to expand...
Click to collapse
ok so why is telling that is needed to set active a or b ?
i need to set it or not ?

XiorgON said:
ok so why is telling that is needed to set active a or b ?
i need to set it or not ?
Click to expand...
Click to collapse
If your clean flashing the factory image via fastboot, then it doesn't matter. It'll wipe the phone and install the OS to both slots.

XiorgON said:
ok so why is telling that is needed to set active a or b ?
i need to set it or not ?
Click to expand...
Click to collapse
I flashed the developer preview using the flashall.sh file and did not have to flash to a then b. The script takes care of that.

Related

[Q] Bricked Galaxy Nexus GSM 4.1.1

I was trying to update my Galaxy Nexus GSM 4.1.1 but I did something wrong and now its not booting.
The bootloader was unlocked using fastboot. Then I am not sure what command I used, it was either "fastboot boot boot.img" or "fastboot flash boot boot.img" and now the phone won't start. Any suggestions?
ytsentas1 said:
I was trying to update my Galaxy Nexus GSM 4.1.1 but I did something wrong and now its not booting.
The bootloader was unlocked using fastboot. Then I am not sure what command I used, it was either "fastboot boot boot.img" or "fastboot flash boot boot.img" and now the phone won't start. Any suggestions?
Click to expand...
Click to collapse
As you are describing adb commands I assume you know at least half the stuff you need to know for manual flashing. If you used the factory image, aka "takju-jop40c-factory-1a47c890.tgz" and unpacked the contents, you need to follow the steps inside "flash-all.sh" - which are as follows:
While in bootloader, type:
Code:
fastboot flash bootloader bootloader-maguro-primelc03.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxlh1.img
fastboot reboot-bootloader
fastboot -w update image-takju-jop40c.zip
This, of course, only applies for the respective update above.
Solution
Thank you for the help but I was able to figure it out after some googling.
I wrote a short guide that will help anyone else that has a problem.
tsentas.net/flash-galaxy-nexus-to-latest-android/

Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command"

Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command"
Fixed flashing error "remote: unsupported command" when flashing a Pixel C back to stock
I used TWRP and SuperSU to root and modify the buildprops to enable and get an early look at the windowing in Android N beta on my Pixel C release 5 ahead of time.
When Release 5 NPD90G was available I decided to flash back to stock from Developer Preview 4 NPD56N rooted with SuperSU and flashed with TWRP. I like root - I run Ubuntu and Win 7. I don't mind running a rooted device if it doesn't have all my work and financial data. When the final N release is out, the Pixel C will become my work machine. It's almost there.
I'm naturally paranoid. I change my long passwords frequently and use 2 factor authentication for everything. So if I can, I'll take a stock release. See my instructions for wiping Android devices: How to wipe an Android Phone: the paranoid editon
I could not flash the NPD90G stock bootloader because of an error "remote: unsupported command"
Here's how I fixed it.
Updated the SDK manager including SDK Tools and USB drivers.
With the Pixel C in recovery mode, {hold the power key and volume down}
In TWRP mount System and reboot to recovery
>ADB Shell.
From ADB Shell I ran
>fwtool vbnv write dev_boot_fastboot_full_cap 1 to reenable Fast boot.
Then I changed from TWRP to Fastboot mode {power button plus hold the volume up button}
>fastboot erase userdata
>fastboot erase boot
>fastboot erase cache
>fastboot erase recovery
>fastboot erase system
See Note 1. Below
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
Note 1.
The first time through I flashed the following line items which resulted in the resting robot Andi. I don't think I needed to do this, but if the above instructions don't work, run the following before continuing for {flash bootloader bootloader-dragon-google_smaug.7900.27.0.img}
>flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot reboot-bootloader
>fastboot flash system system.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
>fastboot flash cache cache.img
Twrp can't flash
The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command
Tugio said:
The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command
Click to expand...
Click to collapse
When in fastboot mode, use:
Code:
fastboot boot twrp-local-file-on-computer.img
DanBUK said:
When in fastboot mode, use:
Click to expand...
Click to collapse
It's nice of you to help a fellow XDA user. But I suspect he's already solved his problem of three months ago.....
Hi guys
I have the same problem:
- the bootloader is unlocked (Coreboot menu says so)
- fastboot says "secure: yes" but "unlocked: yes" too
- "fastboot flashing get_unlock_ability" returns "1"
- "fastboot flashing unlock" says that the bootloader is already unlocked
But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error
Can I do something to unbrick the device?
Regards
lllopa said:
Hi guys
I have the same problem:
- the bootloader is unlocked (Coreboot menu says so)
- fastboot says "secure: yes" but "unlocked: yes" too
- "fastboot flashing get_unlock_ability" returns "1"
- "fastboot flashing unlock" says that the bootloader is already unlocked
But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error
Can I do something to unbrick the device?
Regards
Click to expand...
Click to collapse
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Make sure you have the latest version of fastboot and adb. I get these errors almost every month if I don't update.
https://developer.android.com/studio/releases/platform-tools.html
@stevep2007, thank you so much! I've been dealing with this "remote: unsupported command" nonsense for days now after trying to revert back to an older Oreo version of Lineage. This did the trick!
How can I solve the problem when my Pixel C is not unlocked? My Pixel made an update and after installing the Update I got the green little man. Now I have no Chance to activate USB debugging etc. Its also not possible to install twrp.img
How can I go to ADB shell with locked bootloader? Or isn't it possible?
Fastboot devices shows me my tablet. ADB devices also show my tablet with "sideload".
But every try to flash my Pixel fails. I alway get the message .... remote: unknown command.......fastboot error: command failed
flash-all.bat showes that all "*.img are missing" error: command failed... unknown command etc.......
So any idea to get my Pixel working again? ADB shell would make it I think. But how with locked bootloader.
_Arne_ said:
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Click to expand...
Click to collapse
This did it for me!! Thanks much. I also updated platform-tools at the same time, who knows which did it
_Arne_ said:
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Click to expand...
Click to collapse
In the scenario described by @llopa this solution does not work.
In that scenario there are no solutions
bernardomarx said:
In the scenario described by @llopa this solution does not work.
In that scenario there are no solutions
Click to expand...
Click to collapse
Sorry replied incorrectly

Pixel XL stuck in boot animation

I have a rooted Pixel XL. I kept the OEM ROM. Besides being rooted it's stock. I'm selling the phone and did a factory reset within the menu. It rebooted and now it's stuck in the boot animation screen. I went into recovery mode and wiped it that way as well. When I reboot, it's the same thing. I see the "Google" logo, but then it's just stuck on the animation screen. Did I forget to do something? Do I have to re-lock it before I wipe it? Thank you
flint24 said:
I have a rooted Pixel XL. I kept the OEM ROM. Besides being rooted it's stock. I'm selling the phone and did a factory reset within the menu. It rebooted and now it's stuck in the boot animation screen. I went into recovery mode and wiped it that way as well. When I reboot, it's the same thing. I see the "Google" logo, but then it's just stuck on the animation screen. Did I forget to do something? Do I have to re-lock it before I wipe it? Thank you
Click to expand...
Click to collapse
First and foremost don't relock it. If you want to clean it up for selling purposes, then you're best bet is to flash a full factory image. Nice and easy and the phone will be complete stock after.
Post above is dead on, just flash all. Also remember to properly remove your Google account so the buyer doesn't have problems.
Sent from my Pixel XL using XDA Labs
toknitup420 said:
First and foremost don't relock it. If you want to clean it up for selling purposes, then you're best bet is to flash a full factory image. Nice and easy and the phone will be complete stock after.
Click to expand...
Click to collapse
Thanks. It actually came back up after rebooting it a few times. I'm still a little concerned as I don't want the buyer to go through the same hassle should he also try to factory reset it from the menu. I didn't change the image at all, just unlocked the bootloader and rooted the phone. I'm afraid to **** with it any more. It's working now. I'm just hoping the buyer doesn't a) play with the factory reset and b) mind the "bootloader is unlocked" message when the phone is rebooted.
flint24 said:
Thanks. It actually came back up after rebooting it a few times. I'm still a little concerned as I don't want the buyer to go through the same hassle should he also try to factory reset it from the menu. I didn't change the image at all, just unlocked the bootloader and rooted the phone. I'm afraid to **** with it any more. It's working now. I'm just hoping the buyer doesn't a) play with the factory reset and b) mind the "bootloader is unlocked" message when the phone is rebooted.
Click to expand...
Click to collapse
Wait I'm confused. Did you sell the phone in a non bootable state? Do you have twrp on it?
toknitup420 said:
Wait I'm confused. Did you sell the phone in a non bootable state? Do you have twrp on it?
Click to expand...
Click to collapse
No it boots. It boots into whatever image was on it when I bought it at Verizon. I just unlocked the bootloader and gave myself root access. I didn't use TWRP.
Ok now I have a new problem. The guy I sold the phone to didn't like that the bootloader was unlocked. He called Google who made him re-lock the bootloader. So he sent the phone back to me completely bricked. Now I get a RED exclamation triangle on the boot screen, saying the device is corrupt and can't be trusted. Then it shuts off. It doesn't even go to the bouncing ball Google startup screen. I'm able to get into the bootloader screen which confirms that it's locked. However I'm unable to get to a recovery. When I press the vol up/down buttons to choose recovery, it just reboots and shuts off like before. I can only get to the bootloader.
Is there anything I can do to salvage this phone? Thanks guys.
Edit 1: I'm able to boot into safe mode.
Edit 2: I'm not longer able to get into safe mode. It freezes during the boot and the bouncing balls just stop. A "G" comes up, then it turns off.
Nevermind disregard
Is there any way to boot into safe mode from fastboot? Or install a recovery, even stock recovery, without the bootloader being unlocked?
Sent from my EDI-AL10 using Tapatalk
flint24 said:
Is there any way to boot into safe mode from fastboot?
Click to expand...
Click to collapse
This was the very first result when I googled your question. Hope it helps?
https://recomhub.com/blog/how-to-start-google-pixel-and-pixel-xl-in-safe-mode/
flint24 said:
Or install a recovery, even stock recovery, without the bootloader being unlocked?
Click to expand...
Click to collapse
I'm pretty sure it's not possible. About 97% sure.
But I haven't researched it or anything.
CZ Eddie said:
This was the very first result when I googled your question. Hope it helps?
https://recomhub.com/blog/how-to-start-google-pixel-and-pixel-xl-in-safe-mode/
I'm pretty sure it's not possible. About 97% sure.
But I haven't researched it or anything.
Click to expand...
Click to collapse
Thanks but I've been trying to get back into safe mode this way for days now. I was able to do it once, but never again for some strange reason. Since it turns off immediately after boot, I have to go into fastboot then run the fastboot continue command just to get to the Google startup screen. Then I press and hold volume down. It's only worked once.
Sent from my EDI-AL10 using Tapatalk
flint24 said:
Thanks but I've been trying to get back into safe mode this way for days now. I was able to do it once, but never again for some strange reason. Since it turns off immediately after boot, I have to go into fastboot then run the fastboot continue command just to get to the Google startup screen. Then I press and hold volume down. It's only worked once.
Sent from my EDI-AL10 using Tapatalk
Click to expand...
Click to collapse
I get it now. You're looking for a way to access Safe Mode specifically from within Fastboot.
Try this link?
http://android.stackexchange.com/questions/131188/entering-safe-mode-from-adb-shell
Please let us know what you find out.
Sharing [info] is caring.
EDIT: That link is for ADB, not Fastboot. oops.
CZ Eddie said:
I get it now. You're looking for a way to access Safe Mode specifically from within Fastboot.
Try this link?
http://android.stackexchange.com/questions/131188/entering-safe-mode-from-adb-shell
Please let us know what you find out.
Sharing [info] is caring.
EDIT: That link is for ADB, not Fastboot. oops.
Click to expand...
Click to collapse
Do you have to be in recovery mode to run adb commands? I'm only able to get into fastboot mode.
Sent from my EDI-AL10 using Tapatalk
flint24 said:
Do you have to be in recovery mode to run adb commands? I'm only able to get into fastboot mode.
Click to expand...
Click to collapse
Yep, sorry. That's why I edited my post.
ADB only works from recovery.
I googled for a couple minutes but couldn't find a Safe Mode command for fastboot. Sorry.
---------- Post added at 05:18 PM ---------- Previous post was at 05:17 PM ----------
What happens if you get into Fastboot and run the command "fastboot continue"?
CZ Eddie said:
Yep, sorry. That's why I edited my post.
ADB only works from recovery.
I googled for a couple minutes but couldn't find a Safe Mode command for fastboot. Sorry.
Click to expand...
Click to collapse
You see my pain here man lol. My phone is completely jacked. Whoever this guy called who bought my phone (I think it was Google) had him hack proof the phone.
Sent from my EDI-AL10 using Tapatalk
CZ Eddie said:
Yep, sorry. That's why I edited my post.
ADB only works from recovery.
I googled for a couple minutes but couldn't find a Safe Mode command for fastboot. Sorry.
---------- Post added at 05:18 PM ---------- Previous post was at 05:17 PM ----------
What happens if you get into Fastboot and run the command "fastboot continue"?
Click to expand...
Click to collapse
It starts to boot. I see the spinning balls, then they stop and stand in place. Sometimes I see a "G" and then the screen goes dark. It's not off though. The screen just does dark
Sent from my EDI-AL10 using Tapatalk
flint24 said:
It starts to boot. I see the spinning balls, then they stop and stand in place. Sometimes I see a "G" and then the screen goes dark. It's not off though. The screen just does dark
Click to expand...
Click to collapse
There does not appear to be a safe mode option for fastboot.
I'm very uncomfortable offering suggestions here because I'm out of my depth and your phone is a Verizon that was unlocked and then re-locked which is even more of an unknown for me.
Have you tried to fasboot anything like flash-all.bat or fastboot boot twrp.img just to see what happens?
I'm just throwing stuff on the wall here. TWRP probably won't work because it sounds like you're relocked.
Anything you do from here on could likely brick your phone even harder.
Here's a list of fastoot commands.
I'm really interested to know if unlock works, or if the critical unlock works and lets you boot a boot img or something to gain access to recovery.
Check out all the various unlock options.
Again, I'm out of my depth and doing ANYTHING here could brick you harder.
May be best to wait for some better help.
Code:
C:\Users\xxx\AppData\Local\Android\sdk1\platform-tools>fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> Reflash device from update.zip.
Sets the flashed slot as active.
flashall Flash boot, system, vendor, and --
if found -- recovery. If the device
supports slots, the slot that has
been flashed to is set as active.
Secondary images may be flashed to
an inactive slot.
flash <partition> [ <filename> ] Write a file to a flash partition.
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing
any partition except
bootloader-related partitions.
flashing lock_critical Prevents flashing bootloader-related
partitions.
flashing unlock_critical Enables flashing bootloader-related
partitions.
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked.
flashing get_unlock_bootloader_nonce Queries the bootloader to get the
unlock nonce.
flashing unlock_bootloader <request> Issue unlock bootloader using request
.
flashing lock_bootloader Locks the bootloader to prevent
bootloader version rollback.
erase <partition> Erase a flash partition.
format[:[<fs type>][:[<size>]] <partition>
Format a flash partition. Can
override the fs type and/or size
the bootloader reports.
getvar <variable> Display a bootloader variable.
set_active <slot> Sets the active slot. If slots are
not supported, this does nothing.
boot <kernel> [ <ramdisk> [ <second> ] ] Download and boot kernel.
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ]
Create bootimage and flash it.
devices [-l] List all connected devices [with
device paths].
continue Continue with autoboot.
reboot [bootloader] Reboot device [into bootloader].
reboot-bootloader Reboot device into bootloader.
help Show this help message.
options:
-w Erase userdata and cache (and format
if supported by partition type).
-u Do not erase partition before
formatting.
-s <specific device> Specify a device. For USB, provide ei
ther
a serial number or path to device por
t.
For ethernet, provide an address in t
he
form <protocol>:<hostname>[:port] whe
re
<protocol> is either tcp or udp.
-p <product> Specify product name.
-c <cmdline> Override kernel commandline.
-i <vendor id> Specify a custom USB vendor id.
-b, --base <base_addr> Specify a custom kernel base
address (default: 0x10000000).
--kernel-offset Specify a custom kernel offset.
(default: 0x00008000)
--ramdisk-offset Specify a custom ramdisk offset.
(default: 0x01000000)
--tags-offset Specify a custom tags offset.
(default: 0x00000100)
-n, --page-size <page size> Specify the nand page size
(default: 2048).
-S <size>[K|M|G] Automatically sparse files greater
than 'size'. 0 to disable.
--slot <slot> Specify slot name to be used if the
device supports slots. All operations
on partitions that support slots will
be done on the slot specified.
'all' can be given to refer to all sl
ots.
'other' can be given to refer to a
non-current slot. If this flag is not
used, slotted partitions will default
to the current active slot.
-a, --set-active[=<slot>] Sets the active slot. If no slot is
provided, this will default to the va
lue
given by --slot. If slots are not
supported, this sets the current slot
to be active. This will run after all
non-reboot commands.
--skip-secondary Will not flash secondary slots when
performing a flashall or update. This
will preserve data on other slots.
--unbuffered Do not buffer input or output.
--version Display version.
-h, --help show this message.
C:\Users\xxx\AppData\Local\Android\sdk1\platform-tools>
---------- Post added at 05:39 PM ---------- Previous post was at 05:37 PM ----------
Here is my guide for the flash-all.bat if you want to see if it works.
I think you might have to be unlocked though?
https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
CZ Eddie said:
There does not appear to be a safe mode option for fastboot.
I'm very uncomfortable offering suggestions here because I'm out of my depth and your phone is a Verizon that was unlocked and then re-locked which is even more of an unknown for me.
Have you tried to fasboot anything like flash-all.bat or fastboot boot twrp.img just to see what happens?
I'm just throwing stuff on the wall here. TWRP probably won't work because it sounds like you're relocked.
Anything you do from here on could likely brick your phone even harder.
Here's a list of fastoot commands.
I'm really interested to know if unlock works, or if the critical unlock works and lets you boot a boot img or something to gain access to recovery.
Check out all the various unlock options.
Again, I'm out of my depth and doing ANYTHING here could brick you harder.
May be best to wait for some better help.
Code:
C:\Users\xxx\AppData\Local\Android\sdk1\platform-tools>fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> Reflash device from update.zip.
Sets the flashed slot as active.
flashall Flash boot, system, vendor, and --
if found -- recovery. If the device
supports slots, the slot that has
been flashed to is set as active.
Secondary images may be flashed to
an inactive slot.
flash <partition> [ <filename> ] Write a file to a flash partition.
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing
any partition except
bootloader-related partitions.
flashing lock_critical Prevents flashing bootloader-related
partitions.
flashing unlock_critical Enables flashing bootloader-related
partitions.
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked.
flashing get_unlock_bootloader_nonce Queries the bootloader to get the
unlock nonce.
flashing unlock_bootloader <request> Issue unlock bootloader using request
.
flashing lock_bootloader Locks the bootloader to prevent
bootloader version rollback.
erase <partition> Erase a flash partition.
format[:[<fs type>][:[<size>]] <partition>
Format a flash partition. Can
override the fs type and/or size
the bootloader reports.
getvar <variable> Display a bootloader variable.
set_active <slot> Sets the active slot. If slots are
not supported, this does nothing.
boot <kernel> [ <ramdisk> [ <second> ] ] Download and boot kernel.
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ]
Create bootimage and flash it.
devices [-l] List all connected devices [with
device paths].
continue Continue with autoboot.
reboot [bootloader] Reboot device [into bootloader].
reboot-bootloader Reboot device into bootloader.
help Show this help message.
options:
-w Erase userdata and cache (and format
if supported by partition type).
-u Do not erase partition before
formatting.
-s <specific device> Specify a device. For USB, provide ei
ther
a serial number or path to device por
t.
For ethernet, provide an address in t
he
form <protocol>:<hostname>[:port] whe
re
<protocol> is either tcp or udp.
-p <product> Specify product name.
-c <cmdline> Override kernel commandline.
-i <vendor id> Specify a custom USB vendor id.
-b, --base <base_addr> Specify a custom kernel base
address (default: 0x10000000).
--kernel-offset Specify a custom kernel offset.
(default: 0x00008000)
--ramdisk-offset Specify a custom ramdisk offset.
(default: 0x01000000)
--tags-offset Specify a custom tags offset.
(default: 0x00000100)
-n, --page-size <page size> Specify the nand page size
(default: 2048).
-S <size>[K|M|G] Automatically sparse files greater
than 'size'. 0 to disable.
--slot <slot> Specify slot name to be used if the
device supports slots. All operations
on partitions that support slots will
be done on the slot specified.
'all' can be given to refer to all sl
ots.
'other' can be given to refer to a
non-current slot. If this flag is not
used, slotted partitions will default
to the current active slot.
-a, --set-active[=<slot>] Sets the active slot. If no slot is
provided, this will default to the va
lue
given by --slot. If slots are not
supported, this sets the current slot
to be active. This will run after all
non-reboot commands.
--skip-secondary Will not flash secondary slots when
performing a flashall or update. This
will preserve data on other slots.
--unbuffered Do not buffer input or output.
--version Display version.
-h, --help show this message.
C:\Users\xxx\AppData\Local\Android\sdk1\platform-tools>
---------- Post added at 05:39 PM ---------- Previous post was at 05:37 PM ----------
Here is my guide for the flash-all.bat if you want to see if it works.
I think you might have to be unlocked though?
https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
Click to expand...
Click to collapse
Yes it definitely has to be unlocked to run the flash-all.bat or flash-all.sh (I'm using a mac). I've tried it and it gives me an "oem unlock not allowed" message. I'll try the other commands I haven't tried yet from your list
Sent from my EDI-AL10 using Tapatalk
What about flashing unlock_bootloader request? Also fastboot flashing unlock critical. I am sure this can get fixed.
biggiesmalls657 said:
What about flashing unlock_bootloader request? Also fastboot flashing unlock critical. I am sure this can get fixed.
Click to expand...
Click to collapse
I can only do flashboot oem, not flashboot flashing. I think the newer versions of fastboot only does the oem command.
flashboot oem unlock_bootloader and flashboot oem unlock critical both fail (remote: oem unlock is not allowed)
Sent from my EDI-AL10 using Tapatalk

XT1955-5 bootloader unlock install TWRP & Root with Magisk

So when I got this device I went to root it and found there's not very good documentation on what to do to get root and recovery installed so after many boot loops and reinstall of firmware here is what I did to gain root and TWRP and have a stable environment. You will need to use ADB & Fastboot commands please install either this : https://forum.xda-developers.com/showthread.php?t=2317790 or https://forum.xda-developers.com/showthread.php?t=2588979 or you can install from here: https://developer.android.com/studio/releases/platform-tools. you will also need the Motorola drivers located here: https://support.motorola.com/us/en/solution/MS88481. Once you have obtained these you can proceed with the bootloader unlock. I have the unlocked version of the Motorola G7 Power so I was able to fallow the sets here: https://support.motorola.com/us/en/bootloader/unlockyourdeviceb. If you have a different variant I'm not sure if your able to unlock your bootloader please try and let me know in this thread. I AM NOT RESPONSIBLE IF YOU SCREW YOUR DEVICE UP OR FOR ANY DAMAGE TO YOUR DEVICE
Bootloader unlock steps:
1. On your device go to Settings and to System, Then About phone and click " Build Number " until you unlock developer options.
2. Back out one step and click the Advanced tab and then click " Developer Options ".
3. Once in developer options " OEM Unlocking " turn off " Automatic Updates " and enable "USB Debugging".
4. Once you have done USB Debugging open the start button type "CMD" and open a command prompt.
5. Once in command prompt type " adb devices " make sure you authorize the pc on the phone. then type in command prompt " adb reboot bootloader "
6. Once in bootloader type in command prompt " fastboot oem get_unlock_data " from here fallow the directions on the Motorola Bootloader Unlocking page: https://support.motorola.com/us/en/bootloader/unlockyourdevice
7. Take the number given to you by Motorola and type in command prompt " fastboot oem unlock CODE FROM MOTO " then enter the same command again and your device will be bootloader unlocked.
TWRP & Magisk install:
This is where I found it to be difficult to get things right either I would bootloop or I wouldn't be able to unencrypt my sd card in TWRP so I couldn't read things right all sorts of dumb issues. All the files I used are attached so please let me know if this works as well as it did for me. Please download the TWRP .img file it was too large to attach: https://dl.twrp.me/ocean/ Also make sure that your command prompt is in the directory of your stored files.
Here are a list of commands to get TWRP and install Root please be in bootloader mode to start this process.
1. fastboot boot twrp-3.3.1-2-ocean.img
2. In TWRP go to the wipe option and select the format and type " yes " once it has done that go back to the main TWRP page by hitting the home bottom and select Reboot and select Reboot Bootloader.
3. fastboot boot twrp-3.3.1-2-ocean.img
4. Once in TWRP adb push twrp-installer-3.3.1-2-ocean.zip /tmp/ then click install and navigate to the /tmp folder and install the TWRP .zip file
5. After you install TWRP do this : adb push Magisk-v20.1(20100).zip /tmp/ then navigate to your /tmp folder and install Magisk .zip file
6. After you install magisk you can reboot the system and let it sit it might loop once or twice but it will boot. I did the force encrypt disable with the attached zip file then i rebooted.
Also I found it best to do this with a fresh installed firmware that hasn't been booted yet I downloaded the firmware/ROM from here: https://mirrors.lolinet.com/firmware/moto/ocean/official/RETUS/ here is a list of commands to copy and paste into command prompt please make sure your device is in bootloader/ fastboot mode.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
Well i messed it up some how. my phone would boot loop three times and then go back to the twrp screen. after 30 minutes of messing with it i gave up and factory reset it via the adb platform tools.
Got it to work but had to start fresh as said at very bottom using retus version, I did all that then step by step but i booted once just to enable usb debugging of course, already had oem unlock but then right back into recovery flashed magisk and disable dm verity both back to back before reboot and all went fine cant get ota ofc but surely better roms will start showing up soon and I wont give a crap about stock anymore.
---------- Post added at 08:30 PM ---------- Previous post was at 08:29 PM ----------
toxinburn said:
Got it to work but had to start fresh as said at very bottom using retus version, I did all that then step by step but i booted once just to enable usb debugging of course, already had oem unlock but then right back into recovery flashed magisk and disable dm verity both back to back before reboot and all went fine cant get ota ofc but surely better roms will start showing up soon and I wont give a crap about stock anymore.
Click to expand...
Click to collapse
I am gonna check one thing I had it all working another method before but after installing something thru magisk it soft bricked I think it was vanced youtube maybe also cant seem to find a way to get vipre to work sadly.
Question
Does this method bypass the screen lock password on the phone? I have this phone that is locked with a passcode, so I can't easily get it into developer mode. Sorry, I'm a total newbie to this but am trying to learn. Thanks in advance!
A tip for linux users. If you are getting "< waiting for any device >" after the "fastboot oem get_unlock_data". Ctrl-c to exit the command. Su to root and then "fastboot oem get_unlock_data".
I give up, SIM stopped working after multiple failed attempts at installing Custom ROMs, even so much as installing Magisk+force encrypt disable brings up Factory data reset screen. Now my SIM doesn't even work on another stock phone for some reason, since the ban that apparently exists, if applied, should be IMEI-only, and somehow it works on a Custom ROM+Magisk device of mine. Going back to stock with locked bootloader I guess
SIM stopped working on G7 Power = neither SIM from two different carriers, one that's never been on a rooted/unlocked bootloader phone, don't even show up as a grey signal icon, tried both slots.
My SIM not working on another stock phone (G7 Play) = not recognized at all, but at least it recognizes there's a SIM card in there, grey signal.
Working fine on G5 with Magisk, Xposed and OmniROM
So maybe I banned both the chip (?) and IMEI, but still for some reason it works on another bootloader unlocked phone
Hyoretsu said:
I give up, SIM stopped working after multiple failed attempts at installing Custom ROMs, even so much as installing Magisk+force encrypt disable brings up Factory data reset screen. Now my SIM doesn't even work on another stock phone for some reason, since the ban that apparently exists, if applied, should be IMEI-only, and somehow it works on a Custom ROM+Magisk device of mine. Going back to stock with locked bootloader I guess
SIM stopped working on G7 Power = neither SIM from two different carriers, one that's never been on a rooted/unlocked bootloader phone, don't even show up as a grey signal icon, tried both slots.
My SIM not working on another stock phone (G7 Play) = not recognized at all, but at least it recognizes there's a SIM card in there, grey signal.
Working fine on G5 with Magisk, Xposed and OmniROM
So maybe I banned both the chip (?) and IMEI, but still for some reason it works on another bootloader unlocked phone
Click to expand...
Click to collapse
From what I've been able to tell, the SIM cards are locked via IMEI (from MetroPCS I assume?, cause that's what they do), and will appear invalid, but should show the phone number in the settings. It should also say out of service, unless inserted into the phone that it originally belonged to.
I have an E5 Play, and unlocked it using the device unlock app built-in from MetroPCS, after 3 months of service (maybe 6 I forget). After that, I could throw in other SIMs. But the phones those SIMs would come out of, they couldn't read the metro card. They said invalid. But it still recognized it was a card, and showed phone number in settings. Said out of service.
After realizing this, I found out you can change devices in the website real quick, and that should solve the "invalid SIM" issue.
Possibly some custom ROMs lack what restricts all this in the first place, and the Sim must be valid because it's a SIM, in service, and the proper network. No clue there. What carrier are you on?
Linux-Lord said:
From what I've been able to tell, the SIM cards are locked via IMEI (from MetroPCS I assume?, cause that's what they do), and will appear invalid, but should show the phone number in the settings. It should also say out of service, unless inserted into the phone that it originally belonged to.
Click to expand...
Click to collapse
The thing is, "stopped working" literally, it doesn't have out of service, phone number, no signal, not even the "emergency calls only", heck I can't even find my IMEI in settings nor *#0606#, I think that's what's causing the problem. This SIM also came from that Custom ROM device (originally inserted there, but bought as a standalone data plan)
Linux-Lord said:
and will appear invalid, but should show the phone number in the settings. It should also say out of service, unless inserted into the phone that it originally belonged to.
Click to expand...
Click to collapse
If you're talking about how it showed up like that on the G7 Play it used to work just fine in there, and no, that's not the original phone, it's just a phone I used to test if my SIM was still working
Linux-Lord said:
I have an E5 Play, and unlocked it using the device unlock app built-in from MetroPCS, after 3 months of service (maybe 6 I forget). After that, I could throw in other SIMs. But the phones those SIMs would come out of, they couldn't read the metro card. They said invalid. But it still recognized it was a card, and showed phone number in settings. Said out of service.
Click to expand...
Click to collapse
In this phone, G7 Power, it doesn't even recognize a card is in the tray anymore (unlike the G7 Play which at least knows there's one and G5+Custom ROM, in which it works)
Linux-Lord said:
After realizing this, I found out you can change devices in the website real quick, and that should solve the "invalid SIM" issue.
Possibly some custom ROMs lack what restricts all this in the first place, and the Sim must be valid because it's a SIM, in service, and the proper network. No clue there. What carrier are you on?
Click to expand...
Click to collapse
Not that it's gonna help much but OI (Brazil), and if that's on Motorola support page my G7 Power is main phone already.
Is the force encrypt disable necessary? And what does it do?
So, I have successfully rooted my Moto G7 Power by using the method above, but i tried not doing the "format data" and fortunately, I have rooted my phone. For the 1st attempt, I kinda soft-bricked my device by doing the steps briefly, my phone would always bootloop back to recovery mode, but after not doing the "format data" step, it led to a success. So for anyone who are currently experiencing bootloop, flash the stock firmware to your phone and root it again by using the method above but don't do the "format data" step. (flashing the stock firmware would not re-lock the bootloader, so you can try to root your phone again easily.)
error
I get this error
C:\Program Files (x86)\Minimal ADB and Fastboot> adb push magisk adb push Magisk-v20.1(20100).zip /tmp/
adb: error: cannot stat 'magisk': No such file or directory
adb: error: cannot stat 'adb': No such file or directory
adb: error: cannot stat 'push': No such file or directory
adb: error: cannot stat 'Magisk-v20.1(20100).zip': No such file or directory
---------- Post added at 08:07 AM ---------- Previous post was at 07:49 AM ----------
gladiatorbong said:
Well i messed it up some how. my phone would boot loop three times and then go back to the twrp screen. after 30 minutes of messing with it i gave up and factory reset it via the adb platform tools.
Click to expand...
Click to collapse
same here
brokenlocked22 said:
I get this error
C:\Program Files (x86)\Minimal ADB and Fastboot> adb push magisk adb push Magisk-v20.1(20100).zip /tmp/
adb: error: cannot stat 'magisk': No such file or directory
adb: error: cannot stat 'adb': No such file or directory
adb: error: cannot stat 'push': No such file or directory
adb: error: cannot stat 'Magisk-v20.1(20100).zip': No such file or directory
Click to expand...
Click to collapse
I mean, that's entirely on you, the command is wrong. Remove the first 3 words. And check the name of your Magisk ZIP (and location)
Hyoretsu said:
I mean, that's entirely on you, the command is wrong. Remove the first 3 words. And check the name of your Magisk ZIP (and location)
Click to expand...
Click to collapse
same thing as always.. no matter what lol
brokenlocked22 said:
same thing as always.. no matter what lol
Click to expand...
Click to collapse
If it's same thing as always then you're still using "adb push magisk adb push Magisk-v20.1(20100).zip /tmp/". There's no "but I'm not", if it's indeed the same error as before you're messing up on the syntax. Make sure you've put Magisk inside Minimal ADB folder, rename it to magisk.zip and run "adb push magisk.zip /tmp/"
why is magisk pushed to tmp and not to internal storage . Why not just push magisk to internal sotrage and just install that way through twrp or that wont work. just wondering.
Anyone tried this on XT1955-4?
dirtyscout said:
So when I got this device I went to root it and found there's not very good documentation on what to do to get root and recovery installed so after many boot loops and reinstall of firmware here is what I did to gain root and TWRP and have a stable environment. You will need to use ADB & Fastboot commands please install either this : https://forum.xda-developers.com/showthread.php?t=2317790 or https://forum.xda-developers.com/showthread.php?t=2588979 or you can install from here: https://developer.android.com/studio/releases/platform-tools. you will also need the Motorola drivers located here: https://support.motorola.com/us/en/solution/MS88481. Once you have obtained these you can proceed with the bootloader unlock. I have the unlocked version of the Motorola G7 Power so I was able to fallow the sets here: https://support.motorola.com/us/en/bootloader/unlockyourdeviceb. If you have a different variant I'm not sure if your able to unlock your bootloader please try and let me know in this thread. I AM NOT RESPONSIBLE IF YOU SCREW YOUR DEVICE UP OR FOR ANY DAMAGE TO YOUR DEVICE
Bootloader unlock steps:
1. On your device go to Settings and to System, Then About phone and click " Build Number " until you unlock developer options.
2. Back out one step and click the Advanced tab and then click " Developer Options ".
3. Once in developer options " OEM Unlocking " turn off " Automatic Updates " and enable "USB Debugging".
4. Once you have done USB Debugging open the start button type "CMD" and open a command prompt.
5. Once in command prompt type " adb devices " make sure you authorize the pc on the phone. then type in command prompt " adb reboot bootloader "
6. Once in bootloader type in command prompt " fastboot oem get_unlock_data " from here fallow the directions on the Motorola Bootloader Unlocking page: https://support.motorola.com/us/en/bootloader/unlockyourdevice
7. Take the number given to you by Motorola and type in command prompt " fastboot oem unlock CODE FROM MOTO " then enter the same command again and your device will be bootloader unlocked.
TWRP & Magisk install:
This is where I found it to be difficult to get things right either I would bootloop or I wouldn't be able to unencrypt my sd card in TWRP so I couldn't read things right all sorts of dumb issues. All the files I used are attached so please let me know if this works as well as it did for me. Please download the TWRP .img file it was too large to attach: https://dl.twrp.me/ocean/ Also make sure that your command prompt is in the directory of your stored files.
Here are a list of commands to get TWRP and install Root please be in bootloader mode to start this process.
1. fastboot boot twrp-3.3.1-2-ocean.img
2. In TWRP go to the wipe option and select the format and type " yes " once it has done that go back to the main TWRP page by hitting the home bottom and select Reboot and select Reboot Bootloader.
3. fastboot boot twrp-3.3.1-2-ocean.img
4. Once in TWRP adb push twrp-installer-3.3.1-2-ocean.zip /tmp/ then click install and navigate to the /tmp folder and install the TWRP .zip file
5. After you install TWRP do this : adb push Magisk-v20.1(20100).zip /tmp/ then navigate to your /tmp folder and install Magisk .zip file
6. After you install magisk you can reboot the system and let it sit it might loop once or twice but it will boot. I did the force encrypt disable with the attached zip file then i rebooted.
Also I found it best to do this with a fresh installed firmware that hasn't been booted yet I downloaded the firmware/ROM from here: https://mirrors.lolinet.com/firmware/moto/ocean/official/RETUS/ here is a list of commands to copy and paste into command prompt please make sure your device is in bootloader/ fastboot mode.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
IM a bit confused should I flash a fresh installed firmware first right after i unlock the boot loader?
Also I found it best to do this with a fresh installed firmware that hasn't been booted yet I downloaded the firmware/ROM from here: https://mirrors.lolinet.com/firmware/moto/ocean/official/RETUS/ here is a list of commands to copy and paste into command prompt please make sure your device is in bootloader/ fastboot mode.
[Redacted]
Excellent guide, rooted my Moto G7 from Metro PCS.
brokenlocked22 said:
same thing as always.. no matter what lol
Click to expand...
Click to collapse
I LOVE IT!!! :good:

Question Qualcom CrashDump Mode After OTA, Magisk Lost Root

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

Categories

Resources