• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Cant Unlock, Unknown serial. ADB problems

Is this what you were thinking SA? Basically just pointing to the JB location in the 3rd command series?


adb shell
su
cd /data/local

ssn="1234567890AB" # replace the values in quotes with your 12-byte serial number
echo "trace: $ssn"

dd ibs=1 count=17 if=/sys/devices/platform/cardhu_chipid of=chipid
echo "trace: see if we extracted 17 bytes from the chipid file"
ls -al chipid

mkdir -m 0777 /Removable/p5
echo "trace: verify creation of new directory"
ls -ald /Removable/p5

mount -o remount,rw -t vfat /dev/block/mmcblk0p5 /Removable/p5
echo "trace: verify that new mount worked"
mount

echo -n "$ssn" > /Removable/p5/SSN
echo "trace: verify new SSN file"
ls -al /Removable/p5/SSN

cat chipid > /Removable/p5/UUID
echo "trace: verify new UUID file"
ls -al /Removable/p5/UUID

umount /Removable/p5

exit # exit the secure (su) shell
exit # exit the non-root shell


@miskas, advise waiting to get the green light (or not) from SA before moving forward. I know he's subscribed with updates to this thread so he'll see this in a few.
 
Upvote 0
Looks good to me, IBT, as long as that is the location of the cardhu_chipid file (I wasn't 100% sure, but I'm sure jhawkkw and/or miskas could verify and/or adjust as needed).

Also, I was going to use the mount command listed in the XDA thread that jhawkkw referenced earlier:

I.e., replacing this:

mount -o remount,rw -t vfat /dev/block/mmcblk0p5 /Removable/p5

with this:

mount -t vfat /dev/block/mmcblk0p5 /Removable/p5

Here's yours with my update:

adb shell
su
cd /data/local

ssn="C7OKASQR00JW" # set this to your 12-byte serial number

dd ibs=1 count=17 if=/sys/devices/platform/cardhu_chipid of=chipid
echo "trace: see if we extracted 17 bytes from the chipid file"
ls -al chipid

mkdir -m 0777 /Removable/p5
echo "trace: verify creation of new directory"
ls -ald /Removable/p5

mount -t vfat /dev/block/mmcblk0p5 /Removable/p5
echo "trace: verify that new mount worked"
mount

echo -n "$ssn" > /Removable/p5/SSN
echo "trace: verify new SSN file"
ls -al /Removable/p5/SSN

cat chipid > /Removable/p5/UUID
echo "trace: verify new UUID file"
ls -al /Removable/p5/UUID

umount /Removable/p5

exit # exit the secure (su) shell
exit # exit the non-root shell

Look okay / sound good? :)
 
Upvote 0
Looks good to me, IBT, as long as that is the location of the cardhu_chipid file (I wasn't 100% sure, but I'm sure jhawkkw and/or miskas could verify and/or adjust as needed).

Also, I was going to use the mount command listed in the XDA thread that jhawkkw referenced earlier:

I.e., replacing this:



with this:



Here's yours with my update:



Look okay / sound good? :)

Yeah, the cardhu-chipid is in the same directory where the backup version should have been, so it should be fine.
 
Upvote 0
"C:\Users\adam\Downloads\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>ad
b shell
shell@android:/ $ su
su
root@android:/ # cd /data/local
cd /data/local
root@android:/data/local # ssn=C7OKASQR00JW
ssn=C7OKASQR00JW
root@android:/data/local # dd ibs=1 count=17 if=/sys/devices/platform/cardhu_mis
c/cardhu_chipid
devices/platform/cardhu_misc/cardhu_chipid <
015c7b47ea100a17
17+0 records in
0+1 records out
17 bytes transferred in 0.002 secs (8500 bytes/sec)
root@android:/data/local # echo trace:
echo trace:
trace:
root@android:/data/local # ls -al chipid
ls -al chipid
chipid: No such file or directory
1|root@android:/data/local # mkdir -m 0777 /Removable/p5
mkdir -m 0777 /Removable/p5
mkdir failed for -m, File exists
255|root@android:/data/local # echo trace:
echo trace:
trace:
root@android:/data/local # ls -ald /Removable/p5
ls -ald /Removable/p5
/Removable/p5: No such file or directory
1|root@android:/data/local # mount -t vfat /dev/block/mmcblk0p5 /Removable/p5
mount -t vfat /dev/block/mmcblk0p5 /Removable/p5
mount: No such file or directory
255|root@android:/data/local # echo trace:
echo trace:
trace:
root@android:/data/local # mount
mount
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p1 /system ext4 rw,relatime,user_xattr,acl,barrier=1,data=orde
red 0 0
/dev/block/mmcblk0p2 /cache ext4 rw,nosuid,nodev,noatime,errors=panic,user_xattr
,acl,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/mmcblk0p8 /data ext4 rw,nosuid,nodev,noatime,errors=panic,user_xattr,
acl,barrier=1,nomblk_io_submit,data=ordered 0 0
tmpfs /Removable tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1
023,default_permissions,allow_other 0 0
/dev/block/vold/179:49 /Removable/MicroSD vfat rw,dirsync,relatime,uid=1000,gid=
1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8,errors=remount-ro 0 0
root@android:/data/local # echo -n "$ssn" > /Removable/p5/SSN
echo -n "$ssn" > /Removable/p5/SSN
sh: can't create /Removable/p5/SSN: No such file or directory
1|root@android:/data/local # echo trace:
echo trace:
trace:
root@android:/data/local # ls -al /Removable/p5/SSN
ls -al /Removable/p5/SSN
/Removable/p5/SSN: No such file or directory
1|root@android:/data/local #

1|root@android:/data/local # cat chipid > /Removable/p5/UUID
cat chipid > /Removable/p5/UUID
sh: can't create /Removable/p5/UUID: No such file or directory
1|root@android:/data/local # echo trace:
echo trace:
trace:
root@android:/data/local # ls -al /Removable/p5/UUID
ls -al /Removable/p5/UUID
/Removable/p5/UUID: No such file or directory
1|root@android:/data/local # umount /Removable/p5
umount /Removable/p5
failed: No such file or directory
1|root@android:/data/local # exit
exit
1|shell@android:/ $ exit
exit

C:\Users\adam\Downloads\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>"

rebooted and no luck. but there was quite a few errors that happened along the way.
Also you forgot a path its "platform/cardhu_misc/card_hu" just forgot the "cardhu_misc" but i noticed and fixed it
 
Upvote 0
i also would like to know why my serial # is showing as the 16 digit chiphu number?

miskas,

I went-ahead and plugged-in the serial # you provided earlier in this thread when you first tried the commands if that's what you are asking.

Also, are you copying and pasting the commands from the post above or hand-typing them? (your dd command doesn't look right and is the first error reported that much of the rest of the commands rely upon).

If you could carefully copy and paste the above commands one at a time and stop if you get an error and let us see what is going on--don't do them all unless you are NOT getting an error / warning.

@IBT, I'm looking at your PM now...sorry for the delay :).
 
Upvote 0
C:\Users\adam\Downloads\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>ad
b shell
shell@android:/ $ su
su
root@android:/ # cd /data/local
cd /data/local
root@android:/data/local # ssn="C7OKASQR00JW"
ssn="C7OKASQR00JW"
root@android:/data/local # dd ibs=1 count=17 if=/sys/devices/platform/cardhu_mis
c/cardhu_chipid of=chipid
devices/platform/cardhu_misc/cardhu_chipid of=chipid <
17+0 records in
0+1 records out
17 bytes transferred in 0.001 secs (17000 bytes/sec)
root@android:/data/local # echo
echo

root@android:/data/local # ls -al chipid
ls -al chipid
-rwSrws--T root root 17 2013-07-10 14:16 chipid
root@android:/data/local # mkdir -m 0777 /Removable/p5
mkdir -m 0777 /Removable/p5
mkdir failed for -m, File exists
255|root@android:/data/local # echo
echo

root@android:/data/local #

root@android:/data/local # ls -ald /Removable/p5
ls -ald /Removable/p5
/Removable/p5: No such file or directory
1|root@android:/data/local #


as far as i get before an error
 
Upvote 0
SA and I have been chatting via PM and we have some ideas that MAY help to smooth up the transition through the command list. I'd like to add a couple things though...first probably goes without saying but although we're doing our best to help here with careful forethought, you are ultimately responsible for the decision to move forward. In other words, "user assumes all risk". :D

Also, again it may be wise to move forward one at a time and report the outcomes as SA noted in his previous post. I assume we may get the error for recreation of Removable/p5 but I left in there anyway, should be no harm there.

adb shell
su
cd /data/local

ssn="C7OKASQR00JW" # set this to your 12-byte serial number

dd ibs=1 count=17 if=/sys/devices/platform/cardhu_misc/cardhu_chipid of=chipid
echo "trace: see if we extracted 17 bytes from the chipid file"
cd /sys/devices/platform/cardhu_misc/cardhu_chipid
ls -al

cd /dev/block/mmcblk0p5/
mkdir -m 0777 -p /Removable/p5
echo "trace: verify creation of new directory"
cd /dev/block/mmcblk0p5/Removable/p5
ls -ald

mount -t vfat /dev/block/mmcblk0p5 /Removable/p5
echo "trace: verify that new mount worked"
mount

echo -n "$ssn" > /Removable/p5/SSN
echo "trace: verify new SSN file"
ls -al /Removable/p5/SSN

cat chipid > /Removable/p5/UUID
echo "trace: verify new UUID file"
ls -al /Removable/p5/UUID

umount /Removable/p5

exit # exit the secure (su) shell
exit # exit the non-root shell

edit: added SA's addition of -p to mkdir command. Mentioned in next post, edited here to keep this the working list.
 
Upvote 0
C:\Users\adam\Downloads\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>ad
b shell
shell@android:/ $ su
su
root@android:/ # cd /data/local
cd /data/local
root@android:/data/local # ssn=C7OKASQR00JW
ssn=C7OKASQR00JW
root@android:/data/local # dd ibs=1 count=17 if=/sys/devices/platform/cardhu_mis
c/cardhu_chipid of=chipid
devices/platform/cardhu_misc/cardhu_chipid of=chipid <
17+0 records in
0+1 records out
17 bytes transferred in 0.001 secs (17000 bytes/sec)
root@android:/data/local # echo trace
echo trace
trace
root@android:/data/local # cd /sys/devices/platform/cardhu_misc/cardhu_chipid
cd /sys/devices/platform/cardhu_misc/cardhu_chipid
sh: cd: /sys/devices/platform/cardhu_misc/cardhu_chipid: Not a directory
2|root@android:/data/local #

im getting this error
 
Upvote 0
sh: cd: /sys/devices/platform/cardhu_misc/cardhu_chipid: Not a directory



I thought we determined that to be the existing location? :hmmmm:

Could you use a file explorer and verify if there is indeed a directory:

/sys/devices/platform/cardhu_misc/cardhu_chipid/

or is cardhu_chipid a file within the previous directory? Dang I wish I had one of these to actually look at.
 
  • Like
Reactions: scary alien
Upvote 0
I thought we determined that to be the existing location? :hmmmm:

Could you use a file explorer and verify if there is indeed a directory:

/sys/devices/platform/cardhu_misc/cardhu_chipid/

cardhu_chipid is a file contained in the /sys/devices/platform/cardhu_misc/

My screen shot in post 51 shows the directory

Sorry, I've been preoccupied this past while.
 
Upvote 0
SA and I have been chatting via PM and we have some ideas that MAY help to smooth up the transition through the command list. I'd like to add a couple things though...first probably goes without saying but although we're doing our best to help here with careful forethought, you are ultimately responsible for the decision to move forward. In other words, "user assumes all risk". :D

Also, again it may be wise to move forward one at a time and report the outcomes as SA noted in his previous post. I assume we may get the error for recreation of Removable/p5 but I left in there anyway, should be no harm there.

adb shell
su
cd /data/local

ssn="C7OKASQR00JW" # set this to your 12-byte serial number

dd ibs=1 count=17 if=/sys/devices/platform/cardhu_misc/cardhu_chipid of=chipid
echo "trace: see if we extracted 17 bytes from the chipid file"
cd /sys/devices/platform/cardhu_misc/
ls -al

cd /dev/block/mmcblk0p5/
mkdir -m 0777 -p /Removable/p5
echo "trace: verify creation of new directory"
cd /dev/block/mmcblk0p5/Removable/p5
ls -ald

mount -t vfat /dev/block/mmcblk0p5 /Removable/p5
echo "trace: verify that new mount worked"
mount

echo -n "$ssn" > /Removable/p5/SSN
echo "trace: verify new SSN file"
ls -al /Removable/p5/SSN

cat chipid > /Removable/p5/UUID
echo "trace: verify new UUID file"
ls -al /Removable/p5/UUID

umount /Removable/p5

exit # exit the secure (su) shell
exit # exit the non-root shell



^^Give that a shot.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones