[Recovery] [07-Jan-2011] RA-passion-v2.2.1

Search This thread
By:
Advanced…
G

GuestX0019

Guest
efrant said:
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. :)
Click to expand...
Click to collapse



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
 
Brajin

Brajin

Senior Member
Aug 27, 2009
231
1
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
 
efrant

efrant

Retired Senior Moderator & Developers Relations
Feb 12, 2009
11,469
10,985
Montreal
Samsung Galaxy S20
gravufo said:
nah man, 4 works too, trust me, I've used it on tons of phones.
[snip]
Click to expand...
Click to collapse
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.

gravufo said:
but what does the -t yaffs2 stand for? (I probably won't use it, I'm lazy ^^)
Click to expand...
Click to collapse
It specifies the file system to use.
 
Last edited:
efrant

efrant

Retired Senior Moderator & Developers Relations
Feb 12, 2009
11,469
10,985
Montreal
Samsung Galaxy S20
rugmankc said:
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
Click to expand...
Click to collapse
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>
 
Last edited:
gravufo

gravufo

Senior Member
Sep 26, 2010
341
21
Montréal
efrant said:
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.
Click to expand...
Click to collapse

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
 
G

GuestX0019

Guest
efrant said:
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>
Click to expand...
Click to collapse



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
 
efrant

efrant

Retired Senior Moderator & Developers Relations
Feb 12, 2009
11,469
10,985
Montreal
Samsung Galaxy S20
rugmankc said:
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
Click to expand...
Click to collapse
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.
 
efrant

efrant

Retired Senior Moderator & Developers Relations
Feb 12, 2009
11,469
10,985
Montreal
Samsung Galaxy S20
gravufo said:
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
Click to expand...
Click to collapse

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

SiNJiN76

Senior Member
Sep 14, 2009
3,993
626
anyway to have the unsigned update.zip toggle to stay put until it's toggled manually again?
 
G

GuestX0019

Guest
efrant said:
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.
Click to expand...
Click to collapse


Greatly Appreciated efrant,

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


Ken
 
E

eric923456

Member
May 23, 2010
16
0
efrant said:
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>
Click to expand...
Click to collapse

hey man thx for the command
 
L

Luigi3_it

New member
Feb 24, 2010
1
0
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 :(
 
G

GuestX0019

Guest
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
 
efrant

efrant

Retired Senior Moderator & Developers Relations
Feb 12, 2009
11,469
10,985
Montreal
Samsung Galaxy S20
Luigi3_it said:
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 :(
Click to expand...
Click to collapse
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.
 
SiNJiN76

SiNJiN76

Senior Member
Sep 14, 2009
3,993
626
All apps got deleted/corrupt after flashing 2.0 using apps 2sd froyo way. Happened on 2 different phones. :(
 
H

Hatchet65

New member
Oct 8, 2010
2
0
efrant said:
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.
Click to expand...
Click to collapse

If this is the case, it is very important to a problem that I am having. Where do I access these files?

John
 
RunTimeWorld

RunTimeWorld

Senior Member
Nov 10, 2010
153
29
Switzerland
runtimeworld.com
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.
 
Amon_RA

Amon_RA

Retired Senior Recognized Developer
Jan 2, 2009
1,295
400
RunTimeWorld said:
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.
Click to expand...
Click to collapse

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.
 
Last edited:
RunTimeWorld

RunTimeWorld

Senior Member
Nov 10, 2010
153
29
Switzerland
runtimeworld.com
Amon_RA said:
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.
Click to expand...
Click to collapse

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.
 
Last edited:
You must log in or register to reply here.

Similar threads

imfloflo
[NIGHTLY] [ROM] [GWK74] CyanogenMod 7 for vendor Passion (HTC Nexus One) - KANG
Replies
23K
Views
4M
V
Verrocio
dk_zero-cool
[ROM][MOVED] ICS 4.0.4 BCM RC4.1U2 Passion <2012-07-03> (Bravo CM9 HWA)
Replies
2K
Views
633K
Nognir
Nognir
enomther
  • Locked
[ROM] Enomther's TheOfficial Nexus1 - v2.14.4 - 11/26/2010
Replies
8K
Views
2M
willverduzco
willverduzco
texasice
[ROM] [DEV] [ICS 4.0.4] *7/1* Evervolv's Aosp TexasIce Cream Sandwich
Replies
4K
Views
2M
G
gcbxda
I
  • Locked
[Kernel] [.38.8] intersectRaven's Kernel (AVS/CAVS)01/08/2011 22:00
Replies
6K
Views
1M
Rafase282
Rafase282

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 9
    Amon_RA
    Amon_RA
    This is a custom recovery based on Cyanogen's recovery source with a lot of things added by me. The purpose of this recovery is to avoid using adb by accessing all features directly from the menu.

    This recovery is for the HTC Nexus One only, if you have a :
    - HTC Dream/G1 you should go here.
    - HTC Magic/MT3G you should go here.
    - HTC Hero you should go here.
    - HTC Sprint Hero you should go here.
    - HTC Eris you should go here.
    - HTC Tattoo you should go here.

    Important notes
    • Always check recovery.log before posting your issues!
      You can do this by doing :
      • "cat /tmp/recovery.log" OR "cat /cache/recovery/log" right after you had the issue.
      • Use the "move log to sd" option in the "others" menu right after you had the issue. This will move the log to /sdcard/recovery.log so you can easily open it with a text editor.

    Features

    Use the trackball (up+down) to navigate through the menu, press the trackball to select items. Use the Volume-down key to go back to a previous menu.

    Features
    • full ADB access in recovery mode
    • Alternative CM and JF version
    • Busybox v1.15.3
    • Kernel (2.6.35.7) with ext3 + ext4 support
    • SLCD and AMOLED support
    • HW-Key navigation (Trackball + Volume-key) option
    • Extended menu :
      • Reboot system now :: reboot your phone
      • USB-MS Toggle :: enable/disable USB mass storage (use when the phone is connected to your PC)
      • Backup/Restore
        • Nand backup :: Make a selective Nandroid backup
        • Nand restore :: Restore a Nandroid backup
        • Backup Google proprietary system files :: Makes a backup of the Google proprietary system files in /cache/google
        • Restore Google proprietary system files :: Restores the Google proprietary system files from /cache/google
      • Flash zip from sdcard.
        • Choose zip from sdcard :: Flash a zip update file from any (sub)-directory on your sdcard
        • Toggle signature verification :: Toggles the signature verification for zip files.
      • Wipe
        • Wipe ALL data/factory reset :: wipes /data + /cache + entire ext partition + all apps installed on your sdcard (froyo a2sd).
        • Wipe /data :: wipes /data.
        • Wipe /cache :: wipes /cache.
        • Wipe /sdcard/.android_secure :: wipes all apps installed on your sdcard (froyo a2sd).
        • Wipe /sd-ext :: wipes the entire ext partition on your sd (if present).
        • Wipe Dalvik-cache :: wipes the dalvik-cache located in /cache + /data + /sd-ext is present.
        • Wipe battery stats :: reset the battery calibration.
        • Wipe rotate settings :: reset the sensor calibration.
      • Partition sdcard
        • Partition SD :: Interactive SD partitioning
        • Repair SD:ext :: Repair the ext partition
        • SD:ext2 to ext3 :: Convert ext2 to ext3
        • SD:ext3 to ext4 :: Convert ext3 to ext4
      • Mounts
        • (Un)Mount /system
        • (Un)Mount /cache
        • (Un)Mount /data
        • (Un)Mount /sd-ext
        • (Un)Mount /sdcard
      • Other
        • Fix apk uid mismatches :: Does extacly that
        • Move recovery.log to SD :: Moves the recovery log file to your sdcard. (Use when you want more detailed recovery log information)
      • Power off :: Powers off your phone
    • Scripts available via adb :

    Install

    Pre-Requirements :
    • Root
    • Make sure that init.rc isn't calling any install-recovery.sh script, otherwise you'll boot back to stock recovery (exclamation mark with a little Android). More info on this here.

    via Rom Manager
    1. Download "Rom Manager" from the Android market
    2. Start "Rom Manager"
    3. Select "Flash ClockworkMod Recovery" and wait for it to finish
    4. Select "Flash Alternate Recovery" and wait for it to finish -> this will install the latest version of RA recovery.

    via fastboot
    Code: 
    Copy recovery-RA-passion-v2.2.1.img to a location where fastboot can find it.
Boot your phone into fastboot mode (power on while holding the trackball)
Connect your phone via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery-RA-passion-v2.2.1.img

    via terminal app
    Code: 
    Copy recovery-RA-passion-v2.2.1.img to the root of your sdcard
start the terminal app
su(press enter)
flash_image recovery /sdcard/recovery-RA-passion-v2.2.1.img(press enter)
reboot recovery(press enter)

    How to boot in Recovery Mode

    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.

    Download

    ALWAYS check the md5sum to make sure the zip isn't corrupted.

    Latest version :

    Previous versions :

    Change-log :

    v2.2.1
    • Nandroid backup is now selective, boot/system/cache/data are selected by default.
    • Nandroid checks if there's at least 500MB free on SDcard before starting a backup.
    • Added/updated error/warning messages.

    v2.1.1
    • Fixed ext4 support in kernel! Update from v2.x if you are using sd-ext!

    v2.1.0
    • Reduced recovery size by 800kb so it fits any hboot version to date :
      • Set Kernel compression mode to LZMA (33% smaller kernel)
      • Switched kernel debugging off
      • Removed : Networking support - Bluetooth subsystem support
      • Removed : Device Drivers - Misc device - AKM8973 Compass Driver
      • Removed : Device Drivers - Misc device - A1026 Voice Processor Driver
      • Removed : Device Drivers - Multimedia support
      • Removed : Device Drivers - MSM 3D Graphics driver for Adreno class GPU's
    • Nandroid now backups the entire content of /sd-ext , not just the apps. This fixes bootloops of certain restored roms.
    • Moved the "Toggle signature verification"-option from the Other- to the main flash-submenu.
    • Re-ordered the wipe menu.

    v2.0.0
    Some things in v2.0.0 were kanged with a twist from the Clockworkmod recovery.
    • Updated kernel to 2.6.35 (SLCD and AMOLED are now both supported).
    • Added SDEXT support for update scripts.
    • Added "filebrowser" support when you select a zip to flash.
    • Added "/.." support to the filebrowser so you can navigate up.
    • Added a mount menu so you can manually (u)mount stuff.
    • Added a toggle verification switch so you can flash those awesome unsigned winrar rom releases...
    • Fully re-wrote the wipe menu (it's not using a script anymore), added a few new wipe options.
    • Added "/sdcard/.android_secure" support , nandroid now backups/restores .android_secure (Froyo a2sd apps) by default.
    • Added a few new Google apps to the Google app backup script.

    Special thanks to :
    • packetlss for all the hours of support and awesome coding skills, THANKS man ^^, donate to Haiti
    • Koushik Dutta for all his recovery work ^^
    • Cyanogen for his dedicated work! , buy him a beer!
    • Chris Soyars for the new Apps2SD method ^^
    • JesusFreke for his awesome JFv1.43's recovery , donate
    • pensive for adding awesome features to Nandroid :)
    • Bkmo for his utility script!
    • Devsk for his switchrom script!
    • 51dusty for his sdparted script!
    • k4str0 for his fix_permissions v2.03 update.
    • Devsk, Dumfuq, Overground for creating BART :D
    • rikupw for the ideas and toggle_ums script.
    • http://www.androidspin.com for hosting ^^
    View
    6
    Amon_RA
    Amon_RA
    [Recovery] [27-Dec-2010] RA-nexus-v2.1.1

    Reserved for future use
    View
    6
    crachel
    crachel
    loof13 said:
    The site is down! Can someone upload the file again??
    Click to expand...
    Click to collapse

    See attachment
    View
    4
    Amon_RA
    Amon_RA
    updated to v2.2.1

    Change-log :

    v2.2.1
    • Nandroid backup is now selective, boot/system/cache/data are selected by default.
    • Nandroid checks if there's at least 500MB free on SDcard before starting a backup.
    • Added/updated error/warning messages.
    View
    4
    Amon_RA
    Amon_RA
    updated to v2.1.1

    Changelog : v2.1.1
    • Fixed ext4 support in kernel! Update from v2.x if you are using sd-ext!
    View

New posts