• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

quick question (possibly dumb)...

Thanks to ccapasso for the following:

Option A:
1. Use Kitchen (I didn't but I think it says it can do it)

or

Option B:
1. Mount your SD card, put the 1.6.2 img on your SD card. Unmount your SD Card.
2. Make sure SD Card is unmounted and USB Debugging Is enabled
3. Open a command prompt, and cd to your android-sdk-windows/tools directory
4. Issue the following commands (press enter after each)

adb remount
adb shell
cd /sdcard/
flash_image recovery recovery-RA-heroc-v1.6.2.img

After those commands, make sure it flashes successfully (It will return to the # sign). When I did mine, I kept getting the out of memory error. To fix this I simply unplugged the phone, and repeated my steps. Do not reboot the phone until the img successfully flashes.

After you get it successfully flashed, you will issue the following command

reboot recovery

That should take your into RA

I keep getting the out of memory error, too. I start the process over and over again, but no success. What I am noticing is that when I enter the cmd "adb remount" my phone disconnects from its sync with the pc. Should it be doing this? Also what will happen if I do reboot the phone? Any help would be appreciated.
 
flash_image: not found

So I back out, it tells me the files aren't there and they are, both in tools directory and the sdcard ROOT. What am I missing or doing wrong?

Thanks
:)

oh... and this is what I have loaded onto my phone... if it helps.
[ROM] Newest Sprint leak - RUU_Hero_C_Sprint_2.27.651.5_R_signed_release - xda-developers

I was having this problem, too. Then I realized that I had downloaded one of the RAs with a different color. Instead of the .img file ending in v1.6.2.img, it ended in v1.6.2-blue.img. You may have one of these files by accident. Just a thought.
 
I was having this problem, too. Then I realized that I had downloaded one of the RAs with a different color. Instead of the .img file ending in v1.6.2.img, it ended in v1.6.2-blue.img. You may have one of these files by accident. Just a thought.

Thanks JwPhilly for the help, but my situation was more complicated than a simple mistake. I appreciate your suggestions though as we all sometimes overlook the simple stuff ;)

I actually had lost my recovery console and couldn't re-flash the image (new r old) to attempt to replace it onto the phone. I couldn't get it onto the phone no matter what angle I tried, multiple times and ways. I haven't used linux and I used unix a long time ago but was a bit foggy with any commands there so I went to xda to ask for help. I kinda knew from the errors I was getting that the prevention of me pushing or flashing the file was due to folder/file permissions. With some help, my phone is ok with the recovery console restored! :)

Don't ask me what or how it happened, but it did and I am thankful for it to be fixed.

Happy Trails!
:cool:
 
Back
Top Bottom