• 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

miskas,

Do you have a method for writing only the prescribed number of bytes to the particular files? (i.e., via some shell script command).

I personally haven't tried to figure-out a way to re-write just the bytes in question (if that's even necessary, since I don't know what the files themselves contain right now).

I think I would verify that you can use the mempodroid binary to temporarily gain you root...lemme dig-up a test command for you to try so we can verify that it's not actually a permissions issue which is causing the ratchet binary to fail.
 
Ah, sorry--I didn't realize you were already rooted, therefore you don't actually need the mempodroid portion of this...

Hmm, I'm not 100% sure of the exact commands you'll need for this (there's a reason the dev of ratchet created a C program instead of writing a script).

I can see / envision a few ways to do what you need with a few shell/script commands, but I'd need to do some testing first and validate some things (and probably have jhawkkw try some stuff out first).

So, I would hang loose at this point...there's no hurry, right? :)
 
scary alien said:
miskas,

Do you have a method for writing only the prescribed number of bytes to the particular files? (i.e., via some shell script command).

I personally haven't tried to figure-out a way to re-write just the bytes in question (if that's even necessary, since I don't know what the files themselves contain right now).

I think I would verify that you can use the mempodroid binary to temporarily gain you root...lemme dig-up a test command for you to try so we can verify that it's not actually a permissions issue which is causing the ratchet binary to fail.
Click to expand...
i dont have a method im very unfimiliar with adb and have very little knowledge
 
scary alien said:
Ah, sorry--I didn't realize you were already rooted, therefore you don't actually need the mempodroid portion of this...

Hmm, I'm not 100% sure of the exact commands you'll need for this (there's a reason the dev of ratchet created a C program instead of writing a script).

I can see / envision a few ways to do what you need with a few shell/script commands, but I'd need to do some testing first and validate some things (and probably have jhawkkw try some stuff out first).

So, I would hang loose at this point...there's no hurry, right? :)
Click to expand...
No hurry im just happy to have your help :) with this issue and i hope that other people who have this problem can fix it also :)
 
scary alien said:
Ah, sorry--I didn't realize you were already rooted, therefore you don't actually need the mempodroid portion of this...

Hmm, I'm not 100% sure of the exact commands you'll need for this (there's a reason the dev of ratchet created a C program instead of writing a script).

I can see / envision a few ways to do what you need with a few shell/script commands, but I'd need to do some testing first and validate some things (and probably have jhawkkw try some stuff out first).

So, I would hang loose at this point...there's no hurry, right? :)
Click to expand...

I don't have this device anymore unfortunately. I have the the successor, the TF700, now.
 
In the interim, it may be of value to double check the permissions on the directory that includes the ratchet file(s) via adb shell. It may not work right if the chmod command did not go through.

adb shell
cd /data/local/
ls -l

Copy/paste the cmd output if you are not sure how to read the permissions and we can sift through it and give you an answer.

edit: let's go a little deeper to see that ratchet folder. Commands edited.
 
miskas said:
aww that sucks cause i really want to unl;ock but cant because of this issue :(
Click to expand...
The file structure might be similar enough that I could test, though mine is already unlocked and running a custom stock based rom. Don't know if that will pose a problem or not.
 
iowabowtech said:
In the interim, it may be of value to double check the permissions on the directory that includes the ratchet file(s) via adb shell. It may not work right if the chmod command did not go through.

adb shell
cd /data/local/
ls -l

Copy/paste the cmd output if you are not sure how to read the permissions and we can sift through it and give you an answer.

edit: let's go a little deeper to see that ratchet folder. Commands edited.
Click to expand...
heres what i got
"-rwxr-xr-x root root 4332 2013-07-09 16:03 ratchet
drwxrwx--x shell shell 2013-07-08 13:28 tmp"
 
jhawkkw said:
I don't have this device anymore unfortunately. I have the the successor, the TF700, now.
Click to expand...

Ah, thanks, jhawkkw :).

iowabowtech said:
In the interim, it may be of value to double check the permissions on the directory that includes the ratchet file(s) via adb shell. It may not work right if the chmod command did not go through.

adb shell
ls -l

Copy/paste the cmd output if you are not sure how to read the permissions and we can sift through it and give you an answer.
Click to expand...

:congrats: Great idea / advice!

I think you can also try this if /data/local is secured from reading except when you have already run a rooted shell:

c:\> adb shell "su -c "ls -l /data/local""​

-- or --

c:\> adb shell
$ su
# ls -l /data/local​

edit: doh! too late ;) :) :p
 
What do you make of that SA? I'm having a hard time figuring out if there's some extra stuff there or if that's a file within the directory? Anyway, I'm not seeing a 755 there which was the desired permissions change no?

edit: take that back, the first one is right.
 
heres what i got

Code: 
-rwxr-xr-x root root 4332 2013-07-09 16:03 ratchet
drwxrwx--x shell shell 2013-07-08 13:28 tmp
Click to expand...

iowabowtech said:
What do you make of that SA? I'm having a hard time figuring out if there's some extra stuff there or if that's a file within the directory? Anyway, I'm not seeing a 755 there which was the desired permissions change no?
Click to expand...

I think miskas' ratchet file is properly secured...I did a little test:

Code: 
root@android:/ # cd /data/local
cd /data/local
root@android:/data/local # touch test-ratchet
touch test-ratchet
root@android:/data/local # ls -a -l test-ratchet
ls -a -l test-ratchet
-rw-rw-rw- root     root            0 2013-07-09 21:39 test-ratchet
root@android:/data/local # chmod 0755 test-ratchet
chmod 0755 test-ratchet
root@android:/data/local # ls -a -l test-ratchet
ls -a -l test-ratchet
-rwxr-xr-x root     root            0 2013-07-09 21:39 test-ratchet
root@android:/data/local #

So we've got "-rwxr-xr-x" for both miskas' and my test file above :thumbup:.
 
where does this bring us?

btw if your wondering how i thought of this username i just turned the "W" and removed the "h" is whiskas the cat food lo
 
miskas said:
where does this bring us?

btw if your wondering how i thought of this username i just turned the "W" and removed the "h" is whiskas the cat food lo
Click to expand...

Nice! :)

miskas, lemme spend a little time researching some shell commands you might use in place of the ratchet program.

If you can (and if jhawkkw doesn't think this is a file with personal information in it), can you pull and post this file?

c:\> adb pull /sys/devices/platform/cardhu_misc/cardhu_backup_chipid miskas-chipid
Click to expand...

If that doesn't work, then you might have to do this:

c:\> adb shell
$ su
# cp /sys/devices/platform/cardhu_misc/cardhu_backup_chipid /sdcard/miskas-chipid
c:\> exit
c:\> adb pull /sdcard/miskas-chpid miskas-chpid
Click to expand...

Then you could post-up that miskas-chipid file here (you'll probably have to put it in a .zip file) or you could email it to me (scary.alien@gmail.com). No worries if you're not comfortable using email :).

I'd like to try to re-create / test the commands on my phone first.
 
miskas said:
Its good so far except when i enter my serial this happens

"[**] Ratchet - 'Unknown serial' fix for Asus Transformer Prime TF201.
[**] (C) 2012 Androidroot.mobi. All rights reserved.

[?] Enter your serial number. This is located on the packaging, and stickers on
your tablet: ***********
**********
[1] + Stopped (signal) /data/local/ratchet
root@android:/ #"
then i reboot and no dice please help
Click to expand...

Was checking THIS out just now and noticed they went so far as to make a point of the all caps thing.

This is where the magic happens. Make sure you enter your serial number correctly, all in caps!
Click to expand...

Probably a silly question, but you did the all caps thing right?
 
Yes I made sure to do the all caps thing right :) and scary alien my tablet dead and my laptop is installing updates -_- but I get up around 7am so ill email you those files bright and early and I will also post them here for the other members. Ps: I'm in the eastern time zone so its 10:13 here.
 
miskas said:
Yes I made sure to do the all caps thing right :) and scary alien my tablet dead and my laptop is installing updates -_- but I get up around 7am so ill email you those files bright and early and I will also post them here for the other members. Ps: I'm in the eastern time zone so its 10:13 here.
Click to expand...

No worries...I'm on Eastern time, too (Indianapolis) :).

I just want to carefully try to craft some commands for you to try that I think and hope will work for.

No hurry.
 
One more question to anyone who knows. This fix is from about 1.5 years ago. What is your tablet running for an OS version vs. what this tablet was running at that time?
 
iowabowtech said:
One more question to anyone who knows. This fix is from about 1.5 years ago. What is your tablet running for an OS version vs. what this tablet was running at that time?
Click to expand...
When the TF201 launched, it had 3.2.2 I believe, if not that it was a different 3.2.X. The unlock tool got released after the tablet got updated to 4.0.3. That's when most people started realizing this bug. The OP is now on 4.1.1

I'm on the Eastern zone as well, NY. Totally get it.
 
jhawkkw said:
When the TF201 launched, it had 3.2.2 I believe, if not that it was a different 3.2.X. The unlock tool got released after the tablet got updated to 4.0.3. That's when most people started realizing this bug. The OP is now on 4.1.1

I'm on the Eastern zone as well, NY. Totally get it.
Click to expand...

Reason for asking was primarily that Jellybean brought with it some file stucture changes that could affect the command set. However, after reviewing the code, it's looking to me like everything may be occuring at the root directory. At first I wondered if it would be writing any temp info to a card or internal partition but that doesn't appear to be the case. If so, the newer android version might be a non issue.
 
Okay miskas, I'd like for jhawkkw and IBT to review what I've got below for you to see if these commands seem to mirror what the ratchet.c program does (I also added a bunch of commands for miskas to enter while trying these so we can verify them one at a time).

So, miskas, don't enter these commands yet until we get consensus that it looks viable to the other guys.

I'm pretty confident in everything except the mount command, but feel pretty good about it all.


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_misc/cardhu_backup_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
Click to expand...

Lemme know what you guys think.

Cheers!
 
You must log in or register to reply here.
Back
Top Bottom