Hey!
So I finally managed to install this rom:
http://forum.xda-developers.com/showthread.php?p=22487053#post22487053
But I actually prefer stock for now, so I am wondering if someone can help me get back to stock rom? I have a GSM version.
I have tried the guides, but they result in a bootloop, also my recovery mode just goes into an android with a red "!" above it's chest.
Please help
I followed the "Get back to stock" instructions from here (http://forum.xda-developers.com/showthread.php?p=22492630#post22492630) to the letter, and I always end up in a bootloop What am I doing wrong?
This is my cmd log:
C:\Users\Sebz4n>fastboot-windows devices
---Took away my device ID--- fastboot
C:\Users\Sebz4n>fastboot-windows flash bootloader bootloader-maguro-primekj10.im
g
sending 'bootloader' (2308 KB)... OKAY
writing 'bootloader'... OKAY
C:\Users\Sebz4n>fastboot-windows reboot-bootloader
rebooting into bootloader... OKAY
C:\Users\Sebz4n>fastboot-windows flash radio radio-maguro-i9250xxkk1.img
sending 'radio' (12288 KB)... OKAY
writing 'radio'... OKAY
C:\Users\Sebz4n>fastboot-windows reboot-bootloader
rebooting into bootloader... OKAY
C:\Users\Sebz4n>fastboot-windows -w update image-yakju-itl41f.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...:
getvar:version-baseband FAILED (command write failed (Unknown error))
C:\Users\Sebz4n>fastboot-windows -w update image-yakju-itl41f.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEKJ10
Baseband Version.....: I9250XXKK1
Serial Number........: 0149AE7C11021010
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
checking version-baseband... OKAY
sending 'boot' (4054 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (4386 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (317798 KB)... OKAY
writing 'system'... OKAY
erasing 'userdata'... FAILED (unknown status code)
C:\Users\Sebz4n>
Click to expand...
Click to collapse
Please can someone help me, I really want to get back to stock so I can start using my brand new phone!
Make sure that your .zip isn't corrupted - if possible, verify the MD5 hash against the site you downloaded the zip from.
Edit, also try extracting the .img files from your zip and flashing those individually.
Code:
fastboot flash system system.img
Maybe this thread can help? http://forum.xda-developers.com/showthread.php?t=1391881
http://forum.xda-developers.com/showthread.php?p=22102956
Hope it's helpful. I'm on yakju (dont know if it works for people that were yakju variants and then converted, just saying, since there is a thread for converting, i guess i should read it sometime)
Edit: i did not see OP was using windows. Nevertheless, i agree with previous poster procedure.
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
Hi everyone, I am facing a bootloop problem with my Pixel 2 XL with Android 10 (Build 190711.020) and unlocked bootloader
THE PROBLEM
When I turn the phone on it boots until the Google splash screen then the phone turns off and on again, the issue also occurs when I try to boot to recovery mode or when I plug the phone to a charger or USB. The only thing I can boot fine to is the Bootloader
WHAT I DID PRIOR
A couple of hours ago the phone was not rooted and was working fine and I did the following
1. Rooted the phone with Magisk 19.4 beta,
2. Enabled Gmail dark mode by editing flags with solid explorer
3. Reboot the phone
4. Used it for sometimes
5. Boot into bootloader and flashed boot.img to unroot
6. Boot the phone and used it fine for hours
7. I went to settings and enabled forced dark in developer options
8. Reboot the phone and the bootloops begins
WHAT I HAVE TRIED
After the hone started to bootloop did the following
1. I flashed Android 10 factory image >> Still bootloops
2. Formated userdata >> Still bootloopps
3. Used [TOOL] Deuces Bootloop-Recovery & Flashing Script v5.0 >> Still bootloop
4. Change to boot slot a and flash factory image, change to boot slot b and flash factory image >> Still bootloop
Does anyone have any insight on how to solve this problem?*
Thanks
NingaR said:
Hi everyone, I am facing a bootloop problem with my Pixel 2 XL with Android 10 (Build 190711.020) and unlocked bootloader
THE PROBLEM
When I turn the phone on it boots until the Google splash screen then the phone turns off and on again, the issue also occurs when I try to boot to recovery mode or when I plug the phone to a charger or USB. The only thing I can boot fine to is the Bootloader
WHAT I DID PRIOR
A couple of hours ago the phone was not rooted and was working fine and I did the following
1. Rooted the phone with Magisk 19.4 beta,
2. Enabled Gmail dark mode by editing flags with solid explorer
3. Reboot the phone
4. Used it for sometimes
5. Boot into bootloader and flashed boot.img to unroot
6. Boot the phone and used it fine for hours
7. I went to settings and enabled forced dark in developer options
8. Reboot the phone and the bootloops begins
WHAT I HAVE TRIED
After the hone started to bootloop did the following
1. I flashed Android 10 factory image >> Still bootloops
2. Formated userdata >> Still bootloopps
3. Used [TOOL] Deuces Bootloop-Recovery & Flashing Script v5.0 >> Still bootloop
4. Change to boot slot a and flash factory image, change to boot slot b and flash factory image >> Still bootloop
Does anyone have any insight on how to solve this problem?*
Thanks
Click to expand...
Click to collapse
What is the output/log for when you run the flash-all?
Also, confirm you have the most up-to-date platform-tools as well as using a USB-A to USB-A (avoid USB-C as much as possible, at least with taimen) cord and various different ports.
I'm thinking, instead of flashing the boot.img, you should've just "Uninstalled" within Magisk -- essentially restores the stock boot.img, but with the 2 different slots, it may have some other safeguards or something. But, in any case, loading flash-all and/or deuce's script should've/would've resolved anything that went wrong anyways...
Are you sure you didn't accidentally flash/restore using Pie instead of Q/10?
If nothing else after answering these inquiries, I will walk you through using fastboot commands within bootloader mode to manually format the boot and system partitions....
simplepinoi177 said:
What is the output/log for when you run the flash-all?
Click to expand...
Click to collapse
Here is the output I have attached a .txt file too
Code:
PS C:\Users\Ninga\Desktop\taimen-qp1a.190711.020> .\flash-all.bat
Sending 'bootloader_b' (36352 KB) OKAY [ 0.799s]
Writing 'bootloader_b' OKAY [ 0.277s]
Finished. Total time: 1.242s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.007s
Sending 'radio_b' (60388 KB) OKAY [ 1.339s]
Writing 'radio_b' OKAY [ 0.820s]
Finished. Total time: 2.467s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.005s
--------------------------------------------
Bootloader Version...: TMZ30h
Baseband Version.....: g8998-00012-1905270706
Serial Number........: 711KPRW0625214
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Checking 'version-bootloader' OKAY [ 0.000s]
Checking 'version-baseband' OKAY [ 0.000s]
Setting current slot to 'b' OKAY [ 0.009s]
extracting boot.img (40 MB) to disk... took 0.264s
archive does not contain 'boot.sig'
Sending 'boot_b' (40960 KB) OKAY [ 0.901s]
Writing 'boot_b' OKAY [ 0.538s]
extracting dtbo.img (8 MB) to disk... took 0.033s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (8192 KB) OKAY [ 0.181s]
Writing 'dtbo_b' OKAY [ 0.104s]
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_b' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_b' OKAY [ 0.003s]
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'
extracting system.img (2374 MB) to disk... took 43.496s
archive does not contain 'system.sig'
Sending sparse 'system_b' 1/5 (524284 KB) OKAY [ 12.074s]
Writing 'system_b' OKAY [ 2.236s]
Sending sparse 'system_b' 2/5 (524284 KB) OKAY [ 12.060s]
Writing 'system_b' OKAY [ 2.234s]
Sending sparse 'system_b' 3/5 (524284 KB) OKAY [ 12.096s]
Writing 'system_b' OKAY [ 2.223s]
Sending sparse 'system_b' 4/5 (524284 KB) OKAY [ 12.006s]
Writing 'system_b' OKAY [ 2.237s]
Sending sparse 'system_b' 5/5 (334556 KB) OKAY [ 7.730s]
Writing 'system_b' OKAY [ 1.409s]
archive does not contain 'system_ext.img'
extracting system_other.img (304 MB) to disk... took 5.215s
archive does not contain 'system.sig'
Sending 'system_a' (311784 KB) OKAY [ 6.870s]
Writing 'system_a' OKAY [ 1.312s]
extracting vendor.img (340 MB) to disk... took 4.238s
archive does not contain 'vendor.sig'
Sending 'vendor_b' (348532 KB) OKAY [ 7.695s]
Writing 'vendor_b' OKAY [ 1.482s]
archive does not contain 'vendor_other.img'
Erasing 'userdata' OKAY [ 0.620s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 29518843 4k blocks and 7380992 inodes
Filesystem UUID: 36d24c48-e00a-11e9-8d7d-0f0cf6c3abaa
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (4672 KB) OKAY [ 0.103s]
Writing 'userdata' OKAY [ 0.035s]
Rebooting OKAY [ 0.000s]
Finished. Total time: 804.680s
Press any key to exit...
Also, confirm you have the most up-to-date platform-tools as well as using a USB-A to USB-A (avoid USB-C as much as possible, at least with taimen) cord and various different ports.
Click to expand...
Click to collapse
Yes I have up-to-date platform-tools and I am using USB-A to USB-C (I have been using this cable to update monthly)
I'm thinking, instead of flashing the boot.img, you should've just "Uninstalled" within Magisk -- essentially restores the stock boot.img, but with the 2 different slots, it may have some other safeguards or something. But, in any case, loading flash-all and/or deuce's script should've/would've resolved anything that went wrong anyways....
Are you sure you didn't accidentally flash/restore using Pie instead of Q/10?
Click to expand...
Click to collapse
Yes, I should just have just uninstalled magisk by using the uninstaller zip but I wanted to remove TWRP too and No I did not flash Pie just the same Android 10 build I cleaned flashed when I was updating to Android 10
If nothing else after answering these inquiries, I will walk you through using fastboot commands within bootloader mode to manually format the boot and system partitions....
Click to expand...
Click to collapse
Thank you so much for helping sir.
NingaR said:
Here is the output I have attached a .txt file too
Code:
PS C:\Users\Ninga\Desktop\taimen-qp1a.190711.020> .\flash-all.bat
Sending 'bootloader_b' (36352 KB) OKAY [ 0.799s]
Writing 'bootloader_b' OKAY [ 0.277s]
Finished. Total time: 1.242s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.007s
Sending 'radio_b' (60388 KB) OKAY [ 1.339s]
Writing 'radio_b' OKAY [ 0.820s]
Finished. Total time: 2.467s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.005s
--------------------------------------------
Bootloader Version...: TMZ30h
Baseband Version.....: g8998-00012-1905270706
Serial Number........: 711KPRW0625214
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Checking 'version-bootloader' OKAY [ 0.000s]
Checking 'version-baseband' OKAY [ 0.000s]
Setting current slot to 'b' OKAY [ 0.009s]
extracting boot.img (40 MB) to disk... took 0.264s
archive does not contain 'boot.sig'
Sending 'boot_b' (40960 KB) OKAY [ 0.901s]
Writing 'boot_b' OKAY [ 0.538s]
extracting dtbo.img (8 MB) to disk... took 0.033s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (8192 KB) OKAY [ 0.181s]
Writing 'dtbo_b' OKAY [ 0.104s]
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_b' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_b' OKAY [ 0.003s]
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'
extracting system.img (2374 MB) to disk... took 43.496s
archive does not contain 'system.sig'
Sending sparse 'system_b' 1/5 (524284 KB) OKAY [ 12.074s]
Writing 'system_b' OKAY [ 2.236s]
Sending sparse 'system_b' 2/5 (524284 KB) OKAY [ 12.060s]
Writing 'system_b' OKAY [ 2.234s]
Sending sparse 'system_b' 3/5 (524284 KB) OKAY [ 12.096s]
Writing 'system_b' OKAY [ 2.223s]
Sending sparse 'system_b' 4/5 (524284 KB) OKAY [ 12.006s]
Writing 'system_b' OKAY [ 2.237s]
Sending sparse 'system_b' 5/5 (334556 KB) OKAY [ 7.730s]
Writing 'system_b' OKAY [ 1.409s]
archive does not contain 'system_ext.img'
extracting system_other.img (304 MB) to disk... took 5.215s
archive does not contain 'system.sig'
Sending 'system_a' (311784 KB) OKAY [ 6.870s]
Writing 'system_a' OKAY [ 1.312s]
extracting vendor.img (340 MB) to disk... took 4.238s
archive does not contain 'vendor.sig'
Sending 'vendor_b' (348532 KB) OKAY [ 7.695s]
Writing 'vendor_b' OKAY [ 1.482s]
archive does not contain 'vendor_other.img'
Erasing 'userdata' OKAY [ 0.620s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 29518843 4k blocks and 7380992 inodes
Filesystem UUID: 36d24c48-e00a-11e9-8d7d-0f0cf6c3abaa
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (4672 KB) OKAY [ 0.103s]
Writing 'userdata' OKAY [ 0.035s]
Rebooting OKAY [ 0.000s]
Finished. Total time: 804.680s
Press any key to exit...
Yes I have up-to-date platform-tools and I am using USB-A to USB-C (I have been using this cable to update monthly)
Yes, I should just have just uninstalled magisk by using the uninstaller zip but I wanted to remove TWRP too and No I did not flash Pie just the same Android 10 build I cleaned flashed when I was updating to Android 10
Thank you so much for helping sir.
Click to expand...
Click to collapse
I haven't read the whole post, but I wanted to come on here real quick after a cursory look and suggest something...
There are some things that changed with the Full Factory images for Q/10 -- namely where the flash-all resides -- and I'm completely unsure if things have changed, but AFAIK, for Linux, you are supposed to use the flash-all.sh, NOT the flash-all.bat. I'm sure it's a subtle but significant difference...!
And i'll be sure to read and consider the rest later tonight...
And I am very happy to help!
simplepinoi177 said:
I haven't read the whole post, but I wanted to come on here real quick after a cursory look and suggest something...
There are some things that changed with the Full Factory images for Q/10 -- namely where the flash-all resides -- and I'm completely unsure if things have changed, but AFAIK, for Linux, you are supposed to use the flash-all.sh, NOT the flash-all.bat. I'm sure it's a subtle but significant difference...!
And i'll be sure to read and consider the rest later tonight...
And I am very happy to help!
Click to expand...
Click to collapse
I am using windows, I just run .\flash-all.bat on PowerShell as I was unable to copy the output code in CMD but I get the same output from CMD and PowerShell.
NingaR said:
I am using windows, I just run .\flash-all.bat on PowerShell as I was unable to copy the output code in CMD but I get the same output from CMD and PowerShell.
Click to expand...
Click to collapse
So, actually, I strongly suggest using CMD versus PowerShell. If anything, you make sure to run it “as Administrator” (either by right-clicking, or searching Command Prompt and right-clicking) and then directing to and running the flash-all.bat. And to keep the window from closing, you edit the file – in the same way you would to remove the “-w” – by right-clicking and selecting “Edit”. At the very end, remove/erase the word “exit”; this should keep it from closing out the window. You should do this from here on out. Also, you probably don’t have to do the “./” thing, but I’m not sure if it matters at all or not.
At this point, I (personally) would go through the process of manually formatting the system, boot, dtbo, and data partitions using fastboot commands in the bootloader; but I’m worried it might affect the bootloader in some inadvertent way and completely brick the device – which is why I’d only do it myself with only myself to blame. I super really bricked one device already by accidentally formatting the bootloader partition, then before reflashing/re-installing the stock bootloader, I accidentally rebooted and I couldn’t even recover anything because there was no Bootloader Mode to do it from. So what I suggest to you is this…
I suggest you download TWRP image file and temporarily boot into that custom recovery to “wipe” and format everything. You can do this by downloading and moving the TWRP .img file to the platform-tools folder that has the adb and fastboot executables/files. Then run the command “fastboot boot twrp.img” (replace “twrp” with the actual file name). In there, I would go to the “Wipe” section and wipe the system, data, and internal storage partition – If there was an option to wipe the boot partition I would suggest that; but we’ll get to that if need be – if you go into the “Advanced Wipe” section. While there, you might even try the “Repair or Change File System”. After all of this, you should reboot back into the bootloader and load up a CMD after clicking “Run as Administrator” and run the flash-all.bat again.
If it still is struggling afterwards, you might want to try obtaining the stock boot.img and dtbo.img -- you should be able to find it in the Full Factory image .zip file; you just have to delve deep enough through the multiple .zips -- and manually flashing it to the device; command would be “fastboot flash boot boot.img” & “fastboot flash dtbo dtbo.img” – remember you will have to move the .img files to the same platform-tools folder as fastboot and adb .exe files.
Some thoughts; I really wonder if it is the new Q/10 OS version or something and/or the new way Google has assembled the Full Factory images, but most of the time running the flash-all with the “-w” intact resolves any boot and system issues! None of these steps are usually necessary further than that. I was suspecting something was happening in the flashing, but your log shows that everything is flashing and installing without error. I might’ve even suggested that you redownload and check the checksum (SHA-256), but then again you would have had a bunch of errors if even one byte was off!
Here’s hoping one of these things works…good luck to you!
simplepinoi177 said:
So, actually, I strongly suggest using CMD versus PowerShell. If anything, you make sure to run it “as Administrator” (either by right-clicking, or searching Command Prompt and right-clicking) and then directing to and running the flash-all.bat. And to keep the window from closing, you edit the file – in the same way you would to remove the “-w” – by right-clicking and selecting “Edit”. At the very end, remove/erase the word “exit”; this should keep it from closing out the window. You should do this from here on out. Also, you probably don’t have to do the “./” thing, but I’m not sure if it matters at all or not.
At this point, I (personally) would go through the process of manually formatting the system, boot, dtbo, and data partitions using fastboot commands in the bootloader; but I’m worried it might affect the bootloader in some inadvertent way and completely brick the device – which is why I’d only do it myself with only myself to blame. I super really bricked one device already by accidentally formatting the bootloader partition, then before reflashing/re-installing the stock bootloader, I accidentally rebooted and I couldn’t even recover anything because there was no Bootloader Mode to do it from. So what I suggest to you is this…
I suggest you download TWRP image file and temporarily boot into that custom recovery to “wipe” and format everything. You can do this by downloading and moving the TWRP .img file to the platform-tools folder that has the adb and fastboot executables/files. Then run the command “fastboot boot twrp.img” (replace “twrp” with the actual file name). In there, I would go to the “Wipe” section and wipe the system, data, and internal storage partition – If there was an option to wipe the boot partition I would suggest that; but we’ll get to that if need be – if you go into the “Advanced Wipe” section. While there, you might even try the “Repair or Change File System”. After all of this, you should reboot back into the bootloader and load up a CMD after clicking “Run as Administrator” and run the flash-all.bat again.
If it still is struggling afterwards, you might want to try obtaining the stock boot.img and dtbo.img -- you should be able to find it in the Full Factory image .zip file; you just have to delve deep enough through the multiple .zips -- and manually flashing it to the device; command would be “fastboot flash boot boot.img” & “fastboot flash dtbo dtbo.img” – remember you will have to move the .img files to the same platform-tools folder as fastboot and adb .exe files.
Some thoughts; I really wonder if it is the new Q/10 OS version or something and/or the new way Google has assembled the Full Factory images, but most of the time running the flash-all with the “-w” intact resolves any boot and system issues! None of these steps are usually necessary further than that. I was suspecting something was happening in the flashing, but your log shows that everything is flashing and installing without error. I might’ve even suggested that you redownload and check the checksum (SHA-256), but then again you would have had a bunch of errors if even one byte was off!
Here’s hoping one of these things works…good luck to you!
Click to expand...
Click to collapse
I can not even boot to TWRP the only thing I can boot is the bootloader, booting TWRP or boot to stock recovery from bootloader results to a bootloop, even if I power down the device and plug the charger without doing anything the phone start to bootloop.
I have used both Powershell and CMD(as admin I still get the same result)
Code:
Microsoft Windows [Version 10.0.18362.356]
(c) 2019 Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd C:\Users\Ninga\Desktop\A10
C:\Users\Ninga\Desktop\A10>fastboot devices
711KPRW0625214 fastboot
C:\Users\Ninga\Desktop\A10>flash-all.bat
Sending 'bootloader_b' (36352 KB) OKAY [ 0.803s]
Writing 'bootloader_b' OKAY [ 0.276s]
Finished. Total time: 1.241s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.004s
Sending 'radio_b' (60388 KB) OKAY [ 1.332s]
Writing 'radio_b' OKAY [ 0.819s]
Finished. Total time: 2.400s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.005s
--------------------------------------------
Bootloader Version...: TMZ30h
Baseband Version.....: g8998-00012-1905270706
Serial Number........: 711KPRW0625214
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' OKAY [ 0.000s]
Checking 'version-baseband' OKAY [ 0.001s]
Setting current slot to 'b' OKAY [ 0.009s]
extracting boot.img (40 MB) to disk... took 0.240s
archive does not contain 'boot.sig'
Sending 'boot_b' (40960 KB) OKAY [ 0.898s]
Writing 'boot_b' OKAY [ 0.535s]
extracting dtbo.img (8 MB) to disk... took 0.051s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (8192 KB) OKAY [ 0.180s]
Writing 'dtbo_b' OKAY [ 0.103s]
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_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_b' OKAY [ 0.003s]
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'
extracting system.img (2374 MB) to disk... took 63.201s
archive does not contain 'system.sig'
Sending sparse 'system_b' 1/5 (524284 KB) OKAY [ 12.061s]
Writing 'system_b' OKAY [ 2.228s]
Sending sparse 'system_b' 2/5 (524284 KB) OKAY [ 12.036s]
Writing 'system_b' OKAY [ 2.231s]
Sending sparse 'system_b' 3/5 (524284 KB) OKAY [ 12.034s]
Writing 'system_b' OKAY [ 2.218s]
Sending sparse 'system_b' 4/5 (524284 KB) OKAY [ 12.271s]
Writing 'system_b' OKAY [ 2.237s]
Sending sparse 'system_b' 5/5 (334556 KB) OKAY [ 8.023s]
Writing 'system_b' OKAY [ 1.411s]
archive does not contain 'system_ext.img'
extracting system_other.img (304 MB) to disk... took 5.676s
archive does not contain 'system.sig'
Sending 'system_a' (311784 KB) OKAY [ 6.852s]
Writing 'system_a' OKAY [ 1.315s]
extracting vendor.img (340 MB) to disk... took 4.352s
archive does not contain 'vendor.sig'
Sending 'vendor_b' (348532 KB) OKAY [ 7.676s]
Writing 'vendor_b' OKAY [ 1.479s]
archive does not contain 'vendor_other.img'
Erasing 'userdata' OKAY [ 0.620s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 29518843 4k blocks and 7380992 inodes
Filesystem UUID: e5ba5316-e02a-11e9-92a6-a7920be70672
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (4672 KB) OKAY [ 0.102s]
Writing 'userdata' OKAY [ 0.035s]
Rebooting OKAY [ 0.000s]
Finished. Total time: 171.544s
Press any key to exit...
I don't know much but what does this code means?
Code:
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'
At this point I would try anything possible as I was 99% giving up and prepared to buy a new phone, but if there is even a 0.05% chance of something to work I would try that.
Thanks
NingaR said:
I can not even boot to TWRP the only thing I can boot is the bootloader, booting TWRP or boot to stock recovery from bootloader results to a bootloop, even if I power down the device and plug the charger without doing anything the phone start to bootloop.
I have used both Powershell and CMD(as admin I still get the same result)
Code:
Microsoft Windows [Version 10.0.18362.356]
(c) 2019 Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd C:\Users\Ninga\Desktop\A10
C:\Users\Ninga\Desktop\A10>fastboot devices
711KPRW0625214 fastboot
C:\Users\Ninga\Desktop\A10>flash-all.bat
Sending 'bootloader_b' (36352 KB) OKAY [ 0.803s]
Writing 'bootloader_b' OKAY [ 0.276s]
Finished. Total time: 1.241s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.004s
Sending 'radio_b' (60388 KB) OKAY [ 1.332s]
Writing 'radio_b' OKAY [ 0.819s]
Finished. Total time: 2.400s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.005s
--------------------------------------------
Bootloader Version...: TMZ30h
Baseband Version.....: g8998-00012-1905270706
Serial Number........: 711KPRW0625214
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' OKAY [ 0.000s]
Checking 'version-baseband' OKAY [ 0.001s]
Setting current slot to 'b' OKAY [ 0.009s]
extracting boot.img (40 MB) to disk... took 0.240s
archive does not contain 'boot.sig'
Sending 'boot_b' (40960 KB) OKAY [ 0.898s]
Writing 'boot_b' OKAY [ 0.535s]
extracting dtbo.img (8 MB) to disk... took 0.051s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (8192 KB) OKAY [ 0.180s]
Writing 'dtbo_b' OKAY [ 0.103s]
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_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_b' OKAY [ 0.003s]
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'
extracting system.img (2374 MB) to disk... took 63.201s
archive does not contain 'system.sig'
Sending sparse 'system_b' 1/5 (524284 KB) OKAY [ 12.061s]
Writing 'system_b' OKAY [ 2.228s]
Sending sparse 'system_b' 2/5 (524284 KB) OKAY [ 12.036s]
Writing 'system_b' OKAY [ 2.231s]
Sending sparse 'system_b' 3/5 (524284 KB) OKAY [ 12.034s]
Writing 'system_b' OKAY [ 2.218s]
Sending sparse 'system_b' 4/5 (524284 KB) OKAY [ 12.271s]
Writing 'system_b' OKAY [ 2.237s]
Sending sparse 'system_b' 5/5 (334556 KB) OKAY [ 8.023s]
Writing 'system_b' OKAY [ 1.411s]
archive does not contain 'system_ext.img'
extracting system_other.img (304 MB) to disk... took 5.676s
archive does not contain 'system.sig'
Sending 'system_a' (311784 KB) OKAY [ 6.852s]
Writing 'system_a' OKAY [ 1.315s]
extracting vendor.img (340 MB) to disk... took 4.352s
archive does not contain 'vendor.sig'
Sending 'vendor_b' (348532 KB) OKAY [ 7.676s]
Writing 'vendor_b' OKAY [ 1.479s]
archive does not contain 'vendor_other.img'
Erasing 'userdata' OKAY [ 0.620s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 29518843 4k blocks and 7380992 inodes
Filesystem UUID: e5ba5316-e02a-11e9-92a6-a7920be70672
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (4672 KB) OKAY [ 0.102s]
Writing 'userdata' OKAY [ 0.035s]
Rebooting OKAY [ 0.000s]
Finished. Total time: 171.544s
Press any key to exit...
I don't know much but what does this code means?
Code:
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'
At this point I would try anything possible as I was 99% giving up and prepared to buy a new phone, but if there is even a 0.05% chance of something to work I would try that.
Thanks
Click to expand...
Click to collapse
Yeah..the "archive does not contain" alerts are normal...I think it has something to do with Google covering all their bases and having their install/flashing code be able to apply to other various devices that do have those partitions/images.
Man...yeah I can't think of any reason why your phone shouldn't be working or at least being able to boot to the recovery, even temporarily.
I guess just two things, just "for sh*ts and g*ggles"; please try running the "fastboot flashing unlock" & "fastboot flashing unlock_critical". The next is to try installing the Full Factory image of Android Pie/9 instead of Q/10; maybe something in the new OS version is causing issues -- I might even go a couple months back since they recently changed some stuff in the Full Factory where the flash-all file is located in a different place!
Outside of these 2 things, I can't think of anything more; never have I seen absolutely no errors and completely normal flash-all (or Deuce's script) process and still have this blaring issue.
Hopefully these do something, but if it doesn't, sorry I couldn't do more. Good luck to you...
simplepinoi177 said:
Yeah..the "archive does not contain" alerts are normal...I think it has something to do with Google covering all their bases and having their install/flashing code be able to apply to other various devices that do have those partitions/images.
Man...yeah I can't think of any reason why your phone shouldn't be working or at least being able to boot to the recovery, even temporarily.
I guess just two things, just "for sh*ts and g*ggles"; please try running the "fastboot flashing unlock" & "fastboot flashing unlock_critical". The next is to try installing the Full Factory image of Android Pie/9 instead of Q/10; maybe something in the new OS version is causing issues -- I might even go a couple months back since they recently changed some stuff in the Full Factory where the flash-all file is located in a different place!
Outside of these 2 things, I can't think of anything more; never have I seen absolutely no errors and completely normal flash-all (or Deuce's script) process and still have this blaring issue.
Hopefully these do something, but if it doesn't, sorry I couldn't do more. Good luck to you...
Click to expand...
Click to collapse
Thank you so much for your help mate, I will keep searching and try if I can get it to boot.
simplepinoi177 said:
What is the output/log for when you run the flash-all?
Also, confirm you have the most up-to-date platform-tools as well as using a USB-A to USB-A (avoid USB-C as much as possible, at least with taimen) cord and various different ports.
Click to expand...
Click to collapse
Why avoid USB-C cables?
quera said:
Why avoid USB-C cables?
Click to expand...
Click to collapse
I think he meant to use USB-A to USB-C cable rather than using USB-C to USB-C cable
NingaR said:
Thank you so much for your help mate, I will keep searching and try if I can get it to boot.
Click to expand...
Click to collapse
I have a pixel 2 xl patched boot image that would boot a phone with root but magisk core-only mode.
You are welcome to try it. This has not been zipped. Just rename it. Suffix was added so it could be uploaded.
fastboot boot image-new.img
https://www.androidfilehost.com/?fid=1899786940962594367
So did you finally managed to solve your issue?
Yeah...I'm curious if running a Full Factory Pie/9 produced anything different...
but I'm betting @Ninjar probably called it quits and is sending it "in" or something...
But yes, an update would be great!
arismelachrinos said:
So did you finally managed to solve your issue?
Click to expand...
Click to collapse
Unfortunately No, still same thing.
simplepinoi177 said:
Yeah...I'm curious if running a Full Factory Pie/9 produced anything different...
but I'm betting @Ninjar probably called it quits and is sending it "in" or something...
But yes, an update would be great!
Click to expand...
Click to collapse
I ordered another phone, and I can not send this one in as I bought it from AliExpress.
NingaR said:
I ordered another phone, and I can not send this one in as I bought it from AliExpress.
Click to expand...
Click to collapse
Did you try booting with the modified boot image?
Tulsadiver said:
Did you try booting with the modified boot image?
Click to expand...
Click to collapse
Yes but still same thing, someone said it could be a hardware problem. :crying:
NingaR said:
I ordered another phone, and I can not send this one in as I bought it from AliExpress.
Click to expand...
Click to collapse
Well...since it seems that you may not be doing anything else with "this one", I might just walk you through manually formatting the partitions since/if it might be okay to merely "go for broke" even if there's a risk of permanently bricking it...
let me know here if you'd like to proceed...
simplepinoi177 said:
Well...since it seems that you may not be doing anything else with "this one", I might just walk you through manually formatting the partitions since/if it might be okay to merely "go for broke" even if there's a risk of permanently bricking it...
let me know here if you'd like to proceed...
Click to expand...
Click to collapse
Sure, lets proceed