Quote:
Originally Posted by trevoroni
Looking forward to it! Keep up the great work.
I ran rhodium-nand-seq.sh and here's what it came up with:
Code:
Command:
'/system/bin/rhodium-nand-seq.sh'
-------------
Out:
exec sh '/system/bin/rhodium-nand-seq.sh'
# exec sh '/system/bin/rhodium-nand-seq.sh'
/system/bin/rhodium-nand-seq.sh: /bin/grep: not found
[: RHOD300: unknown operand
[: RHOD210: unknown operand
[: RHOD400: unknown operand
[: RHOD500: unknown operand
CAN'T DETERMINE RHODIUM VARIANT TYPE
RHOD500
cp: can't create '/system/usr/keychars/qwerty.kcm.bin': File exists
I think the issue is that Telus phone's are Rhod500's but have a keyboard like Rhod400's... why couldn't they make life easier and only produce one version of our phones? |
oops.. this is actually my bad. The path /bin/grep exists only in recovery but not in android. I'll have to change this script so it can run on both. thanks for this. But it does recognize your variant type, so the recovery must have installed the correct ones. But if you are having failures, then the kb files themselves need updating.
So the end goal is to have you use the 400 kb right? even tho you are 500?
I can cook up a patch for you.