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.
Related
I have a problem. After finally talkling myself into rooting my phone I was able to pull it off sucessfully, almost. See I havent had service on my phone for 3 months. In that time I have enjoyed using it for wifi, e-mail etc. The phone always kept saying not provisioned a bunch of times but always kept functioning.
I installed cyanogen 7.0.3 (Ithink) last night and after it booted up I said "great I didnt break it" but right in the beginng when I tried to sign into my gmail (at the time already logged into my dads wifi) It wouldnt recognize that I am signed into a wifi. it just kept asking about a data plan. I dont get it.
1 year old Aria
Try going to Settings > Wireless & network settings > Mobile networks, and unchecking "Data enabled".
That was one of the first things I check. I got no idea why it won’t let me jump on internet or market even though I will see on my phone that I am connected to a strong wifi source. Then I'll use rom manager to restore back to 2.1 and my wifi will suddenly work again. It’s driving me nuts because I am having fun with cyanogen mod but the I’ll revert back to 2.1 because I have no internet
Try bypassing ROM Manager. In general there are all sorts of issues that can occur if you use ROM Manager to get to Clockworkmod on S-ON devices like the Aria. I'm not saying this is the actual cause of your problem, but it's one thing you can try.
Shut the phone off completely then do volume down + power button to get into Clockworkmod and try installing CM7 again.
Also, make sure you are doing a full wipe when you upgrade to CM7.0.3. You can't retain any settings from previous versions.
1) Boot into Clockworkmod
2) Wipe data/factory reset
3) Wipe cache partition
4) Advanced > Wipe dalvik cache
5) Partitions menu > format system
6) Install Cyanogenmod zip from sdcard
7) Install Google Apps zip from sdcard
8) Reboot
Parden my newb status for asking I'm learning quick. but after I go ahead with wiping all my data etc. do I keep super user status or do I have to download various boot drivers and root my phone again?
I also just noticed that as my phone was booting up from clockwork recovery it said at the end
"no sd-ext found. skipping backup of sd-ext" Maybe that could have been the prob?
Last question is I just bought a 8 GB sd a couple days ago, should I partition it while I am doing all this? Thanks alot for the help
BeanTown_HTC said:
Parden my newb status for asking I'm learning quick. but after I go ahead with wiping all my data etc. do I keep super user status or do I have to download various boot drivers and root my phone again?
Click to expand...
Click to collapse
Yes you will still be rooted. Clockworkmod will still be installed on your phone (which is what you use to install ROMs), and the ROMs that are available on this site (including CM7.0.3) are already pre-rooted. You shouldn't ever have to use Unrevoked again.
I also just noticed that as my phone was booting up from clockwork recovery it said at the end
"no sd-ext found. skipping backup of sd-ext" Maybe that could have been the prob?
Last question is I just bought a 8 GB sd a couple days ago, should I partition it while I am doing all this? Thanks alot for the help
Click to expand...
Click to collapse
That just means you don't have an ext partition on the SD card. It's normal.
If you partition your SD card and dedicate a portion of it to an ext partition, you can use it for additional app installation space. The Aria's internal memory is somewhat limited so this can be helpful if you like to use a lot of different apps. You don't have to partition the SD card before installing the ROM, although doing it before installing a clean ROM might save you some trouble of having to back up anything from the SD card.
You don't HAVE to partition the card if you don't want to. It's only if you want some extra app space or not.
Great it worked. My WIFI agnolidges me. That was wierd.
Thanks alot for the help.
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).
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
I was running AOKP 4.3 and downloaded the latest 10/30 update. I flashed in CWM recovery and everything took as normal. I wiped cache and dalvik and then rebooted. Apps updated as normal and lockscreen presented. I unlocked and immediately received two force closes (timely & swype) if I click them or not, if I unlock or not, the phone will crash and reboot every 6 or so seconds. Luckily, if I'm quick, I can reboot into recovery. I am in CWM but my external SD card won't mount so I can't load anything onto it and attempt a new flash and the only rom file on my internal SD is the one that got me in trouble here. I've gone back into recovery and attempted to wipe data/factory reset/etc. and nothing changes. Internal storage won't mount when I'm connected to my computer with a cable.
I don't mind losing everything and starting from scratch. I've tried to seek out my own info but there is SOO many threads and videos and I don't know where to start. Can someone please tell me the most efficient way to get back to a clean start? I was on JellyBeans from 1-22 and looking back that was probably more my speed. I shouldn't have tried to switch to 4.3 at all. I was able to run AOKP for about two months without issue but I seem to be out of my element here.
Can anyone smarter than me please take pity on me here? Sorry to waste your time as well.
Try just wiping the system, reflash rom and gapps. I think this keeps your apps in tact, if just not just use tb and restore. Otherwise full wipe sounds necessary, but not horrible. Just restore everything with tb
For last couple of days, Google play services has been throwing up an error dialogue on my phone that it has stopped with OK and Report Button Although there doesn't seem any downside for it, except for its annoyance that I have to click OK , the error comes up randomly. For hours it might not come but it can also come up many times in an hour. Screenshot of what is contained in crash report is attached
Anyway, first I thought my ROM had corrupted. So, I wiped everything and re-installed a new ROM. However, the error didn't go away, again it will come up randomly. So I thought it was due to f2fs format since I had formatted /data, /data/media and /cache partitions to f2fs using arter97's recovery (I was using his kernel also). So I formatted them back to ext4, also changed my recovery back to philz's and installed stock CM rom. But again the error started coming
So I thought maybe it was due to I had been restoring apps via Titanium Backup which is causing the issue. So I stopped restoring apps, however It didn't work either, I was still getting the error. I started flashing many different ROMs (CM, omni, aosp, custom touchwiz) , gapps combination's (banks, 0day PA, others), factory resetting 10s of times, using MegaWipe script to format everything, removing the memory card permanently, however the error is still coming.
So in the end, I flashed stock samsung 4.3 ROM via ODIN and did a factory reset, however the error is still coming
I don't know what else to do ? Is my phone NAND corrupted ? Is there any test I can do to make sure ?
Please suggest..