Develop Bugs

[Q] How to restore back to factory settings after using towel root

I have rooted my device using towel root which doesn't unlock the boot loader. I then used the twrp manager to install custom recovery. I am wondering how to restore everything back to factory as all the tutorials I have seen so far require an unlocked boot loader. Any help will be appreciated, thank you.

Flash a stock r for your phone
swagg blasted from TMO LG G3

jailbreakkid23 said:
Flash a stock r for your phone
swagg blasted from TMO LG G3
Click to expand...
Click to collapse
If I download a stock image from google and flash it from my nexus 7 using twrp will everything be restored to factory settings?

If the boot loader is locked does that mean I can just do a normal factory reset on the device and it will remove the recovery and root?

fastboot
Jordydaman said:
If the boot loader is locked does that mean I can just do a normal factory reset on the device and it will remove the recovery and root?
Click to expand...
Click to collapse
you have to install stock ROM by adb mode using fastboot command
you can't flash stock ROM via custom recovery.

@SidDev said:
you have to install stock ROM by adb mode using fastboot command
you can't flash stock ROM via custom recovery.
Click to expand...
Click to collapse
Would you mind finding a link for me ? I have never encountered this before as I have always unlocked the bootloader to root but this time I used towel root which was different as explained above.

Doesn't the boot loader have to be unlocked to flash a ROM via adb?

try this and press thanks
Jordydaman said:
Doesn't the boot loader have to be unlocked to flash a ROM via adb?
Click to expand...
Click to collapse
nope,
Step 1: Download the ADB/Fastboot files and the
USB drivers for Windows based PC first. The the
latest factory image for your Nexus device can be
downloaded directly from Google’s website .
ADB/Fastboot – Mac , Windows
USB drivers for Windows
Extract the contents of the ADB/Fastboot ZIP file
inside a new folder called ‘google’ on your desktop.
Extract and transfer the contents of the factory
image inside this folder as well. The list of files will
include a ZIP file containing the codename of your
Android device, two files with “flash-all” names, and
a bootloader image file. All the extracted contents of
the factory image should be inside the same folder
as the ADB and Fastboot file, otherwise you will get
a file not found error.
Make sure to install the ADB drivers as well if you
are running a Windows based PC.
Step 2: Now, reboot your Nexus device in bootloader
mode. This is usually done by switching off the
device, and pressing the Volume down + Volume Up
+ Power button simultaneously. If that does not
work, try the Volume down + Power button
combination.
After the device has booted into bootloader mode,
connect it to your PC.
Step 3: Open a new Terminal or Command Prompt
window, and navigate to the ‘google’ folder that you
created in Step 1. Before we start flashing the
factory image, we need to make sure that your
Nexus device is being detected by the PC.
fastboot devices
If you are using a Mac, then you need to prefix a “./”
before every Fastboot command. So, the above
command will look something like this on a Mac -:
./fastboot devices
The above command should confirm if your device is
indeed being detected by your PC or not. If it is,
then proceed to the steps below. If not, repeat the
steps above again. Make sure that you have properly
installed the drivers and are inside the correct
folder.
If you are running Windows, copy-paste the following
command in the command prompt window -:
flash-all.bat
On a Mac, copy-paste the following command -:
./flash-all.sh
The script will then automatically flash the full
factory image on your Nexus device. Once the
factory image has been flashed, your device will
automatically reboot. Keep in mind that the first boot
might take some time so please be patient.
If the flash-all.sh script gives you a fastboot not
found error on your Mac, open up the file in Text Edit
and add a “./” before every fastboot command.
The flash-all script included in the factory image
might not work for all. It has always been pretty
unreliable and has only worked once for me in the
last 2 years. If you are in the same boat as me, you
will have to flash each partition manually on your
device. This is slightly cumbersome though.
The command to manually flash a partition via
fastboot is “fastboot flash partition filename.img”. In
the factory image that you extracted in Step 1, you
will notice there is another ZIP file. Extract the
contents of that ZIP file inside the ‘google’ folder.
Now, its time to manually flash the partitions to your
Nexus device. We will first begin with the bootloader.
fastboot flash bootloader filename.img
Then, we will flash all other partitions. They don’t
necessarily need to be in the same order as I have
listed them below. The names of the image files in
the factory image will clearly indicate the partition
they are intended for as well.
fastboot flash boot filename.img
fastboot flash radio filename.img
fastboot flash recovery filename.img
fastboot flash userdata filename.img
fastboot flash system filename.img

Thank you very much I will try this today.

I couldn't flash all and when I flashed the bootloader it came up with failed bootloader is locked?

Enter this command to unlock the bootloader:
fastboot oem unlock
After unlocking, you can run flash-all.bat (or run manual fastboot commands to flash).

[Q] How to update to 5.0.1 from a rooted 5.0 ?

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:

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.

Possibly Bricked Pixel XL

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.

Need help, locked up phone

Long story short, I bought my awesome Pixel 2 XL back in December, right away I unlocked the bootloader, installed TWRP Recovery and rooted it. Since then I have done nothing to the phone , besides app updates, but never updated top the latest security patches pr anything. Partly because being rooted can't take OTA updates, and didn't want to wipe anything flashing new updates.
Tonight, I wanted to get on the latest, I was currently on 3.2.1.0, so I downloaded the 3.2..1.2 zip, rebooted into Recovery, and flashed the zip, and rebooted into Recovery again, all good, on the latest current TWRP version.
I press reboot system, but it keeps going back into Recovery, every time, always reboots back into Recovery for some strange reason ? Doesn't load the system. So I select the other partition A, I was on B, I put it in A, select reboot system, and it just hangs on the white Goggle screen FOREVER. I then get back into Recovery, now I can't even get into Recovery, the swipe right feature not working, acting like it's not registering my input, I can't swipe the arrow to move it. Now it's just stuck on the opening page in Recovery.
Now what ?

Zorachus said:
Long story short, I bought my awesome Pixel 2 XL back in December, right away I unlocked the bootloader, installed TWRP Recovery and rooted it. Since then I have done nothing to the phone , besides app updates, but never updated top the latest security patches pr anything. Partly because being rooted can't take OTA updates, and didn't want to wipe anything flashing new updates.
Tonight, I wanted to get on the latest, I was currently on 3.2.1.0, so I downloaded the 3.2..1.2 zip, rebooted into Recovery, and flashed the zip, and rebooted into Recovery again, all good, on the latest current TWRP version.
I press reboot system, but it keeps going back into Recovery, every time, always reboots back into Recovery for some strange reason ? Doesn't load the system. So I select the other partition A, I was on B, I put it in A, select reboot system, and it just hangs on the white Goggle screen FOREVER. I then get back into Recovery, now I can't even get into Recovery, the swipe right feature not working, acting like it's not registering my input, I can't swipe the arrow to move it. Now it's just stuck on the opening page in Recovery.
Now what ?
Click to expand...
Click to collapse
Fastboot the boot.img from whatever build your on now and let it boot up. That will remove twrp, then you can go back and fastboot twrp again.

[delete

Badger50 said:
Fastboot the boot.img from whatever build your on now and let it boot up. That will remove twrp, then you can go back and fastboot twrp again.
Click to expand...
Click to collapse
Where do I get the December boot.img ?

Zorachus said:
Where do I get the December boot.img ?
Click to expand...
Click to collapse
Go here....https://developers.google.com/android/images
Download the December factory image, extract it, then extract the other zip you'll find, and in there you'll find the boot.img. Then place that in your platform-tools folder and run...fastboot boot boot.img
Then type fastboot reboot, and let the phone boot up. Then go back and fastboot the twrp.img
Once in twrp, flash the twrp installer zip, then custom kernel if you want, and then magisk for root if you want. Question, why are you still on the December build???

I think if you just flash magisk it will boot again. If you were rooted. Someone posted on the twrp thread. To get touch back on twrp just have to adb reboot recovery. Might worth a try.
Sent from my Pixel 2 XL using Tapatalk

Badger50 said:
Go here....https://developers.google.com/android/images
Download the December factory image, extract it, then extract the other zip you'll find, and in there you'll find the boot.img. Then place that in your platform-tools folder and run...fastboot boot boot.img
Then type fastboot reboot, and let the phone boot up. Then go back and fastboot the twrp.img
Once in twrp, flash the twrp installer zip, then custom kernel if you want, and then magisk for root if you want. Question, why are you still on the December build???
Click to expand...
Click to collapse
Ok I am downloading the 1.6GB December file. I will then extract that, and only need to grab the boot.img file from there ? What do you mean when you say "then extract the other zip you'll find" ?
And then connect my phone to my PC, and open Command Prompt, and run these lines. I need to be in fastboot mode I assume ?
"

Zorachus said:
Ok I am downloading the 1.6GB December file. I will then extract that, and only need to grab the boot.img file from there ? What do you mean when you say "then extract the other zip you'll find" ?
And then connect my phone to my PC, and open Command Prompt, and run these lines. I need to be in fastboot mode I assume ?
"
Click to expand...
Click to collapse
There's another large zip that you'll find after you extract the factory image. It is in that zip that you'll find the boot.img. And yes, you'll need to be in fastboot mode to install the boot.img :good:

Badger50 said:
There's another large zip that you'll find after you extract the factory image. It is in that zip that you'll find the boot.img. And yes, you'll need to be in fastboot mode to install the boot.img :good:
Click to expand...
Click to collapse
Ok so I extracted that 1.6gb December file. Inside the file I see the large 1.5GB file, I open that and see the boot.img, only like 40mb. or do I need to extract this 1.5GB file too ?

Zorachus said:
Ok so I extracted that 1.6gb December file. Inside the file I see the large 1.5GB file, I open that and see the boot.img, only like 40mb. or do I need to extract this 1.5GB file too ?
Click to expand...
Click to collapse
Yes, extract that file, then you can move the boot.img out of it :good:

Badger50 said:
Yes, extract that file, then you can move the boot.img out of it :good:
Click to expand...
Click to collapse
In Command Prompt I am typing " fastboot boot boot.img " and it says cannot load 'boot.img' : No such file or directory

Zorachus said:
In Command Prompt I am typing " fastboot boot boot.img " and it says cannot load 'boot.img' : No such file or directory
Click to expand...
Click to collapse
Ah crud, I messed up. How bout..fastboot flash boot boot.img
Does that work? And, is that boot.img in the platform-tools folder?

Badger50 said:
Ah crud, I messed up. How bout..fastboot flash boot boot.img
Does that work? And, is that boot.img in the platform-tools folder?
Click to expand...
Click to collapse
I moved that boot.img file into the Downloads section of my PC, and in Command Prompt typed cd Downloads, then once there the "fastboot boot boot.img" line, which that worked, and finished in 1.023s, and the phone rebooted, but now I'm back on that white G screen, and still just sitting there.
I have the "platform-tools" folder inside the Downloads folder, but now sure how to direct the Command Prompt to go there ?
EDIT: Silly me, easy to get Command Prompt to the platform-tools, just typed ' cd platform-tools ' and it's there. LOL. So I did that, and then 'fastboot boot boot.img' and the phone rebooted, but it's still hanging in that white G screen

Badger50 said:
Ah crud, I messed up. How bout..fastboot flash boot boot.img
Does that work? And, is that boot.img in the platform-tools folder?
Click to expand...
Click to collapse
Make sure your boot.img is in Android Tools folder along with fastboot.exe.
Then with phone in bootloader, type:
fastboot flash boot boot.img
---------- Post added at 07:31 PM ---------- Previous post was at 07:26 PM ----------
Zorachus said:
I moved that boot.img file into the Downloads section of my PC, and in Command Prompt typed cd Downloads, then once there the "fastboot boot boot.img" line, which that worked, and finished in 1.023s, and the phone rebooted, but now I'm back on that white G screen, and still just sitting there.
I have the "platform-tools" folder inside the Downloads folder, but now sure how to direct the Command Prompt to go there ?
EDIT: Silly me, easy to get Command Prompt to the platform-tools, just typed ' cd platform-tools ' and it's there. LOL. So I did that, and then 'fastboot boot boot.img' and the phone rebooted, but it's still hanging in that white G screen
Click to expand...
Click to collapse
This should cure your sticking at white screen: (wipes phone)
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

Zorachus said:
I moved that boot.img file into the Downloads section of my PC, and in Command Prompt typed cd Downloads, then once there the "fastboot boot boot.img" line, which that worked, and finished in 1.023s, and the phone rebooted, but now I'm back on that white G screen, and still just sitting there.
I have the "platform-tools" folder inside the Downloads folder, but now sure how to direct the Command Prompt to go there ?
Click to expand...
Click to collapse
What happens if you do a hard restart using the power button?
Your platform-tools folder is where? I just leave mine in the SDK folder, then move my stuff from my files from the download folder. But hey, if it works, that's cool :good:

michaelbsheldon said:
Make sure your boot.img is in Android Tools folder along with fastboot.exe.
Then with phone in bootloader, type:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Ok the boot.img is in there, in my CD:\Downloads section in the folder named "platform-tools" , in that folder is all the fastboot.exe, and boot.img, adb stuff, etc...
I go back to Command Prompt typed in 'fastboot flash boot boot.img; phone rebooted, and still hanging in the white G screen

Ran that [TOOL] Deuces thing, unlocked bootloader and erased data, and other stuff, it does all this in fastboot mode it seems.
So after it's done, I am in fastboot mode still, I press the power button on the Green Start arrow. It boots up, then a black screen and bright circle animation and underneath says erasing, it reboots and goes to the white G screen, then reboots again, and I am in some weird screen now ?
Android Recovery, but this sure the hell isn't TWRP Recovery. It's some strange super tiny lettering hard to barely read, gives me two options;
-Try again
-Factory data reset
Above that it says "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset, and erase all your data stored on this device"

Zorachus said:
Ran that [TOOL] Deuces thing, unlocked bootloader and erased data, and other stuff, it does all this in fastboot mode it seems.
So after it's done, I am in fastboot mode still, I press the power button on the Green Start arrow. It boots up, then a black screen and bright circle animation and underneath says erasing, it reboots and goes to the white G screen, then reboots again, and I am in some weird screen now ?
Android Recovery, but this sure the hell isn't TWRP Recovery. It's some strange super tiny lettering hard to barely read, gives me two options;
-Try again
-Factory data reset
Above that it says "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset, and erase all your data stored on this device"
Click to expand...
Click to collapse
I don't mess with tool kits, so may want to post it in that thread. That's the stock android recovery. Your best bet is to factory reset. Then hopefully it'll boot up.

Looks like I'm ****ed. I pressed Factory Data Reset, it rebooted, went to the white G screen, then rebooted back again to that stock Android recovery, with the same options.

Zorachus said:
Looks like I'm ****ed. I pressed Factory Data Reset, it rebooted, went to the white G screen, then rebooted back again to that stock Android recovery, with the same options.
Click to expand...
Click to collapse
That sounds like outdated Android Tools.
Have you tried to flash the March image from Google yet?
If not, download newest Tools, https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Then download March image and follow these instructions: https://developers.google.com/android/images#taimen.