Hi,
My Nexus One has been a pain in the *** the last few months. Flashing roms/recovery gives a lot of issues.
Currently, i have clockwork recovery 2.5.0.1 installed and Cyanogen 6.0 RC2. When I rebooted today, it got stuck in a bootloop and i cannot get it out of it. It boots with the static Nexus X, followed by the animated 4-colour X and then one loop in the cyanogenmod blue colour. Then it loops back to the 4-colour X, the blue X, and it stays in that loop.
What have I tried:
I have already tried to wipe & reflash my phone a few times but am unable to get it out of the bootloop.
fastboot erase recovery returns: erasing recovery''... FAILED (remote: not allowed)
I think my phone was rooted using superboot, maybe that is part of the issue?
Wrong section. This has nothing to do with development.
even i m facing the same problem on my nexus but i installed enom 2.11.1 its kind of working properly but when i reboot i can see those static Nexus X boot loops so try flasing enom 2.11.1.
This happened to me with cyanogen rc 2... I use amon ra recovery and wiped dalvik cache and it fixed the boot loop of death. I went back to rc 1 when this kept happening. Been fine since. There's a reason they are rcs and not final releases. I'm not sure what options your recovery has, but look into wiping dalvik cache and see what you can do.
I had the same issue a little while after updating to RC2 (from one of the nightlies after RC1 mind you)... at first everything seemed fine, then one night the phone just stopped responding, and a reboot got it stuck in the loop.
I ended up recovering an older version from a nandroid-backup, stuff wasnt working correctly, so i wiped everything and flashed RC2 completely clean, restoring with titanium-backup. been pretty much perfect since!
Okay I just got my n1 couple days ago. After days of play i was ready for CM6. I booted, rooted, nand back up with RA recovery. Afterwards, flash the radio and then flashed the rom. Once it booted, it kept getting stuck in the boot loop.
Now you mentioned you went back to RC1. Is there no fix to the boot loop? Another try on installing might fix the problem? IDK. It took me an hour to get it done. Now it will take another 10 min to flash again. I'll try tomorrow. Done for the day.
Hehe I got it to work. I think my copy of the rom was bad. Make sure to wipe before install. Very important. I think. Oh I download the rom directly to the SD card and installed. Just wanted to let u know how I got to work.
Sent from my Nexus One using XDA App
Related
Hey guys i don't know if anyone of you had the same issue but any info/help could be helpful.
I used to flash my N1 A LOT! but today i have this strange issue. I wiped and flashed rodriguezstyle again for a clean start, but i only got the colorful X with the unlocked symbol at the bottom and then just a black screen. i thought I've done something wrong and flashed again, but with the same results.
i changed my sd and downloaded again the rom but still no luck, did a nandroid restore and the phone was working properly. then i got a bit frustrated. downloaded 2-3 more roms but the result was the same.
i read somewhere that flashing with battery <50% may cause some errors so left the phone off to fully charge and tried again... no luck
then i remembered i upgraded the radio and i downgraded it to the old one, but still the same results and nandroid doesn't work... jeeeesh... back to the new radio and to my nandroid, but its no fun owning a smart-phone if you cannot flash it.
anyone with the same issue or any helpful tips/instructions?
Try this:
When the phone hangs at boot, reboot to recovery, wipe cache and dalvik-cache and reboot from recovery. Does that work?
If not, you'll need to logcat the boot process and post the log somewhere for us to have a look at.
So, assuming adb is working on your computer, plug in via usb, use adb logcat > output.log and reboot the phone. Continue logging for about 60 seconds after the phone stops.
Post the log to www.pastebin.com and then link back here.
hmmmm ok i will post results in abt an hour. thanx!
hmmmm i think i sorted it out... reflashed recovery. propably i messed smthing in there! thanx for your effort!
Hello everyone!
Weird problem here, too.
I was backing up my SD card in view of a format/cleanup....and when I went to boot into recovery, my N1 was stuck on the black screen with the white letters at the bottom "Build : RA-nexus-v1.7.0.1"... The phone actually boots great, it is just not loading the recovery image. Is it possible that part of the flash got corrupted? If so, I'm pretty much done flashing my N1, right???
I'll post a log asap (if it could help any)...
Oh and btw i tried to re-flash Amon-RA's recovery twice already...Superboot said it was successful....but I doubt it...
Well try flashing stock rom! I flashed it through fastboot step by step and it worked. Also check if the rom you try to flash needs ext partition or if apps2sd is enabled
Sent from my Nexus One
Test
Sent from my Nexus One using XDA App
Thanks nica.
I had to flash stock boot and rom to fix it...
Sent from my Nexus One using XDA App
I have a HTC Hero, today I tried to update my cyanogen mod 7 to 7.0.3 however when I did, I did all the proper steps to update the Rom properly however it did not work. So I tried a fresh install, and even tried a few new Roms still nothing worked. Recoveries work fine. When I restart my phone it hangs at the HTC screen then restarts and it will do this so far for up to 15 mins. someones gotta have an idea on whats going on. btw phone is rooted and running clockwork.
goshxjosh said:
I have a HTC Hero, today I tried to update my cyanogen mod 7 to 7.0.3 however when I did, I did all the proper steps to update the Rom properly however it did not work. So I tried a fresh install, and even tried a few new Roms still nothing worked. Recoveries work fine. When I restart my phone it hangs at the HTC screen then restarts and it will do this so far for up to 15 mins. someones gotta have an idea on whats going on. btw phone is rooted and running clockwork.
Click to expand...
Click to collapse
What version of cwm? Try flashing a different recovery version (maybe 2.7.0.5)
Make sure you factory wipe as well as format, system, data, cache.
Bad download maybe?
®patience is a virtue©
is your battery charged well above 30%?
Sent from my HERO200 using XDA App
Guys i had this problem when i flashed my first ROM too ...(alas)
Buy my problem was a simple fix ,
: restart in recovery
: wipe all data
: restart and Enjoy
i have the most recent cwr and i wiped my data and everything. i have been flashing for more that a year now this is the first time ive had this issue. im gonna unroot and reroot the phone.
If you haven't unrooted yet try just reflashing your current recovery.
#Root/Hack-Mod_Always*
This has happened to me with different builds ( of all of the different gingerbread roms) since the switch from 2.3.2 to 2.3.3 and .4.
When this happens, I will either try a different Rom, or use something called Fix Flash that is in the development section for the CDMA Hero. My phone currently is liking the Jaybob build. Also, as silly as this might sound, but formatting the partitions 3x can actually help too ( boot, system, data, and cache).good luck, I've been there.
Sent from my HERO200 using XDA App
Can't get past the HTC screen...
I got a new HERO200 as a replacement for a damaged one and am able to root it with confirmed SU permissions. I have tried clockwork 2.5.0.7 and RA 1.6.2 for the heroc. I tried flashing Cyanogenmod 7 (7.0.2 / 7.0.3 / 7.1.0 / and even a 6), AOSP and it keeps hanging at the HTC screen when I reboot the device out of recovery. The first reboot after flashing a ROM will briefly display the HTC screen and then go black. I have to remove the battery to reset the phone. When I power it up again, it will display the HTC screen and just hang, even after multiple restarts via a battery removal. I have wiped all the data/cache/etc. multiple times as from a previous post in this thread, but without luck. I'm getting very frustrated to say the least and any help would be GREATLY appreciated.
never had a rom not booting, but i haven't tried them all,
try the older version again see if it works
I just run the nightlies and skipped the rc and haven't experience such things. could be something to do with the signing?
Sent from my HERO200 using XDA App
I was running nightly 206 and a gapps pack from 03072011 rooted to the nook. Has worked wonderfully for about 2 weeks. I plugged in the nook to the wall charger last night like i do every night. When i opened the cover of the case this morning, i noticed it was on the arrow/circle booting screen, which was odd. I guess it had been doing this all night since the unit was warm around the charging plug. I rebooted and now it is stuck in a boot loop on the arrow/circle CM7 screen. i inserted my boot card and ran clockwork and tried updating cm7 to the newest nightly, 213, but it is still having the same problem. I can't get past the boot loop no matter what i do. i dont want to completely reflash if i can help it because i dont want to lose all my apps and data.
i read a thread about this problem occurring after updating flash through the market. i did update flash yesterday, so its possible this caused the problem. i tried the fix i read, flashing an adobeflash_fix.zip in CWm but this did not fix the problem.....thanks,
No, Flash will not do this. Did you wipe Davlik when you tried the update? You could also boot from a SD card with a newer nightly and just flash that with gaaps and only wipe cache and Davlik.
Hi... I fixed a few bootloops by removing the Flash and AIR apks using CWR and ADB
I've tried repeatedly to install CM7.2 and keep getting stuck on a blank screen. I'll see a "CyanogenMod" then "loading..." right below that. Then it goes blank and nothing ever happens after that.
Some background info. I've had CM7 installed on this in the past without problems. Months ago I went back to a rooted stock. Then yesterday I decided to try CM9 alpha. That installed perfectly. But it was too slow, so I decided to try CM7.2.
I used the same CWM 1GB boot SD, copied "encore_CM72-MiRaGe-02012012.zip" along with the Gingerbread Gapps and CWM. Installed in the same order and wipe data/factory reset.
So I got stuck on that blank screen after the CyanogenMod loading... message. I then decided restore to stock. Installed the 1.01 stock image. It also wouldn't boot up, but I powered it on and off 8 times and it did a factory reinstall and then it booted up normally.
Once back at a factory fresh system. I powered it off and tried installing CM7.2 again. Unfortunately I'm having the same problem again. Ugh, why won't it load now.
Hang on... I might be in the process of making a newb mistake. MD5 didn't match on my SD card, probably the ROM.ZIP is corrupted. Trying again with a good copy.
That was it. It's working now. Please disregard my idiot on the Internet moment. Thank you.
You always figure it out five minutes after you finally give up and post for help/venting.
Been there.
Hi,
So i was running MeDroid v.7.1-C.M7.2 and i was planning on flashing ICS 4.0.4 BCM RC3.3U1 Passion <2012-04-20> (Bravo CM9 HWA) which needs Blackrose and so i installed blackrose and repartitioned my system to 210mb and cache 10mb and it went well. Phone also reboot the first time than i just reboot it again just to be safe and now i am getting bootloops, any idea whats causing that?
Thanks again..
Try wiping everything 3 or 5 times and then flash
Sent from my HTC Nexus One
AttentionIf you phone boots fine the first time after flashing the ROM, but get stuck on boot after a reboot. Remove battery or press "Vol-down+trackpad+power" and hard-reboot the phone. After that it should work just fine
joelshawdow said:
Try wiping everything 3 or 5 times and then flash
Sent from my HTC Nexus One
AttentionIf you phone boots fine the first time after flashing the ROM, but get stuck on boot after a reboot. Remove battery or press "Vol-down+trackpad+power" and hard-reboot the phone. After that it should work just fine
Click to expand...
Click to collapse
Will try that, thanks
Hello,
I'm new here and I had the same problem.
I did what you said and now it's working fine.
Thanks a lot,
willys343