Why is my moto x install cm11 as long as the software associated GPS will automatically reboot
What? I'm guessing that English isn't your native tongue.
CM11 reboots anytime you use an app that utilizes GPS? If so, I'd reflash system.img and wipe cache to see if that fixes it. If not, flash back to stock to rule out hardware.
Related
Please Help I installed a custum ROM and now I am stuck in a loop a skull comes up and droid and it continues till the battery is dies. I have tried to factory reset and nothing the only way to turn it off is to remove the battery can someone please Help
If the ROM is what's causing the problem, doing a factory reset won't change anything; it'll stil keep the same ROM in place. What you might want to do is download a more popular ROM, like a CM7 nightly, put it on your microSD card (using another phone or a microSD adapter, of course) and boot into recovery and flash that.
If that doesn't work, I dunno then. I got a bootloop the other day after using ROM Manager to flash a new kernel. Turns out it was the kernel because after a factory reset, it booted up fine. So I just chose another kernel and it's all good now.
You just might have a screwy ROM. Try reflashing it if you can. What was the custom ROM, btw?
Yeah I'd agree with the above; install another ROM and make sure to wipe cache and dalvik and if it still doesn't work wipe data as well. Note that wiping data will wipe pretty-much everything on your phones memory (SMS messages, contacts, accounts etc)
when it is cm7 than you should take an other kernel
Please, if you are experiencing random reboots (that involve the M logo) or prolonged screen freezes, you should revert to an older beta kernel that is free of the DSI errors. To do so, replace the boot.img in the update-cm-7...zip package with this one (from 0.04 version): http://code.google.com/p/cyanogenmod4milestone/downloads/detail?name=bootimg0.04.zip
Click to expand...
Click to collapse
Stole that from another Thread:
_Flash with any rom you have
_Milestone will auto reboot after flash done and loop
_Don't worry about that, remove battery in 5s and re-plugin
_Turn on your milestone: hold X and POWER to access Recovery. Select Wipe and reboot
Do you have a Droid or a Milestone? If you have a Milestone, which country is the device from?
I had a boot loop issue too on my UK Milestone when I tried to install CM6.1.2, version 28.01.2011 0.07-11.01.28. (http://android.doshaska.net/cm6)
This is what I did to fix the problem...
- Flashed UK 2.1 SBF file
- Flashed Vulnerability Recovery
- Rooted the phone
- Installed and booted into OpenRecovery
- Installed 15.01.2011 0.06-11.01.15 version (phone booted fine)
- Rebooted into OpenRecovery > Wiped Dalvik Cache
- Applied 28.01.2011 0.07-11.01.28 version
One more thing, you may need to update and/or change your baseband files.
I hope this helps.
Thx for the help guys I,m back up an running. Greatly appreciated
Sent from my Droid using XDA App
I've tried flashing slim rom and paranoid Android and all do the same thing. As soon as Google apps are installed the Google voice search prompt pops up repeatedly. It disables calling and also all sounds. I have turned it off in Google settings best I could and it still keeps happening. It has essentially made my nexus 6 unusable. And since I need the Google app I don't know what to do. Anyone seen this problem before? I am guessing it is not rom specific as it happens on all I have tried. Help severely needed
Sent from my Nexus 6 using Tapatalk
wessiide said:
I've tried flashing slim rom and paranoid Android and all do the same thing. As soon as Google apps are installed the Google voice search prompt pops up repeatedly. . .
Click to expand...
Click to collapse
When I flashed a different ROM there were always issues when I did not a wipe in TWRP recovery (factory reset).
I have cleared data and cache along with a system wipe. Any thing else I can try to wipe?
NLBeev said:
When I flashed a different ROM there were always issues when I did not a wipe in TWRP recovery (factory reset).
Click to expand...
Click to collapse
Sent from my Nexus 6 using Tapatalk
wessiide said:
I have cleared data and cache along with a system wipe. . .
Click to expand...
Click to collapse
In TWRP there is a message about wiping.
When you did that it is OK.
Effect should be that after booting the new rom, you need to completely setup the device again (setup wizard).
When there are still issues it could be a corrupt download.
I'll try to be more clear here.
I have done a factory reset (system, data, cache, dalvik) from TWRP.
I install new rom (chroma, paranoid, slim, and a stock build)
Boot up phone, complete setup wizard.
"Listening" prompt from google voice search starts popping up repeatedly, over and over no matter what I am doing on the phone.
I disable google voice search, doesn't matter, continues to pop up.
In the meantime it disables all sounds on the phone and I cannot place a call/take a call.
Again, this is the same actions that happen regardless of what rom I have installed, even after doing the reset.
Try changing the GApps package you flash after your ROMs.
I'm guessing you've been using the same GApps with each ROM you listed. Download another GApps and use that instead in a clean flash of a given ROM.
Good luck!
(One more thought: You could try clean flashing a ROM with a built-in GApps and see if that works...)
Sent from my A0001 using Tapatalk
wessiide said:
I have done a factory reset (system, data, cache, dalvik) from TWRP.
I install new rom (chroma, paranoid, slim, and a stock build)
Boot up phone, complete setup wizard.
Click to expand...
Click to collapse
There are two important options in TWRP.
WIPE and FORMAT.
You have installed several different roms. The memory could be messed up.
A format could help.
The last suggestion I can do is: back to stock.
Flash a factory image.
Leave bootloader unlocked.
Check if the issue is gone when the stock rom is set up.
Than choose a custom rom, start with Chroma.
NLBeev said:
There are two important options in TWRP.
WIPE and FORMAT.
You have installed several different roms. The memory could be messed up.
A format could help.
The last suggestion I can do is: back to stock.
Flash a factory image.
Leave bootloader unlocked.
Check if the issue is gone when the stock rom is set up.
Than choose a custom rom, start with Chroma.
Click to expand...
Click to collapse
What do I format? System? It doesn't seem to be a Google specific problem as even with Google not installed the phone just hangs up when I dial a number and sound doesn't work. It went away on its own about an hour after start up and I've been good for a week. Now just this morning it started doing it again. The volume turned itself up a notch and boom no sound on video can't call anyone. It's very strange, and must be a deep rooted issue as it is across all roms. The only difference with Google now installed is the listening prompt popping up constantly. Without its just what I listed above.
Sent from my Nexus 6 using Tapatalk
Revert back to stock (e.g. with Wug's nexus root Toolkit), leave bootloader unlocked. Then reflash your things and see if problem persists. If it does, try TK GApps and don't install Google App (per gapps-config.txt).
I just updated my bootloader and whenever i try to flash a rom, the booting process takes forever until i wipe my phone myself. But when i flash Andro X rom than it takes max. 3min to boot and then it works.
But i want another rom, how do i fix this?
Do you mean that when u flash lollipop based rom it gets bootloop? if yes then first flash stock lollipop firmware and then try flashing other rom. I mostly wipe my internal storage when going from Kitkat to lollipop it works for me.
Well Firstly Explain your problem clearly (I didnt quite understand it)
OK so here's my solution from what I understood..
1. Restore your stock rom Backup from recovery. Boot it once.
2. Now clean flash (Wipe System, Data , Cache, Dalvik cache) a lollipop based Rom (preferably try to clean flash cm 12.1 build)
3. Dont flash Gapps. First see if your phone boots up properly.
4. Configure data and reboot to recovery and flash Gapps.
If you dont have a Stock backup, Then download Stock Firmware images from gregor's thread and install via fastboot. Then follow from step2.
Hope this helps you.
Haroun16 said:
I just updated my bootloader and whenever i try to flash a rom, the booting process takes forever until i wipe my phone myself. But when i flash Andro X rom than it takes max. 3min to boot and then it works.
But i want another rom, how do i fix this?
Click to expand...
Click to collapse
Use easy installer first and get stock lollipop then u can simply root and install recovery then try roms?
sagar846 said:
Well Firstly Explain your problem clearly (I didnt quite understand it)
OK so here's my solution from what I understood..
1. Restore your stock rom Backup from recovery. Boot it once.
2. Now clean flash (Wipe System, Data , Cache, Dalvik cache) a lollipop based Rom (preferably try to clean flash cm 12.1 build)
3. Dont flash Gapps. First see if your phone boots up properly.
4. Configure data and reboot to recovery and flash Gapps.
If you dont have a Stock backup, Then download Stock Firmware images from gregor's thread and install via fastboot. Then follow from step2.
Hope this helps you.
Click to expand...
Click to collapse
My problem is that when i try to flash roms like CM12, Blisspop it doesn't stop booting, it was taking more than an hour so i shutdown my phone and when i flashed Andro X the booting took around 3mins.
So can anyone explain in easy steps how to fix this?
OK now I understand what your problem is. Give me your full specs (like which Model and and stuff). But if you follow what I said above it might fix your problem.
sagar846 said:
OK now I understand what your problem is. Give me your full specs (like which Model and and stuff). But if you follow what I said above it might fix your problem.
Click to expand...
Click to collapse
I got the XT1068
Haroun16 said:
I got the XT1068
Click to expand...
Click to collapse
are you fully wiping cache and userdata (factory reset) because this is most common problem moving between Roms that causes bootloops and why I include factory reset in my easy installer.
you can only dirty flash when going up (upgrading) the same rom - changing roms or downgrading nearly always causes bootloop / hang.
Hello.
I read about bootloader bricks in moto g 2014 when people trying to flash stock ROM.
Could somebody tell me when this problem occurs? I'm asking because i plan to flash Cyanogenmod to my phone and i want to avoid phone brick
Flashing cm ...doesnt brick ur device
Sent from my falcon using Tapatalk
kamilopl said:
Hello.
I read about bootloader bricks in moto g 2014 when people trying to flash stock ROM.
Could somebody tell me when this problem occurs? I'm asking because i plan to flash Cyanogenmod to my phone and i want to avoid phone brick
Click to expand...
Click to collapse
Just remember to take a nandroid backup and wipe system, data, cache and dalvik cache before flashing.
Most common Soft brick happen when there's conflict due to different gapps package , which is solved by wiping data and system.
Hi everyone, I'm here because i have problems with my phone and i want to fully restore. To do this i would like to install a new ROM, but from what i've seen, to install a ROM is necessary to have the stock JB 4.1.2 on the device, while i have CyanogenMod 11 (4.4.4) running.
This wouldn't be a problem if i could use Odin, but apparently my USB port has something wrong, and i cant connect my phone to any PC, so i cant flash in that way. Luckly i can access to the custom recovery (CWM), so i 'd like to ask if there is a way to flash the stock firmware via CWM.
Instead, If I can install a ROM starting directly from CM11 without restoring stock JB, or if i'm missing something important, let me now, i would appreciate a lot
Thank you in advantage. (Excuse se for any misspelling, I'm not English)
What kind of problems do you have?
If you can access CWM recovery there's no need to install stock in order to flash a new ROM, just be sure to wipe caches and data before installing the new one to avoid related bugs; and you will probably need to update the recovery to TWRP if you want to flash one of the most recent ROMs
It's always recommended to create a backup before everything else.
Peace
Hi, thank you for then anwer Well, it would be a long list of problems ^^ The biggest one though is the fact that if I'm in AeroMode everything works as always, sometimes bugged but nothing exceptional, but in the moment i switch AeroMode off and digit the SIM pin, the phone turns off and then enters in a bootloop(vibrating every 1 minute like before entering the main window, but it remains stuck) that is solvable only pressing for 8/10 secs the POWER button and restarting it. I can't have a phone which is not able to make voice calls :/ Back to the problem, so if i'm not misunderstanding anything, I dont need to reverto to stock and then reflash the new ROM? Because, for example, in the main page of CM13 it's written:
ROM Firmware Required: Stock + CWM compatible with KitKat
and that's the origin of my post... But in case, which wipe should i do? Dalvik + wipe data/factory reset?
OK, the thing is that you need stock + CWM at minimum, it means you can't install it if you are on gingerbread; but if already installed something higher than 4.1 you can go from there.
First create a backup then wipe cache, wipe dalvik, factory reset and install your preferred ROM
Ohhh, that makes sense.... Ok, so i will wipe what you said and flash the new ROM! You saved me a lot of time, thank you so much!