Develop Bugs

[Guide] Re-lock and Un-root **3G & 4G** Xoom

##PLEASE NOTE##
These files are from Motorola's Development site and I take no liability with anything that happens with your device if something goes wrong.
DO NOT ATTEMPT TO FLASH THIS FILE ON ANYTHING BUT THE VERIZON WIRELESS MOTOROLA XOOM Z600 (3G MODEL) OR YOU WILL HAVE A SHINEY PAPER WEIGHT!!!!
Click to expand...
Click to collapse
You're going to need to have the Android SDK installed. You can download it here:
ANDROID SDK - DOWNLOAD
XOOM Firmware Downloads:
[3G|MZ600-HRI66]
[4G|MZ602-HLK75D]
Unzip the files in MZ600_HRI66.zip and move or copy them to the /platform-tools folder in your SDK folder.
Connect your Xoom to your computer. Type:
Code:
adb reboot bootloader
Wait for it to reboot into the bootloader.
Type the following commands, waiting for each to finish before continuing:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
You've now successfully flashed your Xoom back to stock. Now it's time to relock the device. Type
Code:
fastboot oem lock
wait for the menu
then press the volume-down button.
Then press the volume up button.
It'll take a minute or so, then reboot. You're now completely back to stock and ready for the update.

So if you are on Three . One you can use this to revert back to out of the box freshness?

Brenardo said:
So if you are on Three . One you can use this to revert back to out of the box freshness?
Click to expand...
Click to collapse
Yes. That is correct. This will return your XOOM to 100% stock.

word!
I have already been thru the LNX 0x0004 debacle and it was absolutely no fun whatsoever.

well I got a stuck at moto logo for 10 minutes
I am going to try to fastboot oem unlock, reflash images again and fastboot lock to see if I get out of moto logo

second install fix it

jlouang said:
second install fix it
Click to expand...
Click to collapse
So that means that you got it working, correct?
>.>

So the HRI66 is the latest version on the Motorola site? I really need to get a grasp of their version numbers.
EDIT:
Never mind looks like HRI66 is the latest version Thanks anyway.

i was thinking that with the change to the bootloader in the 3.1 update we couldn't use previous versions img's. But I am glad we can return to stock and get this 4G update!

I'm following all those steps directly. Once I type in adb reboot bootloader, it says starting Fastboot protocol support. Once I try to type any other command it says not recognized in adb. Any ideas?

Dead link...

dchurch85 said:
I'm following all those steps directly. Once I type in adb reboot bootloader, it says starting Fastboot protocol support. Once I try to type any other command it says not recognized in adb. Any ideas?
Click to expand...
Click to collapse
Did you extract all of the files in the ZIP into the 'tools' folder? The same one that adb is in.

Could someone help me,
After the rebooting device I got this massage :
Failed to boot LNX 0x0004
Starting RSD mode 2
Then stuck on Motorola logo. I can't enter the recovery mode.
What should I do ?
My Xoom is H.6.1-38-9 International version

CakraMas said:
Could someone help me,
After the rebooting device I got this massage :
Failed to boot LNX 0x0004
Starting RSD mode 2
Then stuck on Motorola logo. I can't enter the recovery mode.
What should I do ?
My Xoom is H.6.1-38-9 International version
Click to expand...
Click to collapse
This is what I was afraid of..... try searching the error you are getting. Not many options on how to fix.

i am curious about the LNX 0x0004 error. I know it comes from trying to relock with non-factory img's but what exactly does that mean? I am curious what actually causes the device to soft brick.

Finally I made it, .
I can enter to bootloader by fastboot method, flash the stock image, then relock my device.

Kinda having the same issue as dchurch... "adb reboot bootloader" reboots Xoom to the "M" logo with "Starting Fastboot protocol support," but I can't continue with nay further commands. My computer no longer recognizes the presence of my Xoom and my Xoom doesn't progress past this screen. I can boot it normally with no problem. I've extracted all of the necessary files into my platform tools folder with adb.. any input?

gatorhater73 said:
Kinda having the same issue as dchurch... "adb reboot bootloader" reboots Xoom to the "M" logo with "Starting Fastboot protocol support," but I can't continue with nay further commands. My computer no longer recognizes the presence of my Xoom and my Xoom doesn't progress past this screen. I can boot it normally with no problem. I've extracted all of the necessary files into my platform tools folder with adb.. any input?
Click to expand...
Click to collapse
You can try manually going into fastboot as well... there are two ways to do this:
No matter what, power off the Xoom. Then, 1) Power on the Xoom and as soon as you see it turn on (within a second or two of the power on), press the Volume Down button, which kicks it into Fastboot. 2) If you miss the 1st couple of seconds and press Volume Down after 3-5 seconds, it will say "Android Recovery." You can then press Volume Down until you get to Fastboot, then press Volume Up.
My guess is that you have a different issue, something to do with your Fastboot image. Not sure if booting the Xoom into the OS and connecting with USB Debugging on will work or not to flash the files, perhaps maybe just the boot.img?

I also believe that when the Xoom says "Starting Fastboot protocol support", it is in fastboot mode and you can send the fastboot commands to the Xoom. If your PC does not show the Xoom as a device in your PC's Device manager, then you will probably need to load new/correct drivers onto your PC.

Did you make sure that adb recognized your device? Adb devices in the camaned prompt
Sent from my Xoom using Tapatalk

[HOW-TO] Take LTE back to 100% Stock

I am not taking credit for this in anyway. But since i had to to it and had never done it before i had to look around on how to do it.
This is pulled from
http://www.droid-life.com/2011/12/1...the-bootloader-and-return-to-a-factory-state/
1. Download the Android 4.0.2 factory images to your PC. Download
2. Unzip the file and its contents into your SDK/Tools folder (wherever your adb.exe and fastboot.exe files
are).
*Make sure they are not in their own folder, but have all been extracted to Tools.
3. From within your Tools folder, open a command prompt (SHIFT + right click – “open command prompt here”):
4. Type the following commands, allowing each to finish before moving onto the next:
adb reboot bootloader
fastboot flash bootloader bootloader-toro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img
fastboot reboot-bootloader
fastboot -w update image-mysid-icl53f.zip
fastboot reboot-bootloader
fastboot oem lock
5. Reboot your phone by highlighting “Start” and pressing the lock switch.
6. It really is as simple as that. Your phone is now back to a 100% stock, unrooted and locked state.

thanks.. nice work

Eh... All I'd want is the back cover with just a Google logo, at this point in time I don't even care if there's bloat. Great guide though, might do it if I'm bored.

Would the files being extracted into tools have anything to do with the files used to root if i decided to re-root? Also my adb.exe and fastboot.exe are in the /platform-tools folder is that ok?

this should get sticky'd in case it becomes an "emergency" in the future and the thread's gotten burried.

how do i get the zip format
i can download the file but it doesnt come as a zip file? im on windows vista.

mikedfromaz said:
i can download the file but it doesnt come as a zip file? im on windows vista.
Click to expand...
Click to collapse
Popular tools like winrar and 7zip will still be able to extract it.

7zip
so i got 7zip to load but the second prompt in the sequence says error cant load bootloader-prime image??

i couldnt see the folder with all the files using winrar, i recommend using 7zip only

I tried these steps 3 times now. Everything seems to go just fine until I'm booted. Cant get a data signal on 3g/4g. Calls/text messages come through fine just missing something with the radios. Anyone else have this problem?

Same issue here. I've tried recovering to a different back up. Also updated radio to the newer leaked ones. Eventually reverted everything back to stock and I am STILL without any data connection.

Rageful said:
Same issue here. I've tried recovering to a different back up. Also updated radio to the newer leaked ones. Eventually reverted everything back to stock and I am STILL without any data connection.
Click to expand...
Click to collapse
I am in NYC and I do not have any data connection either....
I think (hope) it is a Verizon Network issue!!!

Verizon is having a nationwide outage, it affects everyone differently so no worries about loss of data access.
http://phandroid.com/2011/12/21/yes-verizons-data-network-is-experiencing-nationwide-outages-again-new-radios-for-galaxy-nexus-leak-in-the-meantime/

i did all of this this morning, but now everey time i do fastboot reboot-bootloader. i get a waiting for device. prior to this i was able to reboot the bootloader through adb just fine. both of my pc's have the same problem. Is there a problem with the bootloader on the image uploaded versus the one the phone came with? iknow i can boot to the bootloader with vol+ vol- and power. but its just better to doit trough adb. please advice.

Does this also restore the stock recovery? I don't see any fastboot commands to flash recovery. Or is that included in the stock img?

It's in the zip file when you run "fastboot -w update image-mysid-icl53f.zip"

Thank you so much for this! I was trying to root my phone and somehow managed to screw something up and wound up with an infinite boot loop. Followed these simple steps and was able to successfully get out of that mess.

So this puts the stock kernel back on there as well right?

GazaIan said:
Eh... All I'd want is the back cover with just a Google logo, at this point in time I don't even care if there's bloat. Great guide though, might do it if I'm bored.
Click to expand...
Click to collapse
Same here man. I'm coming from a Nexus One on at&t and I hate how Verizon has to put their branding on everything.

Does this still work if I have cwm and a different rom installed or are there more steps to do?
Sent from my Galaxy Nexus using xda premium

Anything special needed for flashing the Google factory restore images?

After initially trying the Android Revolution HD rom after rooting few days ago, I realized I wanted to go back to stock. I downloaded "https://dl.google.com/dl/android/aosp/mysid-icl53f-factory-65895fa8.tgz" off of http://groups.google.com/group/android-building/msg/2cd2b16ed56a7e84 for my Verizon LTE GN variant...
I extracted "image-mysid-icl53f.zip" and flashed it the usually way with CWM, ended up going into a boot loop. Luckily I had a Nandroid backup of my phone just after rooting so I was able to use that to restore back to stock...
Was there any reason that "image-mysid-icl53f.zip" didn't work? I read another unrelated (if I remember correctly) post on here about flashing the image with a modified script from Google, do I need to use the flash-all.sh or something when flashing this zip? Do I need the other files (bootloader-toro..., radio-cdma..., and radio-toro...)? Or did I just get unlucky and a reflash probably would have fixed it?
Thanks

You don't flash the zip with cwm. You need to do fastboot -w update blah.,ip command with it.
Search for the "convert yawuwhatever to yawublah" thread for the directions
Sent from my Galaxy Nexus

s1977 said:
Resetting the phone by taking out the battery shouldn't be a problem if you havent started flashing the new rom. I would try again after confirming that the fastboot and usb drivers can see the device before proceeding any further.
You can use fastboot devices to list attached devices. Only progress further once you can see your phone using the above command.
I did the same today a few hours ago and in my case, I started the phone in bootloader mode via Volume up + down + power button or via adb reboot bootloader. Then with fastboot, issue the fastboot oem unlock command to unlock the bootloader first. Once done, then you can flash the stock image (bootloader, radio and rom) with the following commands.
fastboot flash bootloader <bootloader image>
fastboot reboot-bootloader
fastboot flash radio <radio image>
fastboot reboot-bootloader
fastboot -w update <rom image>
Don't forget to lock the bootloader once done using fastboot oem lock
Just to clarify, depending on the version of the OS on your client PC/Mac/Linux, there are variants of fastboot. I use fastboot-mac from my mac.
Click to expand...
Click to collapse
Also try checking out this thread: How to? Change from yakjuxw to yakju

Galaxy nexus encrypted

Dear gurus of Android,
If possible I would like some help with my Galaxy Nexus since I think it is software bricked. When started it states the the phone is encrypted and wait for the key. I have read all I could get my hands on about this problem. No success so far, so I was hoping someone knowledgeable is willing to sacrifice some of his/her time to help me out.
Thanks in advance.

Hamal said:
Dear gurus of Android,
If possible I would like some help with my Galaxy Nexus since I think it is software bricked. When started it states the the phone is encrypted and wait for the key. I have read all I could get my hands on about this problem. No success so far, so I was hoping someone knowledgeable is willing to sacrifice some of his/her time to help me out.
Thanks in advance.
Click to expand...
Click to collapse
did you read this http://forum.xda-developers.com/showthread.php?t=1730463

Thanks for the quick response. Yes I did read the thread. It was one of the first things I tried. I lock/unlock the boot loader successfully. However when I start the phone in normal mode I get the same message, seems like nothing changed.

So no ideas ei. Seems Will be throwing away a perfectly functioning (hardware wise) Galaxy Nexus away. Shame since my other phone just died.
Anyway thanks for the effort.

Hamal said:
So no ideas ei. Seems Will be throwing away a perfectly functioning (hardware wise) Galaxy Nexus away. Shame since my other phone just died.
Anyway thanks for the effort.
Click to expand...
Click to collapse
Did you flashed factory image?
Sent from my Galaxy Nexus using xda app-developers app

razi914 said:
Did you flashed factory image?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I did, tried several, can't remember which Android version was that finally worked, however upon flashing after I started in normal mode the same **** - encrypted again like nothing happened.

What about CM or another rom?
Sent from my Galaxy Nexus using Tapatalk 4 Beta

sui785 said:
What about CM or another rom?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
Well I only tried stock Android since this is what I really wanted. But does it make sense to try CM if stock does not work. IS there a chance CM works. IF you say I should try than I should I guess. Never thought about it. Thanks for the advice.

Did you flash the factory images with fastboot?
Returning to stock using this method http://forum.xda-developers.com/showpost.php?p=25477039&postcount=1 may fix your problem.

jaizero said:
Did you flash the factory images with fastboot?
Returning to stock using this method http://forum.xda-developers.com/showpost.php?p=25477039&postcount=1 may fix your problem.
Click to expand...
Click to collapse
Well I might be confusing the terms, but I think I did use fastboot. I got the command lines from the XDA Forum actually and entered them manually through the sdk console the way I remember it. I think I also used some-kind of automated tool that basically does the same. The result being the same naturally. But should it even matter. I mean the problem is that whatever I do once I start the phone in normal operation mode I get the encrypted storage message. I have no idea how to get around this. Should I not be able to completely wipe it somehow so there is nothing when I start it ?

Hamal said:
Well I might be confusing the terms, but I think I did use fastboot. I got the command lines from the XDA Forum actually and entered them manually through the sdk console the way I remember it. I think I also used some-kind of automated tool that basically does the same. The result being the same naturally. But should it even matter. I mean the problem is that whatever I do once I start the phone in normal operation mode I get the encrypted storage message. I have no idea how to get around this. Should I not be able to completely wipe it somehow so there is nothing when I start it ?
Click to expand...
Click to collapse
Can you get into the bootloader by pressing the volume up/down keys and power button? Does it give you the encrypted message there?
Were these the commands you used?
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Optional (NOT optional for n00bs) -- Flash the bootloader: fastboot flash bootloader bootloader-maguro-primela03.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot (not required if you did not do step 5): fastboot reboot-bootloader
7) Optional (NOT optional for n00bs) -- Flash the radio: fastboot flash radio radio-maguro-i9250xxla02.img (or whatever the name is of the radio image that you downloaded).
8) Reboot (not required if you did not do step 7): fastboot reboot-bootloader
8a) Verizon and Sprint devices only -- flash the LTE radio: fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img (or whatever the name is of the radio image that you downloaded).
8b) Verizon and Sprint devices only -- reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 5 below for optional items.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Optional (NOT optional for n00bs) -- Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: fastboot erase cache
15) Reboot: fastboot reboot
16) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.

jaizero said:
Did you flash the factory images with fastboot?
Returning to stock using this method http://forum.xda-developers.com/showpost.php?p=25477039&postcount=1 may fix your problem.
Click to expand...
Click to collapse
Jaizero I just did what you suggested. Followed the link you provided and did everything according to he procedure. There were no errors. However when I restarted the phone with the last command line and it booted up in normal mode there was the same message.
The screen looks like the one on the link below (not actually my phones, have no other one to make a picture with).
http://bensullins.com/wp-content/uploads/2011/12/Nexus-S-Decrypt-On-Reboot-Android-4-600x800.png
Also I do not know if it is relevant or not but when it boots the initial screen with the Google logo in the very beginning there is a closed lock icon below the Google logo, probably because of the encryption ?
Thanks for the help in advance again guys/girls.

jaizero said:
Can you get into the bootloader by pressing the volume up/down keys and power button? Does it give you the encrypted message there?
Were these the commands you used?
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Optional (NOT optional for n00bs) -- Flash the bootloader: fastboot flash bootloader bootloader-maguro-primela03.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot (not required if you did not do step 5): fastboot reboot-bootloader
7) Optional (NOT optional for n00bs) -- Flash the radio: fastboot flash radio radio-maguro-i9250xxla02.img (or whatever the name is of the radio image that you downloaded).
8) Reboot (not required if you did not do step 7): fastboot reboot-bootloader
8a) Verizon and Sprint devices only -- flash the LTE radio: fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img (or whatever the name is of the radio image that you downloaded).
8b) Verizon and Sprint devices only -- reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 5 below for optional items.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Optional (NOT optional for n00bs) -- Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: fastboot erase cache
15) Reboot: fastboot reboot
16) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
Click to expand...
Click to collapse
Sorry saw your reply a bit too late. Yes these are the exact commands I used. Followed them exactly as stated every step worked out perfectly.
And no there is no encryption messaging while I am in the bootloader mode.

Hum... no replies. Seems like I am doing everything right yet results are bad. Means I am not doing everything right ofcourse. I am just not knowledgeable enough I guess to figure it out on my own.
Shame I really like the phone.

Hamal said:
Hum... no replies. Seems like I am doing everything right yet results are bad. Means I am not doing everything right ofcourse. I am just not knowledgeable enough I guess to figure it out on my own.
Shame I really like the phone.
Click to expand...
Click to collapse
Unlock the bootloader again, either through fastboot or omapflash. Did you try formatting partitions before flashing? Fastboot allows you to do that. Idk if you tried or have reserves towards ODIN, be extra careful both with omapflash and Odin. There's a link on unlocking the bootloader with omapflash on efrant's android 101 - links section, which is stickied on general.
a manta wrote this.

beekay201 said:
Unlock the bootloader again, either through fastboot or omapflash. Did you try formatting partitions before flashing? Fastboot allows you to do that. Idk if you tried or have reserves towards ODIN, be extra careful both with omapflash and Odin. There's a link on unlocking the bootloader with omapflash on efrant's android 101 - links section, which is stickied on general.
a manta wrote this.
Click to expand...
Click to collapse
Locking/Unlocking the bootloader does not work tried it a couple of times already. Will try the rest of what you suggested and let you know how it goes.
Thank you for the advice.

beekay201 said:
Unlock the bootloader again, either through fastboot or omapflash. Did you try formatting partitions before flashing? Fastboot allows you to do that. Idk if you tried or have reserves towards ODIN, be extra careful both with omapflash and Odin. There's a link on unlocking the bootloader with omapflash on efrant's android 101 - links section, which is stickied on general.
a manta wrote this.
Click to expand...
Click to collapse
I looked around the forums, could not find this Android 101 link tough. Any chance you might help me find it. I know I sound lazy but I really can't find the thread. Also I was thinking could an USB Jig solve this problem ?

If all else fails you could try this...
http://www.extremetech.com/computin...encryption-and-security-put-it-in-the-freezer
https://www1.informatik.uni-erlangen.de/frost

I don't see why fastboot erase userdata wouldn't work...

Sdobron said:
I don't see why fastboot erase userdata wouldn't work...
Click to expand...
Click to collapse
Well I did try it. What I did might be wrong, but here it is:
I followed the guide by jaizero for flashing via fastboot, but instead inserted " fastboot erase userdata" before the "fastboot flash userdata userdata.img" line. Than there was an error message on the phone, not on the pc command line screen, but it was so quick that I could not read it. However the process continued and was okay according to the command window and everyting went on as normal. Alas to no vail since the result was the same.
Any ideas ?
Ah I also noticed than in fastboot mode it said HW Version: 9. Any idea what it means ?
Thanks in advance for taking the time to bother with my bull

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.