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
Related
So coming from MDA89E, I was not receiving the OTA for MDB08I that others around me had received so I decided to go the old "./flash-all.sh" route. I already had performed "fastboot oem unlock" to change build.prop for the hotspot provisioning flag.
However, there was something wrong with the image-bullhead-mdb08i.zip (correct MD5 of the overall package) or my setup, and I received the message "FAILED (remote: data too large)" on the "fastboot -w update image-bullhead-mdb08i.zip" step.
This lead down to long path of frustration until I ran into this post: http://forum.xda-developers.com/showpost.php?p=57272090&postcount=25
After extracting bullhead-mdb08i.zip and manually formatting/erasing and flashing the files individually, I was able to boot as normal.
This error can also be a result of using an out-of-date fastboot binary. Just an FYI.
ahhh didn't think of that.
Time flies.. It's probably time to update. Thanks
EDIT: I use fastboot/adb on Linux Mint 17 Qiana and the package manager says both android-tools-adb and android-tools-fastboot are up-to-date. So whether or not that is actually the case is to be determined, but my OP regarding this issue occurred on the "latest" version of fastboot available via the package manager.
Ugh, I'm running into this issue and I've updated all my ADB/Fastboot files/binaries. I can't, for the life of me, figure out how to get the system.img to flash properly. I've tried everything using Fastboot commands and it just won't work. I updated all my SDK files and I imagine that it updated my ADB/Fastboot binaries. Not sure how to update the Fastboot binaries manually.
Anyone else still running into this?
sn0warmy said:
Ugh, I'm running into this issue and I've updated all my ADB/Fastboot files/binaries. I can't, for the life of me, figure out how to get the system.img to flash properly. I've tried everything using Fastboot commands and it just won't work. I updated all my SDK files and I imagine that it updated my ADB/Fastboot binaries. Not sure how to update the Fastboot binaries manually.
Anyone else still running into this?
Click to expand...
Click to collapse
Try:
fastboot -S 512M flash system system.img
Sent from my HTC One M9 using Tapatalk
efrant said:
Try:
fastboot -S 512M flash system system.img
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
I ended up getting it to work. I uninstalled all instances of ADB/SDK/Fastboot from my mac, rebooted and reinstalled the full SDK tools again and re-setup ADB. After doing that I was able to flash everything, including system.img with no issues. Looks like I was just missing some fastboot binaries afterall.
efrant said:
Try:
fastboot -S 512M flash system system.img
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
this command does not work. I get this as a response when I run this command.
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048
when i try to flash files individually, I get stuck in erasing recovery, do you know why? I can't go further than that, I haven't disconnect it yet because I'm afraid it gets ****ed.
---------- Post added at 09:58 AM ---------- Previous post was at 09:39 AM ----------
peon1-9 said:
So coming from MDA89E, I was not receiving the OTA for MDB08I that others around me had received so I decided to go the old "./flash-all.sh" route. I already had performed "fastboot oem unlock" to change build.prop for the hotspot provisioning flag.
However, there was something wrong with the image-bullhead-mdb08i.zip (correct MD5 of the overall package) or my setup, and I received the message "FAILED (remote: data too large)" on the "fastboot -w update image-bullhead-mdb08i.zip" step.
This lead down to long path of frustration until I ran into this post: http://forum.xda-developers.com/showpost.php?p=57272090&postcount=25
After extracting bullhead-mdb08i.zip and manually formatting/erasing and flashing the files individually, I was able to boot as normal.
Click to expand...
Click to collapse
I did this, it has shown everything ok, from flashing system and rebooting but I am stuck in Google logo now. I flashed bullhead-mtc20k-factory-4a950470, do I have to wait for it to boot or I'll have to heat the processor now?
---------- Post added at 10:00 AM ---------- Previous post was at 09:58 AM ----------
ferdeenandxda said:
when i try to flash files individually, I get stuck in erasing recovery, do you know why? I can't go further than that, I haven't disconnect it yet because I'm afraid it gets ****ed.
---------- Post added at 09:58 AM ---------- Previous post was at 09:39 AM ----------
I did this, it has shown everything ok, from flashing system and rebooting but I am stuck in Google logo now. I flashed bullhead-mtc20k-factory-4a950470, do I have to wait for it to boot or I'll have to heat the processor now?
Click to expand...
Click to collapse
It has rebooted 2 times already i think it didn't work.
efrant said:
Try:
fastboot -S 512M flash system system.img
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
I can't reflash htc desire 700 even with the -S option. It shows the same error (data too large) also in RUU mode. I found the firmware on Hardreset.info in their htc firmware database. If you need firmware, then no problem, though I'm without a computer now, but from my iPhone. I did not download the firmware there (and I'm too lazy to wait for the download, for a long time). Please, help!
Hi everyone ! (I apologyze for my english)
I cant flash anything on my Pixel C because of this:
C:\Users\ykant\Desktop\Minimal ADB and Fastboot>fastboot flash recovery TWRP_dragon_3.0.2-23.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
FAILED (remote: unsupported command)
finished. total time: -0.000s
Click to expand...
Click to collapse
No system to boot on and my TWRP is wiped !!
--> Cant do this:
fwtool vbnv write dev_boot_fastboot_full_cap 1
Click to expand...
Click to collapse
Is my pixel C bricked now ?
regards !
Did you unlock your device first with "fastboot oem unlock"?
redukt said:
Did you unlock your device first with "fastboot oem unlock"?
Click to expand...
Click to collapse
Yes i did this before, i was running on Remix OS
I don't know if this is of relevance but there were new fastboot commands introduced from Android M (?) and I have recollection about "partial unlock" - two flags required to be set and if only one was set it could be reported that the bootloader was unlocked but fastboot saw it as locked. Above may be totally wrong.
Here's the difference between old and current fastboot commands. Note the new lock/unlock commands
Code:
************************ OLD **************************************
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
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
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
************************ NEW **************************************
C:\Program Files (x86)\Android\android-sdk\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.
-Yazh- said:
Hi everyone ! (I apologyze for my english)
I cant flash anything on my Pixel C because of this:
C:\Users\ykant\Desktop\Minimal ADB and Fastboot>fastboot flash recovery TWRP_dragon_3.0.2-23.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
FAILED (remote: unsupported command)
finished. total time: -0.000s
Click to expand...
Click to collapse
No system to boot on and my TWRP is wiped !!
--> Cant do this:
fwtool vbnv write dev_boot_fastboot_full_cap 1
Click to expand...
Click to collapse
Is my pixel C bricked now ?
regards !
Click to expand...
Click to collapse
Hi, I'm just wondering if you were able to fix your tablet. I ran into the same problem as you here and am not able to find a solution to it.
Hi !!
Sorry for bad news, but i didn't found any solution since my Pixel C was bricked. Maybe there is a solution, but I dropped it before finding it.
I hope you find something to fix it !
@viii_xvi Are you using "Minimal ADB and Fastboot" as shown in the post you quoted by -Yazh- ? The current (?) version that I can find is 1.4.3 and that looks to be "2015".
For the current versions of adb and fastboot and the revision history, 12 since October 2016, see https://developer.android.com/studio/releases/platform-tools.html
peterk-1 said:
Are you using "Minimal ADB and Fastboot" as shown in the post you quoted by -Yazh- ? The current (?) version that I can find is 1.4.3 and that looks to be "2015".
Click to expand...
Click to collapse
No. I used the 15 second ADB and Fastboot installer. I'm pretty sure it works fine as I can use fastboot commands.
peterk-1 said:
For the current versions of adb and fastboot and the revision history, 12 since October 2016, see https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
I don't really know what to do with the files found in the zip. If I'm doing it wrong, can you tell me what I should be doing?
viii_xvi said:
No. I used the 15 second ADB and Fastboot installer. I'm pretty sure it works fine as I can use fastboot commands.
I don't really know what to do with the files found in the zip. If I'm doing it wrong, can you tell me what I should be doing?
Click to expand...
Click to collapse
There are Youtube videos on installing Android Platform Tools and a web search for installing Android Platform Tools with your o/s will find many hits. You need to know you are installing just the platform tools - some of the guides assume you are installing or have installed the full Android Software Development Kit (SDK).
Assuming you are using Windows then the simplest method is to copy the contents of the zip file into the current location of your "15 second" files. This ensures that you can run the new version of fastboot with the folder path you have used previously. In file manager "find" fastboot.exe and that will give you the folder to unzip ALL of the platform tools files. You will know if you have done it correctly if you get requests to overwrite existing files when you unzip the files.
peterk-1 said:
There are Youtube videos on installing Android Platform Tools and a web search for installing Android Platform Tools with your o/s will find many hits. You need to know you are installing just the platform tools - some of the guides assume you are installing or have installed the full Android Software Development Kit (SDK).
Assuming you are using Windows then the simplest method is to copy the contents of the zip file into the current location of your "15 second" files. This ensures that you can run the new version of fastboot with the folder path you have used previously. In file manager "find" fastboot.exe and that will give you the folder to unzip ALL of the platform tools files. You will know if you have done it correctly if you get requests to overwrite existing files when you unzip the files.
Click to expand...
Click to collapse
I've followed the instructions so I'm confident I did it correctly. Despite this, nothing has improved. I still can't flash the stock ROM or a custom recovery in fastboot.
What I've noticed from updating the fastboot version are some new commands I found when I entered "fastboot -h"
Code:
fastboot -h
commands:
reboot [bootloader|emergency]
stage <infile>
get_staged <outfile>
options:
--skip-secondary
--skip-reboot
--disable-verity
--disable-verification
--unbuffered
--version
From what I've tried, all the commands in options returns
fastboot: usage: no command
Click to expand...
Click to collapse
viii_xvi said:
I've followed the instructions so I'm confident I did it correctly. Despite this, nothing has improved. I still can't flash the stock ROM or a custom recovery in fastboot.
What I've noticed from updating the fastboot version are some new commands I found when I entered "fastboot -h"
Code:
fastboot -h
commands:
reboot [bootloader|emergency]
stage <infile>
get_staged <outfile>
options:
--skip-secondary
--skip-reboot
--disable-verity
--disable-verification
--unbuffered
--version
From what I've tried, all the commands in options returns
Click to expand...
Click to collapse
Hi, Did you tried to flash with the oldest stock rom of the pixel C ? Because it uses older version of fastboot so maybe it will work. I has also the same problem as you but hopefully twrp still worked so i could flash another system image.
rhmanoa said:
Hi, Did you tried to flash with the oldest stock rom of the pixel C ? Because it uses older version of fastboot so maybe it will work. I has also the same problem as you but hopefully twrp still worked so i could flash another system image.
Click to expand...
Click to collapse
I have now tried to flash the earliest factory image and am disappointed to say the bootloader did not flash and so I wasn't able to complete the flashing.
I don't think the problem is the fastboot version. It may be the bootloader itself. I've read someone describe this problem as "Broken fastboot (bootloader) security." I think the problem is that, when unlocked, the bootloader would return the same messages as if it was locked. The security of the bootloader still thinks it's locked and not allow flashing of any images. Also that locking and reunlocking does not improve the situation. This would explain why, when bootloader is unlocked, I get "remote: unsupported command" and "remote: image verification failed", the same as when I try the same commands when the bootloader is locked.
viii_xvi said:
I have now tried to flash the earliest factory image and am disappointed to say the bootloader did not flash and so I wasn't able to complete the flashing.
I don't think the problem is the fastboot version. It may be the bootloader itself. I've read someone describe this problem as "Broken fastboot (bootloader) security." I think the problem is that, when unlocked, the bootloader would return the same messages as if it was locked. The security of the bootloader still thinks it's locked and not allow flashing of any images. Also that locking and reunlocking does not improve the situation. This would explain why, when bootloader is unlocked, I get "remote: unsupported command" and "remote: image verification failed", the same as when I try the same commands when the bootloader is locked.
Click to expand...
Click to collapse
Just bought today, same issue, have you solved it?
mansonstein said:
Just bought today, same issue, have you solved it?
Click to expand...
Click to collapse
No, I didn't manage to fix it.
did you found a solution yet?
I got a same problem,cant flash anything but ordinary using.
I got the problem caused by flashed twrp3.2.3,cant get into system,just always get into twrp.
cant flash any official firmware with "flash-all.bat",no matter which platform tool or firmware.but the twrp were installed before can flash anything.
finally,I flashed newest OTA firmware,then device can be booted. but got the unsupported command
richardwia said:
did you found a solution yet?
I got a same problem,cant flash anything but ordinary using.
I got the problem caused by flashed twrp3.2.3,cant get into system,just always get into twrp.
cant flash any official firmware with "flash-all.bat",no matter which platform tool or firmware.but the twrp were installed before can flash anything.
finally,I flashed newest OTA firmware,then device can be booted. but got the unsupported command
Click to expand...
Click to collapse
I'm assuming you have the latest version of TWRP installed. IIRC, there should be "Fix Fastboot" in advanced options. If indeed you have the same problem I had, pressing this should fix the problem. I don't know anything beyond this as I never got to find out what happens afterwards.
viii_xvi said:
I'm assuming you have the latest version of TWRP installed. IIRC, there should be "Fix Fastboot" in advanced options. If indeed you have the same problem I had, pressing this should fix the problem. I don't know anything beyond this as I never got to find out what happens afterwards.
Click to expand...
Click to collapse
really?where I can find the“fix fastboot in advanced options”?
richardwia said:
really?where I can find the“fix fastboot in advanced options”?
Click to expand...
Click to collapse
I believe I'm not qualified to help you as I disposed of my tablet months ago. All the advice I've given is off of memory and may not be accurate. That being said, I won't help you anymore in fear of giving inaccurate information that may lead to bricking of your tablet.
I have a pixel C, flashed with latest 3-rd pixel experience before, someday i tried to flash back to factory image, hit the same trouble like this topic, i came here several times before, no solution, today, i found another article about this , it's solved my trouble.
sorry i am new here, i couldn't share the outside article link.
would like to share what i did on my pixel c.
1. root your pixel c
2. adb shell //this command could be executed under recovery mode too.
3. su
4. fwtool vbnv write dev_boot_fastboot_full_cap 1
5. adb reboot fastboot
then you could flash anything you want.
I had this just now - I finally got fed up of my Pixel C being so laggy and also chrome opening up as blank pages (I switched to brace to fix this, but it's abit crashy).
Anyhow I found that after
adb reboot bootloader
that
fastboot flash recovery twrp.img
was failing for me in the "Writing" stage
I discovered that the fix was to use
adb flashing unlock
then it will ask you a question (power button to confirm and one of teh volume keys to cancel).
after this it spins with erasing for a while and then comes back to fastboot after which
fastboot flash recovery twrp.img
Worked, after this you get an annoying 30s delay for each restart, I think that can be fixed by
adb flashing lock
I'll verify this when I've finished flashing a usable ROM to my Pixel C...
Been searching here and Google. No luck.
Do we have a decent list of all the fastboot commands, especially all the ones that pertain to dual partitions?
I want to switch the active partition to make sure all is OK on that side.
@TonikJDK,
This is the only thing I've seen > https://forum.xda-developers.com/pixel-xl/how-to/pixel-xl-fastboot-commands-t3490080
TonikJDK said:
Been searching here and Google. No luck.
Do we have a decent list of all the fastboot commands, especially all the ones that pertain to dual partitions?
I want to switch the active partition to make sure all is OK on that side.
Click to expand...
Click to collapse
If you just type "fastboot" without any switch, you'd get a complete list of switches, right? Then it's really easy to output that to a text file. I'll get one for you shortly.
For now, to answer your end question, you can use "fastboot --set-active=_a" (or _b). It's ten times faster than going through twrp, providing you have access to a PC.
Got it, thanks gang. I looked at the fastboot output and that link before posting. Never saw set_active. Think I will have some more coffee before I dig into why my other slot bootloops.
TonikJDK said:
Been searching here and Google. No luck.
Do we have a decent list of all the fastboot commands, especially all the ones that pertain to dual partitions?
I want to switch the active partition to make sure all is OK on that side.
Click to expand...
Click to collapse
This copy and paste is lousy since it screws up spacing, so I attached the syntax list here.
View attachment 3991598
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>[ort] 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.
TonikJDK said:
Got it, thanks gang. I looked at the fastboot output and that link before posting. Never saw set_active. Think I will have some more coffee before I dig into why my other slot bootloops.
Click to expand...
Click to collapse
If you can't use the set_active or --set-active switch, you don't have the latest adb/fastboot binary from Android SDK. Besides the --set-active parameter, the more important one is 'slot' with which you can establish where to flash. You can issue "fastboot --ver" and check the version number. It should start with a '3'.
quangtran1 said:
If you don't see the set_active or --set-active switch, you don't have the latest adb/fastboot binary from Android SDK. Besides the --set-active parameter, the more important one is 'slot' with which you can establish where to flash. You can issue "fastboot --ver" and check the version number. It should start with a '3'.
Click to expand...
Click to collapse
I'm good, got it. This entire thread is due to my poor reading comprehension today.
TonikJDK said:
I'm good, got it. This entire thread is due to my poor reading comprehension today.
Click to expand...
Click to collapse
Read? Who's got time for that?
quangtran1 said:
Read? Who's got time for that?
Click to expand...
Click to collapse
Yea, no time to read cuz I'm too busy posting about what I should have read.
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.
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: