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?
Related
I had to wipe my phone and have ext2 partition on my card but when I try the copy.sh app command it works but always hangs on the flashing g1 after I reboot the phone. So this leads me to believe its because the apps are still there on the ext2 partition and need to be removed before I could do it again.
Joeriginal said:
I had to wipe my phone and have ext2 partition on my card but when I try the copy.sh app command it works but always hangs on the flashing g1 after I reboot the phone. So this leads me to believe its because the apps are still there on the ext2 partition and need to be removed before I could do it again.
Click to expand...
Click to collapse
well you can try flashing LucidREM mod that has the files for mounting it located here and instead of using the copy.sh app first try this.
$su
# cd /system/sd
# ls -la
check if the app folder is there if it is than
# cd app
#ls
check if the files are there.. and if they exist than try this
# rm -rf /data/app
# ln -S /system/sd/app /data/app
# reboot
hope that helps and it u still want to wipe the ext2 parttition than jut
# rm -rf /system/sd/*
or
# rm -a /system/sd/*
Nitro212 said:
well you can try flashing LucidREM mod that has the files for mounting it located here and instead of using the copy.sh app first try this.
$su
# cd /system/sd
# ls -la
check if the app folder is there if it is than
# cd app
#ls
check if the files are there.. and if they exist than try this
# rm -rf /data/app
# ln -S /system/sd/app /data/app
# reboot
hope that helps and it u still want to wipe the ext2 parttition than jut
# rm -rf /system/sd/*
or
# rm -a /system/sd/*
Click to expand...
Click to collapse
I have problems when I get to ln -S /system/sd/app /data/app
it says link failed no such file exists
Joeriginal said:
I had to wipe my phone and have ext2 partition on my card but when I try the copy.sh app command it works but always hangs on the flashing g1 after I reboot the phone. So this leads me to believe its because the apps are still there on the ext2 partition and need to be removed before I could do it again.
Click to expand...
Click to collapse
I kinda had the same question but was wondering if there was an easier way of wiping the ext2 partition? I'm kinda new at all this and am now starting to get the hang of flashing different roms onto my phone but I realized that doing an Alt+W before flashing new roms does not wipe the ext2 partition. (At least I'm pretty sure it doesn't.)
I'm not too savvy on using terminal yet..I've heard of using adb but I don't even know where to begin with that..so I was wondering if going into Paragon Partition Manager and just formatting the ext2 partition will work? Any info will be greatly appreciated.
Ok i finally have it working. I keep getting a social network force close.
wiping an ext2/ext3 partition
Joeriginal said:
I had to wipe my phone and have ext2 partition on my card but when I try the copy.sh app command it works but always hangs on the flashing g1 after I reboot the phone. So this leads me to believe its because the apps are still there on the ext2 partition and need to be removed before I could do it again.
Click to expand...
Click to collapse
there is an app on the market called lucid REM that runs his script via terminal emulator. after getting it and running it you can go to terminal and type
su
lucid -c (this wipes ext2/3 partition)
hopefully this helps you. if you are on a rom that uses auto a2sd then you will most likely getting force closes all over until you flash your new rom.
I posted a thread with steps to do it http://forum.xda-developers.com/showthread.php?t=533731
Code:
Open console and enter the following commands. Press "Enter" after each line. This wipes the ext partition.
mount -o rw /dev/block/mmcblk0p2 /system/sd
rm -r /system/sd/
[code]
Glad this wasnt deleted right away, maybe it can just be moved?
It helped because I also was wondering the best way of doing this, and now I know.
Thanks .
Odd, double post for no reason. Sorry delete this post?
so i want to wipe my g1 to delete all of its apps.
however I would still like to keep my contacts and sms's/emails.
is this possible? if so, how do i do it?
thanks, God Like
your email's and contacts should be synced to google's servers if you keep sync on. if not just manually sync it a few times to get it to register on the servers. you can back up your messages.
or if you have fastboot, you can make a nandroid back up. pull userdata.img and use fastboot flash data userdata.img or something like that to put it back on your phone.
totally forgot that they were on google :/
but remember i am a noob, how do i wipe lol?
also my apps are on sd so will it delete them off the partition?
also will it delete everything else on my sd?
lastly, it wont delete my rom or root will it?
thanks
well to wipe your phone, boot the phone into recovery (home and power) and there is an option in recovery to wipe your phone. that will clear cache and data.
to wipe your ext2/3/4 boot into recovery, then choose the option recovery console, once in the recovery console hit enter, there will be a prompt to hit enter, so that is how you will know you are in the recovery console. after you hit enter type
Code:
mount /system
rm -r /system/sd/*
that will delete everything off of your second partition.
if you either wipe your phone or format your sdcard, it is recommended that you reflash your rom. but you will not lose root by just wiping your phone or formatting your sdcard
david1171 said:
Code:
mount /system
rm -r /system/sd/*
Click to expand...
Click to collapse
didnt work. My partition is linux ext2 ...do i need to change the asterix to anything?
thanks
mackz said:
didnt work. My partition is linux ext2 ...do i need to change the asterix to anything?
thanks
Click to expand...
Click to collapse
/system/sd is what the phone recognizes the ext2 partition to be. try
Code:
rm /system/sd/*
or
Code:
rm -r /system/sd
or
Code:
rm /system/sd
if that doesn't work then try
Code:
mount -o rw /dev/block/mmcblk0p2 /system/sd
cd /system/sd
rm -r *
that and see if it will work.
make sure you are doing this from the recovery console.
If you are using cm recovery 1.4 you can go into the recovery console and type ums_enable to acess the sdcard with nothing running on it, I just did it to wipe my sd and start over fresh and when you are done type ums_disable to unmount the sd and type reboot to restart the phone
david1171 said:
/system/sd is what the phone recognizes the ext2 partition to be. try
Code:
rm /system/sd/*
or
Code:
rm -r /system/sd
or
Code:
rm /system/sd
if that doesn't work then try
Code:
mount -o rw /dev/block/mmcblk0p2 /system/sd
cd /system/sd
rm -r *
that and see if it will work.
make sure you are doing this from the recovery console.
Click to expand...
Click to collapse
hey, thanks this apparently worked. It replied a # which tells me it worked and when i tried to repeat the command it said (code) could not be found...but after i rebooted, all my apps are still there...and they work. I reflashed and everything still is there
any ideas?
I need to wipe my ext part from the console how can I do this?
in the console:
mount /system
rm -r /system/sd/
are you spacing these commands? It is not working
From recovery console
Code:
mke2fs -j /dev/block/mmcblk0p2
Will completely reformat ext3 partition destroying data and rebuilding table.
pistol4413 said:
in the console:
mount /system
rm -r /system/sd/
Click to expand...
Click to collapse
um, don't you have to mount the partition as rw first?
Code:
mount -o rw /dev/block/mmcblk0p2 /system/sd
This is how I installed without any problems:
: rename to update.zip
: place in the root of sd card
: shut off device
: boot into recovery
: wipe (alt w)
: go to console (alt x) and hit enter
(enter)
# mount -o rw /dev/block/mmcblk0p2 /system/sd
# cd /system/sd
# rm -rf /system/sd/*
# reboot recovery
: now wipe again (alt w)
: run a filesystem check from the menu. If it tells you to run it manually,
drop to a console (alt+x) and run "e2fsck /dev/block/mmcblk0p2".
: flash
Enjoy!!
AdrianK said:
um, don't you have to mount the partition as rw first?
Code:
mount -o rw /dev/block/mmcblk0p2 /system/sd
Click to expand...
Click to collapse
Lol yea i forgot to add it in srry
I, personally, used to use the recovery console or adb. But just download ubuntu and run it from live cd (basically boots linux from cd without installing anything on hard drive). Partition tool inside the OS beats any other method.
dumfuq said:
From recovery console
Code:
mke2fs -j /dev/block/mmcblk0p2
Will completely reformat ext3 partition destroying data and rebuilding table.
Click to expand...
Click to collapse
use that one. Best one available. doing a rm -rf on /system/sd sometimes still leaves some files. reformating ext3 and rebuilding the tables are the best way
yourtravelboy said:
This is how I installed without any problems:
: rename to update.zip
: place in the root of sd card
: shut off device
: boot into recovery
: wipe (alt w)
: go to console (alt x) and hit enter
(enter)
# mount -o rw /dev/block/mmcblk0p2 /system/sd
# cd /system/sd
# rm -rf /system/sd/*
# reboot recovery
: now wipe again (alt w)
: run a filesystem check from the menu. If it tells you to run it manually,
drop to a console (alt+x) and run "e2fsck /dev/block/mmcblk0p2".
: flash
Enjoy!!
Click to expand...
Click to collapse
Would you mind to tell me that if this instruction also apply to reformat ext3. I ask this question because I see the "mmcblk0p2" instead of "mmcblk0p3" in your instuction. I saw some posts which indicate that mmcblk0p2 is for ext2 but the mmcblk0p3 is for ext3. Am I correct?
p_pen said:
Would you mind to tell me that if this instruction also apply to reformat ext3. I ask this question because I see the "mmcblk0p2" instead of "mmcblk0p3" in your instuction. I saw some posts which indicate that mmcblk0p2 is for ext2 but the mmcblk0p3 is for ext3. Am I correct?
Click to expand...
Click to collapse
no, mmcblk0 references your sdcard mmcblk0px means partition substitute in 1 for fat32, 2 for ext2/3/4, and 3 for linux-swap.
p_pen said:
Would you mind to tell me that if this instruction also apply to reformat ext3. I ask this question because I see the "mmcblk0p2" instead of "mmcblk0p3" in your instuction. I saw some posts which indicate that mmcblk0p2 is for ext2 but the mmcblk0p3 is for ext3. Am I correct?
Click to expand...
Click to collapse
This is Not correct.
Everything in /dev/block is a different block device
mmcblk0p3 represents the third partition on you sdcard.
Usually this would be a linux swap partition.
To format ext3 look at my post above...for ext2 just remove the -j flag in the command.
dumfuq said:
This is Not correct.
Everything in /dev/block is a different block device
mmcblk0p3 represents the third partition on you sdcard.
Usually this would be a linux swap partition.
To format ext3 look at my post above...for ext2 just remove the -j flag in the command.
Click to expand...
Click to collapse
thanks for the simple ass formatting command. i actually bookmarked this page so that whenever this question is asked again (we all know it will be) i can easily pop this answer out.
I appreciate for your quick ans. It really solve my concern.
david1171 said:
thanks for the simple ass formatting command. i actually bookmarked this page so that whenever this question is asked again (we all know it will be) i can easily pop this answer out.
Click to expand...
Click to collapse
You should probably just memorize it.
mke2fs -j
Make_extended2_filesystem with journal
I thought this thread died just gave up just revisited this and it works thank you all for your help the command is "mke2fs /dev/block/mmcblk0p3" thank you I am sick of using acronis disk director it works but this takes an extra 10 min.
confused
can someone explain this more.
What is recovery console? How do i get there? Cause if its in my phone I cant get to it cause my boot screen is looping
Can you explain step by step in more detail
spazoid said:
can someone explain this more.
What is recovery console? How do i get there? Cause if its in my phone I cant get to it cause my boot screen is looping
Can you explain step by step in more detail
Click to expand...
Click to collapse
Boot pressing Home + Power
Scroll down to Enter Console
click the trackball
it will say <Press Enter>, so press enter
then type the following
Code:
mke2fs -j /dev/block/mmcblk0p2
and press enter
your ext is partitioned
to reboot your phone, type
Code:
reboot
and press enter
spazoid said:
can someone explain this more.
What is recovery console? How do i get there? Cause if its in my phone I cant get to it cause my boot screen is looping
Can you explain step by step in more detail
Click to expand...
Click to collapse
how exactly have you used your phone without knowing what the recovery console is.......
power down your phone
hold home and power to boot it up
press alt and x on the keyboard
press enter
type mke2fs -j /dev/block/mmcblk0p2
now type reboot recovery
wipe your phone
flash your rom.
reboot your phone with home and back.
Somebody please kill me!
Its clear the op didnt ****ing search when he asked this, otherwise he would have found my post explaining how to wipe your ext partition from your console. God dammit this is pissing me off
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
Hey, I'm looking to find the proper location for the recovery partition so I can dd an image to it.
cat /proc/mtd shows mtd1 but I haven't done this on an mtd device before so I'm wondering if dd if=/my/recovery.img of=/dev/mtd/mtd1 will actually work or if it will mess up my stuff.
Thanks!
NM, I'm just going to use flash_image instead. Ignore me.