[Q] recovery - Nexus One Q&A, Help & Troubleshooting

ok so just recieved a new nexus and am trying to install cyanogen 6. was able to unlock phone and use superboot to root. problem i'm having now is that phone will not accept recoveries. tried installing amon ras latest 1.7 and got a cannot install message on my cmd prompt on my computer. went the clockwork mod way and flashed the clockwork mod recovery, but when i try to boot into recovery the phone goes to the screen with the nexus X and unlocked lock symbol for a few seconds and then the phone shuts off completely. the only way to restart it is to remove and reinstall the battery, also tried flashing amon ra thru clockwork mod and tried amon ras version 1.8.0.1 and getting the same results. my fastboot screen says the following
unlocked
nexusone pvt ship s-on
h-boot-0.35.0017
microp-0c15
touch panel-synt0103
radio-5.08.00.04
my build number is frg33 running stock 2.2
any ideas?

caseuno said:
ok so just recieved a new nexus and am trying to install cyanogen 6. was able to unlock phone and use superboot to root. problem i'm having now is that phone will not accept recoveries. tried installing amon ras latest 1.7 and got a cannot install message on my cmd prompt on my computer. went the clockwork mod way and flashed the clockwork mod recovery, but when i try to boot into recovery the phone goes to the screen with the nexus X and unlocked lock symbol for a few seconds and then the phone shuts off completely. the only way to restart it is to remove and reinstall the battery, also tried flashing amon ra thru clockwork mod and tried amon ras version 1.8.0.1 and getting the same results. my fastboot screen says the following
unlocked
nexusone pvt ship s-on
h-boot-0.35.0017
microp-0c15
touch panel-synt0103
radio-5.08.00.04
my build number is frg33 running stock 2.2
any ideas?
Click to expand...
Click to collapse
If your device is new (it looks pretty new considering what it came with stock) it might be an SLCD screen. This would explain why clockwork is not showing up. Until clockwork is updated to be compatible with SLCD then it might not work for you.
Try flashing the recovery image yourself and see what happens. Put amon_ra 1.8.0.1 or PSFreedom 1.1.1 image on your SD card in the root directory and not in a folder using the method of your choice (USB-MS, ADB, FTP, w/e...). You can have the file renamed to whatever you like as a shorter name might be easier to type. Be sure you have checked the MD5 sum after you DLed the file.
On your N1 open the terminal emulator (assuming you have this since you rooted). If you don't have a terminal then get it from the market. Once in the terminal type the following commands:
Code:
su
flash_image recovery /sdcard/<recovery image file name>
--EXAMPLE: /sdcard/recovery-PSFreedom-N1-v1.1.1.img
These commands ARE case sensitive. If you do not type the filename exactly as it is then the command will not work. See if that works for flashing your recovery image. Once you are done with that if it shows it is successful then reboot to recovery and see if you can go from there.

put the amon ra recovery on sdcard root, verified it was there with astro file manager used terminal emulator,
su
# flash_image recovery /sdcard/recovery-RA-nexus-v1.8.0.1-aw.img
flash_image: not found
so lost..............?????

+1 image not found

Read Nexus One Wiki, Recovery, Amon_Ra's Recovery, using flash_image method.
Generally, read Wiki before asking questions.

Related

Trouble flashing any update.zip

I'm sorry if this is posted anywhere, but I spent a couple hours last night and another couple hours today searching here and in Google with no luck.
-Skip me for TL;DR-
I got a G1 when they first came out, and rooted it as soon as I could. I ran JF1.5 then JF1.6 then after a while upgraded to Cyanogen. It was great and my GF still uses it and loves it. I got a Nexus One about a month after they came out and I've been in love. I haven't went to Cyanogen since, only because the stock rom has been great and I haven't needed any extra features yet.
Now that 720p is available along with a few other things I'd like, I want to upgrade finally.
-TL;DR end-
Basically I'm trying to say I'm not an idiot or very new to loading roms and toying with an Android device.
From past experiences I basically know the process of root/recovery/rom etc.
I loaded froyo onto the phone when it was available via the stock recovery console and an update.zip ... no problems.
Yesterday, I unlocked the bootloader.
Installed Modaco's superboot.
And used fastboot to push recovery-RA-nexus-v1.7.0.1-cyan.img
After that I turned the phone on, and logged in to check it out and make sure I had root. Everything was running great (Froyo saves your app installs in the cloud!!!) and I did, in fact, have root. All seemed well.
-The Problem-
Now, I can't load any more update.zip files. Nothing at all. Stock rom, modded rom, rom updates, anything. When I try to install any update.zip I get the following output:
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
At the top of the recovery screen it reads: Android system recovery <3e>
If that makes any difference....
NOTE: I can still use fastboot to push new recovery images, which I've tried.
System information below:
Fastboot/Bootloader Screen:
NEXUSONE PVT SHIP S-ON
HBOOT-0.33.0012
MICROP0b15
TOUCH PANEL-SYNT0103
RADIO-4.06.00.12_7
Dec 17 2009, 13:05:23
ABOUT PHONE
Model number: Nexus One
Android version: 2.2
Baseband version: 32.36.00.28U_4.06.00.12_7
Kernel version: 2.6.32.9-27220-g328f560 [email protected] #1
Build number FRF50
Thanks in advance for any help/info!!
Looks like you still have the stock recovery image... do you have backup & restore options iin recovery mode, if not, you still have the stock recovery, reflash Amon-RAs recovery...
No, I don't have backup or restore in the options, neither in recovery or fastboot.
This doesn't make much sense. Here's what I'm doing. It looks like it should be working fine:
Code:
C:\Users\Chris\Desktop\meh\android-sdk-windows\tools>fastboot devices
HT9CWP806497 fastboot
C:\Users\Chris\Desktop\meh\android-sdk-windows\tools>fastboot.exe flash recovery
recovery-RA-nexus-v1.7.0.1.img
sending 'recovery' (3948 KB)... OKAY [ 0.582s]
writing 'recovery'... OKAY [ 1.439s]
finished. total time: 2.021s
Edit:
I was thinking maybe I need a different radio image, but then I remembered reading that Froyo came with a new radio image (right?). And I couldn't install a new radio image anyway because the update.zip files won't load. I'm pretty stumped here....
Edit again:
The code above was what I just did to flash the new recovery, and I still don't have the options to backup and restore the data.
Another edit!: I also loaded Modaco's superboot again (successfully) and started the process over again with no luck.
You don't have a backup/restore option with AmonRa's 1.7.0? That means you don't actually have the custom recovery. Your fastboot is lying to you.
In the terminal app,type "reboot recovery". What happens?
And,try dropping the ".exe" from fastboot.
what they said. Sounds like you still have the stock recovery image. Try reflashing the recovery again.
I tried both the regular RA recovery and RA Cyanogen recovery using both commands, fastboot and fastboot.exe but I continue to get the same recovery image.
I know there's no way to relock the bootloader, but is there any way to reverse what Modaco's superboot did and try that again?
Go here. Scroll to the bottom of the first post. Looks at the screenshots. Does your recovery look like that?
Nope, it's the stock recovery image with the exclamation point and Andy in the background. 4 options: reply, update.zip, factory reset, and wipe cache
Flawd said:
Nope, it's the stock recovery image with the exclamation point and Andy in the background. 4 options: reply, update.zip, factory reset, and wipe cache
Click to expand...
Click to collapse
Try using amon ra recovery image stock for n1, not the cyanogen version.
This one:
http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-nexus-v1.7.0.1.img
and rename it to recovery.img or something short then try the fastboot flash recovery recovery.img
Flawd said:
Nope, it's the stock recovery image with the exclamation point and Andy in the background. 4 options: reply, update.zip, factory reset, and wipe cache
Click to expand...
Click to collapse
Confirm you have root. Go to the terminal app and type "su". What does it say?
Well root isn't necessary to flash a recovery. He just needs an unlocked bootloader.
Well, OP, you might as well just find a different computer and try it on that.
FaJu said:
Well root isn't necessary to flash a recovery. He just needs an unlocked bootloader.
Well, OP, you might as well just find a different computer and try it on that.
Click to expand...
Click to collapse
OP said he unlocked the bootloader.... so OP verify that when you TURN ON your Nexus One, the logo with the X there is a PADLOCK on the bottom of the screen. If it does, then your bootloader is unlocked and you need to install amon ra recovery.
If no padlock, you're not unlocked.
OP make life easy. Go to Market. Install ROM manager. Either install clockwork recovery, or scroll down. Select the option to flash another recovery. Flash. Done

[Help] Won't Boot To Recovery

I am running ClockworkMod Recovery, and when I updated to version 2.0.1.0 through Koush's ClockworkMod Rom Manager, my phone won't boot into recovery.
When I plug it in to my computer to run adb logcat, it says "FASTBOOT USB" in red at the top of the screen. When I type fastboot reboot, it says "rebooting..." but doesn't reboot. Any ideas?
IDK. Haven't tried that recovery. Have you tried to download from your computer and flash it on the phone. You might also want to try flashing Amon RA or Godspeed.
I went into ROM Manager and flashed an old version of ClockworkMod. That fixed it.
Have you tried Amon-RA? If so what's the difference?
&RoidRage said:
Have you tried Amon-RA? If so what's the difference?
Click to expand...
Click to collapse
ClockworkMod has a nice app that you use in Android to name your backups, flash things in folders other than root of sd, ecetera.

(Q) Recovery - Not booting into

Hi XDA, as title says, i cant get boot into recovery...
I have an HTC Dream (Spanish version of G1), and Im having problems with the recovery boot.
I have root done on the phone and i've tried to install a new recovery via Clockwork app, adb shell, also via Fastboot and via "RECOVERY FLASHER"...
All of them look to finish succesfully, but I still cant boot onto recovery.
Every time I try to boot on recovery, the phone gets hang on the company logo... until I get out the battery to turn it off.
I dont know what can I try more...
Any idea ?
Thanks
If you cannot boot into recovery by holding down Home and Power, then you're bricked, I believe. What were you trying to do?
Sent from my HTC Dream using XDA App
I can boot normally, and I run apps that need root correctly, but I want to boot into recovery to flash a custom ROM...
Clockwork mod needs to reboot into recovery to reflash a Custom ROM, so I cant get another rom that way neither.
Any idea (again)?
Do you have terminal on your phone? Download amon RA recovery 1.7.0 for HTC Dream and use that instead Clockwork because it is most recommended. Rename it to recovery.img and move it to the root of your SD card.
Go to terminal on your phone and type:
cd sdcard
flash_image recovery recovery.img
Now try to boot into recovery mode.
Sent from my HTC Dream using XDA App
If you have root access, then you can try to (re-)install your recovery image using adb.
Open a shell using the command
adb shell
and then from there you can try to flash the recovery image by entering
flash_image recovery recovery.img
where recovery.img is the name of the recovery image you want to install and it should be located in the current directory.
Edit: two people same ideas ... ;-)
Both things re-done...
Nuthin'
Anything else ?
Thanks for the answers anyway
Bump...
Any help ?
Fastboot is working for me, but I have the default SPL and I cant use "fastboot flash new_recovery.img" ---> Not allowed.
Theres a way to flash another SPL using phone terminal, or using fastboot ?
Thanks
I'm not sure, but if I was in the same boots as you, I would download the DREAIMG.nhb and flash that in fastboot. Once done, you'll be on Stock RC29. Yep, you're going to have to root again and re-install a custom recovery.
This is also safe to do since you're on HBOOT-0.95.000.
Sent from my T-Mobile myTouch 3G using XDA App
removed ...
Thanks for everything guys...
But now im looking for a "Howto unbrick G1"...
I dont have fastboot, recovery boot or normal boot...

[RECOVERY] Amon Ra 1.7.0.1 (unofficial)

Following the ethos of "because I can" I decided to port Amon_Ra to the Legend. Well, "port" might be a bit strong. I used the android kitchen to pull apart Amon Ra for the HTC Hero and ClockworkMOD for the Legend, then copied the relevant files from Ra to CWM and merged them. On that note, ROM Manager probably won't work with Ra. (What I think it will do is fakeflash CWM over Ra, so if you reboot to recovery using ROM Manager you'll get CWM, and if you reboot to recovery using the extended power menu in CM you'll get Ra)
Everything seems to work OK, but don't count on it. Like I said, this was done because I can and for a laugh. Backup with CWM before you try and be sure to have a copy of CWM to hand if you want to go back.
You NEED S-OFF to use this (Alpharev HBOOT) as it's flashed using fastboot. So, enjoy!
To flash:
1. Turn your phone off
2. Turn it on with the back button held down
3. Plug your phone into your PC
4. flash using fastboot
Code:
fasboot flash recovery Amon_Ra-1.7.0.1.img
DOWNLOAD: http://www.mediafire.com/file/j0o63jc4kua1a6x/Amon_Ra-1.7.0.1.img
Amon_Ra is actually pretty cool, there's a lot of stuff you can do via ADB (plug the phone in, type adb shell [enter] then utility [enter]). Main problem: the zips you flash NEED to be signed for Amon_Ra to flash them.
Other recoveries
To aid in recovering your recovery maybe, who knows?
CWM 5.X.X.X: http://forum.xda-developers.com/showthread.php?t=1244371
CWM 2.5.0.1: http://www.mediafire.com/file/l3c3kacbp8w0phm/CWM-2.5.0.1.img
CWM 3.X.X.X: http://forum.xda-developers.com/showthread.php?t=893248
Someone's been busy.

stuck in s-on rooted no recovery hell

So starting with a functioning CM7 and CWMR v2ish...
I started this whole adventure trying to flash a new recovery via adb and got a "mtd: not writing bad block at 0x001c0000 (ret 1 errno 2)" error and have ever since been unable to boot into recovery.
I'd like to wipe everything and start from scratch but I'm having some problems: cannot flash really anything without errors and cannot get into recovery. Installing recovery through rom manager pulls errors. Cannot flash HERCIMG.zip without error. and I'm stuck with s-on. but no recovery leaves me at a loss for getting s-off... the phone boots fine normally and into bootloader and is visible to adb.
any help would be great!
Hi
Have u tried the old school ruu from HTC via USB plug in?
Its the slowest but most reliable.
Have u tried a different recovery?
Not a new cmr but an older one....
Or
Try RA recovery which is available thru ROM manager.
Sent from my HERO200 using Tapatalk
Download any recovery image on here and extract the recovery.img file and place it on the root of your SD card then issue these commands in terminal emulator:
su
flash_image recovery /sdcard/recovery.img
私のEVO 3Dから送信される
dastin1015 said:
Download any recovery image on here and extract the recovery.img file and place it on the root of your SD card then issue these commands in terminal emulator:
su
flash_image recovery /sdcard/recovery.img
私のEVO 3Dから送信される
Click to expand...
Click to collapse
+1. Make sure that you're recovery image is named recovery image, or make sure you use the right name of that image. Some might have numbers as well. It won't work it's not right. That could be what happened the 1st time. I know from experience. Go s-off next so you can use a HERCIMG.
You think Meth is bad? Try being a flash whore with a Gingerbread habit and a legacy device! It ain't pretty.
noriyori said:
So starting with a functioning CM7 and CWMR v2ish...
I started this whole adventure trying to flash a new recovery via adb and got a "mtd: not writing bad block at 0x001c0000 (ret 1 errno 2)" error and have ever since been unable to boot into recovery.
I'd like to wipe everything and start from scratch but I'm having some problems: cannot flash really anything without errors and cannot get into recovery. Installing recovery through rom manager pulls errors. Cannot flash HERCIMG.zip without error. and I'm stuck with s-on. but no recovery leaves me at a loss for getting s-off... the phone boots fine normally and into bootloader and is visible to adb.
any help would be great!
Click to expand...
Click to collapse
I have a Zip file that can be Flashed from RomManager to give you S-Off!
PM me your Email, and I'll Send it to you!
I found a signed (I THINK....not 100% sure how to tell as I'm S-OFF at this point) HERCIMG.zip that's from a stock RUU. PM me if you want it. I'm 99.8% positive I used it to flash back to stock as a normal RUU won't work for some strange reason when I was still S-ON.

Categories

Resources