CM7 rendered my phone useless - Nexus One Q&A, Help & Troubleshooting

I flashed with the stable build of CM7 on my N1. This the first time I have flashed it.
For awhile it was working ok. There were a few bugs here and there, but no showstoppers.
But now, the Launcher has decided to not work at all. It's completely unresponsive to any touch, and it's in an infinite FC loop. My phone is useless now. I've rebooted, powered off, cleaned the cache -- nothing is working.
My question is... can I flash it back to stock? This is beyond frustrating, and I'd rather just stick with a no frills stock OS without all the bells and whistles.

Yes, read the wiki's on how to flash to stock.

Did you do a full wipe before flashing cm7? This include welling the system partition

i followed each and every step of the CM7 instructions.
thanks! i will look into it.

If you flashed CM 7.1 Then i had the same problems as my N1 locked solid.
After a few minutes of flashing it used to become unresponsive and all.
I tried everything but sadly havent been able to find a solution.
I say you should try Cm 7.0.3 That is very stable. I am currently using that and am loving it!!

Related

Constant rebooting

i have had my ATT N1 for a few months now and all has been great. I rooted awhile back and have been using Cyanogen 5.0.7 to great success. I have the pershoot kernal and never really had any issues.
Well, that has all changed. Recently I have been rebooting any many different occasions. It almost always does it when I am in Maps and navigation, which is not good because I need it in my life having relocated.
I have decided that maybe I will look to update my Cyanogen or maybe go over to 2.2. I did this today and still having these issues. I tried Kang and it still rebooted randomly and when I tried Modacos r17 it just would keep rebooting at the setup screen. I think that has to do with not having the stock kernal.
Any clues as to what is happening? I really need help and do not want to stop using Android, but I need my phone to be reliable.
If it happens on any ROM and with no correlation to anything - sounds like HW problem.
Did you use overclocked kernel?
I do have a overclocked under volted kernal
sounds like bad sw. get back to stock 2.1 update 1 (if you can) and see if your phone is stable...
WIPE all ( everything ) , and flash 2.2
http://forum.xda-developers.com/showthread.php?t=692609
Follow those 3 easy steps there !
Does your phone lock up (unresponsive) before rebooting?
Phone doesnt lock up. I tried wiping evertyhing but could not wipe the sd partition. Is that necessary? I have done full wipe's (data, dalvik, & cache) and still had similar results. I have updated my kernal to the newest pershoot and I installed Kang .9b1 and so far have only had 1 rebbot. It happened when I was in the browser and went to a flash heavy site to see how it worked. Is there any 2.2 roms that keep it close to stock? I am not a total fan of adw launcher.
Have a look in this thread,
http://forum.xda-developers.com/showthread.php?t=703687
I'm really determined to figure out what is causing this issue for so many people! I've managed to cure my reboots for the time being, and it seems it is kernel related. That said, we need as many people as possible to give feedback as experiences seem to differ in regards to the ROMs and Kernels people are using.
Regards.
I looked over that thread and see some similarities but it is still not totally consistent with my issues. I am running Kang now fine but still have reboots that I won't call so random anymore. It happens when I use Maps for the first time, and definitely when I go to a flash site on the browser.
I cannot successfully use any other ROM since once I install it it goes into boot loop. This is driving me crazy and do not like the thought of being stuck to one ROM since it is the complete reason I bought this phone.

[Q] Boot Loop when installing ROM

Hey guys; i'll try to provide you with all the information but honestly i'm not 100% on all of it so try and be patient.
I'm trying to go back to SuperE from Froyo by Laszlo which was absolutely killing my battery without me even using it. However, every time i flash it (and i wipe everything) after it goes past the G1 screen it just resets again.
I'm not sure if this is maybe because of the new kernel (2708) which i'm PRETTY sure i have, but am not 100%. I do know that i have one of the new radios though.
Would the kernel be causing the problem? If so how do i downgrade?
I hope you can help me out!
Thank you!
Q: Can you mention step-by-step what did you flash? And confirm the exact setup before flashing. I believe you mentioned your radio is 2708.
Powered by Android
Thank you for replying. I'll definitely try.
I'm back on FroyoByLaszlo-int2.1 because i couldn't successfully flash either Super D or Super E.
My Radio is 2.22.28.25
Kernel version says 2.6.35.10 - froyobylaszlo
Basically i did what i always do. I wiped everything, first by flashing the "all-wipe" and then going back and wiping it all manually.
Then i flashed the appropriate gapps, followed by the ROM. Rebooted afterwards, but every time it gets passed the G1 screen it reboots.
The only thing i can think of is incompatibility with the kernel but then again, i don't know crap, so that's why i'm asking
Yep, most likely it is indeed the incompatibility of the kernel with the radio.
I'd try flashing the ezBiffTestKernel20101106-2708.zip after the ROM+GApps.
Just use Google to find the kernel.
Powered by Android
The battery drain could be becos of the new kernel. Try installing the 35.9 kernel from ezterry (the one he had for CyanogenMod 6.1 2708) It is working good for me, the battery last for a whole day.

[Q] g/aaps not sticking in CM7

[question]
I got a nook color this morning. Got it rooted, Got CM7 up and running but for some reason the Gapps are not sticking when i flash the ones that they recommend in the Cyanogen Wiki. I did a quick, and i do stress quick, google search to see what could be going on and i didn't see anything.
i did boot back into recovery, wipe, flash, reinstall and nothing. So if some could point me in the right direction i'd love you for ever.

[Q] froyo or ginger?

I am in dier (sp?) need of a new rom. I'm currently running cyanogen ..dont know what version but its the purple glass one. Lately everything is coming up as errors, my camera doesnt even work 98% of the time, and it takes about 3 minutes just to dial someone.
So question of the day: I was told by someone I consider "superior in phreaker knowledge" that I shouldnt run 2.3 on my phone. Mainly because his is *so much better than mine* but whatever.
I just need a good rom, a FAST one. I am open to suggestions. And if running 2.3 on my hero is stable and fast then I am open to it. preferably something less glitchy.
Try aosp's new gb build
Sent from my HTC Hero CDMA using XDA App
I ran cyanogen 6 for a while, then Jaybobs extblue froyo build for about 6 months. I've had Aosp's gingerbread mod since Feb, and it is by far the best rom I've ever had.
Yep asop 2.3 best rom I have tryed
clutch_08 said:
Yep asop 2.3 best rom I have tryed
Click to expand...
Click to collapse
+800%. The AOSP Froyo build is awesome, but there is nothing like showing off our little Heroes running Gingerbread like a dream. AOSP 2.3 is damn good.
As of the 4/21 build of AOSP, I would highly recommend it as the go-to gingerbread rom. CM7 and Gingersense are all well and good, but nothing has felt quite as snappy as this build (ymmv). It's also a smaller download than the others by a good margin. Not to mention GB includes a built in CPU governor, so you'll no longer need SetCPU. Seriously, just try it out.
ahhhhhhhhhhh!!!!!!!!!! ive tried flashing 2.3 3 times now. ive tried re-downloading the file, tried downloading it to the phone and via sugarsync, tried wiping everything and it keeps showing "android" then goes to set up, then back to android, then back to set up. guess im going with 2.2
What all are you wiping before you flash?
followed a guide since it'd been over 6 mns since my last flash. did the factory reset, wiped cache, i think those were the only 2 options it gave me to wipe.
MyHerox25 said:
followed a guide since it'd been over 6 mns since my last flash. did the factory reset, wiped cache, i think those were the only 2 options it gave me to wipe.
Click to expand...
Click to collapse
First, if you have the sprint radio that ends in .27, you should upgrade it to .29. Second, if you don't have clockworkmod recovery, get it because it wipes all the correct stuff. Third, go to this site and follow the step by step: http://romrepo.info/wiki/index.php?title=Sprint_HTC_Hero
Definitely get ClockworkMod set as your recovery. I'm not even using the newest one and it works great. Every time I go to a new rom, I wipe the user data, cache, battery stats, and dalvik cache.
i already use rom manager and clockworkrecovery 2.3 just did NOT want to install correctly on my hero, so I went with asop (sp?) 2.2 and it worked perfectly. I love my hero once again- very fast.
Omg this Tom has been the answer to my battery nightmare. Since flashing, I can go all day without my phone dying (and I use it a LOT!)
Sent from my HERO200 using XDA App

Keep getting stuck on Motorola Logo installing CM9 SELFKANG

Tried to go from AXI0M to CM9 SELFKANG and after erasing data etc just like always (just like I have since original Droid) and installing the new Rom I get stuck on the Motorola Logo. I have SBF 3 times now and every time I install CM9 SELFKANG (3 different builds) I reboot and get stuck on the M Logo.
I have let it sit on the M Logo for almost 20 minutes.
I double checked everything and let the stock ROM settle before I did anything and everything did work 100%. I then installed Eclipse 2.2 and everything went perfect.
Gummy_targa-Release-2012-03-06-21_01.zip (Also an ICS ROM) installs no problem also. I just get really REALLY spotty data.
I tried again. Downloaded CM9 SELFKANG from a new source, double-checked I formatted system etc, and even didn't install GAPPS encase that was messing things up and STILL I am getting stuck on that damned logo.
I am out of ideas. Going to try and install AOKP next since it is almost the same thing. It is really annoying me. Anybody have an idea as to WTF is going on? As this is really confusing me. The only thing that makes sense is I am getting a bad download but I have downloaded now 5 different builds, one of them from a different location.
Any ideas?
What I am trying to install:
http://www.droidhive.com/forums/index.php?/files/file/38-cm9-selfkang-bionic-ics-403-r1-nightlies/
What has installed fine since first M Logo:
http://forum.xda-developers.com/showthread.php?t=1327695
http://goo.im/roms/teamgummy/targa
http://www.droidhive.com/forums/index.php?/files/file/37-aokp-selfkang-bionic-ics-403-r1-nightlies/ (I think I am going to stay with this ROM. I would still like to know why CM9 SELFKANG is doing that though. But not doing it with anyone else.)
What I was originally on before this mess:
http://www.droidhive.com/forums/index.php?/files/file/39-aokp-m4-axi0m-kang-bionic/
Are you using bootstrap or safe strap?
The later CM9 builds are not compatible with bootstrap.
Sent from my Xoom using xda premium
That's it! Wish they said so on there ROM page.

Categories

Resources