Has anyone figured out a way to prevent boot loops when rebooting CM10.2 that doesn't involve wiping the device and reinstalling CM10.2 and GAPPS (if you're lucky to even get this to work)?
Went from stock 4.1.2 (unlocked and rooted, before the most recent patch)
Wiped data/cache/dalvik
Installed Skrilax 8/5 nightly and 7/29 GAPPS
Wiped data/cache/dalvik again
Booted up system, installed apps and messed around, then turned phone off. Now the phone sticks at the M logo (or unlocked bootloader, whatever you have showing).
uncgecongrad07 said:
Has anyone figured out a way to prevent boot loops when rebooting CM10.2 that doesn't involve wiping the device and reinstalling CM10.2 and GAPPS (if you're lucky to even get this to work)?
Went from stock 4.1.2 (unlocked and rooted, before the most recent patch)
Wiped data/cache/dalvik
Installed Skrilax 8/5 nightly and 7/29 GAPPS
Wiped data/cache/dalvik again
Booted up system, installed apps and messed around, then turned phone off. Now the phone sticks at the M logo (or unlocked bootloader, whatever you have showing).
Click to expand...
Click to collapse
Sounds like you didn't initially wipe your system. You're going to have to start over
sent from my xt926 RAZR maxx hd
Wiping was the first thing I did after doing a backup, before I installed the ROM. I assume if I hadn't wiped to start I wouldn't have been able to boot CM to begin with, which I was able to do.
I recall this being a known issue, but was just curious if anyone had come up with an answer and hadn't posted yet.
Sent from my DROID RAZR HD using xda app-developers app
I didn't have this issue when I ran CM10.2.
Sent from my DROID RAZR HD using Tapatalk 4
mentose457 said:
I didn't have this issue when I ran CM10.2.
Sent from my DROID RAZR HD using Tapatalk 4
Click to expand...
Click to collapse
I'm only running CM10.1, but I did notice on my first boot it seemed to hang on the CM loading screen for a long time (a few minutes). This was because like a noob I accidentally wiped modem. I had to use the Droid Utility's factory restore, then restart the wipe & flash process.
What did work:
I used CWM's format options to mount then wipe system/data/cache (in that order), and remount them. Then went back to the main CWM and ran the Factory Reset and Wipe Cache options, verified that system/data/cache were still mounted, then flashed from external SD the CM nightly and GApps.
Related
Earlier, I tried installing ViperXL 2.1.0 ROM, wiped the cache, system, and factory restored in TWRP.
When I was installing the ROM, it got stuck at 90%, so I just gave up. This is my first android phone in two years, so I am just
starting to get use to ROMs again.
visualizeit said:
Earlier, I tried installing ViperXL 2.1.0 ROM, wiped the cache, system, and factory restored in TWRP.
When I was installing the ROM, it got stuck at 90%, so I just gave up. This is my first android phone in two years, so I am just
starting to get use to ROMs again.
Click to expand...
Click to collapse
Do it again. I had that happen to me once.
Reboot into recovery, Wipe System/Factory reset and reflash.
If you rooted from 2.20 flash the boot.img first
Could also be a corrupt zip. Chrome used to do that to me.
Sent from my One X using xda premium
Just flashed again and this time it was successful.
Unchecked the exchange mail mod because that is what it froze at earlier.
Vioe does that to ne often. It hangs at 90%. Then I simply reboot to twrp and flash again and it works without modifying anything.. it's weird
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
The problem is either related to TWRP or Aroma. I'm pretty sure all ROMs that use Aroma experience this, although I don't think I've had it happen to me since installing TWRP 2.3.1.0 (at least, from what I remember)
Rebooting back into recovery and reflashing usually works, no matter what the selection is.
I rooted my phone last night and all day today had horrible battery life (4 hours little usage) along with some what looked to be screen reboots. I only rooted phone did not install a rom nor any aps other than titanium. Any ideas why why this is happening and what I should do? Not new to rooting had an incredible that I spent many hours playing with.
Sent from my SCH-I535 using xda premium
Which method did you use to root your phone? There are several different ways to do it.
Have you checked your battery stats to see what is using your battery? Have you tried restarting your phone?
If restarting your phone doesn't solve your issues, you could install a custom recovery and then wipe your data, cache and dalvik-cache, and then install a new ROM which should solve any of your problems (much like your probably did on your Incredible). If you don't want to use a custom ROM, there are strock, rooted images available both for flashing through ODIN as well as flashing through Recovery.
I used the casual file method. Checked battery stats and nothing out of the ordinary. Also rebooted phone several times. I have a mac so I can't use Odin to go back to stock and try again. I also don't want to install a custom rom yet because I'm waiting for some bugs to be fixed on the synergy rom before I make that jump. My main reason for getting root was to freeze some apps in the meantime (haven't frozen any yet) and to enable the gps toggle switch on car dock via nfc which is working great.
Sent from my SCH-I535 using xda premium
Since I can't use Odin how would I go back to stock? Install the nandroid backup i made then unroot using casual? But before trying that do you think wiping dalvik might work? Strange that this is happening.
Sent from my SCH-I535 using xda premium
ancora76 said:
Since I can't use Odin how would I go back to stock? Install the nandroid backup i made then unroot using casual? But before trying that do you think wiping dalvik might work? Strange that this is happening.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
So you do have a custom recovery installed already? You don't need Odin as long as you have a custom recovery.
You can try clearing both your cache and dalvik-cache in recovery, and then reboot to see if it solves your problems.
If it doesn't, then backup and sync your data (wiping your data won't wipe your "internal sd card", but you will lose all of your system settings). UNLOCK YOUR BOOTLOADER (search for ez-unlock on the market). Then put this on your sd card (or internal memory): http://forum.xda-developers.com/showthread.php?t=1941334
Boot to recovery. Wipe data, cache, and dalvik-cache. Install that stock, rooted ROM. Reboot and reset up your phone settings.
i used the recovery that was suggested with the casual process. I think i might have fixed my issue i downloaded Rom Manager and reinstalled recovery and powered off my phone then removed battery and now the phone is smooth again but im still noticing that my battery is draining rather quick. This is very strange. Im thinking of unrooting and trying it all over again. I just need to find the original Verizon image.
Hey guys,
I decided to make the transition over to CM, however I'm having boot loop issues with CM10. Here's the steps that I've taken in order to flash the ROM (what I though was properly):
Download CM10 Stable for HTC One XL
Wipe Cache and Davlik Cache
Factory Reset
Install CM10 .zip from TWRP 2.3.3
Flash boot img using TN WIN Boot Installer
However, as I've previously stated, I'm stuck on the CM boot logo. Any suggestions, I'm at a loss?
Thanks.
Solved the problem. I had to flash the boot img BEFORE flashing the ROM. Mistake on my part.
Mods -- feel free to delete this thread.
Thanks.
It should make no difference if you flash before or after.
Sent from my Sony Tablet S using xda app-developers app
Hi,
I have AT&T Motorola Atrix 2 MB-865 , i was on official ICS after root unlock I flushed pa_edison-3.69-20130729-nokex.zip rom to my atrix 2, using http://forum.xda-developers.com/showthread.php?t=2050705
i did factory reset, data format system, format cache and etc before flushing that ROM after successful flush , I rebooted , after reboot it keep stuck (does't not hang just stuck) on paranoid boot screen, i tried to flush again but same result in addition i want to say i flushed only rom , no gapps, , now i am again on ics_edison using RDS Lite ,Please any one tell me where i am wrong
Thanks in advance.
cheeta123 said:
Hi,
I have AT&T Motorola Atrix 2 MB-865 , i was on official ICS after root unlock I flushed pa_edison-3.69-20130729-nokex.zip rom to my atrix 2, using http://forum.xda-developers.com/showthread.php?t=2050705
i did factory reset, data format system, format cache and etc before flushing that ROM after successful flush , I rebooted , after reboot it keep stuck (does't not hang just stuck) on paranoid boot screen, i tried to flush again but same result in addition i want to say i flushed only rom , no gapps, , now i am again on ics_edison using RDS Lite ,Please any one tell me where i am wrong
Thanks in advance.
Click to expand...
Click to collapse
Firstly its FLASH not FLUSH.!! On which system did you flash the ROM.. If you have flashed on 2nd system you should not wipe data... It will wipe out your other partitions... And did you flash via bmm or cwm??
Sent from my MB865 using XDA Premium HD app
nikhJ said:
Firstly its FLASH not FLUSH.!! On which system did you flash the ROM.. If you have flashed on 2nd system you should not wipe data... It will wipe out your other partitions... And did you flash via bmm or cwm??
Sent from my MB865 using XDA Premium HD app
Click to expand...
Click to collapse
he's is in a habit of writing 'flush' in place of 'flash' (see his other posts)
sent from my A2 running ÑÜMÅ3.0
$ÇÏÊÑÇÈ is the only TRUTH
Re
nikhJ said:
Firstly its FLASH not FLUSH.!! On which system did you flash the ROM.. If you have flashed on 2nd system you should not wipe data... It will wipe out your other partitions... And did you flash via bmm or cwm??
Sent from my MB865 using XDA Premium HD app
Click to expand...
Click to collapse
I used Atrix2BootStrap.apk which seem like CWM based, there was no option 1st system or second system, it was like standard flashing(means normally we flash using Clock world recovery so no 1s or seccond system option appeared).
cheeta123 said:
I used Atrix2BootStrap.apk which seem like CWM based, there was no option 1st system or second system, it was like standard flashing(means normally we flash using Clock world recovery so no 1s or seccond system option appeared).
Click to expand...
Click to collapse
i think this rom can be install via BMM only... my friend has do like what you do before..... the only you can do is FXZ to stock,root,and then go to play store, install BMM 0.3..... dont install bootstrap.apk again after installing BMM and you will be fine...
I seem to have a similar issue.
First of all although this is my first post on XDA I'm not new to flashing and using Custom Roms infact I have been using CM 10.1 versions switching back and forth between 4.1.2 when I run into trouble.
I decided to give PA a shot and seem to have run into a wall. I flashed PA nokex on system 3 (which previously had CM10.1 - JBX 0.8.1(kernel)).
Before flashing PA on it I destroyed and recreated system, data and cache partitions so I didn't see the need to do wipes on them again. Nevertheless I did dod wipes. Flashed PA nokex, Gapps, wiped dlavik cache and rebooted. (Using BMM ofcourse)
I am stuck at a black screen with the red LED. I would really like to sample PA so any help would be really appreciated.
blazebud350 said:
I seem to have a similar issue.
First of all although this is my first post on XDA I'm not new to flashing and using Custom Roms infact I have been using CM 10.1 versions switching back and forth between 4.1.2 when I run into trouble.
I decided to give PA a shot and seem to have run into a wall. I flashed PA nokex on system 3 (which previously had CM10.1 - JBX 0.8.1(kernel)).
Before flashing PA on it I destroyed and recreated system, data and cache partitions so I didn't see the need to do wipes on them again. Nevertheless I did dod wipes. Flashed PA nokex, Gapps, wiped dlavik cache and rebooted. (Using BMM ofcourse)
I am stuck at a black screen with the red LED. I would really like to sample PA so any help would be really appreciated.
Click to expand...
Click to collapse
i think PA non kexec is for ICS base only!
¢@®bøÑ///JBX
Super_Commando said:
i think PA non kexec is for ICS base only!
¢@®bøÑ///JBX
Click to expand...
Click to collapse
Yeah. I flashed the kexec version and it booted up fine... Thank you.
Hi,
I have a razr hd xt925 (Rogers Canada). I flashed CM11 unified msm8960 (do not remember which version) then when M8 snapshot was release I updated it using Cyanogen updates and currently I am on version 11-20140708-SNAPSHOT-M8-moto_msm8960.
- Android version: 4.4.4
- Kernel: 3.0.101-g41dd045
- build# cm_moto_msm8960-userdebug 4.4.4 KTU84P c5de078e68 test-keys
With the previous build and this current one, the browser (this also happens with chrome) gets frozen after like 15 minutes of usage, I'd say once or twice a day, then the razr reboots.
Other than that, the device is very smooth and much better than original ROM.
Can you help?
Did you clean flashed?
In recovery when going from a Nightly to a Snapshot one should always clean flash to avoid any issues, that is, wipe data factory reset (this wipes cache (including dalvik), data (not internal data). It leaves your phone in a factory state. Also, wiping the /system partition is a good idea, this remove the OS and makes it even more cleaner to install the rom.
Sent from my RAZR HD using XDA Free mobile app
Hydr0id said:
Did you clean flashed?
In recovery when going from a Nightly to a Snapshot one should always clean flash to avoid any issues, that is, wipe data factory reset (this wipes cache (including dalvik), data (not internal data). It leaves your phone in a factory state. Also, wiping the /system partition is a good idea, this remove the OS and makes it even more cleaner to install the rom.
Sent from my RAZR HD using XDA Free mobile app
Click to expand...
Click to collapse
I did that and it went fine for a couple of days then I am back to the same issue. I also did not install any app after flashing. Unfortunately, this will force me to reinstall Rogers ROM 4.1.2 and wait for the official update.
goldfinsh said:
I did that and it went fine for a couple of days then I am back to the same issue. I also did not install any app after flashing. Unfortunately, this will force me to reinstall Rogers ROM 4.1.2 and wait for the official update.
Click to expand...
Click to collapse
Very weird. You can try restoring back stock and clean flashing directly to the snapshot M8, and see how it works. Also, gapps can be the problem too. Make sure you use CM 11 updated gapps, you can find them here:
http://wiki.cyanogenmod.org/w/Google_Apps
Hope this helps.
Sent from my RAZR HD using XDA Free mobile app
Hydr0id said:
Very weird. You can try restoring back stock and clean flashing directly to the snapshot M8, and see how it works. Also, gapps can be the problem too. Make sure you use CM 11 updated gapps, you can find them here:
http://wiki.cyanogenmod.org/w/Google_Apps
Hope this helps.
Sent from my RAZR HD using XDA Free mobile app
Click to expand...
Click to collapse
I did all that. I refalshed stock ROM then rooted, installed CWM, then flashed cache, dalvik, data, and formatted system. I then installed M8 but still the device freezes occasionally and reboots.
goldfinsh said:
I did all that. I refalshed stock ROM then rooted, installed CWM, then flashed cache, dalvik, data, and formatted system. I then installed M8 but still the device freezes occasionally and reboots.
Click to expand...
Click to collapse
I will try to reproduce your issue to see if this is not only you. I mostly use Firefox for more than 15 minutes, reading and stuff, and have never noticed that. Going to do the same with chrome for the same amount of time and see what happens.
Sent from my RAZR HD using XDA Free mobile app