When I try to run the flash-all.sh script from the November 2017 release of Android 8, I am getting the following error on my phone
Code:
$ ./flash-all.sh
// Script output until final command in script
wiping userdata...
/usr/local/bin/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
Does anyone know what is going on here? It works when I remove the -w flag from the last command in the shell script
It's the same for me... Really strange, I had to sideload the full ota to update
same here as well, are you guys rooted ??
-Z
I'm trying to run my with -w
fastboot -w update factory_image.zip
still getting the same error.
Yes, I am rooted.
Update: Tried November image and got the same thing. I don't think it's related to the factory image, but possibly something with the phone. Previously, I was able to flash the Nov. image just fine.
By the way, I'm on the first Pixel XL.
zipsnet said:
same here as well, are you guys rooted ??
-Z
Click to expand...
Click to collapse
I am rooted with Magisk. No custom recovery or anything. I'm planning to unroot and reload factory firmware except the flashing isn't working
darkfire404 said:
I am rooted with Magisk. No custom recovery or anything. I'm planning to unroot and reload factory firmware except the flashing isn't working
Click to expand...
Click to collapse
Have you guys updated the Android platform & ADB?
That might be the problem.
the script flash-all.bat is expecting a different version of the bootloader. What I did is to revert back to November image, sideload OTA and then you can do a flash-all.bat.
The solution to this problem is the following
Re-flash your dtbo.img from your factory img.
fastboot flash dtbo dtbo.img
Also , If you guys are running 8.1 do not use Magisk Manager: v5.4.3 since this version will patch up your dtbo.img. Instead use magisk-manager 5.4.0
Make sure you Uninstall Magisk Manager before re-flashing dtbo. Also - open the magisk manager and go to settings and turn-off update notification option
Let me know if that helps !!
Thanks to @Shadow/Walker for this solution to another problem
So after you run this command, then you can run the flash-all command?
I'm getting this error trying to flash the Dec 8.1 factory image on my Pixel 2.
Have you all tried to download the image again? The image might be corrupted.
I flashed the factory image as soon as it was available. Everything went smooth. I had 8.1 DP2 installed prior, and it was rooted. I didn't uninstall the Magisk.
All I did was boot into the bootloader and run flash-all.bat.
Yes, I just downloaded the image a little while ago. I'm not rooted, just have unlocked bootloader on Pixel 2. I sideloaded the image yesterday, and just wanted to do a clean flash of the stock image when I ran into the issue. I was previously on the Nov. 8.0 build.
Hi guys! So I figured out why the error in the OP occurs. Looks like samteeee had the right idea to update platform-tools, but it's a bit deeper than that. This error occurs if you are using the flash-all.bat with ONLY fastboot.exe. The command this batch file attempts to run is "fastboot format userdata". If you run this command with fastboot.exe alone, you will get this message. The solution is to download the latest platform-tools from Google, extract it all, and put all of those extracted filed into the same folder with the factory image with the flash-all.bat file. I just tried it and was finally able to successfully flash the factory image. Hope this helps!
This is very helpful, thanks for posting.
Sent from my Pixel 2 using Tapatalk
alarsama said:
Hi guys! So I figured out why the error in the OP occurs. Looks like samteeee had the right idea to update platform-tools, but it's a bit deeper than that. This error occurs if you are using the flash-all.bat with ONLY fastboot.exe. The command this batch file attempts to run is "fastboot format userdata". If you run this command with fastboot.exe alone, you will get this message. The solution is to download the latest platform-tools from Google, extract it all, and put all of those extracted filed into the same folder with the factory image with the flash-all.bat file. I just tried it and was finally able to successfully flash the factory image. Hope this helps!
Click to expand...
Click to collapse
For the record this did not work for me, Maybe because i ran the coommand `sudo install adb /ust/local/bin` after downloading the latest platform-tools. However I did download platform-tools and move everything in there as you are suppose to.
Any way the solution for me was to edit the `flash-all.sh` file and force it to run fastboot relative to platform.
So what I did was replace every instance of `flashboot` with `/path/to/platform-tools/flashboot` and it worked flawlessly and my stock ota boots up nice
my working flash-all.sh file contents:
Code:
#!/bin/sh
./fastboot flash bootloader bootloader-taimen-tmz12b.img
./fastboot reboot-bootloader
sleep 5
./fastboot flash radio radio-taimen-g8998-00164-1710262031.img
./fastboot reboot-bootloader
sleep 5
./fastboot -w update image-taimen-opm1.171019.013.zip
My experience has been to not extract the folder inside the extracted download. Just put it in with the platform tools. Seems the flash-all is expecting to extract that before flashing.
And I made the mistake of not unlocking critical. The January image has a new bootloader and won't install the system image without doing the bootloader.
@Larzzzz82, the first command really inside `flash-all` is `fastboot flash bootloader bootloader-taimen-tmz12b.img`, so I think you do need to extract the initial stock OTA zip file. At least I need to, and the command seems to explain why.
I just retested it today, the issue in the OP for me was because the `sudo install adb` command moves fastboot into your path, so when you type `flash-all.sh` its running fastboot from /usr/local/bin when it should be running in the same directory as your flashables.
So alarmsama's solution actually would work for me if i just delete /usr/local/bin/fastboot, or remove it from my path, or maybe even just drop a symlink from the directory containing the flashables.
Personally im going to just keep using my hacked script because i prefer it, as you can see from the code you can really have the files anywhere you want if you use absolute paths.
Larzzzz82 said:
My experience has been to not extract the folder inside the extracted download. Just put it in with the platform tools. Seems the flash-all is expecting to extract that before flashing.
And I made the mistake of not unlocking critical. The January image has a new bootloader and won't install the system image without doing the bootloader.
Click to expand...
Click to collapse
This is what worked for me. It seems that the process expects more than the 4 files I usually use to flash the images, and one of them was in the platform tools folder.
I scratched me head for a few minutes then first time i flashed this awesome piece of hardware. I have a lot more reading to do. Flashing this phone is completely different than my N6.
alarsama said:
Hi guys! So I figured out why the error in the OP occurs. Looks like samteeee had the right idea to update platform-tools, but it's a bit deeper than that. This error occurs if you are using the flash-all.bat with ONLY fastboot.exe. The command this batch file attempts to run is "fastboot format userdata". If you run this command with fastboot.exe alone, you will get this message. The solution is to download the latest platform-tools from Google, extract it all, and put all of those extracted filed into the same folder with the factory image with the flash-all.bat file. I just tried it and was finally able to successfully flash the factory image. Hope this helps!
Click to expand...
Click to collapse
oh you are god, thank you :good:
alarsama said:
Hi guys! So I figured out why the error in the OP occurs. Looks like samteeee had the right idea to update platform-tools, but it's a bit deeper than that. This error occurs if you are using the flash-all.bat with ONLY fastboot.exe. The command this batch file attempts to run is "fastboot format userdata". If you run this command with fastboot.exe alone, you will get this message. The solution is to download the latest platform-tools from Google, extract it all, and put all of those extracted filed into the same folder with the factory image with the flash-all.bat file. I just tried it and was finally able to successfully flash the factory image. Hope this helps!
Click to expand...
Click to collapse
you are a genius and my life saver~! managed to flash after...
Related
Hello everyone,
Need some help here, i don't want to factoy flash again, i have a nexus 7 2013 wifi on Lollipop (5.0) rooted with a custom kernel and TWRP.
How to update with the new OTA to 5.0.1, without loosing data and without having FC after the flash ?
Is there a way to flash it with TWRP or with Nexus Root Toolkit ?
I read that i can download the 5.01 system image from Google, extract the system.img from it and flash it in fasboot and i will conserve my data and be updated to 5.0.1.
Is that correct and without issues?
^Yes.
Fastboots the best way to go. No toolkits needed. Takes a couple minutes.
The normal commands to update would be:
fastboot flash bootloader bootloadername.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Since the bootloader didn't change you can skip that part. The kernel (boot) didn't change either this time I don't think but I'd flash it always when flashing system.
Just drag system.img and boot.img to your fastboot folder (platform tools if you downloaded the sdk), hold shift and right click> open command window here then run the above commands.
Let it boot then reflash su from twrp.
Pretty sure you can also drag the image-razor.zip to your fastboot folder and run fastboot update imagename.zip. You will have to reflash twrp though.
Hi, this is a little off topic.
I have a 4.4.4 rooted one and it failed to update to 5.0.1. Now it says system is update even though it still 4.4.4. Is there anyway for me to fix it and get update?
yosmokinman said:
^Yes.
Fastboots the best way to go. No toolkits needed. Takes a couple minutes.
The normal commands to update would be:
fastboot flash bootloader bootloadername.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Since the bootloader didn't change you can skip that part. The kernel (boot) didn't change either this time I don't think but I'd flash it always when flashing system.
Just drag system.img and boot.img to your fastboot folder (platform tools if you downloaded the sdk), hold shift and right click> open command window here then run the above commands.
Let it boot then reflash su from twrp.
Pretty sure you can also drag the image-razor.zip to your fastboot folder and run fastboot update imagename.zip. You will have to reflash twrp though.
Click to expand...
Click to collapse
Is running fastboot format cache necessary?
^I'm no expert but I can't see why not to run it, not going to hurt anything and could possibly save you some problems later.
anhhuy1605 I'd just go to the factory images page download it and do a full clean install. I would not recommend trying to upgrade from KK and keeping data. Though I'm sure it's worked fine for lots of people.
yosmokinman said:
^Yes.
Fastboots the best way to go. No toolkits needed. Takes a couple minutes.
The normal commands to update would be:
fastboot flash bootloader bootloadername.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Since the bootloader didn't change you can skip that part. The kernel (boot) didn't change either this time I don't think but I'd flash it always when flashing system.
Just drag system.img and boot.img to your fastboot folder (platform tools if you downloaded the sdk), hold shift and right click> open command window here then run the above commands.
Let it boot then reflash su from twrp.
Pretty sure you can also drag the image-razor.zip to your fastboot folder and run fastboot update imagename.zip. You will have to reflash twrp though.
Click to expand...
Click to collapse
It's all done, i flashed only the system.img then TWRP and elementalx, i can't live without the DT2W.
Thank You for your very detailed post.
anhhuy1605 said:
Hi, this is a little off topic.
I have a 4.4.4 rooted one and it failed to update to 5.0.1. Now it says system is update even though it still 4.4.4. Is there anyway for me to fix it and get update?
Click to expand...
Click to collapse
First thing first:
1. Uninstall any mod and busybox and xposed (Make sur that your system is clean) thant Unroot with supersu
2. Flash the stock boot (kernel) and stock recovery
3. Sideload the ota for 5.0 and flash it
Hopefully it will be allright but don't forget to backup your data with titanium backup to your computer.
Hello eddy0147,
from where did you get the system.img for 5.0.1?
eddy0147 said:
It's all done, i flashed only the system.img then ...
Click to expand...
Click to collapse
Thanks!
tungdil
tungdil said:
Hello eddy0147,
from where did you get the system.img for 5.0.1?
Thanks!
tungdil
Click to expand...
Click to collapse
If you decompress the new Factory Image from here : https://developers.google.com/android/nexus/images
You're welcome
Thank you very much! :good:
Actually I expected that this factory image would also only contain a system.new.dat just like the LRX21P did before. That's why I din't even have a look at it. I just downloaded and extracted it, and could convert it to a mountable image (using simg2img)
Cheers,
tungdil
P.S.: Just finished flashing Stock 5.0.1 as secondary ROM with MultiROM after building a flashable zip using this system.img. Thanks again eddy0147 for the hint :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.
Hi, I am i dire straits. I have a pixel xl running pure nexus, rooted and on tmobile. I am trying to get back to completely stock. i tried followig the instructions but somewhere I messed up. Currently phone will just bootloop. I went into cmd, typed adb devices, nothing came up so stupid me, I continued anyways with flash-all.bat, something went wrong in command prompt, then i proceeded to reboot from fastboot, this is where i am now. I have attached pictures of the command prompt screens and of the folder in adb fastboot on my pc that I think contained all the files. I do't know where I went wrong. If you can help, it would be greatly appreciated. I can only correspond via pc. Please, I hope someone can help me.
If someone has the time to walk me through step by step, it would much appreciated.
Doesnt looked bricked to me
maybe your factory image is incomplete.
Flash the parts individually see what happens.
Commands i use. note you need to use your own paths or copy mine
) Execute fastboot commands
fastboot flash bootloader c:\_PIXEL_XL_\bootloader.img
fastboot reboot-bootloader
fastboot flash radio c:\_PIXEL_XL_\radio.img
fastboot reboot-bootloader
fastboot flash boot_a c:\_PIXEL_XL_\boot.img
fastboot flash boot_b c:\_PIXEL_XL_\boot.img
fastboot flash system c:\_PIXEL_XL_\system.img
fastboot flash system_b c:\_PIXEL_XL_\system_other.img
fastboot flash vendor c:\_PIXEL_XL_\vendor.img
fastboot flash modem c:\_PIXEL_XL_\modem.img
fastboot reboot-bootloader
fastboot boot c:\_PIXEL_XL_\twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip <--- if you want to root.
5 Still in twrp flash verifiedboot signer.zip
6 Reboot
parakleet said:
Doesnt looked bricked to me
maybe your factory image is incomplete.
Flash the parts individually see what happens.
Commands i use. note you need to use your own paths or copy mine
) Execute fastboot commands
fastboot flash bootloader c:\_PIXEL_XL_\bootloader.img
fastboot reboot-bootloader
fastboot flash radio c:\_PIXEL_XL_\radio.img
fastboot reboot-bootloader
fastboot flash boot_a c:\_PIXEL_XL_\boot.img
fastboot flash boot_b c:\_PIXEL_XL_\boot.img
fastboot flash system c:\_PIXEL_XL_\system.img
fastboot flash system_b c:\_PIXEL_XL_\system_other.img
fastboot flash vendor c:\_PIXEL_XL_\vendor.img
fastboot flash modem c:\_PIXEL_XL_\modem.img
fastboot reboot-bootloader
fastboot boot c:\_PIXEL_XL_\twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip <--- if you want to root.
5 Still in twrp flash verifiedboot signer.zip
6 Reboot
Click to expand...
Click to collapse
No offence but i am lost by what you said, I am trying to get back to completely stock. Is part of my issue the fact that command prompt didn't detect my device? or no?
I'm not exactly sure what to do with the information you shared, sorry
I the tutorial i found it says to make sure the command prompt sees your device but doesnt say what to do when it doesnt see it.
Also, I downloaded the may factory image, i believe it was version O
Am I suppose to use the O image or the L image (verizon). I am on tmobile. I used the O image when i ran into trouble
jreink01 said:
Am I suppose to use the O image or the L image (verizon). I am on tmobile. I used the O image when i ran into trouble
Click to expand...
Click to collapse
If you did not get your phone from Verizon use this
7.1.2 (N2G47O, May 2017)
Download the zip
unpack all the zip files some are nested so unzipping one creates more keep unzipping until there are no more then gather the following img files
bootloader.img
radio.img
boot.img
system.img
system_other.img
vendor.img
modem.img
Some of those names are cut down as i hate typing long strings, jsut rename them as such.
Create a folder on root of c:\_PIXEL_XL_
put all the files there.
You will use way less files than you unpacked
once you have done that run the following commands
copy and paste
fastboot flash bootloader c:\_PIXEL_XL_\bootloader.img
fastboot reboot-bootloader
fastboot flash radio c:\_PIXEL_XL_\radio.img
fastboot reboot-bootloader
fastboot flash boot_a c:\_PIXEL_XL_\boot.img
fastboot flash boot_b c:\_PIXEL_XL_\boot.img
fastboot flash system c:\_PIXEL_XL_\system.img
fastboot flash system_b c:\_PIXEL_XL_\system_other.img
fastboot flash vendor c:\_PIXEL_XL_\vendor.img
fastboot flash modem c:\_PIXEL_XL_\modem.img
fastboot reboot
After last reboot just wait and you will be back at stock
if that doesnt work
Download latest version of TWRP place it in C:\_PIXEL_XL_
rename it twrp.img, again i hate typing long strings
from bootloader run
fastboot boot c:\_PIXEL_XL_\twrp.img
This will take you into twrp
you might need to wipe system and cache and data,
From memory the fourth entry at bottom is internal memory or user data, in any event if you do not check that your data stays on the phone.
Once you have wiped the other 3 rerun the fastboot commands and you will be back at stock
add the twrp and supersu commands from earlier to add root.
dont forget the signatureverify.img if you are doing that.
good luck.
you arent bricked
you just need to find the correct combination of steps to get your phone where you want it to be
Thanks for the response. I am having a hard time with this, the zip file i downloaded from the google website, when i open it, there are only 6 files, 1 of which is a zip file (marlin). When I open marlin it shows a bunch of files, none of which you mentioned. I am confused, was wondering if you would be nice enough to walk me through this over the phone, i would be really grateful.
Is there anyone that can walk me through this this on the phone, the more i try to understand this, the more cofused i get. pLeASE!!!!
jreink01 said:
Is there anyone that can walk me through this this on the phone, the more i try to understand this, the more cofused i get. pLeASE!!!!
Click to expand...
Click to collapse
Yes, i sent you a PM.
HALV0RS3N said:
Yes, i sent you a PM.
Click to expand...
Click to collapse
thanks, sent you my #
Okay so I had the exact problem yesterday. To to the Google developers site and download the official Google pixel or xl 7.1.2 nougut ota update. Once that's downloaded, go to your phone, I had all the exact same screens on my phone so it should work. Hold down the power button until it completely shuts down. Then hold the power and volume down to go to recovery mode, if it goes back to the ext 4 screen, try it again until it goes to recovery mode, then on command prompt type, fastboot boot twrp.img then once it's in twrp, go to advanced-then adb sideload and click both boxed and then swipe to enter sideload. Then on your computer, type adb sideload "file name for Google update" and hit enter. That should do the trick. Like I said, I had the exact same problem yesterday
---------- Post added at 06:56 PM ---------- Previous post was at 06:50 PM ----------
Also, I forgot to mention, download the twrp image file from the Internet. Shouldn't be hard to find just make sure it's the latest. Put that file in the adb file on your computer same with the Google update for your phone. Do not unzip either file. That's very important. DO NOT UNZIP THE UPDATE File. When you type in the twrp.img make sure you type img. And when you flash the update, make sure at the end of the file name you put
.zip ex( marlinpixelxl7.1.2.zip)
jreink01 said:
Hi, I am i dire straits. I have a pixel xl running pure nexus, rooted and on tmobile. I am trying to get back to completely stock. i tried followig the instructions but somewhere I messed up. Currently phone will just bootloop. I went into cmd, typed adb devices, nothing came up so stupid me, I continued anyways with flash-all.bat, something went wrong in command prompt, then i proceeded to reboot from fastboot, this is where i am now. I have attached pictures of the command prompt screens and of the folder in adb fastboot on my pc that I think contained all the files. I do't know where I went wrong. If you can help, it would be greatly appreciated. I can only correspond via pc. Please, I hope someone can help me.
If someone has the time to walk me through step by step, it would much appreciated.
Click to expand...
Click to collapse
Looking at your screen shot you didn't let the file finish flashing. It sticks at the "does not contain" for a bit before it continues.
You were doing it right. You just didn't wait.
If it wasn't going to work it would eventually give you a failure and jump to the command prompt.
jreink01 said:
Hi, I am i dire straits. I have a pixel xl running pure nexus, rooted and on tmobile. I am trying to get back to completely stock. i tried followig the instructions but somewhere I messed up. Currently phone will just bootloop. I went into cmd, typed adb devices, nothing came up so stupid me, I continued anyways with flash-all.bat, something went wrong in command prompt, then i proceeded to reboot from fastboot, this is where i am now. I have attached pictures of the command prompt screens and of the folder in adb fastboot on my pc that I think contained all the files. I do't know where I went wrong. If you can help, it would be greatly appreciated. I can only correspond via pc. Please, I hope someone can help me.
If someone has the time to walk me through step by step, it would much appreciated.
Click to expand...
Click to collapse
i had the same issue and this worked
https://forum.xda-developers.com/showpost.php?p=70972735&postcount=3
dont follow it word for word as that its not the XL version in the post.
RedBlueGreen said:
i had the same issue and this worked
https://forum.xda-developers.com/showpost.php?p=70972735&postcount=3
dont follow it word for word as that its not the XL version in the post.
Click to expand...
Click to collapse
OP was flashing to stock. Didn't let it finish though.
Hello everyone,
So today is the day (at least for me) that I want to try applying the Jan OTA to my Pixel 2 XL. I am currently using Magisk and ElementalX kernel and was wondering if anyone has tried this yet (I know, the OTA just came out)?
If someone has an idea on the process to do this please let me know.
Thanks!
ilatimer1 said:
Hello everyone,
So today is the day (at least for me) that I want to try applying the Jan OTA to my Pixel 2 XL. I am currently using Magisk and ElementalX kernel and was wondering if anyone has tried this yet (I know, the OTA just came out)?
If someone has an idea on the process to do this please let me know.
Thanks!
Click to expand...
Click to collapse
Kernel, TWRP and Magisk get overwritten by the OTA. You need to reinstall.
Also I'd recommend to disable all Substratum themes before flashing - for me this led to a Bootpool...
ilatimer1 said:
Hello everyone, So today is the day (at least for me) that I want to try applying the Jan OTA to my Pixel 2 XL. I am currently using Magisk and ElementalX kernel and was wondering if anyone has tried this yet (I know, the OTA just came out)? If someone has an idea on the process to do this please let me know. Thanks!
Click to expand...
Click to collapse
I recommend using the full image (not OTA) downloaded from Google. Extract the files from the zip into your ADB folder, open up flash-all.bat with a text editor and remove the -w (wipe) switch from the script. Save. Then just execute that file from a fastboot prompt. You will not lose data or settings, but you will lose TWRP, kernel & Magisk. When the script finishes running, boot back into fastboot mode (bootloader) and from your PC, fastboot boot twrp. When it loads queue up (add zips) TWRP.zip, Kernel.zip, Magisk.zip and let her rip. Reboot to system and everything will be normal. Just make sure you have those three files (latest versions) on your phone AND the twrp.img on your PC so you can boot to it. Takes about 3 minutes if you have all the files in place before starting.
v12xke said:
I recommend using the full image (not OTA) downloaded from Google. Extract the files from the zip into your ADB folder, open up flash-all.bat with a text editor and remove the -w (wipe) switch from the script. Save. Then just execute that file from a fastboot prompt. You will not lose data or settings, but you will lose TWRP, kernel & Magisk. When the script finishes running, boot back into fastboot mode (bootloader) and from your PC, fastboot boot twrp. When it loads queue up (add zips) TWRP.zip, Kernel.zip, Magisk.zip and let her rip. Reboot to system and everything will be normal. Just make sure you have those three files (latest versions) on your phone AND the twrp.img on your PC so you can boot to it. Takes about 3 minutes if you have all the files in place before starting.
Click to expand...
Click to collapse
What's the difference between this step and sideloading the OTA?
Edit: nevermind. Realized you'd flash-all without the -w if you have TWRP.
peoplesindian said:
What's the difference between this step and sideloading the OTA?
Edit: nevermind. Realized you'd flash-all without the -w if you have TWRP.
Click to expand...
Click to collapse
Yes, OTA's fail to execute if you have modified the boot or system partition. An OTA is an incremental only update that selectively writes certain files and is (usually) much, much smaller. This is appropriate for a stock, unmodified device. Lots of people get tired of waiting for the OTA to come, and so they just update manually by sideloading the OTA through the stock recovery (over adb). Nothing wrong with that, and it this will sometimes bring a phone back from bootlooping or other serious problems like FC's and crashing.
A full image contains the full partition images and they are written to the device fully and unconditionally via fastboot. You can only flash a full image if your bootloader is unlocked. It essentially erases the partitions by overwriting the entire contents from beginning to end. Some would argue this more "complete" method is less likely to result in errors, or corrupt files. Removing the -w switch from the batch file script prevents the script from overwriting the userdata partition where all your media, user apps and settings are. Some call this "dirty" flashing.
v12xke said:
I recommend using the full image (not OTA) downloaded from Google. Extract the files from the zip into your ADB folder, open up flash-all.bat with a text editor and remove the -w (wipe) switch from the script. Save. Then just execute that file from a fastboot prompt. You will not lose data or settings, but you will lose TWRP, kernel & Magisk. When the script finishes running, boot back into fastboot mode (bootloader) and from your PC, fastboot boot twrp. When it loads queue up (add zips) TWRP.zip, Kernel.zip, Magisk.zip and let her rip. Reboot to system and everything will be normal. Just make sure you have those three files (latest versions) on your phone AND the twrp.img on your PC so you can boot to it. Takes about 3 minutes if you have all the files in place before starting.
Click to expand...
Click to collapse
did exactly this, and all is fine.
otonieru said:
did exactly this, and all is fine.
Click to expand...
Click to collapse
Same
trim81 said:
Same
Click to expand...
Click to collapse
Interesting that Google seems to claim that updating with the OTA should create less problems with this January update:
https://9to5google.com/2018/01/02/psa-google-pixel-2-users-lag-sideload-jan-sec-update-fix/
xclub_101 said:
Interesting that Google seems to claim that updating with the OTA should create less problems with this January update:
https://9to5google.com/2018/01/02/psa-google-pixel-2-users-lag-sideload-jan-sec-update-fix/
Click to expand...
Click to collapse
That article is quite dubious with no source about google confirming the issue :silly:
v12xke said:
Then just execute that file from a fastboot prompt.
Click to expand...
Click to collapse
REALLY dumb question, but how do you execute a .bat from fastboot? Or do you mean with the phone in bootloader/fastboot mode, run the modified .bat?
EDIT: Never mind... put the phone in Bootloader/fastboot mode. Ran the modified .BAT from command prompt within the Platform-tools folder.
I did it last night with no issues. The process is pretty simple.
1) adb reboot bootloader
2) fastboot flash boot /location/of/december/boot.img
3) fastboot flash dtbo /location/of/december/dtbo.img
4) reboot
5) allow the OTA to install
6) adb reboot bootloader
7) fastboot boot twrp
8) install TWRP then custom kernel then Magisk
7) reboot
v12xke said:
I recommend using the full image (not OTA) downloaded from Google. Extract the files from the zip into your ADB folder, open up flash-all.bat with a text editor and remove the -w (wipe) switch from the script. Save. Then just execute that file from a fastboot prompt. You will not lose data or settings, but you will lose TWRP, kernel & Magisk. When the script finishes running, boot back into fastboot mode (bootloader) and from your PC, fastboot boot twrp. When it loads queue up (add zips) TWRP.zip, Kernel.zip, Magisk.zip and let her rip. Reboot to system and everything will be normal. Just make sure you have those three files (latest versions) on your phone AND the twrp.img on your PC so you can boot to it. Takes about 3 minutes if you have all the files in place before starting.
Click to expand...
Click to collapse
I followed this and everything is installed perfectly with root.
Thank you ??
sn0warmy said:
I did it last night with no issues. The process is pretty simple.
1) adb reboot bootloader
2) fastboot flash boot /location/of/december/boot.img
3) fastboot flash dtbo /location/of/december/dtbo.img
4) reboot
5) allow the OTA to install
6) adb reboot bootloader
7) fastboot boot twrp
8) install TWRP then custom kernel then Magisk
7) reboot
Click to expand...
Click to collapse
Slow internet here, you mind uploading the boot and dtbo.img?
sn0warmy said:
I did it last night with no issues. The process is pretty simple.
1) adb reboot bootloader
2) fastboot flash boot /location/of/december/boot.img
3) fastboot flash dtbo /location/of/december/dtbo.img
4) reboot
5) allow the OTA to install
6) adb reboot bootloader
7) fastboot boot twrp
8) install TWRP then custom kernel then Magisk
7) reboot
Click to expand...
Click to collapse
I like this idea better than the flash all, but forgive me as I haven't flashed any Android 8.1 devices yet.
Is dtbo the new name for what used to be called system?
Any help would be appreciated. This is my first time dealing with Magisk, I've always used SuperSU in the past. I finally used my unlock code and the bootloader says unlocked, that was easy. I installed the Magisk Manager apk but am having trouble with Magisk itself. I'm used to flashing in TWRP, which I apparently can't install until Magisk is installed. I have two options, install - download zip only, and patch boot image file...
So I was trying to use the boot image file from this thread https://forum.xda-developers.com/mate-20-x/development/guide-mate-20-x-root-t3883269 and either patch it or used the patched one, but when my phone goes into the bootloader screen, adb is not recognizing the phone or finding the file which I set inside the adb folder itself. Sorry, I am not a noob to flashing. Done many many phones rooting, unlocking, roms, modems, etc. I am just new to adb and Magisk. Any help would be great as I've been at this all day reading and downloading things I needed. Thank you.
EDIT: I'm not sure if I'm putting the .img file in the wrong folder??? I am stuck on step 5 in that thread.
So more specifics on where I am stuck, hoping for help. I've tried, tried and tried and Googled lots...
When I run fastboot devices it does show my phone. I took the Patched Recovery Ramdisk for EVR-AL00 from the site above. I renamed it to recovery.img and put it inside the folder c:\adb where adb and fastboot are located. When I am in the command prompt under c:\adb> I put "fastboot flash recovery_ramdisk recovery_ramdiskMagiskrecovery.img". And I get this error... fastboot: error: cannot load 'recovery_ramdiskMagiskrecovery.img': No such file or directory
DavidMT909 said:
So more specifics on where I am stuck, hoping for help. I've tried, tried and tried and Googled lots...
When I run fastboot devices it does show my phone. I took the Patched Recovery Ramdisk for EVR-AL00 from the site above. I renamed it to recovery.img and put it inside the folder c:\adb where adb and fastboot are located. When I am in the command prompt under c:\adb> I put "fastboot flash recovery_ramdisk recovery_ramdiskMagiskrecovery.img". And I get this error... fastboot: error: cannot load 'recovery_ramdiskMagiskrecovery.img': No such file or directory
Click to expand...
Click to collapse
If you renamed the file recovery.img then the command should be
'fastboot flash recovery_ramdisk recovery.img'
lightning413 said:
If you renamed the file recovery.img then the command should be
'fastboot flash recovery_ramdisk recovery.img'
Click to expand...
Click to collapse
Thank you, but I may have messed up my phone now. I was trying this from the thread above, and even his example shows Magisk in it.
Step 5:
-Once the device is in bootloader and connected to the PC, run the command "fastboot flash recovery_ramdisk recovery_ramdiskMagiskVARIANT" with VARIANT being whatever ramdisk you downloaded. For example with AL00 you would input "fastboot flash recovery_ramdisk recovery_ramdiskMagiskAL00.img"
As soon as I tried your way it seemed to work... except when I booted it still did not have root. And now I cannot get into fastboot or recovery. It just keeps rebooting to the phone if I try recovery or fastboot. I used to be able to do this stuff following directions. It just doesn't seem to be working out. Thanks for trying.
My devices still lists in adb, but not fastboot. I'm still working on this. I do make an effort to do things myself.
Okay, I don't know what happened. My Magisk had an update, I installed it and rebooted and for the first time two green checks in Magisk, ran root checker and I have root. So hopefully I can install TWRP now and on to the ROM. Slow progress...
I have TWRP. Time to make a backup, and I'll install a ROM next.