Develop Bugs

[Q] help might have bricked my nexus

hey guys im a long time reader here. and i think i bricked my brand new verizon nexus. i just got done doing super boot to unlock it and also put clock mod on there. and now the phone will not boto past the word google. just stays on google for a min or so then reboots. im not sure what to do beause there is no sd card to mount (i dont know how to mount it its not working in recvovery mode.) can any one help me with a step by step to fix this. i cant fugure it out. i guess that was a dumb move on my part. =( please help!

I had this same issue, unlocked the bootloader, but then it would not boot past the white google. I tried so many things. Here is how I fixed mine.
First install 7zip or some sort of program that can deal with .tar and .tgz files assuming you don't already have it.
Download the stock image for your phone, I assume you are talking about the Galaxy Nexus LTE Verizon phone. Get that from here You need the mysid version, not the yakju. For a direct link to download the mysid version, click here
Extract that file to your desktop or wherever, you will have a file called "mysid-icl53f-factory-65895fa8.tar" then extract that so you have the following files visable:
bootloader-toro-primekk15.img
flash-all.sh
image-mysid-icl53f.zip
radio-cdma-toro-i515.ek05.img
radio-toro-i515.ek02.img
You can DELETE the radio-cdma-toro file, you don't need it for the LTE version (i hope, haha)
Put these files in your C:/android-sdk-windows/platform-tools folder. Do NOT further unzip the image.mysid zip file.
Put your phone into bootloader menu, plug in your USB cable to your computer, start your command prompt inside the platform-tools folder (in white space, shift+right click).
Type the following (taken from this thread and modified with correct file names)
Assuming you have windows computer
fastboot flash bootloader bootloader-toro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot -w update image-mysid-icl53f.zip
This took a few mins to install, And my phone then rebooted itself and worked! (I don't think I had to manually reboot it).
It took me 5 good hours to find all this info and finally get my phone working again, hope it works for you! I was in a panic, that's for sure!
Btw, the phone's bootloader is still unlocked, but I have not yet tried to gain root access.
Please let me know if this worked for you.

Ive done the same
Can you post what I would need to put in terminal for mac. Im kinda new to this

Hahahahahahahahahahahahahahaahahahahah not even a day

nononononono the same thing happened to me!!
Just do a battery pull and put it back in!

doublea500 said:
nononononono the same thing happened to me!!
Just do a battery pull and put it back in!
Click to expand...
Click to collapse
It does not work for some people. I let mine sit for a half hour and did at least 20 battery pulls. It never went past the white google screen
---------- Post added at 04:13 AM ---------- Previous post was at 04:11 AM ----------
cvv1984 said:
Can you post what I would need to put in terminal for mac. Im kinda new to this
Click to expand...
Click to collapse
I linked to the thread where I got the commands in my post.. anyways.. replace the file names with the ones as above
For OSX, replace "fastboot" with "./fastboot" (i would assume)

Well this did nothing for me. Got to the stage where it rebooted the phone, everything was looking good and reading as "okay" in command prompt. Then when it went to reboot it went right back to google screen. It shows the google logo for about five seconds, then it shuts off for a second, vibrates and logo comes back on. I am at a loss here and don't know what else I can do to fix this thing.
And yes, I just got it today

I followed the instructions to reimage back to stock and still have the same problem. As sublimejhn says it just keeps rebooting in that initial start up screen. Not a fun night.

SlopeSurfer said:
I followed the instructions to reimage back to stock and still have the same problem. As sublimejhn says it just keeps rebooting in that initial start up screen. Not a fun night.
Click to expand...
Click to collapse
I'll keep you posted if I make any progress if you'll do the same!! I have never had an issue rooting, installing roms or anything else on any other phone until now. This is not exactly the phone I want to have bricked, hopefully we can figure this out

Same Problem here, just hangs forever (15min+) at the Google splash screen.
I think I found the problem with mine. I cant mount (or do anything) with the /data part of the phone.
I think its corrupted or something. I realized this when I was trying to do a nandroid restore/backup and could never mount or format the /data
--------edit----------
What Easyski posted work like a charm for me. Thx dude

fly_guy said:
Same Problem here, just hangs for ever (15min+) at the Google splash screen.
I think I found the problem with mine. I can mount (or do anything) with the /data part of the phone.
I think its corrupted or something. I realized this when I was trying to do a nandroid restore/back and could never mount or format the /data
--------edit----------
What Easyski posted work like a charm for me. Thx dude
Click to expand...
Click to collapse
Well that's cool. I have tried it 3 times now and it's a no go for me, but good to hear someone got theirs working again. Now if only the rest of us could get out of this!! At this point I don't even care about root, I just want my phone back

before I tried his steps I flash the stock recovery, stock boot.img, and lock it back.
so maybe try doing that, then use the steps above. I was about to give up myself. Was doing one last scroll of the forums when I saw this thread

Ok, got mine working now. Not sure why this helped, but here's what I did, I typed everything exactly as follows:
fastboot-windows flash bootloader bootloader-toro-primekk15.img
fastboot-windows reboot-bootloader
fastboot-windows flash radio radio-toro-i515.ek02.img
fastboot-windows reboot-bootloader
fastboot-windows -w update image-mysid-icl53f.zip
I don't know if it is the fact that I wasn't using fastboot-windows (can't see why that would matter, since both fastboot and fastboot-windows appear to be the same file), or the addition of that stupid '-w' before the update (got this from another thread), or if the 5th time was just a charm!! But either way, hopefully someone else can get up and running now too

yea 'fastboot' wouldnt work for me, had to use 'fastboot-windows.exe'

I guess the 5th time is a charm. It's working. I didn't think it was going to at first. It did get in the boot animation but then restarted over again. After looping in the boot animation for awhile if finally finished and started working. The only thing I did different on the 5th try was put in the "-w" on the image update.
Persistence counts. Thanks for all the support.

SlopeSurfer said:
I guess the 5th time is a charm. It's working. I didn't think it was going to at first. It did get in the boot animation but then restarted over again. After looping in the boot animation for awhile if finally finished and started working. The only thing I did different on the 5th try was put in the "-w" on the image update.
Persistence counts. Thanks for all the support.
Click to expand...
Click to collapse
that -w makes all the difference.

easyski said:
I had this same issue, unlocked the bootloader, but then it would not boot past the white google. I tried so many things. Here is how I fixed mine.
First install 7zip or some sort of program that can deal with .tar and .tgz files assuming you don't already have it.
Download the stock image for your phone, I assume you are talking about the Galaxy Nexus LTE Verizon phone. Get that from here You need the mysid version, not the yakju. For a direct link to download the mysid version, click here
Extract that file to your desktop or wherever, you will have a file called "mysid-icl53f-factory-65895fa8.tar" then extract that so you have the following files visable:
bootloader-toro-primekk15.img
flash-all.sh
image-mysid-icl53f.zip
radio-cdma-toro-i515.ek05.img
radio-toro-i515.ek02.img
You can DELETE the radio-cdma-toro file, you don't need it for the LTE version (i hope, haha)
Put these files in your C:/android-sdk-windows/platform-tools folder. Do NOT further unzip the image.mysid zip file.
Put your phone into bootloader menu, plug in your USB cable to your computer, start your command prompt inside the platform-tools folder (in white space, shift+right click).
Type the following (taken from this thread and modified with correct file names)
Assuming you have windows computer
fastboot flash bootloader bootloader-toro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot update image-mysid-icl53f.zip
This took a few mins to install, And my phone then rebooted itself and worked! (I don't think I had to manually reboot it).
It took me 5 good hours to find all this info and finally get my phone working again, hope it works for you! I was in a panic, that's for sure!
Btw, the phone's bootloader is still unlocked, but I have not yet tried to gain root access.
Please let me know if this worked for you.
Click to expand...
Click to collapse
Hi Guys,
I'm afraid I have the same problem. I was downloading on my Galay Nexus.(GSM version) since I'm in the Netherlands and suddenly the phone rebooted on it's own. Now the phone keeps on rebooting on the splash screen. The bootloader is unlocked and the phone has been rooted. I would like to follow the instructions above only I need the GSM version of the rom of the galaxy nexus. Does anybody have a link to that
Any help would be very much appreciated
Thanks a lot
Edit:addtional information When I try to restore a backup an error is given when trying to restore perhaps something is wrong with the memory?

Looking at all the problems people seem to have gotten from Superboot, I'm glad I rooted mine manually.
Educational with the added bonus of knowing that you cannot **** up your phone like this in the process.
Also: Seriously lol at the phone is available in the US for -1- day and XDA is already filled with "OMG i bricked/ruined my phone"-threads.
You guys are teh best!

josteink said:
Looking at all the problems people seem to have gotten from Superboot, I'm glad I rooted mine manually.
Educational with the added bonus of knowing that you cannot **** up your phone like this in the process.
Also: Seriously lol at the phone is available in the US for -1- day and XDA is already filled with "OMG i bricked/ruined my phone"-threads.
You guys are teh best!
Click to expand...
Click to collapse
The same thing happened on the Galaxy S2 thread when that first got released loads of people bricked their phones by messing about.
I guess some peeps have money to burn!

odd error on update step
I did get an odd error on the update step...
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
but it still installed those in the update sequence...
it seemed to work, but should i be worried?

HELP!!

Guys let me put this disclaimer out there, this is not my first Android device and neither my first time tinkering or modding it. I've rooted three android devices prior to this.
I upgraded from a Droid Incredible this weekend to Galaxy Nexus on Verizon and finally thought of rooting and flashing a kernel to the phone today since battery life is horrendous. I download the Rootkit that is on the forums here and went through the procedure as laid out in the thread. After unlocking the bootloader and flashing root, the phone hangs on google boot screen. I am fearing that i have bricked the phone. Does anybody else have suggestions on what should i do here? I've never had a problem with rooting a device before.

This is why I always do mines manually. It's better to do it that way and not take the faster route because you get a idea what's going on.
Is your bootloader unlocked? did that successfully work? When you turn your phone on on the bottom center.. is there a lock there?

It's not bricked. Put the phone in fastboot and flash the galaxy nexus image files to it. No big deal.

mysterioustko said:
It's not bricked. Put the phone in fastboot and flash the galaxy nexus image files to it. No big deal.
Click to expand...
Click to collapse
Exactly what I was going to say. +1

fastboot oem lock
fastboot oem unlock
Bricking this phone is nearly impossible, we have fastboot, and even Odin for when things really go to hell.

Restore to stock and start again! You should always keep these images around anyway in case you get stuck at any stage.
1) Grab the latest image for your type of phone from google:
http://code.google.com/android/nexus/images.html
2) Unzip the file and its contents into your SDK/Tools folder (wherever your adb.exe and fastboot.exe files are).
3) From within your Tools folder, open a command prompt (SHIFT + right click – “open command prompt here”) / OR open a command prompt and CD to the folder.
4) Type the following commands, allowing each to finish before moving onto the next:
adb reboot bootloader
fastboot flash bootloader bootloader-<varies>.img
fastboot reboot-bootloader
fastboot flash radio radio-<varies>.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-<varies>.img
fastboot reboot-bootloader
fastboot -w update image-<varies>.zip
fastboot reboot-bootloader
Remember the exact image name will vary depending on which version you use. Also if you have the GSM version you won't have radio-cdma etc.
There's other guide that are specific to GSM or CDMA/LTE version if you need exact filenames.

You guys are awesome! I was able to get it back to Stock Google. Thanks a lot fellas .

what would the command prompts be for a mac user?

silverado9502 said:
what would the command prompts be for a mac user?
Click to expand...
Click to collapse
where ever you see:
fastboot ...
do
./fastboot ...

ok so im on a mac and really not too familiar with the locations for things so im tryng to figure out what to, i can get to fastboot and recovery, somehow i lost my backup and the rom that i have isnt installing, i already wiped all data and now it only reboots to the google splash screen with the lock pad unlocked. what do i need to do exactly i may need a walk through unless what is on previous posts is what i need to do?

[2013] Possibly hard bricked on factory image update. Honestly not sure.

Earlier today I used the Nexus Root Tool Kit to flash stock and flash the factory image for 5.0.
At erasing User Data it seemed to get stuck, it was there for over 40 minutes. While looking at the device I accidentally knocked the USB cable out and it said failed. Upon rebooting the device I got the Google logo and the bootloader unlocked icon and then the bugdroid with the gear like it's doing an update (THIS: http://scottiestech.info/wp-content/uploads/2013/03/Android_Update_Screen.jpg[1] ). It stayed like this for another 40 minutes. I forced it to shut down and tried to get into the bootloader but holding down vol up+vol down+power for almost 60 seconds did nothing.
I then booted it up normally again to the gear bugdroid and left it like that before I went out for almost 6 hours. When coming home it was the same and still stuck on that.
I rebooted again and held down to boot into the bootloader but again it did not boot in over 60 seconds.
So am I hard bricked and should toss this out with the trash tonight or can this be restored somehow.

Are you able to connect to your device using fastboot?
Assuming you have fastboot installed and the drivers installed, open a command prompt and from the directory where your SDK files are (unless you added the directory to your system PATH), type "fastboot devices" without the quotes. What do you get back? If you get back a serial#, you should be able to flash the individual files manually
(Download the factory image from google's site, and extract the files into a folder, and run the flash-all.bat This will wipe all your data out, and assumes your bootloader is already unlocked)
Edit: follow the instructions here - http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
These are for Nexus 5, but the same steps apply for Nexus 7 as well. Just make sure you download the right factory image for your Nexus 7. Use Method 1

jj14 said:
Are you able to connect to your device using fastboot?
Assuming you have fastboot installed and the drivers installed, open a command prompt and from the directory where your SDK files are (unless you added the directory to your system PATH), type "fastboot devices" without the quotes. What do you get back? If you get back a serial#, you should be able to flash the individual files manually
(Download the factory image from google's site, and extract the files into a folder, and run the flash-all.bat This will wipe all your data out, and assumes your bootloader is already unlocked)
Edit: follow the instructions here - http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
These are for Nexus 5, but the same steps apply for Nexus 7 as well. Just make sure you download the right factory image for your Nexus 7. Use Method 1
Click to expand...
Click to collapse
Well I can get it into fastboot but I'm getting errors when it tries to flash the bootloader or boot.

what's the error message?

jj14 said:
what's the error message?
Click to expand...
Click to collapse
originally there was none, it just said failed and completed. now i'm getting invalid arguments.
I'm still in fastboot mode but literally nothing will flash.
*edit* just tried to use tookit again and
writing 'bootloader'
FAILED <remote: flash write failure>
finished.
Seeing a couple people mention that they fixed errors like this just from using a different usb port or cable. going to try that.

Why didn't you use adb to flash factory image from the get-go? It's the safest way to flash. I would be so mad on your place if device would render useless. But that might be just me since i'm poor. I really hope you manage to fix it.

neo5468 said:
Why didn't you use adb to flash factory image from the get-go? It's the safest way to flash. I would be so mad on your place if device would render useless. But that might be just me since i'm poor. I really hope you manage to fix it.
Click to expand...
Click to collapse
I knew of that way but the Nexus Tool Kit has always been perfect and I've never had any issues with it so I figured I'd just do it that way to make it easier and well, it didn't happen.
I'm hoping because I can get into fastboot that it's not actually bricked yet but if so then oh well i guess.

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.

Stuck on loading G screen

I see a lot of people have this same problem for different reasons and the solutions are seemingly all over the place if any
My phone recently lagged out and i had to restart it, which is when my issue happened.
I know my space was running low so im assuming that may have something to do with why it happened.
my Pixel 2xl is stuck at the G loading screen and my goal is to recover the data over all else. I am new to this and have absolutely no idea what im doing. So ive googled as much as i could but some things arent making sense, id appreciate some help or a step by step
some info
my phone is 100% stock aside from my nova home launcher.
I dont not have custom bootloaders
my phone has a password, idk if that matters but just in case
my phone is not jailbroken (i think is the term?)
I did have USB debugging set already, and I BELIEVE i had developer mode enabled
thats about it for the phone info
In the bootloader main scree, it stats im in fastboot mode, secure boot yes, device state, locked
What ive tried
-I have tried the manual OTA install via the adb stuff
i got success 0 but upon restart, nothing changed and i was still stuck
-i tried the flash steps
but i get "flashing is not allowed in lock state pixel 2"
ive tried to use a pull command via adb, but it said some strings were incorrect? I just copy pasted a command from a similar post, it may not have been catered to my situation fully so i dont know about that
Is there any steps i can take to simply either recover my photos before i factory reset, or reset without wiping, or even maybe delete some files to make space via something somehow?? I just need my data, the phone itself i can replace

Most of your photos should be automatically backed up in Google photos already. I'd just factory reset and hope for the best.
Sometimes booting to bootloader then boot system does the trick, or long pressing the power button.

Download the full factory image
Unzip the image
Open the flash-all.bat in editor and delete "-w" and close the editor (save)
Add fastboot.exe (you have to download adb-files) to the image folder
Boot into bootloader
Run flash-all.bat

Edmontonchef said:
Most of your photos should be automatically backed up in Google photos already. I'd just factory reset and hope for the best.
Sometimes booting to bootloader then boot system does the trick, or long pressing the power button.
Click to expand...
Click to collapse
i turned that off initially but checked the site just in case, theyre not backed up ):

Sui77 said:
Download the full factory image
Unzip the image
Open the flash-all.bat in editor and delete "-w" and close the editor (save)
Add fastboot.exe (you have to download adb-files) to the image folder
Boot into bootloader
Run flash-all.bat
Click to expand...
Click to collapse
when following your directions exactly, i get an error for not having the rest of the adb files in the image folder.
I downloaded the full factory image, (NOT the Full OTA), extracted it, edited the .bat file so it wouldnt wipe, and placed the fastboot .exe (from the platform tools folder) inside of the folder, booted into bootloader and ran the file by double clicking on it.
I then tried putting the factory imagine files inside of the platform tools folder and running the flash that way just in case, and instead get "waiting for any device"

buninthesun said:
when following your directions exactly, i get an error for not having the rest of the adb files in the image folder.
I downloaded the full factory image, (NOT the Full OTA), extracted it, edited the .bat file so it wouldnt wipe, and placed the fastboot .exe (from the platform tools folder) inside of the folder, booted into bootloader and ran the file by double clicking on it.
I then tried putting the factory imagine files inside of the platform tools folder and running the flash that way just in case, and instead get "waiting for any device"
Click to expand...
Click to collapse
You can't flash factory images with fastboot unless your bootloader is unlocked and you establish an adb connection but you can sideload the ota without wiping userdata

Edmontonchef said:
You can't flash factory images with fastboot unless your bootloader is unlocked and you establish an adb connection but you can sideload the ota without wiping userdata
Click to expand...
Click to collapse
the OTA sideload has a success of 0 but nothing happens beyond that, the phone still gets stuck at loading
does 0 mean it should have worked? Any idea why nothing changed?

Sorry for the problems.
My bootloader is unlocked, so that might be the reason.

buninthesun said:
my Pixel 2xl is stuck at the G loading screen and my goal is to recover the data over all else.
Click to expand...
Click to collapse
Try the following.
1. Download the latest ADB and Fastboot binaries from the links at this page.
2. Extract the zip file you just downloaded to a directory on the root of a drive. For example, I have my copies of ADB and Fastboot stored at a directory I created, D:\ADB.
3. Open a command prompt, not a powershell window, and navigate to that directory using DOS commands.
4. Enter the bootloader on your device and connect your device to your PC.
5. Type "fastboot devices" to make sure the P2XL appears.
6. If it does, type the following commands:
fastboot getvar all
fastboot --set-active=a/b
fastboot reboot
The idea here is to get you into the device by using the second partition. To do this, you need to find out which slot you are currently using, A or B, and set the active slot to the OTHER partition. "fastboot getvar all" will tell you which slot is currently active. "fastboot --set-active=a/b" will change the active partition to the currently unused one. For example, if the active slot is currently a, you would issue the command "fastboot --set-active=b" to switch to the other partition, and then reboot.

Moral of the story here is unlock your bootloader and leave it that way.
So much easier getting out of trouble