Develop Bugs

[Q] Rom Manager - Failed to Seek

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

problem after install zip

HI all super place this is would like a little help if possable
iv got a sony arc s can root and load in to recover mode but when i try to install any rom from zip it will do all the normal stuff then says reboot ..
after that it just sstays on the sony logo does not go no more no matter how long i leave it ... can you help me in this am i doing some thing wronge :fingers-crossed:

flash the supporting kernel
PLZ SPECIFY WHICH RO YOU HAVE INSTALLED
if you are using a custom rom then IT IS NECESSARY TO FLASH THE KERNEL FOR THE SAME!!!
Eg:- if using ics based rom the flash a kernel for ics, if using cynogenmod the flash the kernel for that..etc
also clear cache,wipe data and dalvik cache using CWM..
_______________________________________________________________________________________________
**IF YOU THINK I HELPED THEN SHOW IT BY PRESSING THE THANKS ICON**:good:

If you want to flash the custom kernel, you should unlock bootloader first.
If your bootloader is unlocked, first flash the custom kernel (ics/jb/gb) thru fastboot that supports the ROM you are installing.
After flashing the custom kernel, wipe user data, wipe cache partition, advanced-> wipe dalvik cache and flash the ROM. Reboot the phone.

hi thanks for your replys
im trying to install
Original Xperia T ICS Rom v5.0 for ARC/ARC-S based on (4.0.4) 587 [9th-Oct-2012]
http://forum.xda-developers.com/showthread.php?t=1746508
mybe a step im doing wronge im not shore follow it step by step
3.1- wipe factory date <<<< does not show this where is this or is it called soem thing els
3.2- wipe cache partition
3.3- wipe delvik cache
3.4- wipe system <<<< does not show this where is this or is it called soem thing els
i see
reboot otions
install zip from sd
apply /sd/update
factory reset
wipe cache partition
backup restore
mount storage
advanced
power off
in advance
reboot recovery
wipe dalvik cache
wipe battery stats
reboot error
key test
show log
partition sd card
fix permissions
that all that in recovery
?

Its in detail!!
THAT'S an ICS rom from xperia t
FROM that post it's clear(text copied from the post)
STEPS ARE QUITE CLEAR AND STRAIGHT FORWARD
How to install.... please do all step as i am describing
Step-1) Download & Flash the kernel From here available in downloads
Quote:
Step-2) Please download Xperia Arc-S 4.0.4_431 ftf pack from here only and flash it through flash tools , in Arc and arc-s both , FTF is available in downloads
Flash every thing from ftf pack just exclude two things
1. simlock.ta
2. Kernel.sin
do not flash these two things, after flash power up your phone and let it start completely, now copy rom zip into SD card , and reboot your device into recovery
Why you need to do this ???
It will give you 440-MB internal memory and 419-MB System Rom memory
If you already have these memories then you can skip this step
3) go into recovery and wipe these things
3.1- wipe factory date
3.2- wipe cache partition
3.3- wipe delvik cache
3.4- wipe system
4) now flash my rom after flash reboot your phone and wait for 60 seconds
5) Tick unknown source, then reboot it recovery again and flash the Xperia T lock-screen mod
6) reboot and enjoy do not wipe data after this for more info read recommendations
Click to expand...
Click to collapse
AGAIN FOR YOUR BETTER UNDERSTANDING
**YOUR BOOTLOADER MUST BE UNLOCKED AND YOU MUST HAVE THE KERNEL INSTALLED PROVIDED IN THAT POST
**YOU MUST install THOSE FTF files excluding (THIS STEP IS DONE IN ORDER TO INCREASE THE INTERNAL MEMORY CAUSE XPERIA T ROM REQUIRE A HIGHER VALUE OF INTERNEL MEMORY WHICH IS BY DEFAULT NOT PRESENT IN ARC/S)
1. simlock.ta
2. Kernel.sin
**NOW GO INTO RECOVERY
3.1- wipe factory date ==factory reset
3.2- wipe cache partition
3.3- wipe delvik cache
3.4- wipe system ==MOUNT and storage>format/system
**THEN install the rom (the zip file) via install zip from sdcard
then step 5,6
I THINK I MADE IT QUITE DESCRIPTIVE NOW AND YOU WOULD BE ABLE TO INSTALL THAT ROM
BTW YOU MUST POST THIS PROBLEM IN THAT THREAD ITSELF SO THAT OTHER PERSON WHO IS FACING THE SIMILAR PROBLEM OR HAVE OVER-COME THIS PROBLEM CAN HELP FOR SURE!!!
---------------------------------------------------------------------------------------------------------------------------------------------
**IF YOU THINK I HELPED THEN SHOW IT BY PRESSING THE THANKS ICON""IT'S FREE:good:

thanks m8 will try now let you know thanks again for your reply

m8 i cannot thank you any more it worked thank q again :good:

Need Urgent Help!! Not able to rectify status 7 error

Hi,
I am using Note GT-N7000.
I rooted it using PhilZ Touch 4 CWM Base Version: 6.0.3.0. After that I tried installing C-RoM-KK-v7.1-22014062-n7000.zip. But m getting status 7 error. I have also checked "updater-script" inside folder META_INF > COM > GOOGLE > ANDROID, everything seems fine in it.
Please help me out in installing Kitkat rom without status 7 error.
Thanks in advance.

wingriderr said:
Hi,
I am using Note GT-N7000.
I rooted it using PhilZ Touch 4 CWM Base Version: 6.0.3.0. After that I tried installing C-RoM-KK-v7.1-22014062-n7000.zip. But m getting status 7 error. I have also checked "updater-script" inside folder META_INF > COM > GOOGLE > ANDROID, everything seems fine in it.
Please help me out in installing Kitkat rom without status 7 error.
Thanks in advance.
Click to expand...
Click to collapse
did u wipe data/factory reset? did u wipe cache and dalvic cache? If u have, u should also go to advanced and format system...i had the same issue...when i did this the installation proceeded as it should...but first of all, backup ur system just in case...also, keep the original zip folder, do not erase the text from the 'update-script'...just keep it original and do as i say above...

fidel_cast0r said:
did u wipe data/factory reset? did u wipe cache and dalvic cache? If u have, u should also go to advanced and format system...i had the same issue...when i did this the installation proceeded as it should...but first of all, backup ur system just in case...also, keep the original zip folder, do not erase the text from the 'update-script'...just keep it original and do as i say above...
Click to expand...
Click to collapse
Thanks mate for the reply.
I had followed all the steps mentioned in your reply except ''format system'' option as I dont see this ''format system'' option inside ''Advanced''.
Original zip folder is kept as it is. Nothing has been erased from the 'update-script'. But still while installing zip (rom) I am getting this on my display:
_ _ Installing: /sdcard/omni-4.4.4-220140922-n7000-NIGHTLY.zip
Finding update package. . .
Opening update package. . .
Installing update. . .
Warning: No file_contextsset_metadata_recursive: some changes failed
E: Error in /sdcard/omni-4.4.4-220140922-n7000-NIGHTLY.zip
(Status 7)
Installation aborted.
I am really tired of seeing this message again and again. Whenever I start my phone PhilZ Touch 4 page appears with all thoes install zip, wipe data..etc etc options. :crying:
Please help me out.

Help "To start Android please enter password" for Xperia M C1905

Basically, as the title say, I have problem with it. Before that, I have a custom install (Archidroid 3.1.5), root and bootloader is unlocked. At one point, the phone hang....then I reboot it and that why I got the problem. Thus, I tried many ways to restore back my phone. I tried...
1. Try wipe data, cache, dalvik, system, factory reset, format data using TWRP - failed (except format data)
1. Try install back the custom ROM (ArchiDroid) - it said symlink: some symlinks failed
2. Try install another custom ROM (cm13) - it said error: 7
3. Try flash stock ROM ftf file using flashtool - it said Processing of kernel.sin finished with errors
Edit 1:
1. Try wipe data, cache, dalvik, system, factory reset, format data using TWRP
2. Try install back the custom ROM (ArchiDroid)
3. Try install another custom ROM (example: cm13)
4. Try flash stock ROM ftf file using flashtool
None of the above help. For 1, 2, and 3 I think is because the /data. It said "unable to mount /data {invalid argument}. As for flashtool, I try version 0.9.19.10 and 0.9.18.6 both got error about the process of kernel.sin finished with error. So, my phone only can do boot to recovery (TWRP), and normal boot (back to problem as in title).
Please help me :crying:

I have same problem. Try to flash/install anything at recovery ---> ( Failed to mount data ).
U 've done with that ?

Dickysuryanata said:
I have same problem. Try to flash/install anything at recovery ---> ( Failed to mount data ).
U 've done with that ?
Click to expand...
Click to collapse
mee to

Your phone gets Ebola now. It's now time to change the motherboard.

Cannot Install Any Custom Rom

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