yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Lanchon:
ok your emmc is locked in read-only mode. i had a gnex brought to me in that condition and there was absolutely nothing i could do to fix it. writes are ignored by the emmc (but return "ok" to the kernel) and take near zero time. i tried issuing emmc erase commands, etc, and they were all ignored. i tried booting via USB (via an OMAP debugger) and i couldn't accomplish anything. there is a thread here in xda that details what i tried and what i found out. in the end, i had to replace the motherboard of that phone.

but... i know more now :)

there is one thing you could try: completely reset the emmc. but really, given that you didnt follow a simple fastboot flash instruction and did a fastboot boot instead makes me think that you wont be able to correctly follow the procedure to completion, but we can try.

the trick is to resize the boot partitions, and during that operation the complete emmc will be wiped. this includes the corrupted FTL data structures inside the emmc that i suspect are causing the read-only lock.

so, caveats:

-this has never ever been tried on this device or this emmc. but it was done successfully in some kindles of the same era, which have a different but similar emmc (both are samsung emmcs). take a look here but DO NOT follow that procedure:

http://xdaforums.com/showthread.php?t=2413453

-everything gets wiped! including bootloaders, partition table, partitions, etc.

-the kindle can boot from usb, but the gnex cant. if the gnex is shut down or rebooted after wiping the emmc but before reconstituting the boot chain, THE DEVICE WILL BE BRICKED FOREVER and never boot again.

-if something goes wrong, BRICK.

-the procedure we will improvise and try can be plain wrong, and the device might BRICK.

-the emmc might ignore the boot partition resize command, in which case it wont brick any further, but this whole adventure would be a failure.

-actually i lied. if the device is rebooted without a proper boot chain, there is a boot-over-USB OMAP debugger that can boot it into a monitor. but reconstituting the boot chain from there might be impossible.

read everything twice and make sure you understand everything i write. ASK instead of guessing!

FROM NOW ON: everything you do, you will do it in latest release of TWRP for your device. before doing ANYTHING here, each time you boot your phone you will enter fastboot mode and "fastboot boot" this TWRP image. then you will "adb shell" to it, or "adb push/pull" to/from it.

first i need a map of your emmc. adb shell then run this and paste the output:

ls -l /dev/block/mmc*

ls -l /dev/block/platform/[whatever device name]/by-name

fdisk -l /dev/block/mmcblk0

---------- Post added at 03:25 PM ---------- Previous post was at 03:19 PM ----------

please post outputs in [ CODE ] tags so that its more readable.
[Samsung Galaxy Nexus] valkata1212:
Im doing the adb shell commands now but I have 1 question: How to find my DEVICE NAME?? im not sure what to type from all the data i get, i will wait until you respond to proceed.

EDIT: This is what i get for now:

~ # ←[6nls -l /dev/block/mmc*
ls -l /dev/block/mmc*
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
brw------- root root 179, 0 2015-02-05 15:26 mmcblk0
brw------- root root 179, 8 2015-02-05 15:26 mmcblk0boot0
brw------- root root 179, 16 2015-02-05 15:26 mmcblk0boot1
brw------- root root 179, 1 2015-02-05 15:26 mmcblk0p1
brw------- root root 259, 2 2015-02-05 15:26 mmcblk0p10
brw------- root root 259, 3 2015-02-05 15:26 mmcblk0p11
brw------- root root 259, 4 2015-02-05 15:26 mmcblk0p12
brw------- root root 259, 5 2015-02-05 15:26 mmcblk0p13
brw------- root root 179, 2 2015-02-05 15:26 mmcblk0p2
brw------- root root 179, 3 2015-02-05 15:26 mmcblk0p3
brw-rw---- radio radio 179, 4 2015-02-05 15:26 mmcblk0p4
brw------- root root 179, 5 2015-02-05 15:26 mmcblk0p5
brw------- root root 179, 6 2015-02-05 15:26 mmcblk0p6
brw------- root root 179, 7 2015-02-05 15:26 mmcblk0p7
brw------- root root 259, 0 2015-02-05 15:26 mmcblk0p8
brw-rw---- radio radio 259, 1 2015-02-05 15:26 mmcblk0p9
~ # ←[6n

~ # ←[6nls -l /dev/block/platform/
ls -l /dev/block/platform/
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x root root 2015-02-05 15:26 omap
~ # ←[6n

~ # ←[6nls -l /dev/block/platform/omap
ls -l /dev/block/platform/omap
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x root root 2015-02-05 15:26 omap2_mcspi.3
drwxr-xr-x root root 2015-02-05 15:26 omap_hsmmc.0
~ # ←[6n

~ # ←[6nfdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0

Disk /dev/block/mmcblk0: 15.7 GB, 15758000128 bytes
1 heads, 16 sectors/track, 1923584 cylinders
Units = cylinders of 16 * 512 = 8192 bytes

Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1923584 15388671+ ee EFI GPT
Partition 1 does not end on cylinder boundary
~ # ←[6n

Tell me if you need something
[Samsung Galaxy Nexus] Lanchon:
you should try all options!

but i think it is probably omap/omap_hsmmc.0

are you sure you are "fastboot boot" booting into the latest TWRP recovery before doing adb shell??? your fdisk command doesn't support GPT disks, that is very strange.

also do:

cat /proc/partitions

cat /proc/mounts

also from the pc (are you using linux or windows?):

create a PC folder and cd into it, then:

adb pull -p /dev/block/mmcblk0boot0

adb pull -p /dev/block/mmcblk0boot1

tell me the exact size of the two downloaded files. KEEP THESE FILES SAFE!
[Samsung Galaxy Nexus] valkata1212:
I can 100% confirm Im on the newest TWRP recovery version v2.8.4.0 flashed with fastboot boot x.img

And here are the results i got, and also those new commands:

~ # ←[6nls -l /dev/block/platform/omap/omap_hsmmc.0/by-name
ls -l /dev/block/platform/omap/omap_hsmmc.0/by-name
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
lrwxrwxrwx root root 2015-02-05 18:06 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-02-05 18:06 cache -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-02-05 18:06 dgs -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-02-05 18:06 efs -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-02-05 18:06 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-02-05 18:06 misc -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-02-05 18:06 param -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-02-05 18:06 radio -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-02-05 18:06 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-02-05 18:06 sbl -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-02-05 18:06 system -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-02-05 18:06 userdata -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-02-05 18:06 xloader -> /dev/block/mmcblk0p1
~ # ←[6n

~ # ←[6ncat /proc/partitions
cat /proc/partitions
major minor #blocks name

31 0 1024 mtdblock0
179 0 15388672 mmcblk0
179 1 128 mmcblk0p1
179 2 3584 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 8192 mmcblk0p7
259 0 12224 mmcblk0p8
259 1 16384 mmcblk0p9
259 2 669696 mmcblk0p10
259 3 442368 mmcblk0p11
259 4 14198767 mmcblk0p12
259 5 64 mmcblk0p13
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
~ # ←[6n

~ # ←[6ncat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,seclabel,relatime 0 0
/dev/block/mmcblk0p11 /cache ext4 rw,seclabel,relatime,user_xattr,barrier=1,data
=ordered 0 0
/dev/block/mmcblk0p12 /data ext4 rw,seclabel,relatime,user_xattr,barrier=1,data=
ordered 0 0
/dev/block/mmcblk0p12 /sdcard ext4 rw,seclabel,relatime,user_xattr,barrier=1,dat
a=ordered 0 0
~ # ←[6n

AND THIS IS WHAT I GET WHEN I TRIED TO PULL THE FILES U ASKED: (both mmcblk0boot0/1)

E:\WugFresh Development\Nexus Root Toolkit\data\MMC>adb pull -p /dev/block/mmcbl
k0boot0
remote object '/dev/block/mmcblk0boot0' not a file or directory
[Samsung Galaxy Nexus] Lanchon:
lol please repeat:

ls -l /dev/block/platform/omap/omap_hsmmc.0/by-name

using a wider terminal so that the output can be read :)

your partitions are:

major minor #blocks name

31 0 1024 mtdblock0
179 0 15388672 mmcblk0
179 1 128 mmcblk0p1 xloader
179 2 3584 mmcblk0p2 sbl
179 3 20480 mmcblk0p3 efs
179 4 8192 mmcblk0p4 param
179 5 4096 mmcblk0p5 misc
179 6 4096 mmcblk0p6 dgs
179 7 8192 mmcblk0p7 boot
259 0 12224 mmcblk0p8 recovery
259 1 16384 mmcblk0p9 radio
259 2 669696 mmcblk0p10 system
259 3 442368 mmcblk0p11 cache
259 4 14198767 mmcblk0p12 userdata
259 5 64 mmcblk0p13 metadata
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0

---------- Post added at 03:34 PM ---------- Previous post was at 03:28 PM ----------

cat /proc/mtd

cat /proc/emmc

dd if=/dev/block/mmcblk0boot0 of=/tmp/mmcblk0boot0

dd if=/dev/block/mmcblk0boot1 of=/tmp/mmcblk0boot1

from the PC:

adb pull /tmp/mmcblk0boot0

adb pull /tmp/mmcblk0boot1

---------- Post added at 03:36 PM ---------- Previous post was at 03:34 PM ----------

get the latest philz touch recovery for gnex. fastboot boot into it, then try this again:

fdisk -l /dev/block/mmcblk0
[Samsung Galaxy Nexus] valkata1212:
~ # ←[6ncat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00001000 "w25q80"
~ # ←[6n

hmm :?

~ # ←[6ncat /proc/emmc
cat /proc/emmc
cat: can't open '/proc/emmc': No such file or directory
~ # ←[6n

I downloaded and fastboot booted latest phillz and i did the command again, but the resault is the same:

~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0

Disk /dev/block/mmcblk0: 15.7 GB, 15758000128 bytes
1 heads, 16 sectors/track, 1923584 cylinders
Units = cylinders of 16 * 512 = 8192 bytes

Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1923584 15388671+ ee EFI GPT
Partition 1 does not end on cylinder boundary
~ #

So i pulled both mmcblk files, they are 2,048 KB each.
[Samsung Galaxy Nexus] Lanchon:
this is going to be redundant, buy do it just in case:

adb pull -p /dev/block/mmcblk0p##

where ## is 1 to 9 and 13 (skip 10, 11, 12)
[Samsung Galaxy Nexus] valkata1212:
Done. had to do the trick with dd if=/dev/block/mmcblk0p of=/tmp/mmcblk0p first then adb pull /tmp/mmcblk0p, but i got the files now, their size range are from 64 KB to 20,480 KB (largest one)

Whats next:?
[Samsung Galaxy Nexus] Lanchon:
EDIT: first reboot into clean latest TWRP

dd if=/dev/block/mmcblk0 of=/tmp/mmcblk0-beg bs=1M count=96

dd if=/dev/block/mmcblk0 of=/tmp/mmcblk0-end bs=1M skip=15000

from the PC:

adb pull -p /tmp/mmcblk0-beg

adb pull -p /tmp/mmcblk0-end

beg should be 96MB

end should be 28MB

verify, that on the PC.

DO NOT REBOOT THE PHONE FROM THIS POINT FORWARD!

we want those files in the ramdrive
[Samsung Galaxy Nexus] valkata1212:
downloaded beg and i confirm its 98 MB but i have a problem with END, it doesnt want to copy it im tmp, i deleted the "skip=15000 part" and it came out 250 MB!! but couldnt pull it cuz it game me "no space left on device"

What should i do? Reboot and do this again or ?
[Samsung Galaxy Nexus] Lanchon:
reboot

redo first dd

no need to pull again

redo second dd, and tell me the error message or whatever it outputs. form now on, i recommend you dont try to fix things without posting first, one error can mean BRICK.
[Samsung Galaxy Nexus] valkata1212:
E:\WugFresh Development\Nexus Root Toolkit\data\MMC>adb shell
~ # ←[6ndd if=/dev/block/mmcblk0 of=/tmp/mmcblk0-end bs=1M skip=15000
dd if=/dev/block/mmcblk0 of=/tmp/mmcblk0-end bs=1M skip=15000

It doesnt start the operation dont know why, just like the first time i did. Beg finished for 2-3 sec but -end just doesnt show up. :rolleyes:
[Samsung Galaxy Nexus] Lanchon:
you are saying:

-no error displayed

-no file created

?

does the phone stop responding?
[Samsung Galaxy Nexus] valkata1212:
yes correct no display error nor file created, BUT PHONE WORKS I ACCESS EVERYTHING ON RECOVERY, as i said when i tried the first time and deleted the skip=15000 then it created a file. I just suggest, when thinking logically if the -beg file is "count=96" why cant we type "count=28" on -end. Im just suggesting, i dont understand it, it may be just problem in the command.
[Samsung Galaxy Nexus] Lanchon:
no.

try the same command with skip=15027 (should create 1M file)

if it doesnt work, try skip=14976 (52MB file)

if it doesnt work, i assume something must be wrong with dd and is unable to handle files bigger than 4GB. we will have to proceed without backing up the backup GPT partition table (but we have the main one backed up, i can only hope that is enough).

---------- Post added at 06:07 PM ---------- Previous post was at 06:00 PM ----------

i will need to leave in about 30 minutes.

lets try to wrap this up
[Samsung Galaxy Nexus] valkata1212:
No result, lets hope its not that important, in the mean time i will reboot again and to the beg file again while ur not here.
[Samsung Galaxy Nexus] Lanchon:
no need.

unmount all partitions from the recovery menu.

download this file:

https://github.com/Hashcode/mmc-utils/blob/master/mmc_utils?raw=true

adb push mmc_utils /sbin

adb push mmcblk0boot0, mmcblk0boot1 and mmcblk0p13 files to /tmp

FROM NOW ON, IF YOU REBOOT YOUR PHONE YOU ARE DEAD

adb shell

mmc_utils vendor 0 /dev/block/mmcblk0

# (wait about a minute)

mmc_utils vendor 1 /dev/block/mmcblk0

# (wait another minute)

now your emmc could be completely wiped, reboot will BRICK. or your emmc might have ignored the commands... :(

pull boot0 again, it should read ok but be all zeroes probably. check the size, it should be the same as before.

if it doesnt read (throws error), you might try:

mmc_utils vendor 2 /dev/block/mmcblk0
# (wait another minute)

and retry. if error again:

mmc_utils vendor 4 /dev/block/mmcblk0
# (wait another minute)

and retry.

if it reads ok but is not cleared, try pulling any main partition again (p1, p2, one that wasnt read and cached by the kernel in this boot), it should be all zeroes. otherwise, probably the emmc ignored the commands... :(

if all is ok....

restore the boots:

adb shell

echo 0 > /sys/block/mmcblk0boot0/force_ro

echo 0 > /sys/block/mmcblk0boot1/force_ro

dd if=/tmp/mmcblk0boot0 of=/dev/block/mmcblk0boot0

dd if=/tmp/mmcblk0boot1 of=/dev/block/mmcblk0boot1

if dd fails (cant write), try repeating replacing "force_ro" with "ro"

restore the partition table and normal partitions:

dd if=/tmp/mmcblk0-beg of=/dev/block/mmcblk0 bs=1M count=96

dd if=/tmp/mmcblk0-end of=/dev/block/mmcblk0 bs=1M seek=15000

# watch it! it says seek=, not skip= now!

restore p13:

dd if=/tmp/mmcblk0p13 of=/dev/block/mmcblk0p13

we should be done if no errors anywhere.

you can now try to pull partitions to check. (note that recently written areas will be cached in ram, not read from the device. lets hope the device unlocked from read-only after the reset!) if you reboot and something was wrong, your device is BRICKED.

---------- Post added at 06:24 PM ---------- Previous post was at 06:22 PM ----------

whatever you do, do not reboot your phone until you are finished. And do not try stuff without consulting me!
[Samsung Galaxy Nexus] valkata1212:
I started the operation but reached adb shell part and got access denied??

E:\WugFresh Development\Nexus Root Toolkit\data>adb push mmc_utils /sbin
1769 KB/s (88004 bytes in 0.048s)

E:\WugFresh Development\Nexus Root Toolkit\data>adb push mmcblk0boot0 /tmp
cannot stat 'mmcblk0boot0': No such file or directory

E:\WugFresh Development\Nexus Root Toolkit\data>cd mmc

E:\WugFresh Development\Nexus Root Toolkit\data\MMC>adb push mmcblk0boot0 /tmp
3472 KB/s (2097152 bytes in 0.589s)

E:\WugFresh Development\Nexus Root Toolkit\data\MMC>adb push mmcblk0boot1 /tmp
3537 KB/s (2097152 bytes in 0.579s)

E:\WugFresh Development\Nexus Root Toolkit\data\MMC>adb push mmcblk0p13 /tmp
3028 KB/s (65536 bytes in 0.021s)

E:\WugFresh Development\Nexus Root Toolkit\data\MMC>adb shell
~ # ←[6nmmc_utils vendor 0 /dev/block/mmcblk0
mmc_utils vendor 0 /dev/block/mmcblk0
/sbin/sh: mmc_utils: Permission denied
~ # ←[6n
[Samsung Galaxy Nexus] Lanchon:
in adb shell:

chmod +x /sbin/mmc_utils
[Samsung Galaxy Nexus] valkata1212:
Started extracting boot0 and recived this:

~ # ←[6ndd if=/dev/block/mmcblk0boot0 of=/tmp/mmcblk0boot0
dd if=/dev/block/mmcblk0boot0 of=/tmp/mmcblk0boot0
4096+0 records in
4096+0 records out
2097152 bytes (2.0MB) copied, 0.131897 seconds, 15.2MB/s
~ # ←[6nadb pull /tmp/mmcblk0boot0
adb pull /tmp/mmcblk0boot0
/sbin/sh: adb: not found
~ # ←[6n
[Samsung Galaxy Nexus] Lanchon:
man, the adb commands must be run from the pc side, you did this already
[Samsung Galaxy Nexus] valkata1212:
everything that i done till now i did on the PC in cmd, i havent touched the terminal on the phone itself.
[Samsung Galaxy Nexus] Lanchon:
after you do adb shell, you ARE in the terminal of the phone itself, only remotely.

open a new PC window to do the abd pull/push commands

---------- Post added at 07:14 PM ---------- Previous post was at 07:12 PM ----------

the adb executable only exists on the PC. all adb commands must be run on the PC shell.

once you do an adb shell, that window turns into a remote shell into the phone (until you type exit or the connection is broken). adb shell is the equivalent of telneting into the phone.
[Samsung Galaxy Nexus] valkata1212:
OK, i got it, here it is without anny erros given, check and confirm:

E:\WugFresh Development\Nexus Root Toolkit\data>cd novo

E:\WugFresh Development\Nexus Root Toolkit\data\novo>adb pull /tmp/mmcblk0bo
3783 KB/s (2097152 bytes in 0.541s)

E:\WugFresh Development\Nexus Root Toolkit\data\novo>adb shell
~ # ←[6necho 0 > /sys/block/mmcblk0boot0/force_ro
echo 0 > /sys/block/mmcblk0boot0/force_ro
~ # ←[6necho 0 > /sys/block/mmcblk0boot1/force_ro
echo 0 > /sys/block/mmcblk0boot1/force_ro
~ # ←[6ndd if=/tmp/mmcblk0boot0 of=/dev/block/mmcblk0boot0
dd if=/tmp/mmcblk0boot0 of=/dev/block/mmcblk0boot0
4096+0 records in
4096+0 records out
2097152 bytes (2.0MB) copied, 0.580200 seconds, 3.4MB/s
~ # ←[6ndd if=/tmp/mmcblk0boot1 of=/dev/block/mmcblk0boot1
dd if=/tmp/mmcblk0boot1 of=/dev/block/mmcblk0boot1
4096+0 records in
4096+0 records out
2097152 bytes (2.0MB) copied, 0.586975 seconds, 3.4MB/s
~ # ←[6ndd if=/tmp/mmcblk0-beg of=/dev/block/mmcblk0 bs=1M count=96
dd if=/tmp/mmcblk0-beg of=/dev/block/mmcblk0 bs=1M count=96
96+0 records in
96+0 records out
100663296 bytes (96.0MB) copied, 3.567596 seconds, 26.9MB/s
~ # ←[6ndd if=/tmp/mmcblk0p13 of=/dev/block/mmcblk0p13
dd if=/tmp/mmcblk0p13 of=/dev/block/mmcblk0p13
128+0 records in
128+0 records out
65536 bytes (64.0KB) copied, 0.017884 seconds, 3.5MB/s
~ # ←[6n
[Samsung Galaxy Nexus] Lanchon:
everything looks alright! what happened with the new boot0 you pulled? what size is it? is it all zeroes, or is it the same content as the boot0 you had pulled before?
[Samsung Galaxy Nexus] valkata1212:
the same size of the one before
[Samsung Galaxy Nexus] Lanchon:
and the contents? windows you can use fc to compare. linux cmp -b

---------- Post added at 07:27 PM ---------- Previous post was at 07:26 PM ----------

or any hex editor you may have installed
[Samsung Galaxy Nexus] valkata1212:
i dont understand this one?? can u explain here please
[Samsung Galaxy Nexus] Lanchon:
compare the contents of the boot0 file that you previously pulled with the one you just recently pulled. see if they are different.

us the fc or cmp -b commands
[Samsung Galaxy Nexus] valkata1212:
how to execute this command? i hear it for the first time
[Samsung Galaxy Nexus] Lanchon:
WAIT THERE IS IS A PROBLEM!!!

you pushed boot0 to tmp/

then you pulled the new boot0 OVERWRITING the file you pushed because you used the same temporary filename in /tmp!!!

then you flashed the wrong boot0.

you need to

1) push boot0 to tmp again, BUT THE FIRST BOOT0 YOU PULLED TO THE PC, not the second

2) in adb shell:

dd if=/tmp/mmcblk0boot0 of=/dev/block/mmcblk0boot0

---------- Post added at 07:37 PM ---------- Previous post was at 07:35 PM ----------

in the PC you have 2 boot0 files:

the one you pulled first and the one you pulled last.

I STILL DONT KNOW IF YOU HAVE A WINDOWS OR LINUX PC!

on a linux pc, compare the 2 files like this:

cmp -b fileA fileB
[Samsung Galaxy Nexus] valkata1212:
Pushing ORIGINAL boot0

E:\WugFresh Development\Nexus Root Toolkit\data>cd mmc

E:\WugFresh Development\Nexus Root Toolkit\data\MMC>adb push mmcblk0boot0 /tmp
3389 KB/s (2097152 bytes in 0.604s)

E:\WugFresh Development\Nexus Root Toolkit\data\MMC>adb shell
~ # ←[6ndd if=/tmp/mmcblk0boot0 of=/dev/block/mmcblk0boot0
dd if=/tmp/mmcblk0boot0 of=/dev/block/mmcblk0boot0
4096+0 records in
4096+0 records out
2097152 bytes (2.0MB) copied, 0.601410 seconds, 3.3MB/s
~ # ←[6n

I said on the FIRST POST EVER MADE, I have Windows 8.1 PC.
[Samsung Galaxy Nexus] Lanchon:
great, try:

fc /?

i think fc /b is the switch for binary mode. if so:

fc /b file1 file2

to compare the two boot0 files
[Samsung Galaxy Nexus] valkata1212:
bad news

E:\WugFresh Development\Nexus Root Toolkit\data>cd novo

E:\WugFresh Development\Nexus Root Toolkit\data\novo>fc /b mmcblk0boot0 mmcblk0b
oot0_2
Comparing files mmcblk0boot0 and MMCBLK0BOOT0_2
FC: no differences encountered

E:\WugFresh Development\Nexus Root Toolkit\data\novo>
[Samsung Galaxy Nexus] Lanchon:
yes, bad news, but there is still the small chance that the reset was done and did not affect boot0. boot are very special partitions.

recommend that you:

1) reboot to fastboot mode

2) fastboot flash recovery some-recovery.img

3) then boot into the newly flashed recovery and check if it was actually written to the emmc, or the old recovery is still there
[Samsung Galaxy Nexus] valkata1212:
:((( bad news fastboot flash recovery x.img sucsesfull rebooted to recovery mode and again old recovery version is still there...

Im going to sleep now, thanks for the instructions, i really appreciate it, if its not a problem we can continue tomorrow. :good:
[Samsung Galaxy Nexus] Lanchon:
sorry to hear that.

there's nothing else to do: the emmc reset attempt failed. you need a new motherboard :(
[Samsung Galaxy Nexus] valkata1212:
it maybe not owrking cuz probably i did something wrong, i could do it again today(now experienced) i see what happens.