Hey guys,
I always have to pull my battery out multiple times on reboots, or after flashing a rom.
When I change roms, I do a fact. reset and wipe cache/dalvik, on updates of same rom I only do a wipe of cache/dalvik. I tried fixing permissions.
How is this caused ? It eventually boot up every time, just very annoying.
Does wiping system help ? I've read that most rom dev's include it anyway in flashing rom.
Phone: Samsung Galaxy Nexus
Rom: AOSP Paranoid Android 2.99 beta 5
Recovery: TWRP 2.3.2.1
Thnx for your help!
Firewalker1980 said:
Hey guys,
I always have to pull my battery out multiple times on reboots, or after flashing a rom.
When I change roms, I do a fact. reset and wipe cache/dalvik, on updates of same rom I only do a wipe of cache/dalvik. I tried fixing permissions.
How is this caused ? It eventually boot up every time, just very annoying.
Does wiping system help ? I've read that most rom dev's include it anyway in flashing rom.
Phone: Samsung Galaxy Nexus
Rom: AOSP Paranoid Android 2.99 beta 5
Recovery: TWRP 2.3.2.1
Thnx for your help!
Click to expand...
Click to collapse
I haven't encountered this but I sometimes get bootloop when I flash Gapps without wiping cache and dalvik. Whenever I flash a new ROM, I do factory reset, wipe system, cache, and dalvik. So you may try wiping all of them and make a fresh install of the ROM then see if this problem keeps affecting you. Just make a nandroid backup in case this does not help so you restore your whole data easily
ahmadallica said:
I haven't encountered this but I sometimes get bootloop when I flash Gapps without wiping cache and dalvik. Whenever I flash a new ROM, I do factory reset, wipe system, cache, and dalvik. So you may try wiping all of them and make a fresh install of the ROM then see if this problem keeps affecting you. Just make a nandroid backup in case this does not help so you restore your whole data easily
Click to expand...
Click to collapse
Hey thx for your suggestions!
I always flash a "new" rom that way though. But an update of the same rom, I "dirty" flash, which should be fine according to everyone.
No matter what Rom/Kernel I use, I still frequently have to pull the battery out.
It's never from locking up within Android. It just freezes/loops on the Google bootlogo.
I once wiped everything, even the storage space, and it helped for a little while, but did not make it go away for good.
Could it be related to certain apps ? Maybe PGM or Seeder or smth ?
All input welcome
---------------------------------------------------------------
Phone: Samsung Galaxy Nexus Maguro
Rom: AOSPA 2.99 latest
Kernel: AK Purity v20
Recovery: TWRP 2.3.3.0
Related
Hi I've tried to change my Build. I'm currently using Android Revolution HD. I've got the kernel the program came with - android-build. I have tried changing it over to a whole of builds. AOKP, Gummy
It never successfully launches any of them.
Every time I wipe data, cache and I wipe Dalvik too.
I don't know what to do...
Is there any one who is on Rogers that can do this?
Thanks guys
Biomera said:
Hi I've tried to change my Build. I'm currently using Android Revolution HD. I've got the kernel the program came with - android-build. I have tried changing it over to a whole of builds. AOKP, Gummy
It never successfully launches any of them.
Every time I wipe data, cache and I wipe Dalvik too.
I don't know what to do...
Is there any one who is on Rogers that can do this?
Thanks guys
Click to expand...
Click to collapse
Don't really make sense??? Try to also format system in recovery ( it won't touch ur personal stuff ) then do all the other wipes then try flash another Rom if that don't work I.got nothing, if u can't figure out there's always fastboot stock Google .img
Can you provide a step-by-step instruction on how you tried to update your Galaxy Nexus ? I'm not on Rogers (I'm on TELUS), but still, maybe we can help you and see if you are following the right path !
You're not doing something right if you can't get another ROM installed.
Do this.
Make sure ROM and Gapps package for that ROM is on your SD card
Reboot into recovery
Wipe data
Wipe cache
Go to Advanced, Wipe dalvik
Go to Mounts and Storage, format system, and cache
INSTALL ROM based on 4.03
Install Gapps
Reboot and Enjoy
Samsuck said:
You're not doing something right if you can't get another ROM installed.
Do this.
Make sure ROM and Gapps package for that ROM is on your SD card
Reboot into recovery
Wipe data
Wipe cache
Go to Advanced, Wipe dalvik
Go to Mounts and Storage, format system, and cache
INSTALL ROM based on 4.03
Install Gapps
Reboot and Enjoy
Click to expand...
Click to collapse
I would back your phone up before doing this. Formatting your system deletes the operating system.
theherodrownd said:
I would back your phone up before doing this. Formatting your system deletes the operating system.
Click to expand...
Click to collapse
Correct. Listen to him and PLEASE make a back-up. I forgot to mention that.
Hi All,
Seem to have a slight problem with flashing Custom Roms onto my GNex at the moment. Not too sure what's causing it to freeze when booting up. All I get is the X logo and will stay there until the battery dies.
I'm able to revert back to a Google rom and regain use of my phone. Just can't seem to flash any custom roms at all. It's happened with CM10.1, CM10, XenonHD Stable-2.0, Minoco.
I've attempted to flash with CWM and TWRP. Both get the same results. Prior to flashing I've whiped both the Cache and Davlik.
I have previously used CM9 and older versions of Minoco on this device. So seems odd that this is happening now.
Any advise or ideas towards what I should look at would be appreciated.
Thanks,
Drav
you have wipe data before flashing different roms... dirty flashing(only wipe cahce and dalvik) is only if you are updating the same rom.. this is how i normally flash ALL roms
1. wipe data/factory reset
2. wipe system
3. wipe cache
4. wipe dalvik cache
5. flash rom
6. flash gapps
7. reboot
8. wait 10 mins then do another reboot
9. enjoy
PS- the 10 min wait and reboot is soemthing i do that IMO lets the new rom settle
Thanks k786,
It's booted up in a custom rom now after following those step by step. Much appreciated! :good:
Cheers,
Drav
So I've been flashing a couple of different roms this week like Carbon (based on AOSP), PACMAN (Don't know what it's based on), Rootbox (based on AOKP) and Slimbean (AOSP) the method I've been using to flash is wiping data/factory reset, wiping cache/dalvic cache, flashing ROM & gapps, flashing NexusLouder mod, flashing custom kernel, advance restoring data only then rebooting. I think this could be the cause of the boot loops. Or... it could be the function implemented in Carbon which doesn't require you to constantly flash gapps anymore since it backs everything in /system/apps. Anyone know what the cause of the boot loops are for sure?
Extra details - I started using this method ever since I was on AOKP which was my first custom rom. Then a few months ago, I moved to Rootbox, then Carbon, then I tried out PACMAN for a while then reverted back and just today I went back to Rootbox for a while, then I tried out SlimBean and ever since today, I've been getting random bootloops when I restart my phone. It doesn't happen every time I reboot my phone but when it does, clearing the cache solves the problem temporarly and I also had to do a full restore of my nandroid a couple of times today.
Also, I use this method because I have over 75 songs on my playlist which I spent hours creating and I don't want to start all over again. I also don't want to set all my rom settings again either.
Reduce any OC
Undo any Voltage mods
Disable any apps that alter how the system behaves
Disable all apps and enable one by one until you have an issue
You get the idea.
Definitely want to avoid restoring data from another rom and flashing audio mod. If after flashing a new rom you still get the random reboot then you can narrow down the problem.
Sent from my Galaxy Nexus
an easy hint may help: always wipe cache and dalvik AFTER flashing rom, mods... to prevent conflicts :good:
samersh72 said:
an easy hint may help: always wipe cache and dalvik AFTER flashing rom, mods... to prevent conflicts :good:
Click to expand...
Click to collapse
I always do that :thumbup:
Sent from my Galaxy Nexus using xda premium
samersh72 said:
an easy hint may help: always wipe cache and dalvik AFTER flashing rom, mods... to prevent conflicts :good:
Click to expand...
Click to collapse
Thanks for the tip
Hi, in the last minutes i've flashed the 2.7 build of LiquidSmooth Rom from the Paranoid Hello Halo rom... I've done the prcedure like XDA said : Wipe Wipe Wipe (cache, dalvik, system) Flash Rom Flash Gapps. It booted fine but all my apps that i've had on my previous rom was still there... all of them. The most disturbing is my settings were also like I've left them ( disabled pie wifi etc) also my Google Accound was already setuped and good to go. Is it a new feature from flashing 4.2.2 rom to an other 4.2.2 rom ? I've never seen that before. I've also rebooted to make sure it wont boot loop on reboot, and it booted like a charm!
Any clues ?
Weird, never seen that before. Tell us what recovery you have and exactly what you are wiping. Can't think of anything else at the moment I'm sure others will chime in.
Sounds to me like you're not wiping /data. This is where your apps and setting are stored and unless you factory reset using stock recovery, deliberately wipe/format /data, or flash a Rom that wipes it for you, all your apps and settings will remain.
Seems like normal behavior to me.
Sent from my SGH-T999L using xda premium
Ya I re-read it and he just wipes caches and system, definitely need to factory reset lol.
kruse1944 said:
Hi, in the last minutes i've flashed the 2.7 build of LiquidSmooth Rom from the Paranoid Hello Halo rom... I've done the prcedure like XDA said : Wipe Wipe Wipe (cache, dalvik, system) Flash Rom Flash Gapps. It booted fine but all my apps that i've had on my previous rom was still there... all of them. The most disturbing is my settings were also like I've left them ( disabled pie wifi etc) also my Google Accound was already setuped and good to go. Is it a new feature from flashing 4.2.2 rom to an other 4.2.2 rom ? I've never seen that before. I've also rebooted to make sure it wont boot loop on reboot, and it booted like a charm!
Any clues ?
Click to expand...
Click to collapse
Tapatalk.
mt3g said:
Ya I re-read it and he just wipes caches and system, definitely need to factory reset lol.
Click to expand...
Click to collapse
Got it that's why. I was sure wiping system would wipe data too. But do you think its dangerous to not wipe data? Because actually my ROM is rocking right now without issues? Should I reflash it for safety?
It just depends....
It's always best to start clean, especially if you were having problems. But if you want to keep data intact, you should be ok as long as you don't go to an entirely different rom, base, or build.
If you are updating to a newer version of the same build, you're fine. Also if updating to a newer build/version you should be ok, but may have a few hiccups.
However, anytime you go backwards (4.2.2 to 4.1.2) you should wipe it all. The same is true if you are moving to a different base, such as CM to TW. Keeping your internal sdcard data is usually ok, but sometimes it can cause some issues.
Sent from my SGH-T999L using xda premium
Hi,
I started using PA on my Galaxy Nexus with a fresh install of 4.0 Beta 6 about 4 weeks ago (unlocked and rooted via nexus root toolkit, recovery is teamwin).
Since then, I installed every update through Paranoid OTA, so I am on current 20140318 now with GAPPS stock 20140318.
Everything was great.
Suddenly, a few hours ago, the phone started rebooting again and again until I decided to take out the battery.
Since then, it hangs during boot at the PA logo.
I tried reinstalling pa_maguro-4.0-BETA6-20140217.zip and pa_gapps-stock-4.4.2-20140217-signed.zip through recovery (after backup of course), but this changed nothing.
Fun thing is... I am moving to a new flat tomorrow and really need my phone to organize things.
So if anybody has an idea what I can look at or how this may be fixed, I would really appreciate it.
Thanks!
Stephan
Edit: wiping cache and dalvik cache did not help...
Factory reset and reinstall
felt0r said:
Hi,
I started using PA on my Galaxy Nexus with a fresh install of 4.0 Beta 6 about 4 weeks ago (unlocked and rooted via nexus root toolkit, recovery is teamwin).
Since then, I installed every update through Paranoid OTA, so I am on current 20140318 now with GAPPS stock 20140318.
Everything was great.
Suddenly, a few hours ago, the phone started rebooting again and again until I decided to take out the battery.
Since then, it hangs during boot at the PA logo.
I tried reinstalling pa_maguro-4.0-BETA6-20140217.zip and pa_gapps-stock-4.4.2-20140217-signed.zip through recovery (after backup of course), but this changed nothing.
Fun thing is... I am moving to a new flat tomorrow and really need my phone to organize things.
So if anybody has an idea what I can look at or how this may be fixed, I would really appreciate it.
Thanks!
Stephan
Edit: wiping cache and dalvik cache did not help...
Click to expand...
Click to collapse
Seems like you got stuck in a bootloop. bootloops can occur pretty easily, it’s mainly caused because system files interfering with each other which causes instability and/or crashes at the boot sequence
Try doing a fresh install (use latest recovery version of your recovery)
- wipe data/factory reset
- wipe cache partition
- format system and data
- wipe dalvik cache and flash the rom and gapss again