Okay, so I have installed cm on 3 phones so far, and thought I had it down. Apperently not.
I flashed the .nbh, used upgrademyg1.com/root.apk, and attempted to install the latest cyanogen. Upon doing so, the phone would hang at the g1 logo. I attempted wiping and repeating to no avail. Thinking perhaps I had corrupted files, I redownloaded cm, with the same results. I can enter recovery. This is not my phone, and would be very appreciative of any help.
Thanks!
-
EDIT: Did everything over again and worked fine - thanks guys!
Related
Hello everyone,
I was hoping someone could help me out with a bit of a problem I'm having here. I'm becoming rather scared and a bit desperate.
I just tried to install cm6 onto my nexus one, which I have done on a previous nexus one without any problem. I unlocked the bootloader, flashed amon ra's recovery image, and then updated the radio. I did all of this manually, not using clockwork or anything of the sort. I proceeded to install cyanogen's and google's addons, and everything seemed to go smoothly. I rebooted the phone and it got stuck in a bootloop. It flashes the nexus boot image and then the blue cyanogen one but just gets stuck there and tries to go at it again, failing every time. I have repeated this entire process twice, both times making sure I wiped the data and the cache, and the same unfortunate event has happened both times. Please could anyone help me out here?! I really need someone's help right now. I'm kind of panicking.
Thank you everyone for your replys. Any help is welcome help! I'm fairly knowledgable with ADB and rooting. I've been doing it quite a while now.
CM6 is very beta at the moment. If you're running one of the RC builds, try flashing a nightly build. It might make things better (or worse).
I've noticed other people seem to be having this same problem and there hasn't really been a distinct solution that I can see, so hopefully this question will be helpful in the future and not repeatative.
I've been trying to update to CM7 from CM 6.1.2 on my Evo. I followed instructions from here http://forum.xda-developers.com/showthread.php?t=902051 and downloaded all the recommended software. First I tried to just flash the rom, then the kernal, then the gapps. All seemed well at first, and I got past the Evo 4G screen, but it got stuck booting on the Cyanogen animation (the arrow just keeps going!)
Then I tried to wipe the Davlik-Cache, and rebooted again. I left the phone alone for about 45 minutes, and it still got stuck on the Cyanogen animation.
Finaly, after searching through the forums, I found another post which suggested I do a hard reset then flash the rom, kernal and gaaps then clear the cache and davlik-cache. Still, I'm stuck on the animation. I have a nandroid backup, so I can get back to 6.1.2, but I'd really like to get CM7 working, anything else I should try?
You should't have to do the kernel separately unless you have a specific reason for doing so the ROM comes with a kernel for you. I had a similar problem with my HTC however I was able to get it resolved by installing gapps. Here's what I did -->
Used ROM Manager to go back to working ROM
From working ROM, accessd ROM Manager and chose rebooted into recovery mode
Once in recovery cleared/wiped everything (cache, data, delvik) installed gapps then cm7
Restarted
It did take awhile after restart to get going however once it did it worked marvelously!
Hope this helps and good luck!
Reboot
Similar Problem, Defy CM7 Bootloop
The first time i tried installing CM7 I got a boot-loop. I have tried at least 7 different tutorials all with different variations of flashing this and wiping that yet none yield results. Still stuck at boot-loop.
The most recent thing i have done was used RSD Lite to flash
"JRDNEM_U3_3.4.2_179-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTCEE_P016_A016_HWp3_Service1FF.sbf"
this got my phone running again, i then pulled off some magic by rooting using a combination of super1click, Z4 and installing superuser myself. after that i copied the files for a bootmenu into my /data/ folder. using CWM Recovery v2.5.1 flashed
"freq_F_US_342_107-850-1700-2100-signed.zip"
to get my 3G running again, and gave up of CM7.
If anyone has anything that could help id appreciate it.
(ps. i've tried many variations of wiping things and re-flashing things)
I hope this hasn't been asked before, but I'm afraid it probably has.
Just unlocked and rooted my N1. After I rooted my device, I downloaded RomManager, then flashed the Clockwork Mod recovery and flashed the alternate recovery. I also downloaded Cyanogen Mod 6.1.1.
I rebooted and it has been stuck on the Cyanogen mod skateboard guy for the past 20 minutes or so. What did I do wrong?
it's hard to say. sometimes errors do occur while flashing a rom.
have you tried flashing the rom again?
Also, did you clear all data before flashing the rom the first time?
Well, crap the bed. I luckily figured it out.
I went into fastboot mode and cleared user data and it booted up just fine. I should have researched this a little more thoroughly before doing this. I knew I wanted my phone rooted, but the entire process wasn't quite as clear (to me) as it probably should have been. As far as I can tell, everything looks to be good to go.
A notification popped up in CM10 alerting me that there was a nightly build update available (stable & evita). I decided to go ahead and run the thing to see if it worked/what the deal was and it followed normal process.. Booted into recovery, attempted flash, rebooted to a black screen.
It appears that it attempted to update and subsequently failed so I booted into recovery and flashed the cm10.0.0.zip myself. Fortunately nothing was lost or bricked and even my phone settings were all there when I booted back up again after (what appeared to be) a successful flash. Any knowledge of this? Seems pretty weird to me so I figured I would ask.
THanks
Tom
tom0779 said:
A notification popped up in CM10 alerting me that there was a nightly build update available (stable & evita). I decided to go ahead and run the thing to see if it worked/what the deal was and it followed normal process.. Booted into recovery, attempted flash, rebooted to a black screen.
It appears that it attempted to update and subsequently failed so I booted into recovery and flashed the cm10.0.0.zip myself. Fortunately nothing was lost or bricked and even my phone settings were all there when I booted back up again after (what appeared to be) a successful flash. Any knowledge of this? Seems pretty weird to me so I figured I would ask.
THanks
Tom
Click to expand...
Click to collapse
Which One X do you have? I'm on the AT&T version and went through what you just said identically... however, after manually installing through recovery I'm still stuck in a boot loop/black screen. Unsure what to do at the moment. I don't know this stuff that well so I'm afraid to flash the build I had before without wiping (which I would really rather not do haha). I'd love to move to the stable version, although mine was pretty perfect as is. I just went ahead with the update for the hell of it, but that looks now like it was a mistake Any advice?
mittortz said:
Which One X do you have? I'm on the AT&T version and went through what you just said identically... however, after manually installing through recovery I'm still stuck in a boot loop/black screen. Unsure what to do at the moment. I don't know this stuff that well so I'm afraid to flash the build I had before without wiping (which I would really rather not do haha). I'd love to move to the stable version, although mine was pretty perfect as is. I just went ahead with the update for the hell of it, but that looks now like it was a mistake Any advice?
Click to expand...
Click to collapse
Cm10 stable works for me. But I installed it in recovery
Sent from my HTC One X-
I figured out the issue. I forgot that with the 2.20 firmware you have to flash the boot.img separately from the ROM. So after the update all I had to do was flash the boot.img and it was all ready to go again
I have been running CWM recovery and installing Wingray nightlies on my MZ604 without any problem for more than a year. A couple of days ago I flashed what I think was a partially downloaded ROM. This soft bricked my Xoom (somewhat unsurprisingly). I ended up in a boot loop so I used this method http://www.xoomforums.com/forum/motorola-xoom-development/18743-how-flash-sbf-rsd-method.html to get out of it.
That worked fine leaving me with a stock Xoom running 3.1.
I then unlocked the bootloader and flashed CWM Touch using adb. I then booted into recovery and flashed the universal Xoom root from here http://forum.xda-developers.com/showthread.php?t=1242241.
Again, this worked fine so now I had what appeared to be a fully functional Xoom running CWM Touch and 3.1. So far, so good.
The final step was to install a recent ROM so I booted into recovery again, flashed the latest Wingray nighly and the GApps package as I have done on numerous occasions (after doing a factory reset and wiping the cache and the Dalvik cache). This appeared to work just as it has always done but now my Xoom just sits at the M logo and nothing else happens. I can still boot into CWM Touch but my Xoom won't get past the M logo in normal boot.
Since everything seemed to work exactly as I would expect right up to the final boot, I'm somewhat mystified as to what is wrong. Can anyone give me any suggestions as to what to do next?
Now I can actually help you. I saw this a day ago but did not respond yet because I did not test my method.
It's been stated by a few in the eos 4 wingray thread that nightlies 204-205 are TEST builds. Only one person said that but from what everyone else is experiencing this appears to be true. You are not alone mine was bootlooping and never getting past the splash animation either.
You don't need to fix or flash a new recovery. All you have to do is use a lower build such as 203 and you'll be fine. I'm testing some roms right now and they work fine now. I did upgrade to twrp recovery as well.
I'm sorry you went through the whole boot loader process again.
At least it's a simple fix. I'd recommend monitoring the eos4 thread and see when people post about newer builds working. I'm sure 206 will fix everything.
Best of luck.
Thanks for the suggestion but unfortunately it didn't work. I did get past the M logo and the multicoloured splash screen appeared but it just got stuck there.
I tried going back to 203 and that didn't work. I also tried going way back to 155 (with the appropriate Google apps package) and that didn't work either.
I am starting to wonder if there is something about the way I am flashing these that isn't working. I have done it so many times that I am rather baffled as to what is going on this time but I think I shall try flashing using Odin and see if that gets me any further. It's all rather frustrating as I haven't been able to use my Xoom for days now.
I have now fixed this although I am not absolutely sure whether my diagnosis is correct.
By flashing Wingray 203 and a very old GApps package, I got past the splash screen. The Google setup program then crashed but at least it had booted. I then tried 203 and the second most recent GApps package (dating from January I think) and it worked.
My guess is that there is some weird interaction between the most recent versions of Wingray and the most recent GApps package (and possibly other factors) but at least my Xoom now works.