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 ?
Related
Noob questions. Every time I flash a new rom I become narotic, and I first disable any lagfix, then go to cwm, and factory reset, cache, dalvik, and batt stats all wiped. I'm assuming I don't need to do this if it's a full wipe rom? Can I even skip the lagfix part or is that always necessary?
Also if I'm upgrading a version of a rom, ex, apex 6.4 to 6.5 or any other situation same as this, can I just flash it without doing any prep before hand?
Sent from my GT-I9000 using XDA App
if it's a full wipe ROM than yes, the ROM does all the wiping for you. And if the OP states for you to disable lagfix before flashing than i do so.. also if your just doing an update you can usually just flash over one another. But its always good to check with the ROM dev and see if he suggests any special wipes or whatnot.
Cdub3 said:
Noob questions. Every time I flash a new rom I become narotic, and I first disable any lagfix, then go to cwm, and factory reset, cache, dalvik, and batt stats all wiped. I'm assuming I don't need to do this if it's a full wipe rom? Can I even skip the lagfix part or is that always necessary?
Also if I'm upgrading a version of a rom, ex, apex 6.4 to 6.5 or any other situation same as this, can I just flash it without doing any prep before hand?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
You can still do whatever your used to and are comfortable with. BUT this is what I do before flashing any rom.
I go to market and make sure all apps are updated.
Next I go to titanium backup and backup all user apps and system apps with data (I NEVER RESTORE THE SYSTEM APPS OR DATA THOUGH)
Next I boot into recovery and perform a backup (which saves almost Evey aspect of my rom I am on before flashing
I boot back up and then reboot into recovery again.
Then I install whatever rom I am flashing at the time.
I DO NOT WIPE ANYTHING OTHER THAN CACHE WHILE IN RECOVERY AND BEFORE FLASHING THE ROM.
I have NOT had more than 1-2 issues flashing anything since I started using froyo, so that includes any froyo rom, the gingerbread rom that first was made, then Continuum and on my second cappy the same except I also have flashed CM7 on it.
The one or two times I had issues ALL I ever did was boot into recovery and run restore from the previous rom I was on. Then reflash the rom I was trying to get on to. I really have have had NO ISSUES NOT wiping anything other than cache.
I look at it this way, if it works the first time I flash a rom I am golden and do not need to reset up everything. If I have a issue then I CAN start from scratch with a factory reset and wipe cache and dalvich cache IF NEED BE. At least then I am ON the rom I was trying g to go on in the first place.
Then after all seems good I will restore my user apps and some user apps with data with Titanium Backup. So MOST of the time I have changed roms and all is working with no issues in 10 to 15 minutes.
Again this is HOW AND WHY I do it that way. A NANDROID BACKUP and TITANIUM BACKUP are your BEST FRIENDS in these cases.
Sent from My KickAss Captivated CM7 OC'd 1.55Ghz/Undervolted
Thanks for the replies. Very helpful
Sent from my GT-I9000 using XDA App
Cdub3 said:
Thanks for the replies. Very helpful
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
6.5 is a wipe version which would take care of wiping caches. You dont need to disable lagfix. But as someone said always keep a nandroid backup
Also you may want to post these queries in ROM thread for quicker response
I always disable lagfixes just for good measure. Most roms do a full wipe so there's no need for any of the other stuff.
So every single rom for any phone I've seen says to clear the dalvik and the cache (or maybe its just the "dalvik cache") but when I went from stock to Thriller, I forgot to, and nothing went wrong. In fact, all my settings and apps were all intact from the previous stock rom.
I've considered that the only other phone I'd done any flashing on was a backflip, without Apps2SD and maybe that's why all my apps and settings were intact, so that still leaves me with the question: why clear it?
This may be a noob-ish question, and I apologize. Thanks for any help!
Tyqar said:
So every single rom for any phone I've seen says to clear the dalvik and the cache (or maybe its just the "dalvik cache") but when I went from stock to Thriller, I forgot to, and nothing went wrong. In fact, all my settings and apps were all intact from the previous stock rom.
I've considered that the only other phone I'd done any flashing on was a backflip, without Apps2SD and maybe that's why all my apps and settings were intact, so that still leaves me with the question: why clear it?
This may be a noob-ish question, and I apologize. Thanks for any help!
Click to expand...
Click to collapse
If there are any compatibility issues between the apk dalvik cache of your previous rom and the apks on the new rom wiping dalvik clears the previous apks stored dalvik cache. In most cases you can flash without a problem. But I recommend wiping between rom flashes just to eliminate any potential problems. Flashing something like Thriller over the stock rom you can probably get away with not wiping anything since all the apks are essentially the same. Flashing kernels you don't need to wipe anything. When flashing a rom with a completely different firmware I recommend a full data wipe. Restoring recovery backups such as nandroid require no wiping at all.
Also, wiping dalvik shouldn't affect any of your settings.
Sent from my LG-P920 using Tapatalk
+1
When switching ROM with different base apps, it is generally better to wipe caches than to get stuck in a boot loop, or having your apps and launcher FC on you. You never lose anything as the cache rebuilds itself on the next reboot, except maybe a few minutes
CallMeAria said:
If there are any compatibility issues between the apk dalvik cache of your previous rom and the apks on the new rom wiping dalvik clears the previous apks stored dalvik cache. In most cases you can flash without a problem. But I recommend wiping between rom flashes just to eliminate any potential problems. Flashing something like Thriller over the stock rom you can probably get away with not wiping anything since all the apks are essentially the same. Flashing kernels you don't need to wipe anything. When flashing a rom with a completely different firmware I recommend a full data wipe. Restoring recovery backups such as nandroid require no wiping at all.
Also, wiping dalvik shouldn't affect any of your settings.
Sent from my LG-P920 using Tapatalk
Click to expand...
Click to collapse
so, when i flashed thriller and followed the instructions, did I do a full wipe or not?
I mean if it doest it on its own, and if not, should I do one?
latinohot said:
so, when i flashed thriller and followed the instructions, did I do a full wipe or not?
I mean if it doest it on its own, and if not, should I do one?
Click to expand...
Click to collapse
If you followed the instructions you did a full data wipe. When you do this the dalvik gets wiped as well. To just wipe dalvik look under the Advanced menu in cwm recovery.
Sent from my LG-P920 using Tapatalk
clearing cache
i am using a nand rom in my HD2, and i also want to install another rom via SD in Magldr, but because of kernel issues i cannot load the Rom from SD unless i use the kernal i am advised to use. I am instructed to clear the dalvik and cache, but does this mean that i would lose anything from my current NAND rom? I still want to be able to use that of coarse so i just want to make sure there are no major risks when clearing cache.
ssj5legend said:
i am using a nand rom in my HD2, and i also want to install another rom via SD in Magldr, but because of kernel issues i cannot load the Rom from SD unless i use the kernal i am advised to use. I am instructed to clear the dalvik and cache, but does this mean that i would lose anything from my current NAND rom? I still want to be able to use that of coarse so i just want to make sure there are no major risks when clearing cache.
Click to expand...
Click to collapse
Clearing dalvik and cache wont make you lose anything, used to do it with my shift because I'd flash about 10 zips a day sometimes...
Also when it comes to flashing any ROM I format system data cache wipe dalvik cache and do a factory reset just to be sure nothing from a previous ROM is left over also wipe my SD ext partition when running an a2sd ROM, my question is can I safely manually format the emmc partition of the thrill from the mounts and storage option of cwm
Sent from my LG-P925 using Tapatalk
PLEASE SIGN THIS PETITION! TO GET US SOME UPDATING LOVE!!!!!
SIGN AND SIGN AND SIGN!!!! THEN SING!,.......: http://www.change.org/petitions/sam...clears some things. Now lets flash some ROMs!
quick question, if you do a factory reset with odin and start from scratch, should you delete everything that is on your internal SD? Would that be a full complete wipe?
That is a FULL wipe but thats not what im talking about. Just the internal phone stuff.
what is formatted when you click to format /boot? for some reason I always thought that formatted the boot loader so I dared not touch that, but now I'm realizing how stupid it would be to even put that option there and how many more phones would have been bricked at this point. anyway when I install a new rom I pretty much wipe everything (including dalvik) except for /boot and /emmc ( I even formated the external recently but moved back images, efs backup, and avatar), then mount /sdcard, insert rom then flash, fix permissions.
formats the boot animation?
or after the VIBRANT logo
it's a ritual for me whenever i install a new rom to go through this installation method. I also notice that i tend to experience far less "bugs" then others.
Odin to Stock JFD
using the update.zip flash CWR
flash ROM (bootloops after updating CWR)
3 button into recovery
mounts and storage menu
format the following
-System
-Cache
-Data
-Data/Data
advanced Menu
Wipe Dalvik Cache
Flash Rom Again
Fix Permissions
Reboot
wait 5 Minutes
Reboot
complete the 1 time google setup
Install your apps Without data
reboot to recovery
Clear Cache/Dalvik fix permissions
Reboot
Play
I use this method from everything from 2.2-miui-ics never a hickup!
Format system wipes the internal sd basically?
juniorkid95 said:
Format system wipes the internal sd basically?
Click to expand...
Click to collapse
Noooooo!!! It wipes the ROM!
If you wanna wipe SD then "format SD"
Updated OP please read!
Sent from the effnn TITAN!!!
VeryCoolAlan said:
Noooooo!!! It wipes the ROM!
If you wanna wipe SD then "format SD"
Updated OP please read!
Sent from the effnn TITAN!!!
Click to expand...
Click to collapse
Now I understand. Thanks Alan. How come most ROM flashing instructions don't advise Format system?
..........
What about clearing Dalvik Cache?
nirogu325 said:
What about clearing Dalvik Cache?
Click to expand...
Click to collapse
Cleared in the process...
Sent from the effnn TITAN!!!
VeryCoolAlan said:
Cleared in the process...
Sent from the effnn TITAN!!!
Click to expand...
Click to collapse
Just being curious because some say it isn't cleared in the Factory Reset. Some ROM and kernel devs do suggest clearing Dalvik Cache after doing a Factory Reset because it prevents some apps giving FCs after flashing a new ROM.
Side note: I wipe dalvik about once every two weeks whether I am flashing or not. Helps with cleaning up corpses and getting better RAM usage. Thanks for the info Alan.
extra post :/
Nice find!
..now bend over.
One question Alan.
Can I Odin to stock from ICS passion just like we go from gingerbread or froyo from? Or is there a special way to get back to stock jfd? I want to try out jcc from but I don't know if I could just Odin to stock from passion. Thanks
Sent from my SGH-T959 using Tapatalk
boystuff said:
it's a ritual for me whenever i install a new rom to go through this installation method. I also notice that i tend to experience far less "bugs" then others.
Odin to Stock JFD
using the update.zip flash CWR
flash ROM (bootloops after updating CWR)
3 button into recovery
mounts and storage menu
format the following
-System
-Cache
-Data
-Data/Data
advanced Menu
Wipe Dalvik Cache
Flash Rom Again
Fix Permissions
Reboot
wait 5 Minutes
Reboot
complete the 1 time google setup
Install your apps Without data
reboot to recovery
Clear Cache/Dalvik fix permissions
Reboot
Play
I use this method from everything from 2.2-miui-ics never a hickup!
Click to expand...
Click to collapse
What you using to reinstall apps and/or app data? Everytime I install a new ROM, I lose all my data connected to an app. For example, I play Drag Racing and you have to create a new login name everytime I install a new ROM. I would like to at least save the data related to that app.
wavestar92 said:
One question Alan.
Can I Odin to stock from ICS passion just like we go from gingerbread or froyo from? Or is there a special way to get back to stock jfd? I want to try out jcc from but I don't know if I could just Odin to stock from passion. Thanks
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
Yep just ODIN to stock , wipe and flash
Sent from my SGH-T959 using XDA App
nirogu325 said:
Just being curious because some say it isn't cleared in the Factory Reset. Some ROM and kernel devs do suggest clearing Dalvik Cache after doing a Factory Reset because it prevents some apps giving FCs after flashing a new ROM.
Click to expand...
Click to collapse
Yea I do it as well just in case....
Sent from my SGH-T959 using XDA App
im just curious and also i want to be able to get an answer to this question. so that noobs like me that have a rooted and s-off device dont get things mixed up.
is truly necesary to do a full wipe ( data, delvik cache, etc.) to flash anything from a simple tweek to something more complex like a custom rom, or kernel?
Yes...it is truly necessary. The only exception being if it's an upgrade for a ROM you're already using. I.e. upgrading WhateverRom 1.4 to 1.5. Even then though a full or partial(cache and dalvik) wipe is usually recommended. You WILL have many problems if you flash a completely different ROM over another one without doing a full wipe.
Edit: proper procedure would be 1. Download the ROM you want 2. Place it onto your external sd card 3. Boot to recovery 4. Full wipe 5. Flash the .zip 6. Reboot 7. Enjoy 8. (optional) Report bugs to the developer in the thread dedicated to the ROM including as much information as you can about your setup, how the bug was achieved and so on
Sent from my HTC Holiday using xda premium
Monkeymannnn said:
Yes...it is truly necessary. The only exception being if it's an upgrade for a ROM you're already using. I.e. upgrading WhateverRom 1.4 to 1.5. Even then though a full or partial(cache and dalvik) wipe is usually recommended. You WILL have many problems if you flash a completely different ROM over another one without doing a full wipe.
Edit: proper procedure would be 1. Download the ROM you want 2. Place it onto your external sd card 3. Boot to recovery 4. Full wipe 5. Flash the .zip 6. Reboot 7. Enjoy 8. (optional) Report bugs to the developer in the thread dedicated to the ROM including as much information as you can about your setup, how the bug was achieved and so on
Sent from my HTC Holiday using xda premium
Click to expand...
Click to collapse
Thanks a lot for your answer, now, to further clarify my questions,
when you are just installing a simple mod, I.E a kernel, to a rom that already feel comfortable with, and you do an delvik and cache wipe? sometimes it really does not writes its properties over the previous kernel, let me explain.
i tried flashing holics kernell which is an non-overclock kernel with an very stable and battery friendly governor. over an more aggressive kernel like the overclocked Faux 123 v007. the results were that my device showed that the kernel installed was the holics but the cpu frequencies that were being run by the governor were more like the previous kernel and the phone was still overclocked although it wasnt supposed to anymore!
is this due to no doing a full data wipe? besides delvik and cache.
also if i was to do a full wipe. wouldnt i have to have some kind of apps back up system planned out. in order to make the phone looked just like it was before the kernel was flashed.?
I'm not that knowledgeable on kernels, but your best bet (afaik) would be to let your ROM boot up for the first time and then flash the new kernel. Titanium Backup is one of if not the best backup program (backs up apps as well as their data among other things). System data such as contacts, texts, etc. can be backed up and restored, but only to the same or very similar ROMs. You're gonna have problems if you restore data from say a touchwiz type interface to sense. Google backs up your contacts and apps anyways if you let it so they'll be restored and re-downloaded once you sign in with your google account.
Sent from my HTC Holiday using xda premium
With any rom or addons always read the devs instructions
Wiping data, cache and dalvik cache is a very safe bet, as for kernels the rom will flash it for you during the installation however if you are wanting to flash a custom kernel other than one in a rom. Just flash the rom and then the kernel.
ronnie498 said:
most devs will let you know what you need to do when flashing their item.
Click to expand...
Click to collapse
That's something I forgot to mention. ALWAYS read the entirety of the original post(s) from the dev. Also read through as much as you can of the thread from there. Nobody appreciates being asked things that were already covered in the thread. Some don't include full instructions, but most will and what they're telling you is what you need to follow.
Sent from my HTC Holiday using xda premium
Here's what I do...
If flashing a whole Rom (even if its just an update) I wipe everything...data, cache and dalvic
If flashing a kernel/apps/tweaks then I just wipe cache and flavorc cache
Those methods have yet to fail me...also, you don't have to let the Rom boot up before flashing a kernel...you can flash a Rom then immediatly flash a kernel (assuming the kernel is compatible with the Rom)
Sent from my HTC Holiday using Tapatalk 2
mg2195 said:
Here's what I do...
If flashing a whole Rom (even if its just an update) I wipe everything...data, cache and dalvic
If flashing a kernel/apps/tweaks then I just wipe cache and flavorc cache
Those methods have yet to fail me...also, you don't have to let the Rom boot up before flashing a kernel...you can flash a Rom then immediatly flash a kernel (assuming the kernel is compatible with the Rom)
Sent from my HTC Holiday using Tapatalk 2
Click to expand...
Click to collapse
THanks, that answers my questions.
i have yet fail to fallow instructions and there have been very little times when i have got my device stuck,
and most of the times when it happened i was able to find the answer of my questions around the forum,
you guys do a great job. :good:
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).