Hello, MS2 guys:
Sorry for starting a new question thread, this problem really bothered me these days.
I was installed CM7( for defy RC1 ) on my Milestone 2 three days ago, it's a triffic rom, but still, many hardwares do not work well. I tried many tricks in this forum but problems remain.
Debug mode/charge light/led notification/unstable wifi-connection/video playback/camera-related apps reboot the phone...etc.
Here comes the Notification LED problem:
*It turns bule on bootmenu first few times, after that, it still blue but very very dim, finally, it doesn't turn on at all;
*The guide thread says it go red-orange-blue when charging, but does not work for me, perhaps the light is too dim to recognize;
*when I slide out the keyboard on charging, notification LED goes bright suddenly.
I reflashed 2.2.2 UK SBF, double-wiped the device. But notification LED doesn't work any more, tested SMS/Coming Call/10-% battery, just never turn on.
Is this a hardware problem, or, like the no GSM signal problem before?
Thanks in advance.
Sorry again for my poor English.
Sent from my MotoA953 using XDA App
Have u tried reflashing other official firmwares? Did you do a complete user data/cache wipe before reflashing the firmware?
MegaBubbletea said:
Have u tried reflashing other official firmwares? Did you do a complete user data/cache wipe before reflashing the firmware?
Click to expand...
Click to collapse
Thanks for reply.
I haven't tried other SBFs, but I wiped data/cache with stock recovery completely.:'(
Sent from my MotoA953 using XDA App
MegaBubbletea said:
Have u tried reflashing other official firmwares? Did you do a complete user data/cache wipe before reflashing the firmware?
Click to expand...
Click to collapse
I wiped data/cache after reflash the firmware, Should I wipe it before flash the SBF?
Sent from my MotoA953 using XDA App
Related
Hey guys.. I am running frankenclean 2.6 voodoo, everything was fine. I flashed VA Green and it worked flawlessly. I flashed Super Light on top, didn't like it so restored to my frankenclean 2.6. At that point I tried to flash over to Honeycomb and thats when the fc loops started. I restored back again then just tried to restore my VA Green, it loads but as soon as I unlock the fc madness starts.... I am pretty new to all of this and would really appreciate it if someone could help a brotha out!
Thanks a lot!
Sent from my SCH-I500 using Tapatalk
Did you wipe data and cache and dalvik? Since restoring restores everything, its always best to wipe before doing so. Unless you did and it's FCing..?
TheSonicEmerald said:
Did you wipe data and cache and dalvik? Since restoring restores everything, its always best to wipe before doing so. Unless you did and it's FCing..?
Click to expand...
Click to collapse
Wiped everything man.. Just read in another thread that other people are having issues with the newer versions of sc. After installing their first theme (which works perfect) they are getting the boot loop issues with every theme from that point on. A guy over in themes has an answer for it, but I was having a hell of a time following his instructions..
I was running cm7 since it was first released. I got a new phone so i decided to give my atrix to my younger brother. The problem is after i went through the process of putting the phone back to stock, there now seems to be dead zones on the phone. For example i cannot press the w,e,s, keys. Can anyone help me or tell me if i've done something wrong?
I'm not sure you did anything wrong specifically. Did you make sure the clear all the cache? How did you put stock back on it (IE. flashed stock via CWM, moto fastboot, etc)?.
Boot into recovery, wipe dalvik cache, system cache, reflash your firmware of choice, reboot.
Sent from my MB860 using Tapatalk
Ive had numerous problems with cm7 for atrix but ive found that backup everything you need with titanium backup and then just reflash the rom and wipe the data and davlik cache and it should. But yh there are lots of issues with the cm7 rom for atrix but its still in beta so dont worry too much it will be ok when there are more updates
Sam
samdrake112 said:
But yh there are lots of issues with the cm7 rom for atrix but its still in beta so dont worry too much it will be ok when there are more updates
Click to expand...
Click to collapse
The CM7 beta does not have the issues that the OP described so please don't let him think that's the reason.
OP, re-flash your phone with a different ROM or with CM7 again and see if it still persists.
I'm having random reboots on my nexus s running stock ICS.
I'm getting at least once a day but sometimes 3-4.
This happens when the phone is idle and never during calls or when I use it.
Are you also having this problem? Do you think it might be a hardware problem?
That's odd. Never got any reboots on mine. Try reflashing ICS if your phone is rooted. If it isn't. Try a full wipe, including the SD card. Hope this is of some help.
Sent from my Nexus S using Tapatalk
I've already done a full wipe including the USB. Didn't solve the problem. I'm not rooted. Do you think I need to reflash the ICS?
donnieace said:
That's odd. Never got any reboots on mine. Try reflashing ICS if your phone is rooted. If it isn't. Try a full wipe, including the SD card. Hope this is of some help.
Sent from my Nexus S using Tapatalk[/QUOTE
agree with that, try wipe dalvik cache and reflashing ICS
Nexus S
Click to expand...
Click to collapse
It's possible it is one of the apps you have installed.
Root the dang thing, then flash AOKP ROM and Matr1x kernel, you won't get reboot.. I semipromise .. Really, AOKP is very stable.
Easy rooting guide at nexusshacks.com.
I am having the same problem prior to this after flashing stock ICS it reboot by itself...
After I rooted it. I did fullwipe and rebooted stock ICS it seems okay for the time being. Hopes this helps.
gwong76 said:
I am having the same problem prior to this after flashing stock ICS it reboot by itself...
After I rooted it. I did fullwipe and rebooted stock ICS it seems okay for the time being. Hopes this helps.
Click to expand...
Click to collapse
Thanks. I'll try to root and wipe during the weekend and update with results
Nexus S i9023
amir80 said:
Thanks. I'll try to root and wipe during the weekend and update with results
Click to expand...
Click to collapse
Hi!
I'm using i9023, and i have the same problem.
I tryd already CM9, Kangy, Stock 4.0.4, MIUI, and this dosn't solved my problem.
Random reboots 3-4 times a day.
Android 4.0.4 helped
Since I've updated to 4.0.4 I only saw one random reboot. It happened when my battery was almost empty.
I replaced with a new battery (original samsung) and I have not seen any reboots since
Phoenee said:
Hi!
I'm using i9023, and i have the same problem.
I tryd already CM9, Kangy, Stock 4.0.4, MIUI, and this dosn't solved my problem.
Random reboots 3-4 times a day.
Click to expand...
Click to collapse
Hi...
Try to full wipe ( wipe dalvik-cache, wipe cache and data) before and after flashing rom...
sent from my nexus s - xda
when i opened the camera app, the phone rebooted itself and now it is stuck on the bootanimation logo. This happened to me 3 times allready but it always goes back to normal. Anyone know what to do, i don't wanna factory reset it.
Tried restarting it with the power button, tried removing battery and i tried rebooting through phils CWM recovery and still always goes back to the bootanimation logo.
Plz help
I'm Using omega Rom V7 with the new adam kernel v1.3
Also my camera was fine with the stock kernel, i think the new adam kernel made my camera app worst.
Jason2k13 said:
when i opened the camera app, the phone rebooted itself and now it is stuck on the bootanimation logo. This happened to me 3 times allready but it always goes back to normal. Anyone know what to do, i don't wanna factory reset it.
Tried restarting it with the power button, tried removing battery and i tried rebooting through phils CWM recovery and still always goes back to the bootanimation logo.
Plz help
I'm Using omega Rom V7 with the new adam kernel v1.3
Click to expand...
Click to collapse
It might b problem of omega rom. Just reflash it while wiping data and caches.
Sent from my Disturbed™ Galaxy S4
Disturbed™ said:
It might b problem of omega rom. Just reflash it while wiping data and caches.
Sent from my Disturbed™ Galaxy S4
Click to expand...
Click to collapse
Can i re-flash omega rom, without wiping data? or will that cause trouble?
re: camera issue
Jason2k13 said:
Can i re-flash omega rom, without wiping data? or will that cause trouble?
Click to expand...
Click to collapse
If you don't want to do a full wipe don't even bother flashing it again.
The whole purpose of re-flashing is that you are having a problem with
the camera.
A clean install of Omega rom should clear it up.
But a dirty flash will make no difference at all.
Backup your apps using titanium backup or some other backup app so you don't loose your apps.
Good luck!
Misterjunky said:
If you don't want to do a full wipe don't even bother flashing it again.
The whole purpose of re-flashing is that you are having a problem with
the camera.
A clean install of Omega rom should clear it up.
But a dirty flash will make no difference at all.
Backup your apps using titanium backup or some other backup app so you don't loose your apps.
Good luck!
Click to expand...
Click to collapse
When i first flashed the omega rom, i did do a full wipe, worked fine until the camera app crashed for the 3rd time. I don't mind doing a full wipe, it's just i did some tinkering with my phone and i have to start again if i have to do a full wipe lol
Always do a full wipe when having problems.
I understand it can be time consuming, i have dirty flash many times and still had the same problems.
If the new flash doesnt work search the Rom thread, i read somewhere of a similar issue.
So I used the Auto CF root and all went well. Next, I went back into recovery and installed the TWRP Recovery though odin. It installed fine. After that I noticed I no longer had root and I can't figure out how to get it back. Supersu was still installed, it just wouldn't work.
At this point, i've tried redoing the root process a couple of times and it says that it worked fine, but doesn't do the job. Anyone got any ideas on what to do?
If anyone's curious, I started on totally stock OTA MF9.
Thanks
Just flash one of the stock rooted mf9 ROMs in the development thread pic one with no data wipe so you don't have to set everything up again.
SGS4 Sent
ifly4vamerica said:
Just flash one of the stock rooted mf9 ROMs in the development thread pic one with no data wipe so you don't have to set everything up again.
SGS4 Sent
Click to expand...
Click to collapse
Thanks for the tip. Downloading the odexed version of this. Slow download so almost 2 hrs left.
[ROM][ZIP]Stock Rooted Deodexed/Odexed MF9 with SuperSU/Busybox 1.20.2
Hopefully it works. I tried wiping cache and dlvik cache and now when i turn the phone on it just keeps giving errors that this and that app can't open so the phone is essentially unusable. Didn't think wiping cache would do that.
Yeah sometimes things just go screwy. Have you tried fixing permissions? While you wait for a download you can wipe cache davlik and fix permissions its in the advanced menu of twrp. The odexed with no data wipe should fix you up I would recommend wiping cache davlik and system before you flash it. If it still gives errors you may have to wipe the data also and start fresh. You can also try TWRP version 5.0.2 if you aren't on it there is a flashable in the dev forum also. Some people have reported issues with the newer version. I think you will be fine flashing that stock odexed ROM though.
SGS4 Sent
Out of curiosity, would there be any danger in installing a custom rom while my phone is in this state? Downloading Blu Kuban Rom and it's going to finish much earlier than the stock rom. I know I would lose all my apps and need to reinstall those.
iivisionii said:
Out of curiosity, would there be any danger in installing a custom rom while my phone is in this state? Downloading Blu Kuban Rom and it's going to finish much earlier than the stock rom. I know I would lose all my apps and need to reinstall those.
Click to expand...
Click to collapse
Nope no danger at all. In fact I recommend blu Kuban. Its a nice ROM. Just do a full wipe of system data cache davlik and preload before flashing to avoid issues. All the custom ROMs have root built into them so you should be good to go.
SGS4 Sent
ifly4vamerica said:
Nope no danger at all. In fact I recommend blu Kuban. Its a nice ROM. Just do a full wipe of system data cache davlik and preloaded.
SGS4 Sent
Click to expand...
Click to collapse
Thanks. I'll have an update soon. Either that or a panic attack and a question in roughly 30-45 minutes.
Did you try to install super SU from the market. Maybe super user is acting up on you.
Sent from my SPH-L720 using Tapatalk 4 Beta
daniel4653 said:
Did you try to install super SU from the market. Maybe super user is acting up on you.
Sent from my SPH-L720 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I tried installing supersu from the market. Next I even tried downloading it to my phone and loading the zip in recovery. No go both ways. I hoped wiping cache and delvick cache would help, but instead the phone is pretty much unusable now. It's really weird.
iivisionii said:
I tried installing supersu from the market. Next I even tried downloading it to my phone and loading the zip in recovery. No go both ways. I hoped wiping cache and delvick cache would help, but instead the phone is pretty much unusable now. It's really weird.
Click to expand...
Click to collapse
Here goes that frantic post. I installed the rom, worked fine. I did one of the updates for the status bar, now whenever it goes to boot it gets stuck at the samsung galaxy s4 screen. I've tried doing a full wipe, wiping cache and delvick cache and even trying to install the stock rooted rom or the blu rom on top of itself and i still get the same thing. Any ideas? I'm trying not to be too flash happy because I don't want a brick.
iivisionii said:
Here goes that frantic post. I installed the rom, worked fine. I did one of the updates for the status bar, now whenever it goes to boot it gets stuck at the samsung galaxy s4 screen. I've tried doing a full wipe, wiping cache and delvick cache and even trying to install the stock rooted rom or the blu rom on top of itself and i still get the same thing. Any ideas? I'm trying not to be too flash happy because I don't want a brick.
Click to expand...
Click to collapse
Have you tried the battery pull trick once frozen?
ObrienDave said:
Have you tried the battery pull trick once frozen?
Click to expand...
Click to collapse
I finally got out of the boot logo. I looked around the forums and found someone with a similar problem. Seems the recovery wasn't deleting all the files for him so he deleted everything manually instead of just wiping. I did the same and installed triforce rom and it's booted now.
Just for future reference though, would you mind explaining or pointing me to where I can read about the battery pull trick?
iivisionii said:
I finally got out of the boot logo. I looked around the forums and found someone with a similar problem. Seems the recovery wasn't deleting all the files for him so he deleted everything manually instead of just wiping. I did the same and installed triforce rom and it's booted now.
Just for future reference though, would you mind explaining or pointing me to where I can read about the battery pull trick?
Click to expand...
Click to collapse
Basically, quite a few people have recommended pulling the battery once frozen.
Even when you do a power off, you are NOT completely removing power from the system.
Disconnecting the power is the only way to accomplish this.
ObrienDave said:
Basically, quite a few people have recommended pulling the battery once frozen.
Even when you do a power off, you are NOT completely removing power from the system.
Disconnecting the power is the only way to accomplish this.
Click to expand...
Click to collapse
Ah ok. Good tip to know. I had tried that and it didn't work. Seems to be working ok now. I'm gonna be careful not to screw it up cuz its already 1 am, hehe. Thanks for everyone's tips.