I think I borked screwed up a few things with my rooted 3XL specifically maybe deleted certain system apps I shouldn't have phones working okay but I can't get the stock pixel launcher back I have to use a third-party launcher otherwise to phone goes into freak-out mode
Can I just do the typical factory reset and have the phone start over from scratch and it'll replenisher or start fresh with all the correct system apps working?
No, a factory reset just wipes data, so that wouldn't fix a borked system. If you think you just deleted the wrong system app then just reflash the latest system image in fastboot.
Sent from my Pixel 3 XL using Tapatalk
superchilpil said:
No, a factory reset just wipes data, so that wouldn't fix a borked system. If you think you just deleted the wrong system app then just reflash the latest system image in fastboot.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. So where exactly specifically do I get the October system .img ?
And what are the detailed steps again please ? Obviously go into fastboot mode, and connect the phone to the PC using command shell adb.
But exact step by step things to type ?
Here's the link https://dl.google.com/dl/android/aosp/crosshatch-ota-pd1a.180720.030-21ac68ff.zip
Extract that zip, and within it should be another zip
If you really think it was just a borked system you can flash the two system images with the following commands
Code:
fastboot flash system_a system.img
fastboot flash system_b system_other.img
Replace the system images with the proper paths or just drag and drop the file in the terminal/command prompt.
Should also go without saying make sure your adb/fastboot is the latest version or it will just fails silently.
Sent from my Pixel 3 XL using Tapatalk
superchilpil said:
Here's the link https://dl.google.com/dl/android/aosp/crosshatch-ota-pd1a.180720.030-21ac68ff.zip
Extract that zip, and within it should be another zip
If you really think it was just a borked system you can flash the two system images with the following commands
Code:
fastboot flash system_a system.img
fastboot flash system_b system_other.img
Replace the system images with the proper paths or just drag and drop the file in the terminal/command prompt.
Should also go without saying make sure your adb/fastboot is the latest version or it will just fails silently.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Thanks, but seemed I needed to download a different zip, one that was 1.7GB which had the system.img, seemed your link didn't that that system file ?
Anyways, when i do this flash, will this make me lose root ?
Zorachus said:
Thanks, but seemed I needed to download a different zip, one that was 1.7GB which had the system.img, seemed your link didn't that that system file ?
Anyways, when i do this flash, will this make me lose root ?
Click to expand...
Click to collapse
I apologise if I gave you the wrong link, but good job finding the proper one!
And it should not as long as you don't replace the boot image
Sent from my Pixel 3 XL using Tapatalk
Related
Hi
When I start up the boot loader or hit start, it just goes into recovery mode
When I turn my phone off normally and start it up, it just goes into recovery mode
I have an unlocked phone that's rather new, and I can't start it up
Thanks for the help
RingPvP said:
Hi
When I start up the boot loader or hit start, it just goes into recovery mode
When I turn my phone off normally and start it up, it just goes into recovery mode
I have an unlocked phone that's rather new, and I can't start it up
Thanks for the help
Click to expand...
Click to collapse
Running stock rom and stock kernel? Or custom rom kernel? Twrp recovery? Any other info
Sent from my Nexus 5X using Tapatalk
The_Automator said:
Running stock rom and stock kernel? Or custom rom kernel? Twrp recovery? Any other info
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I did *fastboot flash boot twrp.img. I mean't to flash it, but I was thinking twrp.img when trying to use boot.img
I couldn't undo it, and I knew I damaged my phone from this, but if there is a possible chance to fix it I am in even if I loose my data.
I was pretty sure this was the reason my Nexus 5x doesn't work, but I did nothing else other then that. Thanks for the help
RingPvP said:
I did *fastboot flash boot twrp.img. I mean't to flash it, but I was thinking twrp.img when trying to use boot.img
I couldn't undo it, and I knew I damaged my phone from this, but if there is a possible chance to fix it I am in even if I loose my data.
I was pretty sure this was the reason my Nexus 5x doesn't work, but I did nothing else other then that. Thanks for the help
Click to expand...
Click to collapse
So you can not boot to bootloader but can boot straight into twrp? But you can't flash the boot image from twrp because you cant use fastboot commands in twrp correct? maybe try this thread dedicated to unbricking phones
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Sent from my Nexus 5X using Tapatalk
The_Automator said:
So you can not boot to bootloader but can boot straight into twrp? But you can't flash the boot image from twrp because you cant use fastboot commands in twrp correct? maybe try this thread dedicated to unbricking phones
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
No no no, I can boot into the bootloader. When I turn on my phone normally, it goes into recovery mode or in twrp. When I load the bootloader and start, it also goes into twrp.
I am pretty sure I can still fastboot commands in twrp, so that's good.
Sorry that I didn't add that, but I hope you know what the problem is because I really want my phone back.
RingPvP said:
No no no, I can boot into the bootloader. When I turn on my phone normally, it goes into recovery mode or in twrp. When I load the bootloader and start, it also goes into twrp.
I am pretty sure I can still fastboot commands in twrp, so that's good.
Sorry that I didn't add that, but I hope you know what the problem is because I really want my phone back.
Click to expand...
Click to collapse
To be clear recovery mode is the same as twrp and you can not use fastboot commands within TWRP you can use adb shell commands (im less familiar with these). You can not flash stock images from twrp only aftermarket roms, kernels, zips etc. Factory images are flashed from the bootloader using fastboot.
But if you can boot into the bootloader and use fastboot (verify by typing fastboot devices)
Download chainfires modified boot image (select bullhead for the Nexus 5X)
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
extract the file so you have the .img file
Verify that your fastboot commands work fastboot devices (should always work from bootloader)
place chainfires image in the same folder as your fastboot exe.
fastboot flash boot boot.img
this should over write the boot image.
You could also just download the factory google image
https://developers.google.com/android/nexus/images?hl=en
Latest bullhead image ends with M. Extract the tar and place the extracted content in your (fastboot/adb folder) on your computer and just double click the flash-all.bat (note this will erase all data and give you a clean phone)
leave your phone until it says press any key to exit.
The_Automator said:
If you can boot into bootloader than the simplest thing to do is to download the nexus 5x image from googles factory image site. Extract that zip into your fastboot folder and double click flash all.bat. This will restore youre ur phone to factory defaults on the latest factory image. Alternatively you can just extract the boot image and use fastboot flash boot boot.img (but for this method youd have to download the factory image you already have installed which is why googlea self installer (flash-all.bat) would be easier
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I just flashed all.bat double clicking it, and it said finished. I turned on my phone already on bootloader, and it went back to twrp. I might have set my fastboot folder wrong, but the location is
C:\Program Files (x86)\Android\android-sdk\bullhead-mda89e if that helps.
Sorry if I am taking to much of your time away, but you've helped me a lot already
RingPvP said:
I just flashed all.bat double clicking it, and it said finished. I turned on my phone already on bootloader, and it went back to twrp. I might have set my fastboot folder wrong, but the location is
C:\Program Files (x86)\Android\android-sdk\bullhead-mda89e if that helps.
Sorry if I am taking to much of your time away, but you've helped me a lot already
Click to expand...
Click to collapse
usually the folder you would want to place the image into is the platform tools folder and you would want to place the files in the directory (not a sub directory) and the mda89e is the first release the newest release from google is
6.0.0 (MDB08M) Link f5233f827a44f99e26722e349f3c9445 5867cc27a23257a47688fe180ec272f1152ddde2
But within the factory image there should be a zip called something like image-bullhead-MDB08M.zip open that zip and extract just the boot.img to your platform tools folder. Then you should be able to use
fastboot flash boot boot.img
RingPvP said:
I just flashed all.bat double clicking it, and it said finished. I turned on my phone already on bootloader, and it went back to twrp. I might have set my fastboot folder wrong, but the location is
C:\Program Files (x86)\Android\android-sdk\bullhead-mda89e if that helps.
Sorry if I am taking to much of your time away, but you've helped me a lot already
Click to expand...
Click to collapse
In your case, it should be: C:\Program Files (x86)\Android\android-sdk\platform-tools\bullhead-mda89e
In this folder your should see fastboot.exe
The_Automator said:
To be clear recovery mode is the same as twrp and you can not use fastboot commands within TWRP you can use adb shell commands (im less familiar with these). You can not flash stock images from twrp only aftermarket roms, kernels, zips etc. Factory images are flashed from the bootloader using fastboot.
But if you can boot into the bootloader and use fastboot (verify by typing fastboot devices)
Download chainfires modified boot image (select bullhead for the Nexus 5X)
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
extract the file so you have the .img file
Verify that your fastboot commands work fastboot devices (should always work from bootloader)
place chainfires image in the same folder as your fastboot exe.
fastboot flash boot boot.img
this should over write the boot image.
You could also just download the factory google image
https://developers.google.com/android/nexus/images?hl=en
Latest bullhead image ends with M. Extract the tar and place the extracted content in your (fastboot/adb folder) on your computer and just double click the flash-all.bat (note this will erase all data and give you a clean phone)
leave your phone until it says press any key to exit.
Click to expand...
Click to collapse
I don't know what to say, but thank you so much! I literally had a heart attack when it happened. You deserve more than a thanks for this .
RingPvP said:
I don't know what to say, but thank you so much! I literally had a heart attack when it happened. You deserve more than a thanks for this .
Click to expand...
Click to collapse
Happy to help glad you got your phone sorted
Sent from my Nexus 5X using Tapatalk
I received the download on my 5x that's rooted. Will this break root for me?
Yes but you can easily re-root after re-installing TWRP
bg1906 said:
Yes but you can easily re-root after re-installing TWRP
Click to expand...
Click to collapse
I don't get this answer. I'm not able to install the security update on my rooted 5X, it reboots into TWRP and after I manually boot to system nothing happened. Tried it 3 times and still have root access.
Is the only way to get the security update by flashing an entire Android image? Or more specifically, can I update without wiping the phone?
Yeah OTA isn't going to work. You need to manually do it. You will need USB Drivers and ADB/Fastboot files. Create a folder on your desktop called Android and put the ADB files there. Now download the image. The image is an archive file. Extract the contents of archive files (there is one archive inside the original archive file you download), and after you have all the files extracted, modify the flash-all file (.bat if you are on Windows) with a text editor (Notepad) to remove the -w and save. This will prevent a wipe of your device. Connect your phone via USB and reboot to the bootloader. Open the folder you are in and if on Windows hold shift and right click and select Open Command Prompt. This will open a Command Prompt Window at the folder's location. Next type the command fastboot devices and press Enter. If everything is right, a device id will be returned. If that works, then go back to the folder and double click the flash-all.bat (Windows) and this will install the update. Root will be lost as will TWRP recovery. After the install, the phone will attempt to reboot. I always stop the reboot and go back to bootloader. Choose Recovery and go to the default recovery. You will see an Android figure with a red X. Simultaneously press the power and volume up & down buttons together repeatedly until you get the recovery menu (this may take a few times). Wipe Cache. Then reboot and you will have the update. You can then reinstall the latest version of TWRP by going to the TWRP website and downloading the latest version of TWRP. I usually put it in the same folder as the Android files and when it downloads rename it to twrp.img. Make sure you are in the bootloader and then at the command prompt all you need type is fastboot flash recovery twrp.img and this will install TWRP. You can then go to TWRP and flash SuperSU. I use the latest beta 2.66. But read here (http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3) for the details on the various versions of SuperSU Beta. *I take no responsibility for what may/may not happen to your phone as that depends on your level of comfort flashing/rooting etc*
Hope this helps. IF the flash-all gives you an error, you will need to flash the various parts of the update individually. If that happens, follow the instructions here for the update: https://www.androidpit.com/how-to-get-android-m-preview
This is exactly what I was looking for, thanks! Couldn't find it anywhere with Google which btw somehow returns mostly Nexus 5 results even when using "nexus 5x"...
I'll try this later on and reply with the results.
bosbeest said:
This is exactly what I was looking for, thanks! Couldn't find it anywhere with Google which btw somehow returns mostly Nexus 5 results even when using "nexus 5x"...
I'll try this later on and reply with the results.
Click to expand...
Click to collapse
Yes please let me know how this goes
Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Info taken from This thread with the help of dmudd
bosbeest said:
This is exactly what I was looking for, thanks! Couldn't find it anywhere with Google which btw somehow returns mostly Nexus 5 results even when using "nexus 5x"...
I'll try this later on and reply with the results.
Click to expand...
Click to collapse
It's the same process with both phones.
Tomyk89 said:
Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Info taken from This thread with the help of dmudd
Click to expand...
Click to collapse
Tried it, worked. Thanks a bunch!
Yaz75 said:
It's the same process with both phones.
Click to expand...
Click to collapse
Still doesn't make sense that you can't search for "5X"
Tomyk89 said:
Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Info taken from This thread with the help of dmudd
Click to expand...
Click to collapse
Does this wipe data?
ch.ch1 said:
Does this wipe data?
Click to expand...
Click to collapse
Nope. The fastboot command has to have "userdata" included to do that.
Sent from my Nexus 5X using Tapatalk
ch.ch1 said:
Does this wipe data?
Click to expand...
Click to collapse
No
ch.ch1 said:
Does this wipe data?
Click to expand...
Click to collapse
No
Sent from my Nexus 5X using Tapatalk
ch.ch1 said:
Does this wipe data?
Click to expand...
Click to collapse
Nope!
SlimSnoopOS said:
Nope. The fastboot command has to have "userdata" included to do that.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Not true- the -w flag will wipe userdata when flashing other partitions.
fastboot -w flash system system.img will wipe data
fastboot flash system system.img will not wipe data.
gee one said:
Not true- the -w flag will wipe userdata when flashing other partitions.
fastboot -w flash system system.img will wipe data
fastboot flash system system.img will not wipe data.
Click to expand...
Click to collapse
Oh, I learned something new
Sent from my Nexus 5X using Tapatalk
jhester1967 said:
I received the download on my 5x that's rooted. Will this break root for me?
Click to expand...
Click to collapse
I doubt it will install. The install will simply fail.
Im not so good at this...
So I just copy the 3 img files to the same folder adb is installed and I run the 4 commands? Do I have to install TWRP again? Do I have to root again?
I did the command "adb reboot bootloader" which rebooted my phone in the bootloader home page, but when I did the next command "fastboot flash boot boot.img" I got the msg "<waiting for any devices>"
ch.ch1 said:
Im not so good at this...
So I just copy the 3 img files to the same folder adb is installed and I run the 4 commands? Do I have to install TWRP again? Do I have to root again?
I did the command "adb reboot bootloader" which rebooted my phone in the bootloader home page, but when I did the next command "fastboot flash boot boot.img" I got the msg "<waiting for any devices>"
Click to expand...
Click to collapse
Keep this guide by Heisenberg for reference, it is very helpful when updating firmware or returning to stock. You want to refer to section 10 to update via fastboot.
If going from MMB29P to MMB29Q OTA, flash in fastboot: boot, system, and vendor. Radio and bootloader are unchanged if you are using MMB29P. Recovery does not need to be flashed since you want to keep TWRP.
Yes, you will need to root again in TWRP.
" SOLVED - System was using 19.99 gb's required user data format. " Cant flash any of 3 factory images ? Anyone have a clue why ? I have a verizon pixel Xl with unlocked bootloader rooted with the newest supersu and every time I try to flash any of the three factory images for pixel XL my adb tools gives me the error " error: failed to load 'image-marlin-nde63l.zip': Not enough space " I flashed images just fine a couple weeks ago on both my Nexus 6 and my Nexus 9 but for some reason I keep getting this problem.
I have tried using flash-all.bat and that is what I get. I never have had any luck using flash-all.bat in the past with my Nexus 6 & 9 so I would use the manual method which I"am listing below but there are a lot more things to flash on these pixel XL. So hopefully someone can list how to manually flash an image on the pixel XL because its totally different. Hopefully someone can tell me what is the problem ?
Run fastboot commands
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Add next step for Nexus 9
fastboot flash vendor vendor.img
I have also tried the following steps and on the last step flashing the image I still get " error: failed to load 'image-marlin-nde63l.zip': Not enough space "
Steps I tried are:
fastboot flash bootloader bootloader-marlin-8996-012001-1608281716.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-012511-1609150631.img
fastboot reboot-bootloader
fastboot -w update image-marlin-nde63l.zip
I just checked my setting and I have 19.99 gb's used by the system. That seems way too much. Could that be the problem ?
M9guy said:
I just checked my setting and I have 19.99 gb's used by the system. That seems way too much. Could that be the problem ?
Click to expand...
Click to collapse
Yeah sounds like it to me might have to wipe userdata that will wipe your phone completely
When I flash the images I use the flash-all.sh.
This works for me "sudo sh flash-all.sh"
I had same issue. I have sideloaded the update zip temporarily. I still wonder what's wrong in flashing zip file. I dont think its the issue with size because i had almost 90GB space left.
M9guy said:
I just checked my setting and I have 19.99 gb's used by the system. That seems way too much. Could that be the problem ?
Click to expand...
Click to collapse
When I flash the images I use the flash-all.sh.
This works for me "sudo sh flash-all.sh"
M9guy said:
I have a verizon pixel Xl with unlocked bootloader rooted with the newest supersu and every time I try to flash any of the three factory images for pixel XL my adb tools gives me the error " error: failed to load 'image-marlin-nde63l.zip': Not enough space "
Click to expand...
Click to collapse
You don't use ADB to flash factory image. You use fastboot, from your bootloader...
cam30era said:
You don't use ADB to flash factory image. You use fastboot, from your bootloader...
Click to expand...
Click to collapse
I was in bootloader fastboot mode and i saw same issue.
rootSr. said:
I was in bootloader fastboot mode and i saw same issue.
Click to expand...
Click to collapse
Just to confirm, you unzipped the factory image and did: fastboot flash system system.img?
If so, you might need to update your Android SDK...
cam30era said:
You don't use ADB to flash factory image. You use fastboot, from your bootloader...
Click to expand...
Click to collapse
I put phone in bootloader mode and held down shift button and righted clicked on my folder with my adb tool that I extracted all files to.
http://androiding.how/flash-firmware-factory-image-google-pixel/
jaythenut said:
Yeah sounds like it to me might have to wipe userdata that will wipe your phone completely
Click to expand...
Click to collapse
The method at the link below I had tried it previously and it did format my data but now each time I boot the phone I get " There"s an internal problem with your device. Contact your manufacturer for details. "
http://androiding.how/flash-firmware-factory-image-google-pixel/
zaksimmermon said:
When I flash the images I use the flash-all.sh.
This works for me "sudo sh flash-all.sh"
Click to expand...
Click to collapse
I have windows 10, which for windows your supposed to use flash-all.bat which that gave me the same error on the last step flashing the system image.
rootSr. said:
I had same issue. I have sideloaded the update zip temporarily. I still wonder what's wrong in flashing zip file. I dont think its the issue with size because i had almost 90GB space left.
Click to expand...
Click to collapse
I have the update downloaded to the phone it just wont install it think because I was rooted, even after formatting user data starting over it still would not install the update with no supersu installed.
Do you remember where the update was downloaded to on your phone what folder, or did you download the update somewhere else to your computer ?
cam30era said:
Just to confirm, you unzipped the factory image and did: fastboot flash system system.img?
If so, you might need to update your Android SDK...
Click to expand...
Click to collapse
It makes sense, I will update and verify. Thanks for quick reply Cam
rootSr. said:
It makes sense, I will update and verify. Thanks for quick reply Cam
Click to expand...
Click to collapse
I just tried updating my Minimal ADB and Fastboot [10-22-16] and still same error. I thought I had already updated but I tried again anyway and still no go, and that was updated on 10-22-16
http://forum.xda-developers.com/showthread.php?t=2317790
M9guy said:
I have windows 10, which for windows your supposed to use flash-all.bat which that gave me the same error on the last step flashing the system image.
Click to expand...
Click to collapse
What version is your pixel running now? I'm on NDE63P.
zaksimmermon said:
What version is your pixel running now? I'm on NDE63P.
Click to expand...
Click to collapse
I"am on NDE63L
You need to try updating the SDK through the SDK manager. It'll have a box to check of to update SDK 25.
Sent from my Pixel XL using Tapatalk
rootSr. said:
It makes sense, I will update and verify. Thanks for quick reply Cam
Click to expand...
Click to collapse
It did work without any issues. I have cleared old SDK and downloaded new. Worked flawless. Thanks. :good:
II am attempting to get back to full stock on my Pixel XL and I am okay with wiping it. I am coming from Rooted, TWRP, custom Kernel, and WETA Rom. I was having some issues with it acting up, and I want now to return to the full factory image. In order to do so, I attempted to run the flash-all.bat script from the Google page, and it seems as if all is going well, then, when it tries to flash the system.img, it fails and throws an error which says "FAILED (Remote: Partition [bootb] does not exist)" I have also tried flashing the factory image in pieces and get the same issue, and also when I try to do it through TWRP. I just want to go back to the way the phone came so I can start fresh. Any input on how to do so would be greatly appreciated. Note: the same error goes when I try to flash-all on slot a.
What version of adb are you running?
Make sure you have 1.0.36. Ref post http://forum.xda-developers.com/showthread.php?t=2932160
Try manually flashing to partition _a or _b. Such as fastboot flash system_a system.img.
I ran into the same issue and was able to flash everything to slot a manually by adding _a to the commands
harmohn said:
What version of adb are you running?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
The latest minimal adb fastboot
gettingerr said:
The latest minimal adb fastboot
Click to expand...
Click to collapse
Okay, just to be sure can you type "adb version" and then "fastboot --version" (without quotes) in a command line console. What were the outputs?
Android Debug Bridge version 1.0.35
Revision fc2a139a55f5-android
fastboot version fc2a139a55f5-android
Zavon said:
Try manually flashing to partition _a or _b. Such as fastboot flash system_a system.img.
I ran into the same issue and was able to flash everything to slot a manually by adding _a to the commands
Click to expand...
Click to collapse
I think that worked! Do I need to flash anything besides boot, system, and vendor? There are a lot of .img files in this folder from google. Do I do them all or just these three? Also, do I need to flash the radio?
Odd that Google wouldn't update their flash-all script to deal with the two slot setup..
gettingerr said:
Android Debug Bridge version 1.0.35
Revision fc2a139a55f5-android
fastboot version fc2a139a55f5-android
Click to expand...
Click to collapse
Right, you need to be on 1.0.36 for fastboot to "see" the partitions correctly. Refer to my initial comment for a download link.
gettingerr said:
I think that worked! Do I need to flash anything besides boot, system, and vendor? There are a lot of .img files in this folder from google. Do I do them all or just these three? Also, do I need to flash the radio?
Odd that Google wouldn't update their flash-all script to deal with the two slot setup..
Click to expand...
Click to collapse
I didn't flash any of the other stuff. Only boot, system, and vendor.
Not sure what causes the mismatch in names of the partitions.
Download the free Unified Toolkit. It works across a large number of Android devices. It takes the hassle out of a lot of ****, including this. It will flash the entire factory package by itself. I had to do this to fix my phone from a recovery bootloop after flash-all.bat failed me too.
Can anyone tell me what parts of the factory image should be flashed? Before anyone says use the flash all script, that just doesn't work for me. I use a 5 year old Mac air with terminal for all my adb and fastboot commands. I use the ./ before every fastboot command (required for Mac) and my fastboot is up to date. The flash all.sh command has never worked dating back to my nexus 6p. Not looking to trouble shoot why I can't flash all..... Just want to know which parts are vital to flash as there are a good 20 files in the zip folder when expanded. I know boot, system, and radio are some of the most important. Probably going to flash 7.1.2 and then grab the OTA for 8.0 for it.
318sugarhill said:
Can anyone tell me what parts of the factory image should be flashed? Before anyone says use the flash all script, that just doesn't work for me. I use a 5 year old Mac air with terminal for all my adb and fastboot commands. I use the ./ before every fastboot command (required for Mac) and my fastboot is up to date. The flash all.sh command has never worked dating back to my nexus 6p. Not looking to trouble shoot why I can't flash all..... Just want to know which parts are vital to flash as there are a good 20 files in the zip folder when expanded. I know boot, system, and radio are some of the most important. Probably going to flash 7.1.2 and then grab the OTA for 8.0 for it.
Click to expand...
Click to collapse
There's a great guide Stickied in the general 6p forum by Heisenberg. I always reference that when I'm flashing via fastboot to make sure I'm doing it correctly. I'd start there!
Sent from my Pixel XL using Tapatalk
smallsmx301 said:
There's a great guide Stickied in the general 6p forum by Heisenberg. I always reference that when I'm flashing via fastboot to make sure I'm doing it correctly. I'd start there!
Click to expand...
Click to collapse
Damn....been out of the forums too long and when I'm back it's all pixel stuff. Totally forget about Heisenberg. Thanks
Does the Pixel XL flash the same way in ADB with the same fastboot commands as the Nexus 6P does(boot, recovery, system, radio, bootloader, etc)?
dcillusions77 said:
Does the Pixel XL flash the same way in ADB with the same fastboot commands as the Nexus 6P does(boot, recovery, system, radio, bootloader, etc)?
Click to expand...
Click to collapse
Yes...use latest SDK
galaxys said:
Yes...use latest SDK
Click to expand...
Click to collapse
Ty sir
dcillusions77 said:
Does the Pixel XL flash the same way in ADB with the same fastboot commands as the Nexus 6P does(boot, recovery, system, radio, bootloader, etc)?
Click to expand...
Click to collapse
Yes, they flash the same way, but there are a decent bit of variances. There are many (and duplicate) partitions in the pixel, when comparing it to the older nexus devices.
Besides manually fastboot flashing each image to each partition, you can use the same format that the flash-all.(bat/sh) uses. Here is in short how the script would run......
fastboot flash bootloader bootloader.img
fastboot reboot bootloader
fastboot flash radio radio.img
fastboot reboot bootloader
fastboot -w update image.zip
of course, the names of the files are dependent upon which image you are flashing, but all files names will be in the factory image archive.
noidea24 said:
Yes, they flash the same way, but there are a decent bit of variances. There are many (and duplicate) partitions in the pixel, when comparing it to the older nexus devices.
Besides manually fastboot flashing each image to each partition, you can use the same format that the flash-all.(bat/sh) uses. Here is in short how the script would run......
fastboot flash bootloader bootloader.img
fastboot reboot bootloader
fastboot flash radio radio.img
fastboot reboot bootloader
fastboot -w update image.zip
of course, the names of the files are dependent upon which image you are flashing, but all files names will be in the factory image archive.
Click to expand...
Click to collapse
Ok simple enough thanks??
noidea24 said:
Yes, they flash the same way, but there are a decent bit of variances. There are many (and duplicate) partitions in the pixel, when comparing it to the older nexus devices.
Besides manually fastboot flashing each image to each partition, you can use the same format that the flash-all.(bat/sh) uses. Here is in short how the script would run......
fastboot flash bootloader bootloader.img
fastboot reboot bootloader
fastboot flash radio radio.img
fastboot reboot bootloader
fastboot -w update image.zip
of course, the names of the files are dependent upon which image you are flashing, but all files names will be in the factory image archive.
Click to expand...
Click to collapse
It really is true if you don't use it you lose it. Used to know these commands like my childhood beat friends phone number. Now I suffer from CRS. What makes it worse is on top of heisenburgs tutorials (which I'm back to my N6P) if you just open the flash all file with text editor..... It friggin spells out all the commands you need. Not really sure I felt the need to flash system, boot, modem etc when I could flash update image.zip. Grrrr. I need to start playing around more again.
Anyway the wife gave her S7 to our daughter so she took my pixel (had to set it back to stock for her) and I'm back to my N6P until the pixel 2 comes out.