Related
Hi,
Following a tutorial on this site, I managed to root and install TWRP 2.6 on my nexus 4 and I had Android 4.3 running. After a notification about an OTA update (I believe the second very small security update), I'm now stuck on the Google name at boot. No coloured animation or anything.
I can still get into TWRP but it shows the "No OS installed" message (rebooting anyway gets me the white Google name).
It seems that fastboot is no longer working either.
adb devices works but fastboot devices does not.
I tried the TWRP sideload feature to install the latest OTA 4.3 image but that did not work either.
I searched for this error and one thread required fastboot, which does not work and the other suggested using adb push. I pushed the latest 4.3 OTA but the installation failed. I then pushed the stock 4.3 image but its installation failed as well. (the error was : "No MD5 file found" and "unable to mount /system"
I don't know much more about adb so I really need help to get my nexus 4 working again
Any suggestions?
Double_U said:
Hi,
Following a tutorial on this site, I managed to root and install TWRP 2.6 on my nexus 4 and I had Android 4.3 running. After a notification about an OTA update (I believe the second very small security update), I'm now stuck on the Google name at boot. No coloured animation or anything.
I can still get into TWRP but it shows the "No OS installed" message (rebooting anyway gets me the white Google name).
It seems that fastboot is no longer working either.
adb devices works but fastboot devices does not.
I tried the TWRP sideload feature to install the latest OTA 4.3 image but that did not work either.
I searched for this error and one thread required fastboot, which does not work and the other suggested using adb push. I pushed the latest 4.3 OTA but the installation failed. I then pushed the stock 4.3 image but its installation failed as well. (the error was : "No MD5 file found" and "unable to mount /system"
I don't know much more about adb so I really need help to get my nexus 4 working again
Any suggestions?
Click to expand...
Click to collapse
download a nexus 4 toolkit and try to adb sideload a rom. then flash it through twrp. had similar issue and the toolkit adb sideload option resolved my problem.
blankit said:
download a nexus 4 toolkit and try to adb sideload a rom. then flash it through twrp. had similar issue and the toolkit adb sideload option resolved my problem.
Click to expand...
Click to collapse
Wow, followed your advice and am now running CM 10.1.3.. Will see whether I keep it or try to return to stock but I'm so relieved that at least my phone is working again. Thanks ever so much!!
Your welcome.
Sent from my Nexus 4 using XDA Premium 4 mobile app
1. I am a newbie and I am I am attempting to flash a new recovery image (Clockwork-6.0.3.8) onto my nexus 10.
I believe the one I have is corrupted or bad or whatever? When I try to update to a newer version on CM I get an immediate error. The tablet starts with a re-boot and immediately when the first step of the update starts I get an error with the image of the android laying down with a yellow or red triangle depicting the error??? So I figure I should reflash the recovery.
I have gotten the nexus connected to my pc and I have fastboot working properly but when I attempt to flash the new image i get the error "cannot load recovery.img : Unknown error" on the PC
I get the error "FASTBOOT STATUS FAILInvalid partiton" on the nexus. I have searched this last error high and low and cannot find anything concrete explaining it.
Apologies if I am posting this in the wrong forum, thanks in advance for any assistance
Nexus 10 with Android 4.2.1 with the following version CM: 10.1-20130120-NIGHTLY-manta. I am trying to update to 10.1.3 and get rid of this nightly.
chuckb74 said:
1. I am a newbie and I am I am attempting to flash a new recovery image (Clockwork-6.0.3.8) onto my nexus 10.
I believe the one I have is corrupted or bad or whatever? When I try to update to a newer version on CM I get an immediate error. The tablet starts with a re-boot and immediately when the first step of the update starts I get an error with the image of the android laying down with a yellow or red triangle depicting the error??? So I figure I should reflash the recovery.
I have gotten the nexus connected to my pc and I have fastboot working properly but when I attempt to flash the new image i get the error "cannot load recovery.img : Unknown error" on the PC
I get the error "FASTBOOT STATUS FAILInvalid partiton" on the nexus. I have searched this last error high and low and cannot find anything concrete explaining it.
Apologies if I am posting this in the wrong forum, thanks in advance for any assistance
Nexus 10 with Android 4.2.1 with the following version CM: 10.1-20130120-NIGHTLY-manta. I am trying to update to 10.1.3 and get rid of this nightly.
Click to expand...
Click to collapse
Go into flashboot and make sure you have no typo's. Redownload your CWM recovery, rename it "recovery.img", and make sure your command line has no typo's. I had issues with a typo and "Unknown errors" and "Invalid Partition", and I had to reboot the tablet a couple times, then retype the command line. Also give TWRP a shot if CWM just won't work
Kit-Kat OTA came out for my Nexus 4 today and I went to apply it but during the install it errored out and the phone subsequently enters a boot loop. I can get into a recovery shell and attempt to push the update via sideload but I get an error:
Symlinks and permissions...
set_metadata_recursive: some changes failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted
I'm 99% sure there's a binary in /system/xbin/ or /system/bin/ thats set immutable (chattr +i) causing this to fail but I can't launch an adb shell from recovery to fix this. Can anybody help me out here?
ykram said:
Kit-Kat OTA came out for my Nexus 4 today and I went to apply it but during the install it errored out and the phone subsequently enters a boot loop. I can get into a recovery shell and attempt to push the update via sideload but I get an error:
Symlinks and permissions...
set_metadata_recursive: some changes failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted
I'm 99% sure there's a binary in /system/xbin/ or /system/bin/ thats set immutable (chattr +i) causing this to fail but I can't launch an adb shell from recovery to fix this. Can anybody help me out here?
Click to expand...
Click to collapse
Are you using stock recovery to do this?
You pretty much explained why, but if you had rooted the phone it could fail due to other reasons too.
If you have an unlocked bootloader then you can boot TWRP (not install, but boot by fastboot boot twrp.img), it have its own terminal and you can go in and chattr -i that file.
Or with unlocked bootloader you just "fastboot format system" and flash the full system.img from the factory image. Or use TWRP to flash a stock rom.
I don't see how else you could have ran a chattr command to the /system without root. But without an unlocked bootloader you pretty much only have the choice of factory reset or unlock the bootloader in which both will wipe all data. But I'm pretty sure beside fastboot erase and format, not even factory reset in recovery could get rid of an immutable file. There is no adb access in stock recovery beside adb sideload signed packages (otherwise every android phones will be very unsecure).
eksasol said:
Are you using stock recovery to do this?
You pretty much explained why, but if you had rooted the phone it could fail due to other reasons too.
If you have an unlocked bootloader then you can boot TWRP (not install, but boot by fastboot boot twrp.img), it have its own terminal and you can go in and chattr -i that file.
Or with unlocked bootloader you just "fastboot format system" and flash the full system.img from the factory image. Or use TWRP to flash a stock rom.
I don't see how else you could have ran a chattr command to the /system without root. But without an unlocked bootloader you pretty much only have the choice of factory reset or unlock the bootloader in which both will wipe all data. But I'm pretty sure beside fastboot erase and format, not even factory reset in recovery could get rid of an immutable file. There is no adb access in stock recovery beside adb sideload signed packages (otherwise every android phones will be very unsecure).
Click to expand...
Click to collapse
Unfortunately, you're correct. I was rooted at one point and had an old 'su' binary around that was immutable, completely forgotten about. My bootloader is stock atm and I'm still stuck on 'no command' I'm accepting the inevitability that I'll have to wipe and start over but I'm not even sure how to flash the factory firmware now since I'm either stuck in a 'Google' boot loop or I get 'no command'.
Any suggestions?
ykram said:
Unfortunately, you're correct. I was rooted at one point and had an old 'su' binary around that was immutable, completely forgotten about. My bootloader is stock atm and I'm still stuck on 'no command' I'm accepting the inevitability that I'll have to wipe and start over but I'm not even sure how to flash the factory firmware now since I'm either stuck in a 'Google' boot loop or I get 'no command'.
Any suggestions?
Click to expand...
Click to collapse
When you see no command that is normal. To bring up the stock recovery menu, while holding Power first, press Volume Up.
Google bootloop have nothing to do with flashing factory image since it required using fastboot in fastboot mode (not in recovery), aka the bootloader menu. Links in my signature have instructions to flash factory image.
eksasol said:
When you see no command that is normal. To bring up the stock recovery menu, while holding Power first, press Volume Up.
Google bootloop have nothing to do with flashing factory image since it required using fastboot in fastboot mode (not in recovery), aka the bootloader menu. Links in my signature have instructions to flash factory image.
Click to expand...
Click to collapse
Cool, gotch ya. Many thanks for the response and help.
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?
I am attempting to put lineageos on my new Mi A1, following the installation guide here https://wiki.lineageos.org/devices/tissot/install
I have previously installed lineage on my old Moto G LTE and a Samsung Galaxy S4 and have not run into issues.
I have unlocked the bootloader and all that but I can't get twrp to boot.
I boot into fastboot with
Code:
adb reboot bootloader
that works fine, then I
Code:
fastboot boot twrp-3.2.2-0-tissot.img
This seems to have no effect, other than my phone 'disconnecting' from the PC.
I get the following terminal output
Code:
./fastboot boot .\twrp-3.2.2-0-tissot.img
Downloading 'boot.img' OKAY [ 0.682s]
booting OKAY [ 0.623s]
Finished. Total time: 1.336s
However nothing happens on the phone, it still just has the fastboot logo on it.
At this point if I manually reboot (long-press power) it will reboot into stock rom.
If I manually reboot into recovery (long-press power+volume up) it will reboot into stock recovery
I have ensured my sytem tools are up to date, and tried the previous version of twrp, and there is no change.
I WAS able to get twrp to boot using the "Mi A1 Tool" i found here https://forum.xda-developers.com/mi-a1/how-to/tool-xiaomi-mi-a1-tool-drivers-unlock-t3742857
However I was not able to install lineage due to an error.
I did not copy the exact output but it was something along the lines of
error 7, kInstallDeviceOpenError
After this attempt, I reflashed the stock rom using Xiaomi tools, and am back to the beginning.
The phone is fully up-to-date with stock updates, Android 8.1, July security update.
Once again went through the bootloader unlocking, and everything, but have arrived at the same result.
Anyone have any ideas?
any help would be greatly appreciated!
Thanks!
Hey, could you try this TWRP made for Oreo? https://www.androidfilehost.com/?fid=818070582850498337 (thread: https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472)
I've also had some issues booting TWRP, but running
Code:
fastboot oem unlock
was enough to boot it successfully (
Code:
fastboot boot recovery-3.2.1-2-oreo.img
)
Thank you!
dgadelha said:
Hey, could you try this TWRP made for Oreo? https://www.androidfilehost.com/?fid=818070582850498337 (thread: https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472)
I've also had some issues booting TWRP, but running
Code:
fastboot oem unlock
was enough to boot it successfully (
Code:
fastboot boot recovery-3.2.1-2-oreo.img
)
Click to expand...
Click to collapse
This recovery image worked great, AND installed lineage, thank you very much.
However, I am now unable to get gapps working.
I was pointed to this changelog here https://lineageos.org/Changelog-19/ by a user in the lineage subreddit.
I rebooted from twrp into the lineage recovery, chose Apply Update -> Apply from ADB
On my PC I run
Code:
./adb sideload .\MindTheGapps-8.1.0-arm64-20180610_024023
.zip
and after a pause I get the output
Code:
serving: '.\MindTheGapps-8.1.0-arm64-20180610_024023.zip' (~0%) adb: failed to read command: No error
and sometimes I get
Code:
serving: '.\MindTheGapps-8.1.0-arm64-20180610_024023.zip' (~0%) adb: failed to read command: Connection reset by peer
What happens on the phone has been a little different each time I have attempted this.
It either pops up on screen that it is unable to verify the file, install anyway?, doing so doesn't work.
OR it is hung up on a progress bar screen, with the following log output, or a slight variation of it
Code:
Stopping adbd...
Now send the package you want to apply to the device with "adb sideload <filename>"...
Finding update package...
Opening update package...
Verifying update package...
E: Signature verification failed
E:error: 21 Restarting dbd... Installation aborted.
After many attempts of this, reflashing lineage, and trying again, it did miraculously start doing the transfer at one point. It got to 47% then failed again.
Can't you just install from recovery?
https://forum.xda-developers.com/mi-a1/development/rom-lineageos-15-1-t3757938
pidermin said:
This recovery image worked great, AND installed lineage, thank you very much.
However, I am now unable to get gapps working.
I was pointed to this changelog here https://lineageos.org/Changelog-19/ by a user in the lineage subreddit.
I rebooted from twrp into the lineage recovery, chose Apply Update -> Apply from ADB
On my PC I run
Code:
./adb sideload .\MindTheGapps-8.1.0-arm64-20180610_024023
.zip
and after a pause I get the output
Code:
serving: '.\MindTheGapps-8.1.0-arm64-20180610_024023.zip' (~0%) adb: failed to read command: No error
and sometimes I get
Code:
serving: '.\MindTheGapps-8.1.0-arm64-20180610_024023.zip' (~0%) adb: failed to read command: Connection reset by peer
What happens on the phone has been a little different each time I have attempted this.
It either pops up on screen that it is unable to verify the file, install anyway?, doing so doesn't work.
OR it is hung up on a progress bar screen, with the following log output, or a slight variation of it
Code:
Stopping adbd...
Now send the package you want to apply to the device with "adb sideload <filename>"...
Finding update package...
Opening update package...
Verifying update package...
E: Signature verification failed
E:error: 21 Restarting dbd... Installation aborted.
After many attempts of this, reflashing lineage, and trying again, it did miraculously start doing the transfer at one point. It got to 47% then failed again.
Click to expand...
Click to collapse
Hey,
Install GApps also at TWRP. Signature verification is failing most probably because the Lineage Recovery should be accepting only Lineage-signed ZIP files.
You can install TWRP in your current boot image (so you don't need to boot TWRP everytime through fastboot) with this ZIP: https://www.androidfilehost.com/?fid=746010030569959456 (yet, you need to boot to TWRP through fastboot so you can flash it, but no need to boot it manually after installing it). Notice that after every system update you may need to install TWRP again (same for Magisk), as boot images get replaced.
Also, if sideload fails, you can just do a
Code:
adb push filename.zip /sdcard/
then install the ZIP directly from the "Install" section on TWRP.
Thanks!
Thanks a lot!
I found and was able to follow this guide
https://forum.xda-developers.com/mi-a1/how-to/lineageos-gapps-magisk-twrp-dolbyatmos-t3762939
instead of the one on the lineageOS website, and I am up and running.
Thank you very much for your time!
Can't boot to recovery or fastboot
I'm totally not getting the problem, i am having network issues on my Mi A1 on both Oreo and pie. So I decided to install a custom ROM but I can't boot my device to fastboot or recovery, it simply reboots . I tried the hard keys as well as through the PC using command prompt it just reboots normally. Any suggestions on what should I do Please?
Azan Qazi said:
I'm totally not getting the problem, i am having network issues on my Mi A1 on both Oreo and and pie. So I decided to install a custom ROM but I can't boot my device to fastboot or recovery, it simply reboots . I tried the hard keys as well as through the PC using command prompt. Any suggestions on what should I do.
Click to expand...
Click to collapse
Have you tried doing reboot in the OS and choosing Recovery option?
Azan Qazi said:
I'm totally not getting the problem, i am having network issues on my Mi A1 on both Oreo and pie. So I decided to install a custom ROM but I can't boot my device to fastboot or recovery, it simply reboots . I tried the hard keys as well as through the PC using command prompt it just reboots normally. Any suggestions on what should I do Please?
Click to expand...
Click to collapse
TrueMS said:
Have you tried doing reboot in the OS and choosing Recovery option?
Click to expand...
Click to collapse
yes sir I did tried several times. But as I said above it simply reboots the system.