• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

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

B

BecauseRed

Lurker
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
 
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?
 
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?
Click to expand...

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.
 
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
 
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?
 
Hello,

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

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

Regards
 
<font color ='#9e9e9e'>crramirez </font>
<font color ='#9e9e9e'>Hello, </font>

<font color ='#9e9e9e'>I had the similar error and I made two things that I don't know which fixed the problem: </font>

<font color ='#9e9e9e'>Used the key combination tov enter recovery mode instead of adb way, and selected ' </font><font color ='#9e9e9e'>Apply update from ADB</font><font color ='#9e9e9e'>'I run cmd.exe with administrative privileges.Hope it helps </font>

<font color ='#9e9e9e'>Regards </font>




ADB
 
You must log in or register to reply here.
Back
Top Bottom