Related
Anytime I try to do anything through Rom Manager (flash a ROM, nandroid backup, etc.) upon rebooting into recovery, I get a white triangle with an yellow exclamation point. After pressing the power button, the following text is revealed along with the Clockwork Recovery Menu.
Finding update package...
Opening update package...
Verifying update package...
E:failed to seek in /cache/update.zip (Invalid argument)
E:signature verification failed
Installation aborted.
If I select advanced->Reboot Recovery after receiving the error, the device reboots. After this second reboot, the process continues as it should have after the first reboot. I've tried downgrading the version of my Clockwork Recovery, but it seems to have no effect.
Any ideas?
...
I believe the standard array of initial questions would be:
1) Did you flash S-OFF?
2) Is your card FAT32 formatted
3) Try redownloading the file using a different browser (to ensure a cache doesn't deliver the same update.zip without trying)
jdmba said:
I believe the standard array of initial questions would be:
1) Did you flash S-OFF?
Click to expand...
Click to collapse
Yes.
jdmba said:
2) Is your card FAT32 formatted
Click to expand...
Click to collapse
Yes.
jdmba said:
3) Try redownloading the file using a different browser (to ensure a cache doesn't deliver the same update.zip without trying)
Click to expand...
Click to collapse
This failure isn't specific to any one file. Besides, I don't think it's a corruption of the file since it works when I select "reboot recovery" from the first failed attempt. In fact, this even happens when choosing "Backup ROM" from ROM Manager.
On a side note, I've tried wiping cache in ROM Manager as well.
Toggle Signature Verification and/or is d/l corrupt?
In CWM, have you tried toggling the on or off setting for the signature verification, as well as the other toggle?
Also, I read some superb advice here:http://http://forum.xda-developers.com/showthread.php?t=765930
check out the advice in post # 285 and see if that fixes you up.
Everyone seems to think my downloads are corrupt. That is definitely not the problem. If they were corrupt, they wouldn't function after the first reboot. They would continue to fail. Let me try explain my problem another way...
Here's my device setup...
Radio - 2.15.00.07.28
Kernel - King's BFS #4
ROM - SR Vanilla RC 2
CWM Version - 2.5.0.5
ROM Manager Version - 2.0.2.6
Here's a process I'm following...
1. Open ROM Manager
2. Clear Download Cache (Just to be sure!)
3. Select Backup Current ROM which causes reboot into recovery.
4. Receive the error which I outlined in my first post. *NOTE* I have not downloaded nor chosen to flash ANY update.zip files. *NOTE*
5. Open the advanced menu in CMW and choose "Reboot recovery" which causes the phone to reboot into recovery.
6. The backup progresses like it should have after the first reboot.
Again, the process above does not involve the use of any downloaded update.zip files. No ROMS, no Kernels, etc.
Does ROM Manager create it's own update.zip file stored in /cache to execute whatever function it needs to after reboot? It appears that might be the case.
I've attempted to reinstall ROM Manager and downgrade to an early version of CWM in ROM Manager. Neither seem to have helped.
I had the same problem trying to flash the latest leedroid
I entered recovery, de-selected signature verification and then flashed the rom through recovery mode.
Flashed normally and up to now it looks like it worked (waiting for first boot)
Hope this helped
Both signature verification and script asserts are toggled off. This is why the update.zip will flash after the second reboot into recovery and manually.
In recovery, is cache, data, or system mounted? If so, can you unmount any/ all, and reboot?
Sent from my ADR6300 using XDA App
I just started having this problem today, at least i noticed it today. It acts as if the signature verification is enabled the first try and disabled the second time. I can't find ANY way to fix this but reboot recovery and it works... If anyone finds a solution, please post.
*edit* I also noticed the "Fix Permissions" utility doesn't work in ROM Manager. Dont know if this is related or not.
PIYIRIO said:
I just started having this problem today, at least i noticed it today. It acts as if the signature verification is enabled the first try and disabled the second time. I can't find ANY way to fix this but reboot recovery and it works... If anyone finds a solution, please post.
Click to expand...
Click to collapse
Did you change anything today? I found someone in the SR ROM thread today that started having the same problem.
No, only an app and removed it. I dont know how long it has been broke since I haven't used it since SR 3.0rc1.. got tired of the reminder for rc3 and it wouldn't automagically run the install.zip.
Interesting.... Please post as this shakes out.
Sent from my ADR6300 using XDA App
I have this same issue, I think it's an issue with Rom Manager. No matter what I try to do from there (Reboot to Recovery, make backup, flash zip, etc.) I get that string of messages.
If I download a file from ROM manager to be flashed, I have to move the file to the root of the sd card before booting to recovery for it to flash correctly. I have just gotten used to doing it this way.
srt4mn said:
I have this same issue, I think it's an issue with Rom Manager. No matter what I try to do from there (Reboot to Recovery, make backup, flash zip, etc.) I get that string of messages.
If I download a file from ROM manager to be flashed, I have to move the file to the root of the sd card before booting to recovery for it to flash correctly. I have just gotten used to doing it this way.
Click to expand...
Click to collapse
Me as well
PIYIRIO said:
*edit* I also noticed the "Fix Permissions" utility doesn't work in ROM Manager. Dont know if this is related or not.
Click to expand...
Click to collapse
If you look in the OP for the SR ROMS, you'll see that a known issue. He includes a fix_permissions binary instead.
I've reached out to the developer. Hopefully we will hear from him soon.
Can you guys try clearing your download cache, and then reflashing recovery?
Possible workaround
Koush said:
Can you guys try clearing your download cache, and then reflashing recovery?
Click to expand...
Click to collapse
Cache wipe have been tried, see post #3.
I have some info that may be valuable:
This evening I rooted my Desire (SLCD) using Unrevoked 3.14 and recovery-clockwork-2.5.0.7-bravo.img I realize this is the incredible forum but hold on.. hear me out
I observed the _exact_ same behavior:
- Yellow eclamation + second reboot to recovery would run backup, also happened when selecting "Reboot Into recovery" in RomManager (RM)
- Tried DL cache wipe in RomManager,
- Tried reflash of recovery
This fixed it for me:
- Re-root via Unrevoked 3.14 using recovery-clockwork-2.5.0.1-bravo-slcd.img
- Re-flash CM (this may be optional, I don't know)
- Boot ROM and start RM just to have it tell me I need to install recovery (obviosly didn't detect my 2.5.0.1-bravo-slcd)
- Allow RM to flash 2.5.0.7-bravo via download
- Now "Backup ROM" and "Reboot to recovery" works as intended
- RM reports 2.5.0.7-bravo installed, recovery booted (via RM) is 2.5.0.7-bravo BUT recovery booted using HBOOT (back+power on Desire) is 2.5.0.1-bravo-slcd (!)
Note: Incredible users should _not_ use -bravo recovery images(!) just outlining how I made it work to help you find a solution
Koush said:
Can you guys try clearing your download cache, and then reflashing recovery?
Click to expand...
Click to collapse
Worked for me. Thanks Koush!
Sent from my ADR6300 using XDA App
Didn't work for me.. I've tried everything that I can think of. Different SD cards, i've formated /data/ /cache/ and reinstalled..
i'm using virtuous 2.7
I previously managed to flash clockwork and sentinel. Now my recovery is corrupt and I cannot flash the recovery (or boot) .img..
I get the error 0X3000 remote fail when I try fastboot flash recovery recovery.img (the name of my ROM).
I cured this on the first install by fastboot erase cache. this now gives the error failed remote err )x 1900000
fastboot devices gives me the device name.
So my recovery is corrupt, and I want to flash a new recovery and then a new ROM.
Thanks
Fish
Managed to get recovery working but could not mount usb no drive E: error.
No backup either, even though i did one, files missing.
Tried to install zip, but lots of directories missing.
fishdude1 said:
I previously managed to flash clockwork and sentinel. Now my recovery is corrupt and I cannot flash the recovery (or boot) .img..
I get the error 0X3000 remote fail when I try fastboot flash recovery recovery.img (the name of my ROM).
I cured this on the first install by fastboot erase cache. this now gives the error failed remote err )x 1900000
fastboot devices gives me the device name.
So my recovery is corrupt, and I want to flash a new recovery and then a new ROM.
Thanks
Fish
Managed to get recovery working but could not mount usb no drive E: error.
No backup either, even though i did one, files missing.
Tried to install zip, but lots of directories missing.
Click to expand...
Click to collapse
Hi there, Which recovery u have u flashed? and with which recovery the backup u mentioned was taken?
SOLVED
keertikumar_ws said:
Hi there, Which recovery u have u flashed? and with which recovery the backup u mentioned was taken?
Click to expand...
Click to collapse
Recovery was clockworkMod (the version with chargimng and full USB).
I eventually rebooted my PC and could then erase cache, flash recovery again, mount USB from recovery and reflah boot, now alls well.
(Except no keyboard
So looks like the errors were PC related.
Ha..ha..okie...glad that its finally resolved
Thread #4
Sent from my HTC One X using XDA Premium 4 mobile app
I have an issue that I cannot for the life of me fix. Last night my wife’s phone received the OTA update and her phone would not restart after that. Total B.S. move on ASUS’s part not to pull that update knowing the issues people were having. But anyways, here’s the rundown. I can boot into bootloader mode but I cannot get into stock recovery. I can, through a certain method get into CWM recovery and I can see the external SD, but I get errors when I try to flash an update or another entire OS. I’ve tried to bypass signature verification also and still cannot get anything to install. ADB will not sideload because it does not find my device, but the method of getting into CWM recovery is done through ADB so I’m confused there. Never have I had such a tough time restoring a bricked device. Samsung, no problem. Huawei, no problem. This POS I’m about ready to throw in the pool and call it a day. Does anyone have any suggestions?
Try flashing CN version and dont forget to disable zip signature and format everything before flashing
Sent from my ASUS_Z00AD using Tapatalk
LiRi2000 said:
Try flashing CN version and dont forget to disable zip signature and format everything before flashing
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
The only way I can flash is through the CMW recovery and everything I try to flash says cant install this package over newer build. But there's nothing on the device as far as I can tell. Also says E: Error in /external_sd status 7
MikeyLee said:
The only way I can flash is through the CMW recovery and everything I try to flash says cant install this package over newer build. But there's nothing on the device as far as I can tell. Also says E: Error in /external_sd status 7
Click to expand...
Click to collapse
Open ROM archive with app (for example WinRAR),
navigate to META-INF\com\google\android
unpack updater-script
open unpacked updater-script with any text editor (I use Notepad++)
remove first line with "(!less_than_int..."
save file
put unpacked file back in archive overwriting it
put rom package on sdcard
flash it via recovery
btw, Updating IFWI takes a 10 or more minutes so wait and don't panic
I'll try that when I get home
MikeyLee said:
The only way I can flash is through the CMW recovery and everything I try to flash says cant install this package over newer build. But there's nothing on the device as far as I can tell. Also says E: Error in /external_sd status 7
Click to expand...
Click to collapse
Try and install twrp recovery through adb you can find how in the forum....if you can install it it will be much easier to flash a room.
Sent from my ASUS_Z00AD using Tapatalk
LiRi2000 said:
Try and install twrp recovery through adb you can find how in the forum....if you can install it it will be much easier to flash a room.
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
Nothing will flash through adb
meciu99 said:
Open ROM archive with app (for example WinRAR),
navigate to META-INF\com\google\android
unpack updater-script
open unpacked updater-script with any text editor (I use Notepad++)
remove first line with "(!less_than_int..."
save file
put unpacked file back in archive overwriting it
put rom package on sdcard
flash it via recovery
btw, Updating IFWI takes a 10 or more minutes so wait and don't panic
Click to expand...
Click to collapse
Still doesnt work. E: error in external sd blah blah blah, same as everything else.
@MikeyLee I had the same problem this morning, i spent a lot of time to fix this, i couldn't access the recovery, i tried to flash thetered recovery and do factory reset, flash again the rom, but nothing.
To fix the bootloop i just rebooted in fastboot mode, launced the adb from pc and format cache partition, thats all.
And the strange thing is that i didn't loose the data, Although I did the factory reset, that's mean maybe a corrupted cache partition that maked impossible to flash anything or do factory reset.
Sent from my ASUS_Z00AD using Tapatalk
Hank87 said:
@MikeyLee I had the same problem this morning, i spent a lot of time to fix this, i couldn't access the recovery, i tried to flash thetered recovery and do factory reset, flash again the rom, but nothing.
To fix the bootloop i just rebooted in fastboot mode, launced the adb from pc and format cache partition, thats all.
And the strange thing is that i didn't loose the data, Although I did the factory reset, that's mean maybe a corrupted cache partition that maked impossible to flash anything or do factory reset.
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
I've wiped cache multiple times. What steps did you go through?
Use the adb fastboot, command "fastboot erase cache"
Sent from my ASUS_Z00AD using Tapatalk
You need the stock recovery as the same version of the firmware you're sideloading, flash the recovery through fastboot.
I was finally able to restore everything. Stock recovery, OS etc… Here’s what I did.
Using ADB and following the procedures here http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556 and using fastboot, flashed the recovery.img, boot.img and droidboot.img in that order. That gave me stock recovery back. Then I sideloaded with ADB the latest FULL firmware from here https://www.asus.com/support/Download/39/1/0/13/Lk0Sg1Ulh0Ph49Hl/32/
It was the only version that did not error out in some form or another. Everything is back to normal.
I just rooted my HTC One M8 and was messing around with roms and when I tapped one my phone shut off and won't fully turn on. It just stayed at the loading screen. I went into fastboot and tried restoring to factory settings and all that and nothing worked. After awhile I relized the phone had no OS
Anyone have any ideas?
Help is much appreciated!
I know!!!
Erase fastboot cache on fastboot mode and flash custom roms on cwm recovery. I do it and working my htc one m8 eye. I think it will be working on your device. ?
nuddinf said:
I just rooted my HTC One M8 and was messing around with roms and when I tapped one my phone shut off and won't fully turn on. It just stayed at the loading screen. I went into fastboot and tried restoring to factory settings and all that and nothing worked. After awhile I relized the phone had no OS
Anyone have any ideas?
Help is much appreciated!
Click to expand...
Click to collapse
i assume you have a custom recovery ( TWRP )
boot to recovery connect your device with PC via USB it will show the storage transfer a custom rom in to your device ( sd card is recommended ) then tap the wipe button in recovery main menu check cash,dalvic,system and data then sweep to confirm
back to main menu , tap install choose your rom sweep to confirm and reboot it should work
Sent from my HTC One M8 using XDA Labs
ahmed.ismael said:
i assume you have a custom recovery ( TWRP )
boot to recovery connect your device with PC via USB it will show the storage transfer a custom rom in to your device ( sd card is recommended ) then tap the wipe button in recovery main menu check cash,dalvic,system and data then sweep to confirm
back to main menu , tap install choose your rom sweep to confirm and reboot it should work
Sent from my HTC One M8 using XDA Labs
Click to expand...
Click to collapse
i can't install rom at all,
this is the code
>>>formatting partitions
>>>mounting partitions
>>>cleaning process
>>>writing data and system
>>>creating toolbox symlinks
symlink: some symlinks failed
E: error executing updater binary in zip '/external_sd/filename'
error flashing zip '/filename
nuddinf said:
i can't install rom at all,
this is the code
>>>formatting partitions
>>>mounting partitions
>>>cleaning process
>>>writing data and system
>>>creating toolbox symlinks
symlink: some symlinks failed
E: error executing updater binary in zip '/external_sd/filename'
error flashing zip '/filename
Click to expand...
Click to collapse
try with another rom this log shows that the updater binary wrong or maybe missing
or maybe you have a wrong zip
are you sure this zip is a rom ?
may be you confused between rom and stock backup
can you post all the log
Sent from my HTC One M8 using XDA Labs
nuddinf said:
i can't install rom at all,
this is the code
>>>formatting partitions
>>>mounting partitions
>>>cleaning process
>>>writing data and system
>>>creating toolbox symlinks
symlink: some symlinks failed
E: error executing updater binary in zip '/external_sd/filename'
error flashing zip '/filename
Click to expand...
Click to collapse
You flashed the new ROM clean, right? With a full wipe? (data~dalvik~cache)
After you get that error select reboot, and in that menu select to reboot to recovery. Then flash the ROM.zip again without wiping.
When done, reboot to system.
After that you should be running your new ROM.
nuddinf said:
i can't install rom at all,
this is the code
>>>formatting partitions
>>>mounting partitions
>>>cleaning process
>>>writing data and system
>>>creating toolbox symlinks
symlink: some symlinks failed
E: error executing updater binary in zip '/external_sd/filename'
error flashing zip '/filename
Click to expand...
Click to collapse
Not enough info.
Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
What version TWRP?
Did you try more than one ROM? What ROMs did you try?
Did you do a default wipe in TWRP, before flashing?
I recently unlocked my bootloader after waiting for 1440 hours. I am/was currently on MIUI 10.0.1.0 but wanted to install a custom rom like lineage 15.1. I installed Red Wolf TWRP and then tried to install the rom. I went to Advanced Wipe section of the recovery and checked Dalvik, Cache, Data and System but not Vendor and Internal Storage. It wiped those partitions without any error. But after that i tried to install the rom but halfway through install it ended with "Update Process Ended with Error 7" and a line saying "Failed to Mount /system (Invalid Argument)" and changed the system partition size to zero. I had to repair it and flash MIUI back using fastboot.
I did this same process over and over with different recoveries ( RED WOLF, ORANGE WOLF and even official TWRP) and different builds of lineage (rom zip was never corrupted) and even with ressurection remix but still failed and same thing happened again and again. Am I doing something wrong in the process? I didn't flash lazyflasher as I read in multiple threads that it is not necessary if flashing a custom rom. Please guide?
I hope it works for my English.
1- mount > select all > restart recovery
2- full wipe > install rom and gapps > format data
prospektus said:
I hope it works for my English.
1- mount > select all > restart recovery
2- full wipe > install rom and gapps > format data
Click to expand...
Click to collapse
Thanks for replying. You said full wipe. Should I include vendor as well or just regular (Dalvik, Cache, Data and System)?
thrustaxehandle said:
Thanks for replying. You said full wipe. Should I include vendor as well or just regular (Dalvik, Cache, Data and System)?
Click to expand...
Click to collapse
yes.. delete internal memory. rom board. format data.
thrustaxehandle said:
I recently unlocked my bootloader after waiting for 1440 hours. I am/was currently on MIUI 10.0.1.0 but wanted to install a custom rom like lineage 15.1. I installed Red Wolf TWRP and then tried to install the rom. I went to Advanced Wipe section of the recovery and checked Dalvik, Cache, Data and System but not Vendor and Internal Storage. It wiped those partitions without any error. But after that i tried to install the rom but halfway through install it ended with "Update Process Ended with Error 7" and a line saying "Failed to Mount /system (Invalid Argument)" and changed the system partition size to zero. I had to repair it and flash MIUI back using fastboot.
I did this same process over and over with different recoveries ( RED WOLF, ORANGE WOLF and even official TWRP) and different builds of lineage (rom zip was never corrupted) and even with ressurection remix but still failed and same thing happened again and again. Am I doing something wrong in the process? I didn't flash lazyflasher as I read in multiple threads that it is not necessary if flashing a custom rom. Please guide?
Click to expand...
Click to collapse
You need to upgrade to a higher version for twrp. 3.2.2
prospektus said:
yes.. delete internal memory. rom board. format data.
Click to expand...
Click to collapse
OK. I will try your method and will report back.
Update: I tried your method but still failed. Any other solution will be appreciated.
esiv129 said:
You need to upgrade to a higher version for twrp. 3.2.2
Click to expand...
Click to collapse
I'm already using TWRP version 3.2.3
thrustaxehandle said:
OK. I will try your method and will report back.
Update: I tried your method but still failed. Any other solution will be appreciated.
I'm already using TWRP version 3.2.3
Click to expand...
Click to collapse
try again unlock
prospektus said:
try again unlock
Click to expand...
Click to collapse
I again tried the process as follows:
Flashed MIUI 9.6.4.0 with MiFlash using clean and lock option.
Then I unlocked it again using miunlock.
Then I flashed RedWolf v28 beta recovery by booting it and flashing it from inside recovery.
This time I flashed lazyflasher and checked options disable dm-verity and force encrypt in recovery and installed magisk. It did it perfectly.
Then I went to Advanced Wipe Section of Wipe tab and checked all the option required like cache, dalvik, data, system and even vendor. It wiped it without any problems like always.
But here the same problem starts to arise: when I again tried to install lineage 15.1 (downloaded latest build this time too) it starts but after halfway through it says Updater process ended with Error 7
Cannot install sdcard/lineage-build date and version
and Unable to mount /system (invalid argument)
When i restart recovery system partition size changes to zero and I have to repair it by changing the file system option.
Currently now I'm on MIUI 9.6.4.0 with RedWolf recovery (options disable dm-verity and force encrypt are enabled) and lazyflasher and Magisk installed. I can use my phone when I flash MIUI 9 or 10 using but it not letting me to install any custom rom. I'm really frustrated.
thrustaxehandle said:
I again tried the process as follows:
Flashed MIUI 9.6.4.0 with MiFlash using clean and lock option.
Then I unlocked it again using miunlock.
Then I flashed RedWolf v28 beta recovery by booting it and flashing it from inside recovery.
This time I flashed lazyflasher and checked options disable dm-verity and force encrypt in recovery and installed magisk. It did it perfectly.
Then I went to Advanced Wipe Section of Wipe tab and checked all the option required like cache, dalvik, data, system and even vendor. It wiped it without any problems like always.
But here the same problem starts to arise: when I again tried to install lineage 15.1 (downloaded latest build this time too) it starts but after halfway through it says Updater process ended with Error 7
Cannot install sdcard/lineage-build date and version
and Unable to mount /system (invalid argument)
When i restart recovery system partition size changes to zero and I have to repair it by changing the file system option.
Currently now I'm on MIUI 9.6.4.0 with RedWolf recovery (options disable dm-verity and force encrypt are enabled) and lazyflasher and Magisk installed. I can use my phone when I flash MIUI 9 or 10 using but it not letting me to install any custom rom. I'm really frustrated.
Click to expand...
Click to collapse
When you get the mount error, come to the home page and get to the mount. speak enable all options enable all options. speak restart recovery restart recovery. make format data
Not sure if the link is forbidden? I can't tell you sorry. https://www.youtube.com/watch?v=dzrWkjOfndA&t=501s
I have read replies and everyone is sharing his bit of suggestions, here are mine
1. boot redwolf as FASTBOOT BOOT recovery.img - (if you arent already)
2. change file type of /data partition to-from (xFat to ext4) and wipe all partitions (internal storage can be skipped)
3. instead of linage15.1 same package, try downloading some other custom rom, i recomend DotOS2.5 or Crdroid4.6.2
4. uncheck enforce md5 bla bla while flashing zip.
i hope you will succeed