Database Users

Troubles with Rom Manager and Flashing

I am having a lot of issues with Rom manager. Whenever I create a backup and try to back it up it refuses to work. It acts like it worked. But when I try to restore to that backup it says MD5 mismatch. I am currently running a froyo leedroid rom. I have tried to flash over to a GB Leedroid rom and a Coredroid rom. Neither of them work.
It says finding update package
opening update package
can't open file bad.
I am seriously annoyed with rom manager WTF is the point in creating a damn backup if I can't restore it at a later point?

Now my sdcard will not mount says its is mounted as read only and it wont do a damn thing now...

Bump wondering how to check an MD5. Still wondering what is up with Rom manager. Silly question but am I having troubles because I bought a different memory card for the phone? I did a partition and wiped it but just not sure.

http://www.softpedia.com/get/System/File-Management/MD5-Checker.shtml
use that to check the MD5. Obviously something getting corrupt along the way. I cant imagine its the memory card but Im not 100%. Hopefully someone with more knowledge than me will pop along shortly.

berserkerx87 said:
I am having a lot of issues with Rom manager. Whenever I create a backup and try to back it up it refuses to work. It acts like it worked. But when I try to restore to that backup it says MD5 mismatch. I am currently running a froyo leedroid rom. I have tried to flash over to a GB Leedroid rom and a Coredroid rom. Neither of them work.
It says finding update package
opening update package
can't open file bad.
I am seriously annoyed with rom manager WTF is the point in creating a damn backup if I can't restore it at a later point?
Click to expand...
Click to collapse
Hi I'm pretty new here so I'm may be wrong about this, but could it be a problem with Froyo and GB? It's like using office 2010 and 2007 version, may not be backward compatible. But I may be wrong, just a a guess on my part.

berserkerx87 said:
It says finding update package
opening update package
can't open file bad.
Click to expand...
Click to collapse
Looks to me like you've got a flaky SD card, certainly I have no problems creating and restoring backups although I am on CM7 but that shouldn't make a difference, first off though make sure youre running the lastest ROM Manager and Clockwork versions then try a different SD card.

Okay I am still having issues with Rom manager. I tried putting in a new sd card and it will not mount to the system. I hit mount and it just pops back up saying its ready to remove. I now can't reboot into recovery nor flash clockwork recovery. It said an error occurred while flashing your recovery.
Also I really don't like that I can't even take a picture or use my camera because it says it can't save to the SD card due to insufficient file permissions. Yes I have done fix permissions in rom manager. But it still wont work..

have you tried to do it directly in CWM?
if so, try to flash a newer CWM version (through fastboot, ROM Manager is known to cause some problems).

Hello iam also having problems but i am have my DHD freeze at the splash screen when trying to enter recovery, any ideas please.

berserkerx87 said:
Okay I am still having issues with Rom manager. I tried putting in a new sd card and it will not mount to the system. I hit mount and it just pops back up saying its ready to remove. I now can't reboot into recovery nor flash clockwork recovery. It said an error occurred while flashing your recovery.
Also I really don't like that I can't even take a picture or use my camera because it says it can't save to the SD card due to insufficient file permissions. Yes I have done fix permissions in rom manager. But it still wont work..
Click to expand...
Click to collapse
ROM manager wouldn't prevent mounting of a new SD card, thats got to be a hardware issue or an issue with your current ROM, try flashing either a different custom ROM or a stock ROM if your SD card woes continue it's a hardware issue, if not it's a ROM issue but either way I think we can safely rule out ROM manager.

sidon100uk said:
Hello iam also having problems but i am have my DHD freeze at the splash screen when trying to enter recovery, any ideas please.
Click to expand...
Click to collapse
Try reflashing Clockwork recovery, either from Fastboot or from ROM manager.

Tried using ROM Manager but got nowhere so i followed this post and it worked first time http://forum.xda-developers.com/showthread.php?t=1003723 , it was great for new guys like me.
But thank you for your help.

I figured out what the problem was. Even though I had formatted that new sd card it still wouldn't mount so I formatted it on the computer and now everything is fine. I don't use that other sd card anymore. I guess it was really just a bad sd card. So a word of advice to everyone that not all sd cards are created equal!
Thanks for all the help everyone!

Wise words there! I've been through 4 memory cards lol and each one broke. One after the other.

I use Rom Manager only to install CWM, and then I flashed all new rom by recovery from SD card.
I propose not to save a money on buying cheap card. It so important

Need Stock-i500-VZW-Kernel.tar.md5

Hosed my Fascinate by trying to flash a recovery through Odin -> The recovery also had a kernel in the file that I didn't realize. Phone attempts to boot then reboots into recovery. I would prefer not to do a factory reset until I try reflashing the right kernel.
I am aware of this thread that used to have the file I need, but evidently the guy has removed it from his Dropbox now. Does anyone have a copy they can throw up for me? I think I could use the recovery image, too, but it is a little bit easier to find so don't go to great lengths for the recovery.
Will reflashing the correct kernel even fix my problem? I haven't touched /system. Should all my stuff still be there when I get back in?

Skyroket said:
Hosed my Fascinate by trying to flash a recovery through Odin -> The recovery also had a kernel in the file that I didn't realize. Phone attempts to boot then reboots into recovery. I would prefer not to do a factory reset until I try reflashing the right kernel.
I am aware of this thread that used to have the file I need, but evidently the guy has removed it from his Dropbox now. Does anyone have a copy they can throw up for me? I think I could use the recovery image, too, but it is a little bit easier to find so don't go to great lengths for the recovery.
Will reflashing the correct kernel even fix my problem? I haven't touched /system. Should all my stuff still be there when I get back in?
Click to expand...
Click to collapse
If you have access to your sd card via windows, look for http://forum.xda-developers.com/showthread.php?t=1459905 on kernels. The stock is in post 1 at the bottom with the rest of the links. Download it, copy to your sd card and install it via recovery and it should work. If not, find droidstyle's guide, download the CWM 2.5 flash that in Odin, then install kernel.
Sent from my SCH-I500 using XDA App

Edit: Got it. Thanks!! It's booting up fully!!
Nothing below this line matters anymore, but I am leaving it for Google arrivals. The problem I list in this post was caused by excessive copying of the files. I first downloaded the file from the internet, copied it from Firefox downloads folder to my desktop, copied it up to my LAN server, copied it over to my Motorola Droid Bionic SD card, unmounted the SD card and put it into the Fascinate for installation.
The RIGHT way that worked was removing the network component. I just plugged the Bionic into the PC and mounted USB storage mode, copied files over, unplugged, let the SD card remount on the Bionic, manually unmount on the Bionic, remove the card and put it into the Fascinate.
Thanks for being patient with me. Your thread is obvious at the top of the forum but I ignored that method because it was flashing zips in recovery, which I couldn't get into at the time. I got the CWM 2.5 to work, and I did make a successful nandroid backup (will a factory reset restore the kernel, now that I have a backup?).
I did try to flash both versions of that stock kernel kernel-eh03-GB.zip and kernel-eh03-GB_signed.zip and get the same error on both. I even tried with a different SD card:
-- Installing: SDCARD:kernel-eh03-GB.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/kernel-eh03-GB.zip
(bad)
Installation aborted.​
I've tried downloading the files again, too. I wonder if it's worth noting that I did previously try to mount the SD card to Windows from CWM. It mounted, but when I tried to copy the file over, Windows told me the media was write-protected. WTF? Haven't seen that since floppies.
I think I'm going to call it a night and if I don't hear anything else on this in the morning I'll just do a factory reset and see if that restores the kernel. Then I can reinstall CWM and restore my backup. *long sigh*
Thanks again, man.

Skyroket said:
Thanks for being patient with me. Your thread is obvious at the top of the forum but I ignored that method because it was flashing zips in recovery, which I couldn't get into at the time. I got the CWM 2.5 to work, and I did make a successful nandroid backup (will a factory reset restore the kernel, now that I have a backup?).
I did try to flash both versions of that stock kernel kernel-eh03-GB.zip and kernel-eh03-GB_signed.zip and get the same error on both. I even tried with a different SD card:
-- Installing: SDCARD:kernel-eh03-GB.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/kernel-eh03-GB.zip
(bad)
Installation aborted.​
I've tried downloading the files again, too. I wonder if it's worth noting that I did previously try to mount the SD card in CWM. It mounted, but when I tried to copy the file over, Windows told me the media was write-protected. WTF? Haven't seen that since floppies.
I think I'm going to call it a night and if I don't hear anything else on this in the morning I'll just do a factory reset and see if that restores the kernel. Then I can reinstall CWM and restore my backup. *long sigh*
Thanks again, man.
Click to expand...
Click to collapse
Thats alright, dont worry about it man. Yeah it does sound like you need a factory reset. your phone isnt accepting the download. for ****s and giggles tho, try not using CWM to put the file onto your SD card, and plug it directly into your computer and redownload and transfer that way and see if it takes, if not then you'll definatly have to factory reset. Go here http://forum.xda-developers.com/showthread.php?t=1238070 Follow section 4 to return to stock. That should fix it.

Please note my previous edit. Thanks, again!

Skyroket said:
Please note my previous edit. Thanks, again!
Click to expand...
Click to collapse
Lol didn't see that till after I clicked reply. No problem. Glad you got it working bro
Sent from my SCH-I500 using XDA App

Possisbly bricked Defy?

Yesterday I flashed Wajks latest WIUI and I noticed that CWM didn't work properly when I was going to flash jellyx kernel.
I got an error message saying something like this: "E: recovery can't mount /cache/recovery", when trying to perform any actions in CWM.
So I thought my SD card was the problem. But the error remained after I formatted my SD Card. So I got kind of stuck. My rom didn't work any good and I couldn't flash/wipe anything. So I flashed the sbf for my phone (Nordic) and now my phone is in a bootloop. I've tried to reflash sbf but I'm still getting the bootloop.
Any help would be highly appreciated.
EDIT: Managed to fix it.

TheBrutalLicker said:
Yesterday I flashed Wajks latest WIUI and I noticed that CWM didn't work properly when I was going to flash jellyx kernel.
I got an error message saying something like this: "E: recovery can't mount /cache/recovery", when trying to perform any actions in CWM.
So I thought my SD card was the problem. But the error remained after I formatted my SD Card. So I got kind of stuck. My rom didn't work any good and I couldn't flash/wipe anything. So I flashed the sbf for my phone (Nordic) and now my phone is in a bootloop. I've tried to reflash sbf but I'm still getting the bootloop.
Any help would be highly appreciated.
EDIT: Managed to fix it.
Click to expand...
Click to collapse
So what did you do to actually fix it? I've been trying to figure out how to get out of a bootloop for 2 days now and haven't found any concise info to help yet. Most responses are with using Odin but I'm on mac so have been trying to use Heimdall but every time I try to load the .tar.md5 file it gives me and error "Tar header contained invalid file size". I've downloaded the fil multiple times thinking it may have gotten corrupt but still the same thing. Tried other files just to make sure and same thing too. :crying:
Samsung Galaxy S s7562

HT6120 said:
So what did you do to actually fix it? I've been trying to figure out how to get out of a bootloop for 2 days now and haven't found any concise info to help yet. Most responses are with using Odin but I'm on mac so have been trying to use Heimdall but every time I try to load the .tar.md5 file it gives me and error "Tar header contained invalid file size". I've downloaded the fil multiple times thinking it may have gotten corrupt but still the same thing. Tried other files just to make sure and same thing too. :crying:
Samsung Galaxy S s7562
Click to expand...
Click to collapse
My friend this is Motorola Defy forum.
Please post your question in your device forum as you may not get any help in here.
I don't want a Tapatalk sig!

I had the same problem. before you do anything in cwm, try to mount the data and sdcard first.
Sent from my MB526 using xda app-developers app

willai was right. Some older cwm does the automatic mount but recent cwm does not, and you need to manually mount it..
Sent from my awesome Defy: JB 4.1.2 - XDA premium

[Q] [q] aborted installs

Why some ROMs work and some fail to install and abort ? I've redownloaded several times and still get the aborted install . I've searched and did all the trouble shooting that the threads I've found had but without any luck .
Any advice would be great thanks .

What is the fail message? Are the failed rom installs stock roms, aosp or both?

Both type , it says installation failed , aborting install and shows the dead android in cwm . some ROMs just install with no problem.
So far , shostock didn't , bean stalk, revolt, clean, and a couple others .
Ones that work is cm10 nightly, slim, task, mint, PAC, and maybe another one or two .

Bigtjmc said:
Both type , it says installation failed , aborting install and shows the dead android in cwm . some ROMs just install with no problem.
So far , shostock didn't , bean stalk, revolt, clean, and a couple others .
Ones that work is cm10 nightly, slim, task, mint, PAC, and maybe another one or two .
Click to expand...
Click to collapse
Check the md5 of the downloaded file to make sure it was a good download
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

jd1639 said:
Check the md5 of the downloaded file to make sure it was a good download
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Will do , but how do I check the md5 ? I'm Google n it now, didn't know I could check a download md5 .

Did you have these same issues in twrp? It appears you're having problems flashing stock roms.

Yeah it was doing it too , I'm trying to check some of the files but I'm not sure what I'm doing yet still going at it now , I also just re downloaded the clean rom and still fails

Bigtjmc said:
Will do , but how do I check the md5 ? I'm Google n it now, didn't know I could check a download md5 .
Click to expand...
Click to collapse
I actually also experience a rather shaky flashing experience, both with CWM and the TeamWin openrecovery. What I find tends to work is to format /system (it seems that the system partition fails to format or something), possibly also rebooting afterwords. There is nothing wrong with the file, but on occasion it just fails to flash, often with a reference to "could not mount /system" or something of that sort.
Using a PC to sideload the rom has also been very helpful if it fails multiple times, but don't ask me why.
/R

Bigtjmc said:
Will do , but how do I check the md5 ? I'm Google n it now, didn't know I could check a download md5 .
Click to expand...
Click to collapse
You can check md5 with a file explore like ES File Explorer:
Find rom on your phone and longpress on it and go to properties. Usually it will say something like Show Checksum, then select md5
You can also use adb:
cd to your adb folder and type md5, then a space
drag your rom from your pc download folder or where ever it is to the space to right of md5. hit enter

What carrier are you with? It would matter, because if you are trying to flash, a loki'ed rom on a unlocked bootloader, I have seen that message also.

TheAxman said:
What carrier are you with? It would matter, because if you are trying to flash, a loki'ed rom on a unlocked bootloader, I have seen that message also.
Click to expand...
Click to collapse
Mine is att , I've downloaded them a bunch and still get the aborted when I check the md5 is passed. I kinda just gave up and stuck with one tyat works for me . thanks for the adivse everyone.

You could also try another recovery. I have seen that issue in the past also.

[Q] CivatoROM - Problems

Hello, i have to post here ´cause no rights to write in development forum.
http://forum.xda-developers.com/showpost.php?p=49492813
Today i tried to flash FlexKat 6.3 over my 6.1 and CWM gave me error. Hash-Code is right and i tried to flash from sd and from internal memory (sd is exfat, was not sure if that would be a problem, was not up to 6.1)
How can i find out if the rom is damaged or what to do?
And in the past days i have serious problems to connect via USB. Am i the only one and my usb is going to die? At the moment my note isnt connected at USB3 and at USB2 i get an error when i try to write date, on internal and on external sd.
Any suggestions?

SirTurbo said:
Hello, i have to post here ´cause no rights to write in development forum.
http://forum.xda-developers.com/showpost.php?p=49492813
Today i tried to flash FlexKat 6.3 over my 6.1 and CWM gave me error. Hash-Code is right and i tried to flash from sd and from internal memory (sd is exfat, was not sure if that would be a problem, was not up to 6.1)
How can i find out if the rom is damaged or what to do?
And in the past days i have serious problems to connect via USB. Am i the only one and my usb is going to die? At the moment my note isnt connected at USB3 and at USB2 i get an error when i try to write date, on internal and on external sd.
Any suggestions?
Click to expand...
Click to collapse
Coming from cwm always requires a clean flash not dirty flash

meawww said:
Coming from cwm always requires a clean flash not dirty flash
Click to expand...
Click to collapse
Öhm? I always flashed newer versions by cwm dirty (only caches wiped). All the years
And i am just bootin a 6.2 flashed dirty over the 6.1 - only the 6.3 gives error. And this error is not because of dirty or not - that MAY be at the USB-Problem, but error at flashing ignores if wiped or not, just writes to a partition that is clean or not. W/o wipe there may be old files causing problems, but in my case there is flashed nothing, just opening romfile seems to fail.
Edit: to makle clear, maybe i used the wrong term? cwm in this case is the custom recovery.

SirTurbo said:
Öhm? I always flashed newer versions by cwm dirty (only caches wiped). All the years
And i am just bootin a 6.2 flashed dirty over the 6.1 - only the 6.3 gives error. And this error is not because of dirty or not - that MAY be at the USB-Problem, but error at flashing ignores if wiped or not, just writes to a partition that is clean or not. W/o wipe there may be old files causing problems, but in my case there is flashed nothing, just opening romfile seems to fail.
Edit: to makle clear, maybe i used the wrong term? cwm in this case is the custom recovery.
Click to expand...
Click to collapse
Ohhh recovery thought was the firmware well it can be corrupted file during download or transfer check the md5 if its all good then transfer

meawww said:
Ohhh recovery thought was the firmware well it can be corrupted file during download or transfer check the md5 if its all good then transfer
Click to expand...
Click to collapse
one of my customers used to say "easy things i can do on my own"*G
In startpost i wrote: "Hash-Code is right and i tried to flash from sd and from internal memory (sd is exfat, was not sure if that would be a problem, was not up to 6.1)" - hashcode/md5 was one of my first thoughts. But - no...
But thanks
Edit: ok, md5 seems to be wrong... "my" md5 was identical to the one on AndroidFileHost. But "now" i see a new hash there... Not the hash, the file on AFHJ appears as it has been corrupt.