Now that I've successfully unlocked my bootloader, I'm having an issue trying to flash the 8.1.0 system image. When I try to execute the flash-all.bat, it acts as if it's flashing the bootloader, and then I get an error message saying it failed. Here's a screenshot. Thanks in advance
Did you extract the zip file that's in the factory image zip? There's another zip in there that has the boot, recovery, etc image files.
Sent from my [device_name] using XDA-Developers Legacy app
I did. I'm wondering if it's an SDK issue...the Android API 27 SDK keeps failing to download via SDK manager because of a mismatched size. I tried downloading it in Android Studio, too, and while it says it's installed there, it says it isn't in SDK manager. Weird. I wish there was a way I could get it to download and install properly.
Google 15 seconds adb xda. That's the easiest way to get Fastboot and adb set up. It don't matter where the image files as it sets it up system wide. But it sounds more like you might have a corrupted file. Try download the factory image again.
Sent from my [device_name] using XDA-Developers Legacy app
Thanks! I tried that, however it still keeps failing I'm at a total loss. I just want to get onto Oreo 8.1 so I can flash the AOSP and root! This really has me baffled. Thanks again for your help
I did also try to redownload the file, and that wasn't the answer, either :/
Are you using Type C to C? I had this issue on my Pixel C and Pixel XL unable to flash a factory img with C to C only when I use A to C
It was indeed the SDK platform! I tried looking for where the API 27 had successfully installed in Android Studio, and found that it was under App Data>SDK. I looked there and voila! There was the downloaded platform. I extracted it and moved it to where the other platforms were located under SDK Tools, and success! I'm flashing the 8.1.0 factory image now
Ok, I spoke too soon The factory image files AREN'T flashing, and I got a data write failure....go figure. When I go to restart my tablet, I get the classic Android with the exclamation point. Here are some pics of what I got:
So I got it working! After a LOT of trial and error, and moving files to the platforms folder and flashing them that way, plus changing which USB port I was using, I was able to manually flash all files! I'm now on 8.1.0!
Related
Trying to just flash a factory image to my N7 but can't find the flash-all script in the SDK. I have it on both Windows and Ubuntu but can't find it. It's not a hidden file and I just want to edit it so I can keep my data.
I installed the latest SDK for both and there is nothing there like that. Looked all over the folders, searched, and can't find it anywhere.
cincibluer6 said:
Trying to just flash a factory image to my N7 but can't find the flash-all script in the SDK. I have it on both Windows and Ubuntu but can't find it. It's not a hidden file and I just want to edit it so I can keep my data.
I installed the latest SDK for both and there is nothing there like that. Looked all over the folders, searched, and can't find it anywhere.
Click to expand...
Click to collapse
It doesn't come with the sdk. It comes with the factory image. There is a new one for every release because the filenames being flashed changes.
If you want just what you need to flash the factory image there is very small addon file in this post that includes fastboot and flash-all-nowipe which is basically flash-all without the -w (which is what you were looking to do) Saves you the trouble of downloading the sdk just to get 3 files.
http://forum.xda-developers.com/showthread.php?p=47423184#post47423184
You're a saint. Thank you.
I thought i was losing my mind when I couldn't find the scripts.
Sent from my Nexus 4 using xda app-developers app
Anyone else get an error when trying to flash system image 63L? Says boota doesn't exist. I know some partitions are doubled but I assume the image should work. Just wondering if it's my PC drivers or an actual issue with the image itself. Not comfortable pulling it apart and flashing the pieces until there is more info on it. Not that I need it. I just like to play:laugh:
Gizmoe said:
Anyone else get an error when trying to flash system image 63L? Says boota doesn't exist. I know some partitions are doubled but I assume the image should work. Just wondering if it's my PC drivers or an actual issue with the image itself. Not comfortable pulling it apart and flashing the pieces until there is more info on it. Not that I need it. I just like to play:laugh:
Edit: Just realized I posted in wrong section. Mods please move to q&a if you see fit.
Click to expand...
Click to collapse
I had to update adb and fastboot
jaythenut said:
I had to update adb and fastboot
Click to expand...
Click to collapse
I updated through SDK and it says it's urrent but maybe my PC drivers are not playing nice. So it works for you though. That's good to know. It's probably my PC then. I should check if I added a static platform tools folder to my path instead of the updated one. Thanks for the reply
I have same problem as OP. Check out this post. I haven't tested, but I think this might solve the problem. http://forum.xda-developers.com/showpost.php?p=69239012&postcount=27
ADB sideload worked for me, but flashing factory images did not.
Golf c said:
ADB sideload worked for me, but flashing factory images did not.
Click to expand...
Click to collapse
Android studio updated the next time I opened it up. SDK tools version 25 is what it updated too and it works fine. Only fails on the first reboot bootloader command but then it flashes the rest no problem.
i just sideloaded with adb.
just open up the factory firmware files downloaded. within the folder there is a file named:flash-all.bat. i just clicked that after unlocking bootloader and it flashed the images. it did gives some slot error, but i haven't have any issues. im on the 63P image now as some claim it improves signal and wifi connectivity
hello - ive got a google pixel xl on android 7.1.2 i can see from the system update that i can update to Android oreo 8.0, when i click to "download and install" it downloads the 950.7MB file, starts to install , but then stops with message "coouldnt update - installation problem"..any ideas ? ta
goofy gorilla said:
hello - ive got a google pixel xl on android 7.1.2 i can see from the system update that i can update to Android oreo 8.0, when i click to "download and install" it downloads the 950.7MB file, starts to install , but then stops with message "coouldnt update - installation problem"..any ideas ? ta
Click to expand...
Click to collapse
Is your storage near full?
sliding_billy said:
Is your storage near full?
Click to expand...
Click to collapse
no mate...i have nothing on my phone as i recently got it...its about 23GB free
goofy gorilla said:
no mate...i have nothing on my phone as i recently got it...its about 23GB free
Click to expand...
Click to collapse
Sounds like the download is getting a corrupted file. I would either DL and install the factory image (if BL unlocked) with the -w removed from the flashall file or sideload the OTA (if not unlocked).
sorry mate - im not that techy but knowing me ill probaly brick my phone..what is bl, and -w ????? ...sorry not techy
https://developers.google.com/android/images
Straight from the source with detailed instructions.
Since he is not unlocked, he should sideload the full OTA from here
https://developers.google.com/android/ota
I would recommend a full system install given that you purchased the phone from someone. Wouldn't want anything malicious on the phone that the previous owner might have left in.
yes i would do that but not very techy, its still under warranty for another 15 days i think as i have the receipt, but the back glass is cracked , hence google say warranty is void..seems to reboot all by itself and sometimes just switches off..
richii0207 said:
I would recommend a full system install given that you purchased the phone from someone. Wouldn't want anything malicious on the phone that the previous owner might have left in.
Click to expand...
Click to collapse
i would do that but i dont have a clue as to where and how to do this ?
ok found this site to reflash to factory settings..HERE
ive downloaded the files but dont understand where to put the files, the instructions are below but not sure what they mean..it says "computer’s system partition" ???..is that drive C ?
where do i put the image that ive downloaded...into the folder called " Platform-tools folder"
what about the google usb drivers ?....do i put the actual usb folder or its contents into the "platform-tools folder"?
its confusing ..
what do they mean by this "Go to Platform-tools folder. Here you need to launch a Command Prompt / Terminal window with administrative rights."
how do i do that ?
Here’s how to do it:
Download the Platform-Tools zip corresponding to your computer’s operating system:
– for Windows PC click here.
– for Mac OS click here.
– for Linux click here.
unzip the file after the download is complete.
you will obtain the Platform-Tools files, save them all on your computer’s system partition.
– make sure to leave the Platform-Tools name as the default folder name.
next, download the Google USB drivers from here.
Next you can continue to the tutorial and learn how to flash a factory image for your device.
How to install Android 7.1.2 Factory Image for Google Pixel XL:
Download the Android 7.1.2 Nougat factory image file from here.
Extract the archived contents and save them on your PC.
Place all the extracted files in the Platform-tools folder.
– that’s the folder obtained using the steps above the tutorial.
well..somehow it managed to update to android oreo 8.0......after trying all day, will see how the phone performs...its rebooted byitself once already, dont know if that was because it was installling something but update has been done....still think this phone has some hardware problem as the screen froze when i was entering my google play details.....weird phone...
Hello, I want to use Pixel Dust Pie and for this you first have to flash a stock image. I follow the instructions here: https://developers.google.com/android/images#taimen and run the flash_all.bat but I get the following error:
error: failed to load 'image-taimen-pq3a.190605.003.zip': Not enough space
My phone has more than 45 GB free
Both disks of my PC have more than 40 GB free
I installed the latest drivers and platform tools
I really do not know what to do, thanks for reading.
After trying it on another laptop, I got it... I guess something is wrong with my drivers.
Sadly all too often the latest platform-tools, windows drivers or a different USB cable has been this phone's Achilles's heel...
Sent from my Pixel 2 XL using XDA Labs
Hello guys,
I have been trying to get this to work on my own for a while now. I am trying to use deuces script and it is not working for the life of me. I have formatted user data entirely and killed all encryption. I have tried to install the factory image numerous times and numerous ways but nothing seems to be working. I have tried to use deuces script, from fastboot and it isnt working (log attached).
Here is what is currently going on and the current setup. No ROM installed currently (I do not believe). Device is UNLOCKED. TWRP is installed, version 3.3, latest version.
I can get into fastboot and the computer can see fastboot with fastboot devices command.
I can get into recovery from the device, which is TWRP. I can sideload things from there and run any commands that twrp can natively run.
I can NOT get deuces script to run with either the latest android 9 factory image, or the latest android 10 image.
I am putting all of the factory image files, unzipped, in the platform tools folder, along with the deuces script files in the same folder... then running the script. It is kicking back an error, which is attached as an image.
Additionally the log is attached as well.
ANY insight on how to get my phone back to stock would be great. Really getting anything installed on it would be great at this point, currently I can only get to fastboot and recovery.
Thank you so much!
Try a different cable or USB port if you haven't already.
Also you can try putting everything into C:\platform-tools, instead of having everything a few directories deep.
All my files just get extracted into C:\platform-tools
ilal2ielli said:
Try a different cable or USB port if you haven't already.
Also you can try putting everything into C:\platform-tools, instead of having everything a few directories deep.
All my files just get extracted into C:\platform-tools
Click to expand...
Click to collapse
I always do the same thing with good results!
Sent from my Pixel 2 XL using XDA Labs
wdarea51 said:
Hello guys,
I have been trying to get this to work on my own for a while now. I am trying to use deuces script and it is not working for the life of me. I have formatted user data entirely and killed all encryption. I have tried to install the factory image numerous times and numerous ways but nothing seems to be working. I have tried to use deuces script, from fastboot and it isnt working (log attached).
Here is what is currently going on and the current setup. No ROM installed currently (I do not believe). Device is UNLOCKED. TWRP is installed, version 3.3, latest version.
I can get into fastboot and the computer can see fastboot with fastboot devices command.
I can get into recovery from the device, which is TWRP. I can sideload things from there and run any commands that twrp can natively run.
I can NOT get deuces script to run with either the latest android 9 factory image, or the latest android 10 image.
I am putting all of the factory image files, unzipped, in the platform tools folder, along with the deuces script files in the same folder... then running the script. It is kicking back an error, which is attached as an image.
Additionally the log is attached as well.
ANY insight on how to get my phone back to stock would be great. Really getting anything installed on it would be great at this point, currently I can only get to fastboot and recovery.
Thank you so much!
Click to expand...
Click to collapse
Do it without unzipping the factory image. The script unzips it itself and you're causing an error by doing it for it.
Title
Forget about recovery and unzipping files or scripts.
If you xan boot into the bootloader google gives you precise instructions to follow to just flash everything executing flashall.bat here: developers.google(dot)com/android/images.
If you followed the exact steps and it's not working show the full final terminal output to help you.
JuanG2 said:
Forget about recovery and unzipping files or scripts.
If you xan boot into the bootloader google gives you precise instructions to follow to just flash everything executing flashall.bat here: developers.google(dot)com/android/images.
If you followed the exact steps and it's not working show the full final terminal output to help you.
Click to expand...
Click to collapse
Just for reference, dueces script is use 99% of the time AFTER Google's flash-all.bat had failed to give the desired results. Not saying this is the case here but it is a likely reality.
Sent from my Pixel 2 XL using XDA Labs
CyberpodS2 said:
Just for reference, dueces script is use 99% of the time AFTER Google's flash-all.bat had failed to give the desired results. Not saying this is the case here but it is a likely reality.
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
I (myself *my opinion*) really wouldn't use that script becouse it's just an incredibly verbose way of forcing the flashing of the images and it's way more tedious to find errors using it.
If google's flash-all script is not working it should be analized why as it only is running 5 fastboot commands to flash all the images and if the phone can't run fastboot commands it's somewhat worring.
In his case the script can be failing for a million reasons like the script cant create the work directory to unzip the factory zip becouse it's only for admin use, or maybe has conflicts of directories, can also not be using an appropiate file for it as the naming scheme does not make sense. In any case the problem here is with the way the dueces script is decompressing the .zip as it can't find the image.zip when it's allocated to the variable here: $imgzipname = (Get-ChildItem _work/*/*.zip).fullname.
This script code is really not prepared to correct it self and is not great, HOWEVER it should work without much of a problem if no naming scheme of the images, partitions, directories changes or so I understand why people use it when they really screw something up.
---------- Post added at 09:30 AM ---------- Previous post was at 09:06 AM ----------
JuanG2 said:
I (myself *my opinion*) really wouldn't use that script becouse it's just an incredibly verbose way of forcing the flashing of the images and it's way more tedious to find errors using it.
If google's flash-all script is not working it should be analized why as it only is running 5 fastboot commands to flash all the images and if the phone can't run fastboot commands it's somewhat worring.
In his case the script can be failing for a million reasons like the script cant create the work directory to unzip the factory zip becouse it's only for admin use, or maybe has conflicts of directories, can also not be using an appropiate file for it as the naming scheme does not make sense. In any case the problem here is with the way the dueces script is decompressing the .zip as it can't find the image.zip when it's allocated to the variable here: $imgzipname = (Get-ChildItem _work/*/*.zip).fullname.
This script code is really not prepared to correct it self and is not great, HOWEVER it should work without much of a problem if no naming scheme of the images, partitions, directories changes or so I understand why people use it when they really screw something up.
Click to expand...
Click to collapse
Actually I just realized why the script is not working for you. You are running it against the incorrect file. You shouldn't be running it against the images.zip that's inside of the factory.zip but rather to the factory.zip itself don't unzip it, just paste the whole zip downloaded from developers.google.com and run the script against it.