Hello
I am trying to use fdisk to partition optimus' nand. I want to delete the last 2 partitions /dev/block/mmcblk0p9 and p8 and merge them into p8 but fdisk wont let me do it. It says "value is out of range" and gives me as default 511kb of space each logical partition by default.
If i delete all partitions till p5 and remake the extended partition everything can go ok but these include things i dont wont to touch
For your quick reference the o2x partitions.
/dev/block/mmcblk0p1 = system partition
/dev/block/mmcblk0p2 = cache partition
/dev/block/mmcblk0p3 = misc partition
/dev/block/mmcblk0p4 = unknown partition
/dev/block/mmcblk0p5 = boot partition
/dev/block/mmcblk0p6 = lgdrm partition
/dev/block/mmcblk0p7 = recovery partition
/dev/block/mmcblk0p8 = data partition
/dev/block/mmcblk0p9 = internal SD partition
How can Solve this? Any ideas?
Can someone please upload the contets Of p5 p6 p7?
P5 depends on your ROM
P6 attached
P7 you can get CWM from anywhere really
Thank you a lot rusty its very much aprisiated
Do you know anything about the original question?
No idea I'm afraid.
busybox fdisk -l /dev/block/mmcblk0
d
9
d
8
n
57537
976128
w
didn't worked btw
get notification that i got damaged sd so i removed the internal sdcard part from the vold
but still no big ass data partition xD
btw i don't know anything about fdisk i just gave it a shot
look at that... looks like our phone has 16gbs or wrong declare from fdisk?
http://forum.xda-developers.com/showpost.php?p=17001387&postcount=12
edit: apparently it was a wrong declare from my brain
Apparently the SU660 has more internal storage than the P99x, so maybe it's got the same amount really, but the P99x is set up to ignore some of it?
I am new to Android, want to customize the system follow the tutorials, but found the Note is different to other Android phones:
for other phone, there will be a /proc/mtd and list all the partitions with mount point, but on Note I can only found /proc/fs, with 3 folders: ext4 jbd2 nfsd
and the mount table is like this:
rootfs on / type rootfs (ro,relatime)
...
/dev/block/mmcblk0p9 on /system type ext4
/dev/block/mmcblk0p7 on /cache type ext4
/dev/block/mmcblk0p1 on /efs type ext4
for other devices, e.g., HTC Wildfire, the partition will like below:
mtd1: recovery
mtd3: system"
...
I downloaded the CF-Root flasher, by Chainfire, found basiclly it's flashing a zImage into /dev/block/mmcblk0p5. I mount the partition before flash and seems there is only some picture files there. how can we know the machine will boot to this partition in recovery mode?
nobody knows? so far what I get seems that the phone do not use the /recovery partition, but use same kernel to handle the recovery state. during boot it will search for /system/etc/install-recovery.sh, maybe that will trigger the recovery process?
The Note, like many other Samsung phones, does not use or follow the mtd layout - at all.
Indeed there is a single kernel for both normal boot and recovery. Normal boot uses init.rc script, recovery boot uses recovery.rc script.
There is a "spare" partition that is both called recovery and available, but it isn't used.
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?