I have rooted sgs3 with android 4.1.1.
My problem start after when I root it. When I turn wifi ON everything works fine, but when I turn it off it's going offline and stuck in this mode and wont turn off complete. Then i can't do nothing with wifi.
Someone got same problem or know solution?
Define not off complete please .
jje
I upload 2 screenshots.
It stays in half dark view and nothing change. I must restart phone to turn on wifi again...
Sent from my GT-I9300
hawaiiek said:
I upload 2 screenshots.
It stays in half dark view and nothing change. I must restart phone to turn on wifi again...
Sent from my GT-I9300
Click to expand...
Click to collapse
uninstall WIFIKILL and stop killing hoggers,wipe cache and dalvik cache ,Reboot done and next time use search, Duplicated Thread
nhariamine
Do the following steps below:
- Boot to CWM recovery
- wipe cache partition
- wipe dalvik cache (under advanced)
- fix permissions (under advanced)
- reboot system now
saywhatt said:
Do the following steps below:
- Boot to CWM recovery
- wipe cache partition
- wipe dalvik cache (under advanced)
- fix permissions (under advanced)
- reboot system now
Click to expand...
Click to collapse
So I've got exactly the same problem, tried scubbing Dalvik and cache, fixing permissions, reboots, de-rooting, rerooting, you name it. I'm running a kernel dated 21/8, build i9300XXDLJ4, which is I believe the current UK build. Short of flashing another kernel, I take it my best bet is to replace the unit?
So I sorted this by, I **** you not, disabling USB debugging and developer options. Wut.
So, turns out that didn't fix it. GREEEAT. Going to flash the latest firmware again to see if it fixes it, or else it's back to the store.
So I flashed this instead using ODIN:
http://androidromupdate.com/2012/10/24/upgrade-uk-samsung-galaxy-s3-jelly-bean-i9300xxdlj4/
It has a more up-to-date kernel than the one that the original JB update I did over KIES had, and so far it hasn't repeated the problem. We'll see how it goes over the next few days.
Related
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.
i am using Onecosmic latest ICS rom and his provided kneral
is it the rom problem or i can setting turn the screen off while charging the phone?thanks~
Screen on When Charging
Foodil,
I had this problem way back when I was on one of the MIUI roms.
My fix: reboot to recovery and fix permissions. If this doesn't work then...
backup rom and SMS/MMS
reboot to recovery
nandroid backup (advanced)
wipe dalvick cache and wipe cache
format system
reflash rom
fix permissions
reboot system.
Good luck!
SGH-T959 ICS Passion 10.6
papa.steve
Check the setting that enables/disables this. There is an option to leave the screen on while charging. Settings/applications/developement. Uncheck stay awake..
papa.steve said:
Foodil,
I had this problem way back when I was on one of the MIUI roms.
My fix: reboot to recovery and fix permissions. If this doesn't work then...
backup rom and SMS/MMS
reboot to recovery
nandroid backup (advanced)
wipe dalvick cache and wipe cache
format system
reflash rom
fix permissions
reboot system.
Good luck!
SGH-T959 ICS Passion 10.6
papa.steve
Click to expand...
Click to collapse
Thankyou.
i have tried your suggestion
at first fix permission not works, so i reflash the rom following the suggestion apporach ( i can't find nandroid backup (advanced) in the cwm , so i skipped it)
however, this time the mobile phone will turn on (not just screen, it will just boot and enter the android system) when i charging..
so i try install another rom (passion v10.6) . The problem sloved , but i think this rom is worse than the onecomic one . It consume more battery and ram.
So now i will flash back to onecomic one to see what will happen. It is just tedious work.
thanks, eweo911
That item is unchecked but the phone screen still keeping on.
This problem seems not that simple
foodil said:
thanks, eweo911
That item is unchecked but the phone screen still keeping on.
This problem seems not that simple
Click to expand...
Click to collapse
More than likely you can modify a file to fix that. Now the question is what file and what to change.
It seems some of the user using that rom have the same problem.
Just wait for the next release
thanks.
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.
Met a problem with my GT-I9300. When I shut the phone off it just reboots. The phone was rooted and running a custom rom when this started. Now I have unrooted with mobile Odin and flashed a official firmware but the problem persists.
I have even tried a battery pull. When battery is inserted again the phone remains off til I push the powerbutton. But when I try to turn it off after this it just reboots again.
Anyone else had this? Tips on what to do?
I've never had any luck fixing this problem. I always had to wipe and flash. However, as a temporary fix, you can power off from recovery.
Sent from my GT-I9300 using Tapatalk
can I ask what you are doing when you turn it off?
Sent from the asylum
Just to clarify, even wipe the phone and restore it to stock completely by flashing official firmware doesnt solve it.
When I turn it off I hold powerbutton til i get the powermenu. From there I choose "turn off". Phone does what it should, screen goes off and everything, only a few seconds later the phone boots again.
basse10000 said:
Just to clarify, even wipe the phone and restore it to stock completely by flashing official firmware doesnt solve it.
When I turn it off I hold powerbutton til i get the powermenu. From there I choose "turn off". Phone does what it should, screen goes off and everything, only a few seconds later the phone boots again.
Click to expand...
Click to collapse
If the phone was totally cleaned formatted sd card and stock firmware installed then its a hardware problem .
But my guess is it as not totally clean .
....................................
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
jje
I have now tried to wipe and format sys/data/cach/sd in cwm. Flashed stock firmware via odin. Still same issue. Guess its hardware.
Thanks anyway.
This may sound strange, but is this the clock problem the Desire HD had.
In time settings, uncheck the auto update.
Change time & date to something random.
Power off and pull the battery before it reboots.
Give it a min, power up, reselect auto update and reboot.
Should be good to go. If its the same problem that is.
Sent from the App that Time Forgot.
It also happens to me yesterday, I wipe cache, system, data, reinstall roms (CM and AOKP) and is still happening
r0uzic said:
It also happens to me yesterday, I wipe cache, system, data, reinstall roms (CM and AOKP) and is still happening
Click to expand...
Click to collapse
It happened also to me once. I flashed my rom in the same order as you did. But what my problem solved was, I made a wipe AFTER I installed the ROM. After that, I didn't had this issue anymore.
These are the steps I did...
- Get into the CWM recovery
- Wipe Data/factory reset
- Wipe Cache
- Wipe Dalvik-Cache
Hope it works also to you...
Solved
I solved it by flashing a later official firmware - XXALF6.
Darkrider82 said:
It happened also to me once. I flashed my rom in the same order as you did. But what my problem solved was, I made a wipe AFTER I installed the ROM. After that, I didn't had this issue anymore.
These are the steps I did...
- Get into the CWM recovery
- Wipe Data/factory reset
- Wipe Cache
- Wipe Dalvik-Cache
Hope it works also to you...
Click to expand...
Click to collapse
basse10000 said:
I solved it by flashing a later official firmware - XXALF6.
Click to expand...
Click to collapse
Thanks, I'll try twice methods
Update: It's rare, but has returned to work normal and I doing nothing
Hello,
i found a solution for that problem. You will lose some sd card files.
go to settings-storage-others (or other) and mark all files. Then delete them an go to downloadmode to reflash you firmware. Reboot and the problem is missing.
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.