Help Hit Bootloop, adb sideload throwing 'std::bad_alloc'

BecauseRed · Mar 19, 2017

I'm on the 7.1.1 March 2017 Security update from Verizon (NUF26N). I went to load a snapchat and my phone blacked out and got stuck in a Google logo bootloop. I followed the guide from here:

https://drive.google.com/file/d/0Bz6x7k-VkpUJRjl6WjRhVmdXU0E/view

but when I went to adb sideload the NUF26N build I got the following error:

C:\Users\XXXX>adb sideload c:\MyNexus\angler-ota-nuf26n-50c44f30.zip
loading: 'c:\MyNexus\angler-ota-nuf26n-50c44f30.zip'...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

My windows machine has 8GB of RAM so I'm not sure why it is getting a bad_alloc. Does anyone have any insight here?

Thanks

BecauseRed · Mar 19, 2017

I was able to successfully sideload from my Macbook Pro instead but upon a successful load and reboot I'm still getting the boot loop google logo. Is there anything else I can try before looking for a replacement?

redduc900 · Mar 19, 2017

Deleted

codesplice · Mar 19, 2017

BecauseRed said:
I was able to successfully sideload from my Macbook Pro instead but upon a successful load and reboot I'm still getting the boot loop google logo. Is there anything else I can try before looking for a replacement?

Had you installed the Android SDK / platform tools (adb/fastboot) on the Windows machine earlier? Some older versions may but fully support the"adb sideload" command - or it could have been an issue with a bad download. Using a newer version or a fresh download may have led to the successful sideload on the Mac.

The only other thing I can think to try would be wiping data from recovery. That can sometimes help to recover from bootloops. Otherwise I'm afraid you're out of options and should look into getting the phone replaced.

BecauseRed · Mar 20, 2017

I installed the tools at the same time on both Windows and Mac.

I was unable to get back into recovery so I contacted Google and got a replacement device. They were able to help me outside of my warranty which did expire last month. Thanks for the help

codesplice · Mar 20, 2017

I'm glad to hear they were able to take care of you.

graystones · May 19, 2017

I'm experiencing the exact same issue. I have a Windows 8 machine. I can't get the Pixel XL out of the bootloop, and selecting "restart bootloader" "recovery mode," or any other option from the one screen I can get to by holding down the power button and down volume key, does nothing.
I'm looking for some sort of solution as this is an extra phone that I have that is not a warranty phone. It's a perfectly good looking, barely used paperweight at this point, and it would be fun to get it to work. Any ideas?

crramirez · Jun 13, 2017

Hello,

I had the similar error and I made two things that I don't know which fixed the problem:

Used the key combination to enter recovery mode instead of adb way, and selected "Apply update from ADB"
I run cmd.exe with administrative privileges.

Hope it helps

Regards

Brenda Ironchild · Jun 13, 2017

crramirez 
Hello, 

I had the similar error and I made two things that I don't know which fixed the problem: 

Used the key combination tov enter recovery mode instead of adb way, and selected ' Apply update from ADB'I run cmd.exe with administrative privileges.Hope it helps 

Regards 

ADB

Help Hit Bootloop, adb sideload throwing 'std::bad_alloc'

Lurker

Lurker

Member

Elite Recognized Moderator

Lurker

Elite Recognized Moderator

Lurker

Lurker

Lurker

BEST TECH IN 2023

Smartphones

Best Android Phones

Upcoming

Best iPhones

Upcoming

Tablets

Best Tablets

Upcoming

Laptops

Best Laptops

Upcoming

Televisions

Best TVs

Upcoming

Game Consoles

Best Game Consoles

Upcoming

Wearables

Best Wearables

Upcoming

Smart Home

Smart Home Tech

Upcoming

Similar threads