Related
This is a modified CWM-based recovery for the Motorola Atrix 4G. It is based on my own custom code forked from the CyanogenMod team's recovery. The major changes I have made include full support for dual SD cards, support for webtop partitions (SD card and internal) and changes to Nandroid backup/restore for this phone's additional partitions.
Some highlights include:
Dual SD card support
ADB support
USB Mass Storage support
Nandroid additions/changes
ext3/4 formatting
Unified kernel for international users
Probably others
This recovery is only for UNLOCKED devices. It is intended to be flashed directly to the recovery partition. Additionally, I have an AT&T phone so that is the kernel I am using. I doubt the memory issue would matter in recovery mode but testing from UNLOCKED international users would be appreciated. UPDATE: Initial indications are it works fine on UNLOCKED international phones. Versions for different tegraparts have also been compiled. UPDATE 2: Unified kernel patch has been applied. Choose whatever color you prefer regardless of phone version!
UNLOCKED users can flash this recovery using:
Code:
moto-fastboot devices
moto-fastboot erase recovery
moto-fastboot flash recovery recovery-atrix5.img
Example from my phone:
Code:
$ moto-fastboot devices
TA20700KXH fastboot
$ moto-fastboot erase recovery
erasing 'recovery'... OKAY [ 0.741s]
$ moto-fastboot flash recovery recovery.img
sending 'recovery' (4780 KB)... OKAY [ 0.490s]
writing 'recovery'... OKAY [ 0.544s]
This is posted in a DEVELOPER forum and is being released to help further the development of Android for the Motorola Atrix 4G. I have personally tested this on my phone but YOU assume full responsibility for any damage incurred to YOUR phone!
Click to expand...
Click to collapse
ALL USERS
Orange 5.0.2.7-atrix5 / ZIP version.
MD5 aebe29124d8c6d6c4b9873bd9ea4ca3b / 1f9a1d6fc83610e5c7c8f2d60e489b69
Cyan 5.0.2.7-atrix5 / ZIP version.
MD5 eb44b910983434d3996383098dff53b6 / 91365993488a9ae060b22c8b820d1c5b
Light green 5.0.2.7-atrix5 / ZIP version.
MD5 e7c7ec152e9e3269ef2ab1ce99b8943e / 1e720c8760898549226a10d4776f5077
Dark green 5.0.2.7-atrix5 / ZIP version.
MD5 c8a4438e5889d5e681a754555c40bc51 / 121d8d9102eac3ed24f1e0be6f8cd5d1
Blue 5.0.2.7-atrix5 / ZIP version.
MD5 9a1fd3c8796d2e768b54d39143c17ea3 / 9059c0c37fd2c547ec8508c893986815
Red 5.0.2.7-atrix5 / ZIP version.
MD5 036a9d9cc390a6071011d4d50b008875 / aa069d1aed20c5cbd13b2098b6a88975
Original ROM Manager installable zip thanks to SolidHelix. You must still be UNLOCKED to use them.
Source is here.
A few notes:
The capacitive buttons can be used to navigate as well. Back is back, search is select. Menu and home are up and down.
The "osh" partition is webtop. It is the largest by far and will take some time to backup. Nandroid is not frozen!
The "sd-ext" partition is an ext3/4 partition on your external SD card. Veterans will know this as apps2sd and data2sd from other phones. The only use I'm aware of on our phone currently is Sogarth's webtop2sd.
Thanks to:
Koush and the CM team for CWM
Everyone who has made unlocking the Atrix possible
** Changelog **
2011-11-14 (5.0.2.7-atrix5):
Minor bugfix release mostly
Added the ability to convert an ext3 partition to ext4 under advanced. Shouldn't break anything, but it is experimental.
2011-09-24 (5.0.2.3-atrix4.1):
Fix an issue with using ext4 formatting on stock ROMs
2011-09-23 (5.0.2.3-atrix4):
Updated to CWR5 base source.
The blue version is now the new CWR5 color. Old blue is gone. New photos welcome!
2011-09-17 (4.0.1.5-atrix3.3):
Unified kernel patch from eval-
New kernel to fix the stuck at "Entering Android Recovery" prompt. Big thanks to bamastang for helping test this.
Added a verify option to the backup and restore menu.
Renamed internal SD card mount point to /emmc and external is now /sdcard (this is largely cosmetic).
Merged in the CM7 device config when building the recovery image (again, just cosmetic).
Merged in miscellaneous fixes from the official CWM. Version 5 will be merged in once its ready.
2011-08-17 (4.0.1.5-atrix3.2):
Added 0MB option to ext3 partition size under External SD card partitioning which removes any ext3 partitions from the card (choose 0MB ext3/0MB swap to have only a FAT32 partition).
Added a red build to the mix.
Updated the update-binary in the CWM zips to be tailored for this phone.
Minor fixes to sdparted (log file related mostly).
2011-08-14 (4.0.1.4-atrix3.1):
Swap kernels to re-enable soft keys. Ext4 support should still work.
Fix for external SD card partitioning (internal is not supported).
CWM zip changed slightly.
2011-08-12 (4.0.1.4-atrix3):
Experimental ext4 support. Thanks to SolidHelix for testing it.
Fix for restoring large yaffs2 images (greater than 10,000 objects).
Tweak to the SD card space check before starting Nandroid backup.
Miscellaneous minor bugfixes and tweaks.
2011-08-07 (4.0.1.4-atrix2):
User is now prompted to wipe sd-ext (webtop2sd) on "Wipe data/factory reset".
User is now prompted to backup or restore webtop (/osh and /sd-ext) during Nandroid.
Four alternate colors created.
Versions for different tegraparts (international phones) created.
2011-08-05 (4.0.1.4-atrix1):
Initial release
Screenshots
Thanks to DarkSim2o9 for the following screenshots:
Orange
Cyan
Blue
Light green
Dark green
Red
Known Issues
sd-ext (webtop2sd) is inadvertently wiped on "Wipe data/factory reset". Next version will make this optional. Fixed in -atrix2.
Miscellaneous
If you'd like ROM Manager to see this recovery as "official" you can try XCellPhoneSalesRep's suggestion posted here.
Alternately, you can try dcarpenter85's suggestion here.
For issues with recovery not sticking or crashing, see here:
Thanks to mrinehart93 for pointing this out.
The system runs /system/etc/install-recovery.sh on boot with the stock rom. On boot it checks the recovery partition for some update and with CWM installed decides to reflash the stock recovery over it. Rename or delete the file and the CWM should stick.
Click to expand...
Click to collapse
Old versions
You can browse and download old versions here.
If I currently have tenfar's latest recovery, is it worth installing this one?
xploited said:
If I currently have tenfar's latest recovery, is it worth installing this one?
Click to expand...
Click to collapse
yes..Nandroid support
ok.. for some reason I can not enter recovery with Tenfar's or this CWM... I can enter it when plugged into AC using the Root Manager CWM.. Any ideas? I always get stuck at the "Entering Android Recovery Mode" screen and that is it... Any help would be greatly appreciated.
bamastang said:
ok.. for some reason I can not enter recovery with Tenfar's or this CWM... I can enter it when plugged into AC using the Root Manager CWM.. Any ideas? I always get stuck at the "Entering Android Recovery Mode" screen and that is it... Any help would be greatly appreciated.
Click to expand...
Click to collapse
were you using Tenfar's old version.
I had at one-point tried using the old version... after trying to flash the new version and having the problem. I flashed the new version I believe right after unlocking (first time flashing the CWM) It had never worked on my phone unless I used the ROM Manager version. I was hoping this would take care of the issue since I did the erase recovery and flashed this...
munchy_cool said:
yes..Nandroid support
Click to expand...
Click to collapse
So, backup and restore is COMPLETELY working on this recovery?
Sent from my MB860 using XDA App
bamastang said:
I had at one-point tried using the old version... after trying to flash the new version and having the problem. I flashed the new version I believe right after unlocking (first time flashing the CWM) It had never worked on my phone unless I used the ROM Manager version. I was hoping this would take care of the issue since I did the erase recovery and flashed this...
Click to expand...
Click to collapse
Hmm not sure I've experienced that. Do you have install-recovery.sh in /system/etc? Maybe it's conflicting
Javi97100 said:
So, backup and restore is COMPLETELY working on this recovery?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Very interested in this as well. The big problem (only problem iirc) with Tenfar's is its inability to properly backup and restore the PDS partition.
If this release gives us all of the features of the official CWM, I will be ecstatic!!!
DK
Javi97100 said:
So, backup and restore is COMPLETELY working on this recovery?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
It should be from my tests, but you should also test it.
romracer said:
It should be from my tests, but you should also test it.
Click to expand...
Click to collapse
I have several backups of my PDS partition. I am very busy tonight, but was planning on spending tomorrow re-building my laptop. So while I'm doing that I'll do a backup, wipe, and restore to see what happens and report back.
DK
DeathKoil said:
Very interested in this as well. The big problem (only problem iirc) with Tenfar's is its inability to properly backup and restore the PDS partition.
If this release gives us all of the features of the official CWM, I will be ecstatic!!!
DK
Click to expand...
Click to collapse
PDS is definitely backed up. It's not restored by default, just as a wimax partition is not on those devices that have them. It is available under Advanced Restore but you should help test it and have a separate backup just in case.
Backup early and backup often.
romracer said:
Hmm not sure I've experienced that. Do you have install-recovery.sh in /system/etc? Maybe it's conflicting
Click to expand...
Click to collapse
The only install-recovery.sh I had was in the /etc not in the /system/etc
I don't know if there is something missing that CWM is dependant on or what. But like I said if I use the one from ROM manager which is 4.0.1.4 I can boot into recover with the plugged in via AC.
Bug during backup?
So I am starting my backup of my phone using this recovery.
I booted into recovery, chose "Backup and Restore", then chose "Backup", and finally told it to makeup to the external card.
Here is my output:
CWM-based Recovery v4.0.1.4-atrix1
SD Card Space free: 4331MB
Backing up boot image...
Backing up recovery image...
Backing up system...
Backing up data...
Backing up .android-secure...
Backing up cache...
No sd-ext found. Skipping backup of sd-ext.
Backing up osh...
Backing up pds...
Generating md5 sum...
Backup complete!
It seems somewhere in the backup code it tries to backup the contents of the SD-Card (external), but the mount point is referenced as "sd-ext" instead of "sdcard-ext".
This isn't a big deal for me at all, as I only have videos and music on the external card - both of which I have copies of on my PC. For some people, they may want to be able to backup the external card as well.
Edit: In the advanced restore options there is also an option to restore the external sdcard, but it is against referenced as the mount point "sd-ext" instead of sdcard-ext".
Like I said, I'll wipe the phone clean tomorrow and test restore it then make a new post with the results.
So far so good!!
DK
bamastang said:
The only install-recovery.sh I had was in the /etc not in the /system/etc
I don't know if there is something missing that CWM is dependant on or what. But like I said if I use the one from ROM manager which is 4.0.1.4 I can boot into recover with the plugged in via AC.
Click to expand...
Click to collapse
Boot regularly and then in Settings enable USB Debugging. From a command prompt, "adb devices" should show your phone. From there, "adb reboot recovery" and wait 10-20 seconds.
Does that get you into recovery? Does the "Motorola Dual Core" boot image change at all when you try to boot into recovery? Like to a little Android guy with a yellow hazard sign?
The "plugged into AC" recovery is just a hijack of the normal system, so if your phone boots normally I'm not surprised that method works.
DeathKoil said:
So I am starting my backup of my phone using this recovery.
I booted into recovery, chose "Backup and Restore", then chose "Backup", and finally told it to makeup to the external card.
Here is my output:
CWM-based Recovery v4.0.1.4-atrix1
SD Card Space free: 4331MB
Backing up boot image...
Backing up recovery image...
Backing up system...
Backing up data...
Backing up .android-secure...
Backing up cache...
No sd-ext found. Skipping backup of sd-ext.
Backing up osh...
Backing up pds...
Generating md5 sum...
Backup complete!
It seems somewhere in the backup code it tries to backup the contents of the SD-Card (external), but the mount point is referenced as "sd-ext" instead of "sdcard-ext".
This isn't a big deal for me at all, as I only have videos and music on the external card - both of which I have copies of on my PC. For some people, they may want to be able to backup the external card as well.
DK
Click to expand...
Click to collapse
"sd-ext" refers to an ext3 partition on the external SD card. On other phones, this is used for crap like "data2sd" and "apps2sd". On our phones, the only current use I've seen of this is for Sogarth's webtop2sd.
Standard CWM does not backup SD card contents (it backs up to them) so there is no support for that in mine. I could consider adding it eventually.
You will see references to "sdcard-ext" in my recovery if you do something like Apply update.zip and then choose External SD card (look at the path it shows you for update.zip on the confirm screen).
I used to get issues to wipe data in the original 4.0.1.4
Is data wipie fixed in this custom recovery?
guidoido004 said:
I used to get issues to wipe data in the original 4.0.1.4
Is data wipie fixed in this custom recovery?
Click to expand...
Click to collapse
Yes. I have personally tested this particular item a few times. mke2fs from Koush's CWM segfaults, but I have supplied a working one.
Will you be including international support?
Hi everyone.
I recently decided to give Temasek's CM ROM a go. I made all my backups and booted into CWM from ROM Manager. Things were looking good so I wiped data, cache and dalvik.
But when I went to 'Install zip from sdcard' it could not find the card (all my .zips were stored on the external.) I saw that the internal SD was accessible so I went to mounts and storage to put my things onto there except it wouldn't mount USB storage.
I tried to reboot into CWM but it was gone. It just did a factory-reset.
Realising CWM was gone I proceeded to reflash CWM using NVFlash. But my computer did not detect the phone at all.
So now. I've got a blank 2X with Stock ROM and Neoblaze Kernel.
Any ideas?
Thanks in advance.
Martin9630 said:
Hi everyone.
I recently decided to give Temasek's CM ROM a go. I made all my backups and booted into CWM from ROM Manager. Things were looking good so I wiped data, cache and dalvik.
But when I went to 'Install zip from sdcard' it could not find the card (all my .zips were stored on the external.) I saw that the internal SD was accessible so I went to mounts and storage to put my things onto there except it wouldn't mount USB storage.
I tried to reboot into CWM but it was gone. It just did a factory-reset.
Realising CWM was gone I proceeded to reflash CWM using NVFlash. But my computer did not detect the phone at all.
So now. I've got a blank 2X with Stock ROM and Neoblaze Kernel.
Any ideas?
Thanks in advance.
Click to expand...
Click to collapse
Do you have a P990 or a P999? (The reason I ask is that you seem to have done a "fakeflash" of CWM, which should only happen on P999.)
If P990 - follow steps 1 to 3 in this thread. (You don't need to download SU303 though.) Don't worry, NVFlash will work if you follow the instructions to the letter.
If P999 - go to the G2X Forum for instructions.
Hey there.
It seems that I'm not booting into CWM simply because I wasn't holding the buttons down long enough!
(This is the second time I've done something stupid.) So I apologize.
But thank you for replying to my post. I will still hit that 'Thanks' button.
No need to apologise, we all have done stupid things. Now it's important that you learn from it
I created backup for my original 2.3.4 ROM in the ClockworkMod Recovery. After installed CM 7.1. The original ROM backup doesn't work in the recovery backup and restore menu's. I Started the phone, and the phone is restart all time.
What's the problem?
I need Original ROM.
Only smartflash?
Copy the attached file to your sd-card, install it from CWM, and then restore your backup.
I created some backups in the CWM Recovery --> Restore Backup --> Backup.
The Backups doesnt works.
ive had this happen to me too and figured out that, at least in my case the emmc and sd card got swapped, making it impossible for CWM to find the backup. also, there was an issue regarding a touch recovery version having problems with our phones.
everest140 said:
I created some backups in the CWM Recovery --> Restore Backup --> Backup.
The Backups doesnt works.
Click to expand...
Click to collapse
Did you try TrymHansen's post already?
Can you post a copy of /cache/recovery/last_log
everest140 said:
I created backup for my original 2.3.4 ROM in the ClockworkMod Recovery. After installed CM 7.1. The original ROM backup doesn't work in the recovery backup and restore menu's. I Started the phone, and the phone is restart all time.
What's the problem?
I need Original ROM.
Only smartflash?
Click to expand...
Click to collapse
TrymHansen said:
Copy the attached file to your sd-card, install it from CWM, and then restore your backup.
Click to expand...
Click to collapse
TrymHansen's solution should work. CM7 uses ext4 and stock uses ext3.
everest140 said:
I created some backups in the CWM Recovery --> Restore Backup --> Backup.
The Backups doesnt works.
Click to expand...
Click to collapse
Same here I made a backup with 5.2.0.8, then flashed new BB, then MD5SUM mismatch when restoring...
Plus some strange behavior of the phone, I even thought it was bricked, impossible to reboot in smartflash mode, and finally rebooted alone in recovery.
Had to made a fresh reinstall. Grrrr....
In as few words as I can muster.
I recently tried to back up my current ROM CheckRomV6 using CWM. In attempting so the following occurs.
CrazyOGuy said:
Screen goes Dark.
Clockwork Mod Opens and Reads:
ClockworkMod Recovery v5.8.1.5
Waiting for SD Card to mount(20s)
SD Card mounted...
Verifying SD Card marker...
SD Card marker not found...
Checking Internal SD Card marker...
Error processing ROM Manager script. Please verify that you are performing the backup, restore, or ROM installation from ROM Manager v4.4.0.0 or higher.
/tmp/recovery.log. was copied to /sdcard/clockworkmod/
recovery.log. Please open the ROM Manager to report the issue.
Click to expand...
Click to collapse
I need to get this fixed so that I can begin the progress change my rom. What is causing this? I'm thinking it's the kernel, but to be frank I really am at a loss. I'm still rather inexperienced with all this. Any suggestions? (I have searched.
You're probably using CWM or a ROM manager to do a backup
Try rebooting in recovery and use the option (Backup & Restore) to do a backup, use .tar format if available in the menu
Backing up the ROM doesn't require a safe kernel, but restoring a backup does
Best of luck
Mohammed Atef said:
You're probably using CWM or a ROM manager to do a backup
Try rebooting in recovery and use the option (Backup & Restore) to do a backup, use .tar format if available in the menu
Backing up the ROM doesn't require a safe kernel, but restoring a backup does
Best of luck
Click to expand...
Click to collapse
I just tryed that. Not. Good. This has officially gone over my current know how.
CWM won't let me select anything. Regardless if I scroll up or down ( to try to select Backup & Restore) The cursor moves... then the screen "blinks" black... and then my cursor is back where it originally was at (reboot). I need to make sure that this isn't a deeper problem before I flash something.
I am open for suggestions.
whats the kernel you on?
nokiamodeln91 said:
whats the kernel you on?
Click to expand...
Click to collapse
2.6.35. 14-ver.4.2
[email protected] #3
you could try a different kernel for you rom
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