Error While Sideloading 5.1 OTA - Nexus 4 Q&A, Help & Troubleshooting

Hello All
I have soft bricked my Nexus 4 by applying the 5.1 OTA update from the notification in Android. This has left me with both normal boot and recovery leading to the No Command screen. From here, it seems my only route of salvage is the 'Android system recovery <3e>' menu, accessed by tapping Vol Up whilst holding Power on this screen, and using the 'apply update from ADB' option. Unfortunately, after modifying my .inf to allow Windows recognition of the device in sideload mode according to instructions I found on this forum and finding the 5.1 OTA zip for download, I reach another error. The sideload process stops at around 92% on the computer and the phone reads:
Code:
Creating parent of system/priv-app/Hangouts/lib failed, error No space left on device E:Error in /sideload/package.zip (Status 7) Installation aborted.
This error in sideloading persists regardless of using the 'wipe data/factory reset' and 'wipe cache partition' options in the Android system recovery menu. For background purposes, I was on stock LRX22C with CWM 6.0.4.7 for a recovery, and I am now trying the LRX22C to LMY47D OTA zip. Your suggestions are appreciated.
Thank You.

You have to be 100% stock system, kernel, and recovery. If you had cwm on your not stock. Flash the system.img from the version of Android you're currently on with fastboot.
Sent from my Nexus 9 using XDA Free mobile app

Thank you. I feel like a dunce having forgotten all the stuff that can be done with adb and fastboot from the bootloader menu, or even that fastboot referred to the bootloader menu. I mainly like to keep CWM around for having the flashable zip of the offline photo gallery these days. Since CWM and the built-in updater aren't compatible, is the best way for me to take updates just to run the flash-all.sh for each one that comes out and replace CWM afterwards?

I'm on a nexus device too and that's what I do. I'd recommend twrp over cwm, cwm is not updated anymore. You'll have to re-root too. Just flash supersu.zip in the customer recovery. This is a good guide to follow, http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312

fripjob said:
Hello All
I have soft bricked my Nexus 4 by applying the 5.1 OTA update from the notification in Android. This has left me with both normal boot and recovery leading to the No Command screen. From here, it seems my only route of salvage is the 'Android system recovery <3e>' menu, accessed by tapping Vol Up whilst holding Power on this screen, and using the 'apply update from ADB' option. Unfortunately, after modifying my .inf to allow Windows recognition of the device in sideload mode according to instructions I found on this forum and finding the 5.1 OTA zip for download, I reach another error. The sideload process stops at around 92% on the computer and the phone reads:
Code:
Creating parent of system/priv-app/Hangouts/lib failed, error No space left on device E:Error in /sideload/package.zip (Status 7) Installation aborted.
This error in sideloading persists regardless of using the 'wipe data/factory reset' and 'wipe cache partition' options in the Android system recovery menu. For background purposes, I was on stock LRX22C with CWM 6.0.4.7 for a recovery, and I am now trying the LRX22C to LMY47D OTA zip. Your suggestions are appreciated.
Thank You.
Click to expand...
Click to collapse
I had a similar problem. Since I have a number of Nexus Devices I have found using "SoftSkip" Android ToolKit allows me to perform lollipop updates and avoid using OTA"s You should check it out. just google it. The instructions are very simple to follow. I have also used it with both of my Nexus 7's and my Nexus 5 sucessfully. I hope that helps......... Now if I could solve the LTE problem that would be great

Related

stock firmware update w/ root

Hey guys.
So I rooted my Nexus 10, running stock firmware. I want to install the stock update from google but it's not working.
I downloaded it (or rather the system automatically downloaded it), and then i pressed restart and install.
It rebooted into CWM Recovery and I pressed 'install zip'. There's an error thou. It says
assert failed: apply_patch_check("/system/app/BrowserProviderProxy.apk" . "eea9b34d255faa1088912
more weird number blab blah blah
E: Error in /cache/07ac4f5d6c30.signed-mantaray-JOP40C-from-JOP40C. 07ac4f5d.zip
(status 7)
installation aborted
I have a feeling that something is wrong with my browser provider proxy apk i'm guessing?
I honestly have no idea, but if someone could maybe give me a working browserproviderproxy.apk and i can try replacing mine and see if that works?
Does anyone know where this stock update zip file is saved to? Maybe I could try it manually.
Anyways, any help is appreciated! Thanks!
Yep. It sounds like BrowserProviderProxy.apk is modified in some way. The deal with OTAs is that they are deltas, meaning they contain only the data that was changed in an update. If a file was changed, the delta will not work.
Basically, you need to restore to stock, apply the OTA, then re-root. The procedures I have outlined will restore the system to stock without wiping your data.
You will need working drivers and the fastboot command. These can both be obtained from Google's Android SDK. The installation instructions differ depending on what OS you are running.
I apologize if this is a little complicated. I like to use the command line instead of graphical toolkits for tasks such as these. If your graphical utility can do a stock restore without wiping your data, then try it.
Download the 4.2 mantaray factory image from Google. Also, download the 4.2.1 OTA.
Dig through the factory image and extract the boot.img, recovery.img, system.img, and cache.img. (They are in another zip inside the tgz archive.)
Do not run the script that automatically flashes everything. This script will wipe all data on the device. Instead, flash the images individually. Power the device off, then hold all three buttons at once (power and volume up/down). If done successfully, your device will have some text on the screen with an android in the background. (This is bootloader mode.) Run the following:
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cache cache.img
Now your device has the stock firmware, but your data is still intact. Boot into recovery by selecting "Recovery Mode" with the volume buttons and pressing power.
When the "dead android" appears, immediately press and hold power. While holding power, press vol. up. Release vol. up then power. If done correctly, the recovery menu should appear. (If you did not succeed, press and hold all three buttons until you are back in bootloader mode.)
Select the adb sideload option in the recovery menu. Run
Code:
adb sideload <OTA package name>
inserting the name of the OTA package.
You are now upgraded. Now, you need to root your device again. This can be done using any method of your choice.
Whew! I know it's a little complicated, so please ask questions. I will do my best to answer.

[Q] Nexus 10 missing from USB connections in recovery

Hi All,
I've been trying to sideload the net OTA. The dvice shows up while it's running. I can do a 'adb reboot recovery' and it reboots OK, sits at a screen where it says "no command" but the Windows cannot see any kind of connected USB device, no unknown....nothing. I checked on all 5 ports. In Bootloader mode it shows up OK but not in recovery.
Any ideas?
Thx
Update: Now the piece of sh1t will only boot into recovery....how do I get out of that?!? I tried to reset, I can get into boot loader, but 'Start' or fastboot reboot does not get be back into Android.....and as I'm typing this it reboots itself into the OS.....oh well :-|
I'm having this exact same issue. Did you find any fix?
timesgodjillion said:
I'm having this exact same issue. Did you find any fix?
Click to expand...
Click to collapse
No but I worked around it:
Download and install the Nexus 10 Toolkit
download the latest TRWP recovery
rename it to that one supported and included in the Toolkit (I found no way to upgrade the Toolkit to 1.7.1 without paying!)
copy it into the right folder inside the toolkit structure
copy the OTA update into the SDCARD
start the toolkit and boot a recovery without flashing (Option 10 I think)
chose the TWRP recovery
once the recovery has booted you install the OTA zip
Mine failed with some assert error (system/bin/debuggerd) so you may need to use the updater script and remove the assert line (and ONLY the line causing you grief)
Make sure you use something like Notepad++ that doesn't mess up the script file
clear cache and dalvik and then reboot
worked for me

[Q] Nexus 7 Bricked, can't access Bootloader or Fastboot

I think I may have my Nexus 7 (2012) in a badly bricked state.
I was running Android 4.3, unlocked and rooted with stock recovery. The tablet froze while using GMail. Pressing the home or back buttons just gave me a black screen with the buttons "highlighted" by circles. I waited several minutes and decided to just power off the tablet. When I looked over about a half hour later I saw that the tablet was frozen on the white Google screen. Two more reboots produced the same result.
I did some research and determined that it might be a good idea to try a cache wipe. I booted into the bootloader and selected Recovery. The tablet rebooted to an android on his back with a red triangle and the words "No command" underneath. Attempting to boot back into the bootloader (Power, Vol+, Vol-) produced the same results - red triangle and the words "No command". I could no longer boot into the bootloader. Powering off and powering on normally also takes me to "No command".
I discovered that I can press Power & Vol+ while in the "No command" state. Doing so produces the following text at the bottom of the screen:
E:Can't open /cache/recovery/log
E: Can't open /cache/recovery/last_log
E: Can't open /cache/recovery/last_install
E: failed closing /dev/block/platform/sdhci-tegra.3/by-name/MSC
(I/O error)
I get a menu at the top with the options to reboot, apply update from ADB, wipe data/factory reset and wipe cache. Attempting to wipe cache produces:
-- Wiping cache...
Formatting /cache..
Cache wipe complete.
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_locale
After a few minutes I boot back to the red triangle android.
Attempting a factory reset produces:
--Wiping data...
Formating /data...
Formatting /cache...
Date wipe complete.
E:failed to mount /cache (Invalid argument)
E:can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:failed to mount /cache (Invalid argument)
E: failed closing /dev/block/platform/sdhci-tegra.3/by-name/MSC
(I/O error)
E:failed to mount /cache (Invalid argument)
I've tried using the apply update from ADB option. I can use adb devices to see the serial number. Fastboot doesn't seem to respond and won't list the device. Flashing the factory 4.3 image (downloaded from Google and unzipped) using adb sideload uploads the image and then produces the error:
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
...followed by all of the "cache mount / open errors shown previously"
Not sure what else to try. (I'm learning all of this as I go from reading posts on this site.) Is there a way to adb sideload the recovery partition as I suspect that it is corrupt?
Sorry to be so long winded. I figured that too much info was better than not enough. Any help would be greatly appreciated.
So you can still access the recovery menu? That surely means that your tablet isn't bricked and if you can access the recovery, then you too must be able to access the bootloader. Power off your tablet and try to boot into fastboot by using power and volume -, volume + isn't necessary. Are you sure you have also installed the drivers for fastboot mode? Then try to flash the factory images using the guide here
http://forum.xda-developers.com/showthread.php?t=1907796
Sent from my Nexus 7 using xda app-developers app
Remcotjuuh said:
So you can still access the recovery menu? That surely means that your tablet isn't bricked and if you can access the recovery, then you too must be able to access the bootloader. Power off your tablet and try to boot into fastboot by using power and volume -, volume + isn't necessary. Are you sure you have also installed the drivers for fastboot mode? Then try to flash the factory images using the guide here
http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
First - thanks for responding.
To answer your questions. No, I can't access the recovery menu. It doesn't matter how I boot - power button only, power button and vol-, vol+ or power, vol- only --- the device immediately boots to the android on his back with the red triangle. I don't get the normal "menu" where I can use the buttons to choose and select recovery mode. Sometimes there are the words "No command" under the android, sometimes there isn't. I can't get the tablet into fastboot mode.
When the device boots to the android + red triangle, the only thing I have been able to do is push power, Vol+ which gets me to the menu with
reboot system now
apply update from ADB
wipe date/factory reset
wipe cache partition
The "wipe" options fail with the text shown in my original post. If I select "apply update from ADB" it puts the device into ADB Sideload mode. (Not normal ADB mode.) My only option here is to ADB sideload images. I have tried sideloading the factory image. The image transferes, but it fails with a signature error and won't install. I have downloaded the image several times directly from google.
I have uninstalled and reinstalled the drivers a few times. I've used the article that you referenced, another article on this site and used the Wugs Nexus Root Toolkit to install the drivers. I know that my drivers were good originally as I used them to root the device.
Could the errors that I am seeing when I attempt the wipe options indicate a hardware issue? The device seems to be attempting to mount the cache and other partitions and can't.
Additional help is greatly appreciated. Thanks.
awhite2600 said:
First - thanks for responding.
To answer your questions. No, I can't access the recovery menu. It doesn't matter how I boot - power button only, power button and vol-, vol+ or power, vol- only --- the device immediately boots to the android on his back with the red triangle. I don't get the normal "menu" where I can use the buttons to choose and select recovery mode. Sometimes there are the words "No command" under the android, sometimes there isn't. I can't get the tablet into fastboot mode.
When the device boots to the android + red triangle, the only thing I have been able to do is push power, Vol+ which gets me to the menu with
reboot system now
apply update from ADB
wipe date/factory reset
wipe cache partition
The "wipe" options fail with the text shown in my original post. If I select "apply update from ADB" it puts the device into ADB Sideload mode. (Not normal ADB mode.) My only option here is to ADB sideload images. I have tried sideloading the factory image. The image transferes, but it fails with a signature error and won't install. I have downloaded the image several times directly from google.
I have uninstalled and reinstalled the drivers a few times. I've used the article that you referenced, another article on this site and used the Wugs Nexus Root Toolkit to install the drivers. I know that my drivers were good originally as I used them to root the device.
Could the errors that I am seeing when I attempt the wipe options indicate a hardware issue? The device seems to be attempting to mount the cache and other partitions and can't.
Additional help is greatly appreciated. Thanks.
Click to expand...
Click to collapse
Is it under warranty?
xbt- said:
Is it under warranty?
Click to expand...
Click to collapse
No. It's about 10 months old.
Your cache partition is corrupt. Because cache is corrupt, your N7 probably can't boot anything but recovery. Did your N7 turn off while you were wiping cache or something?
Sent from my Nexus 7 using Tapatalk 4
Looks to me as if your boot / system is not working or corrupt. But you are writing you boot always to the dead Android, that's the bootloader mode and from there you should be able to flash a new system by fastboot. As long as you can go to bootloader there is hope for your device unless some hardware defect prevents you from flashing the system images. Try to install the fastboot drivers for your OS and then try to flash the system images. Probably you need to unlock your bootloader first.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
Looks to me as if your boot / system is not working or corrupt. But you are writing you boot always to the dead Android, that's the bootloader mode and from there you should be able to flash a new system by fastboot. As long as you can go to bootloader there is hope for your device unless some hardware defect prevents you from flashing the system images. Try to install the fastboot drivers for your OS and then try to flash the system images. Probably you need to unlock your bootloader first.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
He has already said he can only boot into stock recovery, not bootloader.
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 12:08 PM ---------- Previous post was at 12:07 PM ----------
Now I got myself thinking, the factory images fail, but what about an image for a custom recovery? Try to adb sideload yours from www.clockworkmod.com/rommanager. Is your bootloader unlocked?
Sent from my Nexus 7 using xda app-developers app
cmason37 said:
Your cache partition is corrupt. Because cache is corrupt, your N7 probably can't boot anything but recovery. Did your N7 turn off while you were wiping cache or something?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
The tablet froze during normal operation. (Checking GMail.) I simply turned it off...or so I though. When I looked over about 30 minutes later it was stuck on the white "Google" screen. I was able to boot into the normal bootloader at this point. My thoughts were to then select stock recovery and just wipe the cache. It's been in the "red triangle" and "No command" since then.
AndDiSa said:
Looks to me as if your boot / system is not working or corrupt. But you are writing you boot always to the dead Android, that's the bootloader mode and from there you should be able to flash a new system by fastboot. As long as you can go to bootloader there is hope for your device unless some hardware defect prevents you from flashing the system images. Try to install the fastboot drivers for your OS and then try to flash the system images. Probably you need to unlock your bootloader first.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
The bootloader is unlocked. I was rooted with stock recovery. I have uninstalled and reinstalled drivers several times. I know for certain that the ADB drivers are installed. I don't have an easy way to confirm that the fastboot drivers are installed - but they should be.
Remcotjuuh said:
He has already said he can only boot into stock recovery, not bootloader.
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 12:08 PM ---------- Previous post was at 12:07 PM ----------
Now I got myself thinking, the factory images fail, but what about an image for a custom recovery? Try to adb sideload yours from www.clockworkmod.com/rommanager. Is your bootloader unlocked?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I can try sideloading a custom recovery. I may have already tried this...I've tried so many things. I will try again.
The link that you provided points to .img downloads. I thought that ADB Sideload only worked with .zip images. Am I wrong?
awhite2600 said:
I can try sideloading a custom recovery. I may have already tried this...I've tried so many things. I will try again.
The link that you provided points to .img downloads. I thought that ADB Sideload only worked with .zip images. Am I wrong?
Click to expand...
Click to collapse
Remcotjuuh said:
He has already said he can only boot into stock recovery, not bootloader.
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 12:08 PM ---------- Previous post was at 12:07 PM ----------
Now I got myself thinking, the factory images fail, but what about an image for a custom recovery? Try to adb sideload yours from www.clockworkmod.com/rommanager. Is your bootloader unlocked?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I tried sideloading the clockwork recovery. The .img file transfers. The Nexus 7 then displays:
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
:
followed by all of the E: can't mount/open cache/recovery messages as mentioned in my initial post.
Then I'm getting to a dead end here too. I guess you have tried flashing the bootloader too? And how about using the "flash-all.bat" in the factory images package?
Edit:
Maybe sideloading the zip from the images package that contains boot, system and recovery?
Sent from my Nexus 4 using xda app-developers app
Remcotjuuh said:
Then I'm getting to a dead end here too. I guess you have tried flashing the bootloader too? And how about using the "flash-all.bat" in the factory images package?
Edit:
Maybe sideloading the zip from the images package that contains boot, system and recovery?
Click to expand...
Click to collapse
I'm pretty sure that I've tried flashing the bootloader. When I try again (using adb sideload) I get the same signature verification failed message on the N7 that I did when attempting to sideload recovery images. I then get failed to mount cache messages.
I tried the flash-all.bat. Unfortunately that requires fastboot mode and the tablet won't go into fastboot mode. The batch file just sits waiting for the device to respond. Manually typing fastboot devices fails to list anything.
The only "response" that I seem to be able to get is when I put the tablet into sideload mode. I can type adb devices from a command prompt and get a reply with the serial number. The only other adb command that responds is adb sideload - which always reports signature failed on the tablet. Do you think this is a hardware issue?
awhite2600 said:
I'm pretty sure that I've tried flashing the bootloader. When I try again (using adb sideload) I get the same signature verification failed message on the N7 that I did when attempting to sideload recovery images. I then get failed to mount cache messages.
I tried the flash-all.bat. Unfortunately that requires fastboot mode and the tablet won't go into fastboot mode. The batch file just sits waiting for the device to respond. Manually typing fastboot devices fails to list anything.
The only "response" that I seem to be able to get is when I put the tablet into sideload mode. I can type adb devices from a command prompt and get a reply with the serial number. The only other adb command that responds is adb sideload - which always reports signature failed on the tablet. Do you think this is a hardware issue?
Click to expand...
Click to collapse
I have no idea whether this is a hardware issue, could be, could not be. I remember a thread in which someone had a similar problem, only he had only access to fastboot mode. He eventually fixed it by running the flash-all.bat dozens of times, very strange. So how about sideloading the zip containing boot, recovery and system? I haven't read you tried that. And how about adb pushing flashable zip to your device and flash them in recovery? You can try all kinds of zip, ROMs, recoveries. They do need to be signed because you only have access to the stock recovery I guess.
Remcotjuuh said:
I have no idea whether this is a hardware issue, could be, could not be. I remember a thread in which someone had a similar problem, only he had only access to fastboot mode. He eventually fixed it by running the flash-all.bat dozens of times, very strange. So how about sideloading the zip containing boot, recovery and system? I haven't read you tried that. And how about adb pushing flashable zip to your device and flash them in recovery? You can try all kinds of zip, ROMs, recoveries. They do need to be signed because you only have access to the stock recovery I guess.
Click to expand...
Click to collapse
I've tried sideloading the full factory image. That contains all of the boot, recovery and system images. Just like every other sideload that I've tried the file transfers from the PC. The tablet then reports that the signature verification fails. I've downloaded the factory image three times. I've done FC (file compare) from a command prompt and confirmed that none of the downloads are corrupt - they all match each other.
EDIT: I can't push a flashable zip as I can only adb sideload. I can't adb to just transfer a file. I also can't get into the recovery menu so I can't select a file to flash.
I agree that this is very strange. I've tried Googling the various "can't open / mount cache" message that I keep getting. I can't find anything about them. So this may be a very uncommon issue.
I appreciate your help. I'll keep trying different things. If anyone can think of anything else to try I would appreciate any advice. :fingers-crossed:
awhite2600 said:
I've tried sideloading the full factory image. That contains all of the boot, recovery and system images. Just like every other sideload that I've tried the file transfers from the PC. The tablet then reports that the signature verification fails. I've downloaded the factory image three times. I've done FC (file compare) from a command prompt and confirmed that none of the downloads are corrupt - they all match each other.
EDIT: I can't push a flashable zip as I can only adb sideload. I can't adb to just transfer a file. I also can't get into the recovery menu so I can't select a file to flash.
I agree that this is very strange. I've tried Googling the various "can't open / mount cache" message that I keep getting. I can't find anything about them. So this may be a very uncommon issue.
I appreciate your help. I'll keep trying different things. If anyone can think of anything else to try I would appreciate any advice. :fingers-crossed:
Click to expand...
Click to collapse
No problem. Just be persistent and try sideloading, and maybe adb pushing, the different kinds of images/.zips. Maybe you'll be lucky and magically succeed just like the other guy did. I guess this is everything I could advise you. Good luck.
Fastboot is working only when you are in bootloader mode, when you are in recovery or in "normal" operating mode only adb will work. The command is normally located in the sdk/platform-tools directory of the sdk and I suppose you have the latest android SDK installed.
Btw. for me it makes absolutely no sense that the tablet is booting to recovery directly, because the bootloader is loaded and started before, Only from there you are able to go to recovery, i.e. if recovery mode is working, bootloader must work, too.
To recover your system: go to bootloader mode and get fastboot running, then get the system image and extract all files and do the following:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system -w
fastboot flash system system.img
fastboot reboot
this should be sufficient. If you want to be sure you can also do
fastboot reboot recovery
and do a system wipe from there. And after that reboot into your system. Good luck!
@Remcotjuuh: it's better to use fastboot instead of adb, because you are one level below, i.e. if your recovery is not working correctly, adb will fail while fastboot does not depend on a working adb process.
AndDiSa said:
and do a system wipe from there. And after that reboot into your system. Good luck!
@Remcotjuuh: it's better to use fastboot instead of adb, because you are one level below, i.e. if your recovery is not working correctly, adb will fail while fastboot does not depend on a working adb process.
Click to expand...
Click to collapse
I know, but he has clearly said multiple times that he cannot access the bootloader, although I find this very strange too...
Sony xperia s bricked
Remcotjuuh said:
So you can still access the recovery menu? That surely means that your tablet isn't bricked and if you can access the recovery, then you too must be able to access the bootloader. Power off your tablet and try to boot into fastboot by using power and volume -, volume + isn't necessary. Are you sure you have also installed the drivers for fastboot mode? Then try to flash the factory images using the guide here
http://forum.xda-developers.com/showthread.php?t=1907796
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
i'm experiencing a similar problem with my phone. i rooted my phone today (using http://forum.xda-developers.com/showthread.php?t=2327473) and it was running fine, but i installed an application from the play store called [Root] Developer tools to allow me to load up recovery boot. i gave it permission but when i tried turning my phone on it just stays blank. ive tried the hard reset (up+power button) but all that happens is my phone vibrates 3 times and a green light flashes. please help

Unable to root using Nexus Root Toolkit 2.1.0 and Nexus Player Marshmallow MRA58N

I am having a difficult time rooting my Nexus Player on Marshmallow 6.0 MRA58N
I select the "Root" option and it pushes 3 files to my Nexus Player. Then it boots into TWRP and I plug in my mouse so I can flash:
-beta-supersu-v2.52.zip and
-busybox-signed
Then I reboot system but that's when I get the stuck logo.
I flash the provided files in recovery and then I reboot. However, when I reboot, I just see the animated logo (the one with the balls bouncing from left to right). It is stuck there. What am I doing wrong?
Same problem here, someone help plez.
I haven't even been able to get ADB or Fastboot to detect my NP.
fastboot flash in bootloader (do it manually) and heres all the stuff you will use/need:
http://forum.xda-developers.com/nexus-player/orig-development/marshmallow-mra58n-root-t3256647
I would recommend flashing PureNexus rom if your rooting. Million times better then stock, in my opinion. Its MM and pre rooted too. If your up for that, check it here:
http://forum.xda-developers.com/nexus-player/development/rom-pure-nexus-t3260232
I am unable to sideload PureNexus.
dfl said:
fastboot flash in bootloader (do it manually) and heres all the stuff you will use/need:
http://forum.xda-developers.com/nexus-player/orig-development/marshmallow-mra58n-root-t3256647
I would recommend flashing PureNexus rom if your rooting. Million times better then stock, in my opinion. Its MM and pre rooted too. If your up for that, check it here:
http://forum.xda-developers.com/nexus-player/development/rom-pure-nexus-t3260232
Click to expand...
Click to collapse
Hi I have tried to sideload to PureNexus using the instructions from http://forum.xda-developers.com/nexus-player/development/rom-pure-nexus-t3260232
I am receiving Footer is wrong and Signature validation failure errors.
Unlock your bootloader using fastboot. (fastboot oem unlock)
Flash PureNexus recovery. (fastboot flash recovery "purenexus_fugu_recovery-112515.img")
Reboot Bootloader (fastboot reboot bootloader)
Once in bootloader short press bottom button once until you see recovery option then long press the bottom button.
Once in recovery short press until you get to ADB then long press to get to the ADB sideload screen.
Sideload Rom (adb sideload pure_nexus_fugu-6.0-2015xxxx.zip) where xxxx is the date of the rom you are flashing..THIS IS WHERE I RECEIVE ERROR.
Sideload Gapps (adb sideload purenexus-gapps-mm-x86-leanback-20151202-signed.zip)
Short press until you get to Wipe data/factory Reset then long press (Clears data & cache)
Select reboot now
Once booted setup everything including Kodi
Then go back to recovery and sideload Kodi Mapping zip file. (adb sideload NexusPlayer-kodi-keymap-streaming-fix-signed.zip
Can you please help?
My Nexus Player just upgraded to Android 6.0 using the instructions from, http://forum.xda-developers.com/nexus-player/general/guide-nexus-player-how-to-unlock-t2961989.
Thanks...
dfl said:
fastboot flash in bootloader (do it manually) and heres all the stuff you will use/need:
http://forum.xda-developers.com/nexus-player/orig-development/marshmallow-mra58n-root-t3256647
I would recommend flashing PureNexus rom if your rooting. Million times better then stock, in my opinion. Its MM and pre rooted too. If your up for that, check it here:
http://forum.xda-developers.com/nexus-player/development/rom-pure-nexus-t3260232
Click to expand...
Click to collapse
I installed PureNexus as well, it's pretty nice. I lost adb debugging though, can't get adb to detect the nexus player unless I boot into recovery oddly.

adb sideload "Zip signature verification failed!"

I'm on a Nexus 6p with resurrection remix (for android 6.0.1) trying to flash back to stock 6.0.1. I've been attempting to sideload angler-ota-mtc20l-095e81f7.zip on TWRP (After wiping Dalvik, system, data, and cache) but it keeps saying "Zip signature verification failed!" in my phone and "total xfer: 1.00x" on cmd. I had a backup which I attempted to restore after this failed several times but this left me in a bootloop. Any solution would be appreciated. If you need more information just ask.
Hskom said:
I'm on a Nexus 6p with resurrection remix (for android 6.0.1) trying to flash back to stock 6.0.1. I've been attempting to sideload angler-ota-mtc20l-095e81f7.zip on TWRP (After wiping Dalvik, system, data, and cache) but it keeps saying "Zip signature verification failed!" in my phone and "total xfer: 1.00x" on cmd. I had a backup which I attempted to restore after this failed several times but this left me in a bootloop. Any solution would be appreciated. If you need more information just ask.
Click to expand...
Click to collapse
You'll have to flash the full factory image, not an OTA. You won't be able to side load or flash from recovery. You can either use ADB to flash the full image with the included flash-all.bat, or a toolkit like NRT.
v12xke said:
You'll have to flash the full factory image, not an OTA. You won't be able to side load or flash from recovery. You can either use ADB to flash the full image with the included flash-all.bat, or a toolkit like NRT.
Click to expand...
Click to collapse
I exactly have the same issue but, if I understand correctly, because my device is locked I'm unable to flash the factory image. My phone got bricked during a system update. I had this issue once and I was able to recover it with OTA sideload. But this time it doesn't work: when I do the OTA sideload it gives me the signature verification error.
How could I overcome it?
D4rkFloors said:
I exactly have the same issue but, if I understand correctly, because my device is locked I'm unable to flash the factory image. My phone got bricked during a system update. I had this issue once and I was able to recover it with OTA sideload. But this time it doesn't work: when I do the OTA sideload it gives me the signature verification error.
How could I overcome it?
Click to expand...
Click to collapse
Hi... More infos would help troubleshooting the issue more efficiently.
What was the initial build before the device got bricked?
What was the build "system update" that bricked your phone? Did you update manually or through a pushed OTA? If manually, how did you flash it /bricked your phone?
Finally, which build did you try to Sideload?
5.1 said:
Hi... More infos would help troubleshooting the issue more efficiently.
What was the initial build before the device got bricked?
What was the build "system update" that bricked your phone? Did you update manually or through a pushed OTA? If manually, how did you flash it /bricked your phone?
Finally, which build did you try to Sideload?
Click to expand...
Click to collapse
Thanks for your help.
My current build before the phone got bricked is N4F26I .
I think the update that bricked my phone was N4F26O.
I applied the OTA from the recovery system by selecting "Apply update from ADB" and then doing an adb sideload.
More info:
– I have tried to sideload the OTA images for N4F26I, N4F26J, N4F26O but for all of them I get the error above (I downloaded the OTA image files from Google page)
– Re-downloaded the files, but no joy.
– Phone is not rooted. It had the stock image
- Device shows as LOCKED. If I understand correctly, when device is locked it's not possible to flash the factory image
- USB debugging is enabled
this is the error which happens when I reach 47% of the sideload:
E: failed to verify whole file signature
E: signature verification failed
E: error 21
Installation aborted.
D4rkFloors said:
Thanks for your help.
My current build before the phone got bricked is N4F26I .
I think the update that bricked my phone was N4F26O.
I applied the OTA from the recovery system by selecting "Apply update from ADB" and then doing an adb sideload.
More info:
– I have tried to sideload the OTA images for N4F26I, N4F26J, N4F26O but for all of them I get the error above (I downloaded the OTA image files from Google page)
– Re-downloaded the files, but no joy.
– Phone is not rooted. It had the stock image
- Device shows as LOCKED. If I understand correctly, when device is locked it's not possible to flash the factory image
- USB debugging is enabled
this is the error which happens when I reach 47% of the sideload:
E: failed to verify whole file signature
E: signature verification failed
E: error 21
Installation aborted.
Click to expand...
Click to collapse
Did anyone ever figure out this situation. I'm in exactly same situation. Can't sideload full ota image, quits in middle with signature verification. Bootloader is locked and device wont boot up to enable oem unlocking.
How to get past
adb sideload "Zip signature verification failed!"​Disable signature verification
xinulhacker said:
Come superare
adb sideload "Verifica firma zip fallita!"​Disabilita la verifica della firma
Click to expand...
Click to collapse
How?

Categories

Resources