Hi.
I am having problems flashing Amon_RA on my Nexus One.
I am currently running CWM 3.0.0.5 installed via ROM Manager, and i have switched back and forth between Amon_RA and CWM many many times before, using Rom Manager, but now it does not seem to work.
My phone is S-ON and running Newest MIUI Rom from MIUI.us.
I flashed from RA to CWM yesterday, and since that I have been sitting 6 hours trying to get RA back...
I did not find any working solutions searching the forums either, allthough more people seem to have the issue occationally.
Anyone have any idea how to fix this, or at least what's causing it??
I would be Very grateful!
Edit: In Rom Manager, after attemting to flash Ra, it sais the flash was successfull, and displays that Ra is installed, even after reboot, it tells me Ra is currently installed, but booting into recovery still brings up CWM...
Flash it from fastboot.
It works!
albundy2010 said:
Flash it from fastboot.
Click to expand...
Click to collapse
Tried, but did not work.
But, I EVENTUALLY FOUND A SOLUTION!
From here: http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Recovery_Images
For locked bootloader - flash_image using ADB only
Using "blind" flash_image method works for locked bootloaders, requires root and is sSLCD uitable for Nexus users that lost the ability to see their screen. Adapted from here.
Download Amon_RA's Recovery from one of the versions above - NOT INCLUDING 1.7.0.1 - to C:\.
Rename Amon_Ra's Recovery Image to simply recovery.img.
Download flash_image.zip and extract flash_image file to C:\.
Turn off the phone (possible by pulling the battery).
Press Volume Down + Power or Trackball + Power, the phone will boot into bootloader.
Select "BOOTLOADER", press Power.
Select "RECOVERY", press Power. The phone is working, but the screen shows nothing.
On the computer... Open a command prompt/terminal & navigate to the Android SDK Tools folder.
Type in the following commands:
Code:
adb shell
mount -o rw /system
mount -o rw /sdcard
exit
adb push C:\flash_image /system/bin/flash_image
adb push C:\recovery.img /sdcard/recovery.img
adb shell
chmod 755 /system/bin/flash_image
flash_image recovery /sdcard/recovery.img
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
reboot recovery
Click to expand...
Click to collapse
Now I wonder, Why did I suddenly have to use this method to flash, when i have flashed both RA and CWM using Rom Manager hundreds of times before???
Edit: The guide above is for SLCD N1, mine is a AmOLED N1, yet, it was the only method i found that actually worked... Strage :/
CWM 3.xxx has been known to fubar things up here and there.
Sent from my Transformer TF101 using Tapatalk
Related
hi i tried searching for this but couldnt really find anything on it. i tried updating to the cyanogen recovery.img 1.4 using terminal as the guide said here http://forum.xda-developers.com/showthread.php?t=533731, however now whenever i boot into recovery, the bootloader screen comes up instead. i have tried reflashing the recovery numerous times but the problem still persists. am i doing something wrong? any help would be great. thanks in advance
also i am rooted currently running JF 1.5 rom with latest radio and hard spl.
Put the recovery image on the SD card yourself. Get the file from here http://forum.xda-developers.com/showthread.php?t=523558
i have also tried that. once i placed the file on the sd card, i opened up terminal and typed in the command:
flash_image recovery /sdcard/cm-recovery-1.4.img
after i pressed enter nothing happend on screen, so i turned off the phone and tried to boot into recover, but the bootloader screen still appears. am i typing in the wrong command or something?
Do it again and this time wait for the # to appear again. Then type reboot and hold home button while it's booting. Should take you to Cyan's awesome recovery screen
Good luck
... Have you tried flashing it from fastboot like cyanogen recommended if you ran into any issues?
djosiah said:
i have also tried that. once i placed the file on the sd card, i opened up terminal and typed in the command:
flash_image recovery /sdcard/cm-recovery-1.4.img
after i pressed enter nothing happend on screen, so i turned off the phone and tried to boot into recover, but the bootloader screen still appears. am i typing in the wrong command or something?
Click to expand...
Click to collapse
After you open the terminal, did you type "su"?
billquinn1 said:
After you open the terminal, did you type "su"?
Click to expand...
Click to collapse
yeah i did type in su. i have been away for a few days so i ma going to try the suggestions mentioned. and no i havent tried doing it using fastboot as i havent got adb set up yet. i will also try that later. thanks for the suggestions.
I have the same problem. When holding power+home, it flashes t-mobile G1, then the screen disintegrates and it reboots a couple times, finally stopping on a blank black screen.
I have no problem booting straight into the O.S., I've just lost my recovery.
I've done this before and it worked, but I recently had a catastrophic failure and had to start from scratch.
If all else fails or you don't fell like using adb, should be fine if you downgrade and re-root, etc.... unless there is something else messing up your recovery partition.
Put the recovery.img file on the root of your sdcard
Then try:
Code:
mount -o remount,rw /dev/block/mtdblock3 /system
cd /system
cat /sdcard/recovery.img > recovery.img
flash_image recovery recovery.img
I've gone from JF 1.5ADP to Modaco using the cyanogen 1.4 recovery without any problems.
when you flash using terminal, you need to wait till you get the # back, and then restart the phone
which recovery image were you previously using as I was using JF 1.43 recovery
djosiah said:
hi i tried searching for this but couldnt really find anything on it. i tried updating to the cyanogen recovery.img 1.4 using terminal as the guide said here http://forum.xda-developers.com/showthread.php?t=533731, however now whenever i boot into recovery, the bootloader screen comes up instead. i have tried reflashing the recovery numerous times but the problem still persists. am i doing something wrong? any help would be great. thanks in advance
also i am rooted currently running JF 1.5 rom with latest radio and hard spl.
Click to expand...
Click to collapse
Hi djosiah
did you read this post ?
http://forum.xda-developers.com/showthread.php?p=4569666#post4569666
(Please substitude by the file name "update-cm-4.0.4-signed.zip" by "cm-recovery-1.4.img" in my post - sorry, I was misaken as to the file name ...!!)
My problem was a corrupted cm-recovery-1.4.img (a few thousand bytes of the MBs were missing ...!) A new downloaded cm-recovery-1.4.img (from another URL) solved the problem finally. The rest was cream - totally happy now.
Good luck!
My problem was solved.
Unroot the phone
reformat sd card using gparted live cd to fat32
redo root
flash new radio
flash new spl
flash cyanogen rom
flash cyanogen recovery
tada
Hi,
I have a T-Mobile G1.
It was in Android 1.5 when I received it.
I rooted it woth the "one click" method (flashrec 1.1.2) using recovery-RA-dream-v1.2.2.img.
It worked fine, and I was able to test some ROMS.
But the last one I installed, Android 1.6 User debug from HTC, doesn't allow to get root access again.
The one click method doesn't work anymore. I get "Could not run command".
The Fastboot method doens't work anymore too.
I'm stuck with the 1.6 "Android dev phone 1".
Anyone has an idea ?
Thanks,
Yves
yvesg said:
Hi,
I have a T-Mobile G1.
It was in Android 1.5 when I received it.
I rooted it woth the "one click" method (flashrec 1.1.2) using recovery-RA-dream-v1.2.2.img.
It worked fine, and I was able to test some ROMS.
But the last one I installed, Android 1.6 User debug from HTC, doesn't allow to get root access again.
The one click method doesn't work anymore. I get "Could not run command".
The Fastboot method doens't work anymore too.
I'm stuck with the 1.6 "Android dev phone 1".
Anyone has an idea ?
Thanks,
Yves
Click to expand...
Click to collapse
if i remember right the 1 click root only works with 1.5 and wont work with 1.6 . if you made a nandroid back up before you flash the 1.6 i think you can restore from there to get root .read threw the thread on 1.6 i think there was some mention of this !
yvesg said:
It worked fine, and I was able to test some ROMS.
But the last one I installed, Android 1.6 User debug from HTC, doesn't allow to get root access again.
The Fastboot method doens't work anymore too.
I'm stuck with the 1.6 "Android dev phone 1".
Click to expand...
Click to collapse
I think you have still root. Do you have adb installed?
Try this one:
Code:
adb root
adb shell
Now you should get the root-prompt ("#").
The reason why you can't flash any other rom anymore is because the recovery-img operates with wrong keys (that's what I think).
What you could do now is to reflash the recovery by using the flash_image command (you have to copy the flash-image-binary on your phone first - extract it from any other rom - it's located in /system/bin).
So, copy the flash_image binary to your phone:
Code:
adb remount
adb push flash_image /system/bin/.
adb shell chmod 0755 /system/bin/flash_image
Now copy the recovery-image you want on your phone:
Code:
adb push recovery.img /sdcard/.
Flash the recovery:
Code:
adb root
adb shell flash_image recovery /sdcard/recovery.img
Now ... boot into recovery-mode ([power]+[home]) and reflash your phone with whatever you like. Since fastboot doesn't work for you I guess you have never replaced the original SPL.
And ... what I've heard ... the ADP1.6-firmware will check the recovery on boot and will reflash it every time!
You could also check this site.
lucky 69 said:
if i remember right the 1 click root only works with 1.5 and wont work with 1.6 . if you made a nandroid back up before you flash the 1.6 i think you can restore from there to get root .read threw the thread on 1.6 i think there was some mention of this !
Click to expand...
Click to collapse
I ashamed, but I didn't do the backup :-( .....
yvesg said:
I ashamed, but I didn't do the backup :-( .....
Click to expand...
Click to collapse
Try what Harry wrote.
harry_m said:
I think you have still root. Do you have adb installed?
Try this one:
Code:
adb root
adb shell
Now you should get the root-prompt ("#").
The reason why you can't flash any other rom anymore is because the recovery-img operates with wrong keys (that's what I think).
What you could do now is to reflash the recovery by using the flash_image command (you have to copy the flash-image-binary on your phone first - extract it from any other rom - it's located in /system/bin).
So, copy the flash_image binary to your phone:
Code:
adb remount
adb push flash_image /system/bin/.
adb shell chmod 0755 /system/bin/flash_image
Now copy the recovery-image you want on your phone:
Code:
adb push recovery.img /sdcard/.
Flash the recovery:
Code:
adb root
adb shell flash_image recovery /sdcard/recovery.img
Now ... boot into recovery-mode ([power]+[home]) and reflash your phone with whatever you like. Since fastboot doesn't work for you I guess you have never replaced the original SPL.
And ... what I've heard ... the ADP1.6-firmware will check the recovery on boot and will reflash it every time!
You could also check this site.
Click to expand...
Click to collapse
Hi,
Thanks a lot.
I'm now able to get root access and I'm about to flash the G1.
I thaught I replaced the SPL, but I'm not sure .... I've tried so much things since I have this phone (since last sunday) .....
Again, thank you for your help.
Yves
ooops,
"Installation aborted", during the apply of update.zip.
Now the phone is bricked.
I'm going to format my sdcard and retry the flash ....
Same error :
(No such file or directory)
E:Failure at line 80:
set_perm_recursive 0 2000 0755 06755 SYSTEM:xbin
Installation aborted.
redownload the rom
Spon4ik said:
redownload the rom
Click to expand...
Click to collapse
Meanwhile, I try with another rom and it seems to work ....
Thanks again for your help.
In fact, I can only flash with HTC SIGNED roms .....
I tried several others and each crash the same way
If you ask me ... the above mentioned error
Code:
E:Failure at line 80:
set_perm_recursive 0 2000 0755 06755 SYSTEM:xbin
has nothing to do with a wrong-signed rom!
SPL
yvesg said:
In fact, I can only flash with HTC SIGNED roms .....
I tried several others and each crash the same way
Click to expand...
Click to collapse
would this have to do with the SPL? similar to not being able to flash a EUR ROM on a USA phone .. you have to flash the HardSPL etc in order to switch ROMs
Or you could just gain root access manually the way those of us who had RC30 did...
You are may be right about the HardSPL.
When I try to flash it, (with Camera + Power), I get "not allow".
Hi guys,
I have to send me N1 to htc for fix some problem.
I have RA recovery with lock bootloader, and I want to flash the original, but "fastboot" way doesen't work (signature fail ).
How can i flash it in other way?
Ty
(sry for my eng )
Just flash the stock rom with the recovery image like frf92 original.
evilkorn said:
Just flash the stock rom with the recovery image like frf92 original.
Click to expand...
Click to collapse
How? Through recovery? Because "fastboot" hates me, and won't work.
I'd suggest using a passimg for frf85b and then maybe updating to 91 (or just leave it at 85), you can always re-root when you get it back.
________________________
N1 w/ XDA App
got it, thk to cyanogen wiki
Plug the phone into the computer
Reboot into fastboot by holding TrackBall + Power (you should see three Androids on skateboards and the words 'fastboot USB' in red)
On the computer, open a command prompt cd to the sdk/tools directory (we will assume the SDK is located in C:\android-sdk and the recovery file is in the root of the sdk/tools directory for the following steps)
With the phone connect via USB, open up a cmd prompt
Code:
adb reboot recovery"
Code:
adb devices
A device name and 'recovery' should be returned
Code:
adb push recovery.img /sdcard/recovery.img
recovery.img is located on android-sdk/tools dir
Code:
adb shell flash_image recovery /sdcard/recovery.img
This permanently flashes the recovery.img to your phone, you can now boot into it by holding Vol- while powering on the device
Reboot
nrdmtt said:
got it, thk to cyanogen wiki
Click to expand...
Click to collapse
Thanks for searching!
I hope this encourages other users new to ADB, flashing ROMs, etc. to continue to search after asking for help.
Way to go nrdmtt!!
After I got my nexus back from HTC for a faulty power button, my nexus has been rooted via a replaced motherboard. Now I have already root my phone and unlocked the bootloader, however when I try to flash the recovery image I get
sending 'recovery' (4074 KB)... OKAY
writing 'recovery'... FAILED (remote: image update error)
Also I can somehow access recovery, and it looks as it should. However when I try to backup my rom it says "Run 'nandroid-moblie.sh' via adb!" and similar things when I try any other the other options. Could someone please help with this?
How are you trying to flash it? Fastboot is the best foolproof way to do flash the recovery. I have never really seen that error before, what recovery are you trying to flash?
Your nandroid error is most likely because the sdcard thinks it's still mounted, or is mounted. Also, I don't know if this still happens but make sure you only do a backup, not backup +ext if you don't have an ext partition on the sdcard.
he's obviously using fastboot...
Did you make sure recovery.img had the right MD5 hashes as amon_ra posted?
I have check the MD5 checksums, and they match up. Also, i am using fastboot to flash, and I am trying to flash RA-nexus v2.0.0. Are you suggesting that I remount the sd card to get it to flash the recovery image?
cajer said:
I have check the MD5 checksums, and they match up. Also, i am using fastboot to flash, and I am trying to flash RA-nexus v2.0.0. Are you suggesting that I remount the sd card to get it to flash the recovery image?
Click to expand...
Click to collapse
I would suggest you try in command line with the adb commands as follows:
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
You need flash_image for this, check the wiki for the file...don't forget to put the recovery in the root of the sdcard and rename it to recovery.img for convenience purpose
gravufo said:
I would suggest you try in command line with the adb commands as follows:
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
You need flash_image for this, check the wiki for the file...don't forget to put the recovery in the root of the sdcard and rename it to recovery.img for convenience purpose
Click to expand...
Click to collapse
What do I do with flash_image? Also this device came back stock with frg 83, which I am trying to flash the recovery on. When I type in adb shell, I get "error: device not found" even though I can see it through "fastboot devices".
cajer said:
What do I do with flash_image? Also this device came back stock with frg 83, which I am trying to flash the recovery on. When I type in adb shell, I get "error: device not found" even though I can see it through "fastboot devices".
Click to expand...
Click to collapse
flash image has to be placed in the root of your sd card as well as the recovery!
As for the adb shell, try enabling USB Debugging in Setting > Applications > Development
Make sure you're rooted too (use SuperOneClick if you're not already)
I can get through that string of commands until
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
reboot recovery
Then it says "No such file or directory". I have already rooted, and both the flash_image and recovery file have been placed in the root directory of the sd card.
Well, after you did that string of commands, does the problem persist?
Also, do you have at least 400MB free on your SD card?
Well, I can't get
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
reboot recovery
to work as it responds with "No such file or directory". Even if I go through after the errors, the recovery still gives 'nandroid-moblie.sh' via adb!" and similar messages. Do I need to find a way to put the file install-recovery.sh in my sd card root directory if so, where can I get it? In addition when I try to flash recovery with nexus one superboot I get "(remote: signature verify fail)" even though the MD5 sum matches up.
Yes I have over 5 gbs on the sd card.
rm = remove
The steps you are trying to perform with the 2 rm command is to remove the 2 files that automatically rewrite your recovery.
If you reboot without succeeding in removing these files, the recovery image you just flashed will be written over by the stock recovery...
Since you have rebooted, and are still having the problem, you need to do the whole list of commands again... be careful how you type...
Sent from my Nexus One using XDA App
Danger, it seems as I can't remove those two files as I get the error message "rm failed for /system/etc/install-recovery.sh, No such file or directory". Any ways to successfully remove them?
Sounds like the files aren't actually there then, unless you're making a typing error...
Did your recovery update after the last attempt? Did it look different, what is the recovery version that is listed on the recovery screen?
Sent from my Nexus One using XDA App
I have been flashing different themed recoveries to see if any data transfers, and the background changes. But as before the actions all say "Run 'nandroid-moblie.sh' via adb!" or something similar.
cajer said:
I have been flashing different themed recoveries to see if any data transfers, and the background changes. But as before the actions all say "Run 'nandroid-moblie.sh' via adb!" or something similar.
Click to expand...
Click to collapse
if the rm doesn't work it's fine.
But what about your flashing command? It simply works or outputs an error too?
When u flashed themed ones, did the background change?
The background did change when I flashed the themed ones, however it still outputs errors like "Run 'nandroid-moblie.sh' via adb!" when i try to run any of the options under recovery. The fastboot flashing command gives this "writing 'recovery'... FAILED (remote: image update error)" error.
cajer said:
The background did change when I flashed the themed ones, however it still outputs errors like "Run 'nandroid-moblie.sh' via adb!" when i try to run any of the options under recovery. The fastboot flashing command gives this "writing 'recovery'... FAILED (remote: image update error)" error.
Click to expand...
Click to collapse
When you try running a NAND backup or restore a previous NAND?
When restoring, the backup must be at the exact position where it was when you did it: /sdcard/nandroid/HT#####/BCD######
I was trying to backup my current image, and this happens with all other actions even the shut down action on the recovery page just with "Run 'reboot -p' via adb!"
lawl xD that seems useful...
well, that's extremely odd to be honest...uhm...I think you should try and contact amon_ra if possible...He knows the code of his recovery and might know what's wrong...
I really have no clue, sorry =\
PS: Have u tried clockworkmod recovery?
Alright I will try contacting amon_ra, and I will try clockwork tomorrow. I was going for amon_ra recovery to get Sense HD on it with sd partition. Thanks for the help though I learned more stuff about my phone.
EDIT: Wow, clockwork installed like a charm, and I didn't even have to do anything. I'm now a clockwork convert.
somehow i screwed up my recovery. i'm running ads-magpie with no problems. I need to get my recovery working again. either amon-ra or clockwork. in adb shell i type: flash_image recovery /sdcard/recovery-RA-dream-v1.7.0.img It says /system/bin/sh: flash_image: not found
please help
if you are able to boot into the phone then go into your terminal app and then type:
su
mount /sdcard
flash_image recovery /sdcard/recovery-RA-dream-v1.7.0.img
and you're good to go...
still doesn't work?
then flash the recovery using a fastboot zip
newellj79 said:
somehow i screwed up my recovery. i'm running ads-magpie with no problems. I need to get my recovery working again. either amon-ra or clockwork. in adb shell i type: flash_image recovery /sdcard/recovery-RA-dream-v1.7.0.img It says /system/bin/sh: flash_image: not found
please help
Click to expand...
Click to collapse
Can you get into fastboot (hold down the camera button when you restart)? If so, then flash recovery image from there.
Open command prompt in directory where you have recovery image stored. Command:
fastboot flash recovery recovery-RA-dream-v1.7.0.img
yes but hopefully he has fastboot set up. if not then i'm sure we can walk you through or forward you to a tut on how to do so
I got it working, truth be told I don't how. I tried a command string that previously didn't work. It responded out if memory, twice. For kicks I tried boot into recovery and low and behold clockworkmod. thanks guys.
no problem anytime