yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] torchedlh:
Question:

I recently switched from Amon's recovery to ClockwordMod but now i want to go back. I never unlocked my bootloader to begin with, do I need to do anything special for installatoin? Can i just follow the instructions to install via terminal emulator?
[Nexus One Android Development] gravufo:
Make sure you're rooted and have flash_image and the recovery image in the root of your sd card. Then input these commands in a command prompt in windows while your device is plugged in (with USB Debugging preferably):

adb shell

su

mount -o rw,remount /dev/block/mtdblock4 /system

cat /sdcard/flash_image > /system/bin/flash_image

chmod 775 /system/bin/flash_image

flash_image recovery /sdcard/recovery.img

rm /system/etc/install-recovery.sh

rm /system/recovery-from-boot.p

reboot recovery

Done :)

NOTE: The two "rm" commands might give an error, it doesn't matter...it's just preventive measures.
[Nexus One Android Development] yumcax:
Halp.

I used Terminal Emulator, got an error:

error flashing recovery: no space left on device.

What can I do?
[Nexus One Android Development] torchedlh:
Thanks for the help!
[Nexus One Android Development] torchedlh:
Ok so i attempted this in Terminal Emulator. However, I made a mistake and left out the 4. i just did .../mtdblock /system

I realized this after doing all but the last command (reboot recovery).

It looks like I'm okay according to this post:

http://www.droidforums.net/forum/dr...ock3-vs-mtdblock4-stop-using-mtdblock3-1.html

What do you guys think?

Thanks!
[Nexus One Android Development] efrant:
Actually, that was not what he was asking. He was asking if he would still be able to restore Nandroid back-ups made with prior versions of Amon_RA, using the current Amon_RA. The answer I believe is yes, given that the scripts work the same way.

I think you are confusing a couple of things here:

- ADB is short for Android Debug Bridge, and it is a tool to manage Android devices when you connect your device to your computer. ALL android devices "use" ADB.

- flash_image is a utility that allows you to flash partitions via an ADB shell or via a terminal on the device. flash_image requires root access, and it is exactly the same command whether done via ADB or on your device.

- Fastboot commands can only be run on devices with unlocked bootloaders. Fastboot allows you to flash any partition on your device when connected to your computer. Root access is irrelevant. :)
[Nexus One Android Development] efrant:
It actually should be mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system (or mount -o rw,remount /dev/block/mtdblock3 /system if you're lazy) for a Nexus One. Note the 3, not a 4...
[Nexus One Android Development] gravufo:
nah man, 4 works too, trust me, I've used it on tons of phones.

but what does the -t yaffs2 stand for? (I probably won't use it, I'm lazy ^^)
[Nexus One Android Development] overground:
For those of you who know what BART is (check the G1 forum for the thread, basically a wrapper for Nandroid), here is 2.0.0 with BART added in. Credits to Dumfuq for doing this for me. To see the BART options, while in this recovery, and connected to your PC type:

adb shell
bart -h

Enjoy

http://www.4shared.com/file/tIbSrYbE/ra-200-bart-131.html

For those who download from the link below, extract the file first.
[Nexus One Android Development] landstander:
That's not the lazy version... try "mount -o remount,rw /system" instead.
[Nexus One Android Development] :
Thanks efrant,

I have used both Terminal and Fastboot with Command Prompt. Just horrible with the "exact" command lines. Haven't done it enough yet, so have to really research exactly what to type. I just saw somewhere there was no underscore between flash and image on a fastboot command line example. And I use one in Terminal. Been 7 months since doing any real commands in Fastboot so don't remember much. Any way, thanks and 2.0.0 is working well for me.

Ken
[Nexus One Android Development] Brajin:
Just Flash Over, everything works great, thanks for the new update. Can some one post up a screen shot of what the jesusfreke version looks like please thanks
[Nexus One Android Development] efrant:
Just because it may work sometimes doesn't mean it is the right way to do it. The system partition in a Nexus One is mtd3. To see all the partitions in your device, enter this in a root shell (via ADB on a computer or a terminal on your device): cat /proc/mtd

All devices have different partitions, and you should technically mount the correct one.

It specifies the file system to use.
[Nexus One Android Development] efrant:
What I'm trying to get across here, is that there is no flash_image or flashimage in fastboot. For example, if you want to flash a recovery image using fastboot, the command would be:

fastboot flash recovery <recovery.img>

If you wanted to flash a recovery image using flash_image (whether via a terminal shell on your device, or and ADB shell in you computer), the command would be (root required):

flash_image recovery <recovery.img>
[Nexus One Android Development] gravufo:
I see, but please clarify more...how come it would work if I'm using the wrong partition? /system is present in both partitions or what? O.o

Thanks for the specifications
[Nexus One Android Development] :
Thanks for reply,

Must have seen a bad example. Like I said haven't really done anything thru fastboot since I unlocked and rooted 7 months ago.

I do have flash_image on my sd card. Guess that's why I use those commands.

So, you could use flash_image thru adb with a rooted phone but locked bootloader? Or, do you need to be unlocked for both, just not rooted for fastboot?

Appreciate any tutoring info I can get. :)

Ken
[Nexus One Android Development] efrant:
Unlocking your bootloader = the ability to use fastboot to flash images to your device. Nothing more to it than that.

Bootloader locked => need to find another way to flash images to your device (such as the flash_image utility). Rooted or not, it doesn't matter -- you cannot use fastboot without an unlocked bootloader.

To use flash_image, your device needs to be rooted. You can run flash_image from a terminal window on your device, or within an ADB shell. Locked or unlocked bootloader doesn't matter.
[Nexus One Android Development] efrant:
I wish I could answer that, but I don't know why it works when you use mtd4 instead of mtd3 on a Nexus One. Maybe one of the Android gurus will chime in and answer that for us. I have never tried using mtd4 personally. /system is certainly mtd3 on a Nexus One.
[Nexus One Android Development] SiNJiN76:
anyway to have the unsigned update.zip toggle to stay put until it's toggled manually again?
[Nexus One Android Development] :
Greatly Appreciated efrant,

Understand and I will store this info away :) And hopefully pay it forward at some point.

Ken
[Nexus One Android Development] eric923456:
hey man thx for the command
[Nexus One Android Development] Luigi3_it:
Hi to all, I'm new in this world and sorry for my english.

I want to install a cyanogenmod rom and I follow this topic. All ok, but when I try to do:

1.Boot the phone while holding down the VOLUMEDOWN-key.

2.Navigate to RECOVERY with the the VOLUMEDOWN-key.

3.Press the POWER-key to select.

after step 3, I see only a black screen with the android and an esclamation point.

Where I make an error?

Pleas help me :(
[Nexus One Android Development] :
I don't think you'll get much help in this thread on routine rom flashing. Maybe post in Cyanogen Forum or The XDA Nexus One Q&A Thread.

But that said, someone will want to know how you rooted, what recovery did you flash after rooting, and did you do a backup of your stock rom before flashing cyanogen and wipe all before actually flashing the rom. Your post sounds like you already flashed cyanogen, not sure.

Ken
[Nexus One Android Development] efrant:
That is because you still have a stock recovery. You need to flash a custom recovery and make sure you delete or rename these two files (/system/etc/install-recovery.sh and /system/recovery-from-boot.p) before you reboot your device, otherwise, your custom recovery image will get over-written by the stock recovery after every reboot.
[Nexus One Android Development] SiNJiN76:
All apps got deleted/corrupt after flashing 2.0 using apps 2sd froyo way. Happened on 2 different phones. :(
[Nexus One Android Development] Hatchet65:
If this is the case, it is very important to a problem that I am having. Where do I access these files?

John
[Nexus One Android Development] efrant:
What are you talking about? I stated the locations in my post...
[Nexus One Android Development] RunTimeWorld:
This is a real saver, great piece of software. I was wondering if implementing a prevention of overwritten boot images by scripts like the /system/etc/install-recovery.sh would be possible? That would save a lot of time and failure quote.
[Nexus One Android Development] Amon_RA:
The prevention is to actually read the first post of this thread!

Copy paste from the first post :

Pre-Requirements :

- unlocked bootloader : How to unlock the bootloader.

- root access : Modaco's superboot.

If you install Modaco's superboot you'll not have any issue as it removes the startup of any recovery script during boot... so if you are having issues you didn't comply to the pre-requirements.
[Nexus One Android Development] RunTimeWorld:
Copy paste from your post:

Take from this link:

http://android.modaco.com/content/g.../299241/24-feb-1-6-2-ra-nexus-recovery-image/

Install

Pre-Requirements :

- unlocked bootloader : How to unlock the bootloader.

- root access : Modaco's superboot.

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).

So apparently I haven't realized that this was outdated

In any way, I am glad that hard working people like you get me up and running.
[Nexus One Android Development] Silverexp:
I used the following commands & now I'm stuck on boot-loop with th "X". This all started because I wanted to remove clockworks. Anyone have any ideas??? I've spent all of sunday on this...
[Nexus One Android Development] Amon_RA:
It's not outdated... I added that last sentence in bold because people don't read and keep on sending PM's that they can't flash it. My point is that it's mentioned clearly in the the 1st post and it's already handled by modaco's superboot, so it's already prevented automatically. ;)
[Nexus One Android Development] RunTimeWorld:
You could try a battery pull and get back into fastboot mode by holding the trackball. From there you can fastboot flash recovery recovery-RA-nexus-v2.0.0.img . So you have no longer a boot-loop. That might help as a start.

Also I learned in this short period of time that I'm dealing with Android, that clockworkmod does not work, if you have another boot option such as RA.

In fact myself I attempted to install a stock image with ROM Manager on CM 6.1, while having RA installed, resulted in a black screen. Hope this helps as a start.
[Nexus One Android Development] RunTimeWorld:
Gotcha! I really appreciate the time you take to reply to all these posts, while working on the projects. Respect!
[Nexus One Android Development] tltester:
Amon - thanks for your great recovery. Using it since 1.7, the only things that I was missing were the ability to choose folder with update.zip and to disable mandatory signing on demand, now it's completely perfect :)

I'm wondering, however, why are you listing unlocked bootloader as an absolute requirement? I was scared to update to 2.0 for a while after seeing this. However I did update and everything is just great with my locked bootloader :)

Don't you think it's a little missleading?
[Nexus One Android Development] Amon_RA:
Does your regular ROM bootloop or does the recovery boot loop?

Correct, my recovery is not compliant with the automated install features of rom manager. I'll also not add those because ROM Manager is a clockworkmod product and should use the clockworkmod recovery :-)
[Nexus One Android Development] Amon_RA:
True... the 1st post was written when we couldn't root the phone without unlocking the bootloader... I might as well remove it.
[Nexus One Android Development] RunTimeWorld:
Kudos for your help in the other thread! I'm deleting my offtopic question, as it seem to stop the current thread here.
[Nexus One Android Development] RiNo808:
okay i just flashed the new recovery, my problem is that i cant perform a nandroid backup..it gives me an error : run 'nandroid-mobile.sh' via adb! please help in this error...
[Nexus One Android Development] Silverexp:
Thanks for the reply… it was the regular ROM bootloop. I was finally able to flash one of my custom rom to get back to normal, which started another nightmare… All good now. Just need to figure how to slipstream this FRG83D update into my custom FRG83 rom… :o
[Nexus One Android Development] FormelLMS:
Has anyone successfully restored a Nandroid Backup made with the 2.0.0 recovery?

Mine doesn't work. ROM goes to bootloop.

Backup made with 2.0.0

Restore tried with 2.0.0
[Nexus One Android Development] Amon_RA:
Yes, I've tested and used it many times before I released v2.0.0.

Could you please give more details?

- What does your backup contain? (with or without ext?).

- Did you wipe anything before restoring the nandroid backup?

- Where there any errors during the backup/restore?

- Could you provide the recovery log of the backup/restore?
[Nexus One Android Development] haven80:
I have backupped many time with 2.0 with and without EXT.

All works fine as always.

Thank you for the awesome work.
[Nexus One Android Development] :
Try this link for some ideas,

The search button is your friend--:)

I have also seen comments about not restoring a rom with amon that was made with clockwork and vice versa. Know that is not your current problem, just FYI.

Ken
[Nexus One Android Development] gulfie:
Removing /system/etc/install-recovery.sh

I had the problem with /system/etc/install-recovery.sh being present and had to hunt around to find out how to get rid of it. Of course it turned out that you have to remove it before installing the new recovery tool. So here are the steps you need to go through:

Connect the phone to your PC and turn it on (if it isn't already), ensure debugging is enabled.

Once the phone notifies you that USB debugging is connected move to a shell window on your host machine and run the following sequence of commands (when you run 'su' your device will prompt you to grant root access):

adb shell

su

mount -o remount,rw /dev/block/mtdblock3 /system

cd /system/etc

ls​

And, if install-recovery.sh is present:

rm install-recovery.sh​

And finally:

exit​

Now you can install the new recovery image successfully!
[Nexus One Android Development] chris4chelsea:
hi all experts, can anyone tell me what the new Mount function is for? i m not sure if i have mistakenly mount/unmount any of those options under the Mount function.

i see that i have only /cache as unmount and others are mount. is that correct/default?
[Nexus One Android Development] AcoSys:
Hi there,

I need some help and can't find a really solution for it.

I wiped my Nexus completely and installed a new Radio. Now I want to flash the new RA 2.0.0 recovery and I get the following error:

F:\Nexus\android-sdk-windows\tools>fastboot flash recovery f:\Nexus\stock\Mods\recovery-RA-nexus-v2.0.0.img
sending 'recovery' (4074 KB)... OKAY
writing 'recovery'... FAILED (remote: image update error)

If I boot the recovery with "fastboot boot recovery.img" it works. Also I can falsh the Clockworth-recovery or the old 1.7.0.1 version. I didn't install a ROM yet.

Has anybody an idea whats the problem?
[Nexus One Android Development] :
I don't think you wipe phone to flash new recovery.

http://xdaforums.com/wiki/index.php?title=Nexus_One/Recovery_Images

Assuming you are familiar with the right ADB commands (I am not the best) to do this and typed them correctly, did you put the recovery image in the tools folder.

BTW, I flashed mine with Terminal Emulator, no problems. Although some have had issues that way.

Ken
[Nexus One Android Development] efrant:
What HBOOT do you have? Just thowing this out (I have no idea if it is true or not), but some recoveries may have some compatability issues with HBOOT 0.35.
[Nexus One Android Development] AcoSys:
It's the same to Bootloader-version? I have 0.35.0017

Should I update this? If - how?
[Nexus One Android Development] :
AcoSys

These two links talk about hboot .35 and .33. I have .33. Don't know if it has anything to do with your problem or even if mye suggestion will help. It is over my head. efrant may shed some light, he is way better on this stuff. Hope you get it resolved.

http://xdaforums.com/showthread.php?t=726258

http://www.nexusoneforum.net/forum/...lp-phone-asked-update-now-screen-blank-4.html

You can google more links.

Ken
[Nexus One Android Development] efrant:
I don't know if the version of HBOOT has anything to do with it, but I have read that a couple of users had issues with flashing Amon_RA 2.0 while on the 0.35 HBOOT. It could just be something they are doing wrong.

You already have the latest HBOOT, so you can't update.

Try flashing Amon_RA 1.9. If that works, then just use that, no? (I like 1.9 better anyway, as signature checks are disable by default on it, unlike 2.0). Otherwise, if you really want 2.0, re-download it and re-verify the hashes before trying to flash it again.
[Nexus One Android Development] belair56:
Thank You

Thank you for your JesusFreke tribute.

That is GREAT.

#6U396513JT356511C
[Nexus One Android Development] anti-pop:
I'm using a rooted Nexus One (SuperOneClick) with a locked bootloader.

I wasn't able to successfully flash RA-nexus-v2.0.0 recovery because of the "bad block" error:

I tried flashing through an adb shell or via a terminal emulator window directly on the phone, both time using flash_image and I got the error every time.

Several people have had the bad luck to experience this. Am I correct in assuming that:

- Since I have bad blocks in my recovery partition, there's nothing I can do about it. Bad Blocks are bad blocks, there's no magic wand to fix those. It means there's no way for me to use RA's recovery images on my phone at this point.

And another question:

- If the recovery image I was trying to flash was smaller, could I avoid the bad blocks? Meaning if I tried to flash an older (and smaller) RA recovery image, could that work?
[Nexus One Android Development] zenicsg:
For some reason with version 2 on my phone, I am unable to flash kernels. After a successful flashing, upon rebooting, the kernel version remains the same as the old one. Then WiFi stops working.

Another issue is flashing new roms. Gapps is not automatically backup. I have to flash gapps after each cyanogenmod nightly.

Somehow the problems go away with recovery 1.7.0.1
[Nexus One Android Development] gravufo:
Indeed, you are stuck with a bad phone...you COULD try a smaller recovery (try PMing Amon_Ra and he might make you a custom smaller version, give him the error it gives you so he can maybe know how big he needs it to be) I've seen that work...good luck!
[Nexus One Android Development] SBERG117:
Had a similar problem , only mine involved not being able to flash a radio. I went back to recovery 1.9 alpha and now radio flashed with no problem. Read thats its a sig verification thing thats turned off in older recoverys. Didnt bother checking if its able to be undone in 2.0.
[Nexus One Android Development] anti-pop:
Thanks. I now doubt even a smaller custom recovery would work. I tried flashing ClockworkMod (which is 1 Mo smaller than RA's) and got the same error (mtd: not writing bad block at 0x001c0000). I'm stuck with stock recovery.

I won't be flashing any custom rom, doing so without the ability to do backup through a recovery image would be too risky. I guess stock with root ain't so bad.
[Nexus One Android Development] the_canuck:
is there currently an issue with the 0.35 HBOOT?

i am trying to flash the recovery image, and no matter what i do, i get an error.

if i try it from fastboot with the img file in my tools folder, i get:

error: cannot load 'recovery-RA-nexus-v2.0.0.img'

simlar result when trying from the shell and doing the flash_image command:

flash_image: not found

my phone has both the bootloader unlocked and is also rooted. the md5sum is confirmed. running FRG83D. see screenshots attached.
[Nexus One Android Development] gravufo:
You obviously are missing the "flash_image" binary...since you're from Montréal and most probably speak french, go to my website and do only "PREMIERE PARTIE"

http://gravufo.kicks-ass.org/android_flash.html

PS: Don't download the ROM, it's not necessary for that :P
[Nexus One Android Development] the_canuck:
merci beaucoup :)
[Nexus One Android Development] gravufo:
Bienvenue ;)
[Nexus One Android Development] rotaha:
i just can not flash the amon ra recovery

i have hboot 0.35.0017

and it is eror all the time:

what can i do?
[Nexus One Android Development] :
What are the default mount settings for 2.0 while in recovery

I used 2.0 to repartition sdcard and first selected mount sd, nothing happened. Tried mount data etc. Then saw USB Toggle and realized I goofed, am restoring now.

Speed started slow at 700kb now is 1.42mb. Is that normal. CW runs around 2.5mb

When done do I need set default mount settings, or will that be done time I run 2.0

Ken
[Nexus One Android Development] :
Never mind, got it.

Seems they reset. Partitioning went well
[Nexus One Android Development] dai_thang:
could some one solve me this problem ?

Firstly, I install ROM manager and install clockwork

I could enter recovery mode easily. So i flash Radio version 5 the flash desire superhybrid ( in this link ) http://xdaforums.com/showthread.php?t=784260

However this seem to be unstable because after the fist run, it re boot automaticly

the I flash to MIUI in this link

http://xdaforums.com/showthread.php?t=799737

the same problem it reboot automatik

even wipe everything.

i think it maybe because of the recovery of clockwork could not wipe completely

I flash RA 2.0 recovery via Fastboot and .....

I could enter recovery it hang

and now i cant do any thing exept flash via fastboot

Could expert give an advice ?

I see to be mad now :((
[Nexus One Android Development] :
Using 2.0.0 on N1

I repartitioned to 1024mb ext3. 16gb card. Since then I have had trouble rebooting into system from recovery, whether on 2.0.0 or CWMod. It just stays on X. I 3 finger to get to recovery. The first time I had to reflash a rom to get back to system. After that. it has been intermittent on just restoring to get back.

I tried restoring a differnet rom MIUI instaed of the eVil HD I was using. His rom is very large and the reason I increased ext size.

Question is could my repartition have gone bad based on comments I have a couple posts up to cause this issue. And when I restored the MIUI bu that was made with a 512mb partition it said it couldn't mount sdext and put all on internal. Except the links are still to the ext and don't open on some. Is that common for a bu done with 512mb ext not to restore to a larger size ext?

Ken
[Nexus One Android Development] :
Tried to reflash 2.0.0 thru terminal, first time gave me a memory error, second time flashed. But, hung on X, 3 finger did not reboot phone. Pulled battery, sdcard, and sim. That rebooted phone. But, it came back up into RM/CW.

Lot of wierd stuff going on, so any advice would help!

Maybe I should just repartition back to 512 so all roms work, if that is an issue. Had no problems before repartitioning. eVil's HD did work on the 512.

Ken