I got a question here and now the s stuck.
everything done perfectly and I downloaded CM7, updated it. and then the chaos started.
the phone just show up the startup image, after about 20 seconds, it keeps load the startup image again and again.
I am thinking it's keep reboot the system but just won't start the system.
I flashed RC4 version CM7 as well and same problem. It seems it's not the rom problem. should be something wrong with the phone.
can someone help me here?
thanks
did you do a full wipe before flashing it?
Get into your recovery and wipe the data, the cache, and the dalvik cache, then flash CM7
marcoso2 said:
I got a question here and now the s stuck.
everything done perfectly and I downloaded CM7, updated it. and then the chaos started.
the phone just show up the startup image, after about 20 seconds, it keeps load the startup image again and again.
I am thinking it's keep reboot the system but just won't start the system.
I flashed RC4 version CM7 as well and same problem. It seems it's not the rom problem. should be something wrong with the phone.
can someone help me here?
thanks
Click to expand...
Click to collapse
Related
Hey, question. Every single CM from 6.0 I have downloaded I have had issues with. I love the rom, but every time I get the same issue. When I install the rom all worked fine. I wipe all data, clear cache, and have to reinstall of course everything, my issue is that my phone will randomly freeze. Sometimes I get an error message saying the process process.android has failed, other times it just freezes. Does anybody have any ideas?
I loved CM 6.1 best Rom I've had yet. But after a week it started acting up and having problematic auto shutdowns like 8 times a day. I then searched for another stock Rom and tried skyraider vanilla, I hate it. It's basically skinned sense. That's it. I enjoy sense but it eats battery. My favorite roms so far are the desire Hd Rom and
CM but without the shutdowns is be perfect.
Sent from my ADR6300 using XDA App
only people
So this is the only other person I have run into with this problem. Everybody else I have talked to over other forums or IRC has never heard of these issues at all.
The only time I've ever had those shut down issues is when I start screwing with themes or when I start screwing with kernels or overclocking. I'm not sure what you've got going on there though
Well...
Well I have done some of that however I have reverted to "stock" several times. I have Hboot .92 installed also, i saw something online. The latest radio is also installed. I guess has anybody else seen any issues like this?
Try formatting the system in addition to wiping. CM does not format anything when you flash it. In CWM its under mount sd section.
Sent from my Htc Incredible using XDA App
This happened to me today, I am 99% sure it was the kernel I had installed though. I put back invisiblek's #18 and had no problems before or after.
okay I can mess around with that and see what happens then.
justinmburrous said:
okay I can mess around with that and see what happens then.
Click to expand...
Click to collapse
Let us know please.
This morning, I d/l the cyanogen 6.1 stable from ROM Manager, I then rebooted my phone into hboot then into recovery console. I then did a wipe of dalvik and battery stats. I then did the wipe data and then the clear partition cache, I then flashed the Cyanogen 6.1 Inc rom... then went fine... I loaded up into Cyanogen I then did a reboot and that's when my phone would not leave the HTC Incredible screen when rebooting! any ideas that can help me? I really like the Cyanogen ROM
Help!!! please!
neur0tk said:
This morning, I d/l the cyanogen 6.1 stable from ROM Manager, I then rebooted my phone into hboot then into recovery console. I then did a wipe of dalvik and battery stats. I then did the wipe data and then the clear partition cache, I then flashed the Cyanogen 6.1 Inc rom... then went fine... I loaded up into Cyanogen I then did a reboot and that's when my phone would not leave the HTC Incredible screen when rebooting! any ideas that can help me? I really like the Cyanogen ROM
Help!!! please!
Click to expand...
Click to collapse
You need to be a little more specific but do this.
1. Click on the Cyanogen link in my signature and download it.
2. Download google apps
3. Reboot into recovery
4. Wipe Data/Factory Reset
5. Wipe Cache Partition
6. Wipe Dalvik Cache
7. Select install zip from SD card and choose the cyanogen ROM, let it install
8. Select install zip from SD card again and choose the google apps.
9. Reboot your phone and sign into your google account and let everything sync
This is the best way to do it. Not through ROM Manager.
If this doesn't work then I have absolutely no idea. That is the 100% correct way to flash a ROM.
neur0tk said:
This morning, I d/l the cyanogen 6.1 stable from ROM Manager, I then rebooted my phone into hboot then into recovery console. I then did a wipe of dalvik and battery stats. I then did the wipe data and then the clear partition cache, I then flashed the Cyanogen 6.1 Inc rom... then went fine... I loaded up into Cyanogen I then did a reboot and that's when my phone would not leave the HTC Incredible screen when rebooting! any ideas that can help me? I really like the Cyanogen ROM
Help!!! please!
Click to expand...
Click to collapse
I had to revert back to #18 kernel working fine now!
neur0tk said:
I had to revert back to #18 kernel working fine now!
Click to expand...
Click to collapse
Yeah I mentioned it earlier in this thread. For some reason #21 and #22 do not like cyanogen.
I'm running #21 on my phone and I haven't had any issues yet.
Yeah IDK either... I had to revert now it's running like a champ! love the Inexus theme!
ok an update, I have everything working. I an using cm6.1, latest radio (on cm site), kernel 27, hoot .92, and the very latest clockwork that just came out. I know those last two should not matter, just letting you know. As of right now my phone is not freezing and everything works fine, even faster than before. When I first turned it on the phone did freezer and after that yet took a long time for 3g to start working. On reinstall I did a total revert to stock then did a factory reset and cleared all caches and everything on the phone there is to clear. It has been afew hours. I will update this if there are any more problems
Sent from my ADR6300 using Tapatalk
Keeps rebooting more and more time to switch roms
Justinmburrous
Justinmburrous.com
I searched everywhere, but can't find the same problem as mine. I am stuck in the CW recovery screen, after rebooting times after times.
I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install (flash), I hold the power forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stack at the cw recovery screen. Help...
I love my nook and have a road trip coming up. It will be nice to watch a kid movie to keep the kids entertained.
Had you flashed CmWR into eMMC?
Check the ROM information on /dev/block/mmcblk0p2.... this sounds a LOT like the problem 12paq had...
http://forum.xda-developers.com/showthread.php?t=1495913
@Dizzyden, thanks for the tip.
I did repartition to 1g/5g awhile back. I am not sure where to start. 12paq tried many things, which one was the solution? Your rombackup.zip?
Many thanks....
@votinh
what do you mean? I am not using the N&O apps or OS. Pure CM9, therefore I guess it is flashed in eMMC. If not, please advice.
DizzyDen said:
Check the ROM information on /dev/block/mmcblk0p2.... this sounds a LOT like the problem 12paq had...
http://forum.xda-developers.com/showthread.php?t=1495913
Click to expand...
Click to collapse
how can I check this"Check the ROM information on /dev/block/mmcblk0p2"?
please advice.
I tried to adb shell the nook, but not devices found? please help.
Finally, with the help from the good people of this forum, I was able to restore back to B&N, and reflash CM9 from there.
Thank to you all.
Yesterday my nook color was working great. Today I turned the screen on and it hung. Now I'm having the above problem with it hanging at clockwork recovery.
I've got CM7.1 stable on there running from emmc.
can't get adb to recognize the device since it is in cwr... how did you do it?
chilimac02 said:
can't get adb to recognize the device since it is in cwr... how did you do it?
Click to expand...
Click to collapse
Install the google drivers for adb... if you are in CWR adb is enabled... just have to get the drivers loaded on your computer.
try this:
http://forum.xda-developers.com/showthread.php?t=958748
dumper1234 said:
I searched everywhere, but can't find the same problem as mine. I am stuck in the CW recovery screen, after rebooting times after times.
I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install (flash), I hold the power forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stack at the cw recovery screen. Help...
I love my nook and have a road trip coming up. It will be nice to watch a kid movie to keep the kids entertained.
Click to expand...
Click to collapse
It may be that your "boot to recovery" flag is set, and if so, it will always boot to that until it is cleared. When the cyanogenmod logo comes up hold the n button until the boot menu comes up. Then choose boot to emmc. If it works, go to ROM Manager and flash a new CWM Recovery to emmc.
Welcome to the nightmare I lived last week. Don't worry I woke up, was able to fully recover and forget the dream ever occurred.
I to tried to reformat to 1gb/5gb and ended up in the same boot loop.. If you are in the same spot I was, your boot partition got wiped out. And you may notice EMMC is gone.
After much searching I came across a file... Looking....Looking...Looking...
..........................Ah yes here it is. Here is what worked for me.
1. Boot to recovery (Should be easy at this point)
2. Format System, Data, and Cache.
3. Install the attached Zip file. (RecoveryFix.zip), this should recreate the Boot partition and fix the EMMC.
4. Reboot to recovery
5. Install favorite Rom or restore from backup.
6. Reboot to test.
Again this is what finally worked for me, and I went through a lot of trial and error to get there. I am guessing at your situation being exactly the same as mine.
PS. Ignore my since of humor if you need to.
Hello all,
I realize you all are busy but I'm at my wits end here. I installed my bootloader and recovery using afterOTA. This worked really well, I installed Thor 1.7.3 recovery and ICS V8 bootloader using the utility. I then booted into recovery and did a factory reset (really), reset cache and dalvik, battery settings as well... I then went to install ZIP (JB 4.1.2 CM10-FLEX v6supercharged_Aroma-Rev3.4) from internal storage (download folder). I customized the ROM then went back and installed the random apps...
After this was done I hit next and installed the ROM. It didn't take as long as I thought it would, and I hit reboot when it was done, but came to a screen that I could press next on. The installer screen said it was installing permissions, it didn't say that it was completely finished, just installing permissions or something, but I was able to press next.
After rebooting, it started the stock android boot animation, got to the upgrading applications screen, after the applications were done "optimizing" it went back into the stock android boot animation. It never came out of it.
I'm confused as to what I am doing wrong.. I've flashed ROMs multiple times and I thought this one would be the easiest out of all of them considering I didn't care about the data on it and I'm just playing around.
Any help would be appreciated. Thanks!
Fixed.. I'm an idiot
GermanDoerksen said:
Hello all,
I realize you all are busy but I'm at my wits end here. I installed my bootloader and recovery using afterOTA. This worked really well, I installed Thor 1.7.3 recovery and ICS V8 bootloader using the utility. I then booted into recovery and did a factory reset (really), reset cache and dalvik, battery settings as well... I then went to install ZIP (JB 4.1.2 CM10-FLEX v6supercharged_Aroma-Rev3.4) from internal storage (download folder). I customized the ROM then went back and installed the random apps...
After this was done I hit next and installed the ROM. It didn't take as long as I thought it would, and I hit reboot when it was done, but came to a screen that I could press next on. The installer screen said it was installing permissions, it didn't say that it was completely finished, just installing permissions or something, but I was able to press next.
After rebooting, it started the stock android boot animation, got to the upgrading applications screen, after the applications were done "optimizing" it went back into the stock android boot animation. It never came out of it.
I'm confused as to what I am doing wrong.. I've flashed ROMs multiple times and I thought this one would be the easiest out of all of them considering I didn't care about the data on it and I'm just playing around.
Any help would be appreciated. Thanks!
Click to expand...
Click to collapse
Well, I kept working on it and I think I was just impatient. Maybe. Either way I went back and tried to reflash several times, doing the wipes from the wipe screen each time. No luck. Eventually I went and formatted the /system /data and all the other options in the mount/storage menu. I then did all the "wipes" again and reflashed. It worked this time! Running incredibly smoothly.
Thanks for reading everyone.
Hi. My Nexus 4 got stuck in a bootloop while attempting to flash the PAC-man ROM and I have no idea what to do!
I am a total noob at this, so I'll just go through the details. I cleaned Dalvik and Cache and then flashed the files: pac_mako-22.2.0-rc1(Downloaded from official PAC-ROM site) and gappsinverted-jb-20130308-signed(From rootzwiki). After flashing these two, I tried starting the phone. The minigame turned up and then it moved on to the 'PAC is LOADING' screen. It stayed like that for 15 minutes... The only way I knew the phone hadn't hung was because there was the constant movement of the loading bar. So I got into TWRP recovery again and flashed Paranoid Android back so the device would be usable again.
I really want to try PAC-man and would be grateful to anyone who can help me out...
noobvorld said:
Hi. My Nexus 4 got stuck in a bootloop while attempting to flash the PAC-man ROM and I have no idea what to do!
I am a total noob at this, so I'll just go through the details. I cleaned Dalvik and Cache and then flashed the files: pac_mako-22.2.0-rc1(Downloaded from official PAC-ROM site) and gappsinverted-jb-20130308-signed(From rootzwiki). After flashing these two, I tried starting the phone. The minigame turned up and then it moved on to the 'PAC is LOADING' screen. It stayed like that for 15 minutes... The only way I knew the phone hadn't hung was because there was the constant movement of the loading bar. So I got into TWRP recovery again and flashed Paranoid Android back so the device would be usable again.
I really want to try PAC-man and would be grateful to anyone who can help me out...
Click to expand...
Click to collapse
You have to also wipe DATA when you flash a new ROM. Use the factory reset option.
also, your gapps are out of date. you got stuck at rebuilding the dalvik, which is kinda normal for android 4.3. all you have to do, should have to do, is force reboot once or twice until the dalvik gets rebuilt, then itll boot.
simms22 said:
also, your gapps are out of date. you got stuck at rebuilding the dalvik, which is kinda normal for android 4.3. all you have to do, should have to do, is force reboot once or twice until the dalvik gets rebuilt, then itll boot.
Click to expand...
Click to collapse
Sorry, but I don't know what you mean by 'force reboot'. Could you walk me through the steps please? Thanks!
noobvorld said:
Sorry, but I don't know what you mean by 'force reboot'. Could you walk me through the steps please? Thanks!
Click to expand...
Click to collapse
Hold the power button for about 10 seconds.
You are trying to use 4.2.2 gapps on 4.3 rom
I apologize if there is a thread for this but if it exists, I cant find it.
My nexus 4 lags for 5 minutes on Google screen, THEN still boots. I also have no wifi... Even after reflashing boot img, and doing a full wipe
I recently messed up my CWM recovery, and was stuck on stock. I was able to fix it, reflashed CWM using abd and fastboot, everything was successful. Ever since, when my phone loads, it stays on the Google screen for 5 minutes, before it ever starts the rom bootup. This is not just a specific rom, its even happening on stock ROM. My phone does boot, so this is just a OCD fix now, but a 7-10 minute boot for my phone... is kinda crazy. Does anyone have a solution?
xtjx09 said:
I apologize if there is a thread for this but if it exists, I cant find it.
My nexus 4 lags for 5 minutes on Google screen, THEN still boots.
I recently messed up my CWM recovery, and was stuck on stock. I was able to fix it, reflashed CWM using abd and fastboot, everything was successful. Ever since, when my phone loads, it stays on the Google screen for 5 minutes, before it ever starts the rom bootup. This is not just a specific rom, its even happening on stock ROM. My phone does boot, so this is just a OCD fix now, but a 7-10 minute boot for my phone... is kinda crazy. Does anyone have a solution?
Click to expand...
Click to collapse
Try dirty flashing (only wipe cache and dalvik cache) your exact ROM.
abaaaabbbb63 said:
Try dirty flashing (only wipe cache and dalvik cache) your exact ROM.
Click to expand...
Click to collapse
I will try but I dont think its gonna fix it... worth a shot. But I also found out I have no sound... I'm kinda getting worried here.