Related
I installed CM on my Nexus 3 and 10 without incident.
I unlocked and installed CM and clockwork recovery on my Nexus 5 but when I booted into CM, nothing happened except that the CM logo just spun until I turned the phone back off. I wanted to go back to the factory image but despite sudo fastboot devices showing that it was connected, sudo adb push [image].zip /sdcard/ I just got device not found.
I removed android-tools-adp and android-tools-fastboot and reinstalled thinking there might be a driver issue but that has not resolved the problem.
Looking for a way to get either the stock 4.4 or CM 11 working.
from fastboot screen:
Code:
FASTBOOT MODE
PRODUCT_NAME - hammerhead
VARIANT - hammerhead D820 32GB
HW VERSION - rev_11
BOOTLOADER VERSION - HHZ11d
BASEBAND VERSION - M8974A-1.0.25.0.17
CARRIER INFO -None
SERIAL NUMBER - []
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - unlocked
iconoclasthero said:
I installed CM on my Nexus 3 and 10 without incident.
I unlocked and installed CM and clockwork recovery on my Nexus 5 but when I booted into CM, nothing happened except that the CM logo just spun until I turned the phone back off. I wanted to go back to the factory image but despite sudo fastboot devices showing that it was connected, sudo adb push [image].zip /sdcard/ I just got device not found.
I removed android-tools-adp and android-tools-fastboot and reinstalled thinking there might be a driver issue but that has not resolved the problem.
Looking for a way to get either the stock 4.4 or CM 11 working.
from fastboot screen:
Code:
FASTBOOT MODE
PRODUCT_NAME - hammerhead
VARIANT - hammerhead D820 32GB
HW VERSION - rev_11
BOOTLOADER VERSION - HHZ11d
BASEBAND VERSION - M8974A-1.0.25.0.17
CARRIER INFO -None
SERIAL NUMBER - []
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - unlocked
Click to expand...
Click to collapse
I had the same exact problem... Download Factory IMG file and re-flash to stock. Re-install you're drivers
dia_naji said:
I had the same exact problem... Download Factory IMG file and re-flash to stock. Re-install you're drivers
Click to expand...
Click to collapse
Unzip the stock image and use fastboot to flash each part individually.
fastboot flash worked.
iPWNtehNOOB said:
Unzip the stock image and use fastboot to flash each part individually.
Click to expand...
Click to collapse
I downloaded hammerhead-krt16m-factory-bd9c39de.tgz (md5sum: 3a7b6cb66f8ec20edf661aee2d73d3a4) from hammerhead-krt16m-factory-bd9c39de.tgz, which I assume is the download site from developers dot google dot com images#hammerheadkrt16m.
When I tried to send the files with fastboot yesterday, it just hung.
I downloaded everything again this morning and got a different md5sum (36aa82ab2d7d05ee144d18546565cd5f) and instead of trying to manually fastboot the files over I executed the script
Code:
sudo ./flash-all.sh
sending 'bootloader' (2506 KB)...
OKAY [ 0.288s]
writing 'bootloader'...
OKAY [ 0.471s]
finished. total time: 0.760s
rebooting into bootloader...
OKAY [ 0.136s]
finished. total time: 0.136s
sending 'radio' (42033 KB)...
OKAY [ 1.508s]
writing 'radio'...
OKAY [ 2.899s]
finished. total time: 4.407s
rebooting into bootloader...
OKAY [ 0.125s]
finished. total time: 0.125s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ11d
Baseband Version.....: M8974A-1.0.25.0.17
Serial Number........: []
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (8620 KB)...
OKAY [ 0.490s]
writing 'boot'...
OKAY [ 0.744s]
sending 'recovery' (9202 KB)...
OKAY [ 0.536s]
writing 'recovery'...
OKAY [ 0.778s]
erasing 'system'...
OKAY [ 1.323s]
sending 'system' (692940 KB)...
OKAY [ 21.913s]
writing 'system'...
OKAY [ 47.401s]
erasing 'userdata'...
OKAY [ 19.268s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29236371456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7137786
Block groups: 218
Reserved block group size: 1024
Created filesystem with 11/1785856 inodes and 156120/7137786 blocks
sending 'userdata' (139109 KB)...
writing 'userdata'...
OKAY [ 14.185s]
erasing 'cache'...
OKAY [ 0.669s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
sending 'cache' (13348 KB)...
writing 'cache'...
OKAY [ 1.907s]
rebooting...
finished. total time: 110.048s
I guess I had a corrupt download then. Thanks for the help.
Any idea why I could boot into Clockwork but CM just hung? Any additional things to try? Will CM boot without a SIM card?
On the plus side while messing around with trying to get this fixed, I stumbled on a way to get my new nvidia drivers working for the EVGA GTX650 I bought to power my twin 27" displays, so I guess that is also a plus!
same but now works
I just reinstalled recovery again and cm 11.
I flashed a modified 44s ota over a 33r ROM (stock) file to my device and lost the ability to boot. Whenever I try to flash via fastboot I get the error: "FAILED (remote: partition table doesn't exist)"
Does anyone have a way of repairing this? Would love to start using this device again. Thanks in advance :good:
emmanuel_baez said:
I flashed a modified 44s ota over a 33r ROM (stock) file to my device and lost the ability to boot. Whenever I try to flash via fastboot I get the error: "FAILED (remote: partition table doesn't exist)"
Does anyone have a way of repairing this? Would love to start using this device again. Thanks in advance :good:
Click to expand...
Click to collapse
Do this at your own risk:
Go into fastboot and flash 38R. (Available at current time on cygen's site) Flash everything including userdata. Reboot and you should be at the home screen. Then when you are here ota update through settings. Not recommended to modify ota, just do it after the ota if possible. (You might have to unlock the bootloader to follow this guide)
skyguy126 said:
Do this at your own risk:
Go into fastboot and flash 38R. (Available at current time on cygen's site) Flash everything including userdata. Reboot and you should be at the home screen. Then when you are here ota update through settings. Not recommended to modify ota, just do it after the ota if possible. (You might have to unlock the bootloader to follow this guide)
Click to expand...
Click to collapse
I don't think that's going to work, he's borked his partitions. And the modified OTA wasn't technically the problem. The problem is that he flashed an OTA on top of an incorrect preceding build. It should have gone 33>38>44 but instead went 33>44. Because it was a modified OTA with a modified installer script, the safeguard that would normally stop such a mistake from happening had been disabled. Modified OTA's are perfectly fine, as long as you take them in the right sequence.
Transmitted via Bacon
He still has access to fastboot which means he can reflash stock firmware.
Not with borked partitions.
Transmitted via Bacon
timmaaa said:
Not with borked partitions.
Transmitted via Bacon
Click to expand...
Click to collapse
Shouldn't it work with the Official signed 44s Fastboot Image that was released yesterday by Cyanogen?
Not if the partitions are borked. It can't flash to a partition table that doesn't exist. It's like trying to serve dinner onto thin air, it has nowhere to go.
Transmitted via Bacon
And there will be no way to repartition? Guess that something like using parted should work on nand, assumed the right partition tables are known...
It's possible, but getting it done can be tricky. I myself have zero experience in trying to repartition.
Transmitted via Bacon
Note to self: triple check the version numbers before flashing lol
Sorry op I have no constructive feedback
Sent from my A0001 using XDA Free mobile app
timmaaa said:
I don't think that's going to work, he's borked his partitions. And the modified OTA wasn't technically the problem. The problem is that he flashed an OTA on top of an incorrect preceding build. It should have gone 33>38>44 but instead went 33>44. Because it was a modified OTA with a modified installer script, the safeguard that would normally stop such a mistake from happening had been disabled. Modified OTA's are perfectly fine, as long as you take them in the right sequence.
Transmitted via Bacon
Click to expand...
Click to collapse
@timmaaa you were correct I attempted that and it failed. I resolved my problem by flashing calkulin's stock mod 44s. I've come across another issue now. Occasionally the devices screen won't come on at all. I'll have to completely reboot the phone for it to work. Is this an issue on 44s or is there another problem under the hood?
emmanuel_baez said:
@timmaaa you were correct I attempted that and it failed. I resolved my problem by flashing calkulin's stock mod 44s. I've come across another issue now. Occasionally the devices screen won't come on at all. I'll have to completely reboot the phone for it to work. Is this an issue on 44s or is there another problem under the hood?
Click to expand...
Click to collapse
I am running CM11 nightlies, and this issue happens to me (and also on my nexus 5 using milestone builds) ONLY when I am using the Ondemand governor. If you're using that, try changing and see what happens.
Ah yes I am using ondemand. I switched it from interactive last night. Didn't think of that thanks I'll test it.
Sent from my A0001 using XDA Free mobile app
emmanuel_baez said:
Ah yes I am using ondemand. I switched it from interactive last night. Didn't think of that thanks I'll test it.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Please make sure to report back, could be valuable info. I haven't found anyone else discussing this potential cause of the problem, but others do seem to have it.
Sent from my A0001 using XDA Free mobile app
So far it hasn't done it since I changed back to interactive.
Sent from my A0001 using XDA Free mobile app
Hello,
I need some help with a Oneplus One that is stuck on the Cyanogen boot image. I bought this for cheap thinking that I could fix it, but 3 hours later still no luck. I have access to TWRP and Fastboot, which made me hopeful, but no access to the storage on the device.
1. TWRP: I can’t mount /data, /cache/ persist (shows E:Unable to mount ‘/data’, etc). I can mount /firmware or /system.
Trying to sideload a bunch of different roms gives me this in the command prompt:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload cm12.zip
loading: 'cm12.zip'* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
2. Fastboot: trying to flash individual files with fastboot gives me “remote: flash write failure”. I’ve also gotten a “partition table doesn’t exist” error.
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
I tried these directions and got this:
Code:
target reported max download size of 1073741824 bytes
sending 'modem' (57361 KB)...
OKAY [ 1.802s]
writing 'modem'...
FAILED (remote: flash write failure)
finished. total time: 6.860s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.007s
target reported max download size of 1073741824 bytes
sending 'sbl1' (273 KB)...
OKAY [ 0.016s]
writing 'sbl1'...
FAILED (remote: flash write failure)
finished. total time: 5.076s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.009s
target reported max download size of 1073741824 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.005s]
writing 'dbi'...
FAILED (remote: flash write failure)
finished. total time: 5.064s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.010s
target reported max download size of 1073741824 bytes
sending 'aboot' (445 KB)...
OKAY [ 0.019s]
writing 'aboot'...
FAILED (remote: flash write failure)
finished. total time: 5.077s
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.014s
target reported max download size of 1073741824 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.010s]
writing 'rpm'...
FAILED (remote: flash write failure)
finished. total time: 5.067s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.012s
target reported max download size of 1073741824 bytes
sending 'tz' (321 KB)...
OKAY [ 0.015s]
writing 'tz'...
FAILED (remote: flash write failure)
finished. total time: 5.071s
rebooting into bootloader...
OKAY [ 0.009s]
finished. total time: 0.010s
target reported max download size of 1073741824 bytes
sending 'LOGO' (328 KB)...
OKAY [ 0.014s]
writing 'LOGO'...
FAILED (remote: flash write failure)
finished. total time: 5.070s
rebooting into bootloader...
OKAY [ 0.009s]
finished. total time: 0.010s
target reported max download size of 1073741824 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.326s]
writing 'oppostanvbk'...
FAILED (remote: flash write failure)
finished. total time: 5.394s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.007s
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 59914792960
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14627635
Block groups: 447
Reserved block group size: 1024
Created filesystem with 11/3661824 inodes and 275906/14627635 blocks
Cannot read image.
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: 56d36153
--------------------------------------------
checking product...
OKAY [ 0.003s]
sending 'boot' (6372 KB)...
OKAY [ 0.205s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 5.297s
Press any key to exit...
From what I've read, I think Heisenberg will say that the partitions are borked, but I'm hoping I'm a little luckier than others who do not have access to fastboot or twrp. Any suggestions?
majzoob said:
Hello,
I need some help with a Oneplus One that is stuck on the Cyanogen boot image. I bought this for cheap thinking that I could fix it, but 3 hours later still no luck. I have access to TWRP and Fastboot, which made me hopeful, but no access to the storage on the device.
1. TWRP: I can’t mount /data, /cache/ persist (shows E:Unable to mount ‘/data’, etc). I can mount /firmware or /system.
Trying to sideload a bunch of different roms gives me this in the command prompt:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload cm12.zip
loading: 'cm12.zip'* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
2. Fastboot: trying to flash individual files with fastboot gives me “remote: flash write failure”. I’ve also gotten a “partition table doesn’t exist” error.
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
I tried these directions and got this:
Code:
target reported max download size of 1073741824 bytes
sending 'modem' (57361 KB)...
OKAY [ 1.802s]
writing 'modem'...
FAILED (remote: flash write failure)
finished. total time: 6.860s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.007s
target reported max download size of 1073741824 bytes
sending 'sbl1' (273 KB)...
OKAY [ 0.016s]
writing 'sbl1'...
FAILED (remote: flash write failure)
finished. total time: 5.076s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.009s
target reported max download size of 1073741824 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.005s]
writing 'dbi'...
FAILED (remote: flash write failure)
finished. total time: 5.064s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.010s
target reported max download size of 1073741824 bytes
sending 'aboot' (445 KB)...
OKAY [ 0.019s]
writing 'aboot'...
FAILED (remote: flash write failure)
finished. total time: 5.077s
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.014s
target reported max download size of 1073741824 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.010s]
writing 'rpm'...
FAILED (remote: flash write failure)
finished. total time: 5.067s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.012s
target reported max download size of 1073741824 bytes
sending 'tz' (321 KB)...
OKAY [ 0.015s]
writing 'tz'...
FAILED (remote: flash write failure)
finished. total time: 5.071s
rebooting into bootloader...
OKAY [ 0.009s]
finished. total time: 0.010s
target reported max download size of 1073741824 bytes
sending 'LOGO' (328 KB)...
OKAY [ 0.014s]
writing 'LOGO'...
FAILED (remote: flash write failure)
finished. total time: 5.070s
rebooting into bootloader...
OKAY [ 0.009s]
finished. total time: 0.010s
target reported max download size of 1073741824 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.326s]
writing 'oppostanvbk'...
FAILED (remote: flash write failure)
finished. total time: 5.394s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.007s
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 59914792960
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14627635
Block groups: 447
Reserved block group size: 1024
Created filesystem with 11/3661824 inodes and 275906/14627635 blocks
Cannot read image.
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: 56d36153
--------------------------------------------
checking product...
OKAY [ 0.003s]
sending 'boot' (6372 KB)...
OKAY [ 0.205s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 5.297s
Press any key to exit...
From what I've read, I think Heisenberg will say that the partitions are borked, but I'm hoping I'm a little luckier than others who do not have access to fastboot or twrp. Any suggestions?
Click to expand...
Click to collapse
Go here:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
try OTG cable ... ?
Heisenberg said:
Go here:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
I messed up my One by deleting stuff I should not have... it would not read the internal "sd card" memory at all... so nothing would flash to the phone. I had fastboot and TWRP working. I tried this kit and it only partially worked for me, but did get recovery going. What I did get to work is by connecting an on-the-go cable to it and put the files to flash on a flash drive. The phone will find it in TWRP if you set it up to read the OTG cable. Then flash away something that will boot up... then go from there with the ROM you want to use. Using the Caulkin's ROM mentioned earlier will get it at least running. This worked for me, and may work for you too.
Jimmy Rudedog said:
I messed up my One by deleting stuff I should not have... it would not read the internal "sd card" memory at all... so nothing would flash to the phone. I had fastboot and TWRP working. I tried this kit and it only partially worked for me. What I did get to work is by connecting an on-the-go cable to it and put the files to flash on it. The phone will find it in TWRP if you set it up to read the OTG cable. Then flash away something that will boot up... then go from there with the ROM you want to use. Using the Caulkin's ROM mentioned earlier will get it at least running. This worked for me, and may work for you too.
Click to expand...
Click to collapse
That won't work in this situation, he hasn't merely deleted everything, the partition table is borked.
Thanks for the reply. I'd previously read that, but thought it didn't apply because I have fastboot and recovery. I'm trying it now, but I can't get the device to show up in Device Manager. The phone goes to the charger screen when connected and it shows up as MTP USB Device. I tried seeing if it would show up on the downloadtool.exe he mentions, but no go.
So I decided to flash the latest factory image available for the N5 today. I was running Build MOB30Y. I did it using Nexus Root Toolkit and I chose the 'No Wipe Mode', it says that it failed. Here's the exact error:
Flash Stock + Unroot [WugFresh Development]
------------------------------------------------------------------
target reported max download size of 1073741824 bytes
sending 'bootloader' (3124 KB)...
OKAY [ 0.244s]
writing 'bootloader'...
OKAY [ 0.447s]
finished. total time: 0.693s
rebooting into bootloader...
OKAY [ 0.044s]
finished. total time: 0.046s
target reported max download size of 1073741824 bytes
sending 'radio' (45489 KB)...
OKAY [ 1.541s]
writing 'radio'...
OKAY [ 3.086s]
finished. total time: 4.629s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.885s]
sending 'system' (842656 KB)...
OKAY [ 26.533s]
writing 'system'...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 84.341s
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
error: file_write: write: No space left on device
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.507s]
sending 'cache' (2136 KB)...
OKAY [ 0.180s]
writing 'cache'...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 0.969s
rebooting...
finished. total time: 0.003s
---------------------------------------------
Now when I boot up my phone it goes into the black screen with 'Google' on it then it turns off for a second then back to the Google screen and then it boots into custom recover (TWRP). What can I do to fix this? Thanks in advance.
Manually flash the ROM in fastboot.
audit13 said:
Manually flash the ROM in fastboot.
Click to expand...
Click to collapse
Is it possible to do that without wiping my data?
Yes, just don't flash userdata.img or wipe.
Before flashing, you might want to use twrp to back up data or copy files to your computer, then flash.
audit13 said:
Yes, just don't flash userdata.img or wipe.
Before flashing, you might want to use twrp to back up data or copy files to your computer, then flash.
Click to expand...
Click to collapse
Thanks! Hopefully this works. I've never done anything with fastboot though. I'll look it up later.
I have not used kits to flash stock rom, I always do it manually to learn the process.
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
audit13 said:
I have not used kits to flash stock rom, I'm always do it manually to learn the process.
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
Much appreciated! I think I'll start learning how to do things manually now. Thanks again.
audit13 said:
I have not used kits to flash stock rom, I'm always do it manually to learn the process.
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
Thanks for everything! Everything is okay now.
Yesterday I flashed the NMF26U factory image on my Pixel using flash-all. I didn't remove the '-w' because I wanted a clean install. I saved the terminal output and there are several things that have me quite concerned even though my phone appears to be working fine.
Note the two places where it says "FAILED". Am I in trouble but don't know it yet?
Code:
E:\MobileDevices\Minimal ADB and Fastboot>flash-all
target reported max download size of 536870912 bytes
sending 'bootloader' (32980 KB)...
OKAY [ 1.154s]
writing 'bootloader'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 16.255s]
finished. total time: 17.410s
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.047s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (57192 KB)...
OKAY [ 1.919s]
writing 'radio'...
OKAY [ 1.092s]
finished. total time: 3.026s
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
< waiting for device >
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'
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: unknown command)
--------------------------------------------
Bootloader Version...: 8996-012001-1611091517
Baseband Version.....: 8996-012511-1611190200
Serial Number........: FA6C10300677
--------------------------------------------
checking product...
OKAY [ 0.047s]
checking version-bootloader...
OKAY [ 0.031s]
checking version-baseband...
OKAY [ 0.047s]
sending 'boot' (24821 KB)...
OKAY [ 0.889s]
writing 'boot'...
(bootloader) Flashing active slot "_a"
OKAY [ 0.655s]
sending sparse 'system' (516459 KB)...
OKAY [ 18.018s]
writing 'system'...
OKAY [ 6.802s]
sending sparse 'system' (520631 KB)...
OKAY [ 18.470s]
writing 'system'...
OKAY [ 10.998s]
sending sparse 'system' (517487 KB)...
OKAY [ 18.096s]
writing 'system'...
OKAY [ 7.597s]
sending 'vendor' (235186 KB)...
OKAY [ 7.956s]
writing 'vendor'...
OKAY [ 6.599s]
erasing 'userdata'...
OKAY [ 6.848s]
sending 'userdata' (138957 KB)...
OKAY [ 4.696s]
writing 'userdata'...
OKAY [ 1.342s]
erasing 'cache'...
(bootloader) Erasing active slot "_a"
FAILED (remote: Partition table doesn't exist
)
finished. total time: 109.403s
Press any key to exit...
because flash all is bat file, it contains many items which maybe not included in the factory image to be fashed.
Almost, I got same information.
by the way, how can we save or input the flash all results. I am on windows
bush911 said:
by the way, how can we save or input the flash all results. I am on windows
Click to expand...
Click to collapse
Right click the menu bar in the command box and select edit then 'selec all's. Right click again, edit then copy. Paste it into a document.
I had to re-flash back to 7.1.0, then upon setting up the phone, it began taking the OTA 7.1.1 update, which is fine. Now that the phone is unlocked and updated, what is the best method to gain root access from this point? boot-to-root or install the latest SU or ?? Thanks.
Your fastboot binary is out of date. Make sure you're using the latest version.
wbxp99 said:
Your fastboot binary is out of date. Make sure you're using the latest version.
Click to expand...
Click to collapse
Thank you! It's nice to receive a definitive answer on this. I flashed again with the latest fastboot version and the log output is very different from the first time. I am confident now that everything is in its proper place.
pstgh said:
I had to re-flash back to 7.1.0, then upon setting up the phone, it began taking the OTA 7.1.1 update, which is fine. Now that the phone is unlocked and updated, what is the best method to gain root access from this point? boot-to-root or install the latest SU or ?? Thanks.
Click to expand...
Click to collapse
This a thread about fastboot error messages. There are guide in the SU and TWRP threads. Very easy I don't personally think you need anything like boot to root. Just follow the instructions and make sure you use TWRP RC1 and SU 2.79 SR 2
i unlocked the bootloader used twrp to install magisk and installed a custom kernel, all of that went fine, then i decided to try and flash twrp which also worked... reinstalled magisk and kernel etc and it was getting stuck at the google logo,
i then decided to try and uninstall twrp and now i do not get the google logo, it won't go past the bootloader screen, bootloader seems to be functional and is accepting fastboot requests, however, the recovery is not working no matter what option i choose it will always take me back to the bootloader, tried reflashing stock images to get it working again but im getting an error with the bootloader remote command flash error.
any help is appreciated
xsanikax said:
i unlocked the bootloader used twrp to install magisk and installed a custom kernel, all of that went fine, then i decided to try and flash twrp which also worked... reinstalled magisk and kernel etc and it was getting stuck at the google logo,
i then decided to try and uninstall twrp and now i do not get the google logo, it won't go past the bootloader screen, bootloader seems to be functional and is accepting fastboot requests, however, the recovery is not working no matter what option i choose it will always take me back to the bootloader, tried reflashing stock images to get it working again but im getting an error with the bootloader remote command flash error.
any help is appreciated
Click to expand...
Click to collapse
Download the factory image for your current build.Unzip.
In flash-all, remove the -w so it doesn't wipe your device.
Ensure you have newest ADB &Fastboot.
While your device is in fastboot:
Code:
fastboot devices
Ensure you see your device serial number
Double click flash-all
That should reflash recovery so you can start over.
NOTE: You cannot flash TWRP, Kernel, and Magisk all at the same time. It causes issues.
Read this thread: [GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye). There are a lot of people that have had issues and have had help solving within it.
Diesel_Jeremiah said:
Download the factory image for your current build.Unzip.
In flash-all, remove the -w so it doesn't wipe your device.
Ensure you have newest ADB &Fastboot.
While your device is in fastboot:
Code:
fastboot devices
Ensure you see your device serial number
Double click flash-all
That should reflash recovery so you can start over.
NOTE: You cannot flash TWRP, Kernel, and Magisk all at the same time. It causes issues.
Read this thread: [GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye). There are a lot of people that have had issues and have had help solving within it.
Click to expand...
Click to collapse
thanks for the reply but i'm still getting the same error doing that.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38644 KB)...
OKAY [ 0.895s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.902s
xsanikax said:
thanks for the reply but i'm still getting the same error doing that.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38644 KB)...
OKAY [ 0.895s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.902s
Click to expand...
Click to collapse
Are you on 8.0 or 8.1?
Which bootloader are you on?
If you are in the bootloader, does it have the error line at the bottom?
If you cycle your volume buttons and reboot bootloader, does the error go away?
If the error goes away, try flash-all again.
If not:
From the bootloader, try booting the TWRP image.
If that works, reinstall TWRP using the zip.
Ensure you are using the 3.2.1.0 IMG and ZIP. Mismatching will cause problems.
I think you might have caused an issue when you deleted the TWRP recovery without replacing the stock recovery.
This post here might help.
Replace the Magisk with current version.
Diesel_Jeremiah said:
Are you on 8.0 or 8.1?
Which bootloader are you on?
If you are in the bootloader, does it have the error line at the bottom?
If you cycle your volume buttons and reboot bootloader, does the error go away?
If the error goes away, try flash-all again.
If not:
From the bootloader, try booting the TWRP image.
If that works, reinstall TWRP using the zip.
Ensure you are using the 3.2.1.0 IMG and ZIP. Mismatching will cause problems.
I think you might have caused an issue when you deleted the TWRP recovery without replacing the stock recovery.
This post here might help.
Replace the Magisk with current version.
Click to expand...
Click to collapse
was running 8.1 before this happened. bootloader version says mw8998-002.0059.00
there is no error that i can see in the bootloader, looks the same as when it was all functional
trying to boot twrp gives me this error
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.689s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.696s
it seems most things that i try and do give me a remote error, i feel like the partitions might be jacked up but i have no idea how to fix them
xsanikax said:
was running 8.1 before this happened. bootloader version says mw8998-002.0059.00
there is no error that i can see in the bootloader, looks the same as when it was all functional
trying to boot twrp gives me this error
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.689s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.696s
it seems most things that i try and do give me a remote error, i feel like the partitions might be jacked up but i have no idea how to fix them
Click to expand...
Click to collapse
You probably have already done it, but ensure you have the newest ADB, that's what screwed me up.
I had the same problem turns out I wasn't using the latest platform tools.
I couldn't do anything. Would boot strait to bootloader. I couldn't even power down and plug I to charge. It would take me to bootloader with an error. I managed to screw up even more by flashing the wrong image using old tools. Then I lost all options except bootloader ( no recovery or download mode).
I feel as long as you have an unlocked bootloader and you are able to use fastboot you shouldn't worry. I'm only saying this because I was scared as hell haha.
I did notice it would try to boot when switching boot slots. But I screwed that up too by trying to flash with old tools. In the end all I needed was latest Platform tools:
https://developer.android.com/studio/releases/platform-tools.html
iamnotreallyhere said:
I had the same problem turns out I wasn't using the latest platform tools.
I couldn't do anything. Would boot strait to bootloader. I couldn't even power down and plug I to charge. It would take me to bootloader with an error. I managed to screw up even more by flashing the wrong image using old tools. Then I lost all options except bootloader ( no recovery or download mode).
I feel as long as you have an unlocked bootloader and you are able to use fastboot you shouldn't worry. I'm only saying this because I was scared as hell haha.
I did notice it would try to boot when switching boot slots. But I screwed that up too by trying to flash with old tools. In the end all I needed was latest Platform tools:
https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
thanks a lot dude this is what im getting at the minute
target reported max download size of 536870912 bytes
sending 'bootloader' (38644 KB)...
OKAY [ 0.818s]
writing 'bootloader'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.825s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.270s]
writing 'radio'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.544s]
finished. total time: 1.815s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
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'
Creating filesystem with parameters:
Size: 57071874048
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 13933563
Block groups: 426
Reserved block group size: 1024
Created filesystem with 11/3489792 inodes and 265112/13933563 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: mw8998-002.0059.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: FA7AK1A08325
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
FAILED
Device version-bootloader is 'mw8998-002.0059.00'.
Update requires 'mw8998-002.0066.00'.
finished. total time: 0.009s
Press any key to exit...
however i have found a problem when i tried just reflashing the recovery by itself
C:\Unified_Android_Toolkit\recovery\GooglePixel2>fastboot flash recovery recovery-twrp-3.2.1.0-walleye.img
target reported max download size of 536870912 bytes
sending 'recovery' (32768 KB)...
OKAY [ 0.689s]
writing 'recovery'...
FAILED (remote: No such partition.)
finished. total time: 0.691s
seems my partitions are all jacked up, is there a way to sort that out?
oh as a side note my problems are all the same as yours i can only access the bootloader and adb will not recognize my device but fastboot will
this is what happens if i try to flash the version with the same bootloader as the one that it says is on the device
target reported max download size of 536870912 bytes
sending 'bootloader' (38728 KB)...
OKAY [ 0.815s]
writing 'bootloader'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.821s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.271s]
writing 'radio'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.544s]
finished. total time: 1.816s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
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'
Creating filesystem with parameters:
Size: 57071874048
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 13933563
Block groups: 426
Reserved block group size: 1024
Created filesystem with 11/3489792 inodes and 265112/13933563 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: mw8998-002.0059.00
Baseband Version.....: g8998-00122-1708311414
Serial Number........: FA7AK1A08325
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ 0.002s]
sending 'boot' (32768 KB)...
OKAY [ 0.690s]
writing 'boot'...
OKAY [ 0.300s]
sending sparse 'system' (524284 KB)...
OKAY [ 11.668s]
writing 'system'...
OKAY [ 4.745s]
sending sparse 'system' (524284 KB)...
OKAY [ 11.632s]
writing 'system'...
OKAY [ 4.755s]
sending sparse 'system' (524284 KB)...
OKAY [ 11.597s]
writing 'system'...
OKAY [ 4.732s]
sending sparse 'system' (322348 KB)...
OKAY [ 7.126s]
writing 'system'...
OKAY [ 2.915s]
sending 'vendor' (346992 KB)...
OKAY [ 7.342s]
writing 'vendor'...
OKAY [ 3.169s]
erasing 'userdata'...
OKAY [ 0.736s]
sending 'userdata' (140906 KB)...
OKAY [ 2.954s]
writing 'userdata'...
OKAY [ 1.502s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 75.881s
Press any key to exit...
It still sounds like you are not using the latest tools. Are you installing the platform tools or are you using the extracted zip?
the script is going to use whatever is installed on your system.
The first thing I did was download: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
I used this image Android 8.1 stock: https://dl.google.com/dl/android/aosp/taimen-opm1.171019.011-factory-2df1c1cb.zip
I extracted platform tools to my desktop. I opened the file location and did a Shift > Right click - within the folder containing the tools and opened CMD or Powershell( or you can just CD to the directory).
I copied all the commands from the script and ran them one at a time making sure I was using the tools from the zip file and not my system.
and just went down the line.
Like this:
PS C:\Users\myusername\Desktop\platform-tools> C:\Users\myusername\Desktop\platform-tools\fastboot.exe --set-active=b
Setting current slot to 'b'...
OKAY [ 0.016s]
finished. total time: 0.017s
PS C:\Users\myusername\Desktop\platform-tools> cd C:\Users\myusername\Downloads\nv3
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe flash bootloader bootloader-walleye-mw8998-002.0066.00.img
target reported max download size of 536870912 bytes
sending 'bootloader_b' (38644 KB)...
OKAY [ 0.829s]
writing 'bootloader_b'...
(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=01E1E000
(bootloader) Updating: abl @02558000 sz=00065000
OKAY [ 0.894s]
finished. total time: 1.724s
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe flash radio radio-walleye-g8998-00164-1710262031.img
target reported max download size of 536870912 bytes
sending 'radio_b' (60428 KB)...
OKAY [ 1.293s]
writing 'radio_b'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.552s]
finished. total time: 1.848s
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe -w update image-walleye-opm1.171019.011.zip
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (32 MB) to disk... took 0.134s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.020s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1920 MB) to disk... took 8.309s
archive does not contain 'system.sig'
extracting system_other.img (568 MB) to disk... took 2.987s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (347 MB) to disk... took 1.721s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 13933563 4k blocks and 3489792 inodes
Filesystem UUID: 1f46fc9a-edc7-11e7-aa2c-2daa660ba492
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Allocating group tables: done
Writing inode tables: done
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...: mw8998-002.0066.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: HT696969696969
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.001s]
sending 'boot_b' (32768 KB)...
OKAY [ 0.699s]
writing 'boot_b'...
OKAY [ 0.001s]
sending 'dtbo_b' (8192 KB)...
OKAY [ 0.477s]
writing 'dtbo_b'...
OKAY [ 0.001s]
erasing 'system_b'...
OKAY [ 0.316s]
sending sparse 'system_b' 1/4 (524284 KB)...
OKAY [ 11.667s]
writing 'system_b' 1/4...
OKAY [ 0.001s]
sending sparse 'system_b' 2/4 (524284 KB)...
OKAY [ 13.907s]
writing 'system_b' 2/4...
OKAY [ 0.001s]
sending sparse 'system_b' 3/4 (524284 KB)...
OKAY [ 13.876s]
writing 'system_b' 3/4...
OKAY [ 0.002s]
sending sparse 'system_b' 4/4 (393508 KB)...
OKAY [ 11.018s]
writing 'system_b' 4/4...
OKAY [ 0.001s]
erasing 'system_a'...
OKAY [ 2.084s]
sending sparse 'system_a' 1/2 (524284 KB)...
OKAY [ 11.561s]
writing 'system_a' 1/2...
OKAY [ 0.001s]
sending sparse 'system_a' 2/2 (57592 KB)...
OKAY [ 3.758s]
writing 'system_a' 2/2...
OKAY [ 0.001s]
sending 'vbmeta_b' (4 KB)...
OKAY [ 0.288s]
writing 'vbmeta_b'...
OKAY [ 0.001s]
erasing 'vendor_b'...
OKAY [ 0.116s]
sending 'vendor_b' (355428 KB)...
OKAY [ 7.594s]
writing 'vendor_b'...
OKAY [ 0.001s]
Setting current slot to 'b'...
OKAY [ 1.722s]
erasing 'userdata'...
OKAY [ 0.759s]
sending 'userdata' (4669 KB)...
OKAY [ 0.108s]
writing 'userdata'...
OKAY [ 0.001s]
rebooting...
finished. total time: 80.060s
fastboot flash bootloader bootloader-walleye-mw8998-002.0066.00.img
fastboot reboot-bootloader
fastboot flash radio radio-walleye-g8998-00164-1710262031.img
fastboot reboot-bootloader
fastboot -w update image-walleye-opm2.171019.012.zip
iamnotreallyhere said:
It still sounds like you are not using the latest tools. Are you installing the platform tools or are you using the extracted zip?
the script is going to use whatever is installed on your system.
The first thing I did was download: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
I used this image Android 8.1 stock: https://dl.google.com/dl/android/aosp/taimen-opm1.171019.011-factory-2df1c1cb.zip
I extracted platform tools to my desktop. I opened the file location and did a Shift > Right click - within the folder containing the tools and opened CMD or Powershell( or you can just CD to the directory).
I copied all the commands from the script and ran them one at a time making sure I was using the tools from the zip file and not my system.
and just went down the line.
Like this:
PS C:\Users\myusername\Desktop\platform-tools> C:\Users\myusername\Desktop\platform-tools\fastboot.exe --set-active=b
Setting current slot to 'b'...
OKAY [ 0.016s]
finished. total time: 0.017s
PS C:\Users\myusername\Desktop\platform-tools> cd C:\Users\myusername\Downloads\nv3
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe flash bootloader bootloader-walleye-mw8998-002.0066.00.img
target reported max download size of 536870912 bytes
sending 'bootloader_b' (38644 KB)...
OKAY [ 0.829s]
writing 'bootloader_b'...
(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=01E1E000
(bootloader) Updating: abl @02558000 sz=00065000
OKAY [ 0.894s]
finished. total time: 1.724s
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe flash radio radio-walleye-g8998-00164-1710262031.img
target reported max download size of 536870912 bytes
sending 'radio_b' (60428 KB)...
OKAY [ 1.293s]
writing 'radio_b'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.552s]
finished. total time: 1.848s
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe -w update image-walleye-opm1.171019.011.zip
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (32 MB) to disk... took 0.134s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.020s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1920 MB) to disk... took 8.309s
archive does not contain 'system.sig'
extracting system_other.img (568 MB) to disk... took 2.987s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (347 MB) to disk... took 1.721s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 13933563 4k blocks and 3489792 inodes
Filesystem UUID: 1f46fc9a-edc7-11e7-aa2c-2daa660ba492
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Allocating group tables: done
Writing inode tables: done
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...: mw8998-002.0066.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: HT696969696969
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.001s]
sending 'boot_b' (32768 KB)...
OKAY [ 0.699s]
writing 'boot_b'...
OKAY [ 0.001s]
sending 'dtbo_b' (8192 KB)...
OKAY [ 0.477s]
writing 'dtbo_b'...
OKAY [ 0.001s]
erasing 'system_b'...
OKAY [ 0.316s]
sending sparse 'system_b' 1/4 (524284 KB)...
OKAY [ 11.667s]
writing 'system_b' 1/4...
OKAY [ 0.001s]
sending sparse 'system_b' 2/4 (524284 KB)...
OKAY [ 13.907s]
writing 'system_b' 2/4...
OKAY [ 0.001s]
sending sparse 'system_b' 3/4 (524284 KB)...
OKAY [ 13.876s]
writing 'system_b' 3/4...
OKAY [ 0.002s]
sending sparse 'system_b' 4/4 (393508 KB)...
OKAY [ 11.018s]
writing 'system_b' 4/4...
OKAY [ 0.001s]
erasing 'system_a'...
OKAY [ 2.084s]
sending sparse 'system_a' 1/2 (524284 KB)...
OKAY [ 11.561s]
writing 'system_a' 1/2...
OKAY [ 0.001s]
sending sparse 'system_a' 2/2 (57592 KB)...
OKAY [ 3.758s]
writing 'system_a' 2/2...
OKAY [ 0.001s]
sending 'vbmeta_b' (4 KB)...
OKAY [ 0.288s]
writing 'vbmeta_b'...
OKAY [ 0.001s]
erasing 'vendor_b'...
OKAY [ 0.116s]
sending 'vendor_b' (355428 KB)...
OKAY [ 7.594s]
writing 'vendor_b'...
OKAY [ 0.001s]
Setting current slot to 'b'...
OKAY [ 1.722s]
erasing 'userdata'...
OKAY [ 0.759s]
sending 'userdata' (4669 KB)...
OKAY [ 0.108s]
writing 'userdata'...
OKAY [ 0.001s]
rebooting...
finished. total time: 80.060s
fastboot flash bootloader bootloader-walleye-mw8998-002.0066.00.img
fastboot reboot-bootloader
fastboot flash radio radio-walleye-g8998-00164-1710262031.img
fastboot reboot-bootloader
fastboot -w update image-walleye-opm2.171019.012.zip
Click to expand...
Click to collapse
im doing exactly what i'm being told to but i'm still getting the same remote command flash error and the boot slot is set to a it won't let me change it to b
okay i have an update i'm all up and running again everything is fine, turns out i had to download the older version of oreo 8.0.0 from november the latest november update, then i had to download a slightly older version of fastboot and that seems to have fixed it just ran the flash-all batch file thanks everyone for their input
Nice! Now that I think of it I did try flashing Oreo 8.0 before I tried flashing 8.1. 8.0 didn't work by itself tho. So then I flashed 8.1. Maybe that's the trick to fix the partitions.
Thanks a lot
xsanikax said:
okay i have an update i'm all up and running again everything is fine, turns out i had to download the older version of oreo 8.0.0 from november the latest november update, then i had to download a slightly older version of fastboot and that seems to have fixed it just ran the flash-all batch file thanks everyone for their input
Click to expand...
Click to collapse
Thank you for the idea of using an older version of fastboot. I somehow screwed up my Pixel 2 and loaded bootloader 59 on it and couldn't update it back to 66. I had the right image but was still using the newest version of fastboot. Ended up with 26.0.2 which was the first version with Pixel 2 support. It can be found here: https://xiaomifirmware.com/downloads/download-platform-tools-adb-fastboot-r-26-0-0/
Thanks again! :good:
Unlocked my pixel 2 and tried to root through magisk and kinda screwed it up. Tried flashing older Oreo 8.0 and 8.1 as you guys tried before but now I cant get past the fastboot screen. Whenever I try to load the earlier 8.0 it tells me it requires 8.1 to upgrade. any ideas would help
target reported max download size of 536870912 bytes
sending 'bootloader' (38644 KB)...
OKAY [ 0.829s]
writing 'bootloader'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.848s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.007s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.296s]
writing 'radio'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.543s]
finished. total time: 1.845s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.006s
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'
Creating filesystem with parameters:
Size: 57071874048
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 13933563
Block groups: 426
Reserved block group size: 1024
Created filesystem with 11/3489792 inodes and 265112/13933563 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: mw8998-002.0059.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: HT7AR1A01164
--------------------------------------------
checking product...
OKAY [ 0.004s]
checking version-bootloader...
FAILED
Device version-bootloader is 'mw8998-002.0059.00'.
Update requires 'mw8998-002.0066.00'.
finished. total time: 0.070s
Press any key to exit...
jzablocki15 said:
Unlocked my pixel 2 and tried to root through magisk and kinda screwed it up. Tried flashing older Oreo 8.0 and 8.1 as you guys tried before but now I cant get past the fastboot screen. Whenever I try to load the earlier 8.0 it tells me it requires 8.1 to upgrade. any ideas would help
target reported max download size of 536870912 bytes
sending 'bootloader' (38644 KB)...
OKAY [ 0.829s]
writing 'bootloader'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.848s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.007s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.296s]
writing 'radio'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.543s]
finished. total time: 1.845s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.006s
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'
Creating filesystem with parameters:
Size: 57071874048
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 13933563
Block groups: 426
Reserved block group size: 1024
Created filesystem with 11/3489792 inodes and 265112/13933563 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: mw8998-002.0059.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: HT7AR1A01164
--------------------------------------------
checking product...
OKAY [ 0.004s]
checking version-bootloader...
FAILED
Device version-bootloader is 'mw8998-002.0059.00'.
Update requires 'mw8998-002.0066.00'.
finished. total time: 0.070s
Press any key to exit...
Click to expand...
Click to collapse
My dude, you would not believe the hell I went through to figure this out. So it started with me getting the Verizon Pixel 2's bootloader unlocked. I downloaded TWRP onto it, rooted it, and then downloaded a ZIP that would add various modifications to my version of android. Well, I downloaded it, flashed it , and of course it didn't work as intended. Tried finding a way to undo what I'd done (absolutely imbecilic me, I didn't back up my phone WHEN THERE WAS NO SYSTEM IMAGE FOR A VERIZON PHONE YET). I figured the Google images would work fine, but they put you through hell and highwater before they do. I attempted to revert to the current stock image. It screwed my whole system up. Couldn't boot into android, couldn't boot into ANY recovery, etc. It was essentially bricked. I went through countless different errors and threads and forums and files, until I found this one right here. Tried reverting to the old version of Oreo with old ADB and fastboot. Progress, no more error popping up. Then I tried booting up and it stayed in fastboot. Tried then updating to the latest version available from Google as you had and got the exact same line of code. With the OLD ADB AND FASTBOOT and with a file I had downloaded and tinkered with earlier and with the LATEST IMAGE FROM GOOGLE (after your step), I tried it, came up with several "faileds" and other errors, but after the script was done, I rebooted and it got to the boot animation (as it had done before) and FINALLY brought my phone to the setup wizard.
The file I used was this one: https://forum.xda-developers.com/pixel-2/development/tool-deuces-bootloop-recovery-flashing-t3725778
Recap:
Download old ADB and Fastboot
Download the latest Android 8.0 Oreo Stock Image
Flash all bat
Download latest Android 8.1 Oreo Stock Image
From there, put the downloaded script in with the image file of the latest available Android 8.1 Oreo Stock Image and run the script.
Should show errors
Reboot once it's finished
Should be fine.
Keep in mind, this was a Verizon Pixel 2 and it worked fine for me. Couldn't guarantee it'd work for you, and there may have even been precursor steps before this post that I took and didn't keep track of that might have contributed to an extremely lucky brick save.
Long story short folks, if you're on an unlocked bootloader Verizon, don't do anything you can't live with for a while until we've got a proper backdoor developed for us.
Read my message right above your original post. Get the image for oreo 8.0 (nov) and use the fastboot version fron the site I linked to. Should have the 59 bootloader. After it boots, just do the OTA update twice. Check the build number and then get that image from Google to root the boot.img file. All good.
Yupp, just used the tool and saved a couple hundred bucks and a pair of underwear. Really is phone saver. And I'm for sure going to wait until a less risky root is available. I was able to flash the tool with factory image 66 version bootloader, just make sure to have tool in the same folder as the unzipped bootloader and files.
I haven't posted in at least 2 years. Wanted to thank everyone in this thread for the detailed troubleshooting. I locked my bootloader without doing the prep work and this saved me from a fiasco the week before my vacation.