Okay, i did try and search this but seems like nobody asked or its buried under a lot of threads. I thought I saw somebody how to fix it also but cant find it. Anyways, im trying to root my phone but i get after the unrevoked part where i type in:
# Flash_image recovery /sdcard/recovery.img
I typed it in right and i get a lot of out of memory.
Any help from this point?
Thx
to be more specific I get this error after typing in
# Flash_image recovery /sdcard/recovery.img
then i get this
mtd: read error at 0x00000000 (out of memory)
it repeats it and the 0x00000000 changes to different numbers and letters.
Nvm i restarted my phone then tried again and it fixed the prob.
I am pretty sure I have followed the directions for installing CWD correctly but I cannot boot into recovery from "Power Off" state. This is a cut-and-paste of my ADB session. Everything looks OK right?
Thanks for any help.
Code:
# dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
2560+0 records in
2560+0 records out
10485760 bytes transferred in 1.391 secs (7538289 bytes/sec)
# dd if=/data/recovery.img of=/dev/block/mmcblk0p6 bs=4096
dd if=/data/recovery.img of=/dev/block/mmcblk0p6 bs=4096
1238+1 records in
1238+1 records out
5070963 bytes transferred in 0.509 secs (9962599 bytes/sec)
# rm /data/recovery.img
rm /data/recovery.img
# reboot
reboot
You did power+volume down+3D til vibrate then release power and hold volume down+3d til recovery right?
Sent from my LG-P925 using Tapatalk
CallMeAria said:
You did power+volume down+3D til vibrate then release power and hold volume down+3d til recovery right?
Sent from my LG-P925 using Tapatalk
Click to expand...
Click to collapse
I did the power+downvolume+3D multiple times. And then it finally worked AFTER I unplugged my phone from my laptop(it was low on battery and I didn't want to have it power off in the middle of flashing).
Thanks for your help!
Cant flash ClockworkMod Recovery
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.
powers.jereme said:
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.
Click to expand...
Click to collapse
I did this the exact same way and got the directory not found or no such directory. I have the recover.img file but when I type in dd if=/data/recovery.img of=/block/mmcblk0p6 bs=4096 to flash it just doesn't work. What am I doing wrong or where do I need to put the recovery.img after downloading?
Rabidaries said:
I did this the exact same way and got the directory not found or no such directory. I have the recover.img file but when I type in dd if=/data/recovery.img of=/block/mmcblk0p6 bs=4096 to flash it just doesn't work. What am I doing wrong or where do I need to put the recovery.img after downloading?
Click to expand...
Click to collapse
Recovery.img needs to be in
/sdcard
Sent from my LG-P925 using XDA App
Rabidaries said:
I did this the exact same way and got the directory not found or no such directory. I have the recover.img file but when I type in dd if=/data/recovery.img of=/block/mmcblk0p6 bs=4096 to flash it just doesn't work. What am I doing wrong or where do I need to put the recovery.img after downloading?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1363132
Go there and follow those directions they are the easiest way to install cwm. Good luck
I'm getting an error message that says cannot open for read: No such file or directory. I've already download the recovery.img and followed the steps from here http://forum.xda-developers.com/showthread.php?t=1363132
I get this error in CWR (3.2.0.1), I have a nook with a blue sticker:
Code:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/command
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/command
Nothing, and I mean Nothing I have found in this forum solved this error, including the repartition-boot-stock+factory rest.
Any help guys? I am desperate!
adb is working but shell is not
This is what I got, anyone has an idea how to recover from this?
Code:
C:\Users\Barak>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
reifba said:
This is what I got, anyone has an idea how to recover from this?
Code:
C:\Users\Barak>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
Nothing, and I mean Nothing I have found in this forum solved this error, including the repartition-boot-stock+factory rest.
Click to expand...
Click to collapse
If you repartitioned, that may be the reason the adb command is not working....
patruns said:
If you repartitioned, that may be the reason the adb command is not working....
Click to expand...
Click to collapse
So I have 2 two problems in which the solution to one causes the other...
In the mean time I manged to run both the Froyo and HoneyComb from the sd card, but not the CM7 (which is the one I am trying to install on the internal memory)
using ADB to restore
I tried to use the methods described in:
:http://forum.xda-developers.com/showthread.php?t=919353
However it is not clear where should the factory.zip go?
for some reason it also says that the /dev partition is only 244MB so I cannot flash the system.img, it is probably the partition in the SD card and not the memory, so not much advancement here either. I also think that because it gives me 11223344556677 as the S/N and not the real one.
The quest to restore the nook continues...
Is there a way to manually repartition through ADB?
or anything? cause nothing solves the first error posted in this thread
reifba said:
I tried to use the methods described in:
:http://forum.xda-developers.com/showthread.php?t=919353
However it is not clear where should the factory.zip go?
for some reason it also says that the /dev partition is only 244MB so I cannot flash the system.img, it is probably the partition in the SD card and not the memory, so not much advancement here either. I also think that because it gives me 11223344556677 as the S/N and not the real one.
The quest to restore the nook continues...
Click to expand...
Click to collapse
factory.zip and rombackup.zip should be located on /dev/block/mmcblk0p3
system should be written to /dev/block/mmcblk0p5
1123344556677 is normal for the device listing when adb'ing in when running CWM on the uSD
to write the img files you need to use:
dd if=(IMG FILE ON SD) of=(PARTITION ON /dev... i.e. /dev/block/mmcblk0p1)
to help you out...here's a list of what goes where:
mmcblk0p1-boot.img
mmcblk0p2-rom.img
mmcblk0p3-factory.img
mmcblk0p4-logical.img
mmcblk0p5-system.img
mmcblk0p6-data.img
mmcblk0p7-cache.img
mmcblk0p8-media.img
problem:
thanks for the reply, I am studying more about andriod and adb now than during all my bachelor's.
just
adb push factory.zip /dev/block/mmcblk0p3 ??
and
adb shell dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
(in some places I saw they didn't write "/block")
and where is rombackup.zip from?
the problem is that for some reason /dev/ is only 244MB so I can't dd system.img, only the boot.img.
I wish that somewhere in the world would exist something that solves it from CWR, just some zip I would install to fix boot+factory+system in one stroke...
reifba said:
thanks for the reply, I am studying more about andriod and adb now than during all my bachelor's.
just
adb push factory.zip /dev/block/mmcblk0p3 ??
and
adb shell dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
(in some places I saw they didn't write "/block")
and where is rombackup.zip from?
the problem is that for some reason /dev/ is only 244MB so I can't dd system.img, only the boot.img.
I wish that somewhere in the world would exist something that solves it from CWR, just some zip I would install to fix boot+factory+system in one stroke...
Click to expand...
Click to collapse
to get factory and rombackup zip files on mmcblk0p3...
adb shell mkdir /sdcard/tmp3
adb shell mount /dev/block/mmcblk0p3 /sdcard/tmp3
adb push factory.zip /sdcard/tmp3
adb push rombackup.zip /sdcard/tmp3
more problems (desperation is looming)
DizzyDen said:
adb shell mount /dev/block/mmcblk0p3 /sdcard/tmp3
Click to expand...
Click to collapse
when I type the above I get
Code:
[email protected]:/ # mount /dev/block/mmcblk0p3 /sdcard/tmp3
Usage: mount [-r] [-w] [-o options] [-t type] device directory
I had to do it in the shell in order to su.
reifba said:
when I type the above I get
Code:
[email protected]:/ # mount /dev/block/mmcblk0p3 /sdcard/tmp3
Usage: mount [-r] [-w] [-o options] [-t type] device directory
I had to do it in the shell in order to su.
Click to expand...
Click to collapse
then I would use
mount rw /dev/block/mmcblk0p3 /sdcard/tmp3
If that doesn't work:
mount rw -o remout /dev/bloc/mmcblk0p3 /sdcard/tmp3
but it would appear something else is amiss... since it even shows the command should have worked... since everything other than the command (mount) the device (/dev/block/mmcblk0p3) and directory (/sdcard/tmp3) are optional parameters
I am having an issue where my Nook Color will only boot to recovery.
What happened that possibly caused this: While booting up CM9 on emcc, I held the N button down to go into fattire's u-boot menu, I accidentally chose to Alternate boot and I have no alternate boot. The u-boot menu froze for several minutes. I then forced a hard power off by holding the power button. Since then the device will only boot to recovery regardless of the u-boot menu choices.
I have never dual booted and never ran any dual boot scripts. All of the attempts to fix this result in the Nook booting only to recovery. My Nook *will* boot from a bootable CW usd, that I have used for repair attempts of my emcc. I used the most updated CWR version possible. Additionally booting to a "Nookie Froyo" (remember that?) bootable card for repair attempts.
So to be clearer; I can boot to a bootable usd card, but all attempts to boot from emcc result in a boot into recovery.
I have tried:
Full wipe, reflash CM9, clear caches fix permissions.. etc. several times.
Full wipe reflash Cm7, then CM9 respectively.
Manually via adb, removing and installing CWR. (Results in boot to u-boot screen, all menu options lead to boot to blank screen)
Flashed back to stock. (Results in booting to stock recovery, and then fails)
Repartioned boot via flashable zip.
Restore to stock via flashable zip.
Recreated stock boot partitions manually via ADB, fdisk, dd etc..
Recreated all partitions via ADB, and checked the contents and the format structures and sectors.
From stock 8 failed boots, fails.
From stock adb 8 failed boot count. (**All results to revert to stock results in booting to stock recovery and then fails to update**)
Made sure the bootable usd I was useing was latest ver CWR
Tried an eyeballer CWR zip to fix exiting CW.
Installed latest experimental CM9 CWR to emcc and tried all above, and still only boots to recovery.
Made sure no encore or update zips were on the root of my sdcard.
Flashed several iterations of fattire's u-boot.bin, even tho I know it is installed with any encore update.zip
Tried all of the above several times and all the standard tricks to recover that I have learned over the past year.
**All of the above results in a Nook that wants to boot to recovery, any recovery, weather recovery is present or not.**
This leads me to consider the 2nd (rom) partition that can contains 2 (or more?) private files that can control boot that will look for recovery only. I belive BCB and another boot count file I cannot recall..
I would like to reset theses files, if indeed this is the problem, and bring back my Nooks emcc normal boot. Being private files they do not seem to be accessible via normal ADB comands and this is where I start to get over my head.
This is no longer my primary tablet, this is my Android learning device and it continues to be fun. However this issue has me stymied.
So.., If anyone with a deeper understanding of this issue could help me, that would be nice.
Thanks.
12
12paq said:
This leads me to consider the 2nd (rom) partition that can contains 2 (or more?) private files that can control boot that will look for recovery only. I belive BCB and another boot count file I cannot recall..
I would like to reset theses files, if indeed this is the problem, and bring back my Nooks emcc normal boot. Being private files they do not seem to be accessible via normal ADB comands and this is where I start to get over my head.
This is no longer my primary tablet, this is my Android learning device and it continues to be fun. However this issue has me stymied.
So.., If anyone with a deeper understanding of this issue could help me, that would be nice.
Thanks.
12
Click to expand...
Click to collapse
Try this from recovery... we'll use /data as a mount point but you'll really be mounting /rom (p2). First make sure that /data isn't aready mounted, then try this:
mount /dev/block/mmcblk0p2 /data
cd /data
ls
(make sure that this is in fact rom with the bcb and bootcnt so forth)
mv BootCnt BootCnt.bak
mv BCB BCB.bak
dd if=/dev/zero of=/data/BootCnt bs=1 count=4
dd if=/dev/zero of=/data/BCB bs=1 count=1088
reboot
Hope something like this works and doesn't make it worse, but maybe it's worth trying. If it doesn't work, you can always move the backup files back...
Okay, I have seen this sitting here and puzzled on it awhile. I have a couple links for you.
This first is someone who seems to have the same problem you do. They burst into internet-tears after everyone who was trying to help them got pissy and left. He was unfairly lashing out, but they were being kinda condescending.
http://forum.cyanogenmod.com/topic/...ry-boot-after-cm7-install-cant-get-to-the-os/
I only include it so you could see if the problems line up. This guy was about to give up, and this finally worked. There is a second pagebof posts, that is where I found what appears to be a solution..
The zip at this link (from XDA, of course. I don't know xawen but it is his/her work).
This will repair the B&N bootloader.
http://forum.xda-developers.com/showthread.php?t=958748
I hope this works. I crow to my old lady about how this device is basically unbrickable, and it would dash my hopes to see your emmc unrecoverable...
Edit: Note the clockwork version! You may have to enter into your device through the sd card and first flash the correct CWM versiin
Thanks for your time!
ok when I:
C:\android-sdk-windows\platform-tools>adb shell
~ # mount /dev/block/mmcblk0p2 /data
mount /dev/block/mmcblk0p2 /data
~ # cd /data
cd /data
/data # ls
ls
BCB
/data #
ut oh.
No other files show up.
I am wondering since this is not a restore to stock adventure, which of those missing files do I really need?
EDIT:
I'm to going to back up & reset bcb file and see how far that gets me.
C:\android-sdk-windows\platform-tools>adb shell
~ # mount /dev/block/mmcblk0p2 /data
mount /dev/block/mmcblk0p2 /data
~ # cd /data
cd /data
/data # ls
ls
BCB
/data # mv BCB BCB.bak
mv BCB BCB.bak
/data # dd if=/dev/zero of=/data/BCB bs=1 count=1088
dd if=/dev/zero of=/data/BCB bs=1 count=1088
1088+0 records in
1088+0 records out
1088 bytes (1.1KB) copied, 0.078582 seconds, 13.5KB/s
/data #
yeah, with backing up and resetting BCB as ^^ above, I still can only boot into recovery.
Edit:
I guess I need a Bootcnt file.
No dice on the recoveryfix zips? They are meant to repair issues where people cannot boot into recovery, but I believe it may replace the boot files you are looking for. Maybe not, but a couple threads I found had people with your exact problem, trying everything they could, and this turned out to work. I spent a little minute looking into it.
Edit: well, I downloaded and looked into thebzips, and it is the uboot.bin and the recImages which I guess you tried. If you know exact missing file (I located the mmcblkOp2 file, although it breaks down no further in root explorer) could i just pull it out of my device and email/pm it to you?
mateorod-
Yeah, thanks man. I did try all those links and zips before but, thanks for the effort.
I am actually very close to getting this done thru ADB. I have all the files needed. It's just not a simple push from ADB to get them there.
The good news is I am entrenched deep in new stuff and learning and having fun.
I'll keep you posted. Thanks again.
Yeah, I'm interested for sure. Good luck and tell us how you did it.
Fattire-
This what I achieved tonight:
~ # mount /dev/block/mmcblk0p2 /data
mount /dev/block/mmcblk0p2 /data
~ # cd /data
cd /data
/data # ls
ls
BCB BCB.bak BootCnt
/data # mv BootCnt BootCnt.bak
mv BootCnt BootCnt.bak
/data # dd if=/dev/zero of=/data/BootCnt bs=1 count=4
dd if=/dev/zero of=/data/BootCnt bs=1 count=4
4+0 records in
4+0 records out
4 bytes (4B) copied, 0.004242 seconds, 942B/s
/data # dd if=/dev/zero of=/data/BCB bs=1 count=1088
dd if=/dev/zero of=/data/BCB bs=1 count=1088
1088+0 records in
1088+0 records out
1088 bytes (1.1KB) copied, 0.018737 seconds, 56.7KB/s
/data # reboot
reboot
reboot returned
/data # exit
exit
C:\android-sdk-windows\platform-tools>adb reboot
I still can't boot normaly from emcc, it roles right into CWR.
Any other ideas?
Thanks for your time!
ran everything again as seen here:
C:\android-sdk-windows\platform-tools>adb devices
List of devices attached
0000000000000000 recovery
C:\android-sdk-windows\platform-tools>adb shell
~ # mount /dev/block/mmcblk0p2 /data
mount /dev/block/mmcblk0p2 /data
~ # cd /data
cd /data
/data # ls
ls
BCB BCB.bak BootCnt BootCnt.bak tombstones
/data # dd if=/dev/zero of=/data/BootCnt bs=1 count=4
dd if=/dev/zero of=/data/BootCnt bs=1 count=4
4+0 records in
4+0 records out
4 bytes (4B) copied, 0.000702 seconds, 5.6KB/s
/data # dd if=/dev/zero of=/data/BCB bs=1 count=1088
dd if=/dev/zero of=/data/BCB bs=1 count=1088
1088+0 records in
1088+0 records out
1088 bytes (1.1KB) copied, 0.016968 seconds, 62.6KB/s
/data # reboot
reboot
reboot returned
/data # exit
exit
C:\android-sdk-windows\platform-tools>adb reboot
I still cannot get the devices to boot into anything but recovery.
Any help would be greatly appreciated.
Ok so this same exact thing happened to me as well. What I did to fix it was make a bootable sd recovery then slapped cm7 on it. Doesn't matter what one. Slapped meaning the flashable zip, after the sd was made to be a bootable recovery. Then wend though an formated everything but the emmc and then installed cm7 and bam it worked again. No problems still.
Sent from my PG06100 using Tapatalk
This all happened fro.m some thing that went wrong during a cm9 install? That's what caused mine.
Sent from my PG06100 using Tapatalk
Pm me if you need further instruction
Sent from my PG06100 using Tapatalk
halrulez said:
Pm me if you need further instruction
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Thanks, but I am guessing you did not read my op, I have tried that multiple times and ways. But thanks anyway.
12paq said:
Thanks, but I am guessing you did not read my op, I have tried that multiple times and ways. But thanks anyway.
Click to expand...
Click to collapse
Sorry I forgot to not that I used TWRP2.0 to do all this. Cwm has never seemed to format anything correctly. So make it a bootable sd recovery of twrp I tried cwm and it didn't work.
Sent from my PG06100 using Tapatalk
halrulez said:
Sorry I forgot to not that I used TWRP2.0 to do all this. Cwm has never seemed to format anything correctly. So make it a bootable sd recovery of twrp I tried cwm and it didn't work.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Mmm.. well that's worth a try, at this point. I did use Neimath's experimental CWR that's more likely to not have problems with 2nd or Rom partition boot count files, but no go.
So, thanks.
Doh!
Double post.
I hope it works for you.
Sent from my PG06100 using Tapatalk
Any word on your nookie?
Sent from my PG06100 using Tapatalk
halrulez said:
Ok so this same exact thing happened to me as well. What I did to fix it was make a bootable sd recovery then slapped cm7 on it. Doesn't matter what one. Slapped meaning the flashable zip, after the sd was made to be a bootable recovery. Then wend though an formated everything but the emmc and then installed cm7 and bam it worked again. No problems still.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
so to be clear, so no one will fubar their boot partition, when you say, "format everything but emcc" you meant everything but boot and emcc, right?