Amon_Ra v2.0.0

[rugmankc]

not sure nick, wouldn't think so

think i saw a similar post on amon's thread and they recommended trying thru sdk, but i think that needs bootloader ulnocked



ken

[card0124]

I worked the USB problem but I'm using clockwork now. I'm not sure why but I flashed rodriguzstyles miui and it switched me from amon to clockwork.

[rugmankc]

if you had amon 2.0.0 and just flashed Rod's MIUI it won't change recoveries unless you flashed thru rom mgr and and flashed cwmod before booting into recovery and wiping and installing new rom.

[card0124]

I have no idea how it happened. I never use rom manager, and i didn't reflash clockwork it just kinda popped back up. I don't really mind it works just the same, I was just curious as to how it happened.

[rugmankc]

Beats me

[nickshertzer]

not sure nick, wouldn't think so

think i saw a similar post on amon's thread and they recommended trying thru sdk, but i think that needs bootloader ulnocked



ken

Hi ken,

Fastboot commands through sdk requires unlocked bootloader. Grrr... There has to be a way around this. I'm not too concerned right now, because I don't NEED it for anything.

I have no idea how it happened. I never use rom manager, and i didn't reflash clockwork it just kinda popped back up. I don't really mind it works just the same, I was just curious as to how it happened.

Hi Card,
From XDA OP:

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

I know you're booting back to CW and not stock, but might be related.

[rugmankc]

Nick,

Reading on amon's thread that you don't need bl unlocked for using command prompt. But, may want to confirm exact commands to use.


Ken

[guirufo13]

When I type reboot and press enter I always get #not permitted. I think I will give up because clockwork runs perfect so I will leave as is.
Any way,thanks for the help!!!!

Paul

What commands are you using. Some have had Terminal issues, if so go thru fastboot (sdk/adb)


Try this first in Terminal:



$su
#flash_image recovery /sdcard/recovery-RA-nexus-v2.0.0-CM.img <enter>
#reboot



space before the first / no space after second /

after phone reboots then reboot into recovery to verify change

the CM is cyanogen's version as opposed to stock, like colors better

[rugmankc]

Well, you don't have to type reboot, you can just back out of screen and reboot on your own.

Do you have the # on the screen before typing reboot. If not type SU again.



Good Luck,


ken

[rugmankc]

not sure nick, wouldn't think so

think i saw a similar post on amon's thread and they recommended trying thru sdk, but i think that needs bootloader ulnocked



ken

Hi ken,

Fastboot commands through sdk requires unlocked bootloader. Grrr... There has to be a way around this. I'm not too concerned right now, because I don't NEED it for anything.

I have no idea how it happened. I never use rom manager, and i didn't reflash clockwork it just kinda popped back up. I don't really mind it works just the same, I was just curious as to how it happened.

Hi Card,
From XDA OP:

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

I know you're booting back to CW and not stock, but might be related.

Nick,

You can flash recoveries in SDK with ADB and a locked bootloader using flash_image.zip file on your pc C: drive and the flash_image command. I am rooted/unlocked so use fastboot and set up SDK that way. I think you need to install or extract it to your android sdk folder and use flash_image recovery--- as opposed to fastboot recovery----

Not good on all the exact commands and procedures.


Ken