hello, how can i downgrade from recovery 3e to recovery 2e
i am using motorola droid pro
my battery ist about die, and i can not charge it.
i have wiped the cache and all datas.
now i want to flash a new rom but i can not do it, because i always get an error from recovery 3e
e:signature verification failed installation aborted
"rds lite can not connect to the phone"
i think that noone is interested in droid pro development.
that was the reason why i have sold my phone (
Related
I've been trying to follow the steps in this thread: http://forum.xda-developers.com/showthread.php?t=949497
but I'm having trouble in step 3, getting ClockworkMod Recovery working. I'm on EA28, I'm successfully rooted, and I've flashed the cwm_froyo.tar via odin and put the update.zip in the root of my sdcard. But when I try to reboot into ClockworkMod Recovery, via the "Backup Current ROM" option in ROM Manager, the stock recovery loads and I get an error saying:
E: failed to verify whole-file signature
E: signature verifcation failed
installation aborted
In the blue text of the stock recovery, I have the option to install sdcard:update.zip, but if I try that I get the exact same error.
Any ideas?
******
EDIT: I don't know what I was doing wrong, but I just went back to an older CWM, which worked fine, then I was able to run the new one from there. This thread can be pulled.
Hi people,i recently bought a nexus s and when i try to install any update via recovery, such as the official 2.3.5 uk rom(i am on 4.0.4) i get the verification failed error,i even tried to root using the Superuser-3.0.7-efghi-signed.zip file in recovery but still same error,using 4.0.4 with unlocked bootloader, any ideas how to fix this,i only use linux so hopefully not a windows only fix,Cheers.
Couple of possibilities:
-You're using stock recovery/old custom recovery version; flash the latest CWM or TWRP recovery via fastboot
-Your recovery is corrupt/not for your phone; flash the latest CWM or TWRP recovery via fastboot
-You've toggled an option in recovery to check for signed .zips; turn this off via recovery
@Harbb for some reason check for signatures was ticked, all good now, Cheers
Hello. I have a XOLO Play Tegra Note 7.
A couple of days back I, in an attempt to flash a ROM that I downloaded from the NVIDIA website, I accidentally flashed a boot file from a CyanogenMod image that I downloaded for another purpose. Now, I'm neither able to flash the correct boot image (it is not recognised by adb) nor apply update through bootloader recovery (it says E:footer is wrong, E:signature verification failed). All that's happening is that its bootlooping.
Hello GUYS.. So I was on the latest nougat update and I wanted to try CM13 on my P9 Lite VNS-L31 but someone told me that I need to downgrade to 6.0 before I install CM13 So I downloaded oeminfo and 6.0 rom from update finder.. and first I wiped system, data, cache and dalvik cache..okay so now I have no os installed.. Then I tried to install oeminfo with TWRP.. But it can't mount product/vendor/version (invalid argument) And I was like wtf does this mean? so I flashed stock rom image with fastboot again.. it said it's installed but twrp says no os is installed.. ugh I just tried everything to fix that..I tried to extract vendor.img and product.img and flashed them from fastboot.. But it said command not allowed and still twrp gives me the same errors when i try to wipe data or install system.. I asked people on another site and they told me I should install stock boot and recovery images from twrp and install system with 3 buttons method.. So I did but it said failed.. And when I wanted to flash twrp again the bootloader was locked wtf? so then I tried to unlock it again it asked me if i really wanna unlock it and I choose yes..the phone rebooted and I got this
Error Mode
Attention
Please update system again
(Android Logo)
Error!
Func NO: 11 (recovery image)
Error NO: 2 (load failed)
now I can't boot into recovery or fastboot it just stays in this screen
I tried to install system with the 3 button method but it just won't boot to anything.. I also tried to connect the cable and boot to fastboot..But it. just shows the huawei logo and then goes back to error mode.. please tell me what I should I do now?
hi, did you solve this issue?
You should've just downloaded the rollback package and stock mm rom. Flash the roll back package and then the mm rom in eRecovery. Btw if you are going for meticulus Cm13 rom then ot has been removed from his website and in the beanstalk rom of meticulus when you call someone or someone calls you then the UI restarts. Thats a major bug
Hi! my G935F can't boot after a corrupted EFS file was flashed it just said in the recovery e: unable to mount EFS (Invalid argument) I was tired and I have searched on every site but nothing... until the crazyness came to me!
I managed to fix it flashing twrp on odin, then booting on twrp and using the option reboot, then click on reboot on download directly from twrp it will boot on download but there is no text on the download screen, flash EFS with odin http://efs.firmware.ir/sm-g935f/ and wait(use the odin on the page to flash the EFS File), it will fail try again then it will show all the treaths completed (0 succeded/0 Failed) but that doesn't matter then reflash the stock rom using odin, let it reboot and you'll get the "Device does not have DRK" blue screen let it stay a minute then it will boot straight to recovery saying that it updated some files...
after that go to download again and use odin to flash twrp recovery and then reboot on recovery to make it reboot straight to download again, once there flash CF auto root from here https://desktop.firmware.mobi/ and there you go... let it boot it will say "the device is not seandroid enforcing" then it will automatically reboot and it will surpass the samsung logo... my phone is still on 00000000 IMEI but at least it boots...
Hope it works for you, give it a try but I have to tell you am not responsible for any damage to your device.
Tell me in the comments if it worked