Troubles with Rom Manager and Flashing - Desire HD General

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

Related

"Error...Run "nandroid-mobile.sh" via adb!"

ive been using nand backup since eris was rooted. I recently started having this error come up when trying to nand b/u and nand restore. i flashed the fresh rom 2.1 and then i ran into issues. got an error on
my screen:
"Error...Run "nandroid-mobile.sh" via adb!"
everything worked fine up until now.
And i dont think its the rom that did this.
lately, all the latest roms ive been using have been having shutdown issues, requiring battery pulls following shutdown. Im not sure if all the batterypulling broke my amon ra, but im stuck with having to reflash the rom when having issues with it. very time consuming, battery draining, and very annoying. anyone else having this issue or any suggestions??
Mime has done that too. I've noticed it when my battery was below 15%. Try connecting to a charger or let your battery charge a little bit.
After I did that I had no more problems.
iflip said:
ive been using nand backup since eris was rooted. I recently started having this error come up when trying to nand b/u and nand restore. i flashed the fresh rom 2.1 and then i ran into issues. got an error on
my screen:
"Error...Run "nandroid-mobile.sh" via adb!"
everything worked fine up until now.
And i dont think its the rom that did this.
lately, all the latest roms ive been using have been having shutdown issues, requiring battery pulls following shutdown. Im not sure if all the batterypulling broke my amon ra, but im stuck with having to reflash the rom when having issues with it. very time consuming, battery draining, and very annoying. anyone else having this issue or any suggestions??
Click to expand...
Click to collapse
yea its most likely because your battery is low, charge it a bit then restore
iflip said:
ive been using nand backup since eris was rooted. I recently started having this error come up when trying to nand b/u and nand restore. i flashed the fresh rom 2.1 and then i ran into issues. got an error on
my screen:
"Error...Run "nandroid-mobile.sh" via adb!"
everything worked fine up until now.
And i dont think its the rom that did this.
lately, all the latest roms ive been using have been having shutdown issues, requiring battery pulls following shutdown. Im not sure if all the batterypulling broke my amon ra, but im stuck with having to reflash the rom when having issues with it. very time consuming, battery draining, and very annoying. anyone else having this issue or any suggestions??
Click to expand...
Click to collapse
ya it usually does that with a low battery .....
only happened to me once ..... but a very wise man told me this was almost always the cause
ive been charged all day. still no luck.. :-(
iflip said:
ive been using nand backup since eris was rooted. I recently started having this error come up when trying to nand b/u and nand restore. i flashed the fresh rom 2.1 and then i ran into issues. got an error on
my screen:
"Error...Run "nandroid-mobile.sh" via adb!"
Click to expand...
Click to collapse
I think I had the "Error : run 'nandroid-mobile.sh restore' via adb!" problem before when trying to restore a rom in recovery, but i think it was because of renaming the folder inside the "nandroid" folder on the sd card.
i didnt rename anything
quick question what recovery are you using?
I had problems similar to this on CLOCKWORKMOD recovery, to the point where i couldn't flash or restore any nand. I even tried flashing root rom and that also failed. when It tried to write boot and the system in failed and then i had to replace my phone because it wouldn't even boot after trying to flash root rom.
using amon ra.
i think im gonna try to reinstall recovery img via adb. any requests to stop me go right ahead.
i tried reinstalling recoery img via adb and still nothing!!!! AARRGH!!!
Sounds lime my issue js rather unique. Doesnt seem like anyone else had this problem yet. Well i guess for now im .sh out of luck.
-------------------------------------
Sent via the XDA Tapatalk App
iflip said:
Sounds lime my issue js rather unique. Doesnt seem like anyone else had this problem yet. Well i guess for now im .sh out of luck.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
I had this problem when the memory on my sd card was almost full. I deleted a bunch of zip files and a bunch of the nand backups and it worked fine. I've also experienced the low power and the invalid rename issue too. hope this helps.
That sounds like a solution. Thx. i will trh to free up space on sd. Ive been pretty full for a while tho, but never encountered this msg.
-------------------------------------
Sent via the XDA Tapatalk App
nand restore error run nandoid mobile via adb
I just got this error and simply needed to have power plugged in to complete the restore. Hope this helps.
Well, there's two ways to go about solving this type of problem.
One would be to use the built in functionality of the Recovery menu system to copy the recovery log file (/cache/recovery/log) to your SD card and then - oh, I don't know, maybe look at it to see what error messages are in there? Really super-duper users could even just do a "adb shell cat /cache/recovery/log | more" with the recovery console still running, but that presumes a high level of skill (operating a space bar on the keyboard).
The other way would be to ask a bunch of strangers on the internet to speculate about what the problem might be.
I prefer the 2nd way; it's far less efficient, but much more entertaining. Hours of fun, really.
J/K. Have a look at Amon_RA's announcement post for the Eris, where he says:
Always check recovery.log before posting your issues!
bftb0
i am having the same exact problem with my nexus one. the error: run 'nandroid-mobile.sh restore' via adb. i am a new root user and this is my first time attempting to do any nand restores, and i get that error. is it possible i used the newer recorvery which is not compatible with cyanogen 5.0.7 ROM? i just followed all the links on the rooting guide and said to use all latest files.
my battery is 100% and my sd card has 2gb of free space. i'm really at a loss what to do. thanks.
Verify that there is a folder named nandroid in the root directory of your SDcard. If not, create one. I was having the exact same problem until I did that.
there is definitely a nandroid folder on my sdcard root drive, and inside that folder are 3 backup folders with associated files. i'm going nuts.
you can rename the back up files with names starting with "BDS-". You can't rename the folder directly under "nandroid" in your directory. if you do, you will get the "run mobile.sh" error. you will also get this error if your battery is low or you have no storage left. the folder directly under the "nandroid" folder it is your serial number. if you're having issues, just go to the "other" menu and select "send recovery.log to SD card." then go in and search the recovery.log file on your sdcard for "serialno=" right after that there will be a 12 character string of capital letters and numbers directly followed by lower case letters that are useless for this purpose. Create a folder with the same name as that string (capital letters and numbers only, no lower case) and place your previously renamed backups into that folder and voila! you'll be able to restore them.
My issue never got fixed, but I did try a different memory card, copied over my backups, and now they restore fine. And I did rename them to "stockROM" and they restore just fine. So the name does not matter.
I tried formatting the original memory card then copied all the contents back onto it, and still will not work with nand restores. It took me 5 hours to dump my card and reload it, so some files on that card must be screwing something up. Sucks cause now I'm stuck with this small card and with my music on it now It's full, so I have no room to do anything. Wish I could get my main card working with backups.

Problems preparing to flash ROM

My vibrant is running stock 2.2 Froyo. Lately, it dies silently and so frequently in sleep that I can't rely on it for every day usage. I've missed many important calls. So I am trying prepare my phone to flash another ROM. First, I got the phone rooted no problem at all.
Then the first problem I have is with the ROM manager. I purchased the Premium Version 3.0.1.3 and flashed the latest ClockworkMod Recovery 2.5.1.2. Upon rebooting into Recovery, there is, however, no Nandroid backup, just the normal menu shows up with
Samsung Recovery Utils -for BML-
.reboot now
.reinstall packages
.delete all user data
.delete cache data
.format internal sd card
I remove update.zip on the phone and on the sd card and retried and retried without success. Why don't I have Nandroid backup showing up to save the phone before flashing new ROM?
The second problem is with the Titanium Backup. I downloaded the free version and it works fine and could get root privilege without problem. Then I purchased the donated version and followed the instruction to uninstall the app and reinstall it to get the upgrade through the license file. The license file is read correctly and the upgrade version acknowledges that. However, Titanium Backup paid version now fails to get root privilege. I verify that other apps can get root without problem. I've searched all over yesterday and it seems that few people have the same problem getting root with the upgraded version, but no one has offered a solution.
So here I am paying but not able to backup the phone to start flashing anything. Could someone enlighten me about what I did wrong here?
Thank you.
For recovery, just select reinstall packages. Sometimes you have to do it twice.
For titanium backup, click the problems button to get the latest busybox.
You should be good after that.
Sent from my GT-I9000 using XDA Premium App
What offdutyninja808 said, also check your Superuser app, click Titanium and tell it to forget it if it's there.
We'll get you sorted out!
I have the same set-up and I have the same issue. I've selecting reinstall packages several times. Did not work. I tried different, methods: using Rom Manager and AIO Vibrant Toolbox. Didn't work. At first it said said it wasn't signed, and I four a fix for that. Now It loads and says replacing stock recovery with Clockwork... but boots back into the stock one. Is there anything else I can do?
birgertime said:
What offdutyninja808 said, also check your Superuser app, click Titanium and tell it to forget it if it's there.
We'll get you sorted out!
Click to expand...
Click to collapse
+1 Both Off duty and birgertime are correct. Most of the new roms will delete all things for you unless they say to do something particular (like some of the EDT roms) you should be ok, we are here to help if you run into further problems
If hitting "reinstall packages" don't take you to the clockwork recovery, also you can just reinstall the recovery thru rom manager.
Then once you reboot and if it don't take you to clockwork recovery, then hit reinstall packages again. Ya should get to it the second time.
I had this issue a lot when first rooted the phone and installed clockwork recovery.
Sometimes it will even boot halfway into stock recovery then quickly reboot itself into clockwork.
Also, just make sure that there is only ONE update.zip in there. So delete the update.zip using "my files" then open Rom Manager and choose install clockwork recovery. That way you are sure there is only one update.zip there then try the previous mentioned methods
Thanks for your advice. I still have problem with selecting "reinstall packages" in the Recovery menu. If I select that, it says:
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
This repeats if I keep selecting "reinstall packages" again. My SD card is still the original 2GB card that comes with the phone. It still has plenty of space.
Thanks again for helping
FWIW, I upgraded BusyBox and could solve the Titanium Backup problem. However, still can not do a nandroid backup as mentioned above, even with the donated version. So I abandoned my plan to flash another ROM and stay with the rooted stock.
However, what a difference it makes when I replace the 2GB SD card that came with the Vibrant with a 16GB SD card class 10. The unit comes up faster, the UI is no longer sluggish as before. I hope that this was the issue that caused my Vibrant to die in sleep. I need to phone for daily use and don't have a lot of time to muck around with it. Maybe next year when I have another phone to use as main phone, then I can take some risk to flash without nandroid backup. For now I hope that it no longer dies in sleep. Thanks for all your help.
Just a quick note to end this thread.
Since I have plenty of disk space on the internal memory, I removed the SD which I don't need and the phone seems to become reasonably fast responsive with rooted stock 2.2. It's now quite usable for me so I have no more need to flash it with another ROM. People who complain about slowness of their stock 2.2 ROM should try to remove the SD card first.
Thanks again for all your help.

sd-card

how do I un-partition a sd card? running a rom and was just showing b not telling me how much space i have left or anything. was not even telling me how much internal memory i had on phone
reformat it....
copy all your contents off the card..reformat and go from there..
sd card
crstfr said:
reformat it....
copy all your contents off the card..reformat and go from there..
Click to expand...
Click to collapse
ok i got that copied now it is sticking on splash screen. did a battery pull and still sticks on spash screen. did I ruin my phone.
Callie_evo said:
ok i got that copied now it is sticking on splash screen.
Click to expand...
Click to collapse
can you get to recovery?
try flashing a new rom?
i mean your not to borked.. it still somewhat booting!.. your not dead in the water yet
crstfr said:
can you get to recovery?
try flashing a new rom?
i mean your not to borked.. it still somewhat booting!.. your not dead in the water yet
Click to expand...
Click to collapse
yes i can get into recovery. I tried flashing synergy rom. would it be best to just run the ruu and redo the rooting process?
Reformatting is by far the best way. There is a remove sd partition selection in ClockWorkMod and Amon Ra recoverys,but ive never used them,bcuz i have no need to partition my sdcard because i always have 150mb,or more,free space,no matter which rom i use or what apps i add/install(original Evo 4G).Id simply copy the contents of your sdcard to your computer,then reformat the sdcard,and reinstall the content back to your sdcard.I dont suggest the remove sdcard partition method simply because ive never used it. Good luck.
thank ibcary we got that far now i'm just stuck on the splash screen. the reason for wanting to get rid of the partion is cause it was just saying b. not giving me any info on the card.
If u can get to recovery your doing good. Use Amon Ra if possible. CWMod doesnt always do a full wipe. id try going into recovery and perform a full wipe,wipe dalvik,wipe data,etc,etc...Then download a rom that u know works and is stable. I like MikGs Sense 2.1/3.0 roms,but which rom all depends on your device. Choose a rom thats well known to be a good,stable rom.Try flashing the newly downloaded rom from your sdcard thru recovery and if that doesnt work,then id try using a new/different sdcard. Sdcards dont last forever,and some are downright junk. As long as u can get to your bootloader theres still hope. Im sure your device is ok,but it could be a bad sdcard or a bad rom download. Thats why i recomended a new rom download,and if that doesnt work then try a new sdcard. Goodluck
ok. it was a new sd card that i partioned. am download a rom that I have used before and never had any problem with. but if this doesn't work should i just unroot and run the ruu and start over again?
how do i load the rom onto the sd card since it gets stuck at the splash screen??
Callie_evo said:
how do i load the rom onto the sd card since it gets stuck at the splash screen??
Click to expand...
Click to collapse
mount the SD card from recovery and then flash it in recovery.
Holsum said:
mount the SD card from recovery and then flash it in recovery.
Click to expand...
Click to collapse
thanks you Holsum will give it a try.
once you have root and busybox installed correctly theres not much unrooting and then rooting again will solve.Except to return your device to stock,and to unroot i usually flash the unrooted stock rom. U can try the Root Checker app from the Market just to make sure your rooted and have busybox installed correctly. However custom roms are already rooted and have busybox installed correctly. If its a new sdcard id still try another sdcard. Use an sdcard u know is good. I bought a few cheap sdcards that were 8GB class 10 becuz i got a great deal on them,10 for $110.but out of the 10,only 7 were even recognized by my Evo or my HP dv7 Netbook and worked.Also i highly doubt they are class 10,bcuz my SanDisk 16GB C10 sdcard is much faster,and older too. So just bcuz its new doesnt mean its good.If it still wont work after a fresh wipe using Amon Ra recovery,NOT ClockWork Mod recovery,and a fresh/newly downloaded rom flashed from a different sdcard using Amon Ra recovery to fully wipe,then flash the newly downloaded rom from the different sdcard to your device. That shud work,but if it doesnt u can try reinstalling or updating your recovery.
As usual im a little behind again with my post. Good luck
lbcary said:
once you have root and busybox installed correctly theres not much unrooting and then rooting again will solve.Except to return your device to stock,and to unroot i usually flash the unrooted stock rom. U can try the Root Checker app from the Market just to make sure your rooted and have busybox installed correctly. However custom roms are already rooted and have busybox installed correctly. If its a new sdcard id still try another sdcard. Use an sdcard u know is good. I bought a few cheap sdcards that were 8GB class 10 becuz i got a great deal on them,10 for $110.but out of the 10,only 7 were even recognized by my Evo or my HP dv7 Netbook and worked.Also i highly doubt they are class 10,bcuz my SanDisk 16GB C10 sdcard is much faster,and older too. So just bcuz its new doesnt mean its good.If it still wont work after a fresh wipe using Amon Ra recovery,NOT ClockWork Mod recovery,and a fresh/newly downloaded rom flashed from a different sdcard using Amon Ra recovery to fully wipe,then flash the newly downloaded rom from the different sdcard to your device. That shud work,but if it doesnt u can try reinstalling or updating your recovery.
As usual im a little behind again with my post. Good luck
Click to expand...
Click to collapse
oh k. will try the card that came with the phone then. I know that one worked great. just wanted more memory and I got it from walmart. so it maybe poop.
Callie_evo said:
oh k. will try the card that came with the phone then. I know that one worked great. just wanted more memory and I got it from walmart. so it maybe poop.
Click to expand...
Click to collapse
ok got the rom installed on sdcard and booted up. think i'm done flashing roms. that was scary. Thank you all for your help. I really do appreciate it.
Callie_evo
Callie_evo said:
oh k. will try the card that came with the phone then. I know that one worked great. just wanted more memory and I got it from walmart. so it maybe poop.
Click to expand...
Click to collapse
First: Did you partition all the card or only a certain amount ?
Second: Almost all the Custom recoveries have format card so do that.Then boot back in recovery and mount your card from recovery.
Third: Do not run RUU Period.
Fourth: Wipe all, cache, dalvik and all 2or3 times.
You wont get stuck on splash. since you wipe all give it a bit of time to check everything about 5-10 minutes
uraganone said:
First: Did you partition all the card or only a certain amount ?
Second: Almost all the Custom recoveries have format card so do that.Then boot back in recovery and mount your card from recovery.
Third: Do not run RUU Period.
Fourth: Wipe all, cache, dalvik and all 2or3 times.
You wont get stuck on splash. since you wipe all give it a bit of time to check everything about 5-10 minutes
Click to expand...
Click to collapse
on partition the card i just hit the power button on all of it. got a custom rom back on my phone now it is up and running.
I would suggest using this program when formatting your SD ..
https://www.sdcard.org/consumers/formatter_3/
Just and FYI, when partitioning your SD Card, it will wipe the contents. So you'll need to partition SD Card and then move over any content you want to install.

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

[Q] Defy restoring itself to old ROM automatically!!!

Hi All,
I am new here and this is my first post. But i have been reading this forum for quite sometime and know that u guys are now my final stone. I am a proud owner of a Motorola Defy. And I am having this strange behavior, which is effectively rendered the phone almost useless. The phone is acting like its got a restore point in itself, and every time i restart.. it gets back to that point in time.
This includes app installs, uninstalls, stuff placed in system through adb push, theme, everything in the OS. I tried installing a different ROm through clockworkmod, but its not taking effect. Its saying install success but as soon as it restarts, its going back to the old ROM. (takes time to load, so i guess it reinstall back/restored the old version)
Details of device : I am from India and the phone was manufactured in India in around April/May 2011. Its a red lens Defy and and came with Eclair. I updated it officially to the first Froyo release for SEA region. After that i rooted the phone with superone click, and installed WIUI rom. I have been updating the ROM with newer versions around each month. The last one was 1.11.18 though as i waiting for a good ICS version to flash.
The problem occurred after i started installing some gold apps from getJar. It restated in between and install... and that point is kind of acting like a restore point even now.
Things I did: Tried installing different rom by CWM method. Reinstalling second init and CM, both old and new version. Tried restoring nandroid backup of my official ROM. Tried fixed and full sbf flash through rsdlite 4.9.5.2 and now 5.6. First 3 things reset as soon as i restart. For RSDLite, it gives checksum error for each and every ROM i tried. I tried all SEA releases, JORDN_U3_97.21.51, Defy Plus Rom 2.3.6, 2.21 first eclair rom, everything gives the same error. From the RSDLite logs, i could see that there is something wrong as.. say the last successful CG was 33, and the error came for 34, the log says its expecting the checksum on the sbf to be equal to that of CG 33. Its taking the last successful checksum validation and expecting that for all the CGs henceforth. its not showing what the device actually has.
I atlast could somehow, but trial and error, removed all the CGs which were throwing error, and recompiled the sbf to make it pass the RSDLite flash. The CGs present in the ROM (JRDNEM_U3_3.4.3-36-1.7) were 32, 34, 42, 53, 61, 64, 65. And as soon as it booted, it restored back to the checkpoint. Even after i formatted by card and put it in, the app shortcuts remained on the home screen, but as the apps on the card were gone, they are just junk and doesnt open anything.
Thanks in advance. Please let me know what you need from me to help me resolve this issue.
Any help... Anyone?
Can someone please suggest something?
This is what i got from some people. I am not sure how far this is possible, but somehow the theme i installed just before this all happened, from MIUI market.. somehow managed to change something inside phone's kernel, past the locked bootloader? I am totally a noob in this and just a wild imagination?
Or may be some sort of cache wipe is happening everytime the phone boots up, So even when i install the ROM, when it boots up, it gets back the old ROM.. like what would probably happen if i do a factory reset soon after i instal a rom before the restart..?
I would really appreciate it if anyone could help me out with this...
Checksum errors were for me also.
I tried my office computer for flashing and instantly flash was done. The checksum error occurred 7 times on my good computer before that.
Reflashing froyo must take care of all errors happening
Thanks Kapil fr the response. Are you from india? Which sbf did u flash? And waht all did u install in the office pc? I have a pc of my friend where i can try to reflash if you tell me the exact steps that u took in the fresh pc.
Also, can anybody tell me how to use adb commands in CWM mode? Its recognizing my phone in normal mode but as soon as it boots in Moto recovery of CWM, its not recognizing anymore. Want to use adb format commands from recovery.
Hi I was able to use adb in CWM, but format commands were not working. How can i format the system partition? please help me with this.
Is there anyone here who know how to restore a nandroid backup manually using adb commands for MB525???!!!!!
Sounds weird and impossible. Try this. Wipe everything though cwm and flash new rom. Try ms2ginger.
Thanks darshanonline for the suggestion. I tried to wipe everything.. factory reset+cache+dalvik cache wipe. And then tried to install cyanogenmod 7.1 as well as 3 different wiui builds. Everytime it shows that the install was successful, ut as soon as i restart, it would go back to the old ROM.
Is there any checkpoint system in android, seeing the init.rc, i can see comments on something about saving a checkpoint. Is there any particular condition under which this checkpoint may be getting used on very restart?
Also.. is there any way for RSDLite to skip the chksum validations and get the install anyways?.. Some sort of a hack into it?
Ok.. Found something else thats happening. I dont need to shutdown for the system to revert back. Say i install a few things new after a reboot.. After some time.. 1 day at max, i am not able to open them, and neither am i able to open manage applications or market. Everything force closes. I have Ti Backup installed, and i opened it, and i didnt find the new apps to back up. I connected the device and checked through adb, and they were not present in the app folder. They just vanished... So basically after a certain point of tiime, the new stuff just gets deleted on its own.
Guys i know i may sound dumb and stupid with my questions, but i really couldnt find any solution on the net for this. Please tell me waht i should do, and i'll do it. But tell me something. Dont ignore please!
and you did wipe data from within stock recovery (vol down+power etc.), i presume..
Sent from my MB526 using Tapatalk
Yes i did that too.
wiped data and cache. Restarted to cwm and installed update.zip (renamed cm 7.1 stable) and by selecting zip from sd card. Same results. Installs successfully but reverts back as soon as i restart.
Same problem here:
http://forum.xda-developers.com/showthread.php?p=22617834
Soumik84 said:
Yes i did that too.
wiped data and cache. Restarted to cwm and installed update.zip (renamed cm 7.1 stable) and by selecting zip from sd card. Same results. Installs successfully but reverts back as soon as i restart.
Click to expand...
Click to collapse
DL WIUI 1.12.16 ICS > copy to SD card > Boot in CWM > select zip to install > Install WIUI 1.12.16
Hopefully your problem should be solved.
I found 1.12.16 ICS with lesser FC than the 2.21
labsin said:
Same problem here:
http://forum.xda-developers.com/showthread.php?p=22617834
Click to expand...
Click to collapse
Thanks for the link. Now i know that i am not the only one having this issue. But even there its not resolved yet.
@ headers.chennai - Thanks. I will try that ROM, along with Pikachu ROM with Aroma installer, might be a different installer can try fix it?!
BTW.. does anyone have the TI OMAP board utility? Any chance that it can be available outsite here?
I tried the arora installer and it supposedly formatted the system partition and remade it.. but as soon as it finishes and i restart.. I get back the same ROM.
Is it some way that the files are not getting deleted, like some hardware lock or fault?
Soumik84 said:
I tried the arora installer and it supposedly formatted the system partition and remade it...
Click to expand...
Click to collapse
Hi, bro! What is "arora"? I should try it asap, and all other chance.
My trouble here, same as your.
Hey man.. looks like we are having same problem...
Sorry abt the typo... its Aroma Installer. Its with the Pikachu ROM in this link :
http://forum.xda-developers.com/showthread.php?t=1498843
Its a new installer that launches from cwm when u try and install this ROM. u got some options to select and on selecting the complete install option,, the log shows that it formats the system partition and then creates it. I saved the log file, but for some reason the file shows up blank now. Might be problem with the launcher.. or my phone.. dont know.
Soumik84 said:
Its a new installer that launches from cwm...
Click to expand...
Click to collapse
Not for me, my checkpoint without cwm

Categories

Resources