Database Users

Bootloop and can't fastboot flash image

I've been having issues with my Nexus 7. The first time it was stuck in a boot loop not making it past the Google logo. I booted into the bootloader, flashed a new factory image, and I was off.
Then a few weeks later the same thing happened. Only this time, I can't get a factory image to flash. Any ideas?
I think my flash memory is gone bad.

carlowahlstedt said:
I've been having issues with my Nexus 7. The first time it was stuck in a boot loop not making it past the Google logo. I booted into the bootloader, flashed a new factory image, and I was off.
Then a few weeks later the same thing happened. Only this time, I can't get a factory image to flash. Any ideas?
I think my flash memory is gone bad.
Click to expand...
Click to collapse
Possibly... or possibly not.
Hi, carlowahlstedt...
carlowahlstedt said:
...Only this time, I can't get a factory image to flash...
Click to expand...
Click to collapse
It might be helpful if you could be more specific... like, what errors did you encounter?... how did you go about flashing a factory image?... did you use a toolkit, like Wugs?... or just regular fastboot?
For somebody to assist you in diagnosing a given problem, in the hope of fixing it... they need all the facts available... no matter how seemingly innocuous or irrelevant.
The 'devil', as it is said, resides very much in the 'detail'.
Rgrds,
Ged.

Thanks Ged. I guess I was kinda hoping for a tool that could some how test the memory.
Here's the output from the toolkit:
********************************************************************************
* Universal Nexus Linux Toolkit v2.4.2 by tatelucas *
********************************************************************************
Flash Google Factory Image
Before starting the process your device must be in Bootloader Mode.
In the following instructions you will learn how to do it:
1. Power off the device.
2. Press and hold Volume Down, then press and hold Power.
3. Your device screen should show an image of an opened android.
You're now in the Bootloader Mode! If you don't see the image,
you must follow the instructions again.
4. Please connect the device to your PC via USB.
5. Do you want to start the process? [Y/N]: Y
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.020s
erasing 'boot'...
OKAY [ 0.015s]
finished. total time: 0.015s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.015s]
finished. total time: 0.015s
erasing 'recovery'...
OKAY [ 0.015s]
finished. total time: 0.015s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.015s]
finished. total time: 0.015s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.019s]
finished. total time: 0.019s
sending 'bootloader' (2100 KB)...
OKAY [ 0.276s]
writing 'bootloader'...
FAILED (remote: (FileWriteFailed))
finished. total time: 2.247s
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
rebooting into bootloader...​
You'll notice that it doesn't have anything past the "rebooting into bootloader". The screen is locked up on the device and nothing is happening. After sometime I manually reboot into bootloader and get:
ERROR: usb_write failed with status e00002ed
FAILED (command write failed (No such file or directory))
finished. total time: 174.893s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 0## (removed this)
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.020s]
sending 'boot' (4990 KB)...
OKAY [ 0.682s]
writing 'boot'...
FAILED (remote: (AccessDenied))
finished. total time: 2.378s​
I also seems to have lost recovery mode? If I click on Recovery Mode in the bootloader it just flashes the text and that's it.
Not sure what else would be helpful to see/know. Thanks for the help.

Google search
android factory images
Grab the latest for your device
Extract all
fastboot flash bootloader nameofbootloader.img
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now either click the flashall.bat or, as I would recommend, do it manually
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash data userdata.img
fastboot flash recovery recovery.img
(Feel free to use twrp or cwm if you don't want stock)
Now reboot
Side note, stay away from toolkits whenever possible
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
Google search
android factory images
Grab the latest for your device
Extract all
fastboot flash bootloader nameofbootloader.img
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now either click the flashall.bat or, as I would recommend, do it manually
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash data userdata.img
fastboot flash recovery recovery.img
(Feel free to use twrp or cwm if you don't want stock)
Now reboot
Side note, stay away from toolkits whenever possible
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the help. I downloaded the latest image for the Nexus 7 Wifi (NOT 2013) and attempted to flash the bootloader but I get this:
sending 'bootloader' (2100 KB)...
OKAY [ 0.333s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.466s​
I found this thread, which I took to mean to download the bootloader from the 4.3 image. I did that but get the same result.
Also, it shows that I already have 4.23 so it seems like I wouldn't need to flash this in the first place?
Thanks again for the help.

Then skip the bootloader but do the rest of the steps
And you are just using fastboot right? No toolkits
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
Then skip the bootloader but do the rest of the steps
And you are just using fastboot right? No toolkits
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope, no toolkits.
Looks like the erase system command is having issues writing as well. Included the reference to the command so you could see that as well:
platform-tools carlo.wahlstedt$ ./fastboot erase system -w
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.015s]
erasing 'userdata'...
OKAY [ 0.024s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 6453985280
Block size: 4096
Blocks per group: 32768
Inodes per group: 8048
Inode size: 256
Journal blocks: 24620
Label:
Blocks: 1575680
Block groups: 49
Reserved block group size: 391
Created filesystem with 11/394352 inodes and 52512/1575680 blocks
sending 'userdata' (102525 KB)...
writing 'userdata'...
FAILED (remote: (FileWriteFailed))
finished. total time: 81.408s​

Looks like data partition is corrupt, hopefully fixable but you will need adb shell. So continue on with the steps above and hopefully you can get into either recovery or os, then you can use dd or fsck or something to format, well hopefully so long as it is not too corrupt
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
Looks like data partition is corrupt, hopefully fixable but you will need adb shell. So continue on with the steps above and hopefully you can get into either recovery or os, then you can use dd or fsck or something to format, well hopefully so long as it is not too corrupt
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't think it's looking good:
platform-tools carlo.wahlstedt$ ./fastboot erase boot
erasing 'boot'...
OKAY [ 0.015s]
finished. total time: 0.015s
platform-tools carlo.wahlstedt$ ./fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.015s]
finished. total time: 0.015s
platform-tools carlo.wahlstedt$ ./fastboot flash system nakasi-kot49h/image-nakasi-kot49h/system.img
erasing 'system'...
OKAY [ 0.011s]
sending 'system' (625382 KB)...
OKAY [ 86.819s]
writing 'system'...
FAILED (remote: (FileWriteFailed))
finished. total time: 152.721s
platform-tools carlo.wahlstedt$ ./fastboot flash boot nakasi-kot49h/image-nakasi-kot49h/boot.img
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
^C (I forced a reboot here after waiting a long time)
platform-tools carlo.wahlstedt$ ./fastboot flash boot nakasi-kot49h/image-nakasi-kot49h/boot.img
sending 'boot' (4992 KB)...
OKAY [ 0.818s]
writing 'boot'...
FAILED (remote: (FileWriteFailed))
finished. total time: 2.374s
platform-tools carlo.wahlstedt$ ./fastboot flash data nakasi-kot49h/image-nakasi-kot49h/userdata.img
sending 'data' (104289 KB)...
OKAY [ 14.212s]
writing 'data'...
FAILED (remote: Invalid Partition Name.)
finished. total time: 14.227s
platform-tools carlo.wahlstedt$ ./fastboot flash recovery nakasi-kot49h/image-nakasi-kot49h/recovery.img
sending 'recovery' (5532 KB)...
OKAY [ 0.893s]
writing 'recovery'...
FAILED (remote: (FileWriteFailed))
finished. total time: 2.448s
platform-tools carlo.wahlstedt$ ./fastboot reboot
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
rebooting... (I forced a reboot here)
ERROR: usb_write failed with status e00002ed
finished. total time: 106.130s​
It's also "locking up" on most every command that I send. By that I mean, you can't move through the bootloader menu.
Any other thoughts?

Sorry to say but I feel your nand is fried... If you still have warranty you should claim it but as of now I would give it 50/50 that even JTAG would work to resurrect you tab
Sorry for the bad news, best of luck
Sent from my Nexus 7 using XDA Premium 4 mobile app

Well that sucks. Thanks for the help.

[Q] writing 'bootloader'... FAILED (remote: (Unknown error code))

My N7 "2012" kept freezing, so I put it in bootloader and tried to do a recovery mode reset to stock. It froze during the process.
Now, the only thing I can do is get it into bootloader mode manually by holding the buttons. It frezes if I choose any of the options from the bootloader screen including restarting the bootloader from the bootloader screen without holding power and volume.
I have tried the Nexus Root Toolkit a bunch of times with the "flash stock + unroot (soft bricked)" feature, testing different factory builds and the best results are below:
Flash Stock + Unroot...
------------------------------------------------------------------
erasing 'boot'...
OKAY [ 2.526s]
finished. total time: 2.526s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.200s]
finished. total time: 0.200s
erasing 'recovery'...
OKAY [ 0.016s]
finished. total time: 0.016s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.015s]
finished. total time: 0.015s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.015s]
finished. total time: 0.015s
sending 'bootloader' (2100 KB)...
OKAY [ 0.264s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 0.402s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.021s
< waiting for device >​
PLEASE HELP! Keep in mind that I am a newb to messing with this stuff.
I have read forums and tried things that people suggested to others in similar situations, but I am pretty lost at this point. Keep in mind that my device is almost certainly wiped and definitely will not boot the OS.

Is your N7 the Wi-Fi or the 3G variant?
What was the name of the factory image you were trying to flash?

brad3626 said:
My N7 "2012" kept freezing, so I put it in bootloader and tried to do a recovery mode reset to stock. It froze during the process.
Now, the only thing I can do is get it into bootloader mode manually by holding the buttons. It frezes if I choose any of the options from the bootloader screen including restarting the bootloader from the bootloader screen without holding power and volume.
I have tried the Nexus Root Toolkit a bunch of times with the "flash stock + unroot (soft bricked)" feature, testing different factory builds and the best results are below:
PLEASE HELP! Keep in mind that I am a newb to messing with this stuff.
I have read forums and tried things that people suggested to others in similar situations, but I am pretty lost at this point. Keep in mind that my device is almost certainly wiped and definitely will not boot the OS.
Click to expand...
Click to collapse
After doing a bit of research, I've found out that there is a BAD version of the N7 2012 bootloader 4.23 floating around. The unsettling thing is that it's being supplied with a couple of the factory images that come straight from from the Google android devolpers page online. Anyway to make a long story short, I would try flashing the working version of the bootloader first off, then go from there with a factory reset. You can download the the working bootloader (bootloader-grouper-4.23.img) HERE --> h t t p : / / g o o . g l / q A D S A z (sorry about the spaces in the url, I'm new to the forum and can't post links yet, just delete the spaces)
BTW, its the same bootloader for N7 wifi OR 3G. md5 = df53028033c9eccf4fe5ba7bc198ce24
Here's how to install using fastboot:
1. Reboot To Your Bootloader On You Nexus 7 (Power off power button and volume down until you see bootloader screen)
2. Connect Your Nexus 7 To Your Computer
3. Open Up Command Prompt or terminal window (not sure if you are using windows/mac/linux)
4. CD to where you downloaded bootloader-grouper-4.23.img
5. Then type:
fastboot devices (to see if your N7 is connected correctly)
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
Then try the factory reset again.
If you don't have fastboot installed your computer you need it. Makes flashing your N7 a breeze... lock/unlock, custom recovery installs, going back to factory stock, all much more easy with fastboot.
You can get it from the android devolper site, h t t p : / / g o o . g l / 2 q p r for windows/mac/linux. All you need is the SDK tools, not the ADT bundle.

adomol said:
After doing a bit of research, I've found out that there is a BAD version of the N7 2012 bootloader 4.23 floating around. The unsettling thing is that it's being supplied with a couple of the factory images that come straight from from the Google android devolpers page online. Anyway to make a long story short, I would try flashing the working version of the bootloader first off, then go from there with a factory reset. You can download the the working bootloader (bootloader-grouper-4.23.img) HERE --> h t t p : / / g o o . g l / q A D S A z (sorry about the spaces in the url, I'm new to the forum and can't post links yet, just delete the spaces)
BTW, its the same bootloader for N7 wifi OR 3G. md5 = df53028033c9eccf4fe5ba7bc198ce24
Here's how to install using fastboot:
1. Reboot To Your Bootloader On You Nexus 7 (Power off power button and volume down until you see bootloader screen)
2. Connect Your Nexus 7 To Your Computer
3. Open Up Command Prompt or terminal window (not sure if you are using windows/mac/linux)
4. CD to where you downloaded bootloader-grouper-4.23.img
5. Then type:
fastboot devices (to see if your N7 is connected correctly)
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
Then try the factory reset again.
If you don't have fastboot installed your computer you need it. Makes flashing your N7 a breeze... lock/unlock, custom recovery installs, going back to factory stock, all much more easy with fastboot.
You can get it from the android devolper site, h t t p : / / g o o . g l / 2 q p r for windows/mac/linux. All you need is the SDK tools, not the ADT bundle.
Click to expand...
Click to collapse
Thank you for the help, unfortunately, it did not work.
I followed the instructions above, but the Nexus displayed "neither up nor cac partitions found" over and over
While cmd displayed:
C:\Users\Brad>fastboot devices
XXX fastboot
C:\Users\Brad>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.281s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 3.213s
C:\Users\Brad>fastboot devices
XXX fastboot
C:\Users\Brad>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.271s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 3.205s​

Erovia said:
Is your N7 the Wi-Fi or the 3G variant?
What was the name of the factory image you were trying to flash?
Click to expand...
Click to collapse
Wi-Fi
I have tried every one that the NRT offered.

Just read this guide and download the latest factory image from here.
Good luck.

Erovia said:
Just read this guide and download the latest factory image from here.
Good luck.
Click to expand...
Click to collapse
I read that guide.
But that guide seems to be written with the assumption that the device can boot into the OS
No ADB device is found because I can only boot into bootloader.

That part is only for the driver installation. You can skip to the "Extract the Factory Image" part and follow it from there.

Erovia said:
That part is only for the driver installation. You can skip to the "Extract the Factory Image" part and follow it from there.
Click to expand...
Click to collapse
Following from "Extract the Factory Image" part, this is what I am getting:
C:\Users\Brad>cd \Users\brad\AppData\Local\Android\android-sdk\platform-tools
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot devices
XXX fastboot
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>adb reboot-bootlo
ader
error: device not found
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot oem unlo
ck
...
FAILED (command write failed (Unknown error))
finished. total time: 0.590s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase bo
ot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase ca
che
erasing 'cache'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase re
covery
erasing 'recovery'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.022s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase sy
stem
erasing 'system'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase us
erdata
erasing 'userdata'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.018s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot flash bo
otloader bootloader-grouper-4.23.img
error: cannot load 'bootloader-grouper-4.23.img': Invalid argument​

On the bootloader screen is your bootloader shown as "locked" or "unlocked" ?

Erovia said:
On the bootloader screen is your bootloader shown as "locked" or "unlocked" ?
Click to expand...
Click to collapse
lock state - unlocked

What's the output of fastboot -w update image-nakasi-kot49h.zip ?

Erovia said:
What's the output of fastboot -w update image-nakasi-kot49h.zip ?
Click to expand...
Click to collapse
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot -w updat
e image-nakasi-kot49h.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
error: out of memory​

I have no idea what this "out of memory" error is. If I were you I would restart my computer, run fastboot from a cmd opened as Admin and try out different usb ports.

Erovia said:
I have no idea what this "out of memory" error is. If I were you I would restart my computer, run fastboot from a cmd opened as Admin and try out different usb ports.
Click to expand...
Click to collapse
I restarted, ran cmd as admin and tried every USB port and got this as the result each time:
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot -w updat
e image-nakasi-kot49h.zip
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: XXX
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
sending 'boot' (4992 KB)...
OKAY [ 5.460s]
writing 'boot'...
FAILED (remote: (FileWriteFailed))
finished. total time: 8.518s​
The Nexus was frozen at this point and had to be manually forced to restart bootloader.

Do you have a valid warranty for the N7? I'm asking because it seems that your N7's internal memory got corrupted. I might not be right, but that's my best guess.

Erovia said:
Do you have a valid warranty for the N7? I'm asking because it seems that your N7's internal memory got corrupted. I might not be right, but that's my best guess.
Click to expand...
Click to collapse
Thanks for your help
I bought it 13 months ago (perfect timing, coincidentally, right?), so if I could find the receipt I would still be screwed.

I would still try to send it to Asus or Google. Maybe they repair it for a reasonable price.
(But if you plan to do that try to relock you bootloader with fastboot oem lock)

Erovia said:
I would still try to send it to Asus or Google. Maybe they repair it for a reasonable price.
(But if you plan to do that try to relock you bootloader with fastboot oem lock)
Click to expand...
Click to collapse
fastboot oem lock
...
(bootloader) Bootloader is locked now.
OKAY [ 36.032s]
finished. total time: 36.032s​
But then the N7 freezes and after manually restarting in bootloader it is still unlocked.

Then send is as it is. You can't do any more about it.
Good luck.

[Guide] Updating your Pixel 2 to latest factory image, no wipe

Note: This is NOT A FIX FOR SOFTBRICKED DEVICES. This is simply an easy way for someone who is rooted to easily update /system to the most recent build without erasing user data.
Please note this is not a clean factory flash - this does not flash radio or bootloader, and does not wipe /data. This works regardless of whether you have a custom kernel or unlocked bootloader.
This assumes that you already know how to use ADB and fastboot.
1. Download the latest factory image for your device from HERE.
2. Unzip the archive.
3. Open the folder it was unzipped to, and you will find an archive titled "image-[device]-[build number].zip. Copy this to your ADB/fastboot folder.
4. Connect your phone and reboot to bootloader.
5. Type:
Code:
fastboot update [name of image].zip
6. Wait for the process to finish. Phone will automatically reboot into system when complete.
Congratulations, you are now on the latest factory system image. This overwrites boot, dtbo, and breaks root, so reflash kernels and Magisk as desired. Be aware that the kernel you are flashing must match the security update you flashed.
If for whatever reason you do want to wipe /data when flashing this, use:
Code:
fastboot -w update [name of image].zip
If you want to update your radio, simply pull the radio.img from the factory zip, and while in bootloader, type:
Code:
fastboot flash radio [name of radio image].img
After you flash bootloader and radio, make sure you use
Code:
fastboot reboot bootloader
to ensure you're on the new firmware.

I'm getting the following, any advice? I definitely dont want to wipe, and suspect flashing a bootloader image will do that?
:
:\adb> fastboot update image.zip
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
--------------------------------------------
Bootloader Version...: mw8998-002.0066.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: XXXXXX
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
FAILED
Device version-bootloader is 'mw8998-002.0066.00'.
Update requires 'mw8998-002.0067.00.

mjondj said:
I'm getting the following, any advice? I definitely dont want to wipe, and suspect flashing a bootloader image will do that?
:
:\adb> fastboot update image.zip
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
--------------------------------------------
Bootloader Version...: mw8998-002.0066.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: XXXXXX
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
FAILED
Device version-bootloader is 'mw8998-002.0066.00'.
Update requires 'mw8998-002.0067.00.
Click to expand...
Click to collapse
Sounds like you've been without OTAs for a while.
Pull the bootloader and radio images from the .021 zip. They will be right there in the same folder as image-walleye-opm1.171019.021.zip.
Copy to fastboot folder
Code:
fastboot flash bootloader bootloader-walleye-mw8998-002.0067.00.img
fastboot reboot bootloader
fastboot flash radio radio-walleye-g8998-00164-1710262031.img
fastboot reboot bootloader
fastboot update image-walleye-opm1.171019.021.zip

socal87 said:
Pull the bootloader image from the .021 zip. It'll be right there in the same folder as image-walleye-opm1.171019.021.zip.
Copy to fastboot folder
Code:
fastboot flash bootloader bootloader-walleye-mw8998-002.0067.00.img
fastboot reboot bootloader
fastboot update image-walleye-opm1.171019.021.zip
Click to expand...
Click to collapse
---------- Post added at 04:22 PM ---------- Previous post was at 04:21 PM ----------
flashing all those won't wipe the device?

mjondj said:
Pull the bootloader image from the .021 zip. It'll be right there in the same folder as image-walleye-opm1.171019.021.zip.
Copy to fastboot folder
---------- Post added at 04:22 PM ---------- Previous post was at 04:21 PM ----------
flashing all those won't wipe the device?
Click to expand...
Click to collapse
No. Flashing without the -w flag does not wipe. Refer to bottom of first post.

socal87 said:
No. Flashing without the -w flag does not wipe. Refer to bottom of first post.
Click to expand...
Click to collapse
i appreciate the help, but now i'm soft bricked (wont go past G logo) after failing on system. i was rooted w/ magisk. i suspect thats what the problem was. is there any way to avoid a wipe at this point and get back up and running?
PS C:\adb> fastboot devices
xxx fastboot
PS C:\adb> fastboot flash bootloader boot.img
target reported max download size of 536870912 bytes
sending 'bootloader' (38652 KB)...
OKAY [ 0.913s]
writing 'bootloader'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
(bootloader) Updating: partition:1 @0000D000 sz=0000B000
(bootloader) Updating: partition:2 @00018000 sz=0000B000
(bootloader) Updating: partition:3 @00023000 sz=0000B000
(bootloader) Updating: partition:4 @0002E000 sz=0000B000
(bootloader) Updating: partition:5 @00039000 sz=0000B000
(bootloader) Updating: cmnlib64 @00044000 sz=00048000
(bootloader) Updating: cmnlib @0008C000 sz=00037000
(bootloader) Updating: devcfg @000C3000 sz=0000F000
(bootloader) Updating: hyp @000D2000 sz=00040000
(bootloader) Updating: keymaster @00112000 sz=00046000
(bootloader) Updating: lockbooter @00158000 sz=00016000
(bootloader) Updating: pmic @0016E000 sz=0000D000
(bootloader) Updating: rpm @0017B000 sz=0003A000
(bootloader) Updating: tz @001B5000 sz=001DB000
(bootloader) Updating: xbl @00390000 sz=003A2000
(bootloader) Updating: apdp @00732000 sz=00004000
(bootloader) Updating: msadp @00736000 sz=00004000
(bootloader) Updating: hosd @0073A000 sz=01E20000
(bootloader) Updating: abl @0255A000 sz=00065000
OKAY [ 0.918s]
finished. total time: 1.840s
PS C:\adb> fastboot reboot bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
PS C:\adb> fastboot flash radio radio.img
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.437s]
writing 'radio'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.552s]
finished. total time: 2.000s
PS C:\adb> fastboot reboot bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
PS C:\adb> fastboot update image.zip
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
--------------------------------------------
Bootloader Version...: mw8998-002.0067.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: xxx
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.002s]
sending 'boot' (32768 KB)...
OKAY [ 0.775s]
writing 'boot'...
OKAY [ 0.002s]
sending sparse 'system' (524284 KB)...
OKAY [ 13.252s]
writing 'system'...
OKAY [ 0.002s]
sending sparse 'system' (524284 KB)...
FAILED (remote: No such partition.)
finished. total time: 14.383s
PS C:\adb>
Click to expand...
Click to collapse

mjondj said:
i appreciate the help, but now i'm soft bricked (wont go past G logo) after failing on system. i was rooted w/ magisk. i suspect thats what the problem was. is there any way to avoid a wipe at this point and get back up and running?
Click to expand...
Click to collapse
A factory reset in recovery will get it up and running again and afterwards you can reroot.

gee2012 said:
A factory reset in recovery will get it up and running again and afterwards you can reroot.
Click to expand...
Click to collapse
this doesnt really help. the whole point is to not wipe

mjondj said:
this doesnt really help. the whole point is to not wipe
Click to expand...
Click to collapse
Don`t think its possible without a wipe, but good luck anyways

gee2012 said:
Don`t think its possible without a wipe, but good luck anyways
Click to expand...
Click to collapse
the title of this thread includes the words "no wipe"

mjondj said:
the title of this thread includes the words "no wipe"
Click to expand...
Click to collapse
No wipe, extenuating cirumstances not withstanding. But I have an idea.
Boot TWRP and use ADB push to send the image.zip to /tmp. Flash using TWRP, see if that works.
Also, check out Deuce's tool here.

mjondj said:
the title of this thread includes the words "no wipe"
Click to expand...
Click to collapse
We know that, but the dude he is trying to help is soft bricked probably by following op instructions which I do t k ow why we have a other thread about anyway.

dobbs3x said:
We know that, but the dude he is trying to help is soft bricked.
Click to expand...
Click to collapse
This method is not a fix for, nor does it address prexisting issues. Everyone is responsible for their own phones. I will help as much as I can but the responsibility lies on the user to be familiar with flashing as well as what to do if something goes wrong.

socal87 said:
This method is not a fix for, nor does it address prexisting issues. Everyone is responsible for their own phones. I will help as much as I can but the responsibility lies on the user to be familiar with flashing as well as what to do if something goes wrong.
Click to expand...
Click to collapse
If you post instructions and someone bricks their phone from it then they are going to come here and post about it.
We already have threads that talk about updating and there was really no need for this one anyway.

dobbs3x said:
If you post instructions and someone bricks their phone from it then they are going to come here and post about it.
We already have threads that talk about updating and there was really no need for this one anyway.
Click to expand...
Click to collapse
My instructions didn't brick his phone. And while there are threads about updating from the factory zip without wiping, this is a manual way to update /system independently. If you feel the thread is unnecessary, let an admin know, and they will decide whether to remove it.
Or, you could simply be thankful that I'm trying to help.

Will this method work for nonrooted devices?

Phil_Chambers said:
Will this method work for nonrooted devices?
Click to expand...
Click to collapse
Yes. This is functionally similar to flashing the factory zip, except you're typing the commands yourself and omitting the -w (wipe) flag.

Issue solved by using this script to flash all the imgs to both slots. up and running in one pass like nothing happened:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

I'm getting this when I try to boot the OTA .zip.
">fastboot update walleye-ota-opm1.171019.021-bb894efa.zip
archive does not contain 'android-info.txt'
error: update package 'walleye-ota-opm1.171019.021-bb894efa.zip' has no android-info.txt"
Not sure what I'm doing wrong
Edit: I had to sideload the update. But worked like a charm

Phil_Chambers said:
I'm getting this when I try to boot the OTA .zip.
">fastboot update walleye-ota-opm1.171019.021-bb894efa.zip
archive does not contain 'android-info.txt'
error: update package 'walleye-ota-opm1.171019.021-bb894efa.zip' has no android-info.txt"
Not sure what I'm doing wrong
Edit: I had to sideload the update. But worked like a charm
Click to expand...
Click to collapse
Interesting. Did you modify the zip in any way?

Trashed my Bootloader, GPT tables corrupt

So after installing xposed and a few other things my phone crashed, and on reboot, I got boot image did not pass verification message or some such. Normally I would just flash stock then twrp and go from there, but it seems that somehow along the way my partition tables got corrupted. I can get into fastboot, but all fastboot commands fail. I tried to reflash the gpt partition and bootloader partitions first as some suggested, but it's not working
Code:
$ fastboot flash partition gpt.bin
Sending 'partition' (45 KB) OKAY [ 0.002s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) Failed to write EFI backup GPT header.
(bootloader) Failed to program partition table
FAILED (remote failure)
Finished. Total time: 0.059s
$ fastboot flash bootloader bootloader.img
Sending 'bootloader' (5115 KB) OKAY [ 0.114s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition aboot
FAILED (remote failure)
Finished. Total time: 0.309s
I also tried blankflash, but I am unsure how to make it work since everytime I connect a USB cable the device starts itself in bootloader/fastboot mode right away, and attempting to blank flash it then just hangs at
Code:
<waiting for device>
Flashing recovery results in
Code:
$ fastboot flash recovery twrp-3.2.3-1-potter.img
Sending 'recovery' (16316 KB) OKAY [ 0.351s]
Writing 'recovery' (bootloader) Image not signed or corrupt
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
Finished. Total time: 0.355s
Any help is appreciated!

Drkmatr1984 said:
So after installing xposed and a few other things my phone crashed, and on reboot, I got boot image did not pass verification message or some such. Normally I would just flash stock then twrp and go from there, but it seems that somehow along the way my partition tables got corrupted. I can get into fastboot, but all fastboot commands fail. I tried to reflash the gpt partition and bootloader partitions first as some suggested, but it's not working
I also tried blankflash, but I am unsure how to make it work since everytime I connect a USB cable the device starts itself in bootloader/fastboot mode right away, and attempting to blank flash it then just hangs at
Flashing recovery results in
Any help is appreciated!
Click to expand...
Click to collapse
Try erasing everything by using ADB codes then flash the latest bootloader and gpt then flash the stock ROM and lock the bootloader,and the flash the whole firmware again,so there will be no partition corrupted.after that you can unlock your bootloader.

Also, make sure to flash the latest stock firmware, being sure not to try and revert to an earlier version. Don't flash blankflash unless you are totally bricked, with just flashing light. Your device will never be the same if you do.

riyan65 said:
Try erasing everything by using ADB codes then flash the latest bootloader and gpt then flash the stock ROM and lock the bootloader,and the flash the whole firmware again,so there will be no partition corrupted.after that you can unlock your bootloader.
Click to expand...
Click to collapse
How do I use ADB if I can't get beyond fastboot? I can't load TWRP or flash TWRP to get into it to access ADB. And ADB commands don't work from the fastboot bootloader screen.
Doing "fastboot erase <partition name>" or "fastboot format:ext4 <partition name>" also fails same as the other fastboot flash commands so I can't erase my partitions from fastboot before re-flashing.

If all fastboot commands fail, including
Code:
fastboot devices
,
Code:
fastboot getvar all
I would uninstall, and reinstall adb/fastboot and all it's drivers. I would also reinstall the moto drivers. Try a different cable, and perhaps even a different pc. If the phone boots to bootloader mode, you should be able to execute those basic commands if it is communicating. If it is communicating, then try flashing the most recent stock firmware. Many gpt errors are from trying to downgrade.

[email protected] said:
If all fastboot commands fail, including
Code:
fastboot devices
,
Code:
fastboot getvar all
I would uninstall, and reinstall adb/fastboot and all it's drivers. I would also reinstall the moto drivers. Try a different cable, and perhaps even a different pc. If the phone boots to bootloader mode, you should be able to execute those basic commands if it is communicating. If it is communicating, then try flashing the most recent stock firmware. Many gpt errors are from trying to downgrade.
Click to expand...
Click to collapse
Ok, after trying 3 different USb cables, including a brand new one I just ordered, and after uninstalling all drivers on pc and rebooting, then reinstalling, I still get these same responses from fastboot devices and fastboot getvar all
Code:
C:\ProgramData\LMSA\Download\RomFiles>fastboot devices
ZY224262W9 fastboot
and
Code:
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.92
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.008s
Any other fastboot commands fail with similar errors. Trying to reflash OPSS28-85-17-2 results in
Code:
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot devices
ZY224262W9 fastboot
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot reboot bootloader
rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.005s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>OREO.BAT
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem fb_mode_set
FAILED (remote failure)
Finished. Total time: 0.003s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
Sending 'partition' (45 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.146s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash bootloader bootloader.i
mg
Sending 'bootloader' (5115 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.009s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash logo logo.bin
Sending 'logo' (2186 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.009s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash boot boot.img
Sending 'boot' (16384 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 6.967s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash recovery recovery.img
Sending 'recovery' (20580 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.009s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash dsp adspso.bin
Sending 'dsp' (16384 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.008s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash oem oem.img
Sending 'oem' (104608 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.012s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.0
Sending 'system' (256553 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.011s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.1
Sending 'system' (256617 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.007s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.2
Sending 'system' (254213 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.006s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.3
Sending 'system' (256710 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.009s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.4
Sending 'system' (256912 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.010s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.5
Sending 'system' (257861 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.009s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.6
Sending 'system' (260027 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.010s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.7
Sending 'system' (257601 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.006s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.8
Sending 'system' (257805 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.010s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash modem NON-HLOS.bin
Sending 'modem' (71921 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.011s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase modemst1
Erasing 'modemst1' FAILED (command write failed
(Unknown error))
Finished. Total time: 5.006s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase modemst2
Erasing 'modemst2' FAILED (command write failed
(Unknown error))
Finished. Total time: 5.006s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash fsg fsg.mbn
Sending 'fsg' (3012 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.011s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase cache
Erasing 'cache' FAILED (command write failed
(Unknown error))
Finished. Total time: 5.008s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase userdata
Erasing 'userdata' FAILED (command write failed
(Unknown error))
Finished. Total time: 34.761s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase customize
Erasing 'customize' FAILED (command write failed
(Unknown error))
Finished. Total time: 14.723s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase clogo
Erasing 'clogo' FAILED (command write failed
(Unknown error))
Finished. Total time: 5.008s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem fb_mode_clear
FAILED (command write failed (Unknown error))
Finished. Total time: 5.003s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot reboot bootloader
rebooting into bootloader FAILED (command write failed
(Unknown error))
Finished. Total time: 5.007s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>
Occasionally I can get a different message
Code:
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash bootloader bootloader.i
mg
Sending 'bootloader' (5115 KB) OKAY [ 0.325s]
Writing 'bootloader' (bootloader) Validating 'boot
loader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
FAILED (status read failed (Too many links))
Finished. Total time: 0.533s
and
Code:
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
Sending 'partition' (45 KB) OKAY [ 0.005s]
Writing 'partition' (bootloader) Validating 'gpt.
default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
Finished. Total time: 0.085s
But it always fails.

Drkmatr1984 said:
If all fastboot commands fail, including ,
Ok, after trying 3 different USb cables, including a brand new one I just ordered, and after uninstalling all drivers on pc and rebooting, then reinstalling, I still get these same responses from fastboot devices and fastboot getvar all
and
Any other fastboot commands fail with similar errors. Trying to reflash OPSS28-85-17-2 results in
Occasionally I can get a different message
and
But it always fails.
Click to expand...
Click to collapse
Why don't you try latest firmware version, as it is having latest bootloader and gpt.
Here is the link for latest version:-https://mirrors.lolinet.com/firmware/moto/potter/official/

riyan65 said:
Why don't you try latest firmware version, as it is having latest bootloader and gpt.
Here is the link for latest version:-https://mirrors.lolinet.com/firmware/moto/potter/official/
Click to expand...
Click to collapse
I am using the latest from lolinet, they do not have the latest (OPSS28.85-13-5) uploaded there yet. I did manage to find a copy here But I am at work on slow internet so it may take me all night to finish downloading it

At least it is communicating, so as riyan65 posted, you need the current firmware. You don't need blankflash, that will screw the pooch big time.

[email protected] said:
At least it is communicating, so as riyan65 posted, you need the current firmware. You don't need blankflash, that will screw the pooch big time.
Click to expand...
Click to collapse
I know, I am not inexperienced with this phone. Normally I would say that getting messages from fastboot at all is good, but the messages I am getting are all saying that my bootloader and gpt tables are write protected currently. I've actually already hard bricked this device once before, and was able to rescue with blank-flash and then flash the stock firmware. This time is different as it's not hard-bricked. I don't understand why I would "need the most recent firmware" as I was never on "the most recent firmware" I should only have to flash the most recent firmware I have had installed on this phone. I never took the december security update so I shouldn't in theory need the firmware he's recommending but Im giving it a shot anyway. I will update my reply when I get a chance to try flashing the december update.
Thanks for your help guys!

Drkmatr1984 said:
I know, I am not inexperienced with this phone. Normally I would say that getting messages from fastboot at all is good, but the messages I am getting are all saying that my bootloader and gpt tables are write protected currently. I've actually already hard bricked this device once before, and was able to rescue with blank-flash and then flash the stock firmware. This time is different as it's not hard-bricked. I don't understand why I would "need the most recent firmware" as I was never on "the most recent firmware" I should only have to flash the most recent firmware I have had installed on this phone. I never took the december security update so I shouldn't in theory need the firmware he's recommending but Im giving it a shot anyway. I will update my reply when I get a chance to try flashing the december update.
Thanks for your help guys!
Click to expand...
Click to collapse
Well, Still no success. The messages do not even change. At least if it was hard bricked I could try blank flash, but right now it's like all of the partitions are write protected, including the gpt tables themselves and the bootloader. Check out the logs here: The only fastboot commands that work are fastboot devices and fastboot reboot. I finally got fastboot getvar all to print more info out though:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.92
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RC14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: xxxxxxxxxx
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 6C657D3F00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Last time flashing failed
(bootloader) imei: xxxxxxxxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 03-28-2017
(bootloader) sku: XT1687
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jan 2 23:25:13 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:7.0/NPN
(bootloader) ro.build.fingerprint[1]: S25.137-33-11/11:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.211.2.potter.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: M8953_41.50.07.85R POTTER_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-ElementalX-G5-3.00
(bootloader) kernel.version[1]: ([email protected]) (gcc version 4.9.4 201506
(bootloader) kernel.version[2]: 29 (prerelease) (crosstool-NG 1.20.0 - L
(bootloader) kernel.version[3]: inaro GCC 2015.06 - Cortex-A15) ) #1 SMP
(bootloader) kernel.version[4]: PREEMPT Mon Oct 1 22:31:26 EDT 2018
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VC0.92-0-g3ea8df0
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier: retus
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Finished. Total time: 0.010s
Is it because the secure boot is on?

You should edit your imei in your getvar output.
When you recovered from hard brick before, did you use Vache's for this device, or the albus blankflash for Addison?
I assume you are trying to get into recovery by using the volume button, but have you tried fastboot commands.
Code:
fastboot reboot recovery
sometimes works.
With a copy of TWRP in your adb/fastboot folder, try
Code:
fastboot boot image twrp.img
or
Code:
fastboot boot recovery twrp.img
where you have renamed your TWRP image to the twrp.img. This boots into twrp without installing, and has been reported to work with fubarred partition tables. If it boots, you then can access tools to repair gpt partition tables via adb.

Drkmatr1984 said:
Well, Still no success. The messages do not even change. At least if it was hard bricked I could try blank flash, but right now it's like all of the partitions are write protected, including the gpt tables themselves and the bootloader. Check out the logs here: The only fastboot commands that work are fastboot devices and fastboot reboot. I finally got fastboot getvar all to print more info out though:
Is it because the secure boot is on?
Click to expand...
Click to collapse
Before posting this kind of information it's better to remove IMEI ans serial number!
The previous message is a little wrong:
- it's possible to boot the recovery without flashing (and very often raccomanded) but the recovery (both original and TWRP) need a working boot partition!
- it' possible also to try to boot a boot.img: if the system it's ok Android can even start!
What is strange to me is the different behaviour in the same situation: it need investigation!

nicolap8 said:
Before posting this kind of information it's better to remove IMEI ans serial number!
The previous message is a little wrong:
- it's possible to boot the recovery without flashing (and very often raccomanded) but the recovery (both original and TWRP) need a working boot partition!
- it' possible also to try to boot a boot.img: if the system it's ok Android can even start!
What is strange to me is the different behaviour in the same situation: it need investigation!
Click to expand...
Click to collapse
Ok, thanks! and done!
I will give these new suggestions a try later tonight. I did hear about booting into TWRP before, but have had little luck with that. However, I think I have only tried fastboot boot twrp.img and not with recovery or image as keywords in there...

OK, so the two fastboot commands are not the correct syntax.
Code:
C:\Users\Hermes\Moto G5 Plus\TWRPs>fastboot boot image twrp.img
fastboot: error: cannot load 'image': No such file or directory
C:\Users\Hermes\Moto G5 Plus\TWRPs>fastboot boot recovery twrp.img
fastboot: error: cannot load 'recovery': No such file or directory
Doing this:
Code:
$ fastboot boot boot.img recovery.img
fastboot: error: cannot boot a boot.img *and* ramdisk
Almost works lol
"fastboot reboot recovery" just gives this:
Code:
C:\Users\Hermes\Moto G5 Plus\TWRPs>fastboot reboot recovery
fastboot: usage: unknown reboot target recovery
C:\Users\Hermes\Moto G5 Plus\TWRPs>fastboot reboot recovery
fastboot: usage: unknown reboot target recovery
Doing "fastboot boot twrp.img" works but it hangs at the "your device is not safe" screen and never actually loads. "fastboot getvar all" returns interesting things in the slot section. Those slots don't seem normal to me. Also, my ro.fingerprint looks like it's for nougat, but my bootloader is Oreo. I'm willing to break this phone to fix it if possible, so if anyone has any riskier suggestions for me to try I'm down as I've already gone 4 days without a phone and am about to buy a new one either way.

Drkmatr1984 said:
OK, so the two fastboot commands are not the correct syntax.
Click to expand...
Click to collapse
If you are not able to get the fastboot help you have not to try to flash anything!

nicolap8 said:
If you are not able to get the fastboot help you have not to try to flash anything!
Click to expand...
Click to collapse
What? I don't understand you.
I am reading this
And am trying to understand the fastboot boot command better. It requires a kernel image and a ramdisk image. So far I have tried by using zImage from ElementalX kernel as kernel and twrp.img as Ramdisk but the boot just hangs for a long time. Does anyone know the Correct command to boot into TWRP(and kernel) from USB on this device? (Confirmed working and tested, please!)
Here are all of my attempts so far:
Code:
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot elex.zImage twrp.img
creating boot image...
creating boot image - 26769408 bytes
Downloading 'boot.img' OKAY [ 0.563s]
booting OKAY [ 0.080s]
Finished. Total time: 0.860s
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot elex.zImage twrp.img
creating boot image...
creating boot image - 26611712 bytes
Downloading 'boot.img' OKAY [ 0.554s]
booting OKAY [ 0.073s]
Finished. Total time: 0.667s
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot linux-2.6/arch/arm/boot/zImage twrp.img
fastboot: error: cannot load 'linux-2.6/arch/arm/boot/zImage': No such file or directory
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot Ele
ElementalX-G5-3.00.zip elex.zImage
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot ElementalX-G5-3.00.zip twrp.img
creating boot image...
creating boot image - 29065216 bytes
Downloading 'boot.img' OKAY [ 0.606s]
booting OKAY [ 0.081s]
Finished. Total time: 0.764s
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot zImage twrp.img
creating boot image...
creating boot image - 23590912 bytes
Downloading 'boot.img' OKAY [ 0.496s]
booting OKAY [ 0.109s]
Finished. Total time: 0.642s
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot zImage
creating boot image...
creating boot image - 6883328 bytes
Downloading 'boot.img' OKAY [ 0.154s]
booting OKAY [ 0.079s]
Finished. Total time: 0.245s

Bump.
No one knows how to boot into TWRP from USB 100% tried and tested on this device?

Drkmatr1984 said:
Bump.
No one knows how to boot into TWRP from USB 100% tried and tested on this device?
Click to expand...
Click to collapse
fastboot boot twrp.img

craigl14 said:
fastboot boot twrp.img
Click to expand...
Click to collapse
That only works when you have a boot partition that is intact.
Since my partition tables are ****ed it just hangs at boot when I run that command. I need the full command with kernel option to make it boot so that I can edit the partitions from TWRP. However, I don't know enough about the kernel of this phone, or where to obtain its sources, or how to compile them, or any of that to make it work. I'm hoping one of the ROM devs will clue me in as I can't be the only person with this phone to ever Fubar their partition tables.
I found this :
Code:
To boot with a host-side kernel image (and rootfs image)
This command allows you to download a kernel image (and optional root filesystem image) and boot the phone with those, instead of using the kernel and rootfs in the boot flash partition. It is very useful while developing a kernel or modifying the rootfs.
fastboot boot <kernel> [ <ramdisk> ]
Ex: fastboot boot linux-2.6/arch/arm/boot/zImage root-image/recovery.img-ramdisk.cpio.gz
Which seems to suggest it's possible but I just need the correct kernel and rootfs image to boot TWRP.

[GUIDE] Flashing Stock Factory img.

This should help you get back to stock. I was stuck in a bootloop after making a change to the System folder and pieced these steps together, I've simplified the guide with some helpful tips from @pbanj and @mac796.
Please use this at your own risk.
This guide assumes you have a phone with an unlocked bootloader and a PC with usb drivers, adb, and fastboot.
I would never recommend downgrading, ie: if you are sporting the Q beta, don't try to go back to Pie.
-[url]https://developers.google.com/android/images#sargo[/URL] is the place you snag your factory image. Sargo is for the 3a, make sure you choose the correct image
-Check the SHA-256 checksum. (It will save you one day)
-Unzip the folder
-Place your phone in fastboot mode (Vol Dwn + Power)
-Connect your phone to your PC
-Open Command Prompt
-Make sure your phone is connected by typing:
Code:
fastboot devices
-Open your recently unzipped file and find the "flash-all.bat". (If you want to preserve internal data, remove the "-w" by editing the batch file)
-Double click "flash-all.bat".
-BE PATIENT. Don't touch it until your command prompt says "Press any key to exit..."
I'm no expert, feel free to PM for changes or recommendations.

You should just be able to run the batch(.bat) file without having to open cmd or changing the directory

Yep just double click the batch file, I would remove the-w first. Only reason you would need to wipe it completely is if you got the corrupt system message. Other than that, I wouldn't wipe internal

This is for people with unlocked bootloader. How about for people on T-Mobile with locked bootloader like myself. Is there anyway I can go back to stock (pie)?

dhoang said:
This is for people with unlocked bootloader. How about for people on T-Mobile with locked bootloader like myself. Is there anyway I can go back to stock (pie)?
Click to expand...
Click to collapse
I assume you are stuck until you are able to unlock the bootloader.

pbanj said:
You should just be able to run the batch(.bat) file without having to open cmd or changing the directory
Click to expand...
Click to collapse
I'll try that if it happens again and update the guide.

Can you unlock the bootloader on the T-Mobile variant of the 3A if it is a purchased device and not financed? Or do I have to unlock the SIM or what..?

Idiyeet said:
Can you unlock the bootloader on the T-Mobile variant of the 3A if it is a purchased device and not financed? Or do I have to unlock the SIM or what..?
Click to expand...
Click to collapse
You have to request sim unlock first then you can unlock the bootloader.

Is it possible to re-lock the bootloader after flashing the Factory Image? I have to sent it back in RMA

capitanouncino said:
Is it possible to re-lock the bootloader after flashing the Factory Image? I have to sent it back in RMA
Click to expand...
Click to collapse
Yeah just reverse the steps you did when you unlocked it. Make sure your On stock before you do it. I've sent a few phones back to Google for warranty and I've never worried about locking the bootloader back up
Edit. I want to say the first one I sent back I locked until people told me it didn't matter

Ordered the unlocked model by mistake. Can I flash the Verizon FW to get it to work on Verizon?
Thanks,

jmill75 said:
Ordered the unlocked model by mistake. Can I flash the Verizon FW to get it to work on Verizon?
Thanks,
Click to expand...
Click to collapse
I don't think you need to do anything at all. Just use it.
Sent from my Pixel 3a using Tapatalk

jmill75 said:
Ordered the unlocked model by mistake. Can I flash the Verizon FW to get it to work on Verizon?
Thanks,
Click to expand...
Click to collapse
The unlocked model works on Verizon , you accidentally got the right one lol

So I double click on the batch file and get this bit about archive does not contain 'boot.sig' or 'recovery.img' towards the bottom, is that supposed to be there, or is there a reason it's not seeing the files?
"target reported max download size of 268435456 bytes
sending 'bootloader' (8349 KB)...
OKAY [ 0.314s]
writing 'bootloader'...
(bootloader) Flashing Pack version b4s4-0.1-5653622
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
OKAY [ 0.546s]
finished. total time: 0.862s
rebooting into bootloader...
OKAY [ 0.049s]
finished. total time: 0.050s
target reported max download size of 268435456 bytes
sending 'radio' (72988 KB)...
OKAY [ 1.985s]
writing 'radio'...
(bootloader) Flashing Pack version SSD:g670-00011-190411-B-5457439
(bootloader) Flashing partition modem_a
OKAY [ 0.555s]
finished. total time: 2.541s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.050s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate -1904684752 bytes
error: update package missing system.img
Press any key to exit..."

Why would you never recommend downgrading?

Make sure you are extracting the factory image zip into a folder then extract the image zip into the same folder. That folder has the files you need
tcshaddix said:
So I double click on the batch file and get this bit about archive does not contain 'boot.sig' or 'recovery.img' towards the bottom, is that supposed to be there, or is there a reason it's not seeing the files?
"target reported max download size of 268435456 bytes
sending 'bootloader' (8349 KB)...
OKAY [ 0.314s]
writing 'bootloader'...
(bootloader) Flashing Pack version b4s4-0.1-5653622
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
OKAY [ 0.546s]
finished. total time: 0.862s
rebooting into bootloader...
OKAY [ 0.049s]
finished. total time: 0.050s
target reported max download size of 268435456 bytes
sending 'radio' (72988 KB)...
OKAY [ 1.985s]
writing 'radio'...
(bootloader) Flashing Pack version SSD:g670-00011-190411-B-5457439
(bootloader) Flashing partition modem_a
OKAY [ 0.555s]
finished. total time: 2.541s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.050s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate -1904684752 bytes
error: update package missing system.img
Press any key to exit..."
Click to expand...
Click to collapse

how would you flash this for q when twrp is not available?

dhoang said:
This is for people with unlocked bootloader. How about for people on T-Mobile with locked bootloader like myself. Is there anyway I can go back to stock (pie)?
Click to expand...
Click to collapse
You can sideload factory images even with a locked bootloader. You can download the Pie factory image and find the instructions directly from Google.

Archangel said:
Make sure you are extracting the factory image zip into a folder then extract the image zip into the same folder. That folder has the files you need
Click to expand...
Click to collapse
Same thing happens after extracting them into the same folder. Not sure why it doesn't seem to see a file right next to the flash file.

tcshaddix said:
Same thing happens after extracting them into the same folder. Not sure why it doesn't seem to see a file right next to the flash file.
Click to expand...
Click to collapse
The same here. Any solution? I also have my Pixel 3a in bootloop.