Database Develop

clockworkmod issue

helllo i have a samsung galaxy s. i downloaded CWM and used it before and it ran fine did a backup. then i decided to do a full factory reset of the phone including formatting the SD card. the phone is still rooted.
anyway with a clean phone i reinstalled CWM premium and try and backup my rom to get a clean backup done as i want to be able to go back to the original rom supplied by my carrier (optus) once i have played with froyo.
now the issue is the phone reboots and then the following errors happen
--Install from package--
Finding update package...
Opening update package...
E:Cant open /cache/update/zip
(bad)
Installation aborted.
does anyone know what to do, i have tried to do all the things as requested by CWM when i reboot, ie recovery mode is broken.
have enabled erase recovery = cant find this option
clearing the download cache =done no change
i reinstalled the program and have hard reset it again too.

Hi
if i understood correctly you formatted the internal memory of your phone. Well if thats the case, then unfortunately you deleted the ROM backup that you made on the internal memory (unless before formatting you copied the folder /sdcard/clockworkmod/backup/ (the rom back up folder) to your Computer) and also you deleted the clockwork recovery file. So now you need to install CWM from the scratch. and get yourself a stock (optus) rom backed up by someone the same method. i remember i have seen it somewhere here in the forum just search for it.
good luck

sorry what i mean is that i reset my phone to the factory default to get a backup of the stock optus firmware. and am having issues doing this backup. as it wont boot into recovery properly.

ok fixed it... not sure why as this does not make sense. but i went back to the internal sd card memory backup i had done and copied the recovery-update.zip and download folders back to the phone... went into CWM and then tried to do another backup and it works... maybe a bug during re-installation???

Well, glad to hear your problem is solved.
cheers

Moving Dalvik cache to EXT - unable to boot

Hello guys,
I have a little problem which seems to be coming when I move the dalvik cache to the EXT partition of my device.
I am using the latest version of MIUI. It has A2SD built in, but it doesn't seem to be working. It was working before though...
What happened:
I restored the NANDROID backup of the stock ROM I had made before flashing MIUI. Once I booted into it, it warned me about the 2.3.4 OTA update. I did it, but forgot that it overwrites the bootloader, removes root and I will not be able to revert to MIUI.
I pushed the Clockwork recovery and immediately started restoring the NAND backup of my MIUI ROM. Without gaining root on the Stock 2.3.4 ROM.
The Dalvik was moved to the EXT on the MIUI I was trying to restore and functioning properly.
The restore went fine, until it got to restoring the sd-ext. It stood there at some *.tmp file for an hour or so. I removed the battery, booted into recovery, wiped and started the restore again. This time it finished, but when I went to start the phone, it got stuck at the Nexus logo, not even showing the MIUI boot screen.
Wiped again. Tried booting into a previous backup, which didn't have the Dalvik moved to the EXT partition. Restored and booted just fine.
I tried several more times restoring the latest backup I had (the one with dalvik to ext) and got the same result.
Then I tried installing the MIUI backup that didn't have Dalvik moved to EXT and tried moving the Dalvik to EXT. The phone rebooted and same thing happened. Didn't want to get past the Nexus logo.
I then wiped everything except batt stats, formatted ext, and flashed the MIUI ROM. It booted perfectly, but A2SD was not working, just like before (solution was to move dalvik to sd). I downloaded the A2SD GUI only and moved the dalvik to EXT AGAIN. And AGAIN - not booting past Nexus logo.
The only thing I still haven't done is formatting the SD and re-creating the EXT partition.
Any other suggestions on what may be causing this and how to fix it?
I want to have a2sd on this ROM and moving the dalvik to EXT seems to be the only way of achieving this.

Repartition SD card, you've most probably corrupted the EXT partition by pulling the battery.

Do you think that restoring the last MIUI backup I had after this will do the job?

After repartitioning? As long as you back up the files from the main FAT32 partition on the computer, and restore them back - the EXT will be overwritten when restoring nandroid anyway.

Well.... I just formatted the card with Panasonic SD formatter. Transfered only the nandroid backup (without creating an ext partition beforehand) and restored it successfully, but when the phone starts booting it is stuck at the Nexus logo.
I also checked the MD5 of the backup and everything is fine.

Godzi said:
Well.... I just formatted the card with Panasonic SD formatter. Transfered only the nandroid backup (without creating an ext partition beforehand) and restored it successfully, but when the phone starts booting it is stuck at the Nexus logo.
I also checked the MD5 of the backup and everything is fine.
Click to expand...
Click to collapse
Wipe Cache and dalvic. Than try again. Your System Need a ext wenn you push dalvic to sd before.

I ran out of options.
Formatted the card, tried restoring - Nexus logo
Wiped Everything + Dalvik and Cache, restored - Nexus logo
Wiped Everything + Dalvik and Cache, didn't restore old MIUI backup - successful boot. When I tried to move Dalvik to EXT after the successful boot - Nexus logo after restart.
If anyone can suggest anything... Because this way I have no access to the A2SD on the device with this ROM. And everything was working fine before I restored the Stock Ginger.

Did you try installing DT on any other ROM and try and move dalvik to the sd to see if it does the same thing?

Dude Random21 said:
Did you try installing DT on any other ROM and try and move dalvik to the sd to see if it does the same thing?
Click to expand...
Click to collapse
No. I haven't tried with another ROM. I guess I will try CM7 and see what happens when I move the Dalvik to the EXT.
I repartitioned once again, this time using the same EXT size as before the breakdown (512MB). When the backup I am trying to restore was made.
Was using 1024 when I partitioned previously and got the Nexus logo again.
Edit: Same thing. Successful restore and then the Nexus Logo.

I suspect it's the ext partition. Why don't you try formatting through recovery, and do a clean install?
Which recovery do you use? I would avoid Clockwork 3.x...

Well. I formated using Panasonic SD Formatted and then partitioned using the recovery. I did a clean install after that and as soon as I move the Dalvik to the EXT, I can't boot past the Nexus logo.
Yes, Clockwork 3.x. I guess I will try Amon_RA as well. Nothing left to lose.

If you partition with Amon Ra, make sure you up the partition from ext2 to ext3 (available through the Ra menu options)...

Ok. Partitioned with RA.
Tried to transfer the nandroid backup made by Clockwork to a sd/nandroid folder so I can restore it from within RA but it kept giving out some error telling me to look at the recovery log when I selected *.img files from the list.
Good news. I booted into MIUI and installed a2sd GUI. Moved Dalvik to EXT without a problem. I guess Clockwork's partitioning is flawed. Everything is working fine now.
Thank you.
Can anyone suggest a method I can use to restore the Clockwork made NAND backup + the EXT backup now when my partitions are finally alright.
Any method would be fine. Even manual through adb. I don't care. As long as I restore my phone to yesterday.
Thank you guys once again.

You should be fine if you load a clockwork prior to v3.x. I think 2.5.1.4 was the latest version prior to the v3.x series. The issues only arise with v3.x.
But only clockwork is able to restore clockwork backups, and the same goes for Amon_RA.
As an alternative, you can just extract the img files and manually load your data back on. It is definitely more time consuming, but it wouldn't matter what recovery you use. It has been a while since I extracted anything from the img files, and when I did, I just got the data from apps stored on the internal (apps and dalvik were stored on the sdcard), and I think the only program I used was unyaffs2 to extract the data.

Thank you guys!
Partitioning the card with Amon_RA and restoring the old Clockwork-made backup with Clockwork 2.* worked perfectly.
I will not use Clockwork ever agian. Putting Amon_RA and that's it.

You will only have this problem with clockwork 3.x - there doesn't appear to be the same issue with clockwork 2.x

I have been using v2.x without any issues (never upgraded to v3.x). I prefer it because it gives me the option to wipe the /system partition, whereas Amon_RA is missing this feature and you can only do it with a flashable zip.

I use 2.x for a number of reasons. I tried 3.x a few times, but always had ext issues on my N1. Having said that, I've used 3.x on my nook, MT4G and G2, and never had issues with them - just on the N1...

I've used RA 2.2.1 on CM7, MIUI ,Sense rom. I never seen sd-ext issues on my Nexus One.

I think I screwed my phone :(

I downloaded the HydracoreNirvana kernel and installed it through CWM.
Later I thought of installing the Ultimate N7000 XXLSZ JellyBean 4.1.2 v5.2 ROM but I read somewhere that the HydraCoreNirvana kernel was not supported so I download SpeedMod K5-1 and flashed it through odin. The phone Rebooted but it didn't restart. It only showed the "Samsung Galaxy Note" screen and won't turn on.
I managed to boot into recovery and install the SpeedMod kernel and then, as stated in the ROM's OP, I flashed it checking every step as I took.
ROM was installed successfully but after the Language selection screen it shows "Samsung SetupWizard has stopped". I tried reflashing the ROM but its still the same error.
How do I get past this??
Any help would be greatly appreciated.

boot into recovery... mounts and storage> format - system, data, cache and preload and install the rom again

nokiamodeln91 said:
boot into recovery... mounts and storage> format - system, data, cache and preload and install the rom again
Click to expand...
Click to collapse
Okayy. That worked. Thanks a lot!
But the phone is lagging a lot now. Its even worse than before (And I haven't even installed any apps myself yet!). Any way to correct that problem?

install Titanium Backup and remove some of the apps that you dont use.. clear some space and it should become smooth.. also as you have just installed the rom, wait for media scanner to finish... give it a couple of hours

Okay.. One last question, I backed up my Messages and Call Logs through Titanium Backup to an .xml file but now when I want to restore it it doesn't give me the option to select from card/phone. It only shows "DB text editor" and "Dropbox". How do I fix this?

check if your internal and ext SD is detected properly. also check in TB preferences for the location of the backup folder

Yes, the Ext. card and the SD card are detected properly. I copied the backed up .xml files to the existing back up folder for TB but it still doesn't give me the option to restore from the card.

did you try going to preferences>backup folder location> detect

It says "No backup location was found" even though I've set a backup location!

may be try reinstalling TB

Phone Frozen after flash

I was using CM10.1 RC1 by bieltv.3. After he updated the the rom to RC2 I flashed it today after taking a back up.
I then restored the apps I used to have on my SD card, rebooted and moved to SD. Then I restored the remaining apps (twitter, swiftkey etc). The phone froze when i tried to set un check the notification for swiftkey. I waited for sometime and removed the battery.
On restart it loaded until my lock screen. I was waiting for dash clock to load but it didn't only to find out my phone had frozen again. Tried this twice without any success. So i reflashed the ROM after wiping cache/ data/ system/ dalvik cache. It now got stuck on the screen where i select the language.
I then decided to restore the backup taken from CWM 5.2.0.6. While restoring .android_secure it failed.
When i tried to wipe data it got stuck while wiping .android_secure.
Then I reflashed CWM and then wiped again. This time the wipe worked.
Then i tried flashing the RC1 that I had been running all this time. It too got stuck on the language selection screen.
Wiped everything again and now I'm trying to restore the CM10.1 Backup again. Currenly it's been waiting on restoring .android_secure for the last 15 mins. Not really sure what to do.
I'm currently out of ideas. Need help
Update: I tried to do an advanced restore and only restored the boot and system but it still gets stuck and then reboots/ or just stays stuck. it does unfreeze for a few seconds some times but then freezes again :/
after I wipe the dalvik cache if i select show log i get
failed to mount /dev/block/mmcblk0p2 (no such file or directory)
...
...
...
....
After reading about it I have come to the conclusion that my Internal SD partition is corrupt / damage since I can't mount SD-EXT
Am I correct?

iFeelYouJohanna said:
I was using CM10.1 RC1 by bieltv.3. After he updated the the rom to RC2 I flashed it today after taking a back up.
I then restored the apps I used to have on my SD card, rebooted and moved to SD. Then I restored the remaining apps (twitter, swiftkey etc). The phone froze when i tried to set un check the notification for swiftkey. I waited for sometime and removed the battery.
On restart it loaded until my lock screen. I was waiting for dash clock to load but it didn't only to find out my phone had frozen again. Tried this twice without any success. So i reflashed the ROM after wiping cache/ data/ system/ dalvik cache. It now got stuck on the screen where i select the language.
I then decided to restore the backup taken from CWM 5.2.0.6. While restoring .android_secure it failed.
When i tried to wipe data it got stuck while wiping .android_secure.
Then I reflashed CWM and then wiped again. This time the wipe worked.
Then i tried flashing the RC1 that I had been running all this time. It too got stuck on the language selection screen.
Wiped everything again and now I'm trying to restore the CM10.1 Backup again. Currenly it's been waiting on restoring .android_secure for the last 15 mins. Not really sure what to do.
I'm currently out of ideas. Need help
Update: I tried to do an advanced restore and only restored the boot and system but it still gets stuck and then reboots/ or just stays stuck. it does unfreeze for a few seconds some times but then freezes again :/
after I wipe the dalvik cache if i select show log i get
failed to mount /dev/block/mmcblk0p2 (no such file or directory)
...
...
...
....
After reading about it I have come to the conclusion that my Internal SD partition is corrupt / damage since I can't mount SD-EXT
Am I correct?
Click to expand...
Click to collapse
Did you try to fash a Stock via Odin, then flash root + cwn 5.0.2.6. fix and finally flash CM10.1 again and restore your back up?
I think your partitions are corrupted... Were you using sd-ext scripts? as int2ext? wel try with the first method

Viper The Ripper said:
Did you try to fash a Stock via Odin, then flash root + cwn 5.0.2.6. fix and finally flash CM10.1 again and restore your back up?
I think your partitions are corrupted... Were you using sd-ext scripts? as int2ext? wel try with the first method
Click to expand...
Click to collapse
I wasn't using any scripts.
I used odin and flashed the stock rom. Phone starts up goes to unlock screen and all looks fine. after about 1 min the phone starts to lag very very badly until it stops responding and then shuts down completely.
Didn't root or flash cwm still.

Maybe the files got corrupted somehow. Try downloading the ROM again and use another SD card.
That might fix it.
Good luck.

iFeelYouJohanna said:
I wasn't using any scripts.
I used odin and flashed the stock rom. Phone starts up goes to unlock screen and all looks fine. after about 1 min the phone starts to lag very very badly until it stops responding and then shuts down completely.
Didn't root or flash cwm still.
Click to expand...
Click to collapse
Try doing wipes after odin flashing

Viper The Ripper said:
Try doing wipes after odin flashing
Click to expand...
Click to collapse
I forgot to mention i did wipe data and cache after flashing via odin. So that didn't help
Edit- ok I noticed my sd card wasn't being detected so I removed it and rebooted and everything seems to be fine :/
Can a faulty sd card slow down/ make your phone become unresponsive?

iFeelYouJohanna said:
I forgot to mention i did wipe data and cache after flashing via odin. So that didn't help
Click to expand...
Click to collapse
And dalvik cache?

nikwen said:
And dalvik cache?
Click to expand...
Click to collapse
Yeah root it and flash cwm and then wipe dalvik cache if not try to flash a custom stock rom after odin fashing e.i. rooted and cwm installed after odin flash

Viper The Ripper said:
Yeah root it and flash cwm and then wipe dalvik cache
Click to expand...
Click to collapse
And afterwards do that: (also use a fresh downloaded CWM)
nikwen said:
Maybe the files got corrupted somehow. Try downloading the ROM again and use another SD card.
That might fix it.
Good luck.
Click to expand...
Click to collapse

Final Update:
The whole thing was caused by my SD card. I should have checked how the phone responds to with the SD card removed.
I'm suspecting it must have happened while using Titanium backup. Good thing I managed to get most of the titanium back up files copied to my PC so I can restore them later.
Things I overlooked: the phone only locked up a few seconds after it starts (i.e. gets to the lock screen). That's when the phone detects the SD card.
I need to figure out how to format the card now since I don't have another method to connect to the PC and the phone isn't detecting the card.
Thanks for all the help.

Is it detecting the card in CWM? If so, you could format it that way.
I got a miniSD card adapter with my phone? Did you not?

iFeelYouJohanna said:
Final Update:
The whole thing was caused by my SD card. I should have checked how the phone responds to with the SD card removed.
I'm suspecting it must have happened while using Titanium backup. Good thing I managed to get most of the titanium back up files copied to my PC so I can restore them later.
Things I overlooked: the phone only locked up a few seconds after it starts (i.e. gets to the lock screen). That's when the phone detects the SD card.
I need to figure out how to format the card now since I don't have another method to connect to the PC and the phone isn't detecting the card.
Thanks for all the help.
Click to expand...
Click to collapse
so your Sd card was corrupted, use a micro sd reader

Managed to format the SD by mounting USB using CWM.
CWM refused to format saying the card was read only. but the pc did a quick format

iFeelYouJohanna said:
Managed to format the SD by mounting USB using CWM.
CWM refused to format saying the card was read only. but the pc did a quick format
Click to expand...
Click to collapse
Great. :good:

[i9001] Unable to uninstall apps, wipe data, flash rom with Odin or CWM

Hi all, this is my first post on XDA. I'm having big troubles with my device, a Samsung Galaxy S Plus i 9001 and I'm looking for some advice.
After a clean installation of the rom i had been using for some time I started to get messages of force close for most of the apps installed at every boot. The ROM in question is SmoothieICS v2. I believe that the reason of this issue is the fact that I restored all the apps and the data with Titanium backup. To solve the problem I tried to restore a nandroid backup via CWM (version 6.0.1.0), but when a rebooted, the backup was not installed at all and the force close messages continued. After that I tried to wipe data and cache, reinstall the ROM via CWM and Odin, install the stock ROM, fix permissions, format the partition, but nothing worked. Every time I reboot the device, the old ROM boot up with the same force close messages.
I've read several posts on XDA with similar issues, but usually a clean reinstall worked fine. At the moment I'm out of option.
Find attache a copy of the logcat recorded after rebooting the device.
Any suggestion to save my phone is really appreciated.
Thnaks in advance.

Some tips here:
1: Flash BroodROM RC5 (this is an Gingerbread ROM with all the partitions of our device) via odin
2: flash CWM 5.5.0.4 (this is in my eyes the most stable recovery) and wipe all (system, data, cache,dalvic etc)

ibacco said:
Hi all, this is my first post on XDA. I'm having big troubles with my device, a Samsung Galaxy S Plus i 9001 and I'm looking for some advice.
After a clean installation of the rom i had been using for some time I started to get messages of force close for most of the apps installed at every boot. The ROM in question is SmoothieICS v2. I believe that the reason of this issue is the fact that I restored all the apps and the data with Titanium backup. To solve the problem I tried to restore a nandroid backup via CWM (version 6.0.1.0), but when a rebooted, the backup was not installed at all and the force close messages continued. After that I tried to wipe data and cache, reinstall the ROM via CWM and Odin, install the stock ROM, fix permissions, format the partition, but nothing worked. Every time I reboot the device, the old ROM boot up with the same force close messages.
I've read several posts on XDA with similar issues, but usually a clean reinstall worked fine. At the moment I'm out of option.
Find attache a copy of the logcat recorded after rebooting the device.
Any suggestion to save my phone is really appreciated.
Thnaks in advance.
Click to expand...
Click to collapse
First solution,
SmoothieICS is an outdated ROM. Currently there are more stable and bug free releases are available for our device. You can try that.
But, the choice is yours, if you want to continue with it,
Access download mode, install a stable and safe recoveries like CWM 5.5.04, TWRP 2.2.1, or CWM 6.0.3.2 via odin or you can try to flash it via current recovery.
Then do a full data wipe, wipe cache, wipe dalvic cache. If necessary, delete the partition and do a full format
Restore the nandroid backup or do a fresh install
Edit: @mrjraider Haven't seen your reply. Silly me, repeated the same thing you said..

jabrif said:
First solution,
SmoothieICS is an outdated ROM. Currently there are more stable and bug free releases are available for our device. You can try that.
But, the choice is yours, if you want to continue with it,
Access download mode, install a stable and safe recoveries like CWM 5.5.04, TWRP 2.2.1, or CWM 6.0.3.2 via odin or you can try to flash it via current recovery.
Then do a full data wipe, wipe cache, wipe dalvic cache. If necessary, delete the partition and do a full format
Restore the nandroid backup or do a fresh install
Edit: @mrjraider Haven't seen your reply. Silly me, repeated the same thing you said..
Click to expand...
Click to collapse
No problem mate
Things happen

Thank you both, but your solutions didn't work. After installing BroodROM via Odin my phone rebooted in SmoothieICS just like nothing happened. Also a new recovery can't be installed, Tried with TWRP and CWM with no luck :crying:

ibacco said:
Thank you both, but your solutions didn't work. After installing BroodROM via Odin my phone rebooted in SmoothieICS just like nothing happened. Also a new recovery can't be installed, Tried with TWRP and CWM with no luck :crying:
Click to expand...
Click to collapse
That's strange. How is it possible to show up again after deleting and formatting the partition completely.. Are you sure you formatted the data and system in mounts and storage menu of cwm recovery.?
Anyway, Remove your external sd card, and try all the methods again..

Tried again. Did the following:
- removed the external sd card
- rebooted in recovery
- format system and data
- installed CWM 5.5.0.4
- rebooted in recovery
The recovery version installed is still the 6.0.1.0!!!!
It is like the internal SD card can't be written any more.
One thing I maybe didn't mention is that if I delete a file in the internal SD card and the reboot, the file is still there. it is not deleted.
This is really frustrating.

ibacco said:
Tried again. Did the following:
- removed the external sd card
- rebooted in recovery
- format system and data
- installed CWM 5.5.0.4
- rebooted in recovery
The recovery version installed is still the 6.0.1.0!!!!
It is like the internal SD card can't be written any more.
One thing I maybe didn't mention is that if I delete a file in the internal SD card and the reboot, the file is still there. it is not deleted.
This is really frustrating.
Click to expand...
Click to collapse
That's strange and weird. Haven't heard about such a problem before. I will look in to it and will reply you if i get something..

ibacco said:
Tried again. Did the following:
- removed the external sd card
- rebooted in recovery
- format system and data
- installed CWM 5.5.0.4
- rebooted in recovery
The recovery version installed is still the 6.0.1.0!!!!
It is like the internal SD card can't be written any more.
One thing I maybe didn't mention is that if I delete a file in the internal SD card and the reboot, the file is still there. it is not deleted.
This is really frustrating.
Click to expand...
Click to collapse
I recognize those symptoms. The i/o of the sdcard is defect.
What happens is that when you want to format random 0 and 1 are being written to remove the data on the card. If your card is broken and cant be written to you will be unable to format or flash anything. And thus the data on the card remains.
Verstuurd van mijn GT-I9001 met Tapatalk

mrjraider said:
I recognize those symptoms. The i/o of the sdcard is defect.
What happens is that when you want to format random 0 and 1 are being written to remove the data on the card. If your card is broken and cant be written to you will be unable to format or flash anything. And thus the data on the card remains.
Verstuurd van mijn GT-I9001 met Tapatalk
Click to expand...
Click to collapse
Does this mean that the only way to solve the issue is to replace the internal SD card?

Same Issue, but with SGS GT-I9000
I have pretty much the same problem!
Ive been reading a lot and it really seems to be a problem of the internal SD card!
I tried many times to delete all the files on the internal SD card via USB and via Recovery Mode, installed different OS ...nothing worked and most of my apps crash the whole time, so force close to all!
Im now about to decide to use my external SD as internal!
What do you say?
Any ideas
Thanks