[Q] CWM error while making backup image of /data - Android Q&A, Help & Troubleshooting

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

Related

System Recovery Problem

Recently I have been having this problem. I go into system recovery and make a nandroid backup. then tell recovery to reboot phone. when the phone loads. I check the backup directory and there is no new backup. I do however get a rather large file in my lost.dir (I am thinking this is my backup?) I am using the system recovery that comes loaded with eclipse v0.6.1 and have it installed and set to recovery. also using the supplied charger from VZW.
So when you go into nandroid restore there is no backups there?
Sent from my DROID X2 using XDA App
right. I load BSR make a Nandroid backup, reboot the phone and it is not there. I do however have a large file in my lost.dir folder. This does not happen every time, but recently started happening, seems to happen more than not. I have been able to get a backup but it took 2 or 3 attemps for it to "stick"
Had a similar problem recently. I did a nandroid backup, but got some weird message about it not being able to backup sd-ext (which was my target). When I checked, there was no backup created, but in addition my entire Titanium Backup directory wound up in LOST.DIR. Dunno what happened, could be related to some other TB problems I'd had recently, but it was annoying as hell.
Deleted the contents of LOST.DIR, recreated Titanium Backup, and tried to do a nandroid backup again. Still got that weird "could not backup sd-ext" message, but it seemed to take this time. Might have been an error on the SD card?
I have ALWAYS gotten the line about not able to backup sd-ext no partition found.
I don't need to backup my external card anyway. It never gets deleted unless I specific format the card.
I have never had a problem when making my nandroid. I ALWAYS backup to external and it shows up in a folder named clockworkmod>backup>then date and time backup was created.
Are u trying to backup to internal or external? I have noticed that even tho sd flip is installed with eclipse that system recovery does not see this flip so if u backup to external and look for it in root explore it will be in the sd card folder(which is really ur external due to sd flip) sorry if that's confusing how I wrote it.
iCurmudgeon said:
Had a similar problem recently. I did a nandroid backup, but got some weird message about it not being able to backup sd-ext (which was my target). When I checked, there was no backup created, but in addition my entire Titanium Backup directory wound up in LOST.DIR. Dunno what happened, could be related to some other TB problems I'd had recently, but it was annoying as hell.
Deleted the contents of LOST.DIR, recreated Titanium Backup, and tried to do a nandroid backup again. Still got that weird "could not backup sd-ext" message, but it seemed to take this time. Might have been an error on the SD card?
Click to expand...
Click to collapse
I believe the message you're getting is normal. I've seen that message with every nandroid backup that I've created. Not sure if it is related to the problem, maybe? Thank you for the reply.
Sent from my DROID X2 using XDA App
This is a very strange problem indeed.
I have created and restored backups consistently over the past few days due to all the activity here with roms but I haven't had the issue of it not "sticking" when making the backup.
I wonder if a reinstall of system recovery could help with this
Um could you possibly reflash your device? This might be a bug buried deep inside the rom, if you use ti backup it restores your data almost 100 percent.
Make sure to clean data, cache, and dalvik cache.
Sent from my DROID X2 using XDA App
First id like to point out some roms delete worthless directories. If it keeps being put into a lost.dir maybe it actually was a needed directory that was deleted. In which case you can just make the dir "clockworkmod>backup>" maybe that's all it needs. Im not 100% sure
I have read a few posts across forums saying to ignore that error of not being able to backup sd-ext ... although I've also never had an issue with using the backups I've created.
However I hit install system recovery and it does. I go into recovery mode and it does. The strange part is every rom I install takes out my recovery. On my DROIDX I never had this problem. And it makes having a backup a little worthless because if the phone boot loops I only have the option of rsdlite then reinstalling recovery and then using the backup. Yes that keeps it worth it but it loses the usefulness. Does anyone know how to make it permanent? Or at least survive a data wipe... my last rom was ATRIX which did a data wipe without asking in past roms I do a cache wipe and leave data on to make sure it is usable. Then I wipe data and reinstall recovery...
Sent from my DROID X2 using XDA App
I think that rom makers might be able to male it permanent by having isbn debugging already on and have the hijack charge only mode script system recovery uses already installed. I don't know if that is possible tho.
ashclepdia said:
I wonder if a reinstall of system recovery could help with this
Click to expand...
Click to collapse
First thing I tried, but still had two out of three backups disappear.
m125 said:
Um could you possibly reflash your device? This might be a bug buried deep inside the rom, if you use ti backup it restores your data almost 100 percent.
Make sure to clean data, cache, and dalvik cache.
Click to expand...
Click to collapse
Happen to me on both the eclipse v0.6 remix5 and the eclipse v0.6.1, all wiped every time, (not saying it has anything to do with the rom, love eclipse, would have hated this phone if not for him)
SubVirus said:
First id like to point out some roms delete worthless directories. If it keeps being put into a lost.dir maybe it actually was a needed directory that was deleted. In which case you can just make the dir "clockworkmod>backup>" maybe that's all it needs. Im not 100% sure...
Click to expand...
Click to collapse
My directory is there. my previous nandroids are there, the new ones just don't always seem to be saved there? somehow getting corrupted?
SubVirus said:
However I hit install system recovery and it does. I go into recovery mode and it does. The strange part is every rom I install takes out my recovery. On my DROIDX I never had this problem. And it makes having a backup a little worthless because if the phone boot loops I only have the option of rsdlite then reinstalling recovery and then using the backup. Yes that keeps it worth it but it loses the usefulness. Does anyone know how to make it permanent? Or at least survive a data wipe... my last rom was ATRIX which did a data wipe without asking in past roms I do a cache wipe and leave data on to make sure it is usable. Then I wipe data and reinstall recovery...
Click to expand...
Click to collapse
After flashing a new rom, I have always had to go back into system recovery and set superuser privileges and "install" again.

[Q] Question Regarding CWM?

Hey.
My Galaxy S2 is acting up again with bootloop, and I can't access what's on the device. I can get into CWM and I've successfully backed up my current ROM. Now my question is: does CWM back up everything? Like app data and everything? I've got an app that has tons of notes on it that I really need and I'll be distraught if they're gone as it'll take me a good 12 hours of work to get them all back. So if I flash back to stock, then flash the backup will it be exactly like it was left with the notes intact? Thanks for any replies. They're much appreciated.
Thought it was backed up. Apparently not. It's saying something about not finding SD-ext and then something about MD5sum or something? Any help please?
Skellyyy said:
Thought it was backed up. Apparently not. It's saying something about not finding SD-ext and then something about MD5sum or something? Any help please?
Click to expand...
Click to collapse
CWM backups everything. literally everything. Try going into Restore from Internal SD card instead of external SD card. It might show up there. No need to reflash anything, just restore the backup and everything should be back to normal. Only the data you backed up will come back btw.
Even after flashing a new rom you can still restore the data.There is an app called nandroid browser which will allow you to browse cwm backup files just like normal files, you can use that app to restore specific data of any app you want.
Sent from my GT-I9100 using xda premium
Thanks a lot guys. Getting worried about this though, CWM doesn't seem to want to backup for me. It keeps failing on all-sorts of things, just a moment ago I tried and said
"Error while backing up boot image!SD Card Space free: 13200MB"
Click to expand...
Click to collapse
But just before that it says:
SD Card Space Free: 0MB
There may not be enough space to complete backup... continuing...
Click to expand...
Click to collapse
I can't quite understand it though. Why is it even saying no sd-ext? I've got a 16GB SD card for music and videos inside the phone.
After that it let me attempt the backup and once complete (sort of) it says:
Backing up cache...
No sd-ext found. Skipping backup of sd-ext.
Generating md5 sum.,,
Error while generating md5 sum!
Click to expand...
Click to collapse
Is there anything I can do?
Not expert enough but for note app, use programs like 'Evernote' which store all of your notes in the cloud. You can get'em back anytime you want.
pHraiL^ said:
Not expert enough but for note app, use programs like 'Evernote' which store all of your notes in the cloud. You can get'em back anytime you want.
Click to expand...
Click to collapse
Not very useful now is it?
I've got them up-to date to about 2 weeks ago via dropbox but there's still a lot I need from then-on.
Skellyyy said:
Thought it was backed up. Apparently not. It's saying something about not finding SD-ext and then something about MD5sum or something? Any help please?
Click to expand...
Click to collapse
if you did back up of the ROM from CWM to resolve you bootloop issue then it is wrong...you have first resolve bootloop issue and make back up..
1) the ext-sd which you are talking about is not your external SD card...it is an additional partittion which is made for system data on your external SD. when a rom is backed up from CWM this partition also is backed up. if you are not made such partition on your external SD, the process simply skip saying no ext-sd available, this is not an error, it is not really meant that you have no External SD, this action is the second last one before creating the MD5 during back up process.
2) after the completion of the backing up of all the data it automaticaly create a MD5 checksum file of your back-up files. this is the final action during the backing up. if you get an error while creating MD5 cheksum file your back will be there in your SD card, but you cant use that for restoring from CWM. since MD5 is not created properly, it will show the error MD5 checksum mismatching or something like that.
just flash any other kernel like latest siyah kernel and try CWM back-up is working properly till the end.
Try wiping Cache and Dalvik cache for getting rid of the bootlloop.
if you are not at all able to solve boot loop isntall a new rom, you can install your applications from CWM backup using some applications, like Titaniim back up if you have donated. no matter it is not created the MD5 properly.
zaheedahmed said:
if you did back up of the ROM from CWM to resolve you bootloop issue then it is wrong...you have first resolve bootloop issue and make back up..
1) the ext-sd which you are talking about is not your external SD card...it is an additional partittion which is made for system data on your external SD. when a rom is backed up from CWM this partition also is backed up. if you are not made such partition on your external SD, the process simply skip saying no ext-sd available, this is not an error, it is not really meant that you have no External SD, this action is the second last one before creating the MD5 during back up process.
2) after the completion of the backing up of all the data it automaticaly create a MD5 checksum file of your back-up files. this is the final action during the backing up. if you get an error while creating MD5 cheksum file your back will be there in your SD card, but you cant use that for restoring from CWM. since MD5 is not created properly, it will show the error MD5 checksum mismatching or something like that.
just flash any other kernel like latest siyah kernel and try CWM back-up is working properly till the end.
Try wiping Cache and Dalvik cache for getting rid of the bootlloop.
if you are not at all able to solve boot loop isntall a new rom, you can install your applications from CWM backup using some applications, like Titaniim back up if you have donated. no matter it is not created the MD5 properly.
Click to expand...
Click to collapse
Thanks for that. But won't installing a new ROM erase app data? Which is the whole point of the thread really, I can't extract the data which is needed.
Trying to charge it here, and the phone is getting ridiculously hot, so much so that I can't actually hold it for more then a few seconds. Do you think this could all just be a battery issue? I had one previously like this, bootlooping also, but previously without a power source, the phone would not turn on at all. This time it will. I'm just very confused.
Skellyyy said:
Thanks for that. But won't installing a new ROM erase app data? Which is the whole point of the thread really, I can't extract the data which is needed.
Trying to charge it here, and the phone is getting ridiculously hot, so much so that I can't actually hold it for more then a few seconds. Do you think this could all just be a battery issue? I had one previously like this, bootlooping also, but previously without a power source, the phone would not turn on at all. This time it will. I'm just very confused.
Click to expand...
Click to collapse
Installing a new rom doesn't erase data app since all your data is in /data. It will only erase data if you wipe data/factory reset. I suggest you wipe cache, wipe dalvik cache, format /system and flash your rom and flash gapps (if gapps not included in rom). This way, your internal apps data is always safe
Sent from my GT-I9100 using Tapatalk 2 Beta-5
Skellyyy said:
Thanks for that. But won't installing a new ROM erase app data? Which is the whole point of the thread really, I can't extract the data which is needed.
Trying to charge it here, and the phone is getting ridiculously hot, so much so that I can't actually hold it for more then a few seconds. Do you think this could all just be a battery issue? I had one previously like this, bootlooping also, but previously without a power source, the phone would not turn on at all. This time it will. I'm just very confused.
Click to expand...
Click to collapse
Yes it will erase your apps and data...if you are flashing a wipe ROM, but if you have a non wipe rom of your current ROM flashing of that wont erase...
you have made a back up which the process reached till MD5 check sum....that means that back should be there in your SD card from which you can restore your applications..
you go to recovery again and go to mout and storage and mout USB storage after connecting to the PC...check are you able to access the SD card and check clockworkmode folder and the backup file....if it is there then copy paste to PC.
if you are able to access SD Card then you can download another kernel or rom and paste on the SD card for flashing from CWM.
before flashing another ROM you can try changing your Kernel,
on which firmware are you currently?
Hey guys - I'm back. I've had to use my girlfriends old Samsung Genio for a few days. Worst days of my life to say the least.
I need my SII back. A few days ago it wouldn't charge at all (hence not being able to get to CWM). But it seems to be doing just fine now. Although I've still got the same boot-loop. I've mounted the SD card, and found the backups - they contain these files:
boot.img
data.ext4.tar
recovery.img
system.ext4.tar
Click to expand...
Click to collapse
Are these all the necessary files to restore? I'm very wary.
Also, if I do flash a different ROM, how will that have the data from my previous ROM if the new ROM doesn't have the apps?
If I do end up restoring, will that restore everything? I mean settings, SMS, app preferences, widgets, app data (Twitter drafts especially) and stuff like that?
Just want to be safe before I go and ruin things.
Btw could all this be due to the lack of free space on the phone? Seems like there is no space whatsoever. Finder is claiming there is 'Zero bytes' available. Surely that can't be good.
Bump. I really don't know what I should be doing.
Skellyyy said:
Hey guys - I'm back. I've had to use my girlfriends old Samsung Genio for a few days. Worst days of my life to say the least.
I need my SII back. A few days ago it wouldn't charge at all (hence not being able to get to CWM). But it seems to be doing just fine now. Although I've still got the same boot-loop. I've mounted the SD card, and found the backups - they contain these files:
Are these all the necessary files to restore? I'm very wary.
Also, if I do flash a different ROM, how will that have the data from my previous ROM if the new ROM doesn't have the apps?
If I do end up restoring, will that restore everything? I mean settings, SMS, app preferences, widgets, app data (Twitter drafts especially) and stuff like that?
Just want to be safe before I go and ruin things.
Click to expand...
Click to collapse
A full cwm backup contains of:
- .android_secure.vfat.tar
- boot.img
- cache.ext4.tar
- data.ext4.tar
- nandroid.md5
- system.ext4.tar
If you do a full cwm backup, all youre data (Apps, Contacts, Sms, Settings and so on) will be safed
After restoring a cwm backup you will get exactly that system, which you had before flashing, bricking or whatever.
Gesendet von meinem GT-I9100 mit Tapatalk
Dr.MacHack said:
A full cwm backup contains of:
- .android_secure.vfat.tar
- boot.img
- cache.ext4.tar
- data.ext4.tar
- nandroid.md5
- system.ext4.tar
If you do a full cwm backup, all youre data (Apps, Contacts, Sms, Settings and so on) will be safed
After restoring a cwm backup you will get exactly that system, which you had before flashing, bricking or whatever.
Gesendet von meinem GT-I9100 mit Tapatalk
Click to expand...
Click to collapse
Thanks for that! But do you know if I'd be able to fully restore even if I don't have all of the files? It seems that there is two missing from the CWM folder for me.
Skellyyy said:
Thanks for that! But do you know if I'd be able to fully restore even if I don't have all of the files? It seems that there is two missing from the CWM folder for me.
Click to expand...
Click to collapse
Yes I think it should work for you
Gesendet von meinem GT-I9100 mit Tapatalk

Non-booting SII with CM 7.1

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).

[Q] New CWM can't restore backup of older CWM

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.

Really weird wifi problem and mmcblk0p37 error

When I'm on the old CM10.1 ROM, my Rezound detects and connects to my house's wifi and other wifi sources with [seemingly] no problem, and I can access the web pages on chrome when I'm connected to wifi on the old CM10.1 ROM. However, when I flashed to CM10.1.2, and I'm on the starting set up page, trying to connect to a wifi, no wifi source ever pops up, even when my house's wifi is on and there are usually 1-2 other wifi sources in my area that should also pop up. I wait for over 10 minutes, and still no wifi source appears on the starting set up page for cm10.1.2. Additionally, now, when I'm on the old CM10.1 ROM, I can't download any updates or new apps from the play store at all. I was able to download google drive on my rezound only a week ago.
Anyways, the recovery I use is AMON RA-VIGOR-v3.16, and I noticed in amon ra that when I try "Wipe ALL data/factory reset", I get this:
Wipe ALL userdata
Press Power to confirm,
any other key to about.
Formatting DATA:...
Formatting SDCARD:.android_secure...
Formatting INTERNALSD:.android_secure...
E:Can't mount /dev/block/mmcblk0p37 (or /dev/block/mmcblk0p38)
(Invalid argument)
Error mounting /internal_sdcard/.android_secure!
Skipping format...
Formatting CACHE:...
Skipping format of /sd-ext.
Userdata wipe complete!
And that's it. What does this mean? just a couple days ago was the first time I flashed a new ROM on my Rezound for a month, and I think this "error mounting internal_sdcard/.android_secure" started when I flashed the first new ROM in a month. Is there anyway to fix this error and problem? I would really like to keep my Rezound and not have to buy a new phone... I would be happy to provide additional information if it would help solve this problem.
urstinky said:
When I'm on the old CM10.1 ROM, my Rezound detects and connects to my house's wifi and other wifi sources with [seemingly] no problem, and I can access the web pages on chrome when I'm connected to wifi on the old CM10.1 ROM. However, when I flashed to CM10.1.2, and I'm on the starting set up page, trying to connect to a wifi, no wifi source ever pops up, even when my house's wifi is on and there are usually 1-2 other wifi sources in my area that should also pop up. I wait for over 10 minutes, and still no wifi source appears on the starting set up page for cm10.1.2. Additionally, now, when I'm on the old CM10.1 ROM, I can't download any updates or new apps from the play store at all. I was able to download google drive on my rezound only a week ago.
Anyways, the recovery I use is AMON RA-VIGOR-v3.16, and I noticed in amon ra that when I try "Wipe ALL data/factory reset", I get this:
Wipe ALL userdata
Press Power to confirm,
any other key to about.
Formatting DATA:...
Formatting SDCARD:.android_secure...
Formatting INTERNALSD:.android_secure...
E:Can't mount /dev/block/mmcblk0p37 (or /dev/block/mmcblk0p38)
(Invalid argument)
Error mounting /internal_sdcard/.android_secure!
Skipping format...
Formatting CACHE:...
Skipping format of /sd-ext.
Userdata wipe complete!
And that's it. What does this mean? just a couple days ago was the first time I flashed a new ROM on my Rezound for a month, and I think this "error mounting internal_sdcard/.android_secure" started when I flashed the first new ROM in a month. Is there anyway to fix this error and problem? I would really like to keep my Rezound and not have to buy a new phone... I would be happy to provide additional information if it would help solve this problem.
Click to expand...
Click to collapse
try switching to twrp and erasing in that recovery, you can switch back to amon ra right after that if you want to http://forum.xda-developers.com/showthread.php?t=1902381
most mounting errors are fixed by either switching to a different recovery to reformat/partition the partitions (amon ra is a bit outdated, i used it in the past and and got mounting errors to. mostly after RUU and tried to install a ROM right away)
they can be fixed by running the RUU again, if you still get mounting error in amon ra after the RUU than all you have to do is reboot into the stock ROM and unmount and erase the sdcard in the storage settings than go back to recovery and it should be fixed
bunchies said:
try switching to twrp and erasing in that recovery, you can switch back to amon ra right after that if you want to http://forum.xda-developers.com/showthread.php?t=1902381
most mounting errors are fixed by either switching to a different recovery to reformat/partition the partitions (amon ra is a bit outdated, i used it in the past and and got mounting errors to. mostly after RUU and tried to install a ROM right away)
they can be fixed by running the RUU again, if you still get mounting error in amon ra after the RUU than all you have to do is reboot into the stock ROM and unmount and erase the sdcard in the storage settings than go back to recovery and it should be fixed
Click to expand...
Click to collapse
Thank you, bunchies. I never heard of TWRP prior to your response, so I appreciate it. I flashed TWRP version 2.6.0.0 with no problem and did the standard wipe first, which gave me an error and said it failed to wipe. So I went to the advanced settings in wipe and checked all tick boxes except the 'wipe ext sd' check box, and it was successful! I did it 2 more times to try to make sure it was successful. I decided to try to install the July 12 2013 build of CM10.1.2, and then the GSM patch and gapps, but it came out with the same problem of not recognizing any wifi sources within the vicinity like 2 days ago. When I downloaded CM10.1.2 2 days ago, I made sure to check its md5 sum, and it was equal to the one provided. Then I modified it by replacing its mms.apk, copied the resulting ROM to my rezound's root, and checked each others md5 sums, which where again equal. So I flashed amon ra v3.16 again and wiped everything and this time I didn't encounter ANY mounting error. I NAND restored my old back up of cm10.1 and tried to download google drive from google play....but it didn't work again...The error message I get in google play is this:
"Google Drive" could not be downloaded due to an error. (Error retrieving information from server. [RPC:S-5:AEC-0])
When I try to download Rezound Prox Sensor Calibrator, the same exact error message pops up (except inside the quotation marks in Rezound Prox Sensor Calibrator). And still, browsing the web on google chrome works like it should.... what can I do next to try to fix my rezound?
*edit* nevermind about the google play store problem. I went to settings>apps>all, cleared the cache of "google play store" and force stopped it, and cleared the data of both "google play services" and "google services framework" and force stopped both (though I've read that I probably don't have to do all that to google play services). I rebooted and for some reason, I can download and update from google play again. The problem of wifi not ever being recognized for me after I flash to the July 12 2013 build of CM10.1.2 still exists, though.
urstinky said:
So I flashed amon ra v3.16 again and wiped everything and this time I didn't encounter ANY mounting error. I NAND restored my old back up of cm10.1
Click to expand...
Click to collapse
Was this nand backup made during the time of mounting error, or during the time of the wifi problem?
the DATA folder may be corrupted in some way, i have had an issue before where i had a problem with my current rom than did a nand backup of just my data folder because the data folder holds things like apps/setting and other stuff which i didnt want to loose in my new flash but something in there can be corrupted. but after i would re-install the rom and did a nand restore of the DATA folder i would get the same issue in the new flash.
so if you did something like that it could be messing with your wifi
if you did something like that and you have time maybe just do a Nand backup of what you have now. than factory reset/wipe boot/data/system/caches and install the rom again without restoring anything and see if the wifi works as intended
if that makes any sense.. :silly:
bunchies said:
Was this nand backup made during the time of mounting error, or during the time of the wifi problem?
the DATA folder may be corrupted in some way, i have had an issue before where i had a problem with my current rom than did a nand backup of just my data folder because the data folder holds things like apps/setting and other stuff which i didnt want to loose in my new flash but something in there can be corrupted. but after i would re-install the rom and did a nand restore of the DATA folder i would get the same issue in the new flash.
so if you did something like that it could be messing with your wifi
if you did something like that and you have time maybe just do a Nand backup of what you have now. than factory reset/wipe boot/data/system/caches and install the rom again without restoring anything and see if the wifi works as intended
if that makes any sense.. :silly:
Click to expand...
Click to collapse
The nand backup I'm using right now was a backup I saved over a month ago (in June 6). The nand backup I made 2 days ago I think was corrupted (though i don't remember what it did anymore...I didn't think it was important at the time...), so I deleted it. In any case, every time I flashed the new rom, I never nand restored the "DATA" part. I didn't even know you can do that! Is DATA also where all text messages are saved? Anyways...nope, I haven't been nand restoring DATA after flashing the new ROM. I even tried flashing CM10.1.2 by itself without the gapps and gsm patch, but it still didn't recognize any wifi in the area.
urstinky said:
The nand backup I'm using right now was a backup I saved over a month ago (in June 6). The nand backup I made 2 days ago I think was corrupted (though i don't remember what it did anymore...I didn't think it was important at the time...), so I deleted it. In any case, every time I flashed the new rom, I never nand restored the "DATA" part. I didn't even know you can do that! Is DATA also where all text messages are saved? Anyways...nope, I haven't been nand restoring DATA after flashing the new ROM. I even tried flashing CM10.1.2 by itself without the gapps and gsm patch, but it still didn't recognize any wifi in the area.
Click to expand...
Click to collapse
Yeah data holds just about everything user end. this guy is having WiFi problems on 10.1.2 to http://forum.xda-developers.com/showthread.php?p=43605690
Just an observation
Edit: if a clean flash of ROM/gapps didn't work it could either be the ROM has a broken driver or hardware. Could be something els to but not sure, you can keep an eye on that thread to see if he gets his problem fixed if you want
Sent from my ADR6425LVW using xda app-developers app
Was the problem pinned down or resolved? I'm on an SIII, but experiencing a very similar problem.

Categories

Resources