Database Users

Nexus 7 Stuck in Boot Animation Loop--Please Help

***TL;DR AT THE BOTTOM***
*^*EDIT 2!!*^*
Utilizing Cerberus, I was able to get passed the boot animation into the lock screen, though the Launcher is, for all intents and purposes, nonexistent. However, I was able to install Nova Launcher and can go to a home screen just fine. THIS IS NOT SATISFACTORY. I want to get back to STOCK Launcher, but it apparently does not exist anymore. I've managed to copy over my backup of Launcher2.apk, but it still refuses to acknowledge its existence. Can I get an update.zip that'll reinstall the default launcher from someone? I can boot into recovery via ROM Manager now I suppose!
+++EDIT!+++
+++~~~I have discovered that my problem is not the device being stuck in boot up, but that the boot animation will not cease--as +in the device is actually powered on, just displaying the boot animation like a screen saver. I cannot boot into recovery as I get +the Google splash screen and it never goes anywhere, my bootloader is freezing every time I plug it into my computer, and the +drivers will not install. My computer cannot detect fastboot and I can't connect to the Nexus via adb either. I CAN access internal +storage but that's about the extent of what I can do.+++~~~
Long version:
I decided I wanted to change the App Drawer icon from stock to a Nexus X that inverted its colours when pressed. I found the icon, converted it to png, inverted the colours and everything was going fine.
After a while I finally managed to find the right icons to replace in the system apk file "launcher2.apk". "ic_allapps.png" and "ic_allapps_pressed.png" or something very similar. I simply replaced them with my two icons, installed my modified launcher2.apk, and that was it.
Immediately, my home wouldn't open at all, no matter how many times I pressed the home button. It just would not exit the app I had up. So I started backing and ended up in an infinite back loop. I powered off the device, waited a minute, and powered it back on.
It came to the usual "Google" screen with the unlocked symbol at the bottom, no problems. However, then it started playing the boot animation. The boot animation never stopped. It looped infinitely. I tried resetting the tablet a few times for the same result. It was after 3 am and I had to get up for work in 4 and a half hours. I thought that maybe it was gonna take a while. So I flipped the Nexus over while it was "booting up" and went to sleep.
When I woke up and checked the tablet at 7:30, it was STILL booting up. Obviously I had screwed something up.
Now, stupid me, I had never flashed CWM recovery on my Nexus 7 (haven't had it that long), so all I'm stuck with is STOCK Recovery. I'm pretty sure I can rescue the Nexus by factory resetting it or something similar, but I'd rather try to save it first. All I modified was a LAUNCHER application, so I'm pretty sure the current state of the Nexus itself shouldn't be too far gone. Is there any way to save the Nexus WITHOUT a data wipe? And if the data wipe DOESN'T fix my problem, is it possible to somehow flash a stock ROM through stock Android Recovery?
***TL;DR***
I modified launcher2.apk and replaced "ic_allapps.png" and "ic_allapps_pressed.png" with two customized .png files (which I renamed to their appropriate file names). Now my Nexus is stuck on the boot animation indefinitely. I would like to save all of my data, as a data wipe would be inconvenient, but if I must do one I shall. I am on a stock ROM and a stock Recovery. If a data wipe/factory reset will not save my device, is it possible to flash a stock ROM through regular Android Recovery?
===Related but irrelevant to the problem===
Is it completely impossible to change the stock App Drawer icon to something different? I'd rather not have to get a different launcher app just to create a Nexus theme! I did a little more research and found that I should've modified the "all_apps_button_icon.xml" file as well, but I have NO idea how to do that.
Many thanks,
VonDerThWood.

As long as you can get into the bootloader you can flash back to stock using fastboot and the image from here

NeoMagus said:
As long as you can get into the bootloader you can flash back to stock using fastboot and the image from here
Click to expand...
Click to collapse
no need to flash back to stock, silly advice. just flash a custom recovery and flash a stock rooted rom. flashing a stock rooted rom will replace what you messed up on. dont wipe.

simms22 said:
no need to flash back to stock, silly advice. just flash a custom recovery and flash a stock rooted rom. flashing a stock rooted rom will replace what you messed up on. dont wipe.
Click to expand...
Click to collapse
How can I reflash the ROM on stock Android recovery? Googling that returns CWM results.

He is suggesting you flash custom recovery with fastboot and just flash over top of what you did thru the custom recovery which you can do as well, what I suggested just returns it to factory state I don't see whats so silly about it I understand he wants to keep his data but worse comes to worse as long as you can get into the bootloader you're fine

NeoMagus said:
He is suggesting you flash custom recovery with fastboot and just flash over top of what you did thru the custom recovery which you can do as well, what I suggested just returns it to factory state I don't see whats so silly about it I understand he wants to keep his data but worse comes to worse as long as you can get into the bootloader you're fine
Click to expand...
Click to collapse
youre right about if worse comes to worse. reflashing the factory image should be the very last thing to do, when all other options have been tried. im just trying to save his data

If you don't have fastboot set up you might want to give this post a look he describes how to get it set up.
simms22 said:
youre right about if worse comes to worse. reflashing the factory image should be the very last thing to do, when all other options have been tried. im just trying to save his data
Click to expand...
Click to collapse
I don't use custom recoveries and backup my data regularly with Titanium, so restoring after a reflash is really just an afterthought here, to each there own

The problem is not as it seems.
When I plug the Nexus into the computer when in Fastboot mode, it freezes the Recovery. I cannot select anything OR move the selection to anything else. The hell?
I noticed that when the Nexus attempts to boot up, the boot animation gets brighter.
__
Wait, when it attempted to boot up when plugged into my PC, AutoPlay recognized the device as Nexus 7. There is nothing on my screen but the boot animation, however I can browse internal storage.
I cannot, however, connect to it via adb apparently. ADB devices returns nothing.
____
Okay, the problem is NOWHERE near what I thought it was. The boot animation is replacing the lock screen/home screen/everything. I just received an email (I could tell because of the notification noise the tablet made). It is booting up, just not displaying anything passed the boot animation and ADB cannot detect the device. I KNOW it has USB Debugging mode activated and all, but what can I do now?
===
I usually make backups and nandroids but I've barely owned this device. ;P

Does fastboot detect the device?

janedoesmith said:
Does fastboot detect the device?
Click to expand...
Click to collapse
Fastboot doesn't detect the device while booted up like this, and when I plugged it into the computer when in recovery/fastboot mode it not only froze the device, but fastboot wouldn't detect it.
I can get into the internal storage (just not the root of the device unfortunately). So what can one do when he cannot connect to the device via fastboot or adb, nor flash a custom recovery image because he can't access fastboot?
This is getting more complicated the more I dig into it. What the hell did I do?

Are you on the correct screen? I see how you are lumping Fastboot/recovery together, Fastboot is used on the screen with the android with his chest open after holding down the power/vol buttons from complete off , has version info/ unlock status in the lower left.. not sure if you can do that in the recovery but that is where I put the commands in

the freezing in the bootloader is a n7 bug. try a few times. try going into the bootloader then plugging in usb, and try plugging in via usb then going into the bootloader. try a few times, eventually you will get it.

VonDerThWood said:
Fastboot doesn't detect the device while booted up like this, and when I plugged it into the computer when in recovery/fastboot mode it not only froze the device, but fastboot wouldn't detect it.
I can get into the internal storage (just not the root of the device unfortunately). So what can one do when he cannot connect to the device via fastboot or adb, nor flash a custom recovery image because he can't access fastboot?
This is getting more complicated the more I dig into it. What the hell did I do?
Click to expand...
Click to collapse
You have to be in bootloader for fastboot to detect your device. Once in bootloader, open a command prompt where your fastboot.exe is stored and type "fastboot devices" without the quotes. If it detects it, it should list your N7's serial number.

NeoMagus said:
Are you on the correct screen? I see how you are lumping Fastboot/recovery together, Fastboot is used on the screen with the android with his chest open after holding down the power/vol buttons from complete off , has version info/ unlock status in the lower left.. not sure if you can do that in the recovery but that is where I put the commands in
Click to expand...
Click to collapse
Fastboot has the "Recovery mode" option but it just gives me the Google logo with the unlocked icon at the bottom indefinitely...which means I cannot access recovery either? Why didn't I notice this before? >_<
simms22 said:
the freezing in the bootloader is a n7 bug. try a few times. try going into the bootloader then plugging in usb, and try plugging in via usb then going into the bootloader. try a few times, eventually you will get it.
Click to expand...
Click to collapse
Tried 10 times by booting into bootloader first, then 10 times by plugging it in and booting into it while it's plugged in. This is a very...odd bug.
janedoesmith said:
You have to be in bootloader for fastboot to detect your device. Once in bootloader, open a command prompt where your fastboot.exe is stored and type "fastboot devices" without the quotes. If it detects it, it should list your N7's serial number.
Click to expand...
Click to collapse
Nothing at all. Won't detect it or anything.

it is an odd bug. i think every n7 owner who likes to flash roms/kernels has had to deal with it at least once.

VonDerThWood said:
janedoesmith said:
You have to be in bootloader for fastboot to detect your device. Once in bootloader, open a command prompt where your fastboot.exe is stored and type "fastboot devices" without the quotes. If it detects it, it should list your N7's serial number.
Click to expand...
Click to collapse
Nothing at all. Won't detect it or anything.
Click to expand...
Click to collapse
What about in device manager? Does it at least show an unknown device or something similar? Try reinstalling the drivers.

janedoesmith said:
What about in device manager? Does it at least show an unknown device or something similar? Try reinstalling the drivers.
Click to expand...
Click to collapse
Now that I think about it, it DID say something about failing to install an unknown driver the first time I plugged it in. Let me uninstall/reinstall the drivers.
____
After reinstalling the drivers (and removing both of the Nexus7 specific ones), I also removed one named "Android", which, coincidentally, is the driver that the tablet is trying to install upon being plugged in. I have tried to reinstall it several times, but it fails each time, AND I just reinstalled the real Nexus 7 drivers.
___
The Nexus drivers won't reinstall now. I even went to Asus's website and downloaded them, but I have no clue how to install it in this format.
Is there a way to open/install an app through JUST the Internal Storage? If so, I have the stock launcher2.apk file right here...I just need to reinstall it! Damn, how can I get to the Root folder without ADB?

Whoa! Stroke of GENIUS!
I have Cerberus installed on my tablet. Since I know the tablet is booting up, just not displaying passed the boot animation, I decided to give it a try.
I started an alarm, which forced the tablet to the lock screen...I can open apps through the Play Store (as I got an update notification) and the like, but I can NOT get to the home screen.
I opened Total Commander via Play Store, but I can't do anything with it. The app that I used was NinjaMorph and I'm pretty sure the only way I can correct my mistake is through that app. What do I do?
Found NinjaMorph in the Play Store, it couldn't fix my problem. Oh hell.
I tried to copy/replace the launcher2.apk file I screwed up with a backed up one but TotalCommander couldn't do it. It was even granted SuperUser permissions. Attempting with Root Explorer.
Success! I have copied the original Launcher2.apk back into the /system/app folder. HOWEVER, I can NOT install it.
Managed to connect via adb! Things are looking up! Now, how to install this stuff...?
When trying to reinstall the launcher2.apk, it gives me the following error:
INSTALL_FAILED_UID_CHANGED
So I tried uninstalling it to no avail. Troubling.
SO! Now what? I am into the device, and any app I have downloaded through the Play Store is available to me, but I cannot go to the home screen. I need to reinstall the original Launcher2.apk!
Retrying NinjaMorph. It supposedly installed my Launcher2.apk. However, I still cannot return to the Home screen. WTF.
I'm going to install a different Launcher. Hope that works!
Success. I can now return home to Nova Launcher. HOWEVER...
This is not satisfactory. I want my STOCK launcher. Anybody know how I can fix this? The stock launcher is acting like it doesn't exist anymore. Is there a way to just wipe THAT data and keep all the other data on my device?? (Though I admit, I do like how I already was able to change my App drawer icon to my Nexus X <3.)

Edit: I see you resolved it. Good job! I'll just leave this here... :good:
Is there a way to open/install an app through JUST the Internal Storage? If so, I have the stock launcher2.apk file right here...I just need to reinstall it! Damn, how can I get to the Root folder without ADB?
Click to expand...
Click to collapse
You sound to be in Windows driver hell. If you have access to a Linux machine or someone who does, this entire driver mess can be avoided.
You can't install an apk via the MTP or PTP usb interface. You have a few options to fix this, but all depends on getting your drivers sorted.
Otherwise, grab the latest Windows USB drivers from Google - https://dl-ssl.google.com/android/repository/usb_driver_r07-windows.zip and follow these instructions to install them - http://developer.android.com/tools/extras/oem-usb.html
With the drivers installed and the nexus 7 plugged in, try adb devices again. Assuming you can resolve the driver issue, run
Code:
adb install path\to\launcher2.apk

comminus said:
You sound to be in Windows driver hell. If you have access to a Linux machine or someone who does, this entire driver mess can be avoided.
You can't install an apk via the MTP or PTP usb interface. You have a few options to fix this, but all depends on getting your drivers sorted.
Otherwise, grab the latest Windows USB drivers from Google - https://dl-ssl.google.com/android/repository/usb_driver_r07-windows.zip and follow these instructions to install them - http://developer.android.com/tools/extras/oem-usb.html
With the drivers installed and the nexus 7 plugged in, try adb devices again. Assuming you can resolve the driver issue, run
Code:
adb install path\to\launcher2.apk
Click to expand...
Click to collapse
I managed to get ADB working (via adbWireless) after the above post I made, however I cannot get launcher2.apk to install. This time I got the "INSTALL_FAILED_DEXOPT" error instead of the "INSTALL_FAILED_UID_CHANGED" one.

Bootloop after 4.3 OTA, USB and thus Fastboot not working!

I got a serious problem with the N4 of a friend.
First thing to know: his display was broken and he got it repaired. Afterwards, his phone was running fine. Then, he got the Android 4.3 OTA. He accepted the update, but since then in keeps bootlooping (I won't go past the Nexus-X). As far as I know, everything was stock!
Here are the things I tried:
- first I checked the recovery. Indeed it was the stock one, so nothing to do here.
- I wanted to wipe or flash the stock rom using fastboot but i wasn't able to get a connection. First I thought of driver issues, but my N4 works fine (adb & fastboot) on the same computer.
- Establishing a connection failed on two other computers too (my N4 worked)
- Even the device manager in Windows 7 dosen't even recognize anything when plugging in the usb cable (normally you see the ADB whatever device listed in the device manager)
- Right now I tried to get a connection using Ubuntu. Again, no usb device was recognized when plugging in the cable.
So right now, I'm a bit lost. It seems, that the usb port is broken since I can not establish a connection. And without that, I won't be able to wipe or flash anything using fastboot.
Does anyone have an idea what could have gone wrong? I'm still able to boot into the bootloader and see the information:
Bootloader version: MakoZ20i
Radio: .84
HW Version 11
16GB version
According to these information, it seems that the 4.3 Update finished at least the bootloader and radio. But it won't boot into the rom. Could the download mode be of any help?
I appreciate any help.
Thanks.

Since you are in the bootloader scroll up to recovery and select it.
Now you will see a android opened up with "No command." written below the android.
Press volume up and power until it unlocks the recovery and try to wipe the data and cache partition followed by dalvik cache.
Sent from my Nexus 4 using Tapatalk 4

Thanks for your idea, but it turned out to be hardware problem!
I took the device to the lab and had a look at the usb connector. The contact in the middle was teared of the carrier and was stuck to the back and thus no data connection could be established! I was able to to bend it back (more ore less) to its initial position and now its working. Though I'm wondering how long it will last until its pushed back again.
Fact is, that i was able to connect via fastboot. I tried to flash 4.3 again but it still didn't boot. Its back to 4.2.2 and its working now.
Again - thanks for your idea.
Thread can be closed!

[Q] Help i Have tried everything!!! Need a genius!

im hoping someone can help i really want to get my tablet working again! so its stuck on google logo screen i can get it into fastboot but nothings working to bring it back to life i have tried the kits i have tried it manually both get stuck at sending system. i have tried to push the factory zip by using adb sideload but it says waiting for usb debugging to be enabled which i cant do obviously since it doesnt turn on. any help would be awesome!!!

You can't use adb in the bootloader(fastboot mode). Use fastboot commands to flash a custom recovery and then use adb while in custom recovery (TWRP, CWM)
Sent from my Nexus 7 using xda app-developers app

veeman said:
You can't use adb in the bootloader(fastboot mode). Use fastboot commands to flash a custom recovery and then use adb while in custom recovery (TWRP, CWM)
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
tried it didnt work

Erica24 said:
tried it didnt work
Click to expand...
Click to collapse
That's a little lacking on info. What didn't work? Flashing the custom recovery? The adb transfer? The .zip flash? You need to provide the pertinent info if you want the correct help.
As far as the part of being stuck at sending system, this is something I have noticed when using older fast boot binaries or having a driver issue on your PC. Try downloading the sdk and updating to the newest fast boot and adb binaries. Fastboot refuses to work on my wife's laptop, and gets stuck in the exact same place. But, it works fine from mine.
Sent from my Nexus 7 using xda premium

rebel1699 said:
That's a little lacking on info. What didn't work? Flashing the custom recovery? The adb transfer? The .zip flash? You need to provide the pertinent info if you want the correct help.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
i can flash custom recovery no problem but the adb transfer does not work theres no zip. on the sd card so i have to try and get it on the card to flash it because sending system through fastboot hasnt worked i tried to push it to the sd card but it says waiting for usb debugging.

Erica24 said:
i can flash custom recovery no problem but the adb transfer does not work theres no zip. on the sd card so i have to try and get it on the card to flash it because sending system through fastboot hasnt worked i tried to push it to the sd card but it says waiting for usb debugging.
Click to expand...
Click to collapse
Which custom recovery are you using? I would suggest TWRP 2.6.0.0. I always have great luck getting adb to initialize with it. Just go into the advanced menu and hit adb sideload. As a secondary measure, if you have an otg cable, you can put the zip on a flash drive and load that way too. Advanced-mount-click otg
Sent from my Nexus 7 using xda premium

Erica24 said:
im hoping someone can help i really want to get my tablet working again! so its stuck on google logo screen i can get it into fastboot but nothings working to bring it back to life i have tried the kits i have tried it manually both get stuck at sending system. i have tried to push the factory zip by using adb sideload but it says waiting for usb debugging to be enabled which i cant do obviously since it doesnt turn on. any help would be awesome!!!
Click to expand...
Click to collapse
Hi, Erica24....
I've also had issues with 'sending system' myself... many times. Indeed, when fastboot flashing 4.3 a couple of weeks ago, I had endless problems with it. I'm not sure why, but it could be because of its size.
'sending system' should take no more than a minute or so; two minutes tops.
Anyway, if you think it's taking too long, open up another command prompt window (in whatever folder you have the fastboot.exe stored in) and type...
Code:
fastboot devices
If you DON'T see a SERIAL NUMBER, it means the FASTBOOT connection has died... and you'll be sitting there for evermore waiting for system to go across.
If that is the case, disconnect from the PC, reboot the bootloader, and reconnect to a different USB port on your PC. Also, ensure you're using the original USB cable that shipped with your Nexus 7.
As I've said, for me, 'sending system', is often problematic...but changing USB ports, and trying again, has fixed it for me in the past. It's often just a case of perserverance, unfortunately.
Rgrds,
Ged.

rebel1699 said:
Which custom recovery are you using? I would suggest TWRP 2.6.0.0. I always have great luck getting adb to initialize with it. Just go into the advanced menu and hit adb sideload. As a secondary measure, if you have an otg cable, you can put the zip on a flash drive and load that way too. Advanced-mount-click otg
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I have tried doing it through adb sideload but in red letters it states failed and I am to using twrp 2.6.0.0

Erica24 said:
I have tried doing it through adb sideload but in red letters it states failed and I am to using twrp 2.6.0.0
Click to expand...
Click to collapse
That's because the factory images are NOT flashable zips. You have to use fastboot on bootloader screen for factory images.
Sent from my Galaxy Nexus

I'm a geenyous!
But I'm stumped anyway.
Sent from my cell phone telephone using some sort of app...

GedBlake said:
'sending system' should take no more than a minute or so; two minutes tops.
Click to expand...
Click to collapse
Just flashed my grouper and flo back to factory last night. Both on the same computer running Ubuntu12.04. Grouper took about 15 minutes to send system, flo took less than 2 min.
Sent from my Nexus 7 using XDA Premium HD app

mr1ncred1ble said:
Just flashed my grouper and flo back to factory last night. Both on the same computer running Ubuntu12.04. Grouper took about 15 minutes to send system, flo took less than 2 min.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
15 minutes sounds a bit long... when it works on my grouper, it usually goes across in about 90 seconds. But the trick is getting it to work at all. Which usually involves lot's of plugging and unplugging into different USB ports, and repeatedly rebooting the bootloader. Eventually, it acquiesces... and bends to my will... 'cos I'm stubborn like that.
It's an either-or situation for me... it either goes across quickly, or it doesn't goes across at all. But eventually, it does goes across.
Rgrds,
Ged.

GedBlake said:
15 minutes sounds a bit long... when it works on my grouper, it usually goes across in about 90 seconds. But the trick is getting it to work at all. Which usually involves lot's of plugging and unplugging into different USB ports, and repeatedly rebooting the bootloader. Eventually, it acquiesces... and bends to my will... 'cos I'm stubborn like that.
It's an either-or situation for me... it either goes across quickly, or it doesn't goes across at all. But eventually, it does goes across.
Click to expand...
Click to collapse
Fastboot always works perfectly on the first try and system takes 1 minute. You might have a short in your USB cord, or faulty USB ports.

cmason37 said:
Fastboot always works perfectly on the first try and system takes 1 minute. You might have a short in your USB cord, or faulty USB ports.
Click to expand...
Click to collapse
Hi, cmason37...
Well, anythings possible, I suppose... but your explanation doesn't really hold much weight, as I never have other USB connectivity problems. And I've flashed ROMs on other devices before, without problems. Besides, the whole 'sending system' issue isn't unique to me... it's been referred to before, by others.
I have no idea why it happens, but for some reason the fastboot connection is lost when sending system (and it doesn't happen every time)... it never happens with sending boot, or recovery. I'm used to it; I know that it's not really a problem; just a temporary irritation that is eventually resolved by some USB plugging and unplugging, rebooting the bootboader a couple of times... and some very colourful expletives.
It eventually all gets resolved. And I have JellyBean 4.3, rooted, running on my N7.
But, hey... great you don't have similar inconveniences - glad that it all works for you.
Rgrds,
Ged.

Help: Fastboot Not Receiving Files

Wanting to go back to a factory image on my Nexus 10 so that I can take the update for Android 4.4. Being the lazy guy that I am, I tried to take the easy way out and used the WugFresh tool to go back to the factory image and unroot. It didn't work. Now I have no recovery or system so I can only boot into the bootloader. When I try and flash a new bootloader the command prompt just sits on "sending boot" and never gets there. I am noticing that on the Nexus when I initiate the command a cyan colored box comes up that says "FASTBOOT STATUS - DATA00140000" Sometimes the numbers after the data part are different but that's it. I'm not sure how to fix it because I can't send files to it. Any help would be appreciated.
EDIT: completely uninstalled and reinstalled (for the second time) adb, fastboot, and universal drivers and then rebooted my machine Nexus started connecting just fine.

jcrss13 said:
Wanting to go back to a factory image on my Nexus 10 so that I can take the update for Android 4.4. Being the lazy guy that I am, I tried to take the easy way out and used the WugFresh tool to go back to the factory image and unroot. It didn't work. Now I have no recovery or system so I can only boot into the bootloader. When I try and flash a new bootloader the command prompt just sits on "sending boot" and never gets there. I am noticing that on the Nexus when I initiate the command a cyan colored box comes up that says "FASTBOOT STATUS - DATA00140000" Sometimes the numbers after the data part are different but that's it. I'm not sure how to fix it because I can't send files to it. Any help would be appreciated.
EDIT: completely uninstalled and reinstalled (for the second time) adb, fastboot, and universal drivers and then rebooted my machine Nexus started connecting just fine.
Click to expand...
Click to collapse
I the same happens but with Android L. and you say you fix reinstalling drivers?

Stuck in Boot, fastboot locked, no adb sideload

Hello,
I have a Nexus 6P stuck during boot on the white google logo. Apparently it happened during an update to N.
I have attempted a few solutions I have found either on xda or on other pages but the gist of what I’ve attempted so far is thus:
I have tried to reflash android stock after obtaining it from google : https://developers.google.com/android/images (MTC19T) but the oem option was unchecked so “fastboot flashing unlock” returns with an error.
I have tried to apply an OTA update, again I obtained the file from google (MTC19T) , via the recovery > apply update from adb . But it fails. The error from the phone is:
Code:
E: failed to verify whole file signature
E: signature verification failed
And on the pc side I believe that the failure comes from the fact that my pc has never been connected to the phone via ADB, so it’s unrecognized.
- I have also tried to bypass the adb pc signature issue by connecting a usb flashdrive to my phone via a usb-c adapter but the mount /sdcard command doesn’t work.
I’ve tried a few more esoteric solutions, like booting into Emergency Download (EDL) but my phone just boots into the google logo and stays there.
A few informations on my device (according to the fastboot/recovery screen)
Code:
BL: angler-03.51
Baseband: angler-03.61
Product/Variant: ANGLER-ROW-WN1
6.0.1/MTC19T/2741993
Current Build Number: MTC19T
So, to summarize: Fastboot is locked and won’t work, ADB is unrecognized and using a usb drive pretending to be an sdcard doesn’t work and I’m working with a stock recovery.
I'm looking for a way to bypass the fastbook lock or the adb verification. Or (even better) for anyone here to tell me that I've been going the wrong way all this time and that the solutions involves three easy steps...
Thank you!

Hipstronaute said:
Hello, I have a Nexus 6P stuck during boot on the white google logo. Apparently it happened during an update to N.....I'm looking for a way to bypass the fastbook lock or the adb verification. Or (even better) for anyone here to tell me that I've been going the wrong way all this time and that the solutions involves three easy steps...
Click to expand...
Click to collapse
Try again but you have to use an OTA that is newer than MTC19T. You still may be able to sideload when recovery is in ADB Sideload mode. There is no way to unlock your bootloader. Make sure you are using a recent, known working copy of ADB/Fastboot. The problem many people can't overcome is that they never set up ADB before or used it on a few occasions, so now the phone is dead they can't get it set up correctly. When the phone is connected in recovery>>ADB sideload update, what returns when you run "adb devices"? Do you have another phone you can use to confirm your ADB/fastboot setup is installed correctly?

Download the Nexus toolkit and then boot into recovery and select on the toolkit "softbrick" , good luck. Private message if you need any help
Sent from my Nexus 6P using Tapatalk

Hi,
Thank you for your answers.
@v12xke For the OTA after trying MTC19T I downloaded and tried half a dozen images from Google. Previous versions, next version of marshmallow, a few of the nougat versions. The results were exactly the same.
As for adb I just updated my Android studio, and it's not the first time I've used these tools. The process of sideloading the zip always stops at 47% but I can see that adb and the recovery are communicating.
Fastboot devices also detects my device, but I don't have my computer on me right now.
@DavidSantos I already tried the toolkit but it just launched my phone on the Google logo and got stuck there.

Hipstronaute said:
Hi,
Thank you for your answers.
@v12xke For the OTA after trying MTC19T I downloaded and tried half a dozen images from Google. Previous versions, next version of marshmallow, a few of the nougat versions. The results were exactly the same.
As for adb I just updated my Android studio, and it's not the first time I've used these tools. The process of sideloading the zip always stops at 47% but I can see that adb and the recovery are communicating.
Fastboot devices also detects my device, but I don't have my computer on me right now.
@DavidSantos I already tried the toolkit but it just launched my phone on the Google logo and got stuck there.
Click to expand...
Click to collapse
You have turn off your phone , press volume up and power key , then a menu will pop up , then plug in your phone with your PC
Sent from my Nexus 6P using Tapatalk

DavidSantos said:
Download the Nexus toolkit and then boot into recovery and select on the toolkit "softbrick" , good luck. Private message if you need any help
Click to expand...
Click to collapse
Best way to brick your phone if you don't know what kind of softbrick this tool has been made for... :good:

You have turn off your phone , press volume up and power key
Click to expand...
Click to collapse
Yes, I did that. The soft just makes my nexus reboot to the Google logo.

@v12xke: Looks like there are also more and more of those bootloader + recovery access bootloop. With sideload OTA fails...
@Hipstronaute: I have already seen one or two users with the same kind of problem and if I remember, nothing fixed the problem.
Good luck...

Might be a special edition Nexus 6P , oh well. Mine had the same problem and it worked just fine
Sent from my Nexus 6P using Tapatalk

5.1 said:
@v12xke: Looks like there are also more and more of those bootloader + recovery access bootloop. With sideload OTA fails...
@Hipstronaute: I have already seen one or two users with the same kind of problem and if I remember, nothing fixed the problem.
Good luck...
Click to expand...
Click to collapse
That's too bad. Sounds like the storage memory going bad and the write process is interrupted when it hits that area. Thing is, I've heard the same OTA write failure occurring several times at 47%. Wonder what that means? Anyway sounds like @Hipstronaute is looking at a replacement phone, under warranty or otherwise.

@v12xke
Anyway sounds like @Hipstronaute is looking at a replacement phone, under warranty or otherwise.
Click to expand...
Click to collapse
Gosh do I hope that won't be the last post on this topic.