Hi.
I'm running CyanogenMod7.1.0 on my Moto Defy, and recently, when I turn on mobile data the phone crashes (restarts) within a few seconds.
After restarting, the phone boots regularly, and then reboots every few seconds.
The last lines (before the crash) taken from adb are at: gist(dot)github(dot)com/1134269
a much longer logfile is at gist(dot)github(dot)com/1134231 (new user, can't post urls..)
each crash is marked (by me) with '=======================' and some newlines.
any help would be greatly appreciated.
As this works for almost everyone running CM7 (not seen any other reports of mobile data crashing/causing instability) it would seem sensible to clear cache/dalvik cache from Recovery (reboot, 'vol -' when the blue light shows) then Recovery - Clear Dalvik cache is under Advanced....
Also, if you're overclocking, reset to stock clocks/voltages and see if that fixes it..
You could also try the latest nightly builds - I'm using 'cm7-110809-0713-NIGHTLY-Jordan' without any issues (think I've tried almost every nightly build they guys have created!) and would strongly recommend it over your version.
Working brilliantly so far. THANKS russtyd.
And thank you for the detailed explanation, I didn't know about this recovery in cm7.
Sent from my MB525 using XDA App
I'm glad it was that easy to fix
As it turns out, I spoke too soon..
clearing the dalvik cache worked for about an hour, but than the problem came back.
Here's what I know so far:
using 2G network (with data) is OK.
Installing the 2 latest nightlies (110809 and 110806) - does not crash the phone when data is enabled, but it does kill all 2G/3G network connectivity.
Right now, I'm afraid of a hardware issue, so I'm gonna flush some stock sbf (any recommendations? would love a good tutorial, since it's my first time going back..) to check if it works there.
Anything else I might be missing?
If you want to go back to a 2.2 froyo then the CM7 FAQ is helpful for links to the sbf and drivers etc:
http://forum.xda-developers.com/showthread.php?t=1065798
Just download the following two files (links are in the FAQ):
- RSD Lite and Motorola Drivers (updated)
- SBF 3.4.2-177-005 NORDIC
Install Motorola drivers and run RSDLite, and then follow the first 2 steps of "2) How can I install CM7 RC0?", ie
- Power your phone with Volume Down pressed to enter Stock Recovery, then do "Wipe data/Factory reset" and "Wipe cache"
- Reboot from Stock Recovery with Volume Up pressed to enter Bootloader Mode, then open RSD Lite and flash Nordic
There are more sbfs here http://forum.xda-developers.com/showthread.php?t=966537 but having needed to do a clean install myself of CM7 last week (stuck on 'M' logo after a messed-up nightly install) I know this one works and gets you back to 2.2.2....
Related
Hi,
I was recently trying to get CyanogenMod 7 on my Defy. This is what happened...
rooted with z4root
installed ClockworkMod bootloader (using System Recovery apk)
performed a full backup
ran the update.zip for CM7 (from here)
wiped user data + cache (didn't wipe before running update.zip, because I didn't read it properly!)
got stuck in a "M" logo loop
flashed the UK T-Mobile 2.21.1 SBF file (from here) with RSD Lite
ended up with a completely dead Defy! (as described here)
the only ROM i can get to boot at all is the UK Orange 2.3.3 (from here)
i rooted using this method (here)
i've reinstalled the ClockworkMod recovery (using the same System Recovery apk)
when it reboots to the recovery, I just get a black screen
Does anyone know any way of reverting back to the stock T-Mobile ROM (or, ideally, move to CyanogenMod 7?), or does it look like I'm stuck in the Orange ROM?
Any help would be appreciated!
Thanks!
xnoruk said:
Hi,
I was recently trying to get CyanogenMod 7 on my Defy. This is what happened...
rooted with z4root
installed ClockworkMod bootloader (using System Recovery apk)
performed a full backup
ran the update.zip for CM7 (from here)
wiped user data + cache (didn't wipe before running update.zip, because I didn't read it properly!)
got stuck in a "M" logo loop
flashed the UK T-Mobile 2.21.1 SBF file (from here) with RSD Lite
ended up with a completely dead Defy! (as described here)
the only ROM i can get to boot at all is the UK Orange 2.3.3 (from here)
i rooted using this method (here)
i've reinstalled the ClockworkMod recovery (using the same System Recovery apk)
when it reboots to the recovery, I just get a black screen
Does anyone know any way of reverting back to the stock T-Mobile ROM (or, ideally, move to CyanogenMod 7?), or does it look like I'm stuck in the Orange ROM?
Any help would be appreciated!
Thanks!
Click to expand...
Click to collapse
Even for me CM7 Beta 6 didn't worked... well but I am happy to be on Leaked Orange GB 2.3.3 with Blur..
It's definitely an improvement on the original ROM! It supports proxy over wifi (although I haven't tried it yet), although GPS + android Market don't work... but I suppose it's much better than having a bricked phone!
I'm also on the leaked 2.3.3 orange rom and everything seems to work great so far (using it for 1 week now).
I've had a problem with the market too in the beginning. The market needs a google account to work and I couldn't add this account to motoblur from the beginning, where you setup motoblur, so the market wouldn't work for me. I did a wipe data/factory reset, rebooted and this time I could add the google account. Not a single bug, FC, reboot or anything like that so far (ok 1 "bug" to be honest, the signal bars stay empty but the 2g, 3g and hdspa indicators work). I've also used gps navigation without problems and the camera too without the fixes in the forum, but you may want to try the fix from walther79 for gps (http://forum.xda-developers.com/showpost.php?p=14046494&postcount=388).
I haven't tried myself but they say it can be downgraded. If you carefully follow this guide (http://forum.xda-developers.com/showthread.php?t=1054447) and use the sbf mentioned in that post you should be able to install cyanogenmod 7 succesfully. Use this guide for flashing: http://forum.xda-developers.com/showthread.php?t=853674
If you want to wipe data and cache before flashing (suggested) you could use clockwork OR the standard recovery (http://www.hardreset.eu/motorola_defy_hard_reset_soft_reset_en.html). Though you should hold volume up + volume down after you see the droid instead of tapping the touchscreen. There is also a chance clockworkmod will work after you've done a wipe data/factory reset.
PS-> I AM NOT AT ALL RESPONSIBLE FOR ANY BRICKAGE OF PHONE OR ANYTHING. PLEASE TRY AT YOUR OWN RISK!
I finally got GPS to work. Here is what i did.
I used Mobile Odin (or you could use Odin from a PC) to flash the EL26 stock CWM kernel to get CWM back.
When the phone rebooted I HELD The Volume+ and the POWER button at the same time until i got into CWM.
Then I wiped everything and cache and dalvik
Flashed a GingerBread Rom like Blazer 4.1.
Rebooted
Got a GPS lock in the maps app. WITH THE MAP APPLICATION STILL OPEN.
- Held the Volume- Button and Power Button until I got into the DOWNLOAD MODE. Then clicked on Volume+
-Plugged the phone into the computer via USB
-Opened ODIN
-Flashed EL26 stock CWM kernel AGAIN
-When thats done the phone will reboot. When it does HOLD the Volume+ and the POWER button at the same time until i got into CWM
-Wipe Data/Factory, Cache, Dalvik.
-Flash ROM
-Flash Gapps
-Wipe Cache and Dalvik again
-Flash Kernel
-Reboot
When you are all set up after the phone boots up. You may need to download the GPS STATUS app
---Click on
-TOOLS
-MANAGE A-GPS STATE
-RESET
THEN the GPS will work. It did for me.
GOOD LUCK.
wrxphantom said:
PS-> I AM NOT AT ALL RESPONSIBLE FOR ANY BRICKAGE OF PHONE OR ANYTHING. PLEASE TRY AT YOUR OWN RISK!
I finally got GPS to work. Here is what i did.
I used Mobile Odin (or you could use Odin from a PC) to flash the EL26 stock CWM kernel to get CWM back.
When the phone rebooted I HELD The Volume+ and the POWER button at the same time until i got into CWM.
Then I wiped everything and cache and dalvik
Flashed a GingerBread Rom like Blazer 4.1.
Rebooted
Got a GPS lock in the maps app. WITH THE MAP APPLICATION STILL OPEN.
- Held the Volume- Button and Power Button until I got into the DOWNLOAD MODE. Then clicked on Volume+
-Plugged the phone into the computer via USB
-Opened ODIN
-Flashed EL26 stock CWM kernel AGAIN
-When thats done the phone will reboot. When it does HOLD the Volume+ and the POWER button at the same time until i got into CWM
-Wipe Data/Factory, Cache, Dalvik.
-Flash ROM
-Flash Gapps
-Wipe Cache and Dalvik again
-Flash Kernel
-Reboot
When you are all set up after the phone boots up. You may need to download the GPS STATUS app
---Click on
-TOOLS
-MANAGE A-GPS STATE
-RESET
THEN the GPS will work. It did for me.
GOOD LUCK.
Click to expand...
Click to collapse
Honestly with ICS all you have to do is flash back to gingerbread, get a gps lock, then flash back to ICS. This worked for me every time. Fix I talked about was posted a couple times and is a known fix since the original Epic. Actually it was a fix for the original Epic's leaks and tested and proved to work with our phones.
I'm not trying to be mean but, you have more steps than is necessary.
cdszoke said:
Honestly with ICS all you have to do is flash back to gingerbread, get a gps lock, then flash back to ICS. This worked for me every time. Fix I talked about was posted a couple times and is a known fix since the original Epic. Actually it was a fix for the original Epic's leaks and tested and proved to work with our phones.
I'm not trying to be mean but, you have more steps than is necessary.
Click to expand...
Click to collapse
This is great but everyone hhas listed this in almost every thread.
Also, I use gps assit, gps fix, gps status and I always get a lock.
I just turn off the gps.. turn it back on and reset the gps from GPS Status, then download the agps data and get 10/10 sat hit...
Honestly the reciever isn't as sensitive as HTC devices so indoors is finicky.. but I always get a lock outside.
numus said:
I just turn off the gps.. turn it back on and reset the gps from GPS Status, then download the agps data and get 10/10 sat hit...
Honestly the reciever isn't as sensitive as HTC devices so indoors is finicky.. but I always get a lock outside.
Click to expand...
Click to collapse
Wow. Thanks, you saved me some time with this method. Worked great for me. Before I wasn't locking on anything!
this is an older known method, but good lookin out anyhows
Sent from my SPH-D710 using xda premium
Nexus Noob here (hence posting in QA, and not in the dev section)
I've been running Xenon for awhile now with no issues. Over the weekend I flashed the newest version:update-XenonHD-11-03-12-signed-toro.zip. I was coming from version: update-XenonHD-10-13-12-signed-toro.zip. This skipped over one version, so I'm not sure if that was part of my problem.
When I first flashed the rom (CWM > install from flash > wipe cache/delvik, reboot) My phone wouldn't connect to gmail, sync contacts, etc. So I wiped the phone in recovery, flash Franco Kernel, and reboot. then rebooted again into recovery and flashed the newest Xenon, GAPPS, clear cache/delvik, and reboot. This fixed my initial issues, but the phone seems very sluggish compared to previous versions. For instance, when I get a phone call it will ring for 3-5 seconds before the screen pops up so I can see who it is/answer the phone.
Any thoughts on what I can do different to get my phone back to "normal"?
thanks
Hey, everybody.
Had some trouble recently, after a second install of CM10 FreeXperia (version 244) on my Xperia Pro phone. Suddenly, I noticed that the device won't charge when I plug it in (unless I turn off the phone), and that mobile data isn't working anymore. And I'm kinda clueless as to where to go from here. Here's the story;
I've had the device rooted for a month or so, and a few days ago decided to switch to the FreeXperia rom.
Did an install, everything worked fine. Had it running nice & smooth for 3 days, no problem whatsoever, then got an impulse to switch DPI settings. Downloaded "LCD Density Modder", set DPI to 220, and the device was now stuck at blackscreen during boot.
I decided the best option for me would be to reinstall the FreeXperia rom, get everything clean again, and start over without fussing with DPI settings. So i booted into CWM recovery, did a wipe cache, wipe data/factory reset, installed the FreeXperia 244 zip again (aswell as correct gapps), and had everything up and running again!
Atleast that's what I THOUGHT... but by evening, I discovered:
1. the phone wouldn't charge when i plugged it in.
Tried several different chargers, none works. HOWEVER, the phone recharges it's battery when i turn it off.
and,
2. mobile data isnt working, only wi-fi.
No settings changed, looked them through and couldn't find anything obvious (as far as my knowledge goes).
Making calls and sending sms still works, though.
So, I'm a bit stuck here. I'd be extremely glad if someone could give me a few pointers, or instruct me how to do a "proper" re-install (since i assume my way of re-installing things caused these problems).
Anyone got suggestions?
What I tried again now was:
1. wipe everything
2. flash new kernel
3. wipe everything
4. install rom & gapps
5. wipe everything again
However, the problem remains exactly the same.
Download the ROM.zip again, could be a problem with the zip file. Make sure you do a clean install.
僕のLT18iから送られてきた
popthosegaskets said:
Download the ROM.zip again, could be a problem with the zip file. Make sure you do a clean install.
僕のLT18iから送られてきた
Click to expand...
Click to collapse
Thanks for the tip!! managed to fix it though, through:
1. charging issue resolved itself by doing the aforementioned wipe-install-wipe procedure, and
2. internet issue was resolved by manually entering APN (it had somehow been erased).
so, we've got ourselves a happy ending, here.
First, for shortening and simplicity let's use cm versions only last numbers (cm-12.1-20151230-NIGHTLY-nicki will be 30 etc.).
I will arrange my short story in points for better understanding, let's begin here:
- I installed CM 23 (it's 12.1 but the number is for nightly like shown higher) and updated to 26, everything was fine
- quick install of Open Gapps, my apps and doing settings stuff, everything fine
- wild update to 30 appeared, i updated it and it was not very effective
- device rebooted, flashed update automatically, optimized apps aaaaand it got stuck on finishing boot. it was fully ok and responding cause a sound played when i plugged it to charging, it was showing touches ( i set it to show em before update), but it was stuck. So i took battery out and it started to boot, after couple of seconds screen brightness turned down as in every normal booting, boot animation slowed and lagged a few times but then continued to bootloop. Here is a list of things i tried:
- rebooting of course
- clearing cache and dalvik in twrp, then it just optimized apps again and got stuck on starting apps
- wiping data, still bootloop
- wiping everything and installing fresh CM 30
Only the last worked but i lost everything i installed etc. I made a backup of data partition but it restored only some apps ( not even gapps) and settings for some reason.
so after installing everything again i lived it for a while, but because it is a nightly a new update was posted! CM 104
- i downloaded it in cm updater as every other update (btw flashing cm 26 and then 30 from .zip gave the same result), installed it, and it worked soo...
- two days later another update appeared(cm 106), i check every update changelog and this one was big.
- happy of last successful update i just updated it but this time it didn't worked so well
everything is the same as updating 26 to 30, and here we are it got stuck on finishing boot, i took battery out, bootloop, clearing cache and dalvik, optimizing apps, got stuck on starting apps, system fully responding to the same things. i turned the phone down and started this thread.
I have a full backup of everything on another sd with cm 30 and installed apps, but because system is responding i think you guys can help me. i don't want to do a clean install every time a not working update appears. I could stay on last working version, but i'm a type of a person who wants everything updated even if won't give me anything new so staying on last working version from backup is only accepted if you guys won't have any solution or at least idea.
Big thanks for everyone that will bring anything here and probably save some time another happy cm user
EDIT: also, i can restore that backup i have and install version 104, and then figure out how to install it properly
my own idea
so, now i have restored my backup and when i have some free time i'll try to install fresh cm without gapps and update it a few versions, if it'll work problem solved. i will have to just clear cache and dalvik after every update and flash gapps. I only want to ask, if it will work, will flashing gapps with the old ones installed make any issues?
Try to re install rom after full wipe
rohitnegi44 said:
Try to re install rom after full wipe
Click to expand...
Click to collapse
i specially wrote this thread with extra simplicity, but you didn't read that it's working after full wipe, i'm trying to install update AND save my data. read before you post and try to get some easy thank points or whatever this forum has somewhere else.
FIXED IT!!
So for everyone who's looking for answer to this problem here's the fix: after cm flashes and turns off, hold VOL+ button to go to recovery instantly then wipe cache and dalvik, flash gapps, again wipe cache and dalvik reboot. For me it worked.