yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] photo_journ:
Noobie needs help please: - Su = Sorry

Hi,

I’m a total nobble at this and I’ve spent hours trolling this board and others looking for the answer.

I’ve successfully unlocked the bootloader and rooted my nexus one but can’t get passed updating the recovery file.

Like I said. I’m a total Noobie. I’m presuming the recovery file is installed before I install Cyanogen 6 ROM

Johns-MacBook-Pro:fastboot john$ ./fastboot-mac oem unlock

... INFODevice was already unlocked!

OKAY

Johns-MacBook-Pro:~ john$ cd

Johns-MacBook-Pro:~ john$

Then reboot and placed the recovery-RA-nexus-v2.0.0.img on the root level of the SD card

Rebooted holding trackball.

Phone shows Fastboot USB highlighted in red

and Bootloader highlighted in blue

Johns-MacBook-Pro:~ john$ su

Password:

su: Sorry

Johns-MacBook-Pro:~ john$

Then I navigate to HBoot highlighted in Blue

and Recovery highlighted in blue

Johns-MacBook-Pro:~ john$ su

Password: (enter)

su: Sorry

Johns-MacBook-Pro:~ john$

So what am I doing wrong? I'm attempting to perform this on a Mac

Any help appreciated thanks
[Nexus One Android Development] Amon_RA:
A 512mb ext backup should restore on a larger ext.

Could you please provide the following info :

- which ext version are you using? ext2 , 3 or 4?

- did you use the same ext version before or after the increase?

- did you reboot into recovery right after you repartitioned your sdcard or did you just do the restore of the nandroid right after without rebooting? If you didn't reboot it could be that the ext partition isn't mounted properly and the ext restore didn't work like it should.

ALWAYS reboot into recovery after you did a repartition (I think I should make this automatic in my next recovery).

You could try the following :

1. make a backup of the FAT content of your sdcard on your pc

2. repartition your sdcard in recovery to full FAT (set swap and ext to 0 when you do the repartition in recovery mode) and reboot into recovery

3. format your sd via a cardreader on your pc (you can skip this step if you don't have the tools)

4. repartition your sdcard in recovery with the desired ext size (set swap to 0 if you don't need it)

5. switch off your phone

6. restore the FAT content of your sdcard to the FAT partition on your sd (so your nandroid backups are back on the sdcard)

7. boot your phone into recovery and restore your nandroid

8. once restored check the recovery log and verify the ext restore went ok

Flashing recovery images thru terminal isn't a good idea, in many cases flash_image will not have enough memory and the recovery isn't flashed correctly. Flash a recovery via fastboot instead or use flash_image via adb in recovery mode.
[Nexus One Android Development] Amon_RA:
See first post please... and follow the via fastboot install method :

fastboot flash recovery recovery-RA-nexus-v2.0.0.img
[Nexus One Android Development] Mo_Nexus:
Hey i'm wondering if toggling the "signature verify" feature off will enable me to install any ota updates from Google on my rooted N1
[Nexus One Android Development] :
Thanks Amon_RA for taking time to respond,

I always use ext3. I may have flashed a bu before rebooting into recovery after repartition, forget. But, that is the only thing that makes sense, now that you mention it. It seems though that the smaller MIUI rom works OK on the ciurrent 1024 ext3, but the larger eVil HD one doesn't. I'd like to keep the larger ext for the HD roms that I like.

I use sdformatter to format card thru a reader, will try it all again, but this time rebooting into recovery, just in case I did not do that.

I will try to get more experience at flashing thru fastboot/flash_image also.

Ken

Amon_RA,

Redid the repartition and rebooted afterwards, pretty sure I forgot to do that before. Restored eVil's bu and phone booted into system. Hopefully, that was the problem. Time will tell. Thanks for the advice.

Ken
[Nexus One Android Development] Fenopy:
I have seen both of these errors when trying to flash RA-Nexus-v2.0.0

I cannot get it to flash. I have Cyanogen's Recovery Flashed, I have even flashed the "Alternative RA-1.7.0.1" listed in ROM Manager. They work fine, both flashed via ROM Manager, and flashed via Fastboot.

From the posts I have read, it looks like something to do with newer Nexus One's.

*** UNLOCKED ***
NEXUSONE PVT SHIP S-ON
HBOOT- 0.35.0017
MICROP- 0B15
TOUCH PANEL- SYNT0102
RADIO- 4.06.00.12_7
Oct 12 2010, 14:33:16

At this point I guess I am sticking with Cyanogen's Recovery, but I would like to be able to use RA's recovery.
[Nexus One Android Development] Amon_RA:
As of HBOOT- 0.35.x the size of the recovery partition is reduced and the size of the boot partition is increased (they probably did this as a preparation for Gingerbread). So depending on the amount of bad blocks in your recovery partition it could be the case that my recovery doesn't fit anymore. In that case you'll get the error you are seeing.

I'll post a smaller version soon which fits on N1's flashed with a 0.35.x HBOOT.
[Nexus One Android Development] alienmonkey:
*******FIXED MY ISSUE BUT PLEASE ATLEAST READ THE LAST PARAGRAPH; STILL HAVE A QUESTION********

I've looked back the past couple pages, but not sure what my issue could be.

Currently on RA v.1.7.0-cyan trying to put v2.0.0-CM on phone.

Phone stats in fastboot mode (holding trackball while pushing power) is as follows.

*** UNLOCKED***

NexusOne PVT Ship S-On

Hboot-0.33.0012

Microp-0b15

Touch Panel-Synt0103

Radio-4.06.00.12_7

Performing via fastboot mode in dos

fastboot devices produces the following line

HT9CSP807060 fastboot

fastboot flash recovery recovery-RA-nexus-v2.0.0-CM.img produces the following lines

sending 'revocery' <4008 KB>... OKAY

writing 'revocery'... INFOsignature checking...

FAILED <remote: signature verify fail>

I've always installed this way, but since it wasn't working I decided to try via terminal for 1st time ever.

Directly after a boot I go into terminal and do the lines and I get a bunch of lines saying read,re-read, or write errors with different memory location I'm assuming and then at the end of the line (out of memory)

MD5 checksum is verified. Any ideas?

Wondering if I need a smaller version as described in Amon_Ra's last post, but I'm not on hboot 35.x

**EDIT** uh oh now recovery is gone :( When i boot holding the volume down button and select recovery, I'm placed into fastboot and not recovery. I've tried flashing 1.7.0 back on, but getting this issue :(

**EDIT** Tried flashing Modaco's Superboot for FRG83 / FRG83D, figuring it was because I haven't installed superboot since Nexus One launch, but still nothing :(

**EDIT** downloaded rom manager from the apps store and ClockworkMod Recovery v2.5.1.0 installed fine through the app and boots up perfectly fine holding down the volume down button. Tried flashing RA through DOS, but same thing. Tried flashing RA v1.7.0.1 or whatever version is in Rom Manager app and would not boot into recovery. Would really like to get RA recovery working again though as i think it's a more robust recovery and well I'm just too comfortable with the user interface

**EDIT** after ~4hrs I've think I've got it need check stuff out. I just flashed through DOS and got two lines sending okay and writing okay

**EDIT** yay success RA 2.0.0 is finally flashed. I essentially wiped the phone dalvik, cache, and rom completely back to virgin status. Slashed RA and it worked.

So I actually still have a question though. I used to use CyanogenMod but stopped after CM5.0.8 because he stopped supporting apps2sd to ext and frankly i could never get Darktremor scipt to work properly. I therefore about 1-2 months ago switched to Enomther's Rom and was running v2.14.3, since it supported apps2sd to ext out of the box so to speak. I know I never had a problem updating RA under Cyanogen, because I'd done it atleast once, possibly twice, however is RA not flashable under certain roms like Enomthers? Also the option Wipe Only /sd-ext in this version would wipe all my apps saved on ext3?
[Nexus One Android Development] superlantern:
anyone else having nand restore failing? it works but all the restore point stay on the solid x
[Nexus One Android Development] Amon_RA:
This sometimes happens for me too when I'm using Windows. I'm not sure why but I think something must be wrong with fastboot. Just disconnect your phone, pull the battery, reboot your pc and try again. Most of the time it will flash without an issue.
[Nexus One Android Development] Amon_RA:
Please provide a recovery log so we can see what is happening.
[Nexus One Android Development] superlantern:
If it happens again I'll get that log to you... don't plan to flash anything for about a week.
[Nexus One Android Development] VanGTO:
Hi Guys

First posting and got RAGE as the post failed lol!

So here I am typing a bloody essay again!

Anyways to give you a bit of background. About a week ago I was running stock ROM with clockworkmod recovery. I used fastboot to flash the original stock FRG83 recovery image so I could get rid of the bloody OTA reminders which were doing my head in and update the system.

Everything went fine with the update and I re-rooted then re-flashed the clockworkmod recovery via ROM manager and that seemed to go fine I did a backup and all was well.

Now I was just playing about with the phone and I thought why not give RA's recovery a bash! So I put it on the SD then flashed using better terminal app then tried to reboot into recovery and I got the stock android recovery warning triangle and recovery 3e menus. Dang!!

Then gave it a go via fastboot and got the Sending recovery blah blahOKAY then the writing recovery OKAY got the finished message then i did fastboot reboot. From there i tried to boot into recovery manually and via quickboot app and on both occasions I got that damn stock recovery WTF HOW??? :mad:

Anyway this is not urgent as I can go back to clockwork but I am very relentlessly persistent so cant let it go until I have succeeded.

So If any of you more learned than I in all things android can help me out or have experienced such then can you let me know how to remedy it?

Would a flastboot erase recovery then try to flash it again be recommended?

Thanks for your time guys.

Kind regards,

VanGTO
[Nexus One Android Development] Amon_RA:
Copy paste from the first post :

Check if there's no /system/etc/install-recovery.sh script if you keep booting back in the stock recovery (exclamation mark with a little Android).

When you're running a stock boot image init will call an install-recovery.sh script which will overwrite any custom recovery with the stock recovery...

You have 2 options :

Update the boot init script and remove the lines where it calls the recovery install scripts.

OR

Check the init script and delete the recovery install scripts.
[Nexus One Android Development] VanGTO:
Hi there,

Sorry if my problem is what you mention from the first post I didn't think that would apply to my situation as I was not having this problem with clockworkmod recovery. Also of note is that I flashed the RA recovery v1.7.0.1 from the ROM manager without any problems?
[Nexus One Android Development] jimbob_me:
Hi guys, having an issue getting this to install.

Ive tried using the terminal on the phone, and the first time it failed. The second time it appreared to complete the process, but upon rebooting the phone would just hang at the 'X' screen. After a hard reboot it boots up fine but i cannot access any recovery. Not even my old version.

What other things can i try?

Ill give the fastboot method a go if someone can give me a quick guide on how to do it? What to install and what to do on both phone and my mac?

Thanks alot
[Nexus One Android Development] HereAsWell:
I got a new sd card and was thinking about the easiest way to transfer the data from the old to the new card. For the FAT32 partition that is pretty easy, but what is the easiest way to transfer the applications from EXT3 partition?

Do I have to do a full nandroid backup and restore, or is there a way to restore just parts of a nandroid?
[Nexus One Android Development] mijaskydive:
hej guys.

i wanna have the bear from the 1.9.0 version in the 2.0.0.

Can anyone help me? :D

thx
[Nexus One Android Development] Amon_RA:
I am 100% sure that your problem is the install recovery script.
[Nexus One Android Development] VanGTO:
Hi Amon-RA,

Sorted will give it a look when I get home. Thanks again for your time and sorry for any inconvenience caused.

Have a good one :-)

Edit: I apologise to Amon-Ra and others for my posts above twas the n00b in me getting the better of me. It did turn out to be as Amon-RA said regarding the recovery-from-boot.p and install-recovery.sh files.

Just in case someone else stumbles along along this thread with similar issues, to avoid them making my mistake, here is what I used in the terminal emulator on the phone:

# mount -o remount,rw /dev/null /system

# mv /system/recovery-from-boot.p /system/recovery-from-boot.p.bak

# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak

# reboot

To Amon-Ra, I will send a donation for a beer/redbull etc... as soon as I have a job lol.

Many thanks.
[Nexus One Android Development] jonata:
Hi,

any news about a recovery for Desire HD ?

...

by
[Nexus One Android Development] meechto:
Even I had this issue. I was updating from MIUI 0.11.19 to MIUI 0.11.26 and had backed up the MIUI 0.11.19 using Nand + ext backup of recovery v2.0. Somehow, I didn't like 0.11.26 much and wanted to go back to 0.11.19. So, I restored the earlier backed up 0.11.19 and rebooted the phone but it simply wouldn't go past the X screen even after waiting for as long as 10 minutes. I was a newbie then and assumed that I had done something wrong and so the phone didn't boot. I went through a few posts on the web which recommended a fresh install of the ROM after wiping everything. I did so and my N1 booted up just fine. After a few days now, while browsing this forum I came across the post by superlantern specifying the same issue. I backed up my current configuration and restored the 0.11.19 backup which had not worked earlier in order to get the recovery log for you. But to my surprise my phone booted just fine this time. So, I guess the recovery log won't give much clue. Hence, not providing it right now but would definitely do so, if I come across this issue again. ;) Thanks :)
[Nexus One Android Development] ermacwins:
Where is the recovery.img stored on the phone? I remember seeing a recovery.img with root explorer but forgot where. I take it that is the recovery?
[Nexus One Android Development] Alch7:
Tried to flash via fastboot but Im only getting "error: cannot load `recovery-RA-nexus-v2.0.0.img`.

Any help pls?

Root via SOC.

Alch
[Nexus One Android Development] meechto:
Please make sure that you have typed the command correctly as shown below and if you are running the fastboot command from within the tools folder of your android sdk then make sure that your recovery-RA-nexus-v2.0.0.img file is in that folder :)

fastboot flash recovery recovery-RA-nexus-v2.0.0.img
[Nexus One Android Development] mixmaven:
I am missing the care bear, always brought a little smile to my day!

:)

-mix
[Nexus One Android Development] Alch7:
Thank you now ive got another problem.

I didn`t get these Recovery to work properly (with Rom Manager the Recovery worked once but after a reboot it didnt work anymore (Ra 1.7 or something, same with Clockwork which comes with it).

Well i thought i`ll wait and read a bit in the forums because im kinda new to this Root/Flash/Rom things. I installed Metamorph trough market and apllied an Theme which asked me to reboot and from now on im stuck on a boot loop(Didnt notice that this is only for CM/AOSP) :( I tried to flash a recovery (ra 2.0.0, ra 1.7, clockwork (newest dont know the exact version). Always getting the error "siganture failure" (something like that, don`t know it exactly) . I got a Nandroid Backup on SD Card i just need to get this damned recovery working :(( Is there anyway this is possible (to flash a recovery in my circumstances) or do i have to send the N1 to HTC and hope that they dont recognize my Root etc. ?

Would really appreciate some help and thank you with a beer :D

Alch

(sorry my english isn`t the best on earth)
[Nexus One Android Development] dacorde:
Regarding to the errors when flashing the last recovery, I had the same issue:

Command:

flash_image recovery /sdcard/recovery-RA-nexus-v2.0.0.img

Result:

mtd: not wrinting bad block at 0x00060000

error closing recovery: No space left on device

I had no problems flashing the 1.7.0.1 version.

Antecedents:

- I had previously the hboot version 0.33.012 and I wasn't able to flash some ROMs.

- I got this log from last_kmsg, after suffering the famous status 7 error (related to boot partition):

flashing boot fmtd: not wrinting bad block at 0x00060000

error closing rom /tmp/boot.img

mtd: not writing bad block at 0x000c0000

mtd: not writing bad block at 0x00160000

error closing bootscript aborted: assert failed: write_raw_image("/tmp/boot.img", "boot")

- I decided to update the hboot to 0.35.017 and it revolved the "status 7 error" when flashing some ROMs.

After I read this from Amon RA I hope the solution is comming:

As of HBOOT- 0.35.x the size of the recovery partition is reduced and the size of the boot partition is increased (they probably did this as a preparation for Gingerbread). So depending on the amount of bad blocks in your recovery partition it could be the case that my recovery doesn't fit anymore. In that case you'll get the error you are seeing.

I'll post a smaller version soon which fits on N1's flashed with a 0.35.x HBOOT.

Thank you Amon RA!!
[Nexus One Android Development] Alch7:
So u think i should try flashing 1.7? Or is it senseless to try to "repair" my issue and send it to HTC :(

Anyway I´ll try it later when im home, currently at work ...
[Nexus One Android Development] aha27:
Will you tweet this, post it somewhere in this thread or announce it by changing the post #1? just so i know where to look while my n1 is waiting for it ;-)
[Nexus One Android Development] Suatae:
+1 I have 0.33.0012. Thank you so much, I can't wait for the new smaller version.
[Nexus One Android Development] wastegate13:
I am currently running 1.7 recovery version. Is there any reason I should upgrade to 2.0? I don't flash a new rom every day, and am more or less an average user.
[Nexus One Android Development] ronnyzilker:
can someone tell me what am i doing wrong... every time I try to download the recovery image on my mac it says "fail to mount".. what kind I do.. i lost my recovery image when I flashed gingerbread......
[Nexus One Android Development] Frankenstooge:
This is very interesting.

FWIW, I've been using (and loving) the 2.0 recovery for quite a while. But yesterday I upgraded my HBOOT from 0.35.0012 to 0.35.0017 so I could try on the first gingerbeard AOSP port. When I did, the recovery started behaving badly and would not complete backups, restores, and a couple of other things I can't remember. I tried reflashing it, but got the 'not writing bad block' error. I ended up having to flash clockworkmod over it, then problem solved and I got to play with GB.

Now I've restored things back to my old CM6.1.1, and am trying to bring back 2.0 recovery, but no dice - same old error.

I'm thinking that HBOOT 0.35.0017 just doesn't allow room for your sweet recovery.

Thanks for the tip, I'll go back to 1.7 or 1.9 until you calmly work another miracle.
[Nexus One Android Development] GldRush98:
No. As Amon_RA said, it depends on how many bad blocks your phone's flash memory came with from the factory. If you have too many bad blocks, you have a slightly reduced memory space. Reduced enough to where you no longer have room for Amon's recovery.

There are plenty of people on the .35 hboot running Amon 2.0 just fine, including myself.
[Nexus One Android Development] crachel:
The big difference between the two is that, in 2.0, the flashable ZIPs do not have to reside on the root of the SD card, but instead can be anywhere on the SD. The recovery allows you to navigate through folders.

Also, some people with SLCD displays couldn't see the recovery, that has been addressed in 2.0.

So, as a user that doesn't flash ROMs often, doesn't have an SLCD display, I would say the most practical thing is to just stick with 1.7
[Nexus One Android Development] zekers:
Thank you!

Thank you sooo much Amon_RA! I first used 1.8 and more recently 2.0! Thank you for all your hard work. Your recovery is much nicer than Clockwork!
[Nexus One Android Development] Frankenstooge:
You know what? You're right. Criminy.

No way to resurrect that bad block by formatting or anything is there?
[Nexus One Android Development] Amon_RA:
I'm working a new version (will try to release it this weekend) which is +- 800kB smaller. That means it will flash with any hboot, even when you have a few badblocks.
[Nexus One Android Development] :
Is there any reason to upgrade HBOOT? Specifically, while there are no changelogs for hboot, besides allowing Gingerbread to be flashed (which is of no consequence to me until CM releases a stable for it), are there any other known improvements/advantages to hboot 35.whatever.17 over my current 33.something.something hboot?

I also heard that flashing some of the newer hboots on an unlocked nexus one may end up disabling some adb flash commands. Anyone know for sure?

Also, will flashing an HBOOT .img via recovery erase the recovery/ROM I currently have installed, or is it kind of like updating the radio (which only modifies the radio and not /system or /recovery etc) ?

Thanks in advance for replies.
[Nexus One Android Development] efrant:
There doesn't seem to be any reason to upgrade HBOOT aside from it potentially being a requirement for Gingerbread.

Upgrading HBOOT does not disable any ADB commands.

Flashing an HBOOT does not affect the recovery or system partitions.
[Nexus One Android Development] Frankenstooge:
You're the man!

Awesome news!!!!

http://twitter.com/#!/Amon_RA/status/16586646984073216
[Nexus One Android Development] gravufo:
w00t thanks for reportin :P

Btw, will the 800kb less take off any functionality or so, or is it just optimization?
[Nexus One Android Development] :
At a later point on Twitter, Amon Ra stated that the smaller file size was due to optimizations in the recovery kernel--no loss of functionality.
[Nexus One Android Development] gravufo:
Thanks a lot for the info, appreciated :)

Glad it was optimizations, since my device is SLCD and I cannot go under the newest hboot =\
[Nexus One Android Development] jbbandos:
Hi AmonRA,

I was having problems restoring a nandroid backup of a MIUI ROM. It would get stuck in the X screen. I did a adb shell, and found out that /data/sd/dalvik-cache didn't get recreated by the backup. The fix was just creating that dir, inside adb. After that the phone booted smoothly.

Can you please add creating this directory to the restore procedure when there are already /data/sd/app and /data/sd/app-private directories?

Thanks!
[Nexus One Android Development] Amon_RA:
This will be fixed in the next recovery version. This recovery only backups apps on sd-ext, I'll make it backup everything so you don't have this issue anymore. Thanks for reporting this.
[Nexus One Android Development] meechto:
Hey, thanks! :) I had the same issue some days back which I had reported a few pages back. I just didn't know about the /data/sd/dalvik-cache not getting created.

Thanks, Amon_RA. Would be looking forward to this recovery ;)
[Nexus One Android Development] Jesse6749:
I can't wait for the recovery!!! :D, I only started using clockwork recovery only cuase it backs up everything, but I always preffered AmonRa recovery and really want to switch back as soon as this new version is released.
[Nexus One Android Development] MicroMod777:
Yea, good news for next update! Finally HD-ROM's will get full backup support on the ext! :)

...and if possible, can u make signature-off as default as ROM Manager does? Just makes testing updates for ROM's a little easier! I have no problem signing ROM's, as its very easy to do, which I do before I upload my next update! :)