I am having a bit of a problem here. Being a member with less than 10 posts I cannot post this in the development forum. Annoying.
Anyway, I have flashed CM7 - Nightly 23 on to my Wildfire, and it works great. I tried flashing 26 but the phone.apk fc everytime, so nandroid restored and then flashed app.zip. Tried re-flashing Nightly 26 or any newer Nightlies (32, 47, 48) to no avail. In reboot, the CM7 splash screen appears but stutters as if it is loading then freezes. I have left it over night to see if it was just loading but it had crashed. Why is this? I wipe cache & dalvik cache, still nothing. I have tried flashing with Clockwork or ROM Manager but still I cannot get past the CM7 splash .
Solutions ?
aldersonalex said:
I am having a bit of a problem here. Being a member with less than 10 posts I cannot post this in the development forum. Annoying.
Anyway, I have flashed CM7 - Nightly 23 on to my Wildfire, and it works great. I tried flashing 26 but the phone.apk fc everytime, so nandroid restored and then flashed app.zip. Tried re-flashing Nightly 26 or any newer Nightlies (32, 47, 48) to no avail. In reboot, the CM7 splash screen appears but stutters as if it is loading then freezes. I have left it over night to see if it was just loading but it had crashed. Why is this? I wipe cache & dalvik cache, still nothing. I have tried flashing with Clockwork or ROM Manager but still I cannot get past the CM7 splash .
Solutions ?
Click to expand...
Click to collapse
instal zip with CM7 -> then flash kernel 4.1 -> reboot
this must help you
I had the same problem with cm7 in the end i just installed it of rom manager
Related
Unable to post in developer section, have been using custom roms since February.
Sorry if this is in the wrong section, merge it and delete this paragraph if you must with http://forum.xda-developers.com/showthread.php?t=911364&page=1278
Had wolfbreaks rom running previous to installing FXP030 and unlocking bootloader, had issues with wolfbreaks rom. FXP030 seemed great and worked well, aside from the odd glitch. Had ran it for 2 days. Tried to update to FXP030b to test out new fixes (use the camcorder often) and upon flashing new kernel FTF file, phone booted, wiped cache, factory reset, wiped batt stats, wiped dalvik cache. loaded up the custom zips, for FXP030b + gapps, booted fine, couldn't get wifi working, couldn't connect with 3g. Tried to crash system server inside bad behavior in the dev tools as per instructions from collosus. upon crashing system service, phone hung hard for over 20 mins stayed on same screen, did not boot again till i flashed stock kernel. Not even FXP030 worked at that point. Hope I was not close to bricking my device.
quanium said:
Unable to post in developer section, have been using custom roms since February.
Sorry if this is in the wrong section, merge it and delete this paragraph if you must with http://forum.xda-developers.com/showthread.php?t=911364&page=1278
Had wolfbreaks rom running previous to installing FXP030 and unlocking bootloader, had issues with wolfbreaks rom. FXP030 seemed great and worked well, aside from the odd glitch. Had ran it for 2 days. Tried to update to FXP030b to test out new fixes (use the camcorder often) and upon flashing new kernel FTF file, phone booted, wiped cache, factory reset, wiped batt stats, wiped dalvik cache. loaded up the custom zips, for FXP030b + gapps, booted fine, couldn't get wifi working, couldn't connect with 3g. Tried to crash system server inside bad behavior in the dev tools as per instructions from collosus. upon crashing system service, phone hung hard for over 20 mins stayed on same screen, did not boot again till i flashed stock kernel. Not even FXP030 worked at that point. Hope I was not close to bricking my device.
Click to expand...
Click to collapse
Hi Buddy,
What you should have done when your phone froze after crashing the system server is to have taken your battery out and then just re-booted your phone, all would have been good.
If you are still at the same stage now from when you posted just flash the fxp kernel in the flashtool provided by J, your phone will now boot with FXP030b.
You was never close to bricking your phone so do not worry.
Hey there! I was updating my version of Paranoid Android and my kernel and it seemed fine at first but It yield some odd problems. I went into Clockworkmod recovery and Flashed my rom and kernel I then proceeded to wipe my cache and dalvik cache. I have done this many times before on many devices. I encountered a problem when I rebooted for the second time, I got the Android is updating apps display and I continued to get it every time I booted. The device would also randomly turn off when the screen dimmmed. I proceeded to set out and fix it. Here are the steps I took and the problems it caused.
Flashed stock rom-would not boot properly
Flash RESET kernel-I messed up and though this was a real kernel, my problems escalated from here.
Flashed stock rom and recovery.
Flashed reset kernel and then real kernel-Still had problems.
Flashed stock rom
My problems from all this accumulated somewhat and I can barely boot into fastboot. I get weird static screens and weird white noise sounds. It does not always let me boot into android and will get to the google logo 1 out of ten tries.
These is really unnerving and I have no clues whats what.
Note: I am using Faux123's kernels and his reset kernel.
Thanks a lot for any help!!!
I tried loading the latest build (CM10 11/28) onto my defy. I completely forgot to load gapps afterwards and went ahead and rebooted. Now, it gets stuck on the cyanogenmod logo and does not boot past that. The only thing I can do is remove the battery. When I reboot, the same thing happes. Unfortunately, I no longer get the boot menu so I can't even run recovery from my backup.
How can I fix this so I can use my phone again?
atlcr said:
I tried loading the latest build (CM10 11/28) onto my defy. I completely forgot to load gapps afterwards and went ahead and rebooted. Now, it gets stuck on the cyanogenmod logo and does not boot past that. The only thing I can do is remove the battery. When I reboot, the same thing happes. Unfortunately, I no longer get the boot menu so I can't even run recovery from my backup.
How can I fix this so I can use my phone again?
Click to expand...
Click to collapse
Nevermind...apparently pressing vol. down when the LED flashes blue gets me to a boot menu. Pheww!
Got it loaded, but having several problems: cannot connect to Play store, cannot receive phone calls, and email is spotty.
Please ask all questions in Q&A. Thread moved there.
atlcr said:
Got it loaded, but having several problems: cannot connect to Play store, cannot receive phone calls, and email is spotty.
Click to expand...
Click to collapse
Your Gapps not working correctly, probably you installed incorrect ones, I recommend you to repeat the whole process:
1 full wipe x2 (you loose data so if you have data ensure yourself a backup)
2 flash stock sbf with rsd lite
3 root your phone
4 install 2ndinit
6 install cm10 from custom recovery
7 full wipe again
8 boot phone at least once
9 install quarx minimal gapps (thats your actual problem, your gapps not working correctly)
10 wipe again
11 restore backup if any.
3ze said:
Your Gapps not working correctly, probably you installed incorrect ones, I recommend you to repeat the whole process:
1 full wipe x2 (you loose data so if you have data ensure yourself a backup)
2 flash stock sbf with rsd lite
3 root your phone
4 install 2ndinit
6 install cm10 from custom recovery
7 full wipe again
8 boot phone at least once
9 install quarx minimal gapps (thats your actual problem, your gapps not working correctly)
10 wipe again
11 restore backup if any.
Click to expand...
Click to collapse
I don't think he has to flash the sbf, just flash gapps n wipe data n cache. also try dalvik cache
Sent from my MB526 using xda premium
You could simply install a new .zip from recovery. You could use the same CM10 11/28 or any other rom. This shoud work out for you.
I experienced the same with my Defy today and I installed a new CM 10 09/05 by Epsylon and it worked like a charm.
Thank you for the replies!
I had to flash it a hundred times to get it to work (I kept getting write access errors for cache folder). What ended up working was to wipe everything and install the 9/24 build. From there, I rebooted and installed (without wiping) the latest build along with the correct gapps. It works fantastically now! My phone is soo much more responsive and I'm loving CM10.
3ze had it right. I was using the latest gapps (12/2) instead of the "minimal" version in the quarx dir.
I haven't noticed a battery drain as has been widely reported here. In fact, it seems to be less of a drain now though that is likely due to the fact that I wiped everything and only installed apps I needed this time around. Tons of unnecessary apps could explain why my battery life was less before.
I have noticed a slight difference in reception now though. Places that used to be fine for connecting to the network (Tmobile) have now become less strong and frequently dropping out. I wonder if the signal strength could have been messed with?
First off, thanks for all the great information on this site. It has gotten much mileage out of our Nook Color.
Now, the issue. I installed the latest cyanogenmod 10.2 nightly and it worked great. I installed some apps, rebooted, and all was well. Installed some more, rebooted and now I'm stuck at the cyanogenmod boot animation. I did force hardware acceleration in 2D (or whatever that option is called) to see if it helped some games... could that be it? I tried clearing cache and dalvik cache and it "optimized", then stuck on the screen again.
What are my options here? I really don't want to go through loading apps all over again. Any help is appreciated!
Hi all,
I've had CM11 installed and running on my Mi2s for a while and then my screen got cracked. Long story short, 2 month later i'm back to my Mi2s and CM11 does not start, it gets stuck on CM logo boot animation for a very long time (i think the longest i let it run was about 10 minutes).
Things i've tried with the same result:
DATA WIPE / FACTORY RESET, then re-install
DATA WIPE / FACTORY RESET, and installing other simialr ROMs: Omni, Gummy, Lungo
Installing same as above but on 2nd system (where I have WIUI)
Only similar ROM that did start was Mokee. WIUI also starts-up with no problem.
Any suggestions?
Thanks,
-arnon
Nobody?
Some more stuff i tried:
I've run the re-partition script hoping that the bootloop was due to not enough space, but no luck either.
I've also tried to format /system and then install, but no go.
Tried to install CM10.2.... nope
did you check that you have installed the correct rom for mi2s? you should download in ARIES in mokee. i have same problem with you before and I found that i downloaded a wrong rom from xiaomi forum.
cheers