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:
Related
Here's a video tutorial guide for noobs who want to unroot/unbrick your Nexus 10.
Drivers: http://stockroms.net/file/Drivers/android/usb_driver.zip
fastboot for Windows/Mac/Linux: http://downloadandroidrom.com/file/tools/fastboot.zip
Stock Firmware: http://stockroms.net/file/Nexus10
For Windows, type: (XXX may depend on the stock firmware)
Code:
fastboot flash bootloader bootloader-XXX.img
fastboot reboot-bootloader
fastboot flash radio radio-XXX-XXX.img
fastboot reboot-bootloader
fastboot -w update image-XXX-XXX.zip
For Mac OSX, type: (XXX may depend on the stock firmware)
Code:
./fastboot-mac flash bootloader bootloader-XXX.img
./fastboot-mac reboot-bootloader
./fastboot-mac flash radio radio-XXX-XXX.img
./fastboot-mac reboot-bootloader
./fastboot-mac -w update image-XXX-XXX.zip
For Linux, type: (XXX may depend on the stock firmware)
Code:
./fastboot-linux flash bootloader bootloader-XXX.img
./fastboot-linux reboot-bootloader
./fastboot-linux flash radio radio-XXX-XXX.img
./fastboot-linux reboot-bootloader
./fastboot-linux -w update image-XXX-XXX.zip
*Note – If you do not have radio image, you can skip that one.
*Note for Mac/Linux – If you get permissions error, try “chmod 755 *” before doing all the commands and also try adding “sudo” in front of the commands if you still have trouble.
Step-by-Step guide with photos here
for some reason after doing the last step it automatically reboots and it ends up with an android with a triangle with an exclamation point ...help?
jarjar124 said:
for some reason after doing the last step it automatically reboots and it ends up with an android with a triangle with an exclamation point ...help?
Click to expand...
Click to collapse
Try pressing power, volumeup, and volumedown, all together until you see the blue menus, once you see that, do a factory reset and reboot.
zedomax said:
Try pressing power, volumeup, and volumedown, all together until you see the blue menus, once you see that, do a factory reset and reboot.
Click to expand...
Click to collapse
doesnt that bring me to the bootloader?
edit: now i cant mount sd card in recovery after doing this....i think this is why its not booting....any help?
Don't we need do the following code before unroot?
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
if you really bricked yours as badly as I did, you might have to re format one or more partitions.
Fastboot format partitionname
Then fastboot flash partitionname imagefilename.
Sent from my Nexus 10 using xda premium
padest.com said:
Don't we need do the following code before unroot?
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Click to expand...
Click to collapse
Don't think so, it overwrites everything so i don't think it matters.
I've fully flashed the factory image and it just sits there seemingly looping.
I've flashed the stock recovery, from Stockroms . net, the bootloader and image from the Google Developers page and it still just sits there.
Anyone have any ideas?
I've also tried erasing all partitions and then flashing again. Right now i`m willing to try anything
Why not link to the official source?
https://developers.google.com/android/nexus/images#mantaray
H3g3m0n said:
Why not link to the official source?
https://developers.google.com/android/nexus/images#mantaray
Click to expand...
Click to collapse
Also doesn't the official archive even come with a batch file that does all the necessary commands automatically? The latest pre-4.2 image from Google for the Nexus 7 did anyway.
padest.com said:
Don't we need do the following code before unroot?
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Click to expand...
Click to collapse
The batch file I mentioned above for the N7 did this, and a guide somewhere else written before said that this was necessary due to some bug in the past (I guess something wasn't being overwritten properly).
Hmm, I did just the 'fastboot -w update image-mantaray-jop40c.zip' since I didn't want to mess with the bootloader, just reflash the stock rom.
Got the red triangle with !, rebooted and still got it, but after a few minutes it rebooted by itself and worked. Hopefully it was just doing some kind of first boot thing or wiping stuff.
EDIT: Also seems to have flashed over my recovery, but no biggie.
Where did I go wrong?
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\DMR>cd Downloads
C:\Users\DMR\Downloads>cd fastboot
The system cannot find the path specified.
C:\Users\DMR\Downloads>cd fastbot
The system cannot find the path specified.
C:\Users\DMR\Downloads>cd fastboot
C:\Users\DMR\Downloads\fastboot>fastboot flash bootloader bootloader-manta-ma
ntalj12.img
sending 'bootloader' (1280 KB)...
OKAY [ 0.157s]
writing 'bootloader'...
OKAY [ 0.137s]
finished. total time: 0.295s
C:\Users\DMR\Downloads\fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
C:\Users\DMR\Downloads\fastboot>fastboot -w update image-mantaray-jop40c.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CA04NW1T
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
sending 'boot' (4606 KB)...
OKAY [ 0.573s]
writing 'boot'...
OKAY [ 0.131s]
sending 'recovery' (5106 KB)...
OKAY [ 0.637s]
writing 'recovery'...
OKAY [ 0.138s]
sending 'system' (528847 KB)...
OKAY [ 65.906s]
writing 'system'...
OKAY [ 14.811s]
erasing 'userdata'...
OKAY [ 0.231s]
erasing 'cache'...
OKAY [ 0.034s]
rebooting...
finished. total time: 82.474s
C:\Users\DMR\Downloads\fastboot>
Click to expand...
Click to collapse
espionage724 said:
Also doesn't the official archive even come with a batch file that does all the necessary commands automatically? The latest pre-4.2 image from Google for the Nexus 7 did anyway.
Click to expand...
Click to collapse
Here is exactly what the batch file from Google says:
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-manta-mantalj12.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-mantaray-jop40c.zip
echo Press any key to exit...
pause >nul
exit
Mine does same thing
t-mizzle said:
Where did I go wrong?
Click to expand...
Click to collapse
Reboots after erasing cache and then will hang on Nexus X screen forever. Any extra steps or commands to assist?
Not working...
So I somehow bricked my N10 (all I did was flash CWM recovery, and then I couldn't mount /sdcard and it bootloops) so I tried this.
I get this:
Code:
% fastboot-mac -w update image-mantaray-jop40c.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB01971P
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
sending 'boot' (4606 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (5106 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (528847 KB)... ERROR: usb_write failed with status e00002be
FAILED (data transfer failure (No such file or directory))
Anyone have any ideas?...
format?
fastboot help file doesn't show format, it is erase <partition>
Is that the correct command?
c0t0d0s2 said:
if you really bricked yours as badly as I did, you might have to re format one or more partitions.
Fastboot format partitionname
Then fastboot flash partitionname imagefilename.
Sent from my Nexus 10 using xda premium
Click to expand...
Click to collapse
---------- Post added at 10:38 PM ---------- Previous post was at 10:07 PM ----------
t-mizzle said:
Where did I go wrong?
Click to expand...
Click to collapse
So I was kind of stuck at same spot you were I believe, where after the cache the device autorebooted and then hung on the splash screen.
I booted into the (now) stock recovery and formatted and wiped cache and it booted up fine. Hope you have the same luck.
I did exaclty what the OP said and I am at the boot up boot image of the X that is multi color and it just loops there.
I'm still stuck in bootloop. Entering recovery from fastboot brings up the laying android icon with the red triangle/exclamation mark.
What steps do I take next?
t-mizzle said:
I'm still stuck in bootloop. Entering recovery from fastboot brings up the laying android icon with the red triangle/exclamation mark.
What steps do I take next?
Click to expand...
Click to collapse
Press power and volume up and let go, you'll get various recovery options. Select wipe data and confirm. It'll wipe, then reboot.
Hatman41 said:
Press power and volume up and let go, you'll get various recovery options. Select wipe data and confirm. It'll wipe, then reboot.
Click to expand...
Click to collapse
Looks like today I'm more stupid than usually. I tried pressing power and volume up both in fastboot and in recovery mode, neither gave me recovery options. I know I am close but I can't nail it...
Hey guys, I've Pixel 2 XL and I'm trying to flash the factory images on the phone using flash-all.bat. I had 8.1 earlier and was doing some tests with custom ROM and then wanted to start afresh. So I did these steps:
1. downloaded the factory image [taimen-opm1.171019.011-factory-2df1c1cb] from here.
2. Extracted it in a folder
3. Downloaded latest platform tools from here and extracted it to same folder
4. Opened command prompt and ran flash-all.bat
5. It flashed radio, bootloader and then while flashing system.img, it gave this error:
extracting system.img (1936 MB) to disk...W/ziparchive( 4084): Zip: unable to truncate file to 2030555488: File too large
Here is the full log:
Code:
The system cannot find message text for message number 0x2350 in the message fil
e for Application.
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
Not enough storage is available to process this command.
D:\Pixel 2 XL\nitin>fastboot --version
fastboot version 0.0.1-4500957
Installed as D:\Pixel 2 XL\nitin\fastboot.exe
D:\Pixel 2 XL\nitin>fastboot devices
710KPJP0210052 fastboot
D:\Pixel 2 XL\nitin>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_a' (36344 KB)...
OKAY [ 1.170s]
writing 'bootloader_a'...
OKAY [ 0.379s]
finished. total time: 1.551s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
target reported max download size of 536870912 bytes
sending 'radio_a' (60428 KB)...
OKAY [ 1.967s]
writing 'radio_a'...
OKAY [ 0.571s]
finished. total time: 2.540s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.226s
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.037s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1936 MB) to disk...W/ziparchive( 4084): Zip: unable to truncate file to 2030555488: File too large
error:
failed to extract 'system.img': I/O error
Press any key to exit...
Any clues? I tried running the command prompt as an Admin to no avail. I know I can flash all imgs manually (and it works without any problems) but why am I getting that error?
Edit:
This was occuring due to low space on C:\drive (it seems it extracts the system.img before sending it to phone). Thanks to @stevexyz0 for the solution!
Is the disk on your PC out of space? Looks like it's trying to unzip the image before sending it to the phone.
Sent from my Pixel 2 XL using Tapatalk
stevexyz0 said:
Is the disk on your PC out of space? Looks like it's trying to unzip the image before sending it to the phone.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Man, you are awesome! :laugh::laugh::highfive::highfive:
I had the factory images on D:\ drive which had 70GB free; but the C:\ drive had only 1 GB. And I think as you rightly said, it extracts the system.img on PC and that too on C:\ drive (may be in Temp older)
I made the space on C:\ drive and it worked like a charm. Thanks once again!
Nitin
A custom ROM sounds yummy!
nitin.chobhe said:
Hey guys, I've Pixel 2 XL and I'm trying to flash the factory images on the phone using flash-all.bat. I had 8.1 earlier and was doing some tests with custom ROM and then wanted to start afresh. So I did these steps:
1. downloaded the factory image [taimen-opm1.171019.011-factory-2df1c1cb] from here.
2. Extracted it in a folder
3. Downloaded latest platform tools from here and extracted it to same folder
4. Opened command prompt and ran flash-all.bat
5. It flashed radio, bootloader and then while flashing system.img, it gave this error:
extracting system.img (1936 MB) to disk...W/ziparchive( 4084): Zip: unable to truncate file to 2030555488: File too large
Here is the full log:
Code:
The system cannot find message text for message number 0x2350 in the message fil
e for Application.
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
Not enough storage is available to process this command.
D:\Pixel 2 XL\nitin>fastboot --version
fastboot version 0.0.1-4500957
Installed as D:\Pixel 2 XL\nitin\fastboot.exe
D:\Pixel 2 XL\nitin>fastboot devices
710KPJP0210052 fastboot
D:\Pixel 2 XL\nitin>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_a' (36344 KB)...
OKAY [ 1.170s]
writing 'bootloader_a'...
OKAY [ 0.379s]
finished. total time: 1.551s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
target reported max download size of 536870912 bytes
sending 'radio_a' (60428 KB)...
OKAY [ 1.967s]
writing 'radio_a'...
OKAY [ 0.571s]
finished. total time: 2.540s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.226s
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.037s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1936 MB) to disk...W/ziparchive( 4084): Zip: unable to truncate file to 2030555488: File too large
error:
failed to extract 'system.img': I/O error
Press any key to exit...
Any clues? I tried running the command prompt as an Admin to no avail. I know I can flash all imgs manually (and it works without any problems) but why am I getting that error?
Edit:
This was occuring due to low space on C:\drive (it seems it extracts the system.img before sending it to phone). Thanks to @stevexyz0 for the solution!
Click to expand...
Click to collapse
I'm getting this error if U try with manual command,
{ H:\taimen-pq1a.181105.017.a1\platform-tools> fastboot update H:\taimen-pq1a.181105.017.a1\platform-tools\image-taimen
-pq1a.181105.017.a1.zip
error: failed to load 'H:\taimen-pq1a.181105.017.a1\platform-tools\image-taimen-pq1a.181105.017.a1.zip': Not enough space }
I'm getting this error if U try with flash-all command,
target reported max download size of 536870912 bytes
sending 'bootloader' (36336 KB)...
OKAY [ 0.789s]
writing 'bootloader'...
OKAY [ 0.375s]
finished. total time: 1.164s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
target reported max download size of 536870912 bytes
sending 'radio' (60388 KB)...
OKAY [ 1.304s]
writing 'radio'...
OKAY [ 0.569s]
finished. total time: 1.878s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
error: failed to load 'image-taimen-pq1a.181105.017.a1.zip': Not enough space
Press any key to exit...
My drives are enough empty to perform this action as you can see below screen shot. I've kept these files in drive H:/
Please help here. @stevexyz0
I'm rooted from oct patch, and want to update to nov patch full OTA.
wow thank you
stevexyz0 said:
Is the disk on your PC out of space? Looks like it's trying to unzip the image before sending it to the phone.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
sheesh i tried flashing the new android 10 update and got the same error error above and man you saved me!!! omg thank you. spent hrs trying to see whats wrong and came across this post. i couldnt even get passed the google logo thought i bricked my pixel 3 xl!! thank you!!
nitin.chobhe said:
Man, you are awesome! :laugh::laugh::highfive::highfive:
I had the factory images on D:\ drive which had 70GB free; but the C:\ drive had only 1 GB. And I think as you rightly said, it extracts the system.img on PC and that too on C:\ drive (may be in Temp older)
I made the space on C:\ drive and it worked like a charm. Thanks once again!
Nitin
Click to expand...
Click to collapse
hi ...i am getting this error while flashing ruu through my pc.....
sending 'zip'... (2426128 KB) FAILdata too large, 2484355788 > 1973424128
FAILED (data size is too large(2426128 KB) for device to download ZIP file 'rom.zip'
)
please helpppppppppppppp
Execution time is 2(s)
Novair said:
hi ...i am getting this error while flashing ruu through my pc.....
sending 'zip'... (2426128 KB) FAILdata too large, 2484355788 > 1973424128
FAILED (data size is too large(2426128 KB) for device to download ZIP file 'rom.zip'
)
please helpppppppppppppp
Execution time is 2(s)
Click to expand...
Click to collapse
Other than making sure you have enough space on your PC drives, we can't really help you. You'll need to ask your question in the HTC forums. Google devices don't use RUUs.
Novair said:
hi ...i am getting this error while flashing ruu through my pc.....
sending 'zip'... (2426128 KB) FAILdata too large, 2484355788 > 1973424128
FAILED (data size is too large(2426128 KB) for device to download ZIP file 'rom.zip'
)
please helpppppppppppppp
Execution time is 2(s)
Click to expand...
Click to collapse
A simple google search showed this as fist result: https://forum.xda-developers.com/t/q-cannot-flash-failed-remote-download-size-too-large.1286751/
Strephon Alkhalikoi said:
Other than making sure you have enough space on your PC drives, we can't really help you. You'll need to ask your question in the HTC forums. Google devices don't use RUUs.
Click to expand...
Click to collapse
I have 500gb free space on pc .......
But i think this error is because of allocated partition in device [(htv 10) htv32]
While I was attempting to flash the Nitrogen ROM I was having issues and ended up wiping my SD card. I got some help with restoring the ROM but realized I had flashed the wrong factory image along the way. I flashed the Fi image. So, as advised by the individual helping me, I tried flashing the correct factory files and I now cannot get past the white startup screen that says Google and shows the boot loader unlocked icon. I've tried the full factory restore and I get the same result. Was hoping I could get some help here.
This is what it sends back to me after I flash-all.bat
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-N950U using Tapatalk
I would suggest that you read and follow this Guide.
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Great Solid Info and you should be able to figure it out.
Good luck
chazall1 said:
I would suggest that you read and follow this Guide.
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Great Solid Info and you should be able to figure it out.
Good luck
Click to expand...
Click to collapse
While I do appreciate the advice, that's where I was when I was told to create a new post here. I've already done those steps and nothing.
Sent from my SM-N950U using Tapatalk
brackett5 said:
While I do appreciate the advice, that's where I was when I was told to create a new post here. I've already done those steps and nothing.
Sent from my SM-N950U using Tapatalk
Click to expand...
Click to collapse
This has saved my bacon more than once since Version 1:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Make extremely sure that your ADB/fastboot tools are up to date like today.
So...going off of what I was saying in [GUIDE] Unlock/Flash/Root for Pixel 2 XL (taimen) post #1753 (which can be found HERE), I'd like to try resetting/reformatting your system partition. The failure/error stated that it couldn't "determine partition type". I'm hoping by reformatting things, it'll set it correctly to that partition type it wants...
So, if you can prepare it as if you were going to install/flash a Full Factory image -- phone in bootloader mode, command prompt/powershell open, your platform-tools directory open (make sure it is the latest most up-to-date version of the platform-tools) where it shows fastboot and adb -- please input the following commands:
Code:
fastboot --version
*to make sure fastboot is working and to establish a connection
next I want to confirm some information... enter the command:
Code:
fastboot getvar all
*this will show which partitions aren't in the right format and what format we should reformat it in...
please copy and paste here (preferably in the CODE html tags) what it all returns...
Good luck to ya!
Also, @brackett5, you should request a forum moderator/administrator to move this to the Q&A section (I forgot to mention this when advising how to set up this thread) instead of this section... If anything and if any mods are listening, I concur in moving this to the Q&A section as @Az Biker mentioned in this post...Unless you would want brackett5 to create a whole new thread in that section, but leaving any/all the progress made here in this one.........
Sorry about that. I'll have to wait to see if anything works. I managed to also dump over my fiancees vase over into my laptop.
Sent from my SM-N950U using Tapatalk
This will be moved to the Help, Q & A section, as only Roms, Kernels, Recoveries, and other Mods currently being developed belong in this section, (as the title of this section suggests)
brackett5 said:
Sorry about that. I'll have to wait to see if anything works. I managed to also dump over my fiancees vase over into my laptop.
Click to expand...
Click to collapse
Eeek! I know I've been there! (not necessarily a vase but still...) Take ur time to get back here for ur issue after dealing with ur fiance, vase, and laptop...:silly:
Az Biker said:
This will be moved to the Help, Q & A section, as only Roms, Kernels, Recoveries, and other Mods currently being developed belong in this section, (as the title of this section suggests)
Click to expand...
Click to collapse
Again, you're the best! Thanks!
Sent from my Google Pixel 2 XL using XDA Labs
simplepinoi177 said:
So...going off of what I was saying in [GUIDE] Unlock/Flash/Root for Pixel 2 XL (taimen) post #1753 (which can be found HERE), I'd like to try resetting/reformatting your system partition. The failure/error stated that it couldn't "determine partition type". I'm hoping by reformatting things, it'll set it correctly to that partition type it wants...
So, if you can prepare it as if you were going to install/flash a Full Factory image -- phone in bootloader mode, command prompt/powershell open, your platform-tools directory open (make sure it is the latest most up-to-date version of the platform-tools) where it shows fastboot and adb -- please input the following commands:
Code:
fastboot --version
*to make sure fastboot is working and to establish a connection
next I want to confirm some information... enter the command:
Code:
fastboot getvar all
*this will show which partitions aren't in the right format and what format we should reformat it in...
please copy and paste here (preferably in the CODE html tags) what it all returns...
Good luck to ya!
Also, @brackett5, you should request a forum moderator/administrator to move this to the Q&A section (I forgot to mention this when advising how to set up this thread) instead of this section... If anything and if any mods are listening, I concur in moving this to the Q&A section as @Az Biker mentioned in this post...Unless you would want brackett5 to create a whole new thread in that section, but leaving any/all the progress made here in this one.........
Click to expand...
Click to collapse
Sorry, I have to send pics, I'm at work and won't connect to their WiFi.
Sent from my SM-N950U using Tapatalk
I know you're at work and things might not be all too flexible or available, but if you can temp boot into TWRP, do an Advanced Wipe of Dalvik / ART Cache, reboot to bootloader, and run the same flash-all.bat and attempt once again to flash the Full Factory image. Please copy and paste anything in the log of the flashing...
Good luck!
simplepinoi177 said:
I know you're at work and things might not be all too flexible or available, but if you can temp boot into TWRP, do an Advanced Wipe of Dalvik / ART Cache, reboot to bootloader, and run the same flash-all.bat and attempt once again to flash the Full Factory image. Please copy and paste anything in the log of the flashing...
Good luck!
Click to expand...
Click to collapse
target reported max download size of 536870912 bytes
sending 'bootloader' (36344 KB)...
OKAY [ 0.915s]
writing 'bootloader'...
OKAY [ 0.563s]
finished. total time: 1.477s
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.558s]
writing 'radio'...
OKAY [ 0.828s]
finished. total time: 2.464s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
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: 120909180928
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 29518843
Block groups: 901
Reserved block group size: 1024
Created filesystem with 11/7380992 inodes and 511380/29518843 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: TMZ12bb
Baseband Version.....: g8998-00202-1802061358
Serial Number........: $%^&*())_))_*^%$####
--------------------------------------------
checking product...
OKAY [ -0.000s]
checking version-bootloader...
OKAY [ 0.016s]
checking version-baseband...
OKAY [ 0.000s]
sending 'boot' (40960 KB)...
OKAY [ 1.125s]
writing 'boot'...
OKAY [ 0.531s]
sending sparse 'system' (524284 KB)...
OKAY [ 21.422s]
writing 'system'...
OKAY [ 2.203s]
sending sparse 'system' (524284 KB)...
OKAY [ 21.047s]
writing 'system'...
OKAY [ 2.219s]
sending sparse 'system' (524284 KB)...
OKAY [ 20.871s]
writing 'system'...
OKAY [ 2.203s]
sending sparse 'system' (411388 KB)...
OKAY [ 16.320s]
writing 'system'...
OKAY [ 1.734s]
sending 'vendor' (354904 KB)...
OKAY [ 9.344s]
writing 'vendor'...
OKAY [ 1.500s]
erasing 'userdata'...
OKAY [ 1.531s]
sending 'userdata' (144997 KB)...
OKAY [ 3.734s]
writing 'userdata'...
OKAY [ 1.672s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 107.614s
Press any key to exit...
Same results as before. It did let me boot into twrp though.
ok, so I decided to check if ADB is picking up my device and again, its not reading it. I checked it earlier and it was. Its not saying outdated, but when I type the cmd adb devices, it doesn't list it.
brackett5 said:
target reported max download size of 536870912 bytes
sending 'bootloader' (36344 KB)...
OKAY [ 0.915s]
writing 'bootloader'...
OKAY [ 0.563s]
finished. total time: 1.477s
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.558s]
writing 'radio'...
OKAY [ 0.828s]
finished. total time: 2.464s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
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: 120909180928
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 29518843
Block groups: 901
Reserved block group size: 1024
Created filesystem with 11/7380992 inodes and 511380/29518843 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: TMZ12bb
Baseband Version.....: g8998-00202-1802061358
Serial Number........: $%^&*())_))_*^%$####
--------------------------------------------
checking product...
OKAY [ -0.000s]
checking version-bootloader...
OKAY [ 0.016s]
checking version-baseband...
OKAY [ 0.000s]
sending 'boot' (40960 KB)...
OKAY [ 1.125s]
writing 'boot'...
OKAY [ 0.531s]
sending sparse 'system' (524284 KB)...
OKAY [ 21.422s]
writing 'system'...
OKAY [ 2.203s]
sending sparse 'system' (524284 KB)...
OKAY [ 21.047s]
writing 'system'...
OKAY [ 2.219s]
sending sparse 'system' (524284 KB)...
OKAY [ 20.871s]
writing 'system'...
OKAY [ 2.203s]
sending sparse 'system' (411388 KB)...
OKAY [ 16.320s]
writing 'system'...
OKAY [ 1.734s]
sending 'vendor' (354904 KB)...
OKAY [ 9.344s]
writing 'vendor'...
OKAY [ 1.500s]
erasing 'userdata'...
OKAY [ 1.531s]
sending 'userdata' (144997 KB)...
OKAY [ 3.734s]
writing 'userdata'...
OKAY [ 1.672s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 107.614s
Press any key to exit...
Same results as before. It did let me boot into twrp though.
Click to expand...
Click to collapse
...and u did this after wiping the cache in TWRP? And...just to confirm...you are using the most up to date platform-tools? Maybe re download them just in case...
Sent from my Google Pixel 2 XL using XDA Labs
simplepinoi177 said:
...and u did this after wiping the cache in TWRP? And...just to confirm...you are using the most up to date platform-tools? Maybe re download them just in case...
Sent from my Google Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
So, I've been doing some research and I was wondering; I had a version of ADB that I installed for use with Andromeda for my note 8, could this be interfering with it? I heard I have to remove it from my computer, but I've deleted it so I wonder how to do so.
Sent from my SM-N950U using Tapatalk
I downloaded the one you provided.
simplepinoi177 said:
...and u did this after wiping the cache in TWRP? And...just to confirm...you are using the most up to date platform-tools? Maybe re download them just in case...
Sent from my Google Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
Sent from my SM-N950U using Tapatalk
simplepinoi177 said:
...and u did this after wiping the cache in TWRP? And...just to confirm...you are using the most up to date platform-tools? Maybe re download them just in case...
Sent from my Google Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
It changed!!!!
Sent from my SM-N950U using Tapatalk
brackett5 said:
So, I've been doing some research and I was wondering; I had a version of ADB that I installed for use with Andromeda for my note 8, could this be interfering with it? I heard I have to remove it from my computer, but I've deleted it so I wonder how to do so.
Click to expand...
Click to collapse
Sorry...in the midst of a road trip...
I know I mentioned before to use the most up to date ADB/platform-tools (it's what causes like 80% of the troubles in this device's forum). But YES use a different ADB! And the most up to date one (r27.0.1) at that...
but yea changing this and using the URL I have might (or a good chance to) bear a different outcome...
Sent from my Google Pixel 2 XL using XDA Labs
Upon first glance, it looks like you have two things going on;
1) your files for flashing in fastboot are possibly not all in the correct platform tools folder with the fastboot application
your TWRP.IMG file, flash-all.bat, and your factory image files ALL need to be in the same platform tools folder as the fastboot application (.exe)
2) your SDK tools are the latest and greatest, you need to switch your USB cable (2.0 to 3.0 or 3.0 to 2.0) or change USB ports.
Try these things, report back
Az Biker said:
Upon first glance, it looks like you have two things going on;
1) your files for flashing in fastboot are possibly not all in the correct platform tools folder with the fastboot application
your TWRP.IMG file, flash-all.bat, and your factory image files ALL need to be in the same platform tools folder as the fastboot application (.exe)
2) your SDK tools are the latest and greatest, you need to switch your USB cable (2.0 to 3.0 or 3.0 to 2.0) or change USB ports.
Try these things, report back
Click to expand...
Click to collapse
They are all in the same folder. The flash-all.bat is in a sub folder in the platform tools. I'll try and send a video or pictures of howy set up is later.
Sent from my SM-N950U using Tapatalk
Az Biker said:
Upon first glance, it looks like you have two things going on;
1) your files for flashing in fastboot are possibly not all in the correct platform tools folder with the fastboot application
your TWRP.IMG file, flash-all.bat, and your factory image files ALL need to be in the same platform tools folder as the fastboot application (.exe)
2) your SDK tools are the latest and greatest, you need to switch your USB cable (2.0 to 3.0 or 3.0 to 2.0) or change USB ports.
Try these things, report back
Click to expand...
Click to collapse
You are my HERO!!!!!!!!!
Sent from my SM-N950U using Tapatalk
I just received my Android 10 update and after the update when it asked to reboot I tapped reboot and now it has been stuck in a continuous bootloop. My phone was not rooted or modded in any way. I was able to boot into the recovery selection menu but cant go into the actual recovery (it just says "no item" when I select recovery).
Any help/suggestions?
You can reflash the ROM using the full OTA package, as is stated by Google in https://developers.google.com/android/ota : This page contains full OTA update packages that allow you to restore your Nexus or Pixel device's original factory firmware. You will find these files useful if you have experienced a failure to take an OTA. This has the same effect as flashing the corresponding factory image, but without the need to wipe the device or unlock the bootloader." You also have in that page instructions of the whole process.
All you need to do is reboot into recovery, enter adb sideload mode from whitin it and send the zip OTA file using your PC and adb. Download QP1A.190711.020 version under Pixel 2 XL.
In order to boot into recovery, when you see the Android robot with the "no item" message keep pressed the power button and then short-press volume up until the recovery options show up.
It after that it's still failing, just format within recovery or flash the full firmware stock package.
fdgd1998 said:
You can reflash the ROM using the full OTA package, as is stated by Google in https://developers.google.com/android/ota : This page contains full OTA update packages that allow you to restore your Nexus or Pixel device's original factory firmware. You will find these files useful if you have experienced a failure to take an OTA. This has the same effect as flashing the corresponding factory image, but without the need to wipe the device or unlock the bootloader." You also have in that page instructions of the whole process.
All you need to do is reboot into recovery, enter adb sideload mode from whitin it and send the zip OTA file using your PC and adb. Download QP1A.190711.020 version under Pixel 2 XL.
In order to boot into recovery, when you see the Android robot with the "no item" message keep pressed the power button and then short-press volume up until the recovery options show up.
It after that it's still failing, just format within recovery or flash the full firmware stock package.
Click to expand...
Click to collapse
thank you for the helpful reply
i had already started the process and have already downloaded all the files
but i cant unlock the bootloader as it says in the tutorial
am i doing something wrong? or is there any way to flash without unlocking the bootloader?
Edit: I dont have the "oem unlock" option turned on.
PLZ HELP
areebiqbal said:
thank you for the helpful reply
i had already started the process and have already downloaded all the files
but i cant unlock the bootloader as it says in the tutorial
am i doing something wrong? or is there any way to flash without unlocking the bootloader?
Edit: I dont have the "oem unlock" option turned on.
PLZ HELP
Click to expand...
Click to collapse
Are you flashing the OTA or the full firmware? For the OTA bootloader unlock isn't necessary.
And in the instructions are stated the opposite, you must have misread it.
fdgd1998 said:
Are you flashing the OTA or the full firmware? For the OTA bootloader unlock isn't necessary.
And in the instructions are stated the opposite, you must have misread it.
Click to expand...
Click to collapse
hi, so luckily i had oem unlocking checked before this happened, but after the october update ive been stuck in bootloop.
ive tried both sideloading the ota in recovery, and also full firmware flash via fastboot.
after several attempts at both, i can't seem to access the recovery and bootloop persists.
any ideas?
[pixel sailfish never been rooted]
ku81na said:
hi, so luckily i had oem unlocking checked before this happened, but after the october update ive been stuck in bootloop.
ive tried both sideloading the ota in recovery, and also full firmware flash via fastboot.
after several attempts at both, i can't seem to access the recovery and bootloop persists.
any ideas?
[pixel sailfish never been rooted]
Click to expand...
Click to collapse
Have you looked into the Dueces recovery scrip?
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
no dice. appreciate the suggestion though
ku81na said:
no dice. appreciate the suggestion though
Click to expand...
Click to collapse
if you can confirm a couple things for me....
Are you actually getting into the recovery, but not seeing any "items"; because in stock recovery, you just see a broken/dead android image, and only get selections revealed/not-hidden but holding the volume-up & power button at the same time momentarily.
But, then again, you claim that you have attempted to "sideload the ota in recovery", so I imagine you already did this…but then, again again, you don’t describe what “error” or outcome actually happened and it could possibly be that, when you attempted, you just couldn’t or didn’t know how to get into the stock recovery…
Also, the recovery resides in the boot partition; I suggest you download the Full Factory image file (from the Google Developers site), extract it until you can find the boot.img, then manually flash it to overwrite and maybe fix the boot & recovery; to further explain, copy the extracted “boot.img” file to platform-tools folder where adb and fastboot reside, then run the command “fastboot flash boot boot.img” – although, if the flash-all is successfully executed, it would be doing this anyways…..
Which brings me to my next thing…if you could edit the “flash-all.bat” file and remove the word “exit” at the end – and for that matter, if you wish to save your data, remove the -w as well – and if you could please copy the output/log of you running the flash-all; usually this resolves everything & it all, so maybe it’s here that something is going wrong…
And running Deuce’s famous rescue script has saved/recovered countless people and their device (taimen)…it definitely is a good idea to attempt it…
But, then again, this is assuming that you made sure to run (and successfully execute) the fastboot command “fastboot flashing unlock” and/or (depending on your bootloader version) “fastboot flashing unlock_critical”.
Good luck, hopefully you can get back to me/us on some of this stuff, and hopefully all this ends up being helpful…
simplepinoi177 said:
if you can confirm a couple things for me....
Are you actually getting into the recovery, but not seeing any "items"; because in stock recovery, you just see a broken/dead android image, and only get selections revealed/not-hidden but holding the volume-up & power button at the same time momentarily.
But, then again, you claim that you have attempted to "sideload the ota in recovery", so I imagine you already did this…but then, again again, you don’t describe what “error” or outcome actually happened and it could possibly be that, when you attempted, you just couldn’t or didn’t know how to get into the stock recovery…
Also, the recovery resides in the boot partition; I suggest you download the Full Factory image file (from the Google Developers site), extract it until you can find the boot.img, then manually flash it to overwrite and maybe fix the boot & recovery; to further explain, copy the extracted “boot.img” file to platform-tools folder where adb and fastboot reside, then run the command “fastboot flash boot boot.img” – although, if the flash-all is successfully executed, it would be doing this anyways…..
Which brings me to my next thing…if you could edit the “flash-all.bat” file and remove the word “exit” at the end – and for that matter, if you wish to save your data, remove the -w as well – and if you could please copy the output/log of you running the flash-all; usually this resolves everything & it all, so maybe it’s here that something is going wrong…
And running Deuce’s famous rescue script has saved/recovered countless people and their device (taimen)…it definitely is a good idea to attempt it…
But, then again, this is assuming that you made sure to run (and successfully execute) the fastboot command “fastboot flashing unlock” and/or (depending on your bootloader version) “fastboot flashing unlock_critical”.
Good luck, hopefully you can get back to me/us on some of this stuff, and hopefully all this ends up being helpful…
Click to expand...
Click to collapse
yes i've tried everything you've suggested (flashing boot separately/removing exit from flash-all/running deuces script), however i haven't been able to access the recovery since i last messaged so i haven't been able to retry an ota flash from recovery. (the screen is all black and a green line of fuzz blinks across the middle of the screen when holding power and volume up) i did however get into it successfully once, and when i did there were no errors at all.
the strange thing is there are no errors when flashing either. it just does not get passed "Google" without rebooting. i just tried another flash-all after flashing unlock & unlock_critical so here is the full log in case im missing something:
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32480 KB)...
OKAY [ 0.847s]
writing 'bootloader_b'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_b"
(bootloader) Flashing active slot "_b"
OKAY [ 4.107s]
finished. total time: 4.965s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.051s
target reported max download size of 536870912 bytes
sending 'radio_b' (57156 KB)...
OKAY [ 1.434s]
writing 'radio_b'...
OKAY [ 0.458s]
finished. total time: 1.903s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.055s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
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
--------------------------------------------
Bootloader Version...: 8996-012001-1908071822
Baseband Version.....: 8996-130361-1905270421
Serial Number........: FXXXXXXXXXXX
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.046s]
checking version-baseband...
OKAY [ 0.046s]
sending 'boot_b' (30793 KB)...
OKAY [ 0.797s]
writing 'boot_b'...
OKAY [ 0.294s]
erasing 'system_b'...
OKAY [ 0.316s]
sending sparse 'system_b' 1/4 (524284 KB)...
OKAY [ 13.692s]
writing 'system_b' 1/4...
OKAY [ 3.460s]
sending sparse 'system_b' 2/4 (524284 KB)...
OKAY [ 13.802s]
writing 'system_b' 2/4...
OKAY [ 3.481s]
sending sparse 'system_b' 3/4 (524284 KB)...
OKAY [ 13.816s]
writing 'system_b' 3/4...
OKAY [ 3.451s]
sending sparse 'system_b' 4/4 (461052 KB)...
OKAY [ 11.950s]
writing 'system_b' 4/4...
OKAY [ 3.087s]
erasing 'system_a'...
OKAY [ 0.246s]
sending 'system_a' (298348 KB)...
OKAY [ 7.005s]
writing 'system_a'...
OKAY [ 2.036s]
erasing 'vendor_b'...
OKAY [ 0.112s]
sending 'vendor_b' (259272 KB)...
OKAY [ 6.400s]
writing 'vendor_b'...
OKAY [ 1.747s]
Setting current slot to 'b'...
OKAY [ 0.081s]
erasing 'userdata'...
OKAY [ 1.853s]
sending 'userdata' (138957 KB)...
OKAY [ 3.089s]
writing 'userdata'...
OKAY [ 1.293s]
rebooting...
finished. total time: 92.497s
Press any key to exit...
ku81na said:
yes i've tried everything you've suggested (flashing boot separately/removing exit from flash-all/running deuces script), however i haven't been able to access the recovery since i last messaged so i haven't been able to retry an ota flash from recovery. (the screen is all black and a green line of fuzz blinks across the middle of the screen when holding power and volume up) i did however get into it successfully once, and when i did there were no errors at all.
the strange thing is there are no errors when flashing either. it just does not get passed "Google" without rebooting. i just tried another flash-all after flashing unlock & unlock_critical so here is the full log in case im missing something:
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32480 KB)...
OKAY [ 0.847s]
writing 'bootloader_b'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_b"
(bootloader) Flashing active slot "_b"
OKAY [ 4.107s]
finished. total time: 4.965s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.051s
target reported max download size of 536870912 bytes
sending 'radio_b' (57156 KB)...
OKAY [ 1.434s]
writing 'radio_b'...
OKAY [ 0.458s]
finished. total time: 1.903s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.055s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
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
--------------------------------------------
Bootloader Version...: 8996-012001-1908071822
Baseband Version.....: 8996-130361-1905270421
Serial Number........: FXXXXXXXXXXX
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.046s]
checking version-baseband...
OKAY [ 0.046s]
sending 'boot_b' (30793 KB)...
OKAY [ 0.797s]
writing 'boot_b'...
OKAY [ 0.294s]
erasing 'system_b'...
OKAY [ 0.316s]
sending sparse 'system_b' 1/4 (524284 KB)...
OKAY [ 13.692s]
writing 'system_b' 1/4...
OKAY [ 3.460s]
sending sparse 'system_b' 2/4 (524284 KB)...
OKAY [ 13.802s]
writing 'system_b' 2/4...
OKAY [ 3.481s]
sending sparse 'system_b' 3/4 (524284 KB)...
OKAY [ 13.816s]
writing 'system_b' 3/4...
OKAY [ 3.451s]
sending sparse 'system_b' 4/4 (461052 KB)...
OKAY [ 11.950s]
writing 'system_b' 4/4...
OKAY [ 3.087s]
erasing 'system_a'...
OKAY [ 0.246s]
sending 'system_a' (298348 KB)...
OKAY [ 7.005s]
writing 'system_a'...
OKAY [ 2.036s]
erasing 'vendor_b'...
OKAY [ 0.112s]
sending 'vendor_b' (259272 KB)...
OKAY [ 6.400s]
writing 'vendor_b'...
OKAY [ 1.747s]
Setting current slot to 'b'...
OKAY [ 0.081s]
erasing 'userdata'...
OKAY [ 1.853s]
sending 'userdata' (138957 KB)...
OKAY [ 3.089s]
writing 'userdata'...
OKAY [ 1.293s]
rebooting...
finished. total time: 92.497s
Press any key to exit..
.
Click to expand...
Click to collapse
Curious....
I would suggest you try Deuce's script -- again, it has assisted and recovered countless taimens. And, if that doesn't help, I would suggest you try temporarily booting into TWRP custom recovery. If you do not know how to do that, download the TWRP .img file from twrp.me (you'll have to direct yourself to the Google Pixel 2 XL [taimen] section), put it where you put the flash-all and other image files, then run the fastboot command "fastboot boot twrp.img" (replace "twrp.img" with the actual filename of the twrp image file). There you can erase/format the system and/or other partitions, or even "repair" the filesystem! You can also run adb commands, so you might have some luck and be able to install/flash an OTA image file as well....
Good luck and hope this helps...!
Hello, I am trying to unroot my phone and relock the bootloader, but I am having some troubles.
After some trial and error with various forums guides here on XDA, I have been trying to use the Tool All in One, the MSM, but nothing is working. Furthermore, I am worried that I have bricked my phone.
The things I have done so far are:
Initially, I rooted the phone with Magisk. During this, I made a file that told my GPS to be where an application wanted it to be, and saved is a system file.
I have since decided to resell the phone and the buyer wants it to be stock. So, I tried the above mentioned tools of Tool All In one, and tried to flash a stock rom but it gave me an error.
I tried MSM but the device comes back as an error to do with serial number or something.
Whilst playing around with these tools, I have some how sent the phone into a permanent fastboot state and I am unable to reboot into any other state, and so I tried to use the guide found here, https://forum.xda-developers.com/t/...boot-roms-for-oneplus-7-pro-7-pro-5g.3931424/
This just lead to another failure, where it said I don't have the partitian.
If anyone can help me just get the phone to being a stock phone with no bootloader unlock, that would be great. Happy to chat over Discord if that helps!
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: c9c9ee59
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
android-info.txt syntax error: require product=msmnile
Setting current slot to 'a' OKAY [ 0.008s]
extracting boot.img (96 MB) to disk... took 0.262s
archive does not contain 'boot.sig'
Sending 'boot_a' (98304 KB) OKAY [ 2.328s]
Writing 'boot_a' OKAY [ 0.422s]
extracting dtbo.img (16 MB) to disk... took 0.038s
archive does not contain 'dtbo.sig'
Sending 'dtbo' (16384 KB) OKAY [ 0.399s]
Writing 'dtbo' OKAY [ 0.059s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta' (8 KB) OKAY [ 0.012s]
Writing 'vbmeta' OKAY [ 0.003s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'super_empty.img'
archive does not contain 'boot_other.img'
extracting odm.img (100 MB) to disk... took 0.227s
archive does not contain 'odm.sig'
Sending 'odm' (102400 KB) OKAY [ 2.426s]
Writing 'odm' FAILED (remote: '(odm_a) No such partition')
fastboot: error: Command failed
Press any key to exit...
This is what I get when I try to use https://forum.xda-developers.com/t/...boot-roms-for-oneplus-7-pro-7-pro-5g.3931424/
"fastboot reboot fastboot" to get into fastbootD and then reflash all partitions
In case anyone stumbles across this one day looking for a fix, I found one. My issue was that msm would not connect to sahara and tool all in one wouldn't lock the boot loader without the phone becoming corrupt. To make matters worse, through out all this I lost the ability to use adb and had to use fastboot, and even worse, I some how lost the os entirely and was only able to get into the boot loader.
So the fix for all of this, aka, how to get back to entirely stock software with no root or Bootloader unlocked is this:
1. Install lineageos recover and then os using fast boot so there is at least an operating system and ability to use adb again.
2. Start the phone entirely so you know it works
3. Go back to the bootloader and Install twrp recover
4. Format phone and then adb sideload oxygen os
5. boatload lock with Tool all in one
And wallah it was fixed. If someone needs to know the exact step by step I'm sure I might reply again one day but for now, I'm going to bed!