Develop Bugs

January security update?

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.

How do I flash vendor images?

Upon booting the 2nd RC build of Dirty Unicorns, I am faced with the dialog saying that the vendor image is out of date,
I have downloaded one from developer.google.com, I just need to know what I have to do to get it onto my Pixel.

fastboot flash vendor vendor.img

Which leads to the next question (or two):
Using a Windows computer, how do I compile the img file? (I could only find the binary at google, a tgz archive containing an .sh file)
Is there a fastboot flashable image available?

pTeronaut said:
Which leads to the next question (or two):
Using a Windows computer, how do I compile the img file? (I could only find the binary at google, a tgz archive containing an .sh file)
Is there a fastboot flashable image available?
Click to expand...
Click to collapse
If you download the full image from Google there is a second compressed file in the full image that has a vendor.img file. Also the just below the download link on the forum for the du ROM there is a link for the vendor image .

The third ROM release from DU does not require vendor image flash if you're already on the latest image.
Otherwise, reboot to bootloader.
Open your command prompt.
Use the command "fastboot flash vendor vendor.img".
I go the extra mile and do two commands.
"fastboot flash vendor_a vendor.img"
"fastboot flash vendor_b vendor.img"
Though it's probably not necessary.
As mentioned above, download the full Google image.
https://developers.google.com/android/images
Then extract it, and keep extracting it again and again until you find the vendor.img.

You can use TWRP to flash the vendor image. No need for fastboot.

spaceman860 said:
You can use TWRP to flash the vendor image. No need for fastboot.
Click to expand...
Click to collapse
Does that work with twrp on pixel?

toknitup420 said:
Does that work with twrp on pixel?
Click to expand...
Click to collapse
Yes

spaceman860 said:
Yes
Click to expand...
Click to collapse
Sweet deal. I didn't know that was working on pixel yet. Good looks for the info.

Flashing
If I try to do fastboot flash vendor vendor.img it says Failed remote command not allowed.
Can someone help me?

Vestell said:
If I try to do fastboot flash vendor vendor.img it says Failed remote command not allowed.
Can someone help me?
Click to expand...
Click to collapse
Did you unzip the file twice
There another zip inside the folder. Extract that and open your command prompt in there

mac796 said:
Did you unzip the file twice
There another zip inside the folder. Extract that and open your command prompt in there
Click to expand...
Click to collapse
I exstract it to a ADB folder and I opened the command prop there.

Vestell said:
If I try to do fastboot flash vendor vendor.img it says Failed remote command not allowed.
Can someone help me?
Click to expand...
Click to collapse
Hello... Is your bootloader unlocked?
Good luck...

5.1 said:
Hello... Is your bootloader unlocked?
Good luck...
Click to expand...
Click to collapse
Hello,yes its unlocked, I flashed Revolution recovery for nougat, I tryed to do /vendor mount -f in terminal and it says:
Permission Denied,If I flash extracted system.img with fastboot flash system system.img it says OKAY and when its done, I boot up my p9 lite but it wont boot to the system.

Vestell said:
Hello,yes its unlocked, I flashed Revolution recovery for nougat, I tryed to do /vendor mount -f in terminal and it says:
Permission Denied,If I flash extracted system.img with fastboot flash system system.img it says OKAY and when its done, I boot up my p9 lite but it wont boot to the system.
Click to expand...
Click to collapse
Hello I never heard of revolution recovery...
I know about TWRP. You can install vendor.img with TWRP by the way. :good:
Also, maybe you should post in the P9 lite forum... This is the Google Pixel XL forum...
Good luck...

5.1 said:
Hello... Is your bootloader unlocked?
Good luck...
Click to expand...
Click to collapse
5.1 said:
Hello I never heard of revolution recovery...
I know about TWRP. You can install vendor.img with TWRP by the way. :good:
Also, maybe you should post in the P9 lite forum... This is the Google Pixel XL forum...
Good luck...
Click to expand...
Click to collapse
Its a TWRP for p9 lite,if I try to install it I can choose between Recovery and boot, and srry that Im posting in google pixel XL forum,but im just looking for solutions that I could try, btw there is no P9 lite forum

Vestell said:
Its a TWRP for p9 lite,if I try to install it I can choose between Recovery and boot, and srry that Im posting in google pixel XL forum,but im just looking for solutions that I could try, btw there is no P9 lite forum
Click to expand...
Click to collapse
Sorry... Since i don't own the device, it's unlikely I can help you. Maybe flashing g P9 lite requires a different process, I don't know. Again, i guess you won't find much help in this forum.
Good luck...

where do i get the vendor image to install in twrp? the only thing that showed up under, "install image" was twrp. Do I need to install a factory vendor image from google?

ken2736 said:
where do i get the vendor image to install in twrp? the only thing that showed up under, "install image" was twrp. Do I need to install a factory vendor image from google?
Click to expand...
Click to collapse
U need extracted vendor img from stock Google zip then flash image in twrp. Yes click image button. Then click on vendor then flash.

hey everyone,
I recently purchased a used Nexus 5x that is running fine so far. my only problem is i get the message "internal problem, contact manufacturer" after every boot.
the phone is running android 7.0 (NDR90S) and the seller told me he trie to root and flash custom firmware but somehow the boot loader always locked itself. Now its not possible to perform an OTA update to 8.0 (get it offered all the time).
According to the developer setting the Bootloader is unlocked. I read that it should be fine to flash the vendor.image. Is this correct so far?

Flash Question

I rooted my Unlocked xl 2 using a method I found online. Used it a couple of days rooted and decided to go back to stock so....
I downloaded the factory image, ran the flash -all.bat and everything was good. Next I went back to my boot loader to re lock it, ran the command , selected yes.
After I hit yes to re lock the boot loader I got the following error. COULD NOT FIND A VALID OPERATING SYSTEM.
Any help would be greatly appreciated.

skullymullins said:
I rooted my Unlocked xl 2 using a method I found online. Used it a couple of days rooted and decided to go back to stock so....
I downloaded the factory image, ran the flash -all.bat and everything was good. Next I went back to my boot loader to re lock it, ran the command , selected yes.
After I hit yes to re lock the boot loader I got the following error. COULD NOT FIND A VALID OPERATING SYSTEM.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
1. fastboot flashing unlock
2. fastboot flashing unlock_critical
3. Reboot the phone if prompted
4. flash firmware using flash-all script again. Read the results and watch for errors that might explain the problem and which partition (a or b) it is flashing to.
5. fastboot --set-active=b (or a. Just set it to whichever partition the script was not flashing to.)
6. flash firmware with flash-all script again to flash the alternate partition

Ok Thanks Ill give that a try..

skullymullins said:
Ok Thanks Ill give that a try..
Click to expand...
Click to collapse
And don't relock until you are 100 percent certain it is ok. I suggest waiting until you get the next update to be sure. Actually I suggest not relocking it but if you insist then wait and make sure the next update goes ok.

TonikJDK said:
And don't relock until you are 100 percent certain it is ok. I suggest waiting until you get the next update to be sure. Actually I suggest not relocking it but if you insist then wait and make sure the next update goes ok.
Click to expand...
Click to collapse
When I tried the command . fastboot --set-active b i got the unknown command error

skullymullins said:
When I tried the command . fastboot --set-active b i got the unknown command error
Click to expand...
Click to collapse
You rooted your phone with a method you found online??? Hmmmm, that's curious. Hope that didn't do any internal damage. Anyways, when your in fastboot mode, and type in "fastboot devices" do you get your device ID number??

TheSt33v said:
1. fastboot flashing unlock
2. fastboot flashing unlock_critical
3. Reboot the phone if prompted
4. flash firmware using flash-all script again. Read the results and watch for errors that might explain the problem and which partition (a or b) it is flashing to.
5. fastboot --set-active b (or a. Just set it to whichever partition the script was not flashing to.)
6. flash firmware with flash-all script again to flash the alternate partition
Click to expand...
Click to collapse
I told one person that was having trouble also to instead of doing step 4 instead download Deuces bootloop kit and allow it to flash your phone for you because I noticed a few people were not flashing in fastboot properly the pixel is different from the prior phones they are used to there are many more Sig files that were not all getting flashed thoroughly causing issues. Deuces kit does it all perfect and it's pretty easy to set up and go

skullymullins said:
When I tried the command . fastboot --set-active b i got the unknown command error
Click to expand...
Click to collapse
Maybe that command works also. I use
Fastboot --set-active=b

skullymullins said:
When I tried the command . fastboot --set-active b i got the unknown command error
Click to expand...
Click to collapse
Sorry, the previous post is right. You need an = in there.

Think i just bricked my phone

I was following the steps on the rooting process with twrp and I got twrp to boot but i couldn't boot into the system and now it's just stuck in download mode is there any way to fix it

Djcall11 said:
I was following the steps on the rooting process with twrp and I got twrp to boot but i couldn't boot into the system and now it's just stuck in download mode is there any way to fix it
Click to expand...
Click to collapse
Download the factory images.
Run flasg_all.bat.
If you dont want your data partition to be formatted, then edit the .bat file and remove the line where it says "erase userdata". You can also remove tge last line that reads "fastboot reboot".
When rooting, i always boot into twrp using the image and flash both twrp zip and magisk zip in one go.

iliais347 said:
Download the factory images.
Run flasg_all.bat.
If you dont want your data partition to be formatted, then edit the .bat file and remove the line where it says "erase userdata". You can also remove tge last line that reads "fastboot reboot".
When rooting, i always boot into twrp using the image and flash both twrp zip and magisk zip in one go.
Click to expand...
Click to collapse
i have to edit the bat file and add -i 0x1532 to every command anyway for the command to work

so... the razer loading green effect is happening but it hasn't passed that it just keeps going
should I just put back the command to delete the user data

Have you unlocked the critical portion of the bootloader? (First thing I always ask)
If yes then yeah just wipe the whole thing.

Roxas598 said:
Have you unlocked the critical portion of the bootloader? (First thing I always ask)
If yes then yeah just wipe the whole thing.
Click to expand...
Click to collapse
welp the phone booted but it just stays on the loading screen and when I restart it just goes straight to download mode
I did unlock_critical and it just tells me that the device is already unlocked
I don't really know what else I can do from here

Of both bootloader portions are unlocked it should just be a case of running the flash all script from the factory images and you're good to go :S only other thing I can suggest to make sure there's nothing bad in there and in fastboot wiping user data again.

Roxas598 said:
Of both bootloader portions are unlocked it should just be a case of running the flash all script from the factory images and you're good to go :S only other thing I can suggest to make sure there's nothing bad in there and in fastboot wiping user data again.
Click to expand...
Click to collapse
I ran the script how it was and I just get stuck at the green effect loading I will try some other commands and I'm about to try the 7.1.1 mr3 rom to see if that work

so using the 7.1.1 mr3 worked i finally have my phone back thank guy for the help

Djcall11 said:
i have to edit the bat file and add -i 0x1532 to every command anyway for the command to work
Click to expand...
Click to collapse
Why is that? I didnt have to do that.
What does that command do?

Pixel 3xl Encryption issue.

So for starters. I was on the latest Android 11 rooted with magisk and LSposed along with GB.
I decided to sideload the Android 12 DP. So i floashed the stock boot image to both slots and then sideloaded 12DP. Everything went fine and i was testing A12. Tried to root A12 with magisk by the standard patch boot.img and fastboot flash to both slots. The phone hung on the bootscreen for like 10 minutes so i figured it best to flash back to A11. Back to BL mode and flashed theboot.img to both slots and then flash-all A11. Hit start when finished and it just flashed the white google screen for a few seconds then back to bootloader. Strange. Tried again, while changing active slots to ensure its flashing the system to both slots. Will not boot. Straight back to bootloader.
I can flash individual partions and i have no errors other than when wiping data it says it cant. Cant remeber exactly the error. But this is where it gets even more weird. I can flash android 9 and have no issues, I can take OTA updates with not issue. I can and am rooted and my phone is back to A11 via OTA. It will not boot if i flash or sideload any other version of Android other than A9. I believe this has something to do with encrytion. My phone was encrypted when i started this whole proccess and i believe thats why i get the error when trying to wipe data. In A9 recovery, when i factory data reset. it wipes with no errors. If i try to factory data reset in A10 or A11 Recovery i get the error E: can't send spi message: Try again .
So in closing, my phone is working and running fine but i can not flash-all any Android version other than A9 and have the phone boot.
So if anyone knows the proper steps to get this phone right, I would greatly appreciate it.
If not, i guess i will only be taking OTA's until i can figure it out.
Happy flashing!
Quick edit
Yes i pass safetynet and all banking apps work.
so is doing anything at all really necessary. I will leave that for the community to decide.
My opinion is, There is something wrong that needs fixing here. But its not crucial.

On A10-11 did you try "fastboot erase userdata" ?

wangdaning said:
On A10-11 did you try "fastboot erase userdata" ?
Click to expand...
Click to collapse
I did and it gives an error. Wish I wrote down the error like I did the other one. It's the same error at the end of flash-all when I don't remove -w

Try fastboot format userdata.

Just to add.... I can flash PixelDust (custom rom) and it boots and works great but can not flash-all or sideload android 10 or 11. Can only flash Android 9 and take OTA's up to Android 11.

Damn, should have caught this before. Your Platform Tools are out of date. Update adb and fastboot to latest.

wangdaning said:
Damn, should have caught this before. Your Platform Tools are out of date. Update adb and fastboot to latest.
Click to expand...
Click to collapse
I wish it were that simple. Unfortunately i actually updated it and also added the Android S Preview SDK and restarted my PC before even attempting this whole thing. And to make sure, just now checked for updates and its up to date.

What do you get with "fastboot --version" ?
I have see it where people have multiple versions on their computer.

wangdaning said:
What do you get with "fastboot --version" ?
I have see it where people have multiple versions on their computer.
Click to expand...
Click to collapse
You may be onto something here.....thoughtts?

And i think i have fixed that part on my PC. This is now what i get. I had that all-in-one tool installed so it made my system wide fastboot/adb look at its program folder instead of my default installation folder. Thats uninstalled and all folders and registry keys associated with it and my system is looking at my android sdk installation folder as it should.
This may very well have been the issue. I haven't tried to flash anything yet as i'm a bit gun shy after this fiasco lol
Maybe i will try flash-all with -w removed to see what happens.

Fastboot erase data?

jjgvv said:
Fastboot erase data?
Click to expand...
Click to collapse
That may likely work now as one of my issues was my fastboot was the wrong version because of the all-in-one tool i had installed. Haven't tried it yet and may not need to loose data if the flash-all command will work past android 9 which it should now thats its using the proper fastboot/adb version.

wangdaning said:
Try fastboot format userdata.
Click to expand...
Click to collapse

jjgvv said:
Fastboot erase data?
Click to expand...
Click to collapse
that finishes wothout any error....good start

is this how -w should work......sidenote, i can now flash-all android 11 and boot to system

Thank you @wangdaning for suggesting checking my fastboot version! That lead me to see i had 2 version and was defaulting to the wrong version. Removing that version and fixing my system path in windows variables fixed my issues. It was fastboot version the whole time. Again thank you @wangdaning!!
Edit to thank all who replied to this thread. I used everyones ideas

Glad you got it working.