Originally Posted by 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...

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

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...-bart-131.html

For those who download from the link below, extract the file first.

Originally Posted by 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...

That's not the lazy version... try "mount -o remount,rw /system" instead.

Originally Posted by 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.

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

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

Originally Posted by gravufo

nah man, 4 works too, trust me, I've used it on tons of phones.
[snip]

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.

Originally Posted by gravufo

but what does the -t yaffs2 stand for? (I probably won't use it, I'm lazy ^^)

It specifies the file system to use.

Originally Posted by rugmankc

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

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>

Originally Posted by 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.

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

Originally Posted by 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>

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

Originally Posted by rugmankc

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

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.