Hey guys, i have the new CWR on the fascinate... only problem is when i go to make a backup it says "failed to backup boot.img" and bombs out. Anyone else having this problem?
I did a ODIN to the deodexed EB01. didn't add a google account or anything. Shut down, manually entered CWR and it worked.
Rebooted, loaded all my data, rebooted into CWR to make a backup of EB01 w/data and got the error message. Nothing was flashed in between backups. All i did was run Titanium...
Anyone else?
I had the same issue, I couldn't flash any roms either. Only after I replaced the update.zip with the one from jt1134's fix, did i finally get mine to work (i extracted it from the zip and copied replaced the one on my sdcard). Haven't tried a backup, but restore worked. Huh ope this helps.
ya i was going to do that if needed, but i wanted to see if there was a fix for the current recovery before going backwards. I was able to do one backup as I stated, but then it bombs out. not sure what the deal is.
I see to many issues with 3.0. I am gonna stay with the 2.5.x version until I am forced to do otherwise.
gotsflat4love said:
I see to many issues with 3.0. I am gonna stay with the 2.5.x version until I am forced to do otherwise.
Click to expand...
Click to collapse
I.wish I had
3.0 uses edify scripts which is lacking for the fascinate
boostedjti said:
3.0 uses edify scripts which is lacking for the fascinate
Click to expand...
Click to collapse
Yes, but I don't think we need edify scripts just yet. Nor does it work even if it says that it does...
Hey guys...I had the same issue -- but followed this, and all is right with the world again.
G/L!
boostedjti said:
3.0 uses edify scripts which is lacking for the fascinate
Click to expand...
Click to collapse
It is now with superclean 2.7, i deleted the clockworkmod folder and reflashed
recovery from RM, backup works. I have'nt tried restore yet.
Fix permission still does'nt work.
Im was trying to fix permissions as well with the orange cwr but no go . im 0n 2.7 patch btw
billhilt said:
Im was trying to fix permissions as well with the orange cwr but no go . im 0n 2.7 patch btw
Click to expand...
Click to collapse
Since your on 2.7 you can do it from terminal emulator, just type su then fxpms
once its done type reboot.
Related
Hey all.
I've been trying to flash ShadowROM onto my eris (got the eris dl off their site), but everytime I try to flash it on it gives me "E:missing file: recovery/recovery-from-boot.p" and "E:Verification failed" and then aborts the installation.
So I then tried re-downloading the rom, but the same thing happened again.
Any ideas on what might be going on? I did all my wipes and everything so I'm not really sure what could be going on. Also I have been using Evil Eris for a while, if that makes any difference.
Thanks in advance for any advice.
EDIT: Also I'm currently on 2.1 so I'm not sure if theres anything I need to do to be able to put a 2.2 rom on my eris.
greekstallion said:
Hey all.
I've been trying to flash ShadowROM onto my eris (got the eris dl off their site), but everytime I try to flash it on it gives me "E:missing file: recovery/recovery-from-boot.p" and "E:Verification failed" and then aborts the installation.
So I then tried re-downloading the rom, but the same thing happened again.
Any ideas on what might be going on? I did all my wipes and everything so I'm not really sure what could be going on. Also I have been using Evil Eris for a while, if that makes any difference.
Thanks in advance for any advice.
Click to expand...
Click to collapse
At this time it doesn't work with Amon's recovery. It only will work if you use clockwork, which isn't recommended. I got it to work but I use a rom kitchen and replaced the boot-img.
Busphan said:
At this time it doesn't work with Amon's recovery. It only will work if you use clockwork, which isn't recommended. I got it to work but I use a rom kitchen and replaced the boot-img.
Click to expand...
Click to collapse
Ah I see, hrm I really wanted to give it a try too.
Out of curiosity, why isn't clockwork recommended?
greekstallion said:
Ah I see, hrm I really wanted to give it a try too.
Out of curiosity, why isn't clockwork recommended?
Click to expand...
Click to collapse
There have been a few reports of bricks from just flashing roms.
Busphan said:
At this time it doesn't work with Amon's recovery. It only will work if you use clockwork, which isn't recommended. I got it to work but I use a rom kitchen and replaced the boot-img.
Click to expand...
Click to collapse
You don't need to replace the boot.img....the rom just needs to be signed and it will flash fine amon's. Clockwork can load an unsigned rom but amons can't....
Conap said:
You don't need to replace the boot.img....the rom just needs to be signed and it will flash fine amon's. Clockwork can load an unsigned rom but amons can't....
Click to expand...
Click to collapse
Thanks for the info that would have been easier. I just replace it because of the error message.
**please ignore, sorry!**
Clockwork wont hurt your phone. Also when you go into to clockwork and flash clockwork recovery it will only temp use clockwork as a recovery just to install the rom. After that it will boot into amon.
"Clockwork won't hurt your phone" Boyyyyyyyyy I bet a lot of people with broken eris's would be glad to hear that!
Hungry Man said:
"Clockwork won't hurt your phone" Boyyyyyyyyy I bet a lot of people with broken eris's would be glad to hear that!
Click to expand...
Click to collapse
You running clockwork Hungry Man? I wasn't ever trying to stop anyone, I just wanted them to look into it themselves.
Conap said:
You don't need to replace the boot.img....the rom just needs to be signed and it will flash fine amon's. Clockwork can load an unsigned rom but amons can't....
Click to expand...
Click to collapse
Im not knew to the rooting and flashing thing when it comes to my eris, but i do have to ask for my knowledge: what do you mean by the rom needs to be signed?? thanks!!
duccicucci said:
Im not knew to the rooting and flashing thing when it comes to my eris, but i do have to ask for my knowledge: what do you mean by the rom needs to be signed?? thanks!!
Click to expand...
Click to collapse
He means that this rom will not work with amons recovery because it isn't signed. You can create a zip that isn't sign, meaning you never used a program that signs zips, but you can't flash a zip in amons unless it is signed. So if you just create a zip it probably won't work, but if you use an autosigner then you will be in buisness. I hope this helps, probably not because I have been drinking.
Just so there's full information in case someone finds this thread in the future.
There was a bug with using Clockwork Mod Recovery with the Eris. They squashed it, at least 2-3 months ago.
Besides, you don't have to get rid of amon in order to use clockwork. Just download ROM Manager from the Market and it will make it so that you can load clockwork from amon. Then you get all the advantages of ROM Manager and clockwork without any hassles.
Sent from my xtrSENSE Eris using XDA App
I'm having issues loading the rom, it keeps staying on the 3 skateboarding droids then it reboots back to the skateboarding droids whats going on?
johnny quest said:
I'm having issues loading the rom, it keeps staying on the 3 skateboarding droids then it reboots back to the skateboarding droids whats going on?
Click to expand...
Click to collapse
This seems to be a hit or miss build for the Eris. About 50% (guestimated) of Eris users are unable to boot with v0.2.x and there is no known reason why, even after viewing logcats.
I have dropped the entire desirec device configuration (a mix of kaos & conap) and have forked over a pure conap device config for v0.3.x to attempt to fix this issue. We won't know for sure until v0.3.0 finally releases to the masses. All my testers (even myself) are able to run v0.2.x just fine.
There is no ETA for v0.3.0 at this time.
I'm sorry if this is off topic but I need to ask. Were can you get themes for ShadowRom? Do you just use anything that is for cynogen? Is it best to use metamorph or and update.zip?
I flashed shadowrom using clockmod just fine.
Sent from Eris with Froyo
xtreme3737 said:
I'm sorry if this is off topic but I need to ask. Were can you get themes for ShadowRom? Do you just use anything that is for cynogen? Is it best to use metamorph or and update.zip?
Click to expand...
Click to collapse
We currently have zero themes for the eris. We rely on themers to provide ports, which none have done yet.
Guess I'm one of the lucky ones
billygalbreath said:
This seems to be a hit or miss build for the Eris. About 50% (guestimated) of Eris users are unable to boot with v0.2.x and there is no known reason why, even after viewing logcats.
I have dropped the entire desirec device configuration (a mix of kaos & conap) and have forked over a pure conap device config for v0.3.x to attempt to fix this issue. We won't know for sure until v0.3.0 finally releases to the masses. All my testers (even myself) are able to run v0.2.x just fine.
There is no ETA for v0.3.0 at this time.
Click to expand...
Click to collapse
I flashed this rom and it was slow and jittery and all around not good.
Sent from my ERIS using XDA App
So the current iterations of cwm seem to have trouble working reliably with the newer froyo ROMs, and koush's recovery (although seeming to work correctly) is quite broken. So......
please find below a new recovery package that should work for any ROM for the fascinate, mesmerize, or showcase.
This is a "red" cwm recovery, and it will work with both voodoo and non-voodoo installations.
cwm-recovery-ALL.zip can be flashed via any cwm recovery.
if you are using odin, then use the cwm-recovery-ALL odin (.tar) package.
updated 3/29 - thanks to GizmoDroid for help with fixing fix_permissions script and root permissions typo that screwed up nandroid restores
updated 3/30 - fixed 'umount' typo - actually *fixed* fix_permissions this time - fixed odin/heimdall recovery attachment
Thanks, I just installed it. I'd rather not have a broken clockwork mod.
thanks, will give this a try!
ok, so I flashed this in the old cwm and it does come up red, but also says CwM Voodoo Lagfix Recovery, is that right?
In what ways is the old cm broken with froyo? I haven't noticed any problems.
Thanks! Good to have a fully working recovery again.
renf said:
In what ways is the old cm broken with froyo? I haven't noticed any problems.
Click to expand...
Click to collapse
Yeah, I'd like to 2nd this question. I have DL30 and CW worked for me in setting that up. Granted, I haven't tried anything else after that, but I'd like to know too.
Well I've had weird things happen when flashing stuff (I was using the "new-cwm.zip") , seemed like data being written where it shouldn't be? Just flashing theme files or own stuff I want to add, and I've had the following stuff happen:
Nuked my radio, had an unknown baseband and calls would never work, fortunately Radio Odin fixed it.
Had some /data apps disappear. Had some /data/data disappear. On reboot had Setup Wizard pop-up, even though I still had my Google account registered.
Hoping this new clockwork is completely safe. I suspected that clockwork was responsible for my weird happenings, so data-wiped and haven't flashed anything, so far fine functioning.
Using this is it easy to flash back to a prior set up, for me it would be back to dj05 w superdark and voodoo5?
Ive been holding off on froyo bc I need wireless tether, preferably unreported tether. But I really want to play around and see what the fuss is about. Ive downloaded every dl30 rom, havent installed one fearing I cant go back easily
Sent from my SCH-I500 using XDA App
/data on the fascinate is on /dev/block/mmcblk0p1
koush's recovery mounts /data as mmcblk0p2 (THIS IS OUR /DATA/FOTA. THAT'S BAAADDD)
under most circumstances this does not matter , because recovery.rc mounts data CORRECTLY before cwm gets to it, but there are circumstances where /data can be unmounted and then remounted, in which case cwm is gonna mount mmcblk0p2. If things get written there, at best you've got a **** load of FC's to deal with. At worst, a dead radio.
I've pointed this out to koush before, but was met with a "half-response", and to date it not been addressed (except for the recoveries that I've posted)
installed. When I go to do a backup, it gives the messages below. Backup seems to run fine though
E: missing bitmap progress_empty (code -1)
E: missing bitmap progress_fill (code -1)
Click to expand...
Click to collapse
Thanks, jt.
Copied to sdcard, booted into recovery, ran the program, keep coming back to green, no red.
ETA: Interesting. If I go to recovery from ROM mgr and try to load from sdcard, it does nothing, but if (while in ROM Mgr) I load from SDcard, it works. Got the blue screen, ran update, red appeared.
I likewise get the error message mentioned previously, but got it at install. Backup seemed to ahve run fine.
Installed like a charm, thanks jt!
sent from my fascinating XDA App
jackmei2 said:
thanks, will give this a try!
ok, so I flashed this in the old cwm and it does come up red, but also says CwM Voodoo Lagfix Recovery, is that right?
Click to expand...
Click to collapse
Yes, that is correct. It says in the OP. But it may have been edited since the time you posted and my response, so I'll let it slide
thank you JT!!!!! I thought it was just me, Ive had to start over again with my data about 6 times now becuase of Clockwork either not restoring my backups or my phone freaking out once I restored the backup. Thanks again!!!
beenz said:
Yes, that is correct. It says in the OP. But it may have been edited since the time you posted and my response, so I'll let it slide
Click to expand...
Click to collapse
haha thanks... but he said it will be red and that it is not for voodoo, so that's what I wanted to double check since it does have the voodoo menus and all.
superchunkwii said:
Yeah, I'd like to 2nd this question. I have DL30 and CW worked for me in setting that up. Granted, I haven't tried anything else after that, but I'd like to know too.
Click to expand...
Click to collapse
Lets see:
Broken mass storage function.
Broken data mounting function.
Couldn't wipe properly because of the above.
adrynalyne said:
Lets see:
Broken mass storage function.
Broken data mounting function.
Couldn't wipe properly because of the above.
Click to expand...
Click to collapse
The couldn't wipe properly bit me once already. Glad to have a proper recovery.
Sent from my SCH-I500 using XDA App
Thanks very much for addressing this issue.
For a while, I felt like a fresh n00blet, wondering what I was doing wrong. I tried flashing versions of supposedly compatible cwm's in different ways, always coming to the mounting errors.
Other than the errors from the missing graphics, this one works error free.
Scared to mess with this since i haven't experienced any problems with my current cwm stuff from pre dl09... Might just go ahead and do this tomorrow. For some reason I feel more comfortable using the odin method, so I can do all this over my Super Clean 1.0 with Neon GT theme and not have to do any data wiping or anything first?
So this makes no sense and I think its a weird coincident but as soon as I flashed this my beta version of swype started the force close loop..
EDIT: so weird, I had to uninstall the installer and swype itself using titanium backup and then download the installer and install again (had to do it all twice). Seems to be working again now tho..
Superclean 0.7.. aka Froyo.. Thanks devs!
I've always had horrible timing with things. I finally got the guts to root and get SuperClean 2.8 onto my phone, and the next day 2.9 is out. Awesome. XD
Anyways, for the question. How do I go about flashing 2.9 over my current 2.8? Do I do it through ODIN, or can I put it on my SD card and install updates through recovery? And I know there was an issue with flashing 2.8 straight over 2.7, does anyone know if there's a similar problem with this one? A step-by-step would be great, but if not then pointing me in the right direction would be awesome.
I flashed 2.9 over 2.8 through the recovery, no problem. No wiping or anything...it did get rid of some other things I had flashed but I simply went back into recovery and re-flashed all my stuff like the MIUI music app and Windows Phone notifications, etc.
Everything should be fine.
Just download the zip from the thread, boot into recovery, and choose install zip from SD card.
Oh and be prepared to be freaked out when your phone starts talking to you on its first boot.
I flashed 2.9 over 2.8 through the recovery, no problems to report so far. I didnt wipe data but i did wipe cache 3 times and davlik 3 times before i flashed SC2.9 zip.
Might not have to do that but so far i have followed this rule that i was told a few weeks back and so far no issues.
Will it still say "install update.zip", or should it say the actual name of the SC2.9 zip file? Because mine says update.zip, so I'm assuming something is missing >.>
Also, I'm not seeing where to wipe dalvik cache...
To install SC 2.9 you just need to place it on your sd card. Boot into recovery (wipe cache) and install zip from sd.
To wipe dalvik cache you need to go into the advanced setting in recovery.
Sent from my SCH-I500 using XDA App
First, are you running voodoo or non-voodoo? Will you be flashing voodoo over voodoo, over nv or nv over voodoo? Makes a difference.
im trying to flash in rom manager and its saying that cwm 3.0 is not supported for updating or something like that. anyone else have that problem?? or am i just doing something stupid
cwm 3 does not support what you are trying to do. Need to get the old red for all on there. Let me look for a link.
ETA: Here you go: http://forum.xda-developers.com/showthread.php?t=942021
thank you thank you. worked great. let me tell you how fun it is having to use a 7 year old pc to odin... there needs to be a mac version
dklemp said:
thank you thank you. worked great. let me tell you how fun it is having to use a 7 year old pc to odin... there needs to be a mac version
Click to expand...
Click to collapse
you are a lucky man or smart man
you asked before you jumped
Birgertime has done a great job getting EDT ROMs available via Rom Manager (I may have bugged him a couple of times). I was a bit shocked when I was reading the thread and saw people were having issues when they updated using Rom Manager. I think the consensus was that Rom Manager was not properly wiping.
This is what I did:
I was on Trigger 2.9.3 *I try every ROM and I just felt like being old school.
I opened Rom Manager and downloaded the latest Trigger 3.2,
I used the KB1 Modem, KB5 kernel, I selected a few of the apps I wanted (bloater, titanium, maybe a couple others)
I told Rom Manger to wipe and do a backup by clicking the two boxes.
Once the download was completed I proceeded.
It went into CWR and it did a backup... immediately it did a wipe (it showed the steps in CWR like normal)... and then it flashed the ROM and it rebooted perfectly. I have had NO issues with the ROM. It's perfect in my opinion.
What I want to know, for those who had issues... what was different?
Did you get rebooted into the red voodoo recovery (I was at the normal CWR)? I don't understand how it can work perfectly for me, and not others. I would like to know exactly what went wrong so we can go to @koush and try and get both Rom Manager and Clockwork Recovery working better for us.
Between this, Fix Permissions, Partitions F'ing people, stats not working (for the dev's) I think our phone needs this amazing app to be better, and I know koush can do it.
** If there are other things wrong with Rom Manager/CWR, please post... it would be nice to have a list of things to work on.
I can put up a test version on rom manager. The current Trigger 3.2 up there will wipe regardless of what you tell ROM manager.
PS: who rated it 1 star?
birgertime said:
PS: who rated it 1 star?
Click to expand...
Click to collapse
Team Whiskey
EDIT, were you going to fix the prop so it showed 3.2, not 3.1? =)
Im confused. You said you used CWR to wipe and flash the ROM. What exactly did you use ROM Manager for?
s15274n said:
Team Whiskey
EDIT, were you going to fix the prop so it showed 3.2, not 3.1? =)
Click to expand...
Click to collapse
I think I did when I uploaded the vvm fixed version
androidmonkey said:
Im confused. You said you used CWR to wipe and flash the ROM. What exactly did you use ROM Manager for?
Click to expand...
Click to collapse
To download it
Sent from my SGH-T959 using XDA App
duboi97 said:
To download it
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Ah, ok. I dont see why downloading it with RomManager would make a difference, unless its not completely downloading. The safest is like birgertime says in the Trigger thread, download on PC and check Hash.
androidmonkey said:
Ah, ok. I dont see why downloading it with RomManager would make a difference, unless its not completely downloading. The safest is like birgertime says in the Trigger thread, download on PC and check Hash.
Click to expand...
Click to collapse
Rom Manager is the most convenient way to do this. it also checks the MD5 before it flashes the ROM. Trust me when I say I know the process...
I just want to know from those who had issues with using Rom Manager to download/wipe/flash, what went wrong?
I flashed it using Rom manager.
I chose KB5 modem and KB5 Kernel.
along with things like Bloater and swype.
it rebooted into red recovery and seemed to go fine from there.
when it first booted up it seemed ok at first, I let it sit for a while like usual.
and then rom manager force closed.
from there it was just force close after force close.
So I rebooted back into recovery and wiped data and dalvik.
then I rebooted.
and everything works just fine, with the exception of it never installed any of the extras I chose (swype,Bloater, etc...)
but I had those in titanium backup just in case anyways so it wasn't a big deal.
Its been running beautifully ever since.
Pretty much same thing happened to me, it went to red recovery and seemed to flash just fine. then when it rebooted i kept getting force closes everywhere. rebooted to clear cahce, dalvik, and fix permissions and has been fine ever since. it didnt wipe my apps which i found a bit odd
Alright, so as I expected... it sounds like it was
THE RED VOODOO RECOVERY AS THE PROBLEM.
Anyone able to prove that wrong?
I mean, it makes sense, it's not the recovery Rom Manager expects to see.
So, how do we fix it? This would not be koush now, I do not think.
Where did the red voodoo recovery initiate? I remember it just showed up one day. was it supercurio?
Hey guys.
Using Samsung Galaxy S Froyo 2.2.1 I9000
Was installing CM7 today through CWM in Recovery Mode, at first it wouldn't work, threw me an error about signature verification, found it was because of 3e verification on zip files, so flashed the kernel with Odin to 2e.
After installing the kernel, ran the CM7 again and it ran fine, followed the instructions, wiped before installing CM7. The install looked like it ran fine, phone rebooted no problem, but it came back to a wiped Froyo still, didn't load CyanogenMod at all.
Anyway, there's no GMail app, and only Market, and Market wont let me add a Google account even if I say yes to the prompt. Looked round the SGS forums, didn't see anything like this.
I'm guessing I did something wrong, help someone?
Belahzur said:
it came back to a wiped Froyo still, didn't load CyanogenMod at all.
Click to expand...
Click to collapse
What do you mean by this?
Theonew said:
What do you mean by this?
Click to expand...
Click to collapse
I can only describe it as once I got to the step of rebooting the phone, it didn't load CyanogenMod, I was expecting the CM animation but I got my normal Froyo screen, does that make sense?
Probably a bad download. Delete the download and do it again. But just a word of advice...ROM's come with kernels, so if you flash a kernel first and then a ROM, you are going to lose the first one you flashed.
Thanks lowandbehold, one problem though.
I wiped the phone following the instructions, so I don't have ROM Manager anymore and can't open the Market, it asks me if I want to sign in with a Google account, I hit yes and nothing happens.
Ideas?
Sorry for double post, looks like I made some progress possibly.
Got the CM7 animation on boot, but doesn't go any further.
Got Clockworkmod recovery up though, flashed speedmod kernel, and CM7 initial kernel through ODIN.
Now in recovery mode when I go to install "update-cm-7.1.0-GalaxyS-signed.zip" I get an error about assert failed, error in the zip, status 7 and aborts.
Did you make a nandroid backup of the stock ROM before you flashed? If so, try to revert back to that. If you didnt make a backup, do a full wipe...wipe data/factory reset, wipe cache, and go into advanced and wipe the davlik cache. Then go to install zip from SD Card and select the CM7 zip. You should also check the md5 sum of the zip file to see if it matches up to make sure the download was good. You will be able to figure something out, as long as you can get into recovery and not getting crazy cache errors your phone should be 100% recoverable. Maybe even try something that is not CM7...just keep at it.
---------- Post added at 12:13 PM ---------- Previous post was at 12:11 PM ----------
Also, standby on the kernel for now. Get CM7 up and running on the kernel it provides you with and then make a backup in CWM. Then you can try to change the kernel...if you have issues then you can just go to your CM7 backup.
Would the backup be a recovery-update.zip file in the \clockwordmod folder?
Belahzur said:
Would the backup be a recovery-update.zip file in the \clockwordmod folder?
Click to expand...
Click to collapse
No, it's in recovery/backup on the clockword recovery screen.. personally, I like Amon Recovery a lot better than CM. Clockwork doesn't wipe the cache as well good luck! Hope you get it working
Sent from my Evo 4G using Tapatalk.
kendallc123 said:
Clockwork doesn't wipe the cache as well
Click to expand...
Click to collapse
Fixed your spelling (bold). Anyways, do you have proof of this?
Theonew said:
Fixed your spelling (bold). Anyways, do you have proof of this?
Click to expand...
Click to collapse
Thanks haha, went back and fixed it too. I don't have solid facts about it, but I have read in multiple threads that
1) People love Clockwork
2) People say Clockwork doesn't wipe the Dalvik cache thoroughly and sometimes causes boot loops (I've never had one)
I have had some problems with Clockwork personally. But, this is just my opinion. Also, Clockwork doesn't recognize some zips that I try to flash while Amon does. Anyway, it's all your opinion, whatever feels better to you.