1. Download our Official Android App: Forums for Android!

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

Discussion in 'Android Devices' started by BecauseRed, Mar 19, 2017.

  1. BecauseRed

    BecauseRed Lurker
    Thread Starter
    15

    Mar 19, 2017
    3
    1
    15
    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

     

    Advertisement

  2. BecauseRed

    BecauseRed Lurker
    Thread Starter
    15

    Mar 19, 2017
    3
    1
    15
    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?
     
  3. redduc900

    redduc900 Member
    38

    Apr 23, 2011
    55
    20
    38
    Male
    Portland, OR
  4. codesplice

    codesplice Elite Recognized Moderator
    Moderator
    1,063

    Oct 29, 2013
    8,092
    9,032
    1,063
    Male
    SysAdmin
    Huntsville, AL
    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.
     
  5. BecauseRed

    BecauseRed Lurker
    Thread Starter
    15

    Mar 19, 2017
    3
    1
    15
    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 likes this.
  6. codesplice

    codesplice Elite Recognized Moderator
    Moderator
    1,063

    Oct 29, 2013
    8,092
    9,032
    1,063
    Male
    SysAdmin
    Huntsville, AL
    I'm glad to hear they were able to take care of you. :)
     
  7. graystones

    graystones Lurker
    15

    May 19, 2017
    1
    0
    15
    Male
    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?
     
  8. crramirez

    crramirez Lurker
    5

    Jun 13, 2017
    1
    0
    5
    Male
    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
     
  9. Brenda Ironchild

    5

    Jun 13, 2017
    2
    1
    5
    <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
     

Share This Page

Loading...