Related
I've managed to unlock the bootloader on a friend's Zenfone 2 (Z00A); or, at least, I believe I have, because the boot splash screen has the inverted colors that most threads on BL unlocking mention. I used this method, inside a Windows XP VM.
The thing is, I can't flash TWRP. If I try, it tells me permission was denied.
Code:
[email protected]:~/dev/android/sdk/platform-tools$ sudo ./fastboot flash recovery /media/michael/2D66-7551/Zenfone\ 2\ ZE551ML/twrp-3.0.0-0-Z00A.img
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'recovery' (15674 KB)...
OKAY [ 0.967s]
writing 'recovery'...
FAILED (remote: Permission denied
)
finished. total time: 1.123s
(The same thing happens if run from inside the XP VM.)
Could someone please steer me in the right direction?
Sorry i can't post any external link.
I had this kind of problem the first time, because you need to root the phone after you unlock the bootloader.
Follow this step : http://forum.xda-developers.com/zenfone2/general/tool-one-click-bootloader-unlock-root-t3155884
then
Enter that in google : gurus wizard/2015/07/root-and-unlock-bootloader-on-asus-zenfone-2.html
Hi,
I'm getting this error after Watch finish downloading update and restarting. I tried factory reset but no luck. Now I have 2.6.0.176354550 version, build number is N7G75S. Any solution?
Voterx said:
Hi,
I'm getting this error after Watch finish downloading update and restarting. I tried factory reset but no luck. Now I have 2.6.0.176354550 version, build number is N7G75S. Any solution?
Click to expand...
Click to collapse
Same for me.
The dead android picture appears, then the watch restarts. After that as a notification the following appears:
"Couldn't install system update
Tap to learn more"
cybericius said:
Same for me.
The dead android picture appears, then the watch restarts. After that as a notification the following appears:
"Couldn't install system update
Tap to learn more"
Click to expand...
Click to collapse
Please help, it is continuously trying to update itself, draining the battery dramatically.
Can I at least stop it doing this?
Or is there a firmware image that I could download and install via the cradle?
Solution
Ok, I solve this problem and now I have 2.7.0.178645119, October 5 2017 patch.
Note: all your data will be saved! It's just update, after reboot you'll be able to use watch as before with all apps etc.
1) Download 2.0 OTA https://android.googleapis.com/pack.../ee44a144cfa1319430608b5322b7d359c3e4bbf6.zip
1.1) Optionally rename it in "update.zip"
2) Connect watch via USB, enable debugging, install adb... etc. Standard.
3) Copy update.zip in adb folder (or open CMD in folder where is zip file if you have globally installed adb)
4) Check if your PC "see" Huawei watch by typing in CMD:
Code:
adb devices
4.1) Maybe you'll have to confirm on watch adb for that PC (select allow always)
5) If so, reboot in bootloader:
Code:
adb reboot bootloader
6) In the bootloader mode, navigate to "Reboot recovery" option by pressing the side button (short press) and select it by holding the same button.
7) Now, you'll see list, swipe RIGHT to select "apply update from ADB" and click on it with side button
8) In CMD type:
Code:
adb sideload update.zip
(or whathever you name that zip file)
9) WAIT to finish. After that you'll see again list and now select "clear cache" by swiping right.
10) Now select first option "Reboot" to reboot watch.
11) After rebooting, you'll maybe get again "Fail update" notification but don't worry, just select "Try again" (or go in settings and update)
12) Now, watch will update normally, you'll see that colorful rings and progress bar in the middle. WAIT.
13) Watch will reboot and you'll see Google booting animation. WAIT a little longer (about 5 min)
14) You are set! Enjoy in latest update :fingers-crossed:
Didnt work for me. Still got the "Couldn't install message". When I click it, it tells me the system is up to date. Anyone else get this?
Voterx said:
Ok, I solve this problem and now I have 2.7.0.178645119, October 5 2017 patch.
Note: all your data will be saved! It's just update, after reboot you'll be able to use watch as before with all apps etc.
1) Download 2.0 OTA https://android.googleapis.com/pack.../ee44a144cfa1319430608b5322b7d359c3e4bbf6.zip
1.1) Optionally rename it in "update.zip"
2) Connect watch via USB, enable debugging, install adb... etc. Standard.
3) Copy update.zip in adb folder (or open CMD in folder where is zip file if you have globally installed adb)
4) Check if your PC "see" Huawei watch by typing in CMD:
Code:
adb devices
4.1) Maybe you'll have to confirm on watch adb for that PC (select allow always)
5) If so, reboot in bootloader:
Code:
adb reboot bootloader
6) In the bootloader mode, navigate to "Reboot recovery" option by pressing the side button (short press) and select it by holding the same button.
7) Now, you'll see list, swipe RIGHT to select "apply update from ADB" and click on it with side button
8) In CMD type:
Code:
adb sideload update.zip
(or whathever you name that zip file)
9) WAIT to finish. After that you'll see again list and now select "clear cache" by swiping right.
10) Now select first option "Reboot" to reboot watch.
11) After rebooting, you'll maybe get again "Fail update" notification but don't worry, just select "Try again" (or go in settings and update)
12) Now, watch will update normally, you'll see that colorful rings and progress bar in the middle. WAIT.
13) Watch will reboot and you'll see Google booting animation. WAIT a little longer (about 5 min)
14) You are set! Enjoy in latest update :fingers-crossed:
Click to expand...
Click to collapse
Resolved!!
Hi there All...
For those who are having problem for the update... Follow these steps:
1. In CMD :
adb reboot bootloader
2. In the bootloader mode, navigate to "Reboot recovery" option by pressing the side button (short press) and select it by holding the same button.
3. wipe cache...
4.wipe data/factory reset
5.reboot
6.check for update...
DONE!!
this process worked for me.. :laugh:
Tried both methods, still no success.
Is there any other method? It's unbelievable that there is no official resolution for this. There are more people who have the same issue.
Is the firmware available somewhere at least maybe so I could update it with adb directly?
This is what I did for getting N7G75S updated on the watch.
Thanks.
Solution guide with all the needed steps
UPDATED 2018-01-09
Alright, folks.
Here comes the resolution!
1. Download the full AW1.5 M6E69F firmware
On the official Android website, you can find a link that will lead you - after accepting the terms - to the full installation package of a 1.5 firmware, (direct link to M6E69F image).
2. Download and install the Google ADB driver - optional if you already have it
On the official website of Android,, there is a link that always leads to the latest downloadable ADB driver for Windows.
3. Download and install ADB and Fastboot - optional if you already have it
On the official website of Google, threre is a link that leads to the downloadable platform tools including ADB and Fastboot.
4. Extract the M6E69F package file
Get the 7zip installation for your OS to extract the package file.
Follow the installation steps of 7zip.
These are the files we need at the end:
Code:
flash-all.sh
image-sturgeon-m6e69f.zip
flash-all.bat
bootloader-sturgeon-m6e69f.img
5. Copy them into the folder where you have installed ADB/Fastboot.
6. Put the watch on the USB cradle that is connected to the PC.
7. Start up the watch to Fastboot mode:
1) While the watch is on, hold down the power button.
(I just pressed the button of the watch for long enough (~10s), thus it switched off itself and I kept pressing the button onward.)
2) The screen will go black for about 2 seconds and then boot into the Huawei logo. Keep holding down the power button.
3) Wait for the first vibration, release the power button and then immediately give the power button one short press.
Note: If you feel the second vibration, you waited too long to do the release and press. Start over again with Step 1.
Video help: https://www.youtube.com/watch?v=GR9SBGvP8E8
8. Open the Command Prompt/Powershell and get to the ADB/Fastboot/Firmware folder.
1. Start the File Explorer.
2. Navigate to the folder that contains ADB, Fastboot and Firmware, but do not enter into it.
3. Shift-right click on the folder.
4. Select Open Powershell window here - or similar to what the OS you use has (e.g. Command Prompt)
5. Execute the command
Code:
fastboot.exe devices
. This should result in showing an ID of the device:
Code:
PS C:\adb> .\fastboot.exe devices
MQB7N16120000974 fastboot
If that is not shown, do troubleshooting in the forum. Also, make sure you are in fastboot mode once again.
6. Unlock the bootloader:
Code:
fastboot oem unlock
7. Execute the command
Code:
flash-all.bat
from the same folder. You should see something like below:
Code:
PS C:\adb> .\flash-all.bat
target reported max download size of 63963136 bytes
sending 'bootloader' (13746 KB)...
OKAY [ 1.269s]
writing 'bootloader'...
OKAY [ 21.096s]
finished. total time: 22.367s
rebooting into bootloader...
OKAY [ 0.012s]
finished. total time: 0.013s
target reported max download size of 63963136 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: 2499784704
Block size: 4096
Blocks per group: 32768
Inodes per group: 8032
Inode size: 256
Journal blocks: 9535
Label:
Blocks: 610299
Block groups: 19
Reserved block group size: 151
Created filesystem with 11/152608 inodes and 20032/610299 blocks
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...: STURGEONV3.8
Baseband Version.....: N/A
Serial Number........: MQB7N16120000974
--------------------------------------------
checking product...
OKAY [ 0.011s]
checking version-bootloader...
OKAY [ 0.014s]
sending 'boot' (6686 KB)...
OKAY [ 0.621s]
writing 'boot'...
OKAY [ 0.633s]
sending 'recovery' (7854 KB)...
OKAY [ 0.729s]
writing 'recovery'...
OKAY [ 0.735s]
erasing 'system'...
OKAY [ 0.525s]
sending sparse 'system' (62457 KB)...
OKAY [ 5.944s]
writing 'system'...
OKAY [ 6.902s]
sending sparse 'system' (62313 KB)...
OKAY [ 6.019s]
writing 'system'...
OKAY [ 6.534s]
sending sparse 'system' (61976 KB)...
OKAY [ 5.870s]
writing 'system'...
OKAY [ 6.255s]
sending sparse 'system' (61662 KB)...
OKAY [ 5.875s]
writing 'system'...
OKAY [ 6.031s]
sending sparse 'system' (57152 KB)...
OKAY [ 5.416s]
writing 'system'...
OKAY [ 5.403s]
sending sparse 'system' (60517 KB)...
OKAY [ 5.745s]
writing 'system'...
OKAY [ 7.129s]
sending sparse 'system' (59580 KB)...
OKAY [ 5.626s]
writing 'system'...
OKAY [ 5.526s]
sending sparse 'system' (58988 KB)...
OKAY [ 5.573s]
writing 'system'...
OKAY [ 5.526s]
sending sparse 'system' (10312 KB)...
OKAY [ 0.998s]
writing 'system'...
OKAY [ 1.068s]
erasing 'userdata'...
OKAY [ 0.749s]
sending 'userdata' (40964 KB)...
OKAY [ 3.751s]
writing 'userdata'...
OKAY [ 3.894s]
erasing 'cache'...
OKAY [ 0.165s]
sending 'cache' (10432 KB)...
OKAY [ 0.963s]
writing 'cache'...
OKAY [ 0.997s]
rebooting...
finished. total time: 111.323s
Press any key to exit...
8. Lock the bootloader:
Code:
fastboot oem lock
9. Pair your watch
Pair your watch to the Android Wear app on your phone. Unfortunately, it is necessary to continue.
10. Check for new firmware, step 1
Go to the Settings/System/About menu of the watch and select System updates. In my case the download of the new AW2.0 FW was in progress already, but you might need to check for a new firmware manually. Wait for the watch to install the new firmware. In my case it happened to be N7G75S, so I was a bit worried at this point about the successful outcome of step 11, since that FW never has successfully allowed the upgrade to the latest available one.
11. Check for new firmware, step 2
After having the new AW2.0 FW successfully upgraded, check for a new firmware again. Go to the Settings/System/About menu of the watch and select System updates. Wait for the new update to be installed.
12. FINAL DESTINATION
Finally! You should have by now under the Build number section the new firmware version NWD1.171016.002 or newer indicated! System is up to date. Check!
Let me know if I need to update this full description. It would I think help everyone, as only one post would have to be checked as a reference.
:victory:
cybericius said:
Alright, folks.
6. Execute the command
Code:
flash-all.bat
from the same folder. You should see something like below:
Click to expand...
Click to collapse
This worked for me so far. Thank you
Will have to wait and see if the notification returns in a few days or not.
Also, you need to include bootloader unlocking before step 6 otherwise the procedure fails
alleyman said:
This worked for me so far. Thank you
Will have to wait and see if the notification returns in a few days or not.
Also, you need to include bootloader unlocking before step 6 otherwise the procedure fails
Click to expand...
Click to collapse
Thanks, that is true. I have added both unlocking before flashing and locking at the end of flashing.
Voterx said:
Ok, I solve this problem and now I have 2.7.0.178645119, October 5 2017 patch.
Note: all your data will be saved! It's just update, after reboot you'll be able to use watch as before with all apps etc.
1) Download 2.0 OTA https://android.googleapis.com/pack.../ee44a144cfa1319430608b5322b7d359c3e4bbf6.zip
1.1) Optionally rename it in "update.zip"
2) Connect watch via USB, enable debugging, install adb... etc. Standard.
3) Copy update.zip in adb folder (or open CMD in folder where is zip file if you have globally installed adb)
4) Check if your PC "see" Huawei watch by typing in CMD:
Code:
adb devices
4.1) Maybe you'll have to confirm on watch adb for that PC (select allow always)
5) If so, reboot in bootloader:
Code:
adb reboot bootloader
6) In the bootloader mode, navigate to "Reboot recovery" option by pressing the side button (short press) and select it by holding the same button.
7) Now, you'll see list, swipe RIGHT to select "apply update from ADB" and click on it with side button
8) In CMD type:
Code:
adb sideload update.zip
(or whathever you name that zip file)
9) WAIT to finish. After that you'll see again list and now select "clear cache" by swiping right.
9.2) Press Power button a little bit long, so it reboots.
##(10) Now select first option "Reboot" to reboot watch.)
11) After rebooting, you'll maybe get again "Fail update" notification but don't worry, just select "Try again" (or go in settings and update)
12) Now, watch will update normally, you'll see that colorful rings and progress bar in the middle. WAIT.
13) Watch will reboot and you'll see Google booting animation. WAIT a little longer (about 5 min)
14) You are set! Enjoy in latest update :fingers-crossed:
Click to expand...
Click to collapse
It is showing the circle right now!!
Wish me luck
I was able to get to N7G75S just fine but the update after that always gets me the Exclamation Point into the Recovery. I have no idea what is going on but it keeps trying to update and failing. I even tried sideloading the update.zip.
cybericius said:
UPDATED 2018-01-09
Alright, folks.
Here comes the resolution!
1. Download the full AW1.5 M6E69F firmware
On the official Android website, you can find a link that will lead you - after accepting the terms - to the full installation package of a 1.5 firmware, (direct link to M6E69F image).
2. Download and install the Google ADB driver - optional if you already have it
On the official website of Android,, there is a link that always leads to the latest downloadable ADB driver for Windows.
3. Download and install ADB and Fastboot - optional if you already have it
On the official website of Google, threre is a link that leads to the downloadable platform tools including ADB and Fastboot.
4. Extract the M6E69F package file
Get the 7zip installation for your OS to extract the package file.
Follow the installation steps of 7zip.
These are the files we need at the end:
Code:
flash-all.sh
image-sturgeon-m6e69f.zip
flash-all.bat
bootloader-sturgeon-m6e69f.img
5. Copy them into the folder where you have installed ADB/Fastboot.
6. Put the watch on the USB cradle that is connected to the PC.
7. Start up the watch to Fastboot mode:
1) While the watch is on, hold down the power button.
(I just pressed the button of the watch for long enough (~10s), thus it switched off itself and I kept pressing the button onward.)
2) The screen will go black for about 2 seconds and then boot into the Huawei logo. Keep holding down the power button.
3) Wait for the first vibration, release the power button and then immediately give the power button one short press.
Note: If you feel the second vibration, you waited too long to do the release and press. Start over again with Step 1.
Video help: https://www.youtube.com/watch?v=GR9SBGvP8E8
8. Open the Command Prompt/Powershell and get to the ADB/Fastboot/Firmware folder.
1. Start the File Explorer.
2. Navigate to the folder that contains ADB, Fastboot and Firmware, but do not enter into it.
3. Shift-right click on the folder.
4. Select Open Powershell window here - or similar to what the OS you use has (e.g. Command Prompt)
5. Execute the command
Code:
fastboot.exe devices
. This should result in showing an ID of the device:
Code:
PS C:\adb> .\fastboot.exe devices
MQB7N16120000974 fastboot
If that is not shown, do troubleshooting in the forum. Also, make sure you are in fastboot mode once again.
6. Unlock the bootloader:
Code:
fastboot oem unlock
7. Execute the command
Code:
flash-all.bat
from the same folder. You should see something like below:
Code:
PS C:\adb> .\flash-all.bat
target reported max download size of 63963136 bytes
sending 'bootloader' (13746 KB)...
OKAY [ 1.269s]
writing 'bootloader'...
OKAY [ 21.096s]
finished. total time: 22.367s
rebooting into bootloader...
OKAY [ 0.012s]
finished. total time: 0.013s
target reported max download size of 63963136 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: 2499784704
Block size: 4096
Blocks per group: 32768
Inodes per group: 8032
Inode size: 256
Journal blocks: 9535
Label:
Blocks: 610299
Block groups: 19
Reserved block group size: 151
Created filesystem with 11/152608 inodes and 20032/610299 blocks
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...: STURGEONV3.8
Baseband Version.....: N/A
Serial Number........: MQB7N16120000974
--------------------------------------------
checking product...
OKAY [ 0.011s]
checking version-bootloader...
OKAY [ 0.014s]
sending 'boot' (6686 KB)...
OKAY [ 0.621s]
writing 'boot'...
OKAY [ 0.633s]
sending 'recovery' (7854 KB)...
OKAY [ 0.729s]
writing 'recovery'...
OKAY [ 0.735s]
erasing 'system'...
OKAY [ 0.525s]
sending sparse 'system' (62457 KB)...
OKAY [ 5.944s]
writing 'system'...
OKAY [ 6.902s]
sending sparse 'system' (62313 KB)...
OKAY [ 6.019s]
writing 'system'...
OKAY [ 6.534s]
sending sparse 'system' (61976 KB)...
OKAY [ 5.870s]
writing 'system'...
OKAY [ 6.255s]
sending sparse 'system' (61662 KB)...
OKAY [ 5.875s]
writing 'system'...
OKAY [ 6.031s]
sending sparse 'system' (57152 KB)...
OKAY [ 5.416s]
writing 'system'...
OKAY [ 5.403s]
sending sparse 'system' (60517 KB)...
OKAY [ 5.745s]
writing 'system'...
OKAY [ 7.129s]
sending sparse 'system' (59580 KB)...
OKAY [ 5.626s]
writing 'system'...
OKAY [ 5.526s]
sending sparse 'system' (58988 KB)...
OKAY [ 5.573s]
writing 'system'...
OKAY [ 5.526s]
sending sparse 'system' (10312 KB)...
OKAY [ 0.998s]
writing 'system'...
OKAY [ 1.068s]
erasing 'userdata'...
OKAY [ 0.749s]
sending 'userdata' (40964 KB)...
OKAY [ 3.751s]
writing 'userdata'...
OKAY [ 3.894s]
erasing 'cache'...
OKAY [ 0.165s]
sending 'cache' (10432 KB)...
OKAY [ 0.963s]
writing 'cache'...
OKAY [ 0.997s]
rebooting...
finished. total time: 111.323s
Press any key to exit...
8. Lock the bootloader:
Code:
fastboot oem lock
9. Pair your watch
Pair your watch to the Android Wear app on your phone. Unfortunately, it is necessary to continue.
10. Check for new firmware, step 1
Go to the Settings/System/About menu of the watch and select System updates. In my case the download of the new AW2.0 FW was in progress already, but you might need to check for a new firmware manually. Wait for the watch to install the new firmware. In my case it happened to be N7G75S, so I was a bit worried at this point about the successful outcome of step 11, since that FW never has successfully allowed the upgrade to the latest available one.
11. Check for new firmware, step 2
After having the new AW2.0 FW successfully upgraded, check for a new firmware again. Go to the Settings/System/About menu of the watch and select System updates. Wait for the new update to be installed.
12. FINAL DESTINATION
Finally! You should have by now under the Build number section the new firmware version NWD1.171016.002 or newer indicated! System is up to date. Check!
Let me know if I need to update this full description. It would I think help everyone, as only one post would have to be checked as a reference.
:victory:
Click to expand...
Click to collapse
Thanks for this, worked like a charm
Good morning -
Got to work this morning and wanted to flash the April update for the Pixel 2 XL.
I followed this guide:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
And after completing the flash (no errors reported in console), I now get "your device is corrupt" in red instead of the usual orange, and it will not complete a boot cycle. It will go to the Google logo, then run the same cycle again.
I downloaded the latest platform tools, as i saw that when searching for my error, and tried again. I still get the same result.
I suppose at this point I may need to add the -w and try again, but would like to see if this can be salvaged.
@Badger50 , any words of wisdom for a small brown idiot?
thanks
myk.robinson said:
Good morning -
Got to work this morning and wanted to flash the April update for the Pixel 2 XL.
I followed this guide:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
And after completing the flash (no errors reported in console), I now get "your device is corrupt" in red instead of the usual orange, and it will not complete a boot cycle. It will go to the Google logo, then run the same cycle again.
I downloaded the latest platform tools, as i saw that when searching for my error, and tried again. I still get the same result.
I suppose at this point I may need to add the -w and try again, but would like to see if this can be salvaged.
@Badger50 , any words of wisdom for a small brown idiot?
thanks
Click to expand...
Click to collapse
Your no idiot my friend. This kinda stuff just happens at times to all of us. Question, did you unlock_critical as well when you unlocked your phone?? If so, then I would try fastbooting the factory image again with the -w removed to both slots for starters to see if that works. If you need the fastboot commands, just let me know :good:
Badger50 said:
Your no idiot my friend. This kinda stuff just happens at times to all of us. Question, did you unlock_critical as well when you unlocked your phone?? If so, then I would try fastbooting the factory image again with the -w removed to both slots for starters to see if that works. If you need the fastboot commands, just let me know :good:
Click to expand...
Click to collapse
Any commands you wanna lay on me, bring it.
I just tried one more time, I added my platform tools directory to my PATH environment variable to make 100% sure that perhaps something went wonky with the commands.
Here's the output for what I have done:
Code:
c:\Users\mykro\Downloads\Pixel 2 XL\platform-tools-latest-windows\platform-tools\taimen-opm2.171019.029>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader' (36344 KB)...
OKAY [ 0.781s]
writing 'bootloader'...
OKAY [ 0.523s]
finished. total time: 1.320s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
target reported max download size of 536870912 bytes
sending 'radio' (60412 KB)...
OKAY [ 1.303s]
writing 'radio'...
OKAY [ 0.853s]
finished. total time: 2.156s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
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...: TMZ12bb
Baseband Version.....: g8998-00202-1802061358
Serial Number........: NOPE NOPE NOPE
--------------------------------------------
checking product...
OKAY [ -0.000s]
checking version-bootloader...
OKAY [ -0.000s]
checking version-baseband...
OKAY [ -0.000s]
sending 'boot' (40960 KB)...
OKAY [ 0.880s]
writing 'boot'...
OKAY [ 0.572s]
sending sparse 'system' (524284 KB)...
OKAY [ 12.073s]
writing 'system'...
OKAY [ 2.213s]
sending sparse 'system' (524284 KB)...
OKAY [ 12.094s]
writing 'system'...
OKAY [ 2.216s]
sending sparse 'system' (524284 KB)...
OKAY [ 12.078s]
writing 'system'...
OKAY [ 2.216s]
sending sparse 'system' (410816 KB)...
OKAY [ 9.406s]
writing 'system'...
OKAY [ 1.735s]
sending 'vendor' (354880 KB)...
OKAY [ 7.675s]
writing 'vendor'...
OKAY [ 1.506s]
rebooting...
finished. total time: 64.727s
Press any key to exit...
So yeah, i'd like some hand holding
thanks
Sorry, i failed to answer your question. Yes, I unlocked critical initially.
And to confirm, i had removed the -w and the flash-all.bat looks like this:
Code:
@ECHO OFF
:: Copyright 2012 The Android Open Source Project
::
:: Licensed under the Apache License, Version 2.0 (the "License");
:: you may not use this file except in compliance with the License.
:: You may obtain a copy of the License at
::
:: http://www.apache.org/licenses/LICENSE-2.0
::
:: Unless required by applicable law or agreed to in writing, software
:: distributed under the License is distributed on an "AS IS" BASIS,
:: WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
:: See the License for the specific language governing permissions and
:: limitations under the License.
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-taimen-tmz12bb.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-taimen-g8998-00202-1802061358.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot update image-taimen-opm2.171019.029.zip
echo Press any key to exit...
pause >nul
exit
myk.robinson said:
Any commands you wanna lay on me, bring it.
I just tried one more time, I added my platform tools directory to my PATH environment variable to make 100% sure that perhaps something went wonky with the commands.
Here's the output for what I have done:
So yeah, i'd like some hand holding
thanks
Click to expand...
Click to collapse
Do you have the secondary zip from the factory image in your platform-tools folder?? Also, instead of using a path to the platform-tools folder, I just go straight to it and double click the flash-all.bat file to get it started.
Badger50 said:
Do you have the secondary zip from the factory image in your platform-tools folder?? Also, instead of using a path to the platform-tools folder, I just go straight to it and double click the flash-all.bat file to get it started.
Click to expand...
Click to collapse
Perhaps I did something wrong here... Do I need to extract all the contents of the first .zip file into my platform tools folder? I extracted it all into a subfolder and ran the flash-all.bat from there, but I am now realizing that i also have a flash-all.bat in the platform tools folder as well, suggesting I did that the last time...
Is this where I went wrong?
I can't break it any more that it already is, so I'll compare directories, purge stuff in the platform-tools folder that is identical to what is in the factory image subfolder, then move the factory image stuff to the platform tools top level.
Looks like more stuff is flashing this time. Let's hope for the best
#dyslexia
@Badger50 is is booting up now. Looks like my problem was failure to extract the image into the root of the platform tools folder.
Thank you so much for being available and talking me through this
myk.robinson said:
@Badger50 is is booting up now. Looks like my problem was failure to extract the image into the root of the platform tools folder.
Thank you so much for being available and talking me through this
Click to expand...
Click to collapse
There ya go my friend. It's a mistake a lot of people make. Going forward, after you extract the factory image, you want to take the extracted contents and place them directly in the platform-tools folder, that will always include the....bootloader...radio...3 smaller files with the flash-all.bat being the most important for Windows users....and the large secondary zip that has all the other images in it. I'm old school and not that computer savy, which is why I manually navigate to the platform-tool folder and open my command prompt from that folder when I want to issue fastboot commands. Glad you got it figured out though. See, now your a pro ???
Badger50 said:
There ya go my friend. It's a mistake a lot of people make. Going forward, after you extract the factory image, you want to take the extracted contents and place them directly in the platform-tools folder, that will always include the....bootloader...radio...3 smaller files with the flash-all.bat being the most important for Windows users....and the large secondary zip that has all the other images in it. I'm old school and not that computer savy, which is why I manually navigate to the platform-tool folder and open my command prompt from that folder when I want to issue fastboot commands. Glad you got it figured out though. See, now your a pro
Click to expand...
Click to collapse
On behalf of all of us, I just want to say thank you Badger for owning a pixel 2 XL
danielrod said:
On behalf of all of us, I just want to say thank you Badger for owning a pixel 2 XL
Click to expand...
Click to collapse
Hahahahahaha...thanks my friend. I enjoy the crap outa this stuff :good::laugh:
Hello,
I have an LG Nexus 5X (Bullhead?) running PA 7.3.1-RELEASE (Android 7.1.2). It had PA installed on it when I purchased it from ebay some six months ago.
I really would like to go back to the original Google ROM but am struggling to do this.
I've downloaded SuperSU but when I run it I get "SuperSU SU Binary is occupied" and a "HOW TO SOLVE" button.
Clicking "HOW TO SOLVE" takes me to www supersu dot com faq subinaryoccupied which reassures me that: "Only needs a coffee's time to make it happen" and a Community link and Message Us link. Community Link returns a 502 Bad Gateway response (not very reassuring!), the Message Us link goes to a facebook group (SuperSUofficial). Is this route even worth entertaining? I feel I'm only at the tip of the iceberg in getting my phone returned to factory/OEM status.
Any advise would be most appreciated. (Sorry ,not allowed to post links as I'm under the 10 posts requirement)
Thanks, BloodBaz
Follow #10 in this guide, or #11 if you want to retain the contents of the phone's internal storage. You don't need SuperSU for anything.
Jacquestrapp said:
Follow #10 in this guide, or #11 if you want to retain the contents of the phone's internal storage. You don't need SuperSU for anything.
Click to expand...
Click to collapse
Thanks Jacquestrapp, that looks like exactly what I need. I'll give this a go this week and let you know how I get on. Thank you.
Jacquestrapp said:
Follow #10 in this guide, or #11 if you want to retain the contents of the phone's internal storage. You don't need SuperSU for anything.
Click to expand...
Click to collapse
Thanks Jacquestrapp. I'm struggling at the very first step.
Here's where I'm at:
Step 10 (How To Flash The Factory Images (And Return To Stock)) has the prerequsite that I have to unlock bootloader (section 1).
Gone to section 1
Enabled Developer mode (was already enabled)
Enabled OEM unlocking
Enabled USB debugging
Powered off phone
Booted into Bootloader (Power+Volume Down)
Connected phone to PC via USB cable
Opened command prompt, gone to platform tools but as you can see, I'm not connecting here:
Code:
C:\android\platform-tools>fastboot devices
C:\android\platform-tools>fastboot devices
C:\android\platform-tools>adb devices
List of devices attached
00cad250a0599972 device
C:\android\platform-tools>fastboot reboot
< waiting for any device >
My PC is the latest Windows 10 Pro (64-bit).
I have an LG Nexus 5X (Model LGH791).
And I'm guessing I've not got the right drivers installed but I'm struggling to find where to get them (I'm in the UK)
Here's where I've tried:
Attempt 1:
Followed the same guide to "Google USB Driver Install": https://developer.android.com/studio/run/win-usb.html
which takes me to: "Click here to download the Google USB Driver ZIP file (ZIP)" (latest_usb_driver_winodws.zip 8.3MB).
Downloaded, unzipped.
Gone to Device Manager but my phone doesn't appear under "Portable Devices" or anywhere else in device manager.
Attempt 2:
Gone to LG's website, entered model which lead to this page:
https://www.lg.com/uk/support/softw...00008356&subCateId=CT00008358&modelNum=LGH791
(but alas, no software!)
Can anyone advise on how to get the phone and PC to communicate?
Thanks
Chris
You mentioned that your phone has a custom ROM on it (Paranoid Android), which means it almost certainly has an unlocked bootloader. If you reboot the phone, the first thing you see when it reboots should be a message to this effect, advising you to lock the bootloader.
Jacquestrapp said:
You mentioned that your phone has a custom ROM on it (Paranoid Android), which means it almost certainly has an unlocked bootloader. If you reboot the phone, the first thing you see when it reboots should be a message to this effect, advising you to lock the bootloader.
Click to expand...
Click to collapse
Thanks, yes it does! Sorry, I not good at this. So the pre-req for section 10 is already done.
(I'm assuming I will still need to get adb / fastboot working at some point though).
I'll start looking into section 10 now. Thanks.
Are you connecting the phone to the PC through a USB hub? If so, try connecting directly to one of the PC's built-in USB ports. It's been a while since I first set up my PC for adb/fastboot so I'm not sure what to do about the fact that fastboot doesn't show the phone. I think I used the Android SDK manager, and not the ZIP file, to install the USB drivers.
Jacquestrapp said:
Are you connecting the phone to the PC through a USB hub? If so, try connecting directly to one of the PC's built-in USB ports. It's been a while since I first set up my PC for adb/fastboot so I'm not sure what to do about the fact that fastboot doesn't show the phone. I think I used the Android SDK manager, and not the ZIP file, to install the USB drivers.
Click to expand...
Click to collapse
No, directly onto USB port on top of PC. Tried both ports on top and a USB 3 port in the back. Still no sign of the phone in Device Manager.
I've got a laptop - I will try that next.
After that I will install the Android SDK manager (although I was hoping to avoid this for a one off job).
Thanks.
Okay, so I *think* my laptop is recognising the phone, however I still don't see the phone under Device Manager > Portable Devices or Device Manager > Other Devices (in fact, neither folder exists on my Laptop in Device Manager). However I have got "Nexus 5X" listed under Device Manager > USB Devices.
I'm now following instructions in section 10 of the guide you have given me:
"Download the latest build via the appropriate factory images for your model (Nexus 5X/Bullhead) here (https://developers.google.com/android/nexus/images?hl=en)".
For me this is 8.1.0 (OPM7.181005.003, Oct 2018) under "bullhead" (https://dl.google.com/dl/android/aosp/bullhead-opm7.181005.003-factory-e23fac1c.zip)
I've done the appropriate unzips and copies and I have the following folder set up:
Code:
Volume in drive C has no label.
Volume Serial Number is 1202-7717
Directory of C:\android\images
19/10/2018 22:55 <DIR> .
19/10/2018 22:55 <DIR> ..
01/01/2009 00:00 101 android-info.txt
01/01/2009 00:00 12,068,070 boot.img
21/09/2018 12:04 4,731,396 bootloader-bullhead-bhz31b.img
21/09/2018 12:04 57,989,632 radio-bullhead-m8994f-2.6.41.5.01.img
01/01/2009 00:00 17,847,530 recovery.img
01/01/2009 00:00 2,002,471,632 system.img
01/01/2009 00:00 194,892,768 vendor.img
7 File(s) 2,290,001,129 bytes
2 Dir(s) 136,452,927,488 bytes free
C:\android\images>
The next instruction is to "Boot into the bootloader and connect your phone to your PC via usb cable."
So I shut down my phone then booted it back up again using POWER +VOLUME DOWN buttons to get the screen with the big fat green START option and FASTBOOT mode showing
Connect USB cable to laptop and phone
BUT... now the device isn't showing anymore in Device Manager and running adb devices -l just says "List of devices attached" and nothing underneath!! Grrrrr!
Q1) Should the laptop still be able to communicate with the phone when the phone is booted into the bootloader?
Q2) Could there be something fundamentally wrong with the phone that is causing it not to be recognised?
Booting up the phone and disconnecting and connecting the phone a couple of times re-established the device. This time I was able to run adb reboot bootloader but as soon as the phone starts to shut down for the reboot, the connection to the laptop is lost and the laptop shows an error popup (temporarily) (wish I knew how to keep the popup visible but it was something about an error with the USB device).
Q3) Should I select RECOVERY MODE before I can expect the USB connection to reconnect? Documentation just says to go into bootloader (with the menu)
Any more advice is appreciated. Thanks, Chris
BloodBaz said:
The next instruction is to "Boot into the bootloader and connect your phone to your PC via usb cable."
So I shut down my phone then booted it back up again using POWER +VOLUME DOWN buttons to get the screen with the big fat green START option and FASTBOOT mode showing
Connect USB cable to laptop and phone
BUT... now the device isn't showing anymore in Device Manager and running adb devices -l just says "List of devices attached" and nothing underneath!! Grrrrr!
Click to expand...
Click to collapse
That last command should be fastboot devices, not adb devices.
BloodBaz said:
Q1) Should the laptop still be able to communicate with the phone when the phone is booted into the bootloader?
Click to expand...
Click to collapse
Yes, but using fastboot commands, not adb commands. With the phone in bootloader mode (the green screen with the big Start sign), you should see it listed after the fastboot devices command. Here's what I see:
Code:
C:\adb>fastboot devices
00bc94d02c6ab546 fastboot
BloodBaz said:
Q2) Could there be something fundamentally wrong with the phone that is causing it not to be recognised?
Click to expand...
Click to collapse
The phone's type-C port can collect lint, and plugging the connector into the phone compacts the lint. Over time, the lint layer can build up to the point where the connector no longer makes full contact with the port. I don't think that's your problem though.
@Jacquestrapp, thank you for your replies. You've been a life line.
After a couple of hours I think I've now managed to do it. I've tried two laptops, multiple USB ports and two USB cables. Whatever is happening, the PC/Phone connection seems very tempremental and I have to unplug and replug in the USB cable after each reboot. However, as you say, the fastboot commands did work after I figured this out, and from the fastboot screen. Also, whenever the phone rebooted or I disconnected the USB cable, the error message was as per attached screenshot.
So, I ran the following commands:
Code:
C:\android\platform-tools>adb devices -l
List of devices attached
00cad250a0599972 recovery product:omni_bullhead model:Nexus_5X device:bullhead transport_id:5
C:\android\platform-tools>fastboot flash bootloader C:\android\images\bootloader-bullhead-bhz31b.img
< waiting for any device >
Sending 'bootloader' (4620 KB) OKAY [ 0.212s]
Writing 'bootloader' OKAY [ 0.238s]
Finished. Total time: 0.493s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader OKAY [ 0.009s]
Finished. Total time: 0.011s
C:\android\platform-tools>fastboot flash radio C:\android\images\radio-bullhead-m8994f-2.6.41.5.01.img
< waiting for any device >
Sending 'radio' (56630 KB) OKAY [ 1.633s]
Writing 'radio' OKAY [ 0.543s]
Finished. Total time: 2.300s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader OKAY [ 0.013s]
Finished. Total time: 0.014s
C:\android\platform-tools>fastboot flash boot C:\android\images\boot.img
< waiting for any device >
Sending 'boot' (11785 KB) OKAY [ 0.538s]
Writing 'boot' OKAY [ 0.133s]
Finished. Total time: 0.786s
C:\android\platform-tools>
C:\android\platform-tools>fastboot flash recovery C:\android\images\recovery.img
Sending 'recovery' (17429 KB) OKAY [ 0.545s]
Writing 'recovery' OKAY [ 0.309s]
Finished. Total time: 0.900s
C:\android\platform-tools>fastboot flash system C:\android\images\system.img
Sending sparse 'system' 1/4 (508768 KB) OKAY [ 13.739s]
Writing sparse 'system' 1/4 OKAY [ 9.283s]
Sending sparse 'system' 2/4 (524230 KB) OKAY [ 14.787s]
Writing sparse 'system' 2/4 OKAY [ 8.650s]
Sending sparse 'system' 3/4 (501070 KB) OKAY [ 14.592s]
Writing sparse 'system' 3/4 OKAY [ 12.445s]
Sending sparse 'system' 4/4 (421469 KB) OKAY [ 11.842s]
Writing sparse 'system' 4/4 OKAY [ 16.174s]
Finished. Total time: 112.698s
C:\android\platform-tools>fastboot flash vendor C:\android\images\vendor.img
Sending 'vendor' (190324 KB) OKAY [ 5.424s]
Writing 'vendor' OKAY [ 5.682s]
Finished. Total time: 11.145s
C:\android\platform-tools>fastboot reboot
Rebooting
Finished. Total time: 0.012s
The pre-google animation too ages and eventually talked about corruption on the filesystem. This is presumably because it had Paranoid Android installed on it previously. So I took the option to wipe everything (I don't have anything precious on the phone that isn't already backed up) and I've got myself back to stock Google and I'm very happy!
Thanks again for your support @Jacquestrapp.
The only thing I haven't done yet is relock the bootloader.
The guide states this warning:
"Important: do not relock your bootloader unless your phone is fully stock. You must flash the factory images first in order to remove root and custom recovery (if you have them), if this precaution isn't taken you may end up with a brick. Please see section 10 of this guide for full instructions on how to return to stock"
Now that I am booting up fine in standard Google Android 8.1, is it okay for me to issue the fastboot oem lock command? I'm not going to kill my phone am I? If it's a "yes", then I'll probably leave it a few days before I actually do it.
Thanks
BloodBaz said:
[MENTION=301158]
The only thing I haven't done yet is relock the bootloader.
The guide states this warning:
"Important: do not relock your bootloader unless your phone is fully stock. You must flash the factory images first in order to remove root and custom recovery (if you have them), if this precaution isn't taken you may end up with a brick. Please see section 10 of this guide for full instructions on how to return to stock"
Now that I am booting up fine in standard Google Android 8.1, is it okay for me to issue the fastboot oem lock command? I'm not going to kill my phone am I? If it's a "yes", then I'll probably leave it a few days before I actually do it.
Thanks
Click to expand...
Click to collapse
You're welcome. I *think* you are OK to re-lock the bootloader, but I've never done it, so I can't say with 100% certainty. Both of the 5Xs in my house have been running custom ROMs since I bought them. Also, if the USB connection is as temperamental as you say, take a toothpick (or something else thin and non-conductive) and poke around gently in the USB port to see if lint is the problem. It probably isn't, but it's easy enough to fix if it is: just dig all the lint out.
Okay, I've seen similar problems to mine but none of the suggested solutions seem to work out the problem. This seems to be the recommended solution, but it's not getting me anywhere:
https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
My bootloader is unlocked. I unlocked it the second I got the phone to save pain down the road. I've now hit the fork. It's an unlocked phone, not Verizon, I'm not sure what the original carrier was, it was second-hand and under no warranty. I'm on Android 10 Marlin, I updated it to the latest about a month ago. I got up to do some laundry last night and came back to a spontaneously dead phone. For detail, I was transferring a movie to my phone via USB to internal storage so I could watch it later. No idea what happened while I was up, but the phone was in the exact same position as when I left. Developer options were on, USB debugging was on.
What I have now is this: It will enter fastboot. When I prompt it to boot to recovery, it shuts down, or it will go to the unlocked bootloader warning screen, allow me to pause/continue booting, at which point it will either go directly to black, or briefly show the Google bootloader and then shut off. When I leave it on a charge, either trickle or full, it will sometimes loop through the unlocked bootloader warning, flicking that screen on and off, but sometimes it's just off. I never see the charging battery screen. I've left it to charge for hours.
Sometimes windows acknowledges a USB device is connected and that it's android, but at no point can I access storage. When working through a command line prompt, acknowledges that the device is there, but trying to flash anything fails immediately. Here is a sample of some of my results.
When trying the flash-all solution:
PHP:
Sending 'bootloader_b' (32480 KB) OKAY [ 1.779s]
Writing 'bootloader_b' FAILED (remote: 'Verify bootloader image failed on production device.')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.040s]
Finished. Total time: 0.044s
The device goes black. I'll bring it back up to fastboot and the command line spits this out:
PHP:
< waiting for any device >
Sending 'radio_b' (57156 KB) OKAY [ 3.785s]
Writing 'radio_b' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.199s]
Finished. Total time: 0.207s
Using fastboot to try and boot factory bootloader, it says it's worked but then the phone again just goes to black and does nothing:
PHP:
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot boot bootloader-marlin-8996-012001-1908071822.img
< waiting for any device >
creating boot image...
creating boot image - 33261568 bytes
Sending 'boot.img' (32482 KB) OKAY [ 2.100s]
Booting OKAY [ 0.531s]
Finished. Total time: 2.944s
Flashing that factory bootloader, seems successful, again, back to black screen and nothing until going back to fastboot:
PHP:
>> PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot boot bootloader-marlin-8996-012001-1908071822.img
>> < waiting for any device >
>> creating boot image...
>> creating boot image - 33261568 bytes
>> Sending 'boot.img' (32482 KB) OKAY [ 2.100s]
>> Booting OKAY [ 0.531s]
>> Finished. Total time: 2.944s
And finally, trying to push an update image over fastboot:
PHP:
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot update image-marlin-qp1a.191005.007.a3.zip
--------------------------------------------
Bootloader Version...: N/A
Baseband Version.....: N/A
Serial Number........: HT6AD0202367
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.044s]
Checking 'version-bootloader' FAILED
Device version-bootloader is 'N/A'.
Update requires '8996-012001-1908071822'.
fastboot: error: requirements not met!
I am wondering if locking the bootloader would give this thing what it wants and let me boot into recovery, but I have a terrible feeling it would just further lock me out of saving this phone. Does anyone have any insight? Is this a shot motherboard? Sorry, I know my problem has a ton of commonalities with a lot of other people's but it seems for all my searching, reading and Googling that it's idiosyncratic to the point of every solution not working for me. Thank you so much.
Edit: For interest, I just saw the screen throw up an odd block of static, for lack of a better term. In the bottom right corner, it took up a little more than 1/4 of the screen. It looked lik there was cut off text at the top, too little showing to read. It disappeared before I could take a picture with a spare phone. It lasted maybe 5 seconds and then it was gone. It's on USB charge, not sitting on fastboot right now.
ekjean said:
Okay, I've seen similar problems to mine but none of the suggested solutions seem to work out the problem. This seems to be the recommended solution, but it's not getting me anywhere:
https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
My bootloader is unlocked. I unlocked it the second I got the phone to save pain down the road. I've now hit the fork. It's an unlocked phone, not Verizon, I'm not sure what the original carrier was, it was second-hand and under no warranty. I'm on Android 10 Marlin, I updated it to the latest about a month ago. I got up to do some laundry last night and came back to a spontaneously dead phone. For detail, I was transferring a movie to my phone via USB to internal storage so I could watch it later. No idea what happened while I was up, but the phone was in the exact same position as when I left. Developer options were on, USB debugging was on.
What I have now is this: It will enter fastboot. When I prompt it to boot to recovery, it shuts down, or it will go to the unlocked bootloader warning screen, allow me to pause/continue booting, at which point it will either go directly to black, or briefly show the Google bootloader and then shut off. When I leave it on a charge, either trickle or full, it will sometimes loop through the unlocked bootloader warning, flicking that screen on and off, but sometimes it's just off. I never see the charging battery screen. I've left it to charge for hours.
Sometimes windows acknowledges a USB device is connected and that it's android, but at no point can I access storage. When working through a command line prompt, acknowledges that the device is there, but trying to flash anything fails immediately. Here is a sample of some of my results.
When trying the flash-all solution:
PHP:
Sending 'bootloader_b' (32480 KB) OKAY [ 1.779s]
Writing 'bootloader_b' FAILED (remote: 'Verify bootloader image failed on production device.')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.040s]
Finished. Total time: 0.044s
The device goes black. I'll bring it back up to fastboot and the command line spits this out:
PHP:
< waiting for any device >
Sending 'radio_b' (57156 KB) OKAY [ 3.785s]
Writing 'radio_b' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.199s]
Finished. Total time: 0.207s
Using fastboot to try and boot factory bootloader, it says it's worked but then the phone again just goes to black and does nothing:
PHP:
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot boot bootloader-marlin-8996-012001-1908071822.img
< waiting for any device >
creating boot image...
creating boot image - 33261568 bytes
Sending 'boot.img' (32482 KB) OKAY [ 2.100s]
Booting OKAY [ 0.531s]
Finished. Total time: 2.944s
Flashing that factory bootloader, seems successful, again, back to black screen and nothing until going back to fastboot:
PHP:
>> PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot boot bootloader-marlin-8996-012001-1908071822.img
>> < waiting for any device >
>> creating boot image...
>> creating boot image - 33261568 bytes
>> Sending 'boot.img' (32482 KB) OKAY [ 2.100s]
>> Booting OKAY [ 0.531s]
>> Finished. Total time: 2.944s
And finally, trying to push an update image over fastboot:
PHP:
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot update image-marlin-qp1a.191005.007.a3.zip
--------------------------------------------
Bootloader Version...: N/A
Baseband Version.....: N/A
Serial Number........: HT6AD0202367
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.044s]
Checking 'version-bootloader' FAILED
Device version-bootloader is 'N/A'.
Update requires '8996-012001-1908071822'.
fastboot: error: requirements not met!
I am wondering if locking the bootloader would give this thing what it wants and let me boot into recovery, but I have a terrible feeling it would just further lock me out of saving this phone. Does anyone have any insight? Is this a shot motherboard? Sorry, I know my problem has a ton of commonalities with a lot of other people's but it seems for all my searching, reading and Googling that it's idiosyncratic to the point of every solution not working for me. Thank you so much.
Edit: For interest, I just saw the screen throw up an odd block of static, for lack of a better term. In the bottom right corner, it took up a little more than 1/4 of the screen. It looked lik there was cut off text at the top, too little showing to read. It disappeared before I could take a picture with a spare phone. It lasted maybe 5 seconds and then it was gone. It's on USB charge, not sitting on fastboot right now.
Click to expand...
Click to collapse
First, do not repeat do not lock your boot loader.
Second, try this:
- Make sure you have the latest SDK Platform-tools installed on your computer r29.0.5.
There is a link for it in the guide below (Prerequisites c.).
- Make sure you plug the USB into a non charging USB port.
- Extract the boot.img (#6 in the guide brlow) from the Factory image you are currently using and flash it:
fastboot flash boot --slot all boot.img
or
fastboot flash boot boot.img --slot all
Guide
Homeboy76 said:
First, do not repeat do not lock your boot loader.
Second, try this:
- Make sure you have the latest SDK Platform-tools installed on your computer r29.0.5.
There is a link for it in the guide below (Prerequisites c.).
- Make sure you plug the USB into a non charging USB port.
- Extract the boot.img (#6 in the guide brlow) from the Factory image you are currently using and flash it:
fastboot flash boot --slot all boot.img
or
fastboot flash boot boot.img --slot all
Guide
Click to expand...
Click to collapse
Thank you thank you thank you for lending a hand. And for confirming that my temptation to lock the bootloader is a bad idea.
I have three ports on my laptop, I'm not sure any are non-charging. I'm selecting one that it wasn't attached to when the file transfer apparently went wrong.
Here goes nothing. I updated SDK tools last night during all this to be sure everything was kosher.
Unfortunately this was my result from all USB ports, testing both formats of the command:
PHP:
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.846s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.873s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) OKAY [ 0.936s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) OKAY [ 0.864s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.827s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.821s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.939s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3>
ekjean said:
Thank you thank you thank you for lending a hand. And for confirming that my temptation to lock the bootloader is a bad idea.
I have three ports on my laptop, I'm not sure any are non-charging. I'm selecting one that it wasn't attached to when the file transfer apparently went wrong.
Here goes nothing. I updated SDK tools last night during all this to be sure everything was kosher.
Unfortunately this was my result from all USB ports, testing both formats of the command:
PHP:
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.846s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.873s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) OKAY [ 0.936s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) OKAY [ 0.864s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.827s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.821s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.939s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3>
Click to expand...
Click to collapse
Are you using SDK Platform-tools r29.0.5?
Why? When you extract it it creates a Platform-tools folder.
Put this folder in PS C:\ so you have a
PS C:\Platform-tools folder.
Not: PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3>
That folder set up may be causing the to many links
error.
Then put the boot.img in the Platform-tools folder and do #6 in the guide.
Homeboy76 said:
Are you using SDK Platform-tools r29.0.5?
Why? When you extract it it creates a Platform-tools folder.
Put this folder in PS C:\ so you have a
PS C:\Platform-tools folder.
Not: PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3>
That folder set up may be causing the to many links
error.
Then put the boot.img in the Platform-tools folder and do #6 in the guide.
Click to expand...
Click to collapse
I was still working from the soft-bricked guide, where I had a copy of fastboot/platform tools pasted to everthing else. Not a problem at all to move Platform tools to C:/ Thank you!
I have noticed that what I have is r29.0.6. Should I roll it back? Assuming I should have the newest, I get the same result...
PHP:
PS C:\platform-tools> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) OKAY [ 1.729s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\platform-tools> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.788s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\platform-tools>
ekjean said:
I was still working from the soft-bricked guide, where I had a copy of fastboot/platform tools pasted to everthing else. Not a problem at all to move Platform tools to C:/ Thank you!
I have noticed that what I have is r29.0.6. Should I roll it back? Assuming I should have the newest, I get the same result...
PHP:
PS C:\platform-tools> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) OKAY [ 1.729s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\platform-tools> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.788s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\platform-tools>
Click to expand...
Click to collapse
No, do not roll back you have the latest version.
At this point I really don't know what will fix the problem but here are three long shots that might help/work:
1. Try fastboot flash boot boot.img. If that works. Do fastboot flash boot boot.img --slot other.
2. Download the latest Pixel or Pixel XL OTA image (which ever phone you have) and sideload it.
3. Do a Factory Reset. Settings => System => Advanced => Reset options => Erase all data (factory reset)
Good luck.
If none of them work, it could be a hardwear problem. Pixel/Pixel XL are failing because of age or manufacturing. I don't know which.
Homeboy76 said:
No, do not roll back you have the latest version.
At this point I really don't know what will fix the problem but hear are three long shots that might help/work:
1. Try fastboot flash boot boot.img. If that works. Do fastboot flash boot boot.img --slot other.
2. Download the latest Pixel or Pixel XL OTA image (which ever phone you have) and sideload it.
3. Do a Factory Reset. Settings => System => Advanced => Reset options => Erase all data (factory reset)
Good luck.
If none of them work, it could be a hardwear problem. Pixel/Pixel XL are failing because of age or manufacturing. I don't know which.
Click to expand...
Click to collapse
Sadly, anything that requires ADB/recovery is cut off to me, and so is anything that requires the actual OS interface, so accessing settings and factory resetting is out, and so is sideloading. All I can work from is fastboot.
The final option you had gave me another write failure. Thank you for working with me on this - this is my favorite phone I've ever had, and it may be time to eulogize it. I appreciate all you ran me through. <3
ekjean said:
Sadly, anything that requires ADB/recovery is cut off to me, and so is anything that requires the actual OS interface, so accessing settings and factory resetting is out, and so is sideloading. All I can work from is fastboot.
The final option you had gave me another write failure. Thank you for working with me on this - this is my favorite phone I've ever had, and it may be time to eulogize it. I appreciate all you ran me through. <3
Click to expand...
Click to collapse
RIP Pixel/Pixel XL!
hey bruh, try to cooling it in the freezer, my pixel xl turned on that way, give it a shot
@mateodiaz802 said:
hey bruh, try to cooling it in the freezer, my pixel xl turned on that way, give it a shot
Click to expand...
Click to collapse
Maybe I will! Did it stay on?
it will stay on the enough time to recover your data
@mateodiaz802 said:
hey bruh, try to cooling it in the freezer, my pixel xl turned on that way, give it a shot
Click to expand...
Click to collapse
I'm afraid in my case this was the death blow. Let out a few buzzes when attempting to power into fastboot, flashed a red light at the top and then nothing. She was euthanized by freezer around 5PM, 3/2/20, went quietly into that good night surrounded by friends and family at home. RIP Pixel.
did you cover the phone holes like the charging port and aux jack? I forgot to mention because I thought it was obvious
@mateodiaz802 said:
did you cover the phone holes like the charging port and aux jack? I forgot to mention because I thought it was obvious
Click to expand...
Click to collapse
I wrapped 'er in plastic wrap before putting it in. So it would've been covered. Oh well, stuff happens. Funny thing, I tried it again just to see. It started vibrating and hasn't stopped. XD
i covered the holes with tape, it's more effective, also you should try booting it with "start" optino from the bootloader