I have installed aosp pixel ui based ROM on my Lenovo a7000a. It is very nice ROM but at certain times in automatically restart. I don't know why this is happening. I have also flash it again. But this bug is now going. So may I remove this and install another ROM or there is a solution on it.
Use daredevil kernel. Flash it and then wipe dalvik and data or factory reset. Then reboot the phone.
Sent from my Lenovo P2a42 using XDA-Developers Legacy app
Related
it seems like every rom I install these days restart randomly.
Whats causing this ?
Bad flash probably, with all sure respect sound like user error, try completely clean fresh install
Sent from my GT-I9000 using XDA Premium App
How can everyone be flashing wrong? Most people post that they have the reboot problem. Maybe its an overclocking thing or lock screen issue. Its a bad problem with most roms it looks like.
Sent from my GT-I9000
Well people without the problem aren't going to post are they? And, again, with due respect, a lot of people simply don't know what they are doing or don't read install instructions properly
Sent from my GT-I9000 using XDA Premium App
I don't have this problem on cm7. Try a fresh install of JVR or something, and that includes a repartition and factory reset (which are basically the same thing ).
Sent from my GT-I9000 using XDA Premium App
Sidneymac said:
it seems like every rom I install these days restart randomly.
Whats causing this ?
Click to expand...
Click to collapse
The user
Okay. I guess.
Sent from my GT-I9000
No problems on darky rom 10.2 on my i9000m
Sent from my GT-I9000 using XDA Premium App
Sidneymac said:
Okay. I guess.
Sent from my GT-I9000
Click to expand...
Click to collapse
I know not all users do this, but whenever I flash a new ROM, I generally like to wipe data/dbdata/cache and dalvik from the phone. Then flash the ROM, do a full factory reset and wipe the internal SD card as well. I've never experienced any random reboots personally after following this proceedure.
It means I have to backup and restore apps using Titanium Backup, and copy over all my music again, but I like knowing I've got the cleanest possible installation
Ivegottheskill said:
I know not all users do this, but whenever I flash a new ROM, I generally like to wipe data/dbdata/cache and dalvik from the phone. Then flash the ROM, do a full factory reset and wipe the internal SD card as well. I've never experienced any random reboots personally after following this proceedure.
It means I have to backup and restore apps using Titanium Backup, and copy over all my music again, but I like knowing I've got the cleanest possible installation
Click to expand...
Click to collapse
While I respect the cajones your flashing procedure requires, and agree that it will ensure a perfect ROM flash, every time....it still strikes me a little like doing the dishes by lighting the kitchen on fire.
Unless a new ROM specifically calls for a /data wipe aka factory reset I would propose this less extreme method to the OP which should still solve their reboot problems in most cases:
1) Go into Recovery
2) Clear the Dalvik cache
3) Clear or Format the /cache
4) Format the /system directory (this will not wipe your apps or data, it will just clear the system files that are most likely to cause conflicts with the new ROMK, hence reboots)
5) Flash the new ROM
6) Flash new gapps (optional but usually saves hassles down the line)
7) Fix Permissions
8) Reboot
That should fix you up 9 times out of 10. If you are still seeing reboots, then do a factory reset from recovery to clear out all your apps, reflash your current ROM and then reinstall your non-system apps from either the market or Titanium backup one by one (without data if at all possible). Try to stagger the reinstall so you can try and isolate if the reboot problem is due to a specific app (doubtful since normally an app will fc, not reboot the entire system, but it is possible).
Any questions, let me know, and good luck.
rschenck said:
While I respect the cajones your flashing procedure requires, and agree that it will ensure a perfect ROM flash, every time....it still strikes me a little like doing the dishes by lighting the kitchen on fire.
Click to expand...
Click to collapse
I agree, but when I've had problems (or when I'm installing a completely different ROM), I like to use the procedure I mentioned. It gets rid of any old stuff that might be left behind from a mixture of old ROM's, kernels, themes and apps. I thought trying it might help solve the OP's problem
rschenck said:
Unless a new ROM specifically calls for a /data wipe aka factory reset I would propose this less extreme method to the OP which should still solve their reboot problems in most cases:
1) Go into Recovery
2) Clear the Dalvik cache
3) Clear or Format the /cache
4) Format the /system directory (this will not wipe your apps or data, it will just clear the system files that are most likely to cause conflicts with the new ROMK, hence reboots)
5) Flash the new ROM
6) Flash new gapps (optional but usually saves hassles down the line)
7) Fix Permissions
8) Reboot
Click to expand...
Click to collapse
Agreed.
Sent from my GT-I9000 using XDA Premium App
In 14 hours ive experienced one reboot, but the yesterday I had like 10 reboots.
I usually factory reset etc and most roms clean everything before installing anyways.
And to keep my apps etc when I format the /system directory I guess I should pick the no wipe rom package ?
hi,
im using cm10.1 rom (stunner 2) and everything was going well when suddenly the phone restarts and got stuck at the boot screen, i wiped and installed the rom once more everything went well when after a month or so the same thing happends again and today was the third time ...
i took a nandroid backup and will install a new rom, but i just want to know what is happening ? does this has anything to do with soft bricking or anything ?
this time try downloading a fresh copy of the rom and install again..
Are you using up to date ROM if not download updated one and flash its most likely his kernel tweaks which should be better now on new builds
Sent from my GT-N7000 using XDA Premium HD app
i was using latest rom, the same rom and kernel are on a friend's note and this problem did not happen with him.
this time i downloaded the P.A.C true all in 1 rom, wiped data/factory reset, format system then installed the rom
everything is ok until now but I'll wait and see if this happens again with this rom or not
Hi,
I recently rebooted my Droid 4 after not changing or installing anything, and since then it is stuck in the cm boot animation logo.
Is there any possibility to get it back to work, without reinstalling the image? As I would lose some App configurations and data otherwise...
Currently installed version is the latest stable maserati; I think it is 10.2.1
I already deleted Cache and Dalvik Cache multiple times.
Thx in advance
You can reinstall rom without wiping data, just use same file, may work may not depends on what the problem is.
Sent from my XT894 using Tapatalk
Already tried that in the meantime, did not work...
Would it maybe work if I installed another rom (cm11) on Slot 2 (next to the crashed cm10 on Slot 1) in Safestrap? Would that enable me to use my installed apps, configs, and data (photos etc)?
Here is the problem that I've never met on my previous Nexus 4 devices.
I was trying to update my Nexus6 to the latest CM12.1 nightly today(my Nexus6 already runs on CM12.1).
Then I downloaded the zip from cyanogenmod.org, and flashed it without clean cache or wipe, because I'm updating within the version 12.1.
I always updating system on my N4 this way, it never fails.
But on my N6, when it finishing Optimizing Apps, it will restart immediately, and start optimize apps again, then start over.
I had the same problem before when I was using Chroma rom, and that's why I switch to CM(always had to re-install all my apps after updating).
Is there anybody know what causing this problem and how to solve it? So that I can update ROM normally.
May be it's sometime essential to wipe data/ factory cache before installing another ROM.
Sent from my Nexus 6 using Tapatalk
raikecody said:
Here is the problem that I've never met on my previous Nexus 4 devices.
I was trying to update my Nexus6 to the latest CM12.1 nightly today(my Nexus6 already runs on CM12.1).
Then I downloaded the zip from cyanogenmod.org, and flashed it without clean cache or wipe, because I'm updating within the version 12.1.
I always updating system on my N4 this way, it never fails.
But on my N6, when it finishing Optimizing Apps, it will restart immediately, and start optimize apps again, then start over.
I had the same problem before when I was using Chroma rom, and that's why I switch to CM(always had to re-install all my apps after updating).
Is there anybody know what causing this problem and how to solve it? So that I can update ROM normally.
Click to expand...
Click to collapse
You have to wipe. From TWRP, wipe dalvik, cache, system, and data.
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).