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.
Related
HTML:
C:\Superboot>fastboot-windows flash recovery recovery-RA-nexus-v1.7.0.1-cyan.img
sending 'recovery' (3962 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
what am i doing wrong?
i just rooted my nexus one without unlocking following "[Tutorial] Root Without Unlocking"
im trying to flash a custom recovery image so i can load a custom rom
and should i use the Normal recovery image or the CyanogenMOD version?
Just after rooting stock FRF91, while having rw in /system, you should rename the file /system/etc/install-recovery.sh (to smth like /system/etc/BKP_install-recovery.sh). This script is responsible for resetting the recovery, but with changing the name you ommit this.
After that install Amon RA's or Clockwork Recovery and you can flash whatever ROM you want.
Regarding which recovery to use, AFAIK there isn't much difference between normal Amon RA's & Cyanogen version. I've used both & they work fine.
Of course don't forget to do a nandroid backup of your stock system just in case .
Good luck!
You can't use fastboot to flash custom recovery when the bootloader is locked.
Use flash_image from Terminal Emulator or ADB.
Normal and Cyanogen differ only by colors.
+1 to Jack_R1 !
Forgot to mention that, after rooting your stock FRF91, you indeed need to copy flash_image to /system (/system/bin i think) as well (don't forget to make it executable!). Of course this again needs to be done while still have rw-access to /system
i followed the tutorial more for flashing a custom recovery and then this happened
HTML:
cd /data/local/tmp
chmod 755 flash_image
./flash_image recovery /sdcard/recovery-RA-nexus-v1.7.0.1-cyan.img
rm /system/etc/install-recovery.sh
rm failed for /system/etc/install-recovery.sh, Read-only file system
i cant seem to find how to rename the file to "BKP_install-recovery.sh"
would this fix the problem?
also i put flash_image into SDK tools but how to you acess /system and put it in there?
Use adb or Root Explorer.
"adb remount" will make the system partition read-write.
Root Explorer has a button for that.
thanks for everyones help but i took the easy way out and used ROM manager and it worked perfectly
this guide is for those who still have Clockwork Mod Recovery still on device you can thank bogdi1988 for his work and orginal guide here :
http://forum.xda-developers.com/showpost.php?p=12185475&postcount=76
BUT THIS MAY WORK FOR OTHERS IF YOU KNOW HOW TO MOUNT SYSTEM AND DATA AND THOSE THINGS FROM ADB
but to simplify I did this :
stock images
recovery.img
http://dl.dropbox.com/u/2252176/recovery.img
boot.img
http://dl.dropbox.com/u/2252176/boot.img
Once in recovery mount everything you can system , data , cache , everyrthing besides sd card
then go into command prompt and type adb shell make sure its working if you still have root it will show # if not it will show $ I believe no biggie as long as it picks up in shell.
then type : flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
then type : flash_image /dev/block/mmcblk3p1 /sdcard/recovery_orig.img
select reboot from the recovery. now it will reboot and it will format misc and it will reboot again.
bogdi1988 suggest flash all images over again in fastboot
in this order
system.img
recovery.img
boot.img
thanks go to everyone who has a dell streak 7 that was willing to try all these hacks and risking your devices for the greater good of the streak
P.S. I will post system.img in a second
Also for fastboot help thank bogdi1988 again heres his post that helped me
http://forum.xda-developers.com/showpost.php?p=11929063&postcount=23
I have read and tried everything
I attempted the adb method but can't get into fastboot... I believe I got the adb commands correct and I don't get an error but my the restore is not taking... at the reboot it goes right back into CWM 3.0.2.0 here's my adb shell read out...
C:\android\platform-tools>adb shell
~ #
C:\android\platform-tools>adb shell
~ # flash_image /dev/block/mmcblk3p2/sdcard/boot_orig.img
flash_image /dev/block/mmcblk3p2/sdcard/boot_orig.img
usage: flash_image partition file.img
~ # flash_image /dev/block/mmcblk3p1/sdcard/recovery_orig.img
flash_image /dev/block/mmcblk3p1/sdcard/recovery_orig.img
usage: flash_image partition file.img
~ #
I don't know what else to do, I can't find a thread that stays on track long enough to follow this issue all the way thru... please help... I have read and tried everything, i can't find a clear set of alternatives... am i missing a step?
ya, i'm stuck in the same situation. I either get a "error -1" or it says "usage: flash_image partition file.img"
does getting "usage: flash_image partition file.img" mean the file was successfully flashed?
dfspot said:
I attempted the adb method but can't get into fastboot... I believe I got the adb commands correct and I don't get an error but my the restore is not taking... at the reboot it goes right back into CWM 3.0.2.0 here's my adb shell read out...
C:\android\platform-tools>adb shell
~ #
C:\android\platform-tools>adb shell
~ # flash_image /dev/block/mmcblk3p2/sdcard/boot_orig.img
flash_image /dev/block/mmcblk3p2/sdcard/boot_orig.img
usage: flash_image partition file.img
~ # flash_image /dev/block/mmcblk3p1/sdcard/recovery_orig.img
flash_image /dev/block/mmcblk3p1/sdcard/recovery_orig.img
usage: flash_image partition file.img
~ #
I don't know what else to do, I can't find a thread that stays on track long enough to follow this issue all the way thru... please help... I have read and tried everything, i can't find a clear set of alternatives... am i missing a step?
Click to expand...
Click to collapse
You are missing the space between mmcblk3pX and /sdcard.
ok, thats what i thought. when i do it the other way i get the "failed with Error: -1" any ideas on that. also if i send it back to t-mobile under the warranty, they won't send it back as damaged since i had CMW installed o it will they?
thatruth132 said:
this guide is for those who still have Clockwork Mod Recovery still on device you can thank bogdi1988 for his work and orginal guide here :
http://forum.xda-developers.com/showpost.php?p=12185475&postcount=76
BUT THIS MAY WORK FOR OTHERS IF YOU KNOW HOW TO MOUNT SYSTEM AND DATA AND THOSE THINGS FROM ADB
but to simplify I did this :
stock images
recovery.img
http://dl.dropbox.com/u/2252176/recovery.img
boot.img
http://dl.dropbox.com/u/2252176/boot.img
Once in recovery mount everything you can system , data , cache , everyrthing besides sd card
then go into command prompt and type adb shell make sure its working if you still have root it will show # if not it will show $ I believe no biggie as long as it picks up in shell.
then type : flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
then type : flash_image /dev/block/mmcblk3p1 /sdcard/recovery_orig.img
select reboot from the recovery. now it will reboot and it will format misc and it will reboot again.
bogdi1988 suggest flash all images over again in fastboot
in this order
system.img
recovery.img
boot.img
thanks go to everyone who has a dell streak 7 that was willing to try all these hacks and risking your devices for the greater good of the streak
P.S. I will post system.img in a second
Also for fastboot help thank bogdi1988 again heres his post that helped me
http://forum.xda-developers.com/showpost.php?p=11929063&postcount=23
Click to expand...
Click to collapse
great how to
white99 said:
ok, thats what i thought. when i do it the other way i get the "failed with Error: -1" any ideas on that. also if i send it back to t-mobile under the warranty, they won't send it back as damaged since i had CMW installed o it will they?
Click to expand...
Click to collapse
humz mine wont flash at all
Guys,
If someone can help people struck here like me, it would be great.. i get the same -1 error message... when i run the second command. the first one passes through and i get a # for flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img.
When we downloaded the file boot.img, how would boot_orig.img work? am i missing something?
The second command throws me an error..
Guys really waiting for help... bricked my streak in hours after i brought it..
where are you at in la
I need a little bit of help for an ex-ipohone user
Hey guys sorry to ask u a noob question, but can anyone give me an ideea how to remove/unistall CWM Recovery so i can send back my Streak 7 for repair? I have installed CWM thru fastboot an i am currently on stock 2.2.2 rom. Or if there is a thread that i didnt find please a little help would be much apreciated.
i have figured it out eventualy after 20 hrs of brain scratching ived used NVflash and worked fast and easy
thatruth132 said:
this guide is for those who still have Clockwork Mod Recovery still on device you can thank bogdi1988 for his work and orginal guide here :
http://forum.xda-developers.com/showpost.php?p=12185475&postcount=76
BUT THIS MAY WORK FOR OTHERS IF YOU KNOW HOW TO MOUNT SYSTEM AND DATA AND THOSE THINGS FROM ADB
but to simplify I did this :
stock images
recovery.img
http://dl.dropbox.com/u/2252176/recovery.img
boot.img
http://dl.dropbox.com/u/2252176/boot.img
Once in recovery mount everything you can system , data , cache , everyrthing besides sd card
then go into command prompt and type adb shell make sure its working if you still have root it will show # if not it will show $ I believe no biggie as long as it picks up in shell.
then type : flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
then type : flash_image /dev/block/mmcblk3p1 /sdcard/recovery_orig.img
select reboot from the recovery. now it will reboot and it will format misc and it will reboot again.
bogdi1988 suggest flash all images over again in fastboot
in this order
system.img
recovery.img
boot.img
thanks go to everyone who has a dell streak 7 that was willing to try all these hacks and risking your devices for the greater good of the streak
P.S. I will post system.img in a second
Also for fastboot help thank bogdi1988 again heres his post that helped me
http://forum.xda-developers.com/showpost.php?p=11929063&postcount=23
Click to expand...
Click to collapse
OMFG I would so kiss you right now. I was stuck where I could only load up CWR and nothing else was working. You are my hero. *sigh*
No biggie just hit that thanks.button
Sent from my Dell Streak 7 using XDA Premium App
The links are down, any mirrors?
Same need files links re not working
IMG Reposted?
Hi Folks,
A couple of people have posted that the boot, recovery, and system image links respond with a "404 not found" error. This is still the case.
I recall reading somewhere else that the images may still live on the SD card on the device. If this is true does someone know where in the file structure they may be?
If not, does anyone know where to obtain the images?
Currently I'm in CWM reboot hades on my Dell Streak 7. Tried the Dell OTA update for Honeycomb...didn't know that was a BAD thing until it was too late.
I've tried flashing boot and recovery images from a backup I'd made earlier, but no luck, so thatruth's excellent guide here: http://forum.xda-developers.com/show....php?t=1006829 doesn't help much...unless I can get the recovery and boot images.
So to reiterate:
I can get to CWM and clear the caches and flash a recovery.
I can communicate with the device via ADB and have flashed it with the backup images.
I can mount the internal SD card via CWM and my pc.
After flashing with the backup images, Fastboot still does not recognize that the device is connected, and the device does not apper to go through the 'format steps'.
Cheers,
L2
Found 'lightly modified' roms (thank you DJ Steve!) for a T-Mobile streak on another XDA thread. Flashed using adb, and tadaaaa, it booted! sliiiight problem. Will not boot into recovery and no wireless.
Managed to install rom manager (AKA ClockWorkMod) via ADB but CWM wan't an internet connection to install the recovery rom. grrrrr.
One of the other modifications (aside from root) by DJ Steve is the installation of 'BusyBox', This actually seems to complicate things for me because I don't really know how to issue ADB commands from the BusyBox shell. I get a lot of 'invalid command' and the like... I was able to install CWM OUTSIDE the adb shell (adb install rommanager) but once I'm in the shell (adb shell)I don't know how to issue the proper commands.
What I want to do is either remove busybox, or use ADB inside busybox to flash the CWM recovery rom, then flash my backup roms. (and hopefully return to full functionality.)
Any suggestions on how to use ADB commands inside of busy box to flash a rom?
Can anyone upload the stock rom images? I need to flash back to stock :\
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
When i type the dd if=/data/recovery.img of=/block/mmcblk0p6 bs=4096 to flash over the clockworkmod, into my command promt it says 'cannot open for read: No such file or directory' and i dont know what im doing wrong.
I mean everything else seemed to workout fine. i downloaded the recovery image it said to save it but it was already saved to my computer after i downloaded it so i dont know if this could be the problem.
Then i used the adb push recovery.img/data command to push the recovery image to my phone, i think this might be where i messed up. After i put in the command a long list of text pops up on the command prompt. It starts out showing 'Android Debug Bridge version 1.0.26' then is followed by a long list of adb commands. Idk know if this is what its supposed to show.
Next i did the adb shell, su, dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096 command and that worked fine it said 2560+0 records out, 2560+0 records in 10485760 bites transfered in 0.413 secs and i actually found that file on my sdcard. So i think i did that right.
Next i tried to use the command 'dd if=/data/recovery.img of=/block/mmcblk0p6 bs=4096' and like i said earlier it just says 'cannot open for read: No such file or directory'
Lastly i tried the rm /data/recovery.img command and it said rm failed for /data/recovery.img, No such file or directory in the command prompt.
Im sorry i am new at this but i thought i followed the directions perfectly and any help anyone could give me would be greatly appreciated.
First off, before someone else says it, you shouldn't start a new thread for something we already have a topic for. But anyways,
Sounds to me like recovery.img never got pushed to /data. Not sure if its a typo in your post but 'adb push recover.img/data' should be 'adb push recovery.img /data'. The space is important. On your phone use a root file explorer and go to your /data partition and see if recovery.img is there. You may need to either change permissions for /data or just put recovery.img on your sdcard and move it to /data with a root explorer.
Sent from my LG-P925 using Tapatalk
Well im sorry im new to this kind of thing, i didnt want to make anyone mad i just wanted some help and i apologize if ive ticked somone off. How would i change the permissions for the data? And could you tell me how to use the root explorer to put the recovery image in the right place? Again i appreciate any help you can offer.
Is recover.img in the same folder as adb? Because the instructions assume your recovery.img is in the same folder you are working from. So if you have to cd to your adb folder to use adb then recovery.img should be in that folder as well. Look at your cmd window, whatever directory/ folder it says you are in that is where you should put recovery.img.
If you saw a bunch of commands it means the .img did not go through your command did not work. You dont have the recovery.img in /data either put the file on your sdcard and use a root explorer to move it to /data or try the adb push again, you most likely made a typo or something.
You would put recovery.img on your sdcard through your computer. Open root explorer and navigate to your sdcard, long press on the recovery.img select move, go to/ data on the root of the phone, not the one on either sdcard it MUST be /data not /mnt/sdcard/data or anything like that once there paste file to /data and finish up in adb shell.
Alright i copied the recovery image to the /data folder and finished up in command prompt and everything worked out like it was supposed to. what was i supposed to do next to put it into cwm recovery mode? I held power, volume down, 3d button but i just went into normal recovery mode. then i went to rom manager to try and put it into cwm recovery that way but it just rebooted my phone. And when i went back into the /data folder i couldnt find the recovery image there anymore and i did a search on my root explorer and couldnt find it anywhere.
Hold vol down + 3D + power when lg logo appears release power but keep vol down +3D held down until recovery pops up. If you still don't boot into cwm try flashing recovery.img again. Do NOT use rom manager at all to install cwm on this phone.
Well ive tried to take the recovery image from the sd card to the /data folder but when i run 'rm /data/recovery.img' on the command prompt then reboot my phone, i turn it off then try and put it in recovery mode but its just regular recovery mode not cwm recovery mode. And everytime i run the 'rm /data/recovery.img' when my phone boots back up the recovery image is no longer in the /data folder or anywhere. But if i dont run the 'rm /data/recovery.img' after moving the recovery image to the /data folder it stays in the folder. Is it supposed to dissapear from the /data folder?
And i tried putting the recovery image in the same folder as abd which is the platform tools folder then flash it over and i got the same message. (cannot open for read: No such file or directory.)
Im sorry for all the questions and I am thankful for your help. I feel like i cant be the only person having this problem, well i hope im not that would make me feel really stupid. Thanks.
powers.jereme said:
Well ive tried to take the recovery image from the sd card to the /data folder but when i run 'rm /data/recovery.img' on the command prompt then reboot my phone, i turn it off then try and put it in recovery mode but its just regular recovery mode not cwm recovery mode. And everytime i run the 'rm /data/recovery.img' when my phone boots back up the recovery image is no longer in the /data folder or anywhere. But if i dont run the 'rm /data/recovery.img' after moving the recovery image to the /data folder it stays in the folder. Is it supposed to dissapear from the /data folder?
And i tried putting the recovery image in the same folder as abd which is the platform tools folder then flash it over and i got the same message. (cannot open for read: No such file or directory.)
Im sorry for all the questions and I am thankful for your help. I feel like i cant be the only person having this problem, well i hope im not that would make me feel really stupid. Thanks.
Click to expand...
Click to collapse
rm is the command to remove. So yes, recovery.img is supposed to disappear after that command. Put it back on /data and run the whole process from the CWM thread again making sure you do every step. Sounds like you may have accidentally skipped a step.
Sent from my LG-P925 using Tapatalk
Double post.
Ugh...keep selecting quote instead of edit on Tapatalk...Triple post...
Alright ill try that again, so i should put the file back on the /data folder and then still do the step where you try to flash over cwm from the cwm thread, even though its already there? Thanks
powers.jereme said:
Alright ill try that again, so i should put the file back on the /data folder and then still do the step where you try to flash over cwm from the cwm thread, even though its already there? Thanks
Click to expand...
Click to collapse
Yea just do it all again. Worst case is you flash cwm back over cwm
Sent from my LG-P925 using Tapatalk
I got it to work Urabewe was right i just needed to put the recovery image in the correct folder and everything worked perfect. Thanks guys.
Hello, as I said in the title, I have a problem with the recovery menu (Same with OR) - problem is I can boot in recovery (the screen with the triangle) but there can not go to the menu. I press Volume Up + camera and nothing happens. Remains the same screen with the triangle and phone.
Please give me a solution because my phone is moving very slowly with Android 2.2.x
Device - Motorola a853 Milestone
Bootloader - 90.78
Button on the camera work, as well as the volume.
What could be the problem?
Sorry for bad English ..
Come on guys, 26 views and no response to my question?
I searched all forums and tried all the solutions posted there, but none worked! But those were old solutions ...
No one knows who could be my problem?
Not sure what kind of problem you are facing. You can surely try this.
Looks like OR is not loading in ur case. You can download the latest OR, I'm using minimod OR, copy the update.zip file into the root of SD card, again reboot into recovery. If u find ur milestone stuck in triangle button try pressing volume up button. This time it should invoke the OR or it should ask u to update the zip file.
Still if it doesnt works i think u have to take advice from experts who can help u to use ADB comnands to troubleshoot further. Anyways best of luck.
Sent from my Milestone using xda app-developers app
like the last post, you should verify if you have OpenRecovery folder and update.zip file in your /sdcard.
You can try via adb or terminal emulation "reboot recovery"
I tried what you said nagabushan.c, but it does not work ... Always the same problem, no menu displays..
At least do u get exclamatory mark when u booted or milestone while pressing camera button ? Then give a sec gap and then press volume up button.
Any device both rooted or non rooted should display this.
Try ADB steps..
Let us know what u observe
Sent from my Milestone using xda app-developers app
nagabushan.c said:
At least do u get exclamatory mark when u booted or milestone while pressing camera button ? Then give a sec gap and then press volume up button.
Any device both rooted or non rooted should display this.
Try ADB steps..
Let us know what u observe
Sent from my Milestone using xda app-developers app
Click to expand...
Click to collapse
I see an exclamation mark only when you press power + x (bootloader 90.78).
I tried ADB steps..not working.
Have you verified OpenRecovery folder and its update.zip on sdcard? Try to re-download and unpack it fresh new.
What rom you said you currently have?
Have you installed vulnerable recovery?
Have you verified OpenRecovery folder and its update.zip on sdcard? Try to re-download and unpack it fresh new.
I tried, does not work ...
What rom you said you currently have?
Stock rom 2.2.x.
Have you installed vulnerable recovery?
Of course, just as there's no difference ... the menu does not show.
The menu should show. Any menu. Either from stock or OpenRecovery. I would try with a different sdcard because the older kernel (2.6.29) in recovery does not support some cards well. If the buttons are working and you have installed everything correctly then it should work. I'd try with different sdcard.
Alternatively, you can try to tell recovery to apply update.zip from sdcard automatically
Code:
echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
but note that I am not sure if you need to be rooted for that. I assume not. You can either install Terminal emulator from PlayStore or enable usb debbuging in settings and try to connect through adb if you choose to try.
To see if adb detects your device
Code:
adb devices
if all is OK you should get some output (aphanumeric) and after that 16 characters, it should display in what mode is your device (device for a normally booted system, recovery for device in recovery...)
And then
Code:
adb shell
echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
reboot
I'm no expert but it might be an unsupported sdcard...
mrvek said:
The menu should show. Any menu. Either from stock or OpenRecovery. I would try with a different sdcard because the older kernel (2.6.29) in recovery does not support some cards well. If the buttons are working and you have installed everything correctly then it should work. I'd try with different sdcard.
Alternatively, you can try to tell recovery to apply update.zip from sdcard automatically
Code:
echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
but note that I am not sure if you need to be rooted for that. I assume not. You can either install Terminal emulator from PlayStore or enable usb debbuging in settings and try to connect through adb if you choose to try.
To see if adb detects your device
Code:
adb devices
if all is OK you should get some output (aphanumeric) and after that 16 characters, it should display in what mode is your device (device for a normally booted system, recovery for device in recovery...)
And then
Code:
adb shell
echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
reboot
I'm no expert but it might be an unsupported sdcard...
Click to expand...
Click to collapse
Here's what I get from cmd:
C:\android-sdk\platform-tools>adb devices
List of devices attached
04037B7518003010 device
C:\android-sdk\platform-tools>adb shell
# echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
cannot create /cache/recovery/command: directory nonexistent
#
My device is rooted wth "superoneclick" method.
es7ar said:
cannot create /cache/recovery/command: directory nonexistent
Click to expand...
Click to collapse
Create it.
Code:
adb shell
mkdir -p /cache/recovery
mrvek said:
Create it.
Code:
adb shell
mkdir -p /cache/recovery
Click to expand...
Click to collapse
C:\android-sdk\platform-tools>adb shell
$ mkdir -p /cache/recovery
mkdir -p /cache/recovery
mkdir failed for -p, Read-only file system
$
Try without -p
Code:
mkdir /cache/recovery
mrvek said:
Try without -p
Code:
mkdir /cache/recovery
Click to expand...
Click to collapse
I created the folder "recovery" inside "cache" with root explorer.
Now cmd shows me: ( check attachments )
are you missing "echo"?
Code:
echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
it simply writes what is in the first argument (in quotes) to file named "command" located in /cache/recovery
Edit: you can ommit adb devices. You just test the first time when you connect to be sure if adb detects your device. After that it should generally give "device not found" or something like that if connection to device is lost.
I do not understand ...
The command "echo" - update_package = sdcard: update.zip "> / cache / recovery / command" should create a file called "command" in the folder "recovery" from the "cache"?
If so, there is no file called "command"
Sorry, I'm newbie ... I do not want to stress you out.
Edit : Hmm ...
Instead of reboot, like you said, I typed "reboot recovery" then restated the phone ... and the loading bar appears. The phone has rebooted when it came to approx. 30% ..
es7ar said:
I do not understand ...
The command "echo" - update_package = sdcard: update.zip "> / cache / recovery / command" should create a file called "command" in the folder "recovery" from the "cache"?
If so, there is no file called "command"
Sorry, I'm newbie ... I do not want to stress you out.
Click to expand...
Click to collapse
Yes, it should create that file with that content, to instruct recovery to automatically apply update.zip.
You can try to create that file manually with the
Code:
--update_package=SDCARD:update.zip
content in it.
Could you post the content of
Code:
mount
executed in adb? i was sure you can write to cache, it should be mounted read-write.
---------- Post added at 03:32 PM ---------- Previous post was at 03:30 PM ----------
es7ar said:
Edit : Hmm ...
Instead of reboot, like you said, I typed "reboot recovery" then restated the phone ... and the loading bar appears. The phone has rebooted when it came to approx. 30% ..
Click to expand...
Click to collapse
hm...
could you please execute in adb:
Code:
ls -laR /sdcard/OpenRecovery /sdcard/*.zip
post output.
Okay, it looks like it was done!
You've explained it very well ... but I did not openrecovery and update.zip in sdcard.
I thank you so much for helping me! Thanks a lot!!
es7ar said:
but I did not openrecovery and update.zip in sdcard
Click to expand...
Click to collapse
That leads us back to the very begining of the process...