I've been researching this problem all night/morning and I'm at my wits end Hoping you guys can help me think through it..
First things first: I'm using a macbook, with the most updated version of the SDK platform tools. My nexus 7 was already rooted and flashed with a 4.4.2 ROM.
I tried to flash the Lollipop factory image onto my 2012 Nexus 7 Wifi yesterday by running './flash-all.sh'. First few times, it errored out (alternating between 'broken pipe' errors and fastboot just flat out not seeing my device). Finally, after rebooting my laptop and continuously running 'fastboot devices' until a device Id actually turned up, I managed to run ./flash-all.sh
The script progressed, errored out on flashing the boot loader, successfully erased pretty much everything including recovery, flashed the system image, and then failed while trying to validate the bootloader version (since it had errored out).
Now I'm stuck in a situation where 'fastboot devices' does not return anything (I've tried 3 different USBs and every single port on 2 different macbook + a linux tower) and I can't get into recovery because it errors out with a 'boot failed' message over the 'Google' icon screen.
I've ruled out the possibility of a driver issue since I'm on a macbook, although I'm going to try installing hte SDK onto my Windows 7 tower later tonight, just to see what happens. Can anyone think of anything else I can try to recover my Nexus 7? I dont even care about flashing Lollipop will do haha.. even stock is fine.
Hi folks,
I've browsed a number of other threads looking for an answer, and tried a number of methods but I feel like further attempts without asking for help are going to be shots in the dark. The issue I'm experiencing is really strange to me, as the device will boot all the way into the OS before rebooting itself after a few seconds. This is my friend's tablet, and I assumed it would be fairly straight forward for me, but that was an incorrect assumption. All apologies if there's a clear cut answer to this solution posted somewhere, I spent quite a lot of time between reading threads here and various search results before finally swallowing my pride and posting here.
Anyway, what the device is doing: It reboots within seconds of booting up to the lock screen (which is responsive to input sometimes, but not others). When it is responsive, I can unlock the device, but I'm not able to do much else before it reboots. As far as I can tell, ADB debugging is not turned on, but "adb devices" returns the device SN when in recovery/sideload mode.
I am able to access fastboot without issue, which displays the following:
PRODUCT NAME - grouper
VARIANT - grouper
HW VERSION - ER3
BOOTLOADER VERSION - 4.23
BASEBAND VERSION - N/A
SIGNING - not yet defined
LOCK STATE - LOCKED
Click to expand...
Click to collapse
I can issue a "fastboot oem unlock," which will bring up the unlock confirmation screen. Here, one of two things will happen.
It will either drop back to the fastboot screen with "Unlocking now......" displayed in the upper left corner of the screen and do nothing, or start the bootloop described above. On the PC side, I get "FAILED (remote: ()"
In recovery mode, it says "Android system recovery <3e> KTU84P." and I'm able to push files via adb sideload (though I had to install Koush's universal ADB driver) . I tried applying the signed-nakasi-LRX21P-from-KTU84P zip, which made it all the way to "patching system files," before rebooting, so I thought I was going to be in good shape, but the bootloop returned. I've also tried sideloading nakasi-ktu84p-factory-76acdbe9.tgz, as well as the image-nakasi-ktu84p.zip from inside the .tgz, but I get "E: footer is wrong, E: signature verification failed."
Even trying a data wipe/factory reset from recovery mode doesn't seem to do a thing, despite it claiming to wipe the cache and data partitions.
Anyway, I'm optimistic considering the tablet is booting (or at least kind of before rebooting). I've tried both the Nexus Root Toolkit (on two different win7 machines) and even went so far as trying it all manually via what they're now calling Android Studio and its dependencies. I'm wondering if either a) there's some kind of image that doesn't require the bootloader to be unlocked (as I was hoping would be the case with the above reference signed LRX21P/Lollipop update zip), or b) if I'm missing something in my attempts to get the bootloader unlocked.
Any thoughts or considerations would be greatly appreciated. I'm not sure what to try other than starting from scratch at this point.
Thanks!
Okay so my brother got an update for his nexus 7 to 5.1 I believe it was. Anyways for whatever reason the update has failed and the tablet will no longer load up to android. Just gets stuck on the boot up screen. I can access fastboot and recovery mode but recovery is saying no command and my pc doesn't recognize the nexus 7 so using adb doesn't seem to be an option. I've gone through and updated all the drivers needed to see the tablet. I'm wondering how in the world do I factory reset this thing? I'm like at a loss so if you can help much thanks to you.
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.
Hello everyone,
I have a very peculiar problem with getting my Essential Phone to work again. It was lying around for roughly two years as I switched to another phone. Seeing as one of my relatives needs a new phone and has really low requirements I thought I could try to set it up again. I downloaded the official drivers again (Version 1.0.0 I think) as well as the last official release of fastboot images (February 2020).
Before I switched to a new Phone I had the Essential running with Lineage OS and remember wiping it with fastboot -w after I got the new device.
Now when I try to flash anything the device won't respond. It shows up when fastboot devices is used in the bootloader, but all fastboot commands get no answer whatsoever. I then switched from the official fastboot drivers to the latest android drivers which then gave me the sending x to y message when I try to flash anything, but nothing actually happens.
Interestingly enough, I can reboot to bootloader just fine and the Lineage Recovery is still accessible eventhough it shows an:
E: Failed to bind mount /mnt/staging/emulated/media/0 on storage/emulated: No such file or directory
on the bottom which leads me to believe that my device partitions may be corrupted outside of the recovery partition and the phone is bricked. In recovery adb commands can be used and I can reboot to bootloader for example.
When trying to sideload via the "Appy Update" function of the Lineage Recovery, I get an:
Error applying update: 26 (ErrorCode::kDownloadMetadataSignatureMismatch))
everytime. I tried different methods and Roms but nothing worked so far.
Can anyone help me with regards to bypassing signature verification entirely or point me in the direction of another solution?
Thanks for reading, I hope you have a nice day!
McMeth said:
Hello everyone,
I have a very peculiar problem with getting my Essential Phone to work again. It was lying around for roughly two years as I switched to another phone. Seeing as one of my relatives needs a new phone and has really low requirements I thought I could try to set it up again. I downloaded the official drivers again (Version 1.0.0 I think) as well as the last official release of fastboot images (February 2020).
Before I switched to a new Phone I had the Essential running with Lineage OS and remember wiping it with fastboot -w after I got the new device.
Now when I try to flash anything the device won't respond. It shows up when fastboot devices is used in the bootloader, but all fastboot commands get no answer whatsoever. I then switched from the official fastboot drivers to the latest android drivers which then gave me the sending x to y message when I try to flash anything, but nothing actually happens.
Interestingly enough, I can reboot to bootloader just fine and the Lineage Recovery is still accessible eventhough it shows an:
E: Failed to bind mount /mnt/staging/emulated/media/0 on storage/emulated: No such file or directory
on the bottom which leads me to believe that my device partitions may be corrupted outside of the recovery partition and the phone is bricked. In recovery adb commands can be used and I can reboot to bootloader for example.
When trying to sideload via the "Appy Update" function of the Lineage Recovery, I get an:
Error applying update: 26 (ErrorCode::kDownloadMetadataSignatureMismatch))
everytime. I tried different methods and Roms but nothing worked so far.
Can anyone help me with regards to bypassing signature verification entirely or point me in the direction of another solution?
Thanks for reading, I hope you have a nice day!
Click to expand...
Click to collapse
I've been reading around a little, it seems like it could be a recovery issue? try the official lineage recovery if you're not already. If you can get fastboot working at all try to reflash the stock rom and go from there.
I had a similar problem. Use a windows computer with the essential drivers (you can download from reddit) and use the official cable
DO NOT use the cable supplied with the Essential phone for data transfer, it is likely to brick your phone. Use a high quality one from a reputable manufacturer!