Thread: [Root] Galaxy Xcover S5690 development

OP by [Only registered and activated users can see links. ] @ xda

I've finally managed to root the son of a bitch! I used the Universal GB Root kit but with a small modification: I've added the GT-S5690 phone model to the getprop statements at the beginning of the file "META-INF\com\google\android\updater-script" assuming that it should work as well on this Samsung model. Well... it did work!

Here is the patched version of Universal GB Root:
[Only registered and activated users can see links. ]
Mirror:
[Only registered and activated users can see links. ]

Here is the code (in red) that I've added to the "META-INF\com\google\android\updater-script":

Code:

       getprop("ro.product.product") == "GT-B7510" ||
       getprop("ro.product.device") == "GT-S5690" ||
       getprop("ro.build.product") == "GT-S5690"
       );

Follow >> [Only registered and activated users can see links. ]

Hello,

Any ideas about how to sim unlock this phone? I'm tlc76 from xda-developers.
I found the hash for the NCK, it is located in /dev/bml25 filesystem. The hash is 32 bytes long, so I assume that the used algorithm is SHA256 (or maybe not?). BUT, I don't know the salt!

I have two pairs of NCK<->hash:
NCK=24830530
hash=A126425F6D07A2DE4C75F169D0CBF073239EF51ECEC46BF3C71F1BD15D029C0E

NCK=00000000
hash=CAE201A8B791CA25B81B04876CACD62897883EE4C1907D2BD51D5671FEEC7562

(please ignore the spaces, they were added by the forum app)

here are some bml25 fs samples: [Only registered and activated users can see links. ]

Another way would be to change the first 2 bytes in /dev/bml25 from 01 to 00, but I do not know how to make that modification...
thank you,

the salt for this phone should be something unique in this phone.. if you compare the 00000000 hash from 2 phones you see they are not the same

so try imei / serial nr as salt

Hi there I try the Root scrypt "Universal_GB_ROOT_v5_patched_for_S5690", but it failed.
Is there an obvious reason and correction ?

Code:

--- STARTING ----
--- WAITING FOR DEVICE
--- cleaning
--- pushing zergRush"
721 KB/s (23056 bytes in 0.031s)
--- correcting permissions
--- executing zergRush

[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.

[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.

[+] Found a GingerBread ! 0x00028118
[+] Found a Samsung, running Samsung mode[*] Scooting ...
klogctl: Operation not permitted[*] Sleeping a bit (~40s)...[*] Waking ![*] Sending 149 zerglings ...
klogctl: Operation not permitted[*] Sleeping a bit (~40s)...[*] Waking ![*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
   disconnect usb cable and reconnect it
   toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
2243 KB/s (1075144 bytes in 0.468s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: Read-only file system
--- correcting permissions
Unable to chmod /system/xbin/busybox: Read-only file system
--- installing busybox
[1]   Segmentation fault      /system/xbin/bus...
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
 file system
--- cleaning
--- rebooting
ALL DONE!!!

I rooted my S5690 with [Only registered and activated users can see links. ] file for Wonder I8150 from androidbg forum (i`m from Bulgaria). Now i search way to overclock and don`t know what to do. Found some interesting files in /sys/devices/system/cpu/cpu0/ and i think they are performance info, or something like that. Files are enable_op, op and ops. But i think they can`t be used for overclock.
Thank you if you understand what i mean, because my english is not good. Thank you again if help to make overclock possible for this device.

EDIT: I cannot copy these files so i post their contain.
ops contains this:

Code:

OP:0 name:D0CS [Disabled, 3]
vcore:1250 vsram:0 xl:0 xn:0 smcfs:15 sflfs:60 hss:60 dmcfs:30 axifs:60 gcfs:60 vmfc:120 df_clk:15 power_mode:1 flag:0
OP:1 name:156M [Enabled, 0]
vcore:1250 vsram:0 xl:12 xn:1 smcfs:156 sflfs:156 hss:104 dmcfs:208 axifs:78 gcfs:156 vmfc:156 df_clk:78 power_mode:0 flag:0
OP:2 name:156M_HF [Disabled, 1]
vcore:1250 vsram:0 xl:12 xn:1 smcfs:156 sflfs:156 hss:104 dmcfs:312 axifs:78 gcfs:156 vmfc:156 df_clk:78 power_mode:0 flag:0
OP:3 name:208M_HF [Disabled, 1]
vcore:1250 vsram:0 xl:16 xn:1 smcfs:156 sflfs:156 hss:104 dmcfs:312 axifs:78 gcfs:156 vmfc:156 df_clk:78 power_mode:0 flag:0
OP:4 name:416M_VGA [Disabled, 1]
vcore:1250 vsram:0 xl:16 xn:2 smcfs:156 sflfs:156 hss:104 dmcfs:312 axifs:78 gcfs:156 vmfc:156 df_clk:78 power_mode:0 flag:0
OP:5 name:416M [Enabled, 0]
vcore:1250 vsram:0 xl:16 xn:2 smcfs:156 sflfs:208 hss:156 dmcfs:312 axifs:156 gcfs:312 vmfc:312 df_clk:78 power_mode:0 flag:0
OP:6 name:624M [Enabled, 0]
vcore:1250 vsram:0 xl:24 xn:2 smcfs:156 sflfs:312 hss:208 dmcfs:400 axifs:156 gcfs:312 vmfc:312 df_clk:78 power_mode:0 flag:0
OP:7 name:806M [Enabled, 0]
vcore:1250 vsram:0 xl:31 xn:2 smcfs:156 sflfs:312 hss:208 dmcfs:400 axifs:156 gcfs:312 vmfc:312 df_clk:78 power_mode:0 flag:0
OP:8 name:D1 [Disabled, 2]
vcore:1250 vsram:0 xl:0 xn:0 smcfs:0 sflfs:0 hss:0 dmcfs:0 axifs:0 gcfs:0 vmfc:0 df_clk:0 power_mode:2 flag:0
OP:9 name:D2 [Disabled, 2]
vcore:1250 vsram:0 xl:0 xn:0 smcfs:0 sflfs:0 hss:0 dmcfs:0 axifs:0 gcfs:0 vmfc:0 df_clk:0 power_mode:3 flag:0
OP:10 name:CG [Disabled, 2]
vcore:1250 vsram:0 xl:0 xn:0 smcfs:0 sflfs:0 hss:0 dmcfs:0 axifs:0 gcfs:0 vmfc:0 df_clk:0 power_mode:4 flag:0
OP:11 name:CUSTOM OP [Disabled, 1]
vcore:0 vsram:0 xl:24 xn:2 smcfs:156 sflfs:312 hss:208 dmcfs:400 axifs:156 gcfs:312 vmfc:312 df_clk:78 power_mode:0 flag:1
OP:12 name:BOOT OP [Disabled, 1]
vcore:0 vsram:0 xl:24 xn:2 smcfs:156 sflfs:312 hss:208 dmcfs:400 axifs:156 gcfs:312 vmfc:312 df_clk:78 power_mode:0 flag:2

I think 806M is 806MHz and vcore 1250 is 1.25V... op contains only OP:7, enable_op contains active values and change every time.

From some time now I was trying to find a way to wake up the phone from other button than POWER (just wake up, not power on/off). Yesterday I finally did it. I edited the file sec_keypad.kl located in /system/usr/keylayout as follows

key 399 GRAVE
key 158 BACK WAKE
key 102 HOME WAKE
key 139 MENU WAKE
key 107 POWER WAKE
.
.
.

In red you see what I had to add...



Now the phone wakes up when pressing either of the nexy buttons:

-power
-back key
-home
-menu

@B^4g - XCover's platform has a native speed of 1,2GHz (it is PXA968 from Marvell). It is quite seriously underclocked.. Might be for working temperature reasons, since our phones are dust and water proofed and there is actually no ventilation whatsoever.

Originally Posted by paultt

From some time now I was trying to find a way to wake up the phone from other button than POWER (just wake up, not power on/off). Yesterday I finally did it. I edited the file sec_keypad.kl located in /system/usr/keylayout as follows

key 399 GRAVE
key 158 BACK WAKE
key 102 HOME WAKE
key 139 MENU WAKE
key 107 POWER WAKE
.
.
.

In red you see what I had to add...



Now the phone wakes up when pressing either of the nexy buttons:

-power
-back key
-home
-menu

@B^4g - XCover's platform has a native speed of 1,2GHz (it is PXA968 from Marvell). It is quite seriously underclocked.. Might be for working temperature reasons, since our phones are dust and water proofed and there is actually no ventilation whatsoever.

Thanks for sharing been wondering for a while if this was possible. My power button is tempremental at best but now i can use the trusty home button. Thanks