#Smartphone recovery pro v1..0.0.5 install
#Smartphone recovery pro v1..0.0.5 serial
#Smartphone recovery pro v1..0.0.5 driver
#Smartphone recovery pro v1..0.0.5 android
#Smartphone recovery pro v1..0.0.5 Pc

Sometimes the orange LED did not light-up when the power adapter was plugged sometimes a crazy loop of messages charger plugged - charger unplugged begun, which can result in phone crash. Link/ether ba:59:39:c0:bd:e1 brd ff:ff:ff:ff:ff:ff # ip route showĭefault via 10.200.148.163 dev ccmni0 scope linkġ0.200.148.163 dev ccmni0 scope link Charging problem: disassembling the G9000Īfter three months of use, the phone started suffering from charging problem. Link/ether 2a:9a:3b:cc:26:60 brd ff:ff:ff:ff:ff:ffĩ: ccmni2: mtu 1500 qdisc noop state DOWN qlen 1000 Link/ether b6:bb:e4:c9:8d:54 brd ff:ff:ff:ff:ff:ffĤ: tunl0: mtu 1480 qdisc noop state DOWNĦ: ip6tnl0: mtu 1452 qdisc noop state DOWNħ: ccmni0: mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000 Link/ether 46:2a:bc:c3:79:5b brd ff:ff:ff:ff:ff:ffģ: ifb1: mtu 1500 qdisc noop state DOWN qlen 32 This is the state with data connection enabled, WiFi # ip addr showġ: lo: mtu 16436 qdisc noqueue state UNKNOWN The storage is based on EMMC (Embedded MultiMedia Card): dev/block/vold/179:8 /mnt/secure/asec vfat dev/block/vold/179:8 /mnt/media_rw/sdcard0 vfat

The three partitions of 3.9 Gb are really the same device, just check the mounted /system /data /cache /protect_f /protect_s ext4 With root permission you can see the # blockdev -getsize64 /dev/block/mmcblk0 The device is advertised as per 16 Gb of storage space, but even without root permission you can see that something is different (in the $ cat /proc/partitions I don't know an offical repository for the driveres, here you can find an unverified archive: MT6577 USB VCOM drivers.rar.ģ.87 Gb of /storage/sdcard0 (Phone Storage)

#Smartphone recovery pro v1..0.0.5 driver

Once the driver are installed, the preloader device is displayed as MediaTek PreLoader USB VCOM Port.

#Smartphone recovery pro v1..0.0.5 install

MS-Windows users can install the required drivers in the little time the device appears: start the Device Manager (from Computer properties), attach the USB cable and wait until the MT65xx Preloader appears, quickly right-click on it and provide the drivers you downloaded. usb 5-5: USB disconnect, device number 8 cdc_acm 5-5:1.1: ttyACM0: USB ACM device usb 5-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 5-5: New USB device found, idVendor=0e8d, idProduct=2000

#Smartphone recovery pro v1..0.0.5 serial

The kernel registers the activation/deactivation of the serial interface in its log:ġ7982.380087] usb 5-5: new high-speed USB device number 8 using ehci-pci This is the lsusb output during the time the interface is exposed:īus 005 Device 007: ID 0e8d:2000 MediaTek Inc.

#Smartphone recovery pro v1..0.0.5 Pc

A communication interface is activated just for a few seconds (2 or so), the MT65xx device will keep the communication interface alive longer (as long as required) if it detects a data flow from the PC (Example: from SP Flash Tool). To activate this mode: turn off the device, remove the battery, and connect the USB cable to a PC (removing the battery is not strictly required). See this post: SP Flash Tool + MediaTek MT65xx.ĭevices based on the MT65xx chip can be put in Download Mode, a state in which the flash memory can be formatted and reprogrammed. It seems that the safe procedure is to edit the files with correct values.ĪnTuTu benchmark v5.1.5 is cheated by the fake RAM amount, but not in the overall scores it reports a scores of about 22400 even after getting rid of fakes. WARNING: Do not remove that files! Someones ( here and here) reported that the phone was bricked after removing the changeram.xml file. system/etc/agold_cheat_evaluating_software.xml

#Smartphone recovery pro v1..0.0.5 android

The Android operating system on my Kingelon was purposely patched to report fake information about RAM and storage, there are also traces of cheating well known benchmark tools.