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

[Q] Error in CACHE:recovery/log

Lets make this easy:
-Tried to install CyanogenMod on my rooted Desire using the ROM Mananger.
-Installed it but it got into a loop at the CyanogenMod boot logo
-Searched around and found out that you had to go into recovery and try to reflash there
-Every time I go into ClockworkMod Recovery, there's a message "E:Error in CACHE:recovery/log (No space left on device)"
-Tried to wipe data/factory reset
-Got a black screen
(It seems that all the options give me a black screen and the only way I could solve that is to remove the battery)
I was told to reflash the recovery, but how would I go about doing that?

Pleas don't tell me you also try to confirm actions in recovery with the power button. Use the trackpad/optical joystick instead, the reason the screen turns black is because you actually turn it off(simple press of the power button should fix it and not pulling the battery). Also make sure in recovery you wipe data/factory-reset, cache and dalvik cache(under advanced)

TheGhost1233 said:
Pleas don't tell me you also try to confirm actions in recovery with the power button. Use the trackpad/optical joystick instead, the reason the screen turns black is because you actually turn it off(simple press of the power button should fix it and not pulling the battery). Also make sure in recovery you wipe data/factory-reset, cache and dalvik cache(under advanced)
Click to expand...
Click to collapse
Oh Thank you soooo much. Thought I had to spend hours on this, but your comment saved the day!

[Q] Problem with ClockworkMod Recovery

Problem with ClockworkMod Recovery
I was trying to install MIUI ROM but after performing a data wipe I got an
E: unknown volme for path [sd/ext]
Back Menu Button Disabled
Davik Cache wiped
message.
I'm now not able to use any of the options in the first clockwork mod recovery screen even though I can freely move throughout them. Whenever I choose one the background remains but nothing happens.
Any ideas on how to fix this? I'm afraid to reboot since I have no ROM installed.

take the battery out, put it back in then power on holding the volume down button then get back in recovery wipe again then flash again

[Q] Root Help Please SM T210R

I have CWM installed on my Tab 7 and when I go to install the universal root that I copied and pasted into the external SD I get two messages saying in red
"failed to verify whole file signature"
and one saying in red
"failed file signature"
I downloaded the universal zipped root file twice and its the same thing over and over. I have USB de bugging on too. Any help would be greatly appreciated. I have been up all night and been at it for hours trying to fix this issue.

PMK19 said:
I have CWM installed on my Tab 7 and when I go to install the universal root that I copied and pasted into the external SD I get two messages saying in red
"failed to verify whole file signature"
and one saying in red
"failed file signature"
I downloaded the universal zipped root file twice and its the same thing over and over. I have USB de bugging on too. Any help would be greatly appreciated. I have been up all night and been at it for hours trying to fix this issue.
Click to expand...
Click to collapse
When you select Install zip in CWM, select Toggle signature Verification, then choose your zip.

Not an option
gr8nole said:
When you select Install zip in CWM, select Toggle signature Verification, then choose your zip.
Click to expand...
Click to collapse
Thank you for the timely response. Unfortunately I just noticed in the background in CWM that my droid man has a red triangle with ! point inside him. The options given to me are as follows...
Reboot system now
Apply update from ADB
Apply uopdate from Ext. Storage
Wipe data/factory reset
Wipe cache partition
Apply update from cache
Which of these options should I use if any and or should I flash CWM again on Odin in order to get the screen you are speaking about?
If I do need to flash again what are the correct steps to clear what CWM is already in place? Thank you again for all of your help. I am a noob that rooted my SIII a while back and obviously it is a little different with the Tab 7.0.

PMK19 said:
Thank you for the timely response. Unfortunately I just noticed in the background in CWM that my droid man has a red triangle with ! point inside him. The options given to me are as follows...
Reboot system now
Apply update from ADB
Apply uopdate from Ext. Storage
Wipe data/factory reset
Wipe cache partition
Apply update from cache
Which of these options should I use if any and or should I flash CWM again on Odin in order to get the screen you are speaking about?
If I do need to flash again what are the correct steps to clear what CWM is already in place? Thank you again for all of your help. I am a noob that rooted my SIII a while back and obviously it is a little different with the Tab 7.0.
Click to expand...
Click to collapse
Just try flashing CWM again and uncheck auto reboot in Odin.

gr8nole said:
Just try flashing CWM again and uncheck auto reboot in Odin.
Click to expand...
Click to collapse
Ok I did that and got a pass on Odin. Now my screen is still in Odin mode with a green droid in the middle and under that it says in white letters Downloading....Under that it says Do not turn off target!! in green letters. How do I properly restart? In CWM as normal? (Hold POWER, Volume UP, and the HOME button all at the same time. When you see the Samsung Logo, let go of the POWER button, but keep holding the Volume UP and HOME until you see the recovery screen). Thanks...

PMK19 said:
Ok I did that and got a pass on Odin. Now my screen is still in Odin mode with a green droid in the middle and under that it says in white letters Downloading....Under that it says Do not turn off target!! in green letters. How do I properly restart? In CWM as normal? (Hold POWER, Volume UP, and the HOME button all at the same time. When you see the Samsung Logo, let go of the POWER button, but keep holding the Volume UP and HOME until you see the recovery screen). Thanks...
Click to expand...
Click to collapse
Update...Just re read this
--Auto Reboot can be un-checked if CWM doesn't flash correctly on your device. Some have reported that un-checking Auto Reboot fixes this issue. If you un-check Auto Reboot, you will need to reboot the device yourself (refer back to step 10).
Trying now fingers crossed!!!

PMK19 said:
Update...Just re read this
--Auto Reboot can be un-checked if CWM doesn't flash correctly on your device. Some have reported that un-checking Auto Reboot fixes this issue. If you un-check Auto Reboot, you will need to reboot the device yourself (refer back to step 10).
Trying now fingers crossed!!!
Click to expand...
Click to collapse
Update....ROOTED!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!:good: Thanks for all of your help as well as the rest of the build team.

[Q] HELP! Bricked my P600!!

Guys
really need some help here. Stupidly i decided i wanted to try my hand at installing clean rom,.
Firstly -
1. i rooted the device, and then used titanium backup to freeze some knox apps.
2. I didnt bother to put the stock recovery back on as i wanted to install clean ROM.
3. I followed the instructions i found on here to a tee - as below. They all worked perfectly.
4. I went through the install screens on CLEAN ROM - that all worked fine.
5. It ended with a screen back to TWRP and i hit reboot.
6. Not the device just gets stuck at the glowing samsung logo.
7. I can get back into TWRP but i have no idea what to do next. I have tried rebooting from TWRP, both system and power, but no luck. The device powers down, and comes back up but remains stuck on the glowing samsung logo.
What can i do?
these were the instructions i followed. Any help much appreciated, and i will chuck a couple of quid towards someone that can help.
3.
Download latest CleanRom and copy it to your SD-Card
4. ODIN
- Run Odin as administrator
- untick -Auto Reboot-
- Click -PDA- (in latest version it's -AP-) and choose your TWRP version
- Now turn off your device and restart it by holding down Power+Volume Down. Proceed with Volume Up to enter DownloadMode
- now connect your device to your PC using USB
- Device drivers should get installed if not already done
- check the Message box in Odin. There should be an "Added!!"
- There should be nothing checked but F. Reset Time
- Press -Start-
- when finished there should be a "RES OK !!" in the Message box
- TRWP is now flashed to your device
4.1.
Now restart your device manually by holding down Power+Volume Up. As soon as you see the Samsung Logo, wait a second and release the Powerbutton but keep holding Volume Up until TWRP is loaded.
5. TWRP
In TRWP
- click Wipe
- advanced wipe and check:
Dalvik, Cache, Data, Internal Storage (should be enough), System
- do NOT tick external SD. You don't want to get it wiped.
- Swipe to Wipe
Now back to Mainmenu
- click Install
- choose your desired ROM
- Swipe to Confirm Flash
- Follow Rom's Installshield and you should be good
Have fun and good luck

If you can get back to TWRP, then wipe data , cache & dalvik, then re-flash clean rom again.
If problem still persists then flash a stock rom via odin.

still no joy
I can wipe cache, system, data, but when i try to include dalvik cache i get a "Failed". the message in the screen says E: unable to mount '/cache

rakeshm01 said:
I can wipe cache, system, data, but when i try to include dalvik cache i get a "Failed". the message in the screen says E: unable to mount '/cache
Click to expand...
Click to collapse
You shouldn`t wipe system . data , cache & dalvik was the requested options.
Now since you wiped system, your only choice is to download a stock firmware from sammobile, enter download mode power+volume down , then volume up, & flash via odin .

lsherif said:
You shouldn`t wipe system . data , cache & dalvik was the requested options.
Now since you wiped system, your only choice is to download a stock firmware from sammobile, enter download mode power+volume down , then volume up, & flash via odin .
Click to expand...
Click to collapse
Hi thanks all – i think the problem was the boot loop issue. I wiped cache, dalvik cache, system, and data, one by one, and then reinstalled clean rom and it seemed to push it through. Thanks for the support though!

Almost, if it powers on and you're even getting in to recovery, bricked is not the proper term.
Bricked = no power, dead beyond repair.
All you had was a software issue.

and if twrp does not find sd card ?
then what ?..