So, I recently installed CM10.1 from Quarx, with the 2.6.32 kernel on my defy+, and I keep getting notifications
that my sd card is corrupted/blank, also apps that are on the SD keeps disappearing.
I already know about the mmcfix on this thread: http://forum.xda-developers.com/showthread.php?t=1596997
but i don't know if it will work on CM 10.1, also don't want to mess up since, i don't know why, my defy+ only
accepts custom roms if the stock rom is installed first and not one custom rom over another, and that would be
a very tedious and long process.
Anyone having the same problem, knows if the mentioned mmcfix work on CM10.1, or know a better way to fix this problem?
Am I the only one with this problem?
The mentioned fix is not compatible(says so in its thread).
You can try backing up the data from the card and formatting it from a pc and using it again
To install custom roms over each other you must wipe data, system and cache from twrp recovery, or use the wiper script. To downgrade to a ginger bread or earlier rom, one more step of converting data and cache to ext3 is also required, from the boot menu(tools: format to ext3)
Sent from my MB526 using Tapatalk 2
thekguy said:
The mentioned fix is not compatible(says so in its thread).
You can try backing up the data from the card and formatting it from a pc and using it again
To install custom roms over each other you must wipe data, system and cache from twrp recovery, or use the wiper script. To downgrade to a ginger bread or earlier rom, one more step of converting data and cache to ext3 is also required, from the boot menu(tools: format to ext3)
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
I already know about wiping everything, had other android phones in the past and this defy+ is the only one with this kind of problem with installing another roms, say if i try to install any rom that's different than the one currently being used, it bugs the whole phone and nothing works until a factory restore is done, but the real thing that keeps haunting me is the sdcard bug that keeps not being recognized, and as of late the phone stops working out of nowhere and only works again after deleting everything and reinstalling the same rom, which is making me think that my defy+ could be reaching it's end.
Igneom said:
I already know about wiping everything, had other android phones in the past and this defy+ is the only one with this kind of problem with installing another roms, say if i try to install any rom that's different than the one currently being used, it bugs the whole phone and nothing works until a factory restore is done, but the real thing that keeps haunting me is the sdcard bug that keeps not being recognized, and as of late the phone stops working out of nowhere and only works again after deleting everything and reinstalling the same rom, which is making me think that my defy+ could be reaching it's end.
Click to expand...
Click to collapse
If you tried CM10 then even I've experienced that bug. Don't know why that happens but even I've had to wipe everything and start again atleast 3-4 times in the past.
Igneom said:
I already know about wiping everything, had other android phones in the past and this defy+ is the only one with this kind of problem with installing another roms, say if i try to install any rom that's different than the one currently being used, it bugs the whole phone and nothing works until a factory restore is done, but the real thing that keeps haunting me is the sdcard bug that keeps not being recognized, and as of late the phone stops working out of nowhere and only works again after deleting everything and reinstalling the same rom, which is making me think that my defy+ could be reaching it's end.
Click to expand...
Click to collapse
Data and cache (and system optionally) must be wiped between switching roms for best results, since 'dirty' installation of roms requires them to be similar as well. If wiping data does not fix your roms issue then it's indicative of eMMC issues(hardware). The sdcard bug seems to occur with only some classes of sdcards. If possible you could try a different sdcard to see if the problem is resolved. Your problem prima facie does not appear to be linked to your mobile hardware.
Related
So for the last 5 days I had some very weird problems with my phone. About 2 weeks ago I started with my first Cronos Rom and it worked great. I flashed 1.5 and 1.5.1 without problems and I used it without an ext partition all the time. But then the problems started. When I wiped my whole phone and tried to reinstall 1.5.1 JIT, the phone didnt boot anymore (stuck on the "Android" bootscreen). I wiped again and again, tried 1.5.1 without JIT, 1.5 etc, but I couldt get the phone to work. Nothing worked, so I created an ext partition and tried again. It worked. My phone started and I was able to use it for about a day without problems though I didnt want apps2sd. But then some other weird things happened. 3 Days ago I bought a bigger SD Card, partitioned it, wiped the whole phone and flashed 1.5.1 JIT. The phone started, but after I installed a few apps, I got an error message (installing xxx failed). I found out that theres an "repair ext" function, and it worked, but after I installed some more apps, the problem was back. The second problem was, that after rebooting the phone, more and more apps wouldnt start anymore (FC). The last problem that occured was an FC of the market app. After that, I wiped everything again, tried to flash 1.5.1 JIT, but it happened exactly the same like on the first time. Problems installing apps, FCs, stuck on boot etc.
I am totally down at the moment because I killed my whole weekend trying to get my phone working again. Could anyone please help my with this? I just dont understand what I did wrong. Shouldnt a complete wipe fix almost every problem? And I dont understand why I suddenly cant use my phone without an ext partition. Any Cronos version I try freezes on bootscreen without an ext patition. Is there any way to get my hero working again? Please please help me.
(PS: I also posted this on the Cronos Board.)
I would take out the sd card, wipe system and dalvik cache, and install some custom rom.
well, to make sure it is NOT your phone, did you try another ROM? Eliminate possible problems?
At least try something that is known and stable, like a stock rom, the Taiwain-rooted-repacks (not a rom based on it, but just the taiwan rom rooted) or good ol' MoDaCo 3.2 (based on 1.5 stock).
Til now I just tried the last 2 or 3 Cronos Roms, and as I said, they didnt work, but when I get home from work I'll try the Modaco Rom I used before.
I dont understand what this has to do with the Rom I use. I always wiped the whole phone, dalvik, etc. so shouldnt it just work like the first time I flashed it? No matter what Rom I use?
Another weird thing (could have something to do with this): After I wiped everything and flashed Cronos 1.5.1 JIT, the market still knew what apps I had installed last time. It showed my bought apps AND the apps I was able to install before the latest crash. So does this mean the phone wasnt wiped completely?
The market tracks your purchases and (free) downloads through your google account. So that's normal that the download-list is full.
But it might very well be that you didn't wipe correctly, although I'm curious how you manage to accomplish that. What is your current recovery?
The whole point about trying another ROM is elimination. It doesn't need to make sense, but you need to check things of the list.
There is something weird going on, so trying to solve it logically will only get you so far . Keep trying to narrow down the list of causes. Might well be a bug with Cronos 1.5, or the overclock not working these days because your phone is just a bit hotter than before, who knows.. Like I said: eliminate causes!
I'm using the newest AmonRa recovery to wipe the phone.
Theres one thing I forgot: Yesterday I flashed 1.5.1 without JIT, and then 1.5.1 JIT right after it (just rebooted a few times between). The phone worked great until my SD card crashed. In the taskbar it always showed me "checking for errors"(something like that, my phone's in german ), but in my PC and in the recovery the card worked like always, so I had to wipe the card and start again from the beginning.
Try another ROM , and if that doesn't work, try without SD card.
tombond said:
I'm using the newest AmonRa recovery to wipe the phone.
Theres one thing I forgot: Yesterday I flashed 1.5.1 without JIT, and then 1.5.1 JIT right after it (just rebooted a few times between). The phone worked great until my SD card crashed. In the taskbar it always showed me "checking for errors"(something like that, my phone's in german ), but in my PC and in the recovery the card worked like always, so I had to wipe the card and start again from the beginning.
Click to expand...
Click to collapse
Maybe sdcard faulty? What are the logs you get when booting up the phone?
Soooo, I wiped everything again and flashed Modaco 2.8 without an ext partition. It booted correctly, so I wiped the dalvik cache and flashed Cronos 1.5.1 JIT. It also booted (wow, first time it booted without ext since all the problems started to occur) but I instantly got FC's (phone app for example). Now I wiped completely again and flashed 1.5.1 JIT. I hope it boots, as I still dont have an ext partition. As soon as I know something new, I'm gonna tell you.
So now it seems like its working again. I was able to install all the apps I need without a single error and now I'm restoring my settings and contacts. Suddenly it even works without ext again.
I guess there was something very big f*ked up that I couldnt repair by simple wiping the phone. Very weird that just flashing Modaco got it running again. Now I have back my working phone with ultrafast Cronos Rom and without App2SD, perfect. At least till now I hope it keeps working.
Thanks for your help guys, I think I would have smashed the phone to the wall sooner or later. I never thought about flashing Modaco so I'm happy there are people like you.
Thanks again, and thanks to Feeyo for his unbelievable Rom.
PS: Can I uninstall, Facebook and Footprints without destroying everything again?
Yes, just delete both apps using ADB or use a root explorer, search both apps in System/app and delete them.
Or you could use the MoDaCo online kitchen for removing those apps.
I am running CM6 (with no bugs) and when I go to flash a different ROM after going through the splash screen when the phone is about to load and installing last bit, the message "android.process.media..." FC happens. I have looked and looked through XDA for a fix but have yet to find one.
I have rebooted after full wipe, no SD Card, wiping the SD Card etc. all to no avail.
As a note- the only reason I was going to flash a different ROM was to check 4G speeds in SF.
Does anyone know what is causing this?
Maximiano said:
I am running CM6 (with no bugs) and when I go to flash a different ROM after going through the splash screen when the phone is about to load and installing last bit, the message "android.process.media..." FC happens. I have looked and looked through XDA for a fix but have yet to find one.
I have rebooted after full wipe, no SD Card, wiping the SD Card etc. all to no avail.
As a note- the only reason I was going to flash a different ROM was to check 4G speeds in SF.
Does anyone know what is causing this?
Click to expand...
Click to collapse
Not exactly sure why it does this except knowing it doesnt happen when you start your device with the sd card out. I've had the same problem that I was finally able to fix.
Just nandroid backup your phone, wipe everything (Factory wipe/dalvik etc) and nandroid restore.
I tried every other thing imaginable and finally this fixed it as my last resort.
I'm happy I found this out as I was always having to nandroid back to an old backup every other month or so as once this starts FC'ing I'd never been able to make it stop without a full reload of the rom or nandroid restore...
Hi guys,
i was thinking that after flashing a new ROM and wiping everything, this issue will be gone. But isn't.
I cleaned contacts on everything (SIM, SD card, battery,...) no change. (it is also rebooting when there is no SIM and SD card)
Can you help me with this?
Biggest issue is that it happends in the morning, when alarm should be ringing
Here is the vid of the issue
http://www.youtube.com/watch?v=KwJtz76C8PI
Did you wipe system, data and cache? Not restoring from titanium backup?
If not, do that. Most issues like this are just some remaining data or some restored data.
Else try a different kernel, most have a undervoltage that works with almost all phones but might not work with yours. Add more voltage or switch kernel =)
Hope you manage it
sir did you try to use a different sd card to install the rom? just wondering because if this is a board problem i think it should at least boot properly or not at all. im not really an expert but i think that there is a problem with the flash
My DHD started rebooting randomly this weekend It's happening every now and then, but one time it was constantly rebooting until I was able to do a complete restart.
I'm using ARHD 6.1.2 atm, and will try 6.1.4 to see if it helps...
Yes, before flashing i always wipe cache, dalvik cache, data.
I am not using any software for restoring my data.
I tried another RADIO, but no change
AdamiX said:
Hi guys,
i was thinking that after flashing a new ROM and wiping everything, this issue will be gone. But isn't.
I cleaned contacts on everything (SIM, SD card, battery,...) no change. (it is also rebooting when there is no SIM and SD card)
Can you help me with this?
Biggest issue is that it happends in the morning, when alarm should be ringing
Here is the vid of the issue
Do you use any sort of CPU overclocker?
I had exactly the same problem, my fix was uninstalling SetCPU and flashing the Set_to_default_1GHz.zip
After this solved the problem I tried OC Daemon, which brought back the problem. Some CPU`s just cont handle overclocking or undervolting
Click to expand...
Click to collapse
If nothing happens with custom roms, go back to stock rom. Install an RUU. Then see what happens...
No i was not overclocking my CPU. Today i flashed original RUU, and i am going to send my phone to HTC. Because plastic cover is doing some sound, music jack is broken and the phone is rebooting. I think that they will change my motherboard.
Hi everyone
Not sure how, at which point and why, but I've screwed up installing new rom, and now while I can install whatever I want, latest CWM 5.5.04 installed, new roms while do start just fine, don't detect sim, battery shows at 0% full stop, etc...
It started with me wanting to update to latest Elite Rom 9.7 based on MIUI by Terramino. Tried 2 versions, multiple re-downloads, every time it would try to install from zip and just returned the install aborted, bad zip message.
At this point phone is wiped to factory reset, dalvik cache wiped, cache wiped, /system mounted and formatted, so ok, need something else...
Downloaded MIUI 2.1.20 (2.6.35 kernel like the one before reset), and that's when I noticed the problem, thought maybe didn't wipe something correctly, so again factory reset, wipe cache, format /system, retry - same issue, after that it's always the same result whether I use CM7, MIUI or whatever.
Following few threads loaded the 5.5.04 CWM in the end, and to my surprise to add to the problem - now when I mount SD card from within CWM to system - it shows with a cd icon in the system and is now read-only, so can't even add anything to it seemingly.
Booting to pink screen still gives debugging access to internal SD card of the phone via usb.
Any ideas from knowledgeable users as to how to fix this problem? Help greatly appreciated!
That elite rom is only for .32 kernel
you flashed it over official gb that's the prob
Sent from my U8800 using XDA Premium App
Thanks, figured that this was the case, just not sure why after trying to load back newer roms meant for .35 it's still messing it up.
Will do full reload of a kernel and get a proper rom to follow suit, hopefully it resolves the issue.
Hi Guys,
I am not sure if I am posting in the right place, but I could use some assistance on the Team EOS nightlies. They won't let me post in the DEV section yet, becuase I am mostly reader, not a poster. Anyway....
I've been running the EOS roms for a while, but I can't seem to run any nightly past 74. 74 runs great, when I tried to update to 75 (rom/gapps/wipe cache) it won't get past the "DUAL CORE" logo. I thought I bricked my xoom, but I am able to boot to recovery, reflash 74 (gapps/wipe) and it boot with no issue. I did a full wipe, and tried again with 76 but no joy (77 wasn't out at the time). I thought it was a problem with n75 and n76. I flashed back to n14 and it works fine, and I can upgrade back to n74. Tonight I tried to update again to n77, but still no dice. I let it sit for 15 minutes at the "Dual Core" logo, and all I noticed is that is got warm, but still no boot.
Any thoughts? All advise is welcome!
BTW, this is for a Stingray 4g xoom
And while I have your attention, I love the work you guys do, and this community, it really makes Android something special!
Weird. Try going into fastboot and do a full wipe of userdata, cache, and system. Then install. If need be, do a backup. This will totally wipe your device.
Wipe cache, wipe dalvik, flash ROM, flash GAPPS, fix permissions. Do it in that order and you should be fine.
Also make sure your using the latest GAPPS. It should be dated 2012-03-17.
Good Luck.
Still not working right, very frustrated, but I have new information
dellenrules said:
Wipe cache, wipe dalvik, flash ROM, flash GAPPS, fix permissions. Do it in that order and you should be fine.
Also make sure your using the latest GAPPS. It should be dated 2012-03-17.
Good Luck.
Click to expand...
Click to collapse
bigrushdog said:
Weird. Try going into fastboot and do a full wipe of userdata, cache, and system. Then install. If need be, do a backup. This will totally wipe your device.
Click to expand...
Click to collapse
Thanks to both of you. I did try this. What I have discovered so far is that some of the flashing fun I have been doing with my may have caused so minor issues with my external SD Card. I backed up the internal to it, and pulled it. I went through the process of nuking the xoom entirely. I.E. Wiped Cache, dalvik, full wipe, factory reset, reset permission, and deleted everything off the internal SD (wasn't in this order, but it all got done) I was able to flash N77, without GAPPS fine. It seemed to run faster with nothing else installed. Rebooted a few times, no problem. I was stoked. I flashed gapps, 03-17 version (the latest). factory reset again so that it was fresh and wiped the cache (just in case). It booted again no problems, ran me through initial config, and then began downloading my apps back. It seemed to run much faster than it ever did before.
Then I rebooted it, without doing any titanium backup restores, just fresh tablet, N77 with my 90 or so apps freshly installed from the market, and it froze again at the "Dual Core" boot screen. I waited hoping for some delayed joy, but none came.
So I went back through the process once again, factory reset, N77 install, wipe cache, install GAPPs. Booted.....initial config, auto downloaded 90 apps from market, reboot......dead.
So then I just flashed N74 again, wiped cache, install GAPPS, initial config, app download.....reboot.......works fine.
<general frustration directed at tablet, not anyone here/>
What gives???? I can't tell what the difference in internal apps in the ROM are that could be conflicting with the ones installed from the market.
Why the hell is N74 working and N77 not, when the apps in both ROMs look the same?
Why does N77 work great when the apps aren't restored?????
Why don't I make a million dollars?????
Why aren't I emperor of the universe???????????????
</general frustration directed at tablet, not anyone here>
Thanks much for all your help!
alright.... i have 2 suggestions these may not work and the second one is a pain in the butt to do but it got me out of a jam way back when i lost my softkeys no matter what i flashed
firstly.. in the sequence of your flashing throw in the 'format /system' see if that has any effect it is 'possible' the system is not being flashed correctly or it could be possible that it is getting corrupted and causing the bootloops (i always format system when full wiping)
second... and this is a pain.. but you can always try flashing back to STOCK... there could be other factors that aren't being flashed or fixed correctly causing ya problems... you can then go through the process and flash directly to the latest build... as i noted earlier this fixed a problem that nothing else could for me and has helped others but really this is a last last resort as it takes alot of time and screwing around
lastly... i have no idea sorry these are all i can input.. if possible can always try and use logcat while booting to see what is causing the crash if im not mistaken and upload a log and one of the devs may be able to have a look at it...
I Would stop dinking around with n77 and go to n90 I had the same issues around those nightly numbers, so I went all the way back to stock... (honeycomb) didn't fix it but I redid the whole install on a higher number and it seems to work itself out..... long story short try another maybe the 1.0 stable by them.
fkntwizted said:
I Would stop dinking around with n77 and go to n90 I had the same issues around those nightly numbers, so I went all the way back to stock... (honeycomb) didn't fix it but I redid the whole install on a higher number and it seems to work itself out..... long story short try another maybe the 1.0 stable by them.
Click to expand...
Click to collapse
He has the STINGRAY not the WINGRAY Xoom.
N77 is the latest for the 4G version. The version he has.
Read the OP
EOS Nightlies hate my xoom, my Xoom wanted CM9 I guess
joshndroid said:
alright.... i have 2 suggestions these may not work and the second one is a pain in the butt to do but it got me out of a jam way back when i lost my softkeys no matter what i flashed
firstly.. in the sequence of your flashing throw in the 'format /system' see if that has any effect it is 'possible' the system is not being flashed correctly or it could be possible that it is getting corrupted and causing the bootloops (i always format system when full wiping)
second... and this is a pain.. but you can always try flashing back to STOCK... there could be other factors that aren't being flashed or fixed correctly causing ya problems... you can then go through the process and flash directly to the latest build... as i noted earlier this fixed a problem that nothing else could for me and has helped others but really this is a last last resort as it takes alot of time and screwing around
lastly... i have no idea sorry these are all i can input.. if possible can always try and use logcat while booting to see what is causing the crash if im not mistaken and upload a log and one of the devs may be able to have a look at it...
Click to expand...
Click to collapse
Thanks much for this. I had already attempted the formatting of everything except the SD card before.....but for sh*ts and giggles I tried it one more time. unfortunately that didn't work.
Using the second option, of reverting stock, I went through sleeplessnija's tutorial on reverting. It really didn't seem that bad, taking me longer to setup my work machine than it did to send the fastboot commands. I was able to get it to boot stock (of course I didn't re-lock it) just fine, and it was quick....so it seems like my hardware is fine.
I used fastboot to put the replacement tiamat recovery, and formatted everything in the mounts menu again. I also mounted my SD card as USB storage and used the full format for it under windows. Then i copied N77 and GAPPS back to it, and re-installed them. It got to the second boot logo (first was the shaking team eos, the second is the square thing with rounded corners that moves). It hung for about 10 minutes, and I shut it off. annoyed.
So I went back into recovery, mounted my SD for USB access from my desktop, and copied the unofficial (which I think is now official) CM9 distro from Team Rogue (Steady's Rom I believe?). I formatted everything, and wiped everything (except the SD) again, and installed CM9 and gapps. Booted fine. Configured account, downloaded 90 apps, rebooted, no problems. Played with it for a while, rebooted....no problems.
I like that my xoom is back up and running......however it seemed that Steadies rom is just a little less fully featured than Team EOS. THAT IS NOT A KNOCK AGAINST TEAM ROGUE OR CM9.....my Xoom is working again (so far) thanks to him (them), and I run CM9 on my AT&T GSII. I just really like Team EOS on my Xoom, and have been with them since the beginning. I would love to know why my xoom suddenly hates the latest nightlies (everything since 74).
Edit: I forgot to ask, Joshndroid.....you mentioned running logcat to see what going on. If it can't boot past the dual core logo or the second boot logo from Team EOS....how do I get the logs? I am not familiar with android's logging.....even though I am a flash-a-holic. I am just thinking that if this is happening to me, maybe I can help out the devs (and myself, and maybe someone else) with the log output.
Edit 2: And Josh.....I forgot to tell you .....good call on the revert to stock answer. I didn't think about that before and thought I was screwed!
Thanks!!