Let me start from the beginning: I got my tablet a year ago and about 5 months ago. (so its out of warranty) anyways about 8 months ago i had to send it in for a broken back camera. after a month they sent me back a new tablet and i was happy. after it came out of warranty i decided to go and root my tablet. that went fine with no problems. i wanted to see what else i could do with my tablet and i found unlocking it would open up the world of custom rom's. intrigued i looked it up and decided to unlock my tablet. after downloading the unlocker i tried to unlock it and it wouldn't unlock. after looking around at possible solutions i found out that my device had an unknown serial number. I tried using ratchet to fix it but it kept giving me the error of "device not found". when type adb devices it shows up there as connected but when i try to push the file its not. ive read it might be caused because my system directory dosen't have write permissions. any help would be greatly appreciated. Also in adb devices its listed but in adb shell its not.
Asus transformer Prime
Android 4.1.1
kernel:3.1.10-00004-gc770ddc
Build:JRO03C.US_epad-10.4.2.17-20121018
but im not locked out of my device. i still have full usage im trying to use adb push to push ratchet to my device and restore the serial so i can unlock.
but im not locked out of my device. i still have full usage im trying to use adb push to push ratchet to my device and restore the serial so i can unlock.
i tried looking through the forums and other sites amongst the web and other forum sites. but i just didn't find an answer for this particular problem with these circumstances.
i tried looking through the forums and other sites amongst the web and other forum sites. but i just didn't find an answer for this particular problem with these circumstances.
Don't worry LilBit, I moved it. Moved to the TF Prime Root forum.
I use to have this device, but never encountered this error. Did you root your device using one of the old exploits? The issue could also be because the unlocker tool was originally optimized for 4.0.3 and moving to 4.1.1 cause many issues with it. One thing you could look into is one of the downgrade methods to take you back to ICS to unlock, then flash your custom recovery & rom of choice.
Don't worry LilBit, I moved it. Moved to the TF Prime Root forum.
I use to have this device, but never encountered this error. Did you root your device using one of the old exploits? The issue could also be because the unlocker tool was originally optimized for 4.0.3 and moving to 4.1.1 cause many issues with it. One thing you could look into is one of the downgrade methods to take you back to ICS to unlock, then flash your custom recovery & rom of choice.
I used motochopper on 4.1.1. downgrading wouldnt help because my serial is unknown so the unlock tool cant contact the server to download the proper unlock files. i found a solution online called ''ratchet'' and i had to adb push the files. when i went to push i got "error:device not found" even though its listed in adb devices. so this is the problem i need help with. fixing the serial so i can unlock.
Since you're rooted, why not just download the files directly to the normal internal sd and then use a root enabled file explorer like root explorer or similar to move it there manually?
Since you're rooted, why not just download the files directly to the normal internal sd and then use a root enabled file explorer like root explorer or similar to move it there manually?
You, are a genius. idk why i never thought of that. the awnser was so simple yet i never thought of doing that. thanks a million. i really really apreciate it.
You, are a genius. idk why i never thought of that. the awnser was so simple yet i never thought of doing that. thanks a million. i really really apreciate it.
You, are a genius. idk why i never thought of that. the awnser was so simple yet i never thought of doing that. thanks a million. i really really apreciate it.
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
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
I might seem sily, but I know when I tried to register my tablet, that I thought something was a zero and it turned out to be a capital O. Does your's have something similar?
I might seem sily, but I know when I tried to register my tablet, that I thought something was a zero and it turned out to be a capital O. Does your's have something similar?
Yeah i made sure to input the right one. Ive entered quite a few serial numbers and have learned the difference between the two. ive tried a few times and it still shows unknown... what to do?
"[1] + Stopped (signal) /data/local/ratchet" what does this line mean?
Yeah i made sure to input the right one. Ive entered quite a few serial numbers and have learned the difference between the two. ive tried a few times and it still shows unknown... what to do?
"[1] + Stopped (signal) /data/local/ratchet" what does this line mean?
Sorry I'm late to the party ...I haven't read all of the above goings-on, but I got a kind heads-up from jhawkkw re. this and I have a few things that might help...
I've seen that type of "[1] + Stopped (signal)" error before on Unix, but I'm guessing it's pretty-much a catch-all thing that might not help you zero-in on what is actually going on. Signal 1 means "SIGHUP 1 Term Hangup detected on controlling terminal or death of controlling process" so it's probably just telling you that the ratchet program encountered some error and died.
The semi-good news is that the ratchet.c program is actually pretty simple:
printf("\n[**] Ratchet - 'Unknown serial' fix for Asus Transformer Prime TF201.\n");
printf("[**] (C) 2012 Androidroot.mobi. All rights reserved.\n\n");
if(geteuid() != 0) {
printf("[-] This utility needs to be run as root. Ensure you have a root shell (run mempodroid?) and try again.\n");
return -1;
}
//Get the serial number as user input.
printf("[?] Enter your serial number. This is located on the packaging, and stickers on your tablet: ");
fgets(ssn,13,stdin);
//Get the ChipID from sysfs.
FILE *cardhu = fopen("/sys/devices/platform/cardhu_misc/cardhu_backup_chipid", "rb");
char chipid[17] = {0};
fgets(chipid, 17, cardhu);
fclose(cardhu);
printf("[=] Configuration data written, all done! Reboot for the changes to take effect.\n\n");
return 0;
}[/HIGH]
and you could probably fairly easily glean the proper commands to be run from the above code (using the mempodroid binary to launch said commands, of course, since the rooter is using mempodroid to gain the superuser permissions).
To me, it looks like ratchet.c is:
- getting a 13 character "ssn" from the keyboard and assigning it to a variable named ssn
- reading 17 bytes from /sys/devices/platform/cardhu_misc/cardhu_backup_chipid into a variable called chipid
- creating a directory called /Removable/p5 and securing it to 0777
- mounting /Removable/p5 to /dev/block/mmcblk0p5 as a vfat filesystem
- writing the entered (13 byte) ssn to the /Removable/p5/SSN file on the new mount point
- open the /Removable/p5/UUID file for writing
- writing the first 16 bytes of the chipid variable to the above UUID file
- unmounting the /Removable/p5 file
and that's it (other than rebooting afterwards).
This doesn't look like it would be too hard to either manually do with shell commands or create a script to do so.
Unfortunately, I don't have this device to practice/test/verify this on, but I'm hoping this might help you guys see what actually needs to be done.
Sorry I'm late to the party ...I haven't read all of the above goings-on, but I got a kind heads-up from jhawkkw re. this and I have a few things that might help...
I've seen that type of "[1] + Stopped (signal)" error before on Unix, but I'm guessing it's pretty-much a catch-all thing that might not help you zero-in on what is actually going on. Signal 1 means "SIGHUP 1 Term Hangup detected on controlling terminal or death of controlling process" so it's probably just telling you that the ratchet program encountered some error and died.
The semi-good news is that the ratchet.c program is actually pretty simple:
printf("\n[**] Ratchet - 'Unknown serial' fix for Asus Transformer Prime TF201.\n");
printf("[**] (C) 2012 Androidroot.mobi. All rights reserved.\n\n");
if(geteuid() != 0) {
printf("[-] This utility needs to be run as root. Ensure you have a root shell (run mempodroid?) and try again.\n");
return -1;
}
//Get the serial number as user input.
printf("[?] Enter your serial number. This is located on the packaging, and stickers on your tablet: ");
fgets(ssn,13,stdin);
//Get the ChipID from sysfs.
FILE *cardhu = fopen("/sys/devices/platform/cardhu_misc/cardhu_backup_chipid", "rb");
char chipid[17] = {0};
fgets(chipid, 17, cardhu);
fclose(cardhu);
printf("[=] Configuration data written, all done! Reboot for the changes to take effect.\n\n");
return 0;
}[/HIGH]
and you could probably fairly easily glean the proper commands to be run from the above code (using the mempodroid binary to launch said commands, of course, since the rooter is using mempodroid to gain the superuser permissions).
To me, it looks like ratchet.c is:
- getting a 13 character "ssn" from the keyboard and assigning it to a variable named ssn
- reading 17 bytes from /sys/devices/platform/cardhu_misc/cardhu_backup_chipid into a variable called chipid
- creating a directory called /Removable/p5 and securing it to 0777
- mounting /Removable/p5 to /dev/block/mmcblk0p5 as a vfat filesystem
- writing the entered (13 byte) ssn to the /Removable/p5/SSN file on the new mount point
- open the /Removable/p5/UUID file for writing
- writing the first 16 bytes of the chipid variable to the above UUID file
- unmounting the /Removable/p5 file
and that's it (other than rebooting afterwards).
This doesn't look like it would be too hard to either manually do with shell commands or create a script to do so.
Unfortunately, I don't have this device to practice/test/verify this on, but I'm hoping this might help you guys see what actually needs to be done.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.