Update 7.1.1 Rooted XL to 7.1.2 Without Losing Data? - Google Pixel XL Questions & Answers

Please explain throughly and provide the download links, I've only had an android for a month and I am still learning the OS / Phone

tryfont said:
Please explain throughly and provide the download links, I've only had an android for a month and I am still learning the OS / Phone
Click to expand...
Click to collapse
Third post in the thread below. Just get the 7.1.2 full image instead of the 7.1.1 I mention in that post.
Pay attention to removing the -w from the flashall bat file. That is the key to saving your data.
And second to the last post in the thread are the​ instructions for getting root back.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242

SOLVED
TonikJDK said:
Third post in the thread below. Just get the 7.1.2 full image instead of the 7.1.1 I mention in that post.
Pay attention to removing the -w from the flashall bat file. That is the key to saving your data.
And second to the last post in the thread are the​ instructions for getting root back.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
Click to expand...
Click to collapse
I'm on a mac, not sure how to do the last step with running the .bat file
Edit: went into the bat file and ran the equivalent commands in terminal
(fastboot flash bootloader bootloader-marlin-8996-012001-1702151126.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-marlin-8996-012901-1702171013.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot update image-marlin-n2g47e.zip)
Here is the terminal messages I got
Last login: Mon Apr 3 18:00:13 on ttys000
Tryfons-MBP:~ tryfon$ cd /Users/tryfon/Desktop/platform-tools
Tryfons-MBPlatform-tools tryfon$ ./fastboot flash bootloader bootloader-marlin-8996-012001-1702151126.img
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32380 KB)...
OKAY [ 0.811s]
writing 'bootloader_b'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_b"
(bootloader) Flashing active slot "_b"
OKAY [ 4.163s]
finished. total time: 4.974s
Tryfons-MBPlatform-tools tryfon$ fastboot reboot-bootloader
-bash: fastboot: command not found
Tryfons-MBPlatform-tools tryfon$ ./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.046s
Tryfons-MBPlatform-tools tryfon$ fastboot flash radio radio-marlin-8996-012901-1702171013.img
-bash: fastboot: command not found
Tryfons-MBPlatform-tools tryfon$ ./fastboot flash radio radio-marlin-8996-012901-1702171013.img
target reported max download size of 536870912 bytes
sending 'radio_b' (57240 KB)...
OKAY [ 1.444s]
writing 'radio_b'...
OKAY [ 0.704s]
finished. total time: 2.148s
Tryfons-MBPlatform-tools tryfon$ ./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.050s
Tryfons-MBPlatform-tools tryfon$ ./fastboot update image-marlin-n2g47e.zip
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'
--------------------------------------------
Bootloader Version...: 8996-012001-1702151126
Baseband Version.....: 8996-012901-1702171013
Serial Number........: HT72A0200395
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.050s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boot_b' (25997 KB)...
OKAY [ 0.701s]
writing 'boot_b'...
OKAY [ 0.260s]
erasing 'system_b'...
OKAY [ 0.457s]
sending sparse 'system_b' 1/4 (514854 KB)...
OKAY [ 14.106s]
writing 'system_b' 1/4...
OKAY [ 6.005s]
sending sparse 'system_b' 2/4 (524140 KB)...
OKAY [ 14.606s]
writing 'system_b' 2/4...
OKAY [ 4.937s]
sending sparse 'system_b' 3/4 (512784 KB)...
OKAY [ 14.072s]
writing 'system_b' 3/4...
OKAY [ 6.243s]
sending sparse 'system_b' 4/4 (32756 KB)...
OKAY [ 0.905s]
writing 'system_b' 4/4...
OKAY [ 0.297s]
erasing 'system_a'...
OKAY [ 0.411s]
sending sparse 'system_a' 1/4 (520579 KB)...
OKAY [ 13.904s]
writing 'system_a' 1/4...
OKAY [ 3.787s]
sending sparse 'system_a' 2/4 (521193 KB)...
OKAY [ 13.721s]
writing 'system_a' 2/4...
OKAY [ 4.103s]
sending sparse 'system_a' 3/4 (510216 KB)...
OKAY [ 14.206s]
writing 'system_a' 3/4...
OKAY [ 3.788s]
sending sparse 'system_a' 4/4 (128745 KB)...
OKAY [ 3.513s]
writing 'system_a' 4/4...
OKAY [ 1.049s]
erasing 'vendor_b'...
OKAY [ 0.154s]
sending 'vendor_b' (242238 KB)...
OKAY [ 6.003s]
writing 'vendor_b'...
OKAY [ 3.653s]
Setting current slot to 'b'...
OKAY [ 0.087s]
rebooting...
finished. total time: 131.364s
Tryfons-MBPlatform-tools tryfon$
Everything turned out fine!!!

Related

[SOLVED] fastboot: "FAILED (remote: Write Fail)"

I've never experienced the fastboot error below and I am not sure about how to proceed.
The error is on the third to last line.
I am attempting to flash the Google factory image: yakju-jwr66y-factory-09207065
to my maguro.
Code:
sending 'bootloader' (2308 KB)...
OKAY [ 0.224s]
writing 'bootloader'...
OKAY [ 0.290s]
finished. total time: 0.518s
rebooting into bootloader...
OKAY [ 0.009s]
finished. total time: 0.010s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEMD04
Baseband Version.....: I9250XXLJ1
Serial Number........: 0149BD310A01D011
--------------------------------------------
checking product...
OKAY [ 0.008s]
sending 'boot' (4376 KB)...
OKAY [ 0.416s]
writing 'boot'...
OKAY [ 0.526s]
sending 'recovery' (4924 KB)...
OKAY [ 0.468s]
writing 'recovery'...
OKAY [ 0.600s]
erasing 'system'...
OKAY [ 0.018s]
sending 'system' (479248 KB)...
OKAY [ 44.424s]
writing 'system'...
[B][COLOR="Red"]FAILED (remote: Write Fail)[/COLOR][/B]
finished. total time: 46.532s
Press any key to exit...
Edit:
I locked and then unlocked the bootloader and re-downloaded and verified the factory image before flashing. After doing this I was able to successfully flash the factory image.

Cannot install stock rom: FAILED (remote: data too large)

I tried installing Cyanogenmod on a Nexus 5X, and it didn't work, so now I'm trying to install the stock rom from this site: https://developers.google.com/android/images#bullhead.
I'm doing this on Ubuntu 15.10. When I run the flash-all.sh script (on any of them), I get this output:
target reported max download size of 536870912 bytes
sending 'bootloader' (4382 KB)...
OKAY [ 0.195s]
writing 'bootloader'...
OKAY [ 0.077s]
finished. total time: 0.272s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.008s
target reported max download size of 536870912 bytes
sending 'radio' (56614 KB)...
OKAY [ 1.715s]
writing 'radio'...
OKAY [ 0.338s]
finished. total time: 2.052s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: BHZ10i
Baseband Version.....: M8994F-2.6.22.0.56
Serial Number........: 00a9164559592811
--------------------------------------------
checking product...
OKAY [ 0.020s]
checking version-bootloader...
OKAY [ 0.020s]
checking version-baseband...
OKAY [ 0.020s]
sending 'boot' (11469 KB)...
OKAY [ 0.406s]
writing 'boot'...
OKAY [ 0.073s]
sending 'recovery' (12521 KB)...
OKAY [ 0.393s]
writing 'recovery'...
OKAY [ 0.092s]
erasing 'system'...
OKAY [ 0.089s]
sending 'system' (1950236 KB)...
FAILED (remote: data too large)
finished. total time: 1.210s
I'm not seeing many resources online about this error. The only thing I've seen is to update fastboot, but I've already got the latest installed with this ppa: http://askubuntu.com/questions/34702/how-do-i-set-up-android-adb
Is there anything that I can do to get it working correctly?
adanedhel728 said:
I tried installing Cyanogenmod on a Nexus 5X, and it didn't work, so now I'm trying to install the stock rom from this site: https://developers.google.com/android/images#bullhead.
I'm doing this on Ubuntu 15.10. When I run the flash-all.sh script (on any of them), I get this output:
target reported max download size of 536870912 bytes
sending 'bootloader' (4382 KB)...
OKAY [ 0.195s]
writing 'bootloader'...
OKAY [ 0.077s]
finished. total time: 0.272s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.008s
target reported max download size of 536870912 bytes
sending 'radio' (56614 KB)...
OKAY [ 1.715s]
writing 'radio'...
OKAY [ 0.338s]
finished. total time: 2.052s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: BHZ10i
Baseband Version.....: M8994F-2.6.22.0.56
Serial Number........: 00a9164559592811
--------------------------------------------
checking product...
OKAY [ 0.020s]
checking version-bootloader...
OKAY [ 0.020s]
checking version-baseband...
OKAY [ 0.020s]
sending 'boot' (11469 KB)...
OKAY [ 0.406s]
writing 'boot'...
OKAY [ 0.073s]
sending 'recovery' (12521 KB)...
OKAY [ 0.393s]
writing 'recovery'...
OKAY [ 0.092s]
erasing 'system'...
OKAY [ 0.089s]
sending 'system' (1950236 KB)...
FAILED (remote: data too large)
finished. total time: 1.210s
I'm not seeing many resources online about this error. The only thing I've seen is to update fastboot, but I've already got the latest installed with this ppa: http://askubuntu.com/questions/34702/how-do-i-set-up-android-adb
Is there anything that I can do to get it working correctly?
Click to expand...
Click to collapse
the system image always is too large and usually it gets transferred in smaller pieces automatically. I'd try to flash all the images manually on a Windows mashine, following this guide (section 10).
I did it many times this way without issues.
ulxerker said:
the system image always is too large and usually it gets transferred in smaller pieces automatically. I'd try to flash all the images manually on a Windows mashine, following this guide (section 10).
I did it many times this way without issues.
Click to expand...
Click to collapse
Well, I can't get it working on Windows at all, because the driver won't install. (At least I assume that's the reason why-- The driver won't install and fastboot won't show any devices.)
I tried fixing that, but with no luck.
I did also try section 10 from Ubuntu, with the same results for the system part:
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.284s]
sending sparse 'system' (514493 KB)...
OKAY [ 12.333s]
writing 'system'...
OKAY [ 3.149s]
sending sparse 'system' (514543 KB)...
OKAY [ 12.427s]
writing 'system'...
OKAY [ 3.117s]
sending sparse 'system' (524291 KB)...
FAILED (remote: data too large)
finished. total time: 31.327s
Fastboot is too old. Remove it from system. apt remove android-tools-fastboot . Place fastboot from dl link into a folder where is your system img. Change permissions if needed and exexute it with ./fastboot
https://mega.nz/#!CYYjHYSK!yjhPZ-OYQNhFxq-0JXVibtUps7AwoFDtvk0yPu_194s
Even better is to place fastboot file into a system /bin folder from where you can execute command in any folder.
Best regards.
icrunchbanger said:
Fastboot is too old. Remove it from system. apt remove android-tools-fastboot . Place fastboot from dl link into a folder where is your system img. Change permissions if needed and exexute it with ./fastboot
https://mega.nz/#!CYYjHYSK!yjhPZ-OYQNhFxq-0JXVibtUps7AwoFDtvk0yPu_194s
Even better is to place fastboot file into a system /bin folder from where you can execute command in any folder.
Best regards.
Click to expand...
Click to collapse
My gosh, that finally worked, and I didn't believe it would. I had thought that the one I had gotten from that PPA was the newest, but, apparently not. I actually got it directly from Google (which was a chore in itself, but outside the scope of this thread).
Thank you very much. Now, let's see if I can find out how to mark this as solved...
adanedhel728 said:
My gosh, that finally worked, and I didn't believe it would. I had thought that the one I had gotten from that PPA was the newest, but, apparently not. I actually got it directly from Google (which was a chore in itself, but outside the scope of this thread).
Thank you very much. Now, let's see if I can find out how to mark this as solved...
Click to expand...
Click to collapse
Your welcome. Never trust PPA ?
I got issuse
icrunchbanger said:
Fastboot is too old. Remove it from system. apt remove android-tools-fastboot . Place fastboot from dl link into a folder where is your system img. Change permissions if needed and exexute it with ./fastboot
https://mega.nz/#!CYYjHYSK!yjhPZ-OYQNhFxq-0JXVibtUps7AwoFDtvk0yPu_194s
Even better is to place fastboot file into a system /bin folder from where you can execute command in any folder.
Best regards.
Click to expand...
Click to collapse
Bro link doesnt work, can you sent me app via email: [email protected]
suleymanov5 said:
Bro link doesnt work, can you sent me app via email: [email protected]
Click to expand...
Click to collapse
You can download android tools from Google
https://dl.google.com/android/repository/platform-tools-latest-linux.zip
Also you can check my github for some nifty scripts .
https://github.com/icrunchbanger/android

FAILED (remote: 'Chunk data size exceeds partition size') when flashing system.img

Hi, guys.
I couldn't install update 10.0.3.0 after restoring boot.img from Magisk.
So, I flash boot.img in fastboot but still cannot.
And then I found out maybe because Substratum modified system.img
Then I tried to flash 10.0.2.0 system.img using this command:
Code:
fastboot flash system_a system_10.0.2.0.img
and this error shown:
Code:
Sending sparse 'system_a' 1/3 (462332 KB) OKAY [ 10.736s]
Writing sparse 'system_a' 1/3 FAILED (remote: 'Chunk data size exceeds partition size')
Finished. Total time: 30.924s
I also tried these 2 commands get from this solution:
Code:
fastboot flash -S 256M system_a system_10.0.2.0.img
fastboot flash -S 128M system_a system_10.0.2.0.img
but same error.
Any help is appreciated.
current-slot:
Code:
D:\platform-tools>fastboot getvar current-slot
current-slot: a
Finished. Total time: 0.003s
Sorry guys, problem solved.
I don't know what happened, my phone suddenly stuck in bootloop?
no animation just black screen, increase brightness to 100 then drop to 0 then increase to 100 and cycle.
then I boot into fastboot and try flash again
Code:
D:\platform-tools>fastboot getvar current-slot
current-slot: a
Finished. Total time: 0.012s
D:\platform-tools>fastboot flash boot_a boot_10.0.2.0.img
Sending 'boot_a' (27219 KB) OKAY [ 0.633s]
Writing 'boot_a' OKAY [ 0.339s]
Finished. Total time: 0.996s
D:\platform-tools>fastboot flash system_a system_10.0.2.0.img
Sending sparse 'system_a' 1/4 (522236 KB) OKAY [ 17.728s]
Writing sparse 'system_a' 1/4 OKAY [ 5.516s]
Sending sparse 'system_a' 2/4 (522236 KB) OKAY [ 17.947s]
Writing sparse 'system_a' 2/4 OKAY [ 5.576s]
Sending sparse 'system_a' 3/4 (522236 KB) OKAY [ 17.854s]
Writing sparse 'system_a' 3/4 OKAY [ 5.629s]
Sending sparse 'system_a' 4/4 (447916 KB) OKAY [ 15.042s]
Writing sparse 'system_a' 4/4 OKAY [ 4.804s]
Finished. Total time: 148.451s
D:\platform-tools>fastboot reboot
Rebooting
Finished. Total time: 0.012s
now the system.img split into 522.236 MB instead of 462.332 MB and got 4 parts instead of 3?
wtf is happening!
Anyway, the updated is installed successfully.

Help... Soft-bricked New Pixel 2 XL... Fastboot Flash Stock Does Not Work'

EDIT: I ran this tool and it brought the phone back to life! Not sure why the flash all script is broken. I will keep this thread open and post the log that this tool generated and hopefully the community can figure out what happened. I noticed the all-in-one tool flashed some additional partitions like "dtbo" that the flash all script did not.
Just got a used device, figured i'd unlock bootloader and update it via fastboot instead of OTA. Unlocked bootloader, ddownloaded image from Google site, ran flash-all.bat. Now when device starts, right after the bootloader unlocked warning, I get the Google logo, then device is corrupt and untrusted warning, then a bootloop. Trying to clear the cache does not work (see error in output below). Clearing data via recovery works, but does not help. I have a fair amount of experience with this. What am I missing!?
What I have already tried:
* Update fastboot to latest version:
Code:
> fastboot --version
fastboot version eac51f2bb6a8-android
* Try Different Cable/USB Port
* Try running "fastboot flashing unlock_critical":
FAILED (remote: Device already : unlocked!)
Click to expand...
Click to collapse
* Using the July 2019 update instead of the latest
* Google research
Sometimes I get this from the flash all command. Sometimes writing user-data works, but clearing cache gives "Error: Check device Console":
Code:
target reported max download size of 536870912 bytes
sending 'bootloader' (36356 KB)...
OKAY [ 0.795s]
writing 'bootloader'...
OKAY [ 0.556s]
finished. total time: 1.354s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
sending 'radio' (60388 KB)...
OKAY [ 1.285s]
writing 'radio'...
OKAY [ 0.408s]
finished. total time: 1.872s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.004s
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'
W/ ( 7216): Zip: unable to truncate file to 357556432: File too large
failed to extract 'vendor.img': I/O Error
Creating filesystem with parameters:
Size: 56946044928
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 13902843
Block groups: 425
Reserved block group size: 1024
Created filesystem with 11/3481600 inodes and 264598/13902843 blocks
error: file_write: write: No space left on device
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: TMZ30l
Baseband Version.....: g8998-00020-1912122233
Serial Number........: 906KPJP2073036
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.003s]
sending 'boot' (40960 KB)...
OKAY [ 0.865s]
writing 'boot'...
OKAY [ 0.250s]
sending sparse 'system' (524284 KB)...
OKAY [ 12.159s]
writing 'system'...
OKAY [ 3.249s]
sending sparse 'system' (524284 KB)...
OKAY [ 12.145s]
writing 'system'...
OKAY [ 3.265s]
sending sparse 'system' (524284 KB)...
OKAY [ 12.331s]
writing 'system'...
OKAY [ 3.247s]
sending sparse 'system' (524284 KB)...
OKAY [ 12.289s]
writing 'system'...
OKAY [ 3.262s]
sending sparse 'system' (340228 KB)...
OKAY [ 7.984s]
writing 'system'...
OKAY [ 2.102s]
erasing 'userdata'...
OKAY [ 1.127s]
sending 'userdata' (138830 KB)...
OKAY [ 2.923s]
writing 'userdata'...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 78.283s
Press any key to exit...
Log from successful flash with all-in-one tool:
Code:
Sending 'bootloader_a' (36356 KB) OKAY [ 0.792s]
Writing 'bootloader_a' OKAY [ 0.547s]
Finished. Total time: 1.412s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.005s
Sending 'radio_a' (60388 KB) OKAY [ 1.325s]
Writing 'radio_a' OKAY [ 0.397s]
Finished. Total time: 1.897s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.006s
--------------------------------------------
Bootloader Version...: TMZ30l
Baseband Version.....: g8998-00020-1912122233
Serial Number........: 906KPJP2073036
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Checking 'version-bootloader' OKAY [ 0.001s]
Checking 'version-baseband' OKAY [ 0.001s]
Setting current slot to 'a' OKAY [ 0.009s]
extracting boot.img (40 MB) to disk... took 0.277s
archive does not contain 'boot.sig'
Sending 'boot_a' (40960 KB) OKAY [ 0.891s]
Writing 'boot_a' OKAY [ 0.253s]
extracting dtbo.img (8 MB) to disk... took 0.023s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (8192 KB) OKAY [ 0.178s]
Writing 'dtbo_a' OKAY [ 0.057s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.002s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'super_empty.img'
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
archive does not contain 'product_services.img'
extracting system.img (2380 MB) to disk... took 13.415s
archive does not contain 'system.sig'
Sending sparse 'system_a' 1/5 (524284 KB) OKAY [ 11.907s]
Writing 'system_a' OKAY [ 3.243s]
Sending sparse 'system_a' 2/5 (524284 KB) OKAY [ 11.848s]
Writing 'system_a' OKAY [ 3.248s]
Sending sparse 'system_a' 3/5 (524284 KB) OKAY [ 12.040s]
Writing 'system_a' OKAY [ 3.243s]
Sending sparse 'system_a' 4/5 (524284 KB) OKAY [ 11.884s]
Writing 'system_a' OKAY [ 3.252s]
Sending sparse 'system_a' 5/5 (340228 KB) OKAY [ 7.723s]
Writing 'system_a' OKAY [ 2.115s]
extracting system_other.img (306 MB) to disk... took 2.303s
archive does not contain 'system.sig'
Sending 'system_b' (313556 KB) OKAY [ 7.041s]
Writing 'system_b' OKAY [ 1.940s]
extracting vendor.img (340 MB) to disk... took 2.480s
archive does not contain 'vendor.sig'
Sending 'vendor_a' (349176 KB) OKAY [ 7.777s]
Writing 'vendor_a' OKAY [ 2.166s]
archive does not contain 'vendor_other.img'
Erasing 'userdata' OKAY [ 1.376s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 13902843 4k blocks and 3481600 inodes
Filesystem UUID: 09419b40-81a8-11ea-8938-4b5d199bc358
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Allocating group tables: done
Writing inode tables: done
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (4400 KB) OKAY [ 0.095s]
Writing 'userdata' OKAY [ 0.063s]
Rebooting OKAY [ 0.001s]
Finished. Total time: 122.672s
Press any key to exit...

Soft/Hard Brick help needed please

From the start: I was previously running the PixelDust ROM and wanted to try the 11 preview so i attempted to flash it via ADB commands. Script ran through the first time and finished overall but had some failed parts under the formatting section and rewriting partitions. With the first time using it i did forget to take out the -W string, well i purposely left it as i dont mind resetting the phone. Fast forward 8 hours, my phone still wont boot past the white google screen after NUMEROUS retries with flashing the 11 preview through ADB as well as using the flash-all. It also now shows the RED "your device is corrupted" screen on initial boot (not the standard yellow warning after unlocking) and seems like it bootloops to the bootloader or google screen and stays there. ANY help greatly appreciated.
Currently trying to use the Deuces flash-all script and latest version of Android 10. Will report
Welcome to Deuces Flashing Script!
v5.0-Windows
Checking if Fastboot exe is accessible..
Checking if Fastboot works correctly
fastboot version eac51f2bb6a8-android
Fastboot Detected!
Checking if device is detected via Fastboot.
Device Detected in Fastboot!
Are you SURE you want to continue?
Press Enter to continue...:
This tool will reformat partitions in your device!
It will attempt to keep your user data!
Data could be lost! - Use At Your Own Risk!
Continue? (y/N) y
Checking if bootloader is unlocked.
Look at device to confirm if script is waiting...
Preparing files for flash...
Extracting C:\Users\Tiffany\Downloads\Deuces-Bootloop-Recovery-Flashing-Script-master\Deuces-Bootloop-Recovery-Flashing-Script-master\taimen110.zip...
target reported max download size of 536870912 bytes
sending 'bootloader' (36356 KB)...
OKAY [ 0.940s]
writing 'bootloader'...
OKAY [ 0.388s]
finished. total time: 1.412s
target reported max download size of 536870912 bytes
sending 'radio' (60388 KB)...
OKAY [ 1.601s]
writing 'radio'...
OKAY [ 0.576s]
finished. total time: 2.198s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.008s
Extracting C:\Users\Tiffany\Downloads\Deuces-Bootloop-Recovery-Flashing-Script-master\Deuces-Bootloop-Recovery-Flashing-Script-master\_work\taimen-qq2a.200501.001.b3\image-taimen-qq2a.200501.001.b3.zip.
Flashing B-Slot items first.
target reported max download size of 536870912 bytes
erasing 'system_b'...
OKAY [ 0.033s]
sending 'system_b' (313556 KB)...
OKAY [ 8.515s]
writing 'system_b'...
OKAY [ 1.475s]
finished. total time: 10.358s
target reported max download size of 536870912 bytes
sending 'boot' (40960 KB)...
OKAY [ 1.086s]
writing 'boot'...
OKAY [ 0.372s]
finished. total time: 1.462s
target reported max download size of 536870912 bytes
sending 'dtbo' (8192 KB)...
OKAY [ 0.217s]
writing 'dtbo'...
OKAY [ 0.079s]
finished. total time: 0.302s
target reported max download size of 536870912 bytes
sending sparse 'system' (524284 KB)...
OKAY [ 26.436s]
writing 'system'...
OKAY [ 2.457s]
sending sparse 'system' (524284 KB)...
OKAY [ 25.678s]
writing 'system'...
OKAY [ 2.472s]
sending sparse 'system' (524284 KB)...
OKAY [ 24.613s]
writing 'system'...
OKAY [ 2.464s]
sending sparse 'system' (524284 KB)...
OKAY [ 25.794s]
writing 'system'...
OKAY [ 2.462s]
sending sparse 'system' (340260 KB)...
OKAY [ 15.858s]
writing 'system'...
OKAY [ 1.593s]
finished. total time: 129.943s
target reported max download size of 536870912 bytes
sending 'vbmeta' (4 KB)...
OKAY [ 0.004s]
writing 'vbmeta'...
OKAY [ 0.006s]
finished. total time: 0.012s
target reported max download size of 536870912 bytes
sending 'vendor' (349176 KB)...
OKAY [ 9.269s]
writing 'vendor'...
OKAY [ 1.645s]
finished. total time: 10.922s
Format UserData? (y/N) n
Done!
Press Enter to continue...:
Android 10 worked....

Categories

Resources