Allo gents here's the issue as quick as I can explain it:
- had back ups of everything
- installed Slim Bean i9300-4.2.2.build.6-OFFICIAL. Failed to format the right folders properly.
- wiped Data, Cache, Dalvik
- found that CWM couldn't mount /sdcard, /efs, or /data
- as a result, no backup, and god knows what is destroyed.
- currently downloading stock ROM hoping that will help (6 hour left on download though...)
- installed TWRP hoping for some better options. No avail.
I'm stuck at Samsung loading screen. TWRP is accessible but no OS. I need options, anyone have ideas?
Thanks for your time.
What I have tried to follow so far:
http://forum.xda-developers.com/showthread.php?t=1264021 Doesn't work as I cannot find "nv_data.bin", "nv_data.bin.md5"
Installed Samsung S3 Toolkit
EFS Professional
Googled and googled and googled and searched for the past 6 hours non stop.
http://forum.xda-developers.com/showthread.php?t=2187081 Working on this, still need the stock rom.
Have you backed up your EFS folder ??
If so restore no backup take it to a service centre .
jje
Related
As of yesterday, my CM7.1 phone won't boot - it gets stuck at the "rotating arrow" blue Android for ever. It's a Samsung Galaxy S II GT-9100.
I have been running CM 7.1.0 for several happy months now, and haven't tried to install or upgrade my ROM. The last action I took before this happened is that I made a full system backup (using CWM 5.0.2.6).
That backup is present on the internal memory. I can boot into recovery, mount drives and access devices using adb shell. So I do have an opportunity to fix what's broken, if I can work out what it is.
Given that the last thing I did was a backup, I checked to see if any of the partitions were full, but none are. (None is more than 42% full according to df; although strangely, df does not show any partition mounted on /.) I tried making another backup, watching carefully - that worked fine. I tried restoring the first backup - no improvement.
I've also tried wiping everything Recovery allows me to that's non data-destructive - cache, Dalvik cache etc. It hasn't helped.
How do I work out what's wrong? Is there a boot log file anywhere which might give me a clue as to what is wrong? I've searched for "*.log" but can't find anything obvious.
I don't want to do a factory wipe if I can avoid it, because obviously that will lose all my data. If I do a factory wipe and restore just the data partition, does that put me pretty much back where I was? If so, how do I restore just the data partition? The Restore option in CWM Recovery seems to do full backups only, and only from a particular directory.
The original CM and Google Apps zips are still on the internal SD (same versions as are currently not working). Would it be worth trying to reinstall those, without wiping? Or would that be data-destructive?
Any other ideas?
Thanks!
Gerv
SOLVED - remove 0-byte data/system/profiles.xml
I tried doing a full factory reset from Recovery. This got the phone booting again, but without any of my data . Fortunately, ClockWorkMod has a "partial backup restore" function. I restored the data partition... and the phone stopped booting again.
So this is progress. I now had some idea where the problem lay. I finally found it using a laborious 5-minutes-per-cycle manual bisection technique. Delete half the stuff on the data partition, reboot, if it still fails, delete more, reboot... once you get it to boot, restore the data partition, narrow it down further. Once you find a top-level directory, repeat the process inside it.
The result: the existence of a single 0-byte file stopped my phone from booting entirely. The file was: data/system/profiles.xml.
I have no idea what that file does (there are only a few references online), how a 0-byte version of it got created, or why having it existent but empty breaks things but if it's not present everything works fine. I have no idea if anyone else will ever see this problem, or if they will ever find this forum post. But still, here's my Wisdom of the Ancients (google the phrase for the relevant XKCD comic).
Hello, I'm running RR 2.6.1 with Dorimanx's latest kernel and I've run into a huge problem.
I'm not sure what the trigger is but I think it could be updating the SuperSU app, or it could just be that I'm super unlucky. In any case, I really really hope someone will be able to help me here.
I was facing random freezes and SODs on the kernel but I was in the midst of tweaking my settings to see if I could fix it. I updated the SuperSU app on the bus on the way home, went home & tried to power my phone on but it wouldn't work so I force-restarted by holding down the power button. When it rebooted, I had all sorts of FCs so I went to CWM Recovery & cleared cache & dalvik & fixed permissions. Nothing worked. Here's what I've tried so far:
- reflashing the kernel
- reflashing the ROM
- re-rooting via Odin
- flashing another kernel (I tried fluxi but it was stuck at the animation screen & wouldn't boot)
- Googled for how to fix process.acore and Gapps FCs, tried to clear all the Google-related apps' data but they wouldn't clear
- trying to delete the apparent offending files from /data/data/... via adb and Android Explorer but it didn't work, kept saying it was read-only or something, even though I followed all the instructions to SU and mount as RW
By this time, exTweaks didn't recognise the kernel as compatible, Whatsapp and TB FC'd, just about everything FC'd.
I went into CWM Recovery to try and make a Nandroid but it said "Error while making a backup of /data".
I am truly at my wits' end. My phone wouldn't even let me access it after the right passcode was input. At this point, I just want to go in and backup my Whatsapp and relevant TB apps.
Please, if anyone is able to help me, PM me or something. I'm on Skype if you're so kind as to be willing to walk me through anything you think may help.
Thank you.
Flash a clean ROM, wipe cache and dalvik, do a factory reset and start from scratch.
Multiple fc can be caused due to several reasons like:
-wrong phone.apk
-wrong framework
-wrong ROM
-too much undervolt
Sorry for telling but my first sentence might be your fastest approach.
Tapatalked from my Samsung GT9100
Tyrol said:
Hello, I'm running RR 2.6.1 with Dorimanx's latest kernel and I've run into a huge problem.
I'm not sure what the trigger is but I think it could be updating the SuperSU app, or it could just be that I'm super unlucky. In any case, I really really hope someone will be able to help me here.
I was facing random freezes and SODs on the kernel but I was in the midst of tweaking my settings to see if I could fix it. I updated the SuperSU app on the bus on the way home, went home & tried to power my phone on but it wouldn't work so I force-restarted by holding down the power button. When it rebooted, I had all sorts of FCs so I went to CWM Recovery & cleared cache & dalvik & fixed permissions. Nothing worked. Here's what I've tried so far:
- reflashing the kernel
- reflashing the ROM
- re-rooting via Odin
- flashing another kernel (I tried fluxi but it was stuck at the animation screen & wouldn't boot)
- Googled for how to fix process.acore and Gapps FCs, tried to clear all the Google-related apps' data but they wouldn't clear
- trying to delete the apparent offending files from /data/data/... via adb and Android Explorer but it didn't work, kept saying it was read-only or something, even though I followed all the instructions to SU and mount as RW
By this time, exTweaks didn't recognise the kernel as compatible, Whatsapp and TB FC'd, just about everything FC'd.
I went into CWM Recovery to try and make a Nandroid but it said "Error while making a backup of /data".
I am truly at my wits' end. My phone wouldn't even let me access it after the right passcode was input. At this point, I just want to go in and backup my Whatsapp and relevant TB apps.
Please, if anyone is able to help me, PM me or something. I'm on Skype if you're so kind as to be willing to walk me through anything you think may help.
Thank you.
Click to expand...
Click to collapse
Try the following:
-Download this: Ultimate kernel cleaning script
-Reboot to CWM recovery
-Flash Ultimate kernel cleaning script
-Under kernel specific option, Reset extweaks settings
-format /system (under Mount and storage)
-Flash ROM (RR 2.61)
-Flash Gapps
-wipe cache partion
-wipe dalvik cache (under advanced)
-fix permissions (under advanced)
-Reboot your phone
My above steps will not wipe your and should definitely fix your problem
good luck
Thank you both for your suggestions!
Unfortunately, I didn't get to try them but I'll definitely be checking this again if (touch wood) this happens again. Hopefully it'll be useful to someone else facing similar issues, I know I couldn't find clear answers on what to do.
@jokesy If the /data partition is somehow stuck at read-only, I'm not sure formatting /system will help. I could be wrong, I apologise if I sound ungrateful ('cause I do appreciate your help) but wouldn't reflashing a ROM kind of overwrite the existing /system files already?
I'm not aware of the details and technicalities of what exactly happens during a ROM flash but according to the AROMA installer, it seems like /system is wiped first.
What I did
Gave up on backing up apps & WhatsApp through the normal ways, most of my TB apps are backed up daily anyway, just lost some data like that for Sleepbot.
Pulled WhatsApp database files from /data/data/com.whatsapp via ADB, restored the previous day's Nandroid backup & copied the database files to the relevant directory. I guess it may seem minor, but as everything was melting down on my phone, I kept getting messages from friends about project work in school & other stuff that I couldn't read so I really wanted to not lose all the new messages that had come in.
Restoring my Nandroid (thank God I backup daily) fixed everything, fortunately, but there are little quirks I'm still ironing out. Eg. My Godville app can't seem to connect to the main server & retrieve details of my character despite clearing data, uninstalling & reinstalling. Not too sure why.. :/
-----------------------
サンソングガラクシS II からタパトクで書いた。
@Tyrol
Ididn't know you were using aroma installer though, but formatting /system has nothing to ago with /data sms vice versa
Following my wouldn't have hurt though, ur would only ensure a clean system partition before install.
I'm happy for you
Better luck next time
Swyped from my Samsung Galaxy SII
I recently had a very similar problem. The only way I could resolve it was to also format /data during the usual full wipe re-install
Karl.morteo said:
I recently had a very similar problem. The only way I could resolve it was to also format /data during the usual full wipe re-install
Click to expand...
Click to collapse
Tough luck man. I don't know why the data corrupts spontaneously, it happened once to me when I was playing Plague, everything started FC-ing all of a sudden while I was in-game. Bizarre. Didn't want to do a full wipe so I just restored the /data partition from my latest Nandroid.
-----------------------
サンソングガラクシS II からタパトクで書いた。
Hey guys,
I have a little problem I can't find a solution to by searching.
I have a GS3 i9300 rooted with CF-Root-SGS3-v6.4.
When rooting, a version of CWM was installed (5.something).
Later, when installing af custom rom, I followed instructions and updated to a newer CWM (6.0.1.2):
http://forum.xda-developers.com/showthread.php?t=1719744
Later, I was thinking about restoring my original system backup, which I had made with the older CWM version right after rooting.
The new CWM can't restore my older backup. It can't recognize the file, not even when I copy it manually to the new CWM folder.
How can I solve this problem?
Do I need to install an older CWM again?
If yes, then one more question: As I said, my original CWM was installed when rooting. Can someone give me a download just for the CWM tar file included in the mentioned CF-Root?
Thanks a lot in advanced,
Agoston
Replace with older CWM root .
From Original Development section .
jje
still not recognizing + weird directory tree
After trying out three custom ROMs and after updating CWM, my system directory is rather weird. Besides the usual system folders, there is a "0" folder, that contains another set of system folders, and another "0" folder, containing the same. Also, my free internal storage as good as disappeared, from 8 GB to 1 GB. So, it looks like I have several systems on each other?!
How can I reduce this weird directory tree to just one? Do I need to wipe the SD-card?!
And by the way, I rooted the device again through Odin, and the old CWM is now installed again. Still though, it can't recognize the old backup.
As you probably imagine, I am hesitating to format SD-card, especially if CWM can't restore my factory ROM.
Can anyone help?
Thanks!
szaboagoston said:
Still though, it can't recognize the old backup.
Click to expand...
Click to collapse
I copied the backup directory manually to the "most superficial" CWM folder, and now trying system restore. I'ts not easy with four (!) different CWM directories.
Unfortunately I got an "error restoring data" message, and the phone is stuck in Samsung logo when booting.
Also, when trying to do a factory reset, I get the message: "error mounting /sd-card/.android_secure!"
Could this be because there is not enough space or something?!
If someone could help me with how to proceed, I would appreciate it!
Thanks.
Okay, the issue is solved. I admit, I might have been a little inpatient. Despite the "error restoring data" message, the stock factory system booted after a few tries - I might not have waited long enough. It seems that these "Folder 0"s were all just security copies of the old systems, and of course consumed a lot of hard disc space, so I just deleted them. Haven't met any negative consequences so far. I just got scared because of the error message and the too long boot time. Also this phenomenon with "Folder 0"s is not something I met before on other devices.
This error is still not answered on the forums so im starting a new thread.
i get the error as the title.
sd card space is not the problem.
i tried formatting the sd card.
i have less than 50 apps installed.
wiped dalvik cache, and all other sorts people say on other posts.
(my phone is LG P936 so "fix permission" screws up the phone. all text disappears)
have latest cwm recovery.
and still get the error.
any answers please?
and please dont reply if you are going to write an opinion.
only answers please.
sorry for my rude behaviour but I'm sick and tired of reading posts full of opinions and "maybe"s.
Not sure if you ever got this fixed but I 'm suffering from the same error. I tried pretty much everything you tried (even fix permissions) and I have about 20GB free on my SD card so space shouldn't be an issue. I have not yet tried formatting the SD card since it has always worked and CWM is able to write to it because the following files are created:
- boot.img
- data.ext3.tar
- recovery.img
- system.ext3.tar
The files that are missing are (based on older backups):
- .android_secure.vfat.tar
- cache.ext3.tar (probably because I wiped it first?)
- nandroid.md5
I have attached the log from CWM in the hopes that someone can tell me what is wrong. The error occurs at the end of the progress bar of 'backing up /data'.
hey just use TWRP Recovery. It's way better than CWM. normal backup on cwm took me like an hour but twrp was never longer than 10minutes.
Today I have formatted the SD card and tried again, but as expected it did not change anything.
ceoleaders said:
hey just use TWRP Recovery. It's way better than CWM. normal backup on cwm took me like an hour but twrp was never longer than 10minutes.
Click to expand...
Click to collapse
I guess I will give this a try. Can I just install it over CWM or can they run side by side?
different reciveries cannot be run side by side as they are installed on a different partition. so it will always be installed over your current one.
ceoleaders said:
different reciveries cannot be run side by side as they are installed on a different partition. so it will always be installed over your current one.
Click to expand...
Click to collapse
Well, I tried TWRP and it also fails at backing up my data partition. The log is a bit more clear though and it seems to get stuck on "/data/data/com.android.vending/cache/images" which is the last line before it gives an error. I checked the "images" folder and it seems empty but I cannot delete it. Tried ES File Explorer and Terminal Emulator but no way to get rid of it. The folder appears to be related to Google Play, so I cleared all data and cache from Google Play, even uninstalled the updates but there 's simply no way to get rid of it. I 'm not sure if this is the reason why the backup fails, but I CAN copy the folder and even rename it.
Pff looks like I 'm going to have to do a clean install after all .
Hello, I too have this problem and unfortunately TWRP is not available for my phone.
I used to be able to do CWM backups fine on my old phone, and they work great on my tablet. But they consistently fail at "/data" on my Galaxy Ace II x. Might it be because I'm using Link2SD? I don't see why that would cause a problem, but maybe it's having trouble with the symlinks?
Hmm. Seems the issue was that, despite having only 1.28 GB total available storage space on stock, the backups wanted more than 4 GB. Cleared some room on my microSD card and suddenly backups worked fine! Of course, shortly after I installed CyanogenMod, which has much smaller backups...
Sent from my GT-S7560M using Tapatalk 4
I forgot to report back here but the only way I found to fix the problem was by doing a clean install. After that, I was able to backup my data partition again. I then restored my apps ' data with TB and was unable to backup the data partition again. I 'm guessing one of my apps had corrupt data, but never got to find out which one it was.
maybe your partition not match with recovery, like something wrong vold.fstab
Just in case anyone still wants to know how to fix this, I managed to solve it by running these commands:
1. run adb shell in recovery.
2. unmount data partition (umount /dev/block/mmcblk0p26). -> this one failed so I skipped it
3. run e2fsck /dev/block/mmcblk0p26
See http://forum.xda-developers.com/showpost.php?p=48659092&postcount=868 for original post.
I got a few HTREE errors and a bunch of duplicate names which I renamed when prompted. Booted the phone and rebooted into TWRP and now I am able to backup my data partition again. :good:
EDIT: Problem reappeared so I tried the above commands again but it said that the filesystem was clean. Ran 'e2fsck -f /dev/block/mmcblk0p26' instead and had to fix a bunch of HTREE errors from Facebook again and duplicate names from Xprivacy but now I 'm able to backup my data partition again.
Dude just selest the backup format as both zip and tar filea
Hi,
I'm new around, hope this is the right forum...
I have a galaxy s1 (i1900) which I flashed with a new ROM (2.3.6) in the past and then installed 4.2.2 from a zip, and it worked fine for a few months.
Having the same ROM file I used before, I tried to get it back to 2.3.6, as the 4.2.2 didn't work quite well, causing some problems when trying to make phone calls / receive calls.
After flashing the 2.3.6 again, the phone kept rebooting itself. Having read a few different guides online I tried all options - wipe data, wipe cache, wipe dalvik cache... then did some dramatic things like formatting /system, /cache /sdcard... I know it's not a very smart things to do when you don't know what you're doing, but I guess I felt I have nothing to lose at this point...
I also tried to reinstall 4.2.2 again and it only rebooted to the recovery mode whenever turning it on.
When mounting to USB I see no files in the device at all, only a folder called 'clockworkmod' with file called '.recovery_version' inside, and 2 empty folders named 'external_sd' and 'LOST.DIR'. It also shows it has 13.2GB free out of 13.2GB, which is weird, because the os doesn't occupy any of the capacity.
How do I save this poor device?
Many thanks in advance for your kind help!
Naama