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.
Related
Hey my xda'ers. I apologize with the bombardment of questions i have recently, theyre all things i have looked into and couldnt find exactly what i needed.
Its an easy question for those who use data to ext.
I had to go back to my backup (stock rom) to update my prl. This was from CM7.03 with data2ext applied. In recovery i wiped data/fac reset., cache partion, format boot, cahche, data, system, and sd-ext (this part is what i might mis understood) But anyway. I did what i had to do then decided to flash an AOSP rom. So in recovery i did the exact same wipe as above. Flashed rom, gapps, and data2ext4 v4. I didnt partion my card cause i though it was already partioned from my CM rom when i did it then (correct?) so i booted in and ran all the commands i needed for data2ext4 and it didnt run down my internal memory. so i decided to partion my sd card (again) to see if that would fix, it did NOT.
So can anyone shed light on what i did wrong and if i need to format and start over!?
When you were running data2ext you were supposed to do a nand+ext backup first and then flashed the data2ext zip and then rebooted. Then you were supposed to boot back into recovery and only wipe data,cache & dev-cache and then flashed your sense rom of choice. After you updated pri/prl power down and reboot back into recovery and make a regular nand and reboot. Then boot back into recovery and wipe data,cache & dev-cache then restore your nand+ext you made and then flash the data2ext zip and reboot. When your running data2ext ext don't wipe the sd-ext it will more than likely result in bootloops and could make your nands useless. Also your partition you setup on your sd should still be there unless you reformatted your sd. So when you wiped the sd-ext you essentially wiped out your data2ext link. And as far as if you have to start over well you could try to restore your nand+ext if you made one and then flash the data2ext and reboot to see if it will. If not then yes. But when you get it all set back up just make a nand+ext backup and remember not to wipe the sd-ext.
Root/Hack-Mod_Always *
laie1472 said:
When you were running data2ext you were supposed to do a nand+ext backup first and then flashed the data2ext zip and then rebooted. Then you were supposed to boot back into recovery and only wipe data,cache & dev-cache and then flashed your sense rom of choice. After you updated pri/prl power down and reboot back into recovery and make a regular nand and reboot. Then boot back into recovery and wipe data,cache & dev-cache then restore your nand+ext you made and then flash the data2ext zip and reboot. When your running data2ext ext don't wipe the sd-ext it will more than likely result in bootloops and could make your nands useless. Also your partition you setup on your sd should still be there unless you reformatted your sd. So when you wiped the sd-ext you essentially wiped out your data2ext link.
Root/Hack-Mod_Always *
Click to expand...
Click to collapse
hahahaha freakin A dude.
Thanks for sticking this with me as i understand this better. Ill re format and starrt over, and do this right! Hey once i get a few extra bucks ill donate to you for your constant help with buligernet questions from me
Lol na man I don't do donations but thanks for the offer. I don't mind helping out my fellow xda member. If you need anything else just let me know.
Root/Hack-Mod_Always *
I appreciate it so much. god bless
Ha Now that's a thanks I'll be glad to accept. God bless you to man.
Root/Hack-Mod_Always *
Oh and you don't have to reformat your sd your partitions should still be there as long as you didn't reformat your sd. You can just flash a fresh copy of your rom and just resetup the data2ext mod. But remember to make a nan+ext backup. Also always remember when you do and nand+ext backup always flash the data2ext zip and reboot. Then go back into recovery and continue. Same with restoring a nan+ext always reflash the data2ext zip right after.
Root/Hack-Mod_Always *
im using CW 3.0.2.8 and it doesnt say nand+ext, so i assume you use RA?
But i also assume CW backs up the ex if it exsits?
Edit: also you say flash it then reboot, then go back into recovery.
When i reboot do i need to enable it while im there, or just simply boot and go back to recovery?
coffeehandle said:
im using CW 3.0.2.8 and it doesnt say nand+ext, so i assume you use RA?
But i also assume CW backs up the ex if it exsits?
Click to expand...
Click to collapse
yes, CWM automatically backs up ext.
Thanks Il Duce!
From which part are you flashing the data2ext zip from???? And my bad. I'm using Ra, I should have asked you what recovery you were using. The same applys. And thanks duce for the cwm info.
Root/Hack-Mod_Always *
From the rom i had enabled with? yes. Cause i dont know how to disable it haha
If you already have the mod enabled and you want to do a update the same applys. Roms, kernels,etc. And since cwm already backs up the ext, then after you do the nand just flash the zip and reboot. Same applys for an update for pri/prl. And to disable data2ext in terminal do this
Su
data2ext --disable
Root/Hack-Mod_Always *
I tried a long various way, no success and now i can't use my loved nexus.
Everything was working very fine till i used my nexus' sd to flash a rom in a friend's nexus ( his was not working): here started the problem.
After re-putting on my sd on my n1, i lost all data, settings, no apps, no market, no adw..
-Tried to reflash the rom(kang 1.3 which was working perfectly till before): still no market, no adw, stock look, no apps (included in the rom)
-Tried to wipe all data/factory reset, reflash the rom: still no market, no adw, stock look, no apps (included in the rom)
Then i reached to install the 2.3.6 stock rom, which was working: i rooted it with superoneclick, installed rom manager
First i tried to backup with clockwork recovery but it stopped on backing up sd/ext: i had to remove battery and reboot, install ra recovery to have a success in backing up ( in recovery's opinion).
At this point i tried to reflash the rom, but i got stuck on the starting animation which is in loop..
I tried to nandroid restore from ra recovery but it said "Oooops something went wrong"
don't know how to solve, can you please help me? i can't use the phone! (recovery seems to work, have drivers correctly installed)
Ok my guess it's your SD card that has a problem so try making a full wipe (erase on) of your SD card and see what happens.
Dude Random21 said:
Ok my guess it's your SD card that has a problem so try making a full wipe (erase on) of your SD card and see what happens.
Click to expand...
Click to collapse
I'm re-flashing the passimg of stock 2.3.6 which yesterday was working.
again i noticed some problems on boot animation, but it moved on and it seems to works..
should i partition again my sd? Because it works on my pc ( in this way i put into the sd the passimg.zip, so it shouldn't be broken) and i guess maybe it's because of that..
A re partition would be a good idea.
When my sd-ext got corrupt the fat32 portion was fine but ext portion was busted
repartioned sd, still get the problem wtf..
http://pastebin.com/igvgPHSN here is the boot log, hope this'll help you..
thanks!!
I would format card outside phone with sdformatter--I use v2.0? Full Erase and Size Adj ON. Then repartition and swap is 0.
i first tried this:
http://imageshack.us/photo/my-images/38/problems2.png/
and then this:
http://imageshack.us/photo/my-images/23/problems3a.png/
but it didn't solve the problem.
Then i did a full wipe and it worked, i reached to install the rom, BUT missing some pre-installed apps (like adw, facebook, android stock keyboard etc., but with market, gapps et.)
i put this apps on my own and now it's working, but still miss something like the link to "power off", "reboot" , "recovery" etc.
what is going on?
I've flashed custom roms many times, but I have a couple questions regarding Texas ICS p10.
Currently running:
MeDroid 4.1.
BlackRose with System 220MB Cache 16MB Data 200MB
Amon’s RA recovery
Here's a checklist of what I should do:
Backup everything.
Update Blackrose to system 210 / cache 8 / userdata 218.
Wipe everything / factory reset 3 times
What do I need to do regarding formatting/partitioning the sdcard? ext4? setting dalvik cache to use sdext or data partition? In Amon's RA recovery, I have a "partition sdcard" option, with options to
- Partition SD
- Repair SD:ext
- SD:ext2 to ext3
- SD:ext3 to ext4
Do I need to do anything to get a2sd working other than rebooting a couple times?
Flash Texas' p10.
Flash google apps.
Restore.
Done.
Thanks in advance.
Sounds like you got it
if you are ext4 from medroid, you should be fine--not sure, but ext3 may work too
your current partition sizes are ok
see this on a2sd
http://forum.xda-developers.com/showpost.php?p=21222591&postcount=1374
i think you only rin a2sd install one time
i went to p10 and tiamets kernel and had some issues, restored back to p9 and lost my app links--even a sdcard reformat didn't work with p9 so went back to a medroid nandroid
haven't had time figure it out
medroid 6.1 is pretty stable for me
Ken
How can I check if the sdcard is formatted as 4ext?
Isn't it dangerous having a cache partition of only 8 MB?
Sent from my Nexus One using Tapatalk
maybe gparted or a partition tool program
i am having sdcard issues atm so can't test--terminal em can check, forget command, but sometimes it wasn't accurate for me
i don't know that 8mb is dangerous--some larger apps may not work right--depends how rom handles them. cm7 handles them well--miui doesn't--or so folks say
Don't know about 8MB cache, but it's kinda vurnerable to have only 210MB system partition now. If you have any plan to switch to other ics rom, i.e. MeDroidMod, you'll only have a little size left, or even nothing left. I repartizied back to 220/16/200, which is acceptable for any rom.
Sent from my Nexus One
Ok, so I followed the checklist I listed above. p10 stalls at the blue X boot logo for 10 minutes now. Anyone know why it's doing this? I'm going to go do a full wipe/repartition/reinstall again. I left my hboot alone, as suggested twice.
Actually, I opened blackrose and it automatically installed the latest blackrose, which put my phone in recovery and apparently wiped the rom??? Anyway, now I couldn't change hboot partitions anyway, so I proceeded with the rest of the checklist...
Have a 220/16/200 partition?
Boot into recovery, if you have 4ext recovery, you can format everything except sdcard, then flash p10 & gapps.
Sent from my Nexus One
Yeah, I have that partition. I just wiped everything, repartitioned the sdcard and reflashed... currently 8 minutes in the boot animation...
Not sure what to do from here.
Installed latest medroid 1.3.2a and it just keeps booting back into recovery.... hrm.
Do I need to flash a boot img as described here?
http://forum.xda-developers.com/showthread.php?p=22731102#post22731102
Ok, it installed. Updating blackrose, which took out my ROM for some reason, reverted to the default hboot as far as I can tell. I put the 220 version back on wiped and reflashed and it booted just fine.
Ended up using Medroid 1.3.2a instead of TexasIce p10. Even though p10 has HWA, it has bugs (browser rendering on zoom takes 2 seconds, sometimes longer) and isn't as fast as Medroid in general.
just got 1.3.2a and is running great
samuaz is loading HWA version now, but may have same issues as T's
First boot on ICS may take a while ! Just chill out ^^
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:
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