Related
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.
Ever since moving up to JB 4.2.2 from ICS 4.0.3, I always get this "Android is upgrading apps" message everytime I reboot. Is this normal?
Not sure if its related but I get a lot of "corrupt messages" error in whatsapp sometimes after a reboot. This makes me lose some messages prior to the reboot as I have to restore from the backup (whatsapp only backs up messages at 4am everyday) and its getting real annoying, have gotten this error about 4-5 times in about 2 weeks so far.
I am using CarbonROM v1.7 (offical stable), and Dorimanx's kernel, from 9.14 to 9.30, 9.31, 9.32, and now 9.33 (I get the most errors in this version).
Would appreciate it if anyone could help me out! Can't find any relevant info after searching (or maybe I suck at searching).
iamatechnoob said:
Ever since moving up to JB 4.2.2 from ICS 4.0.3, I always get this "Android is upgrading apps" message everytime I reboot. Is this normal?
Not sure if its related but I get a lot of "corrupt messages" error in whatsapp sometimes after a reboot. This makes me lose some messages prior to the reboot as I have to restore from the backup (whatsapp only backs up messages at 4am everyday) and its getting real annoying, have gotten this error about 4-5 times in about 2 weeks so far.
I am using CarbonROM v1.7 (offical stable), and Dorimanx's kernel, from 9.14 to 9.30, 9.31, 9.32, and now 9.33 (I get the most errors in this version).
Would appreciate it if anyone could help me out! Can't find any relevant info after searching (or maybe I suck at searching).
Click to expand...
Click to collapse
the upgrading apps message isn't an issue, it occurs when any dalvik operations are running, or also optimisations (wheel align, zipalign, sqlite, detailing, etc.)
as to the corrupt messages error, i'm not sure at all, sounds like sd card rw errors in boot
eskriminal said:
the upgrading apps message isn't an issue, it occurs when any dalvik operations are running, or also optimisations (wheel align, zipalign, sqlite, detailing, etc.)
as to the corrupt messages error, i'm not sure at all, sounds like sd card rw errors in boot
Click to expand...
Click to collapse
So.. what should I do to get rid of that error? Any possible solutions you can think of?
Fully wipe and reflash Rom. That should get rid of problems. If continue to do this change Rom.
iamatechnoob said:
So.. what should I do to get rid of that error? Any possible solutions you can think of?
Click to expand...
Click to collapse
mmmm, try wiping the data and cache of what'sapp
Sent from my GT-I9100 using Tapatalk 2
andrewwright said:
Fully wipe and reflash Rom. That should get rid of problems. If continue to do this change Rom.
Click to expand...
Click to collapse
I'm trying to avoid that, haha. It was doing fine initially, then after I flashed Dori's kernel after about 1-2 weeks of use, it started popping up. I used Hawker's wipe scripts so it should be pretty clean.
eskriminal said:
mmmm, try wiping the data and cache of what'sapp
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
I've cleared data and cache and reinstalled whatsapp, hope it gets rid of the problem.
iamatechnoob said:
I'm trying to avoid that, haha. It was doing fine initially, then after I flashed Dori's kernel after about 1-2 weeks of use, it started popping up. I used Hawker's wipe scripts so it should be pretty clean.
I've cleared data and cache and reinstalled whatsapp, hope it gets rid of the problem.
Click to expand...
Click to collapse
hope it works for you
Sent from my GT-I9100 using Tapatalk 2
For your backup issue of Whatsapp... Just click on that " backup conversations " tab. Yes its given that the backups occur at 4:00 am but that's the automatic backup. Tap that box and it backs up real time
Go Bk to stock kernel if dori is upgrading all the time. well the message. Reflash Rom no wipe will give you stock kernel Bk
I'm not the developer but kitkat nightly is out.
ROM download: http://download.cyanogenmod.org/?type=nightly
gapps download: http://wiki.cyanogenmod.org/w/Gapps
Change log: http://changelog.bbqdroid.org/#/t0lte/next
You might experience problem with twrp so it might be better to use CWM.
Also I believe it'll be a full wipe installing the ROM the first time. Good luck.
ps. if the cm dev wants to create a new thread for this ROM, please do so and I'll ask a moderator to close/delete this one.
here are the results of my trials earlier today. ROM is working nicely now. at least on the apps I've tried it on. Still using dalvik though.
-------------------------
some tips (all my testing was done using official CWM 6.0.4.1):
1. Definitely do not use TWRP unless there's an update to 2.6.3.7. (seems TWRP could work if one use the modified version. see message below. I haven't tested this myself.)
2. using CWM and exFAT is a hit and miss. A fresh install and the ROM can't see sdcard. The only time the sdcard was detected was after a nandroid restore.. Since all the files in my SDcard is < 4GB, I can use FAT32.
3. nandroid restore = no mobile connection for me. this was fixed by reflashing the even if it's the same nightly (example: say I made a nandroid backup of 17-Dec nightly ROM. due to having messed up stuff, I decided to restore my backup. as said above, this will result in no mobile connection. but if I reflashed the zip file for 17-Dec nightly, this will fix the problem)
4. the hangouts included in the gapps (See link above to CM wiki) resulted in FCs when trying to make a video call. this was fixed by uninstalling hangouts using titanium and reinstalling it via the playstore.
5. I believe all official recoveries need updating to support 4.4 properly.
---------------------------------------------------------------------------
original message is below. you can see the problems I've encountered during testing.
just flashed the nightly for t0lte using TWRP 2.6.3.7 and somehow it can't see my SIM. Will be flashing again using latest CWM (6.0.4.1 as of now).
initial observations:
1. NTFS work on SD cards
2. 2 launchers are present (launcher and launcher3)
3. looks better than Jb (it could be placebo effect because kitkat is new)
update: definitely use CWM at least for t0lte. ROM has recognized my SIM.
update2: been playing around with the ROM and when I tried to access my NTFS-formatted SDcard, it cannot see. I had no problems at all with my SDcard using TWRP. I can even browse the folders inside it using file manager. I also had a problem with the built-in hangouts and video chat. I'm getting FCs.
update3: restoring from CWM nandroid backup = no cellular/mobile connect. Can't even call anyone.
update4: update to update3. I did lose cellular/mobile connectivity (phone can't find sim) BUT it can recognize my NTFS-formatted sdcard now!
update5: removing hangouts via titanium and then reinstalling the playstore version, I can make a video call.
update6: restore from nandroid (which gives me a working NTFS-formatted sdcard) and then reflashed the ROM. I got mobile signal but no sdcard. I guess I can always format it at as FAT32 which I'm doing now.
mrjayviper said:
update3: restoring from CWM nandroid backup = no cellular/mobile connect. Can't even call anyone.
update4: update to update3. I did lose cellular/mobile connectivity (phone can't find sim) BUT it can recognize my NTFS-formatted sdcard now!
Click to expand...
Click to collapse
Keep us posted. Would love to know how to sort out the data connection/sim issues before I flash.
Cheers.
Sheikx800 said:
Keep us posted. Would love to know how to sort out the data connection/sim issues before I flash.
Cheers.
Click to expand...
Click to collapse
gave up on making an NTFS-formatted sdcard work on a new flash. I'm formatting my sdcard now to FAT32. It'll probably be fixed down the road.
and I think flashing the ROM after restoring from nandroid backup will bring back mobile signal. At least that's my conclusion. But I do get a signal only if I use CWM.
Yea twrp 2.3.6.7 is buggy. Look for twrp 2.3.6.1, it's modified and will work with cellular signal. Keep us posted.
The modded twrp is linked on one of the last pages in the beanstalk thread iirc
Sent from my GT-N7105 using XDA Premium 4 mobile app
updated 2nd post to give some tips on how to install ROM properly. seems to be working nicely now. That said, I don't have much app/games installed on my phone compared to my tablet (50-60 apps on the phone compared to 90+ on the tablet. mostly games).
a sample list of apps installed on phone are dashclock, lightflow, dynamicnotifications, various messaging. various Google apps and 1 game.
Installed with latest CWM and Data works great, no issues with Calls / LTE etc.
ROM seems really good so far, using Google's OK Google is fun but does tend to drain the battery faster, that said I will switch to a different kernel as I miss Viper so will most likely go with Devil, hopefully it helps with the battery.
I've never had an issue with CWM, I upgraded to the latest version using ROM Manager.
My tip for flashing is to always wipe perform a full wipe plus Cache, Davlik and System before flashing and Cache, Davlik after.
Miss some features / tweaks from other Roms but I know that CM is the best stock experience out there so no problems there.
IMO no issues running as a daily driver.
Proximity sensor not working. Is it just me or...?
Tapatalk-kal küldve az én GT-N7105-el
I had problems to are you running any other kernels or are you on the stock one?
Sent from my GT-N7105 using XDA Premium 4 mobile app
CWM 6.0.3.1 Touch (I think!) doesn't work, got bad flash error 7 (I think!) every time.
ROM manager update to 6.0.4.1 to non-touch* worked like a charm.
(*because I'm both tight and lazy)
---------- Post added at 10:14 PM ---------- Previous post was at 10:04 PM ----------
richyy74 said:
Proximity sensor not working. Is it just me or...?
Click to expand...
Click to collapse
Definitely not working on a clean install, with a few apps installed.
According to a test app the light sensor is responding but the prox is not.
Camera app is buggy, useless in fact. 3rd party camera is fine temporary replacement.
Facebook edit post doesn't allow cursor placement, facebook app 4.4 problem I assume.
Is anyone able to successfully set the DPI to another value in build.prop? Mine always defaults to 320 after each reboot.
Update:
I seem to be able to edit/save build.prop changes fine in 12/07/13 nightly.
Had the same flash error 7 corruption had boot loop into recovery and had to use a nand backup to get back. Did a clean install, and the process went well. Only issues so far are my Microsd can't be seen. And can't manage to get the 'Ok google' stuff working. A few random crashes but overall working well so far.
So would love some help with the Microsd issue as this is quite important?
Sent from my GT-N7105 using Tapatalk
leebag said:
Had the same flash error 7 corruption had boot loop into recovery and had to use a nand backup to get back. Did a clean install, and the process went well. Only issues so far are my Microsd can't be seen. And can't manage to get the 'Ok google' stuff working. A few random crashes but overall working well so far.
So would love some help with the Microsd issue as this is quite important?
Sent from my GT-N7105 using Tapatalk
Click to expand...
Click to collapse
my NTFS-formatted sdcard can be seen when I use TWRP 2.6.3.7. not so with CWM 6.0.4.1.
I'm running the modified TWRP mentioned in page1 but my sdcard is still FAT32. I'll format my sdcard and see if it works.
I'm going back to CWM. just noticed all sorts of problems on my phone running the modified TWRP. :/ sucks!
No radio signal when flashing with TWRP 2.6.3.7. Flash again with CWM 6.0.4.1 radio is back. No problem with the external SD card (FAT32).
AkiraBBQ said:
No radio signal when flashing with TWRP 2.6.3.7. Flash again with CWM 6.0.4.1 radio is back. No problem with the external SD card (FAT32).
Click to expand...
Click to collapse
@mrjayviper Wasn't twrp 2.6.3.7 a bugged and accidental upload?
(At least people kept telling me a short while ago. )
Try the modded twrp 2.6.3.1 been linked a few days ago in the beanstalk tread
Sent from my GT-N7105 using XDA Premium 4 mobile app
Updated to the latest nightly and running Agni kernel and all running well.
Battery life is great, loving this ROM so far!
is anyone been able to successfully make a video call on hangouts? it's been FCing on me. using cwm and twrp.
I just tried the PA full gapps and no luck with that. thanks
I've installed a 4.3 unbranded rom (I9300UBUGML1_I9300UVOUGMK1_ARO) and it come with a lot of bloatware.. so i tried to uninstall some "system apps" but Link2SD says "mount: device or resource busy". i want to know what this means cause it worked fine with 4.1.2. Thanks for the help!
Is your device rooted?
If positive- try to use 'System app remover', works great for me
Sent from my GT-I9300 using Tapatalk
Hi,
I am also receiving a LINK2SD error after updating my Galaxy S3 to stock firmware 4.3
it worked fine when using stock firmware 4.1.2
The error reads:
Mount script cannot be created.
mount: Device or resource busy
ext4 may not be supported on your device.
Try FAT32 on the second partition
I notice that this new firmware has the ability to save apps to SD (I believe this is APP2SD support), but I want to use LINK2SD
Please can anyone who is also using stock firmware and managed to get LINK2SD working tell me how ?
don't know if this is anything to do with it, but I do not have an 'init.d' folder under /etc/ or /system/etc ... when I attempt to create a folder in either of the 2 locations I get a read-only error ..
Rolled back to 4.1.2
bah, too many other things also not working on 4.3, gave up, wasted 2 days
nand backup to 4.1.2 .. back where I was and all working again
"... if it ain't broke"
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..