Database Develop

[Q] Cant flash ClockworkMod Recovery (cannot open for read: No such file or directory

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.

[Q] Can't get gapps to install on NC CM7.2

Hello...i've search4ed and searched and no answer pertains to my problem that I can find. I followed this guide to get CM7.2 loaded on my 16gb sandisk sd card: http://forum.xda-developers.com/showthread.php?t=1000957 The gapps I'm using the CM7 download link. The CM7.2 rom is the newest one available on the download link
Everything loaded smooth and works great except when I get to the part of installing gapps, I reboot into recovery mode (blue penguin with scrolling writing) and everytime it cannot find gapps installer so it ignores it!! I don't know what else to do here.. I've verified the hash using md5sum and it matches... I have my gapps.zip file located on the ROOT of my sd card /sdcard/gapps.zip. I've also tried putting gapps in /sdcard/boot. I've also tried changing the name to gapps-update.zip, update-gapps.zip, gapps-gd....etc.zip, etc etc etc. No matter what or where I put the file it isn't found.
When I boot the NC i can get to a boot menu from there, i've tried all combinations of booting (internal, sd, normal, etc etc). I've tried installing through boot manager and that doesnt work. It reboots to recovery mode and still doesn't find the file. I've flashed clockwork in boot manager and that didn't help anything.
I'm not sure what I just did, but i rebooted and now I have a "burrito manager" icon. I tried installing through that and no go. Don't know what else to do.
I DO have wifi setup/connected.
*EDIT... not sure if it matters, but I do seem to have an issue. I'm connected to wifi but NTP isn't updating my clock settings. It is setup in settings to auto update the date/time using network settings and it doesn't update. Could this be an issue with getting market to show up if the time is wrong??

Its most likely you are not placing gapps in the root of the boot partition... try this:
if adb works for you:
adb shell mkdir /sdcard/boot
adb shell mount /dev/block/mmcblk1p1 /sdcard/boot
adb push ***GAPPS INSTALLER*** /sdcard/boot
then when you reboot to sd recovery mode it will see the gapps installer.

DizzyDen said:
Its most likely you are not placing gapps in the root of the boot partition... try this:
if adb works for you:
adb shell mkdir /sdcard/boot
adb shell mount /dev/block/mmcblk1p1 /sdcard/boot
adb push ***GAPPS INSTALLER*** /sdcard/boot
then when you reboot to sd recovery mode it will see the gapps installer.
Click to expand...
Click to collapse
Hello...thanks for the reply! But I'm a little confused what you mean? I manually put the gapps.zip file on /sdcard/gapps.zip AND also copied to /sdcard/boot/gapps.zip. The file is there. What is the filename supposed to be??? I've tried gapps-...zip, update-gapps...zip, gapps.zip, etc.
Is there something that adb does that copy on the terminal doesn't do??
See attached screenshot, the file is there. For some reason the installer script in recovery mode isn't finding it. That's why i was asking what filename it's looking for?

ballgum said:
Hello...thanks for the reply! But I'm a little confused what you mean? I manually put the gapps.zip file on /sdcard/gapps.zip AND also copied to /sdcard/boot/gapps.zip. The file is there. What is the filename supposed to be??? I've tried gapps-...zip, update-gapps...zip, gapps.zip, etc.
Is there something that adb does that copy on the terminal doesn't do??
See attached screenshot, the file is there. For some reason the installer script in recovery mode isn't finding it. That's why i was asking what filename it's looking for?
Click to expand...
Click to collapse
Do not put the file in 'sdcard'. It needs to go in the boot partition like dizzy said. Take the card out of the nook and put in your PC. That will show the boot partition. Put the gapp file there. Make sure the name starts with gapps-gb-. Put the card back into the Nook and reboot to recovery like before.

leapinlar said:
Do not put the file in 'sdcard'. It needs to go in the boot partition like dizzy said. Take the card out of the nook and put in your PC. That will show the boot partition. Put the gapp file there. Make sure the name starts with gapps-gb-. Put the card back into the Nook and reboot to recovery like before.
Click to expand...
Click to collapse
That worked! thank you very much...

[q] problem transfer twrp

hello all
I need help transferring rom TWRP but no possibility of installer.les files appears on TWRP but they are empty I think I can not flash.
what should I do,?

I could use as few more details, but try my tutorial, that tells how to push a file to the device from recovery: http://forum.xda-developers.com/showthread.php?t=2459498
Sent from my Amazon Kindle Fire HD using Tapatalk

If you have adb drivers installed, place the files you want to push in that folder. Then go to that directory on your command prompt. On your kindle go into recovery, go into advanced, and select adb sideload. Once there, type, "adb sideload [filename].zip" without quotation marks and place the name of the file in the brackets. It should push the file to your device and your set. Hope it helps.

[Q] Cant get MB886 into custom recovery

I have been trying for hours to install a custom recovery in my AT&T Atrix HD (mb886) phone. Every time I go through the flashing process, no matter what recovery I try, and whether I use the stock SDK fastboot or one of alternatives, when I try to boot into recovery, I get an ominous error message about how my bootloader is unlocked, and Motorola and ATT will not honor the warranty, and so on. However - it then always boots into the normal startup. I did try holding down both volume buttons when I cycled the power button, and I briefly (about 5 seconds, maybe?) got what looked like a text-based recovery menu, but then the error message popped up again, and I'm back to ????? is going on.
Any help? I have read a number of article/forums online, but all assume that your recovery is working so you can install a custom ROM. I have done this on a couple of Android tablets in the past, so I know I'm not totally stupid, but I can't seem to get past the AT&T nanny.
How can I fix this?
Android 4.1.1
System 98.4.20.MB886.ATT.en.US

If I remember correctly, I had to rename install-recovery.sh (or something like that) by adding .bak to the end of the filename. Boot into fastboot, flash your recovery, and try to boot into recovery.

Nevadadave said:
I have been trying for hours to install a custom recovery in my AT&T Atrix HD (mb886) phone. Every time I go through the flashing process, no matter what recovery I try, and whether I use the stock SDK fastboot or one of alternatives, when I try to boot into recovery, I get an ominous error message about how my bootloader is unlocked, and Motorola and ATT will not honor the warranty, and so on. However - it then always boots into the normal startup. I did try holding down both volume buttons when I cycled the power button, and I briefly (about 5 seconds, maybe?) got what looked like a text-based recovery menu, but then the error message popped up again, and I'm back to ????? is going on.
Any help? I have read a number of article/forums online, but all assume that your recovery is working so you can install a custom ROM. I have done this on a couple of Android tablets in the past, so I know I'm not totally stupid, but I can't seem to get past the AT&T nanny.
How can I fix this?
Android 4.1.1
System 98.4.20.MB886.ATT.en.US
Click to expand...
Click to collapse
That warning you see is just the boot logo and can be gotten rid of by flashing a custom logo. Stock Moto boot logos on this platform have two images -- one for locked and another for unlocked bootloaders. It's a non issue and just confirms that the bootloader is unlocked.
You accessed that menu by powering up and holding both volumes and power. Volume down scrolls and volume up selects in there.
To install a custom recovery, boot into fastboot mode and flash it with fastboot. Mythtools, maybe BootMyHD, can do that for you if you don't have moto-fastboot binary or are unable to run "moto-fastboot flash recovery recovery.img" with your phone plugged into a rear usb port in fastboot mode with a terminal/command prompt open to the directory with the recovery image.

More questions
audit13, how do I access that file to change the name? I tried again this morning, and after doing the boot to recovery key sequence, I got a menu, and before it went away, I selected boot to recovery, but got the dead android icon. I tried several other options and it just did a normal boot. Still stumped.
skeevydude, I have tried installing a couple of custom recoveries, using fastboot, and when I do, I get a message saying all went well, but when I boot up, it either does the "failed Android" or just boots up normally. I'll try Mythtools and BootMyHD, but it seems that there is something else going on here.

Nevadadave said:
audit13, how do I access that file to change the name? I tried again this morning, and after doing the boot to recovery key sequence, I got a menu, and before it went away, I selected boot to recovery, but got the dead android icon. I tried several other options and it just did a normal boot. Still stumped.
skeevydude, I have tried installing a couple of custom recoveries, using fastboot, and when I do, I get a message saying all went well, but when I boot up, it either does the "failed Android" or just boots up normally. I'll try Mythtools and BootMyHD, but it seems that there is something else going on here.
Click to expand...
Click to collapse
Maybe something else going on. Are you flashing using the rear usb port of your PC? It really does matter.
To answer the first question about install-recovery, once you're rooted, use Root Explorer or something similar, mount /system as read/write, go to /system/etc, rename the file install-recovery.sh to install-recovery.sh.bak, and reboot.
If you have adb installed on your PC you can do
adb root
adb shell mount -o remount,rw /system
adb shell cp /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
adb shell rm /system/etc/install-recovery.sh
adb reboot

I'll try it and see what happens
skeevydude said:
Maybe something else going on. Are you flashing using the rear usb port of your PC? It really does matter.
To answer the first question about install-recovery, once you're rooted, use Root Explorer or something similar, mount /system as read/write, go to /system/etc, rename the file install-recovery.sh to install-recovery.sh.bak, and reboot.
If you have adb installed on your PC you can do
adb root
adb shell mount -o remount,rw /system
adb shell cp /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
adb shell rm /system/etc/install-recovery.sh
adb reboot
Click to expand...
Click to collapse
OK, I did not know about USB port preference. I'll try it and see what happens. Thanks!

No joy
Nevadadave said:
OK, I did not know about USB port preference. I'll try it and see what happens. Thanks!
Click to expand...
Click to collapse
Well, I tried front and back USB ports, in all cases, adb says "adb can't run as root in production builds". adb sees the phone, but about all I can do is start fastboot, but once there adb doesn't work until I reboot.
I tried running the remount command, but got a message, "Operation not permitted" I'm assuming because I could not root into the phone. Titanium backup shows that the phone is, indeed, rooted.
Stuck again...

Install Root Explorer, find the file, add .bak to the end, reboot to fastboot, install Philz, boot into recovery.

audit13 said:
Install Root Explorer, find the file, add .bak to the end, reboot to fastboot, install Philz, boot into recovery.
Click to expand...
Click to collapse
I tried that, got a "Rename failed". It appears that the file is set to read-only, and the Root Explorer doesn't seem to have a way to change that. I'm open to additional suggestions. I had thought that root access would allow me to do things like change file permissions, but I cannot do this with Root Explorer. Everything I try, I get a message that it can't be done, because the file system is read-only.
At the top of the file list, it says "mounted as r/o, but nothing shows to change that, although I see num,erous web posts that claim that there should be a "R/W" button somewhere.

Better luck
Nevadadave said:
Well, I tried front and back USB ports, in all cases, adb says "adb can't run as root in production builds". adb sees the phone, but about all I can do is start fastboot, but once there adb doesn't work until I reboot.
I tried running the remount command, but got a message, "Operation not permitted" I'm assuming because I could not root into the phone. Titanium backup shows that the phone is, indeed, rooted.
Stuck again...
Click to expand...
Click to collapse
OK, I dropped Root Explorer and loaded ES File Explorer. ES Explorer allowed me to change the file R/W permissions and rename the stock recovery file.
adb would still not allow me to get to root, so I loaded adbd insecure from the Play store, and that gave me root access. I flashed the CWR 6.0.4.4, and so far (fingers crossed) I was able to boot to CWM and I'm backing up my system now. Hopefully, the next update will be to say that I have a new ROM installed...

Nevadadave said:
OK, I dropped Root Explorer and loaded ES File Explorer. ES Explorer allowed me to change the file R/W permissions and rename the stock recovery file.
adb would still not allow me to get to root, so I loaded adbd insecure from the Play store, and that gave me root access. I flashed the CWR 6.0.4.4, and so far (fingers crossed) I was able to boot to CWM and I'm backing up my system now. Hopefully, the next update will be to say that I have a new ROM installed...
Click to expand...
Click to collapse
All you need to gain r/w access is to click on the ro button to change it to read/write.

audit13 said:
All you need to gain r/w access is to click on the ro button to change it to read/write.
Click to expand...
Click to collapse
Audit13 I'm not sure what you mean here. Root Explorer never indicated a "R/O" button or any other way to change permissions, it just kept saying that the file system was write-protected. ES File Explorer was very easily able to change this and allow me to remove the automatic recovery overwrite.
So, at this point, I have Cyanogen 10.2 running on my Atrix HD, and although I have found a few glitches, it is faster and it is now MINE!

Nevadadave said:
Audit13 I'm not sure what you mean here. Root Explorer never indicated a "R/O" button or any other way to change permissions, it just kept saying that the file system was write-protected. ES File Explorer was very easily able to change this and allow me to remove the automatic recovery overwrite.
So, at this point, I have Cyanogen 10.2 running on my Atrix HD, and although I have found a few glitches, it is faster and it is now MINE!
Click to expand...
Click to collapse
In Root Explorer, You'll see the words "Mounted as r/o". To the right will be a button that says "Mount R/W".
I went with Validus 5.1 over 10.2.

[Q] Atrix HD can't access recovery mode

I've been trying for sometime now to install a custom rom (CM11 or anything else for that matter) on my Atrix HD. I got as far a unlocking my boot loader so now every time I reboot, I get a scary warning message saying, my phone has been tampered with.
I've made several attempts to install CWM and even though it seems to install, if I try to boot my phone by holding the power and volume down buttons at the same time, it seems to do nothing, or it will just boot normally. I did try to hold down the power and volume up and volume down buttons and that leads to a menu. One of the options was recovery. I selected that, but then a display of android robot with a red triangle.
Can anyone give me some tips on what I'm doing wrong. I'm a programmer, but I have no experience with android, so you can stay technical but not too "android specific" technical.
Thanks,
Mark

Are you installing it via fastboot? Once you flash recovery, do not allow the phone the reboot. Try and boot into recovery.
If you still can boot into cwm, boot the phone, install Root Explorer, and rename recovery.sh to recovery.sh.bak, boot to fastboot, install cwm, and boot into cwm.

audit13 said:
Are you installing it via fastboot? Once you flash recovery, do not allow the phone the reboot. Try and boot into recovery.
If you still can boot into cwm, boot the phone, install Root Explorer, and rename recovery.sh to recovery.sh.bak, boot to fastboot, install cwm, and boot into cwm.
Click to expand...
Click to collapse
These are the commands I used.
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery.img
fastboot reboot
Where recovery.img was the CWM one.
Based on another thread, I attempted to rename ~/system/etc/install_recovery.sh, but even though I'm rooted, ES File Explorer not Root File Explore is able to rename that file.
Any help would be appreciated.
Thanks,
Mark

After renaming the file, stock recovery still comse up?

Sorry, there was a typo. I was NOT able to rename the file.

Use root explorer to do it. That's what I did.

audit13 said:
Use root explorer to do it. That's what I did.
Click to expand...
Click to collapse
I had tried that.
I had installed
ES File Explorer
Root File Explorer
Root File Manager Explorer
All seemed to either give an error or just not change the name. Is there a trick? I'm pretty sure my phone is rooted since I am prompted to ask permission to do these things. I think if I can get past this the renaming issue, I may actually be able to install a new rom. Can you help?
Thanks,
Mark

Did you change the permission in root explorer to r/w from r/o?

Can you be more specific about "root explorer" which app is it. I've used a couple of root file explorers and none of them can seem to rename /system/etc/install-recovery.sh.
I tried to use Root File Manager to change the permissions on that file to have write permissions. The problem is that it says it does, but then when I look again, it's unchecked.
I checked the /system/etc folder and it has write permissions for "owner". I tried to create a test folder in it. It said it was granted permission, but in the end, the test folder was not created.
Maybe my phone is not rooted properly?
I'm not sure at which point in the rooting process I got this, but I have an app named "#SuperSU". If I open it and check it's logs, I can now see an error message saying "SuperSU Pro is required for this feature". Did I screw up with rooting? Should I use something else. Any help to remedy this would be greatly appreciated.
Thanks,
Mark

markdemich said:
Can you be more specific about "root explorer" which app is it. I've used a couple of root file explorers and none of them can seem to rename /system/etc/install-recovery.sh.
I tried to use Root File Manager to change the permissions on that file to have write permissions. The problem is that it says it does, but then when I look again, it's unchecked.
I checked the /system/etc folder and it has write permissions for "owner". I tried to create a test folder in it. It said it was granted permission, but in the end, the test folder was not created.
Maybe my phone is not rooted properly?
I'm not sure at which point in the rooting process I got this, but I have an app named "#SuperSU". If I open it and check it's logs, I can now see an error message saying "SuperSU Pro is required for this feature". Did I screw up with rooting? Should I use something else. Any help to remedy this would be greatly appreciated.
Thanks,
Mark
Click to expand...
Click to collapse
I upgraded to SuperSU Pro. It was only $2.50. Now the log says, "Unable to chmod /system/etc/install-recovery.sh: Read-only file system"
This happened when trying to give write permissions to that file. Am I doing something wrong?

if your adb is setup and working try using this command in adb 'adb reboot recovery' and see if the phones boots to little android with its heart open given a excalmation mark there press all three buttons at the same time and recovery should open

mega_man said:
if your adb is setup and working try using this command in adb 'adb reboot recovery' and see if the phones boots to little android with its heart open given a excalmation mark there press all three buttons at the same time and recovery should open
Click to expand...
Click to collapse
I did that and when the screen you described displayed, pressed the power, and center of the volume up and down rocker switch so I can get but up and down. After a few seconds the screen went blank and I let go. The phone then just booted normally without going into recovery.

markdemich said:
I upgraded to SuperSU Pro. It was only $2.50. Now the log says, "Unable to chmod /system/etc/install-recovery.sh: Read-only file system"
This happened when trying to give write permissions to that file. Am I doing something wrong?
Click to expand...
Click to collapse
Root Explorer: https://play.google.com/store/apps/details?id=com.speedsoftware.rootexplorer&hl=en

audit13 said:
Root Explorer: https://play.google.com/store/apps/details?id=com.speedsoftware.rootexplorer&hl=en
Click to expand...
Click to collapse
Thanks. I purchased that app and when I tried to set the permissions of the file it prompted to mount the volume with write permissions. Once it did that, everything else worked.
Thanks again,
Mark