So my nexus one froze today, and now whenever I pull the battery and put it back in, it will vibrate 7 times and wont boot. Is it bricked, or what can I do to fix this?
Thanks
What were u doin when this happened and what does the boot animation come up
Sent from my Nexus One using XDA App
I opened up the navigation app and it froze. Puller the battery and had that problem. I then decided to pull the battery, press the power button a few times to discharge the phone and it booted back up. So hopefully it wont happen again
Same thing happened to me. I was experimenting with an undervolted kernel which up until then had been behaving well. Received a bunch of texts and notifications simultaneously. By the time I got to my phone, it had gone to sleep. I was able to power on, but the screen was completely unresponsive. The powering on was also very delayed. I couldn't shutdown with the power button so I pulled the battery.
It could only do a 7-vibrate boot/freeze every single time I pulled the battery and replaced it. Finally, with the above advice, I left it out for several minutes, hit the power button a few times, then replaced the battery and got it to finally boot.
This happened to me today too, I took out my SD and it booted up just fine after that..not sure what happened. I checked my SD for errors but it didn't have any and had no problems after I put it back in.
hmm havent faced these errors yet, have u modded the rom at all?
mine just did it now when i changed the sd card.
taking the card out doesn't help.
i'm guessing it thinks the battery is flat or something similar, will try charging.
edit: just kept trying and it eventually worked.
I have the same problem, hitting the power button does nothing, I leave the battery out for ~ 5 minutes and eventually get a fastboot screen and 7 times vibrate, but no control, power button, volume and trackball not working. I have to pull the battery out, wait another 5 minutes or so and try again.
Does anyone have a clue about what that 7 times vibrate means? sounds like an error code.
If after have pulled out the battery for 5 minutes I keep pressed the volume down and the power, I eventually have a fastboot working screen, but choosing recovery from the menu takes me back to the fastboot screen with 7 times vibrate. Taking the card out or the sim does not make a difference.
How did I get here: Was using Cyanogen 2.2, rooted, screen froze one day, pulled the battery out and here I am.
Tried to do a reset with volume down and power, it freezed during the procedure and now it won't boot at all.
I'm still able just to start in fastboot. Recovery and clear storage do nothing useful. Booting normally gives me the nexus logo for a while and then the screen blanks after a few seconds.
I can do fastboot flash boot, but I can't do fastboot flash system, it just says sending and that's it:
Code:
[[email protected] apps]# ./fastboot erase userdata
erasing 'userdata'... FAILED (remote: not allowed)
[[email protected] apps]# ./fastboot erase cache
erasing 'cache'... OKAY
[[email protected] apps]# ./fastboot flash boot Passion\ Google\ WWE\ 1.01.1700.1_ERD79/boot.img
sending 'boot' (2044 KB)... OKAY
writing 'boot'... OKAY
[[email protected] apps]# ./fastboot flash system Passion\ Google\ WWE\ 1.01.1700.1_ERD79/system.img
sending 'system' (116663 KB)...
Any ideas anyone ?
alexxed said:
I'm still able just to start in fastboot. Recovery and clear storage do nothing useful. Booting normally gives me the nexus logo for a while and then the screen blanks after a few seconds.
I can do fastboot flash boot, but I can't do fastboot flash system, it just says sending and that's it:
Code:
[[email protected] apps]# ./fastboot erase userdata
erasing 'userdata'... FAILED (remote: not allowed)
[[email protected] apps]# ./fastboot erase cache
erasing 'cache'... OKAY
[[email protected] apps]# ./fastboot flash boot Passion\ Google\ WWE\ 1.01.1700.1_ERD79/boot.img
sending 'boot' (2044 KB)... OKAY
writing 'boot'... OKAY
[[email protected] apps]# ./fastboot flash system Passion\ Google\ WWE\ 1.01.1700.1_ERD79/system.img
sending 'system' (116663 KB)...
Any ideas anyone ?
Click to expand...
Click to collapse
Since you said you were using CyanogenMod, I will assume you are using CM6 RC2 not that it matters now. So you are running a custom recovery right? Try to wipe everything, data, cache, and the dalvik cache. Then flash a different ROM, either stock or any other really to see if that helps.
edited.
sent back to HTC
There are a batch of n1 that has this problem. I had bought a new att 3g version in june and returned it for a new. I also had the booting problem. It would constantly reboot or be stuck at the nexus boot logo. Its a hardware issue. Call google and they will transfer you to htc and work out a exchange or repair for you.
Sent from my GT-I9000 using XDA App
Vakman said:
Since you said you were using CyanogenMod, I will assume you are using CM6 RC2 not that it matters now. So you are running a custom recovery right? Try to wipe everything, data, cache, and the dalvik cache. Then flash a different ROM, either stock or any other really to see if that helps.
Click to expand...
Click to collapse
I'm trying to flash the stock image following the instructions here: #614850
Flashing hangs in various steps of flashing system.img, so I tried repeatedly until I succeeded, but still no success in booting afterwards, so I suspect I need to match the radio with the system as I've read that the radio boots before system. Right now I have FRF50 (4.06.00.12_7).
The problem is that once I leave the phone off for a while with battery in, the phone does not start in any mode (power, power + volume down, power + trackball) until I leave it with battery out for 2-3 days after which I can boot in any of the three modes above, the power button shows the nexus logo for a few seconds than the image scrambles and the phone goes off. If I choose to go in recovery I see the nexus logo forever.
Fastboot works, but as said, it hangs when flashing about 90% of the time.
I'll keep trying as sending off the phone for repair is a tricky option considering that I'm not in US, I haven't bought the phone from US, and so on.
Ive had this problem for awhile. It first started when i updated to froyo. I called htc Tech support an they told me it was probably caused by an app but i dont know if thats true or not. Iam curious to know what the 7 vibrations mean
In case you can't/don't want to send it back for warranty repair, it seems that leaving the phone charging for 12-24 fixes the issue (though it might look dead during those hours).
maxdadev said:
In case you can't/don't want to send it back for warranty repair, it seems that leaving the phone charging for 12-24 fixes the issue (though it might look dead during those hours).
Click to expand...
Click to collapse
Tried that and almost anything I could have imagine. Finally I sent the phone to HTC and they were kind enough to repair it free of charge, I only paid for the shipping to them, they paid the shipping back.
The interesting part is that I got the same phone (it has the same IMEI), but locked again, so I guess that means there is a way to lock the phone back.
I hate to revive an old thread, but it's probably better than making a new one about the same issue.
A friend of mine said this happened on his Nexus and now it won't boot past the "X" splash screen, and it vibrates 7 times. He gave it to me to try to fix, and I've done everything I can think of. When I try to use a PASSIMG.zip through Hboot the progress bar on the side fills, then it says "Checking PASSIMG.zip," but then it just returns to the Hboot screen.
I've tried using Fastboot to install Amon_Ra's recovery and Clockworkmod recovery, even a radio update, but any .img file I try tells me "FAILED (remote: signature verify fail)"
Has anyone found a fix for this, or have any suggestions?
If I have to call Google/htc can I still have it replaced, even if the bootloader has been unlocked, voiding the warranty?
Thanks.
You have to unlock the bootloader to use fastboot.
I have unlocked the bootloader. It says ***Unlocked*** at the top, it's still S-ON though.
I can't access recovery or ADB to tell if it's rooted or not, either.
*** UNLOCKED ***
NEXUSONE PVT SHIP S-ON
HBOOT-0.33.0012
MICROP-0b15
RADIO-4.06.00.12_7
OK, that's weird then. I've never heard of fastboot failing before.
Hi Folks,
I had a CyanogenMod-6.1 for Nexus One :: V6.1.0-RC1 (10/28/2010) installed on my Nexus 1.
Prior to that i was using CM6.0 RC1 stable release. Did an upgrade (with full void and nandroid backup) to try out the new features.
However this afternoon, out of nowhere, my volume buttons and trackball started to malfunction.
i.e to say : I cannot adjust volumes in any part of the apps/phone and i can't select/click stuffs with the Trackball.
Hence, I thought of removing CM6.1. Here's the problem started.
#1. I can't boot into recovery. The phone itself will be stuck at the big "X" screen. After 5mins, it will boot into CM6.1
- Using ROM Manager i tried to reflash Clockwork Mod 2.5.1.0 for a couple of times but i still cannot get into Recovery.
Be it powering up with trackball held down, booting into recovery up via Rom Manager. Surprisingly, volume down was working together with power down was able to go into Bootloader
for me to select "Recovery", however, i still can't access Recovery.
#2. I tried using ./fastboot-mac flash recovery updatedclockwork.img also can't.
#3. I tried using Amon-RA. ./fastboot-mac flash recovery Amon-RA.img also to no avail.
#4. i used ./fastboot-mac update to load a StockFRF91 Froyo also can't get into recovery.
As of now, my phone is stuck continuously in bootloop, cannot access Recovery. I've tried almost 30+ fixes on XDA and other Android Forums but i still can't fix it.
Is there anyway, i can wipe everything inclusive of the "Corrupted Recovery" files and restore back my Nexus One?
Thank you all please save my phone! :'(
Dude I feel your pain. I have the exact same problem. I wonder if it is a CM6 issue?
Hi guys...
First off, i'm somewhat of a noob. Got my N1 already rooted a few months back but i've tried many different ROM's since. I'm using Clockworkmod Recovery.
I was running Cyanogen 6.1 yesterday and wanted to create a backup of stock froyo for gingerbread's release.
So, i did a backup of Cyan 6.1 and followed the following steps off Android Central's forum.
Step One
Download this file. It's the flashable, stand alone version of FRG33.
You can't go straight back to FRG83 using this method. Just trust us.
Place the PASSIMG.zip file on the root of your SD card.
Power off your Nexus One, then hold volume down while pressing the power button.
Your phone will spend a minute or so looking for an update file (the PASSIMG.zip file).
When it has the info it needs, it will ask if you would like to install it. Press the volume up key to choose to install the file.
Your Nexus One will take another few minutes installing the update, then it will reboot.
Let it reboot the whole way, then go on to step two.
Step two is for the update to FRG83 which i did.
The phone boots and runs fine...
But ever since I did all that, my N1 looks like its unrooted. I can't use ROM manager, Titanium backup to restore since they all tell me they don't have su rights. I installed Superuser from the market. It opens but does nothing with my app's rights.
adb can't find my device when I try to list it (adb devices). Neither can Fastboot (fastboot devices), in fastboot mode.
I see the padlock at boot
I can't go into recovery. I get the robot with an exclamation mark. If i hit the power and vol-up I get the android system recovery menu (in blue) with only 4 options; reboot, apply sdcard:update.zip, wipe data/factory reset and wipe cache partition.
I've tried rooting it with Universal Androot but it failed.
I've no idea where to go from there...
Please help!
You have to root again. Use the rageagainstthecage exploit.
Sent from my Nexus One using XDA App
Ok... N1 is rooted using VISIONary.
However, I can't boot into recovery mode (clockworkmod). I still get the exclamation mark.
If I try to use adb, i always get an error: device not found.
If I try to unlock with fastboot oem unlock, i get a waiting for device message but it never finds anything....
Almost there... i think!
Ok... using Clockworkmod, flashed recovery and all is good!
Thanks for your help!
I have a rooted HTC Hero (Sprint) and during preparations for upgrading to CM7 I ran into issues with ROM Manager.
First, I backed up everything (apps and data) via two different methods. I cleared davlik cache, and then performed a CWM Flash Recovery backup. Once that completed successfully, I sought out to apply the CM7 ROM. I selected it from the GUI menu, rather than rebooting into the Flash Recovery. I selected to backup everything and then wipe the data/cache. During the process, the phone hung (white HTC screen for over 10 minutes). I could reboot successfully after this, and selecting "Recovery" didn't work either. I figured my phone was bricked. But miraculously, it managed to finally recover.
The recovered ROM was a fresh clean slate. So, I installed ROM Manager and Titanium backup again. However, when I tried to reboot to the CWM Flash Recovery, or even try entering the CWM CUI menu from power up (by holding the HOME key), the phone hangs. Something is seriously screwed up with ROM Manager. I'd like to wipe it completely clean and start over, but everything I've tried results in a phone that hangs. I'm now thinking I should use a different program for managing the ROMs... but, being familiar with ROM Manager and seeing other people use it successfully, I feel determined to make it work. Any suggestions?
I would just flash an RUU and start from scratch.
https://docs.google.com/file/d/0B9lyYjZr_O3gZnJrRVFqRmh4eVU/edit
I was able to recover.
What I didn't realize is that the first boot can take upwards of 20-30 minutes. I pulled the battery after around 15 minutes, thinking my phone had hung.
Anyway, when I selected "Recovery" again I left the phone alone and eventually I got a stock ROM again. Whew!
While ClockworkMod is fine for 2.1, when you're on 2.3 there's no question that TWRP is the way to go. I've flashed it to my phone (did "flash_image recovery [recoveryfilename.img]") from the terminal window and it's working great, far more extensive than ClockworkMod.
I was following instructions on rootjunky.com for unlocking and rooting. I successfully unlocked bootloader with sunshine app. Then I flashed TWRP and got it running. But TWRP didn't have the swipe to allow changes to system partition on startup, so I thought I needed to flash system image per the rootjunky video. I figured it couldn't hurt even if it wasn't needed. so I flashed the 10 parts of system image per video and then tried to get to recovery but just saw little dead android flash on screen every few seconds. I have tried holding all combinations of buttons but after unlocked bootloader warning comes up I get lying down android that says "No command" that flashes briefly every few seconds. Am I totally screwed?
All the messages in the command prompt window while flashing all 10 of the system chunks looked nominal ("sending system ... OK ... writing system ... OK", and my batch file looked just like the one in the video.
Any help is appreciated.
Wait. I gave up too soon. Looks like I can get back to fastboot. Somehow TWRP got messed up. I just reflashed TWRP. Whew! Looks like system flash was bad. I'll try flashing system again.
No joy. I have TWRP now, but still can't get system running. When I try to reboot to system from TWRP it comes back to TWRP. I had verified md5sum of system before flashing, so I know that file downloaded ok. Also, adb doesn't see phone when in recovery. I'll keep trying stuff.
Update: I double checked the mda5sum on the system image zip and it was (still) good. Then I re-extracted the ten image chuncks and re-flashed. Now I can boot to system from bootloader and all is as it was before this misadventure. Almost. If I power down phone and then power up I get the dead android with the "No command" message. It just comes on and stays on rather than flashing, so that's an improvement. From there I can get back to the bootloader and then select "Start" to boot up the phone. I can live with that, but it's an annoyance. If anyone has any suggestions to how to make it boot up by itself from power on I'd love to hear them.
Reflash your phone with Verizon Software Update http://www.verizonwireless.com/support/knowledge-base-116673/ and then flash TWRP (fastboot flash recovery twrp.img)
It does't affect your unlocked bootloader.
Thanks, Aptahar, but I have a new theory. I started a new thread here http://forum.xda-developers.com/droid-turbo/help/device-encryption-question-issue-t3283333.