Database Develop

[Q] Think I screwed up?

Ok so I have an unlocked Nexus One that I rooted when I first got the phone 6 months ago. I've been running CM6 no problems at all, everything has been great.
Heres where my problem starts I decided to flash the stock frf91 image onto the phone and did not check superuser permissions or whatever option they gave me before i did it. I was doing this because I thought I was selling my phone. Now I'm not and want to go back to CM6.
The problem is I cant get into recovery at all I get the error with the ! in a triangle with android standing next to it. I've searched everywhere and tried everything. Fastboot and ADB gives me errors like waiting for device (even though my drivers are up to date and it recognizes the phone?) or status failed too many links.
I tried doing a backup from my nandroid information through my nandroid backups on my computer (aka pulling system.img etc) I tried going through the terminal but Im getting denied superuser permissions.
Im just not sure where to go from here ive looked through so many articles and threads and posts and im very confused.
After I flashed the stock image I thought i would still be able to boot into recovery but i guess i dont have recovery? I try to flash the recovery but with no avail.
Anyone have any advice or even just somewhere to start I would really appreciate it. Thanks

When u flashed the stock rom it wasnt a rooted version so u have the stock recovery search for how to root the stock Rom once rooted u can put a custom recovery on there hope this helps

The procedures for the different handsets kind of blur together in my memory, so just want to check.
When you booted into recovery and got the "!" screen with the android did you try holding either the volume up, or volume down key <along with the power button> to bring up the menu?

The ! With the Android is the stock recovery image if I remember correctly if u press the power button the menu should pop up

[Q] Nexus One stuck at X/ No recovery

First of all, I have checked around quite a bit on this forum as well as others to try and avoid having to ask a question that's already been answered. Here's my problem/ what happened. I was rooted (one-click with locked bootloader) and had tried out several roms for a couple of months now. A few days ago I reverted back to an old stock 2.2 backup. My phone received two ota updates and I'm pretty sure I lost root. I had just went on using the phone for about two days when I ran into a problem today. After shutting the phone off I have now become "stuck" at the initial "X" screen (not animated). I pulled the battery and tried again several times. I then tried to reboot into recovery from the bootloader/ 3 skateboards screen with no luck. Any time I hit recovery it simply takes me back to my stuck "X" screen. I have an entire backup of my SD card from earlier as well as at least 4 nandroid backups (one of which was the stock 2.2 before the latest ota). I am thinking I need to somehow put clockwork recovery back on my phone so I can restore to one of my backups. I do not know how to do this. Sorry for the lengthy post but I want to provide as much information as possible. Any help at all would be greatly appreciated.

Just like you restore to stock 2.2. You should have used recovery.img. use adb fastboot to put the stock or anom recovery. I am not am expert but I have had the same problem few times. Always use adb commands
Sent from my Nexus One using Tapatalk

Does my n1 have to be in usb debugging mode because it's acting like it's not connected or something. I get the message "error: device not found." I'm on the fastboot screen on my n1 and using terminal on a mac. I usually didn't leave debugging mode on

No it doesn't but you have to have the drivers installed as well as the SDK with dependencies.

Whew! Thank God! I ended up getting a FRG33 stock rom onto the sd card and the bootloader detected it. I'm not sure what happened but when I tried recovery after that it took me to the android with an "!" point (meaning no recovery?) and then back to the X. This time however it loaded on through and went right back to the way it was before it was stuck. Again, not sure what happened but thanks for the replies and help.

fastbook oem unlock
install Amon RA recovery
flash new rom.

Caseyp789 said:
Whew! Thank God! I ended up getting a FRG33 stock rom onto the sd card and the bootloader detected it. I'm not sure what happened but when I tried recovery after that it took me to the android with an "!" point (meaning no recovery?) and then back to the X. This time however it loaded on through and went right back to the way it was before it was stuck. Again, not sure what happened but thanks for the replies and help.
Click to expand...
Click to collapse
The exclamation mark is just the stock Android recovery - it was re-installed when you loaded the stock FRG33 ROM.
Performing OTA updates requires you to have the stock recovery installed. Simply reverting to a stock 2.2 nandroid isn't sufficient, so trying to install those OTAs (which should have failed without stock recovery) may have broken something there.
GldRush98 said:
fastbook oem unlock
install Amon RA recovery
flash new rom.
Click to expand...
Click to collapse
This is by far the easiest (and safest) way. Google/HTC provided us an easy and safe method for gaining full access to our phones.... Why so many people refuse to use it is beyond me. If you root it the proper way (with fastboot oem unlock), it will make recovery from any further issues a lot more simple.

From what I can tell, I am having the same symptoms as the topic creator. I believe the problems started during a failed flash of cyanogenmod 6, but I am not sure by what means the flashing took place.
I can't boot the phone normally, it hangs on the X splash screen and the same occurs when trying to enter recovery mode.
I have tried the passimg approach to fix this, it either doesn't recognize my zip or starts loading it and freezes on a loading bar.
Fastboot flashing recovery completes, but doesn't fix the issue.
I can fastboot flash every image partition except system or radio, both hang.
As danger rat and dude random both know, I have posted this problem on the nexus one forums but I thought I'd post here to have some more minds look at it.

[Q] Help? I think i've bricked Nexus one

Hello,
I have a nexus one that isn't working anymore. I was trying to install the cyanogenmod, but I guess I didn't do it correctly.
I was following the clockworkmod way from this: h t t p ://wiki.cyanogenmod.com/index.php?title=Nexus_One:_Full_Update_Guide
When flashing the rom something went wrong. After step 6 my phone didnt reboot, it just stayed off. Now it will only give me the nexus sign if i turn on the phone.
I can still acces the recovery menu when holding Power + volume down.
People told that I should go back to the stock rom.
Can anybody please help me?
*don't know if i've posted in the right category

When you get to recovery is it still clockwork or stock? If clockwork then try and flash cm6 again. If not you will have to download a stock rom push it to the sdcard as an update.zip and boot into the boot loader.
Sent from my Galaxy Tab, that makes phone calls

Since you can boot into recovery you have NOT bricked it for sure
As mentioned in the earlier post try to flash the CM ROM again

If you are unable to access the custom recovery (as in, the stock recovery is still in place), you can follow the manual instructions for installing ClockworkMod: http://wiki.cyanogenmod.com/index.php?title=Nexus_One:_Full_Update_Guide#Manual_Method
You can then follow the procedure for flashing the appropriate radio image: http://wiki.cyanogenmod.com/index.p...ll_Update_Guide#ClockworkMod_Recovery_process
And you can even install the ROM without using Rom Manager using this process: http://wiki.cyanogenmod.com/index.p...Update_Guide#Second_Method_.28via_Recovery.29
All of this is, as I'm sure you've noticed, posted on the same page that you linked. Hopefully this information will help you, now that you have been assured that your phone is not bricked.

Thanks for quick replies. I've contacted a guy with a lot of knowledge about these kind of thinks and helped me fixing me phone. I dont know exactly what went down but I will give it a try.
My first mistake was thinking that I rooted my phone (using the one click method). Don't know if thats the right way to do it, but in the end it wasn't rooted and I tought it was.
The guy rooted my phone, did the AmonRa recovery install and installed the Ethernom Rom for me. Great to have my phone back to working and great Rom btw.

[Q] Flashed wrong CWM before trying to flash new kernel.

I tried to flash the boot image for my first custom rom using easy kernel flasher, and my Vivid is now stuck at the white HTC screen. I then realized that I had used rom manager to flash CWM, even though I had already flashed the custom CWM from the superguide. Is this what caused my phone to hang at the HTC screen?
Is it safe to pull my battery? What is the next step, repeat step 2 from the superguide and then reflash the new kernel and rom?
I apologize if this has already been answered, I just haven't seen this exact question elsewhere and I don't want to pull my battery without being sure that I won't brick my phone or make my problem worse.

Rom manager does not work for our phones. That is why your phone is stuck. I remember another post like this. The guy pulled the battery and flashed the new cwm image without rom manager and it worked. I believe you would start at step two to correct your issue. Let us know how it goes for you.

Ok I pulled the battery and put it back in and now it won't boot at all. The power light flashes orange and then nothing happens. I'm getting a bit more worried about this now.

androuglas said:
Ok I pulled the battery and put it back in and now it won't boot at all. The power light flashes orange and then nothing happens. I'm getting a bit more worried about this now.
Click to expand...
Click to collapse
Alright, so I just did the same exact thing you did... updated CWM from ROM manager and tried to backup the ROM, hung at HTC screen. I haven't gone through the steps to reverting my CWM yet but I did get it to boot. Pull the battery, put it back, boot into HBOOT and let it do its thing, go to fastboot and then reboot. Give it a minute. Mine came back, set for a while at the boot image but it came back.
I just did the whole thing again but with out the HBOOT process and it worked too. Didn't take nearly as long as before at the boot image. Try both or see if you can't get to recovery from HBOOT. I'm pretty new to the Vivid since this is my wifes phone and its a lot different from my Inspire, the process of everything that is
Now reading your 1st post again, I didn't do the exact thing you did but close...

I tried again and it went in to h-boot, and i was able to reinstall the custom vivid CWM. But now I'm not sure if the kernel flash which started all this worked. Is there a way to find out while in recovery?
Should I reboot the phone now, or just flash the rom I was planning on flashing originally? Or should i try to return everything to stock and start all over?

cbronson41 said:
Alright, so I just did the same exact thing you did... updated CWM from ROM manager and tried to backup the ROM, hung at HTC screen. I haven't gone through the steps to reverting my CWM yet but I did get it to boot. Pull the battery, put it back, boot into HBOOT and let it do its thing, go to fastboot and then reboot. Give it a minute. Mine came back, set for a while at the boot image but it came back.
I just did the whole thing again but with out the HBOOT process and it worked too. Didn't take nearly as long as before at the boot image. Try both or see if you can't get to recovery from HBOOT. I'm pretty new to the Vivid since this is my wifes phone and its a lot different from my Inspire, the process of everything that is
Now reading your 1st post again, I didn't do the exact thing you did but close...
Click to expand...
Click to collapse
Thanks man. I got into recovery and fixed the CWM problem, but now I'm not sure what kernel I have running so I don't know if its safe to reboot.

Though I know how to use CWM I couldn't tell you how to check your kernel and whatnot from there. Best thing I can think of, or what I'd do, would be to wipe everything out and restore a nandroid, granted if you have one I've never really messed with kernels untill now so I don't even know if that would work

I realized I could just reflash the kernel while I was in recovery. It hung at the htc screen on the reboot like before, but i just pulled the battery, went back into recovery, flashed the rom, and now everything is working perfectly with the new rom. What a relief.
I think the original kernel flash may have actually worked, and I just freaked out when it hung at the htc screen and assumed it was because of the rom manager/cwm thing. It may have been fine all along.

Here is something that will help with flashing kernels.
http://forum.xda-developers.com/showthread.php?t=1423151
Flash Image GUI

ok i did the same thing awhile ago, i flashed new CWM then insatlled rom ...the Kernal did load thats the reason you got the white screen ..so just go ahead and load your rom you should be fine

How long should the 4.2.2 OTA take to flash?

Got the update through today.
Put the original recovery back in place as CM fails the install.
It's now been sat on a picture of a phone with green arrow circles above it, and a scroll bar stuck on ~30% for about an hour and a half. So I guess nothing is happening- thoughts?
*EDIT - tried turning it off. When I turned it back on, it said "Entering recovery" and is now back at the same point?

jmbillings said:
Got the update through today.
Put the original recovery back in place as CM fails the install.
It's now been sat on a picture of a phone with green arrow circles above it, and a scroll bar stuck on ~30% for about an hour and a half. So I guess nothing is happening- thoughts?
*EDIT - tried turning it off. When I turned it back on, it said "Entering recovery" and is now back at the same point?
Click to expand...
Click to collapse
Is your phone rooted and were you on a stock rom when you downloaded the update ?

maxal said:
Is your phone rooted and were you on a stock rom when you downloaded the update ?
Click to expand...
Click to collapse
I /was/ rooted, although after it rebooted the first time and tried to update in CWM that seemed to deactivate itself. Stock ROM, yes.
I have since tried wiping cache and re-flashing stock recovery once more, but now the recovery just goes to the warning triangle rather than the green arrows, so I've probably made it worse
I can still get into fastboot ok. Can I get the OTA zip and flash it through fastboot anywhere?

jmbillings said:
I /was/ rooted, although after it rebooted the first time and tried to update in CWM that seemed to deactivate itself. Stock ROM, yes.
I have since tried wiping cache and re-flashing stock recovery once more, but now the recovery just goes to the warning triangle rather than the green arrows, so I've probably made it worse
I can still get into fastboot ok. Can I get the OTA zip and flash it through fastboot anywhere?
Click to expand...
Click to collapse
I have the same problem. I tried fixing it trough flashing a firmware.zip but I think it might've been the 4.2.2 firmware zip and now my phone's proper messed up. Still boots and everything works except for camera and sd card.

markvdn said:
I have the same problem. I tried fixing it trough flashing a firmware.zip but I think it might've been the 4.2.2 firmware zip and now my phone's proper messed up. Still boots and everything works except for camera and sd card.
Click to expand...
Click to collapse
I would advice trying a factory reset if you have a backup of your data to see if that helps with the issue's.
I know there are some issue's being reported when trying to update to 4.2.2 with root

gazlufc said:
I would advice trying a factory reset if you have a backup of your data to see if that helps with the issue's.
I know there are some issue's being reported when trying to update to 4.2.2 with root
Click to expand...
Click to collapse
Hmm okay, did a factory reset through fastboot, will try the 4.2.2 OTA again.
Will report back in 5 mins.

markvdn said:
Hmm okay, did a factory reset through fastboot, will try the 4.2.2 OTA again.
Will report back in 5 mins.
Click to expand...
Click to collapse
Kewl waiting to hear if all works again

I have the same problem with mine

I may just do a full wipe and start over with a new ROM. Seems as good a time as any seeing as it's buggered! Unless anyone knows where to get the OTA from and how to flash it through fastboot

I found the OTA zip on my phone this place : /data/data/com.android.providers.downloads/cache
Impossible to flash it, it returns errors

gazlufc said:
Kewl waiting to hear if all works again
Click to expand...
Click to collapse
Doesn't seem to be working, freezes in the exact same place as before
Took a bit longer cause I had to download it over 3G instead of wifi.
---------- Post added at 05:52 PM ---------- Previous post was at 05:27 PM ----------
Can anyone provide me with the firmware.zips for 4.1? I've accidentally flashed the 4.2 ones and need to revert to 4.1 for the OTA to work.

I'm stuck too, phone was rooted previously did I didn't reroot after the last upgrade, just flashed CWM. Flashed stock recover from ARHD, accepted OTA update, now stuck on upgrade screen. Pain in the arse, really hoping to avoid starting from scratch.

dahamsta said:
I'm stuck too, phone was rooted previously did I didn't reroot after the last upgrade, just flashed CWM. Flashed stock recover from ARHD, accepted OTA update, now stuck on upgrade screen. Pain in the arse, really hoping to avoid starting from scratch.
Click to expand...
Click to collapse
I gave up. Put Revolution Stock ROM onto a 4Gb memory stick, flashed CWM, mounted external SD and installed the zip.
To be fair, HTC Backup has restored my email accounts already. Apps downloading now.

I hard-cycled and it restarted, completed, and went to black for an extended period of time. Hard-cycled again and it completed. Terrible process feedback.

I had the same problem, it was stuck around ~25% and just didn't move. I turned mine off and held the down volume button down, but that just took it back into recovery but this time it installed. Bar is just at ~90% now.
Do you have S-OFF or S-ON?
I still had root but I recovered my recovery from clockwork to original and also relocked bootloader and remove tampered message and then did S-ON before doing the OTA.
Since writing this, my install has just finished and on the reboot now.

nicelad_uk said:
I still had root but I recovered my recovery from clockwork to original and also relocked bootloader and remove tampered message and then did S-ON before doing the OTA.
Since writing this, my install has just finished and on the reboot now.
Click to expand...
Click to collapse
Hi nicelad,
Could you explain how did you get your One relocked and S-on ? Thanks

I used revone to do the relocking and then a fastboot oem writesecurelock 3 via cmd on pc to write the S-ON
Sent from my HTC One using Tapatalk 4 Beta

Thanks, i'm going to try this
Edit : Did what you said, but still can't update. The update stops at almost 20 %