Develop Bugs

[Q] Hard Bricked Nexus 7 (2013)

I am an idiot.
Today I decided I would play around with some different ROMs. All was going well. I was becoming adept at flashing, booting, restoring, repeat.
All the ROMs I had tried up to this point were 4.3. I decided to go with something different. I installed OmniRom, which went okay, other than the fact it wouldn't recognize WiFi signals.
As any modern-day geek would do, I took to Google. I found a pretty promising solution that had me flash a firmware zip. This the point at which I made my mistake. As I should have remembered, firmware is DEVICE SPECIFIC. I did not bother to look at what device it was for as I had included "2013 Nexus 7" in my Google search.
The zip I flashed was for the Oppo Find 5. Facepalm.
My device will now not boot at all. I have tried charging for an hour or two from a computer, then a wall charger. The computer does not recognize the device. I've tried every possible button combination to get into recovery, fastboot, normal boot, etc. None have worked.
Anyone have any ideas?

What kind of firmware was it? Bootloader?
Sent from my Nexus 7 (2013) using Tapatalk 4

Muikkuman said:
What kind of firmware was it? Bootloader?
Sent from my Nexus 7 (2013) using Tapatalk 4
Click to expand...
Click to collapse
It was just firmware to help with network, called "modem-4.1.zip"

Blockerville said:
I am an idiot.
Today I decided I would play around with some different ROMs. All was going well. I was becoming adept at flashing, booting, restoring, repeat.
All the ROMs I had tried up to this point were 4.3. I decided to go with something different. I installed OmniRom, which went okay, other than the fact it wouldn't recognize WiFi signals.
As any modern-day geek would do, I took to Google. I found a pretty promising solution that had me flash a firmware zip. This the point at which I made my mistake. As I should have remembered, firmware is DEVICE SPECIFIC. I did not bother to look at what device it was for as I had included "2013 Nexus 7" in my Google search.
The zip I flashed was for the Oppo Find 5. Facepalm.
My device will now not boot at all. I have tried charging for an hour or two from a computer, then a wall charger. The computer does not recognize the device. I've tried every possible button combination to get into recovery, fastboot, normal boot, etc. None have worked.
Anyone have any ideas?
Click to expand...
Click to collapse
I was able to experience a HARD BRICK myself but it was because I flashed a 4.3.1 update on top of a 4.3 once which led me to go into the TWRP recovery and delete my SYSTEM AND INTERNAL STORAGE by accident.
Don't fret my friend. If you're experiencing the supposed HARD BRICK I experienced before (wherein it does not turn on at all), all you have to do is this:
- download the WugFresh N7 toolkit and look for a thread/try to discover how to unbrick your device using that. (they have a specific option for that actually; THANK YOU WUGFRESH)
- download the necessary factory image of your choice and binaries from this page (courtesy of google https://developers.google.com/android/nexus/images)
- You will see a button for at the WugFresh toolkit with instructions on how to unbrick your thing.
Hit thanks if this helps and if you have any more questions, feel free to reply

MartCLEANRFr said:
I was able to experience a HARD BRICK myself but it was because I flashed a 4.3.1 update on top of a 4.3 once which led me to go into the TWRP recovery and delete my SYSTEM AND INTERNAL STORAGE by accident.
Don't fret my friend. If you're experiencing the supposed HARD BRICK I experienced before (wherein it does not turn on at all), all you have to do is this:
- download the WugFresh N7 toolkit and look for a thread/try to discover how to unbrick your device using that. (they have a specific option for that actually; THANK YOU WUGFRESH)
- download the necessary factory image of your choice and binaries from this page
- You will see a button for at the WugFresh toolkit with instructions on how to unbrick your thing.
Hit thanks if this helps and if you have any more questions, feel free to reply
Click to expand...
Click to collapse
There's an option for a soft-bricked device (will turn on, just stuck in a bootloop). However, I don't see the option for a hard-bricked device.
Anyway, I'll try the soft-bricked solution and see if that works.
EDIT: Yep, doesn't seem to be working. It requires the tablet to be in Fastboot mode, which I cannot get into, because the tablet will not boot at all.
Which option did you use to unbrick your tablet?

Still no luck. Any ideas?

Did you try to start into bootloader ?
Nexus off, press volume buttons and power simultaneously.

lapocompris said:
Did you try to start into bootloader ?
Nexus off, press volume buttons and power simultaneously.
Click to expand...
Click to collapse
Yes, I tried that multiple times.

You could try to download the factory image (https://developers.google.com/android/nexus/images), extract the files into the adb platform-tools folder, open a command window and run flash-all.bat

lapocompris said:
You could try to download the factory image (https://developers.google.com/android/nexus/images), extract the files into the adb platform-tools folder, open a command window and run flash-all.bat
Click to expand...
Click to collapse
I will try that. However I do not think it will work, considering the tablet will not boot, so adb will probably not work.
But it's worth a try.

lapocompris said:
You could try to download the factory image (https://developers.google.com/android/nexus/images), extract the files into the adb platform-tools folder, open a command window and run flash-all.bat
Click to expand...
Click to collapse
Yeah doesn't work. adb doesn't see the Nexus.

Blockerville said:
Yeah doesn't work. adb doesn't see the Nexus.
Click to expand...
Click to collapse
Just an update -- sending in the tablet to SquareTrade as I purchased an extended warranty. However I only have $60 coverage at the moment because I already had the screen repaired. If they can't repair it, I'll be getting $60 to put toward buying a new Nexus. I hope all goes well :fingers-crossed:.

So, Nexus devices aren't unbrickable after all?

antypas said:
So, Nexus devices aren't unbrickable after all?
Click to expand...
Click to collapse
They usually are, but if you jack up the boot loader then you're done for.
prshosting.org

Hey Blockerville,
Have you tried this: http://forum.xda-developers.com/showthread.php?t=2381582 ?

Hey guys... i have almost the same problem. I have hard-bricked my nexus 7.
I can go to the Bootloader, but i'm not able to make the pc see the device. I tried installing usb drivers in all the ways, but when in the terminal i go in the sdk directory, and i write "adb devices", it doesn't see anything.......
Is there a way to solve this problem..?
Thanks in advances.

met97 said:
Hey guys... i have almost the same problem. I have hard-bricked my nexus 7.
I can go to the Bootloader, but i'm not able to make the pc see the device. I tried installing usb drivers in all the ways, but when in the terminal i go in the sdk directory, and i write "adb devices", it doesn't see anything.......
Is there a way to solve this problem..?
Thanks in advances.
Click to expand...
Click to collapse
While in bootloader mode, try:
fastboot devices
...not adb devices.

mdamaged said:
While in bootloader mode, try:
fastboot devices
...not adb devices.
Click to expand...
Click to collapse
IT WORKS!
Writing the command "fastboot devices" it sees the device. Now what should i do? I just want to wipe all, reinstal the recovery and flash the factory image... What command i have to write?
PS: Currently recovery doesn't work, for that i need to reinstall it..

met97 said:
IT WORKS!
Writing the command "fastboot devices" it sees the device. Now what should i do? I just want to wipe all, reinstal the recovery and flash the factory image... What command i have to write?
Click to expand...
Click to collapse
Whoa, whoa, I can't tell you what to do next until I know what you've already done, or didn't do.
Please answer the following:
Did you get the correct factory image? <-- very very important
What device do you have (FLO or DEB), I'll assume you know for sure you have the Nexus 7 2013 and NOT the Nexus 7 2012 model.
Which image did you download (so I can check). FLO is wifi, DEB has the LTE.
You do know it will revert your device to like how you got it? So make backups if possible. (you can edit the batch file and remove the -w to prevent wiping).
The following is for when you make sure you have everything right, do not do the following if you are not sure, you should answer those questions above first and I will let you know if it is ok to proceed to the stuff below.
You will need at least these files in a directory before you can do it:
From the factory tgz (once unzipped):
bootloader-flo-flo-04.02.img
flash-all.bat
flash-all.sh
flash-base.sh
image-razor-kot49h.zip
And at least these files from the dev kit:
fastboot.exe
You don't need the following for this operation, but it does not hurt:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
If all that checks out and you verified everything is right, you just do:
flash-all.bat
That will flash EVERYTHING, bootloader, recovery, system, data, cache and userdata.

mdamaged said:
Whoa, whoa, I can't tell you what to do next until I know what you've already done, or didn't do.
Please answer the following:
Did you get the correct factory image? <-- very very important
What device do you have (FLO or DEB), I'll assume you know for sure you have the Nexus 7 2013 and NOT the Nexus 7 2012 model.
Which image did you download (so I can check). FLO is wifi, DEB has the LTE.
You do know it will revert your device to like how you got it? So make backups if possible. (you can edit the batch file and remove the -w to prevent wiping).
You will need at least these files in a directory before you can do it:
From the factory tgz (once unzipped):
bootloader-flo-flo-04.02.img
flash-all.bat
flash-all.sh
flash-base.sh
image-razor-kot49h.zip
And at least these files from the dev kit:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
If all that checks out and you verified everything is right, you just do:
flash-all.bat
That will flash EVERYTHING, bootloader, recovery, system, data, cache and userdata.
Click to expand...
Click to collapse
Yes, you're right........
Well: i got the right factory image, but, sorry for that, when i was searching a solution for my problem, i have found this thread, and i didn't notice that this is for the 2013 model..... well, i've got the 2012 model. And thank you for asking that........ =S
It is the wifi model...
About the backup... i don't really care about the files, i don't actually need to do a back up.
This files:
From the factory tgz (once unzipped):
bootloader-flo-flo-04.02.img
flash-all.bat
flash-all.sh
flash-base.sh
image-razor-kot49h.zip
Click to expand...
Click to collapse
can be in a casual directory? Or they should be in the sdk directory?
the command to flash is....?

Nexus 7 2013 - completely BRICKED

So I completely bricked my tablet, cant even get my PC to recognize the tablet, and the only screen i have up is the Google and the unlock padlock. and if i try a hard reset, all i get is android on his back and the red triangle. I have decided to buy a used motherboard, I see from ifixit.com that they are easy to repair, will this solve my dilema? I found used mobo's on ebay, made sure to get the correct one, is this the answer to not buying a new tablet?

My nexus 7 lte is in the exact same state(that's why I've posted here instead of starting new thread)...by using nrt to try updating to marshmellow as per site's instructions...wondering if anyone can offer a solution???
(bought at google play almost 2 years ago and they already sent me a free refurb replacement...but I still wanna try getting the old one going before sending it back if possible...worth a try before buying a replacement mobo)
here some details of my situation:
ran this on my nexus 7 2013 lte...failed on the first try...tried again..it wiped everything and then failed on install...now I have bootloader (accessible by volume down and power button simultaneously) only and no functional recovery(get the android with red triangle and asterisk when I select Recovery)...the only Android device listed in Device manager is Android Bootloader Interface.
If I start from fastboot mode:
gives a driver failed to load error from windows" and also, now in Device Manager my Android Device Listed changed from "Android Bootloader Interface" to "Android Composite ADB Interface", as well, there is now a Portable Device listed also but it's the driver that failed to load I guess "MTP USB Device" with a yellow asterisk.
If I run the flash-all.bat in the image download that the NRT got on the first attempt, everything goes fine until I get to "sending system"...this fails with unknown data transfer error...
when I download the latest image from developers google.com and extract it I get just one big file with no extension...shouldn't there be a bunch of files including a flashhall.bat file?

^Yes, inside the main image zip is the bootloader (+ radio in your case) and another zip of the actual partition images.
Run fastboot devices from the bootloader just to be sure it's detected. If not uninstall all traces from your pc and start fresh.
Flash the new bootloader, reboot bootloader, flash the radio, reboot bootloader then flash each .img individually with fastboot. Don't use any toolkits.
You should get the "OKAY" after flashing each image. Is it only system that fails? Do you get the okay with boot and recovery? If system only I don't know.
ronf1011 said:
So I completely bricked my tablet, cant even get my PC to recognize the tablet, and the only screen i have up is the Google and the unlock padlock. and if i try a hard reset, all i get is android on his back and the red triangle. I have decided to buy a used motherboard, I see from ifixit.com that they are easy to repair, will this solve my dilema? I found used mobo's on ebay, made sure to get the correct one, is this the answer to not buying a new tablet?
Click to expand...
Click to collapse
The android with the red triangle with exclamation is what happens with stock recovery, you need to press power, volume up and down quickly all at the same time to get in. Usually takes a few tries. If you can get into recovery you could factory reset. It could be another problem though. You have to describe what you previously did to it if you really wan't help.

rma
Thanks for the reply...was never able to get the system image to load...google play is supposed to reemburse me once they receive my original nexus 7 (already got a pristine refurb from them..updated to marshmellow..will be staying away from NRT with this one...)
Thanks again for the reply and suggestions!

system image can't be written
Exactly the same happened to me. After a successful update to MM with Wugfresh's NRT 2.0.5 (with no root) I tried to root my device with 2.0.6 which was released in the meantime.
But that failed because NRT thinks my bootloader is locked, while in fastboot mode I can see that it is unlocked. With fastboot commands I can relock and re-unlock but for NRT it makes no difference.
It seemed to me that a manual reflash of bootloader (FLO-04.05), kernel, cache, system and data should solve this, but no way. The flashall. bat reports a write error of the system.img. A direct fastboot flash system system.img command leads to FAILED (remote: unknown chunk type).
I couldn't find any information about chunk types. I am afraid that somewhere in the process the partitioning was affected. Is that a possibility and can anything be done to fix this? Or are there other solutions for the chunk type error?

Can't use fastboot. target didn't report max download size

Hey all,
I was on android P and wanted to go back to Oreo so i booted twrp and wiped system/data and then afterwards, fastboot is giving me errors and i cant even boot twrp to my phone it just says remote: unknown command. Heres a pic https://imgur.com/a/odn4w
edit: i was able to get the feb image to flash but now im stuck at the loading G screen. If i open fastboot and try fastboot boot twrp i get unknown command. See here https://imgur.com/a/Ropme

Hold the power button while at no command. Then hit volume up and release both. That will give you the menu.
Get rid of minimal adb and fastboot. I don't understand why people are using something made before even the original pixels were released. It doesn't understand dual partitions or handle the larger sizes of our partitions. Get adb and fastboot from Google.

joedajoester said:
Hey all,
I was on android P and wanted to go back to Oreo so i booted twrp and wiped system/data and then afterwards, fastboot is giving me errors and i cant even boot twrp to my phone it just says remote: unknown command. Heres a pic https://imgur.com/a/odn4w
edit: i was able to get the feb image to flash but now im stuck at the loading G screen. If i open fastboot and try fastboot boot twrp i get unknown command. See here https://imgur.com/a/Ropme
Click to expand...
Click to collapse
Try a different USB port.
Ensure you have USB drivers installed first.

TonikJDK said:
Hold the power button while at no command. Then hit volume up and release both. That will give you the menu.
Get rid of minimal adb and fastboot. I don't understand why people are using something made before even the original pixels were released. It doesn't understand dual partitions or handle the larger sizes of our partitions. Get adb and fastboot from Google.
Click to expand...
Click to collapse
Problem is for sure the Minimal setup.
Only setup to use (ever) is here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Updated regularly.

michaelbsheldon said:
Problem is for sure the Minimal setup.
Only setup to use (ever) is here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Updated regularly.
Click to expand...
Click to collapse
I am using that platform tools and i still get the remote:unknown command error. Any idea what i should do? I already factory reset and relocked and unlocked the bootloader and critical. I cant even boot twrp to flash magisk. it broke when i was on android p i booted twrp and wiped system data cache from slot a and b. Reboot and then fastboot was wonky like it still is now.

joedajoester said:
I am using that platform tools and i still get the remote:unknown command error. Any idea what i should do? I already factory reset and relocked and unlocked the bootloader and critical. I cant even boot twrp to flash magisk. it broke when i was on android p i booted twrp and wiped system data cache from slot a and b. Reboot and then fastboot was wonky like it still is now.
Click to expand...
Click to collapse
Just curious, but when your in the OS, and open a command prompt on the platform-tools folder and type...adb devices...do you see your device ID?? Same thing for when your in bootloader mode and type...fastboot devices...??? ?

did you fix this? im in the same boat, on p beta tried to flash factory image back to 8.1 and getting "target didn't report max download size".
Im using platform tools

OP, have you managed to solve the issue?
I ran into a lot of trouble updating June OTA and had the same error. Tried to change ports, USB cables, etc. and just when I was about to give up, I decided to restart my PC and tried again, this time things worked fine without any issue whatsoever.

This is likely not your issue, but if your computer has less than 4 gigs of RAM, or you are trying to flash a file larger than your available RAM you will get this message.

This (i.e. rebooting PC) worked
DanteXXL said:
OP, have you managed to solve the issue?
I ran into a lot of trouble updating June OTA and had the same error. Tried to change ports, USB cables, etc. and just when I was about to give up, I decided to restart my PC and tried again, this time things worked fine without any issue whatsoever.
Click to expand...
Click to collapse
This indeed worked when I rebooted my pc.

Starting to pull my hair out over flashing the Razer Phone

I've been trying to install TWRP and Magisk to the Razer phone for upwards of 3 days now. I cannot get anything to flash through fastboot to the phone no matter what I try. At one point I even said screw it and tried flashing the stock boot image back over to re-lock my bootloader, but no luck, still won't flash.
I was originally following this tutorial here but during the flashing of the boot image it kept failing. Then I tried following the "foolproof" guide found here
I either ended up with the error of "no such file or directory" or "too many links" or "unable to identify current slot". Did a ton of Googling but ultimately came up with no solutions.
I have Android SDK and development studio installed. I have the google drivers installed. I have the Razer phone drivers installed and I have ADB and Fastboot installed.
I have all the files I need on the SD card, and when I'm flashing everything I have the files I need placed in the same folder as the ADB\Fastboot files.
I have my bootloader unlocked, developer mode on and USB debugging enabled. I am using a USB Type A to Type C cable as recommended (made by Anker if it matters). I've tried all 3 USB ports on my laptop. I've even disabled Antivirus.
I have flashed many Android devices in the past and none have given me such a headache as this one. I'm even more ticked off that I can't even get the factory boot image back over to re-lock the bootloader after now realizing that I can't install Netflix anymore because they wen't and blocked installations for Rooted android users (for whatever ridiculous reason).
I will say that for whatever reason that when I go to open command prompt by using the shift+right click I only get the option to use Windows Powershell, not Command Prompt. I also have to put a .\ in front of every command I send. I'm unsure why, but I found no work around for it.
I'd like to try to get the TWRP and Magisk installed. I'm sure I can force Netflix to install over to the phone using another method.
Open to any suggestions!

FireGuy0723 said:
I've been trying to install TWRP and Magisk to the Razer phone for upwards of 3 days now.
Click to expand...
Click to collapse
I feel for you as when things don't work, like someone says they do, it's frustrating. I personally wouldn't be doing everything through power shell but would instead press Windows Key+R to bring up the "Run" dialog box then type "cmd" for command prompt. Trying to restore "command prompt here" to Windows 10 seems stupidly hidden. I'm just not sure if using powershell is messing with your progress.
Second thought is that your Razer phone drivers may not be installed correctly. For me I spent days/hours with my main PC, I then tried another PC and got my phone flashed in minutes. What would happen is that I could send "adb" commands without issue but some of the "fastboot" commands were not working. So at the critical times when it's trying to flash the different portions of our phone, some of them were successful while the others were giving little errors here and there.
I spent a lot of time updating my adb and fastboot commands to newer ones because it seems every time you download someones resources you get a different version. Also the more phones you have owned the more times you have installed specific USB drivers for those phones and they are now hanging around messing things up. There are programs such as USBDeview that will allow you to uninstall those old drivers. For me I had HP drivers from an old tablet, OnePlus drivers, LG drivers, etc.

Munk0 said:
I feel for you as when things don't work, like someone says they do, it's frustrating. I personally wouldn't be doing everything through power shell but would instead press Windows Key+R to bring up the "Run" dialog box then type "cmd" for command prompt. Trying to restore "command prompt here" to Windows 10 seems stupidly hidden. I'm just not sure if using powershell is messing with your progress.
Second thought is that your Razer phone drivers may not be installed correctly. For me I spent days/hours with my main PC, I then tried another PC and got my phone flashed in minutes. What would happen is that I could send "adb" commands without issue but some of the "fastboot" commands were not working. So at the critical times when it's trying to flash the different portions of our phone, some of them were successful while the others were giving little errors here and there.
I spent a lot of time updating my adb and fastboot commands to newer ones because it seems every time you download someones resources you get a different version. Also the more phones you have owned the more times you have installed specific USB drivers for those phones and they are now hanging around messing things up. There are programs such as USBDeview that will allow you to uninstall those old drivers. For me I had HP drivers from an old tablet, OnePlus drivers, LG drivers, etc.
Click to expand...
Click to collapse
I've been messing with it today a bunch. I am back to following the "foolproof" guide and this time I have completely uninstalled all my old drivers for anything android or USB or ADB related and reinstalled everything.
All commands work, I am using command prompt now.
What I am getting hung up on now is even after pushing all three files to the SD card, I run the command "fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot" and it bounces back with " Failed: Write to device failed (no such file or directory)"
I've double checked the file names numerous times. I have no idea what I am doing wrong now. I have tried the command "fastboot boot twrp-3.2.1-0-cheryl.img" as stated in the other tutorial and it bounces back with "failed to identify current slot".
So I'm making progress at least. I'm trying to follow the first set of instructions listed in the fool proof guide but still no luck. I also tried the "clean method" listed below on that guide and that one doesn't work either. Apparently the Fool Proof guide thinks I'm a fool!

FireGuy0723 said:
What I am getting hung up on now is even after pushing all three files to the SD card, I run the command "fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot" and it bounces back with " Failed: Write to device failed (no such file or directory)"
Click to expand...
Click to collapse
I believe that when you run "fastboot flash boot twrp-3.2.1-0-cheryl.img" you are pushing the file called "twrp-3.2.1-0-cheryl.img" that is sitting on your PC's C: or whichever drive you are currently sitting in to the Razer Phone. So make sure the file is in the same directory as where you are running that command. This will then transfer it to the Razer and will reboot into TWRP.
But after you reboot into TWRP you will want to flash the version you have sitting within your SD card to the "recovery" partition. That way it is permanent.

Munk0 said:
I believe that when you run "fastboot flash boot twrp-3.2.1-0-cheryl.img" you are pushing the file called "twrp-3.2.1-0-cheryl.img" that is sitting on your PC's C: or whichever drive you are currently sitting in to the Razer Phone. So make sure the file is in the same directory as where you are running that command. This will then transfer it to the Razer and will reboot into TWRP.
But after you reboot into TWRP you will want to flash the version you have sitting within your SD card to the "recovery" partition. That way it is permanent.
Click to expand...
Click to collapse
I was finally able to get the phone to accept a flash! I ended up saying screw it and dug a old laptop out, fresh install of windows and installed all the proper drivers onto it.
It worked almost flawlessly. It was able to correctly send the twrp.img file and the phone was able to boot into twrp which is about as far as I got. As it was attempting to load twrp it would "crash" the screen would flash twice and try rebooting back to TWRP.
What ended up happening was it got stuck in a boot loop trying to boot into TWRP. (I haven't even installed TWRP.zip yet, just tried booting the .img file).
I couldn't get the phone to boot to the system anymore. I thought I had a nice $600 paperweight on my hands.
I finally got the phone to go back into the boot loader and flashed all the factory stuff back on and relocked the bootloader. So right now I'm 100% back to stock.
I'm not sure what went wrong in the boot up of the twrp.img file. I'd like to try again but I'm kinda getting sick of wiping the phone Everytime something goes wrong.
Sent from my Phone using Tapatalk

I'm wanting to get TWRP / Magisk on my Razer too, but see too many bootloop stories after attempting to flash TWRP.... making me nervous ha ha.
Sorry, not much help, but hope you get it sorted...
Peace

chris5s said:
I'm wanting to get TWRP / Magisk on my Razer too, but see too many bootloop stories after attempting to flash TWRP.... making me nervous ha ha.
Sorry, not much help, but hope you get it sorted...
Peace
Click to expand...
Click to collapse
I had mine in boot loop, I was able to get it out pretty easily. If your able to get the phone into the bootloader (I did using a fastboot command while it was in a boot loop) you can just execute the script provided by Razer and it does the rest. Took about 10 minutes and I had factory everything back on the phone. Relocked the bootloader after and done, phone fixed.
Sent from my Phone using Tapatalk

FireGuy0723 said:
I had mine in boot loop, I was able to get it out pretty easily. If your able to get the phone into the bootloader (I did using a fastboot command while it was in a boot loop) you can just execute the script provided by Razer and it does the rest. Took about 10 minutes and I had factory everything back on the phone. Relocked the bootloader after and done, phone fixed.
Sent from my Phone using Tapatalk
Click to expand...
Click to collapse
In my case I actually had to flash the stock boot.img from the May 2018 stock OS. Then I was able to use Razers guide to flash stock again. I haven't locked my bootloader since I still want to give it a try again. But I want to find a reliable way of rooting and then unrooting in case I want to do so in the feature.
So far I haven't found said documentation.

Installed Magisk v17.1 via TWRP loaded in fastboot boot (not fastboot flash boot ie not permanently installed) and so far all seems well. No boot loops when restarting...
Peace

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