I had the R33 and downgrade to TC4-RC30 to get my phone modded, now im trying to get the update HardSPL, and:
When I get into Recovery Mode, yes I have SU with the #, it states "E:Can't open /cache/recovery/command"
I try to update but it says:
E:No Signature (442 files)
E:Verification failed
and im also trying to update to multi-touch ,autorotate and new! JFv1.43 but i cant get passed this
RE update:
Just rename it to update not update.zip
Related
I have tried the SD Card Flashing, by following the instructions on the wiki. The bootloader will scan my SD card but comes up with and Invalid Certificate error and won't start the upgrade.
What now?
hello, yes, i have this problem too.
and..
when i flash a new rom over RUU, abrout this at 3%, and i become a error message.
The message is: Error 270
The Image file is corrupted. Please check your Update utility
and i always have this Problem.
I must unlock the mobile usw.. an then i can flash a new Image
hello, yes, i have this problem too.
and..
when i flash a new rom over RUU, abrout this at 3%, and i become a error message.
The message is: Error 270
The Image file is corrupted. Please check your Update utility
you have to follow ThisTutorial first and there after you can flash any rom you want.
rgds
PAtrick
Hi Patrick,
We Do agree with the Tatorial.
But, after following all this; with One of the ROM after flashing it stays on HTC logo and wont go further.
If trying the Re-Flash from Bootloader the RUU - The message is: Error 270
The Image file is corrupted. Please check your Update utility
Now unable to Boot the Device.
We can get the Bootloader screen but no go further.
ThanX
Shir
Hi, I am currently using the Nexus S i9020a on 4.0.4 and it's unrooted on stock rom.
I wanted to know if it was possible to root it (for apps like AdAway) and maintain the stock rom? The reason why I want to keep the stock is because I tried Cyanogen a few months back and it crashed at least twice a week for me. This is troublesome because at night I use the phone as an alarm and it crashing would kill the purpose.
Thank you!
does it show the unlock icon when you boot?
if so, it should be pretty easy.
just flash a su.zip
if you're locked
you need to unlock your bootloader (which may factory reset your phone)
so backup, unlock bootloader, flash clockwordmodrecovery and su.zip
and there you are, stock, with root
The bootloader is unlocked.
How do I flash su.zip? I had someone do it for me last time so I can't remember how.
I can DL the SuperUser app off the app store but I've learned that it does nothing.
Lastly, is it possible to flash su.zip (wherever that is found) without using a USB cable (mine broke, need a new one I guess)?
Nook000 said:
The bootloader is unlocked.
How do I flash su.zip? I had someone do it for me last time so I can't remember how.
I can DL the SuperUser app off the app store but I've learned that it does nothing.
Lastly, is it possible to flash su.zip (wherever that is found) without using a USB cable (mine broke, need a new one I guess)?
Click to expand...
Click to collapse
you can use SolidExplorer's share files feature (via FTP client) , or AirDroid (via internet browser) to push over su.zip
su is here
http://downloads.androidsu.com/superuser/su-bin-3.0.3.2-efghi-signed.zip
move that to your sdcard and boot into clockwork recovery with (VolUp + Power, then select Recovery)
I tried downloading that file and then going to Recovery.
I did "apply update from /sdcard" and hit the .zip file but I get the following errors:
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Any ideas?
Nook000 said:
I tried downloading that file and then going to Recovery.
I did "apply update from /sdcard" and hit the .zip file but I get the following errors:
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Any ideas?
Click to expand...
Click to collapse
are you sure you have clockworkmod recovery installed?
Not completely sure, when I go to Recovery, the top says:
"Android System Recovery <3e>"
Edit: I just went to http://www.clockworkmod.com/rommanager to download CWM Recovery but it's an .img file which it won't let me flash after reboot into Recovery.
Flash it either via fastboot or download through Rom Manager and install. I usually do the former.
Open up adb.
Turn off device and power back on into fastboot(power+vol up)
Make sure the recovery image is in the same directory as adb.
Name the recovery image to recovery if it hasn't been changed
Type fastboot flash recovery recovery.img
I've done it that way for a while now no issues. You also need a script or a .zip file that will keep the custom recovery so the stock one doesn't replace it.
You can flash it:
http://forum.xda-developers.com/showpost.php?p=23125913&postcount=2
Or you can edit the file that does this by following these steps in this post
http://forum.xda-developers.com/showpost.php?p=27027436&postcount=8
HTH
Thank you a whole very much!! Using both of your advice, I was able to root the device. It took a while because despite installing the drivers, when I went into the Bootloader, it wasn't detected. The remedy was manually setting it to the Bootloader driver irregardless of Windows suggesting I shouldn't.
Now it's all good to go! Thanked you both.
chronophase1 said:
Flash it either via fastboot or download through Rom Manager and install. I usually do the former.
Open up adb.
Turn off device and power back on into fastboot(power+vol up)
Make sure the recovery image is in the same directory as adb.
Name the recovery image to recovery if it hasn't been changed
Type fastboot flash recovery recovery.img
I've done it that way for a while now no issues. You also need a script or a .zip file that will keep the custom recovery so the stock one doesn't replace it.
You can flash it:
http://forum.xda-developers.com/showpost.php?p=23125913&postcount=2
Or you can edit the file that does this by following these steps in this post
http://forum.xda-developers.com/showpost.php?p=27027436&postcount=8
HTH
Click to expand...
Click to collapse
He's right...and thanks for the refrence
If you are going to keep stock then when you reboot Clockworkmod Recovery won't stick. Do as I said in the referenced post or flash a new Rom (my choice , or just live with it. If you want CWM you will have to USB, cmd fastboot flash recovery recovery.img every time.
Edit: posted a minute before me. Awesome and enjoy!
Glad to hear it worked! And no problem, bud! I try to keep the good posts saved for situations like this
guide
Personally when i rooted my nexus S for the first time,i followed this guide
Its precise,step-by-step and includes a video incase you need one
i am prevented from posting the link but if you search google for nexusshacks.com,you should easily find it.
Hi.
I tried to update to Android Lollipop 5, and after I sideload the zip to the device it says (in the device):
Code:
e: footer is wrong
e: signature verification failed
I have a D821 Nexus 5, the device has never been rooted nor have I changed roms.
What can I do to fix this?
Thanks!
BTW: I noticed that when I open the fastboot menu, it says "Secure boot - enabled, lock state - locked" if it means anything.
having same issue. any ideas?
AlonMln said:
Hi.
I tried to update to Android Lollipop 5, and after I sideload the zip to the device it says (in the device):
Code:
e: footer is wrong
e: signature verification failed
I have a D821 Nexus 5, the device has never been rooted nor have I changed roms.
What can I do to fix this?
Thanks!
BTW: I noticed that when I open the fastboot menu, it says "Secure boot - enabled, lock state - locked" if it means anything.
Click to expand...
Click to collapse
What zip are you talking about? Is it the .tgz from the android developers site?
You don't flash that in recovery, your extract it on your computer, put your phone in download mode, then run the batch file called flash-all.bat
That message at the end means your bootloader is locked. You need to follow the instructions on the page you got it from.
we're talking about sideloading the update to the device so data isn't lost
realised that this is the factory file and not the proper ota file which is why it's not working. noob moment...
krs360 said:
What zip are you talking about? Is it the .tgz from the android developers site?
You don't flash that in recovery, your extract it on your computer, put your phone in download mode, then run the batch file called flash-all.bat
That message at the end means your bootloader is locked. You need to follow the instructions on the page you got it from.
Click to expand...
Click to collapse
Am I able to sideload LRX21O if I am currently running 5.0 DP on my N5?
dholms said:
Am I able to sideload LRX21O if I am currently running 5.0 DP on my N5?
Click to expand...
Click to collapse
No. The OTA is for 4.4.4
Ok. I'm trying to install CyanogenMod 10.2.1 (From download.cyanogenmod.org/?device=d2vzw&type=stable) via Recovery via the second set of instructions at wiki.cyanogenmod.org/w/Install_CM_for_d2vzw. This is because errors were made and I can only currently access Recovery mode and Download mode. I am not well-versed in this kind of stuff, I'm simply doing this because my phone is otherwise bricked.
In case it's important... My recovery mode differs from what the instructions seem to expect though: I have to select "Apply update from ADB." I send it to the phone using the command "adb sideload cm-10.2.1-d2vzw.zip" and the phone finds, opens, and attempts to verify the update package. That's where the snag is:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Do I have a corrupted zip? Am I following the instructions wrong? Help!
Edit: I tried a different version of CM and got the same error.
KalininTest said:
Ok. I'm trying to install CyanogenMod 10.2.1 (From download.cyanogenmod.org/?device=d2vzw&type=stable) via Recovery via the second set of instructions at wiki.cyanogenmod.org/w/Install_CM_for_d2vzw. This is because errors were made and I can only currently access Recovery mode and Download mode. I am not well-versed in this kind of stuff, I'm simply doing this because my phone is otherwise bricked.
In case it's important... My recovery mode differs from what the instructions seem to expect though: I have to select "Apply update from ADB." I send it to the phone using the command "adb sideload cm-10.2.1-d2vzw.zip" and the phone finds, opens, and attempts to verify the update package. That's where the snag is:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Do I have a corrupted zip? Am I following the instructions wrong? Help!
Edit: I tried a different version of CM and got the same error.
Click to expand...
Click to collapse
If your phone is on 4.3 or 4.4.2 you cannot install a custom recovery or CM because your bootloader is locked.
Is there any way to unlock or replace the bootloader from Recovery, then? I tried forum.cyanogenmod.org/topic/67061-trying-to-flash-cm-on-d2vzw/#entry369787, but it just says, "error: closed" on the command prompt.
KalininTest said:
Is there any way to unlock or replace the bootloader from Recovery, then? I tried forum.cyanogenmod.org/topic/67061-trying-to-flash-cm-on-d2vzw/#entry369787, but it just says, "error: closed" on the command prompt.
Click to expand...
Click to collapse
As far as I know, there is no way to unlock or replace the bootloader
Hello,
This is probably a 'noobish' question but I'm a bit confused.
I have an AT&T Sonim XP8 that I flashed with this user debug image since the device got bricked so had to be re-flashed completely.
For reference, the bootloader is also unlocked.
Every time I try to update from AT&T Software Updater, the update downloads but the install will 'interrupt' and then if I try again it says the software is fully updated.
So I tried downloading the OTA updates from here but receive the error 'failed to verify whole-file signature' when I boot into recovery mode and try to install updates via adb.
So what I did next was factory reset the phone, run AT&T Software Updater with adb logcat running so I could try and capture the OTA update. I was able to, and this is the link if anyone wants it.
Then I booted into recovery mode and used this with the adb sideload command, and it still failed with the same failed to verify whole-file signature error. I was kind of confused why this would fail, considering that it's literally from the carrier.
If anyone could help me I would greatly appreciate it.