Has anyone ever found a solution to this bug under CM7? I've searched and all threads end with no answer.
Thanks,
Jim
jmdearras said:
Has anyone ever found a solution to this bug under CM7? I've searched and all threads end with no answer.
Thanks,
Jim
Click to expand...
Click to collapse
+1 on this problem.
Boot up in clockwork, go to mounts and storage, mount system, mount data. Back out to cwm main menu, wipe cache partition, go into cwm advanced menu and wipe dalvik cache, back to cwm main menu and choose reboot system now.
That fixed the widget loading error for me with CM7.
Sent from my CM7 OC'd G-Tablet
hitekredneck said:
Boot up in clockwork, go to mounts and storage, mount system, mount data. Back out to cwm main menu, wipe cache partition, go into cwm advanced menu and wipe dalvik cache, back to cwm main menu and choose reboot system now.
That fixed the widget loading error for me with CM7.
Sent from my CM7 OC'd G-Tablet
Click to expand...
Click to collapse
Tried that. Nothing fixes it permanently, they still vanish after a few reboots. I have wiped my gtab, and installed fresh several times, always fails after a few reboots.
jmdearras said:
Tried that. Nothing fixes it permanently, they still vanish after a few reboots. I have wiped my gtab, and installed fresh several times, always fails after a few reboots.
Click to expand...
Click to collapse
I know you say you have wiped and installed fresh several times, but have you tried this -> After a wipe and fresh install, wait about ten minutes on first boot for everything to settle in, then shut down, boot into CWM and do a factory reset on the new install that you just performed. Then boot back into the rom and wait for everything to settle in again before attempting any installations of apps or widgets.
Just something to try.
Have the same issue. Widgets crash after a few reboots (I would understand if it crash every reboot but NO you will need several )
any proven solution????
gtab_11 said:
any proven solution????
Click to expand...
Click to collapse
Try the "fix" suggested in this thread. Basically, a) run fix_permissions and b) take a backup of /data/system/appwidgets.xml to restore at a later date.
That fixed most of my widgets. Not all though. One of them completely disappeared instead of showing "Problem loading gadget". I'll go over the procedure again and see how it goes.
Basically, I booted in recovery, cleared cache and dalvik cache, fixed permissions, and rebooted.
---------- Post added at 10:54 AM ---------- Previous post was at 10:44 AM ----------
aisPanais said:
That fixed most of my widgets. Not all though. One of them completely disappeared instead of showing "Problem loading gadget". I'll go over the procedure again and see how it goes.
Basically, I booted in recovery, cleared cache and dalvik cache, fixed permissions, and rebooted.
Click to expand...
Click to collapse
Went over it again and it fixed the last problematic widget. Let's see if it sticks.
Related
ok i attempted to install BAMF Remix v1.6. is there a way to confirm that this was flashed properly? i still have bloatware like blockbuster etc. i think i missed something along the way.
is it possible i just did a factory reset?
thanks
markkal123 said:
ok i attempted to install BAMF Remix v1.6. is there a way to confirm that this was flashed properly? i still have bloatware like blockbuster etc. i think i missed something along the way.
is it possible i just did a factory reset?
thanks
Click to expand...
Click to collapse
How did you flash it? Did you do it through ROM Manager? Did you wipe data and cache? Something's not quite right, the bloatware should be gone.
i am having the same issue. are you also missing stuff like the notification power control widget?
io flashed mine from cwm and wiped everything.
phatjames167 said:
i am having the same issue. are you also missing stuff like the notification power control widget?
io flashed mine from cwm and wiped everything.
Click to expand...
Click to collapse
Hmm. Count me in on this one too then: http://forum.xda-developers.com/showthread.php?t=1069980
count me in as part of the galactically stupid. (worse than nube)
go to here http://forum.xda-developers.com/showthread.php?t=1027804
download and install
BAMF Remix v1.6:http://tinyurl.com/3wkpmh3
MD5: CF461768DBC8A729CB7D28B97D5B8717
download and install
BAMF Remix Patch 1.6.2: http://tinyurl.com/3ntawj6
MD5: d45d597d42d40ca31319786cfb9450dc
i was only installing BAMF Remix Patch 1.6.2 not realinzing it is only a patch to BAMF Remix v1.6!!!
i booted into ClockworkMod
everything now appears to be as expected for the ROM
thanks for your help.
it looks like this worked. when it first boots though the wallpaper is black with a red streak but then changes to the default wallpaper from stock. is that normal?
That got me closer to everything being 100%. I installed Remix 1.6 and 1.6.2 and I noticed changes like the battery indicator and the market being black (very nice, btw), but I still have bloat & the notification bar is missing. Wiped Dalvic Cache both times, wiped data fully when I installed the main BAMF 1.6 at the start of this.
aerojad said:
That got me closer to everything being 100%. I installed Remix 1.6 and 1.6.2 and I noticed changes like the battery indicator and the market being black (very nice, btw), but I still have bloat & the notification bar is missing. Wiped Dalvic Cache both times, wiped data fully when I installed the main BAMF 1.6 at the start of this.
Click to expand...
Click to collapse
I had this same exact issue. The cause of mine was installing through ROM Manager. I was wiping everything that should be just like you are it sounds. The fix I found was rebooting into recovery and flashing manually. There is an option in ROM manager to reboot into recovery. Once you are into recover wipe data/cache three times. Wipe cache partition three times. Wipe Davlik Cache(Under advanced menu) three times. I usually wipe three just to be sure everything is clean before I flash. Flash 1.6. Now load 1.6.3(since it's out now) onto the SD card. Boot into recovery again, wipe cache partion and davlik cache three times. Install 1.6.3.
devindpotts said:
I had this same exact issue. The cause of mine was installing through ROM Manager. I was wiping everything that should be just like you are it sounds. The fix I found was rebooting into recovery and flashing manually. There is an option in ROM manager to reboot into recovery. Once you are into recover wipe data/cache three times. Wipe cache partition three times. Wipe Davlik Cache(Under advanced menu) three times. I usually wipe three just to be sure everything is clean before I flash. Flash 1.6. Now load 1.6.3(since it's out now) onto the SD card. Boot into recovery again, wipe cache partion and davlik cache three times. Install 1.6.3.
Click to expand...
Click to collapse
I did the install through the ROM manager, so I'm hoping your solution works out. I'll give it a try this evening. Thanks for the suggestion!
aerojad said:
I did the install through the ROM manager, so I'm hoping your solution works out. I'll give it a try this evening. Thanks for the suggestion!
Click to expand...
Click to collapse
Actually I just looked and 1.6.3 is an entire rom instead of a patch so you can skip flashing 1.6. And just flash 1.6.3 after wiping data/cache/davlik cache.
devindpotts said:
Actually I just looked and 1.6.3 is an entire rom instead of a patch so you can skip flashing 1.6. And just flash 1.6.3 after wiping data/cache/davlik cache.
Click to expand...
Click to collapse
Thank you very much, your suggestions were exactly what I was looking for. Now have that full BAMF Remix experience
aerojad said:
Thank you very much, your suggestions were exactly what I was looking for. Now have that full BAMF Remix experience
Click to expand...
Click to collapse
Not a problem at all, enjoy.
devindpotts said:
I had this same exact issue. The cause of mine was installing through ROM Manager. I was wiping everything that should be just like you are it sounds. The fix I found was rebooting into recovery and flashing manually. There is an option in ROM manager to reboot into recovery. Once you are into recover wipe data/cache three times. Wipe cache partition three times. Wipe Davlik Cache(Under advanced menu) three times. I usually wipe three just to be sure everything is clean before I flash. Flash 1.6. Now load 1.6.3(since it's out now) onto the SD card. Boot into recovery again, wipe cache partion and davlik cache three times. Install 1.6.3.
Click to expand...
Click to collapse
I had the same issue and this worked for me. I just reflashed 1.6.3 directly from CWR (after wiping everything 3x) and everything worked correctly (notification widget, etc.)
thanks for the help
I am glad I found this, I had this same issue and it was driving me nuts. I'm reinstalling now and hopefully everything just comes out perfect.
I am adding this to my list of why I don't like RM.
after flashing cm7 pre beta #2 for the atrix my for just sits in the motorola bootlogo. I can get back to recovery mode but I dont have any backups to restore from. Ive whipped the data and cache and reflashed it but it dont fix it. Is there a way to facotory restore or other options?
Thanks for any help
NWilz said:
after flashing cm7 pre beta #2 for the atrix my for just sits in the motorola bootlogo. I can get back to recovery mode but I dont have any backups to restore from. Ive whipped the data and cache and reflashed it but it dont fix it. Is there a way to facotory restore or other options?
Thanks for any help
Click to expand...
Click to collapse
Did you wipe the dalvik cache? If you didn't, go into recovery, then click advanced, then click wipe dalvik cache.
i whipped dalvik cache, still sits in the boot logo
NWilz said:
i whipped dalvik cache, still sits in the boot logo
Click to expand...
Click to collapse
Maybe you've had a bad install. Try wiping everything again, and then re-installing. After you've reinstalled, wipe everything again just for good measure.
This happened to me before, just download CM7 again onto your sd card and then go into your recovery menu and wipe dalvik, wipe cache, wipe data, then try reflashing the new CM7 zip you have on your sd card and reboot
Sent from my MB860 using Tapatalk
I think this maybe my problem
http://forum.xda-developers.com/showthread.php?t=1219956
cause I can only access my internal memory, but I have a bigger problem it says my battery is to low to flash and it doesnt seem to be charging. Iis there any mode under those options when you hold power and down volume that would charge the phone?
Try the method I posted on that thread to charge your phone, its a video on youtube that tells you how to.
I was flashing CM9 from CM7 on my Motorola Defy, botched it up intially due to a slip of my finger which led to me to Clear the cache first. But then I restarted the entire process by Clearing Data -> Installing -> Flashing Kernel and so on...
But when I tried to clear the Dalvik Cache, the phone didn't delete it. It didn't give me a message that it wiped the cache, but it didn't say otherwise either. This led me to believe that the cache just didn't exist anymore.
As a result, I'm unable to install apps - Says there is no memory and I need to make more. Also, everytime the phone comes on is treated as the first time. It takes me through the whole process of Setting up an account and everything. This has rendered my phone obsolete.
Please help me!
Thanks in advance.
~Bloo (newb) ^_^
EDIT: Solved, reflashed the stock SBF. But is this the only solution? :O
Have you tried doing a clean install?
Honestly, any time you get issues like this where the phone gets stuck (either in a boot loop or resetting your settings every boot, etc.) it's best to just wipe/factory reset and re-flash everything.
This is also why it's important to make backups so that if something does go wrong when flashing, you can just restore and be good to go.
If by a clean install you mean starting from wiping data, flashing the ROM on again and going on to clear cache and dalvik cache; Yes I did that. But I'm unable to clear the cache.
I ought to have created a backup, didn't.
So how can I go about fixing this issue?
bloomark said:
If by a clean install you mean starting from wiping data, flashing the ROM on again and going on to clear cache and dalvik cache; Yes I did that. But I'm unable to clear the cache.
I ought to have created a backup, didn't.
So how can I go about fixing this issue?
Click to expand...
Click to collapse
A clean install seems like the main thing to do (again). If you want, you could try going back to stock.
Installing again didn't do the job. Still can't wipe Dalvik Cache and the Setting still reset on every boot.
The chief problem I have with this is that I'm in India whereas the stock baseband is Europe. So to change it I've to reboot and can't do that because it resets every boot. @[email protected]
Is it a problem with the Kernel?
I'll go back to stock, but it seems a bit complex and I'm afraid I'll brick my phone. :'(
EDIT: Felt it was important to mention that the boot screen still shows CM7.1 and not CM9
I have a similiar problem.
Everytime I choose clear Dalvik men, it looks like he freezes for about a second or two. Then you see the 'menu' no - no - no - no - yes, clear dalvik memory - no - no - no (or something like that) pop up for half a second, and then it is gone. Is this a problem in CWM? Or is it in my phone?
I have a similar problem too! When I hit 'clear dalvik cache', the CWM screen just flashed once and nothing happened, and nothing says 'cleared dalvik cache' or similar...
Me too , how to solve it? Can anyone help? Mine is samsung gio
I have an issue similar to yours with my tablet (samsung galaxy tab 4 10.1 or SM-T430NU) in which it doesn't mount /data and it doesn't let me wipe to factory. Still haven't found how to fix this.
Hi,
I really don't understand what just happened with my Galaxy S2. It was on and well, then crashed for no reason and displayed two error messages in a loop: "Falcon Pro has stopped unexpectedly" (that's my Twitter client) and "android.process.media has stopped unexpectedly". I had not even the time to click on "OK" before the other message appeared and so on, so I forced the reboot by pressing the power button.
Now the phone is stuck on the "S2" logo when booting.
I tried wiping the parition cache, it did nothing.
I have Android 4.0.something, Samsung/Bouygues original rom with Siyah kernel.
What can I do (without losing all my data if possible)?
Thank you...
Zuddi said:
Hi,
I really don't understand what just happened with my Galaxy S2. It was on and well, then crashed for no reason and displayed two error messages in a loop: "Falcon Pro has stopped unexpectedly" (that's my Twitter client) and "android.process.media has stopped unexpectedly". I had not even the time to click on "OK" before the other message appeared and so on, so I forced the reboot by pressing the power button.
Now the phone is stuck on the "S2" logo when booting.
I tried wiping the parition cache, it did nothing.
I have Android 4.0.something, Samsung/Bouygues original rom with Siyah kernel.
What can I do (without losing all my data if possible)?
Thank you...
Click to expand...
Click to collapse
Do you still have the original rom zip on your sd card? If you do, you could try a dirty flash of it on top of your current setup. Wipe cache/dalvik cache and then flash the rom zip. Seeing as you're having FC's, you could also fix permissions in recovery, can't hurt.
Edit: Note, that's attempting to not wipe your data. If that doesn't work you'll likely have to factory reset from recovery.
Hopper8 said:
Do you still have the original rom zip on your sd card? If you do, you could try a dirty flash of it on top of your current setup. Wipe cache/dalvik cache and then flash the rom zip. Seeing as you're having FC's, you could also fix permissions in recovery, can't hurt.
Edit: Note, that's attempting to not wipe your data. If that doesn't work you'll likely have to factory reset from recovery.
Click to expand...
Click to collapse
No, I didn't have any rom on my card...
I tried to wipe dalvik, fix permission, wipe cache and reboot but the problem was not fixed.
So I said goodbye to my data, did a factory reset and that worked. Phew!
Thank you
Howdy partners, not sure if I should have started my own thread...let me know if that is proper procedure please. I've already read the recent boot loop thread by vlmaadir t=2558286, but I'm unsure as to the applicability of the solutions in that thread to my problem.
I'm in a similar situation as the vlmaadir, except I've been running the most recent stock ROM (UCMD8) and have rooted via framaroot and flashed the AJKv4.9 - NoSwap Kernal successfully around 12/5/2013. Of course I've yet to do a backup of the OS or apps, but pics/vids/contacts were all recently backed up.
About two weeks ago I started noticing random reboots, but wasn't really sure what to make of that, never any boot looping though. Well this morning the phone was working when i woke (phone alarm raised me from the dead on time) and had approx. 70% battery, but by the time I got to work, the phone had apparently powered off.
When I powered it back on, it took a several minutes to boot up (normally around 45sec-1min), once booted the battery showed about 10-15% (in the red). The few apps I opened worked (naked browser, outlook), but were a bit laggy. I decided to restart the phone from the regular power menu to see if that would help the laggy/battery issue, and upon restart I am now solidly stuck in my 1st android boot loop!!!
I can boot into CWM recovery, but have yet to do any wiping as I wanted to seek a bit of advice here 1st.
If anyone has any pointers, I'm listening.
Thanks!
I would 1st try a wipe cache and wipe dalvik cache from cwm recovery and see if it will reboot.
If it doesn't then u will probably have to wipe data/factory reset from cwm recovery and then reboot.
If ya have been runnin good for a while with AJ's kernel, then a rogue app may be the cause of ur problem.
R u tweakin anything in the kernel through stweaks apk ?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
4-2ndtwin said:
I would 1st try a wipe cache and wipe dalvik cache from cwm recovery and see if it will reboot.
If it doesn't then u will probably have to wipe data/factory reset from cwm recovery and then reboot.
If ya have been runnin good for a while with AJ's kernel, then a rogue app may be the cause of ur problem.
R u tweakin anything in the kernel through stweaks apk ?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Thanks 4-2.
If I have to go wipe data/factory reset, should i have to re-flash the rom and kernel?
I've been running the AJK for about a month, no tweaks. Like I said in the OP, I had noticed some random reboots in the past few weeks and at some point over Christmas day, when I was doing a good bit of pic/video work on my phone, it came up with a message that the internal storage memory was low. I knew this wasn't the case, at least as far as the entire internal memory, which had around 3 gigs free. Just a few strange things I've noticed since having AJK in place.
Are there any other good kernels for stock 4.1.2? AJK seemed to be the go-to of main stock and custom ROM folks.
I did a cache wipe, but when I enter the dalvik wipe confirm menu, the output shows
E:unknown volume for path [/sd-ext]
and when I confirm yes, wipe dalvik, the screen goes black, then the phone restarts into the boot loop.
Any one know what is up here?
^^
Doing and wipe data/factory reset in the cwm recovery will just return the Stock MD8 to just full stock, as if u first installed it through Odin or att official, Except u will still have the AJ kernel. There is no need to reflash the rom as u say.
But if u cannot find an app that is causing the problem, then a complete Odin flash to Stock MD8 should help in the troubleshooting.
---------- Post added at 07:40 PM ---------- Previous post was at 07:37 PM ----------
wolfboogie said:
I did a cache wipe, but when I enter the dalvik wipe confirm menu, the output shows
E:unknown volume for path [/sd-ext]
and when I confirm yes, wipe dalvik, the screen goes black, then the phone restarts into the boot loop.
Any one know what is up here?
Click to expand...
Click to collapse
The "E:unknown volume for path [/sd-ext]" is the norm from what i remember.
But not sure why choosing to wipe dalvik cache resulted in a bootloop.
Have ya tried the wipe data/factory reset yet ?
Just did a wipe data/factory reset and I got out of the boot loop! Now I just have to set the phone up like I had it once again! Boo!
Thanks for the input 4-2!!!
Glad ya got it going. :good:
If any other problems arise, just let us know. There are several good members around that are glad to help.