Differences

This shows you the differences between two versions of the page.

--- doc:appunti:hardware:kingelon_g9000 [2014/11/08 15:53] – [VRoot with PC and USB cable] niccolo
+++ doc:appunti:hardware:kingelon_g9000 [2017/11/17 12:27] (current) – [The Android System Recovery menu] niccolo
@@ Line 14: / Line 14: @@
       * mmcblk0p7 2416640 blocks (**2.3 Gb**) mounted as **''/data''**
       * mmcblk0p8 4058112 blocks, (**3.9 Gb**) mounted as **''/storage/sdcard0''**
+  * Display: 1080 x 1920
   * Operating system: Android 4.4.2
   * Kernel: 3.4.67
@@ Line 69: / Line 70: @@
 Finally I removed the line with **''item name="package_name"''** from the file ''agold_cheat_evaluating_software.xml'', this, indeed, didn't change anything in AnTuTu scores.
 ===== Get a shell on PC with Android SDK =====
+Here it is how the phone is seen on the USB bus (using ''lsusb''):
+<code>
+Bus 005 Device 010: ID 0bb4:0c03 HTC (High Tech Computer Corp.)
+</code>
 Enable the USB debug feature on the phone: //Opzioni// -> //Opzioni sviluppatore// -> //Debug USB//.
@@ Line 128: / Line 135: @@
   - Power-off the phone and detach any USB cable.
-  - Keep pressed the **volume + button** while pressing the **power button**.
+  - Keep pressed the **Volume UP button** while pressing the **power button**.
   - Release the buttons, after the Welcome logo you get the broken Android icon.
   - Press the **power button once**, you get the menu.
 **WARNING!** **There is a bug** in the Recovery, buttons does not work as stated:
-  * To **navigate** the menu use only the **volume - button**
+  * To **navigate** the menu use only the **Volume Down button**
-  * To **select** the menu item use the **volume + button**
+  * To **select** the menu item use the **Volume Up button**
   * The power button does not work, it just hide/show the menu
@@ Line 172: / Line 179: @@
 See this post: [[http://laurentiumihet.ro/sp-flash-tool-mediatek-mt65xx-drivers-download-and-installation-guide-including-bricked-devices/|SP Flash Tool + MediaTek MT65xx]].
-Devices based on the **MT65xx** chip can be put in **Download Mode**, a state in which the flash memory can be formatted and reprogrammed. 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). 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).
+Devices based on the **MT65xx** chip can be put in **Download Mode**, a state in which the flash memory can be formatted and reprogrammed. 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). 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).
-This is the **lsusb** output:
+This is the **lsusb** output during the time the interface is exposed:
 <code>
@@ Line 214: / Line 221: @@
   - Enable **USB debugging option** on the phone (//Settings//, //Developer options//, //USB debugging//).
-  - Connect the device using the USB cable, go to the //Control Panel//, //Device Manager//, you will see the **MT65xx Android Phone** with the yellow exclamation mark. Install the **Android ADB Interface** drivers. If Windows does not find the drivers automatically, you can find them on the web. I don't know the offical repository, here it is an [[http://droidchina.com/forum/attachment.php?aid=8|unverified one]].
+  - Connect the device using the USB cable, go to the //Control Panel//, //Device Manager//, you will see the **MT65xx Android Phone** with the yellow exclamation mark. Install the **Android ADB Interface** drivers. It seems that Windows is not able to find the drivers automatically, neither using Windows Update. The .inf file must contain **''%%USB\VID_0BB4&PID_0C03&MI_01%%''** (which stands for USB device 0bb4:0c03). I don't know the offical repository, here it is an [[http://droidchina.com/forum/attachment.php?aid=8|unverified one]].
   - **Detach** the USB cable.
   - **Install VRoot 1.7.9** and run the program (just say Yes, Yes, ... Next, Next, ... the **''Next>''** button is in Chinese, but you can see the **''>''** char on it). Windows and the antivirus program suggested thath the program is a threat for the system, you have to trust the VRoot author and the download site :-(.
@@ Line 220: / Line 227: @@
   - **Click the root button** and wait. Something is uploaded to the phone which is then rebooted. The VRoot program does not sensed that the procedure wents fine, so it remained in an endless loop (picture 4). After several minutes I verified that the phone finished rebooting and installing, so I detached the cable and closed VRoot program on the PC.
-{{.:g9000:vroot-fig01.png?direct&180|}}
+{{.:g9000:android-composite-adb-interface.png?direct&180|}}
 {{.:g9000:vroot-fig02.png?direct&180|}}
 {{.:g9000:vroot-fig03.png?direct&180|}}
@@ Line 449: / Line 456: @@
 The back camera takes pictures at about 13 Mpixels (4160 x 3120). While colors are quite satisfying, the quality is poor indeed. With default settings in good light conditions, **the noise** in midrange shadows is rather visible, **compression artifacts** are also annoying. It seems also that some sort of sharpening filter is applied automatically: zoom at 1:1 or more to see the exagerated contrast of fine details.
+===== Headset connector =====
+The provided headset has a 3.5 mm jack with 4 poles (TRRS), but is has a **non-standard length**. I tried some other headsets, but they are not recognized: no "headset" icon in the status bar. Using a third party headset the **FM radio application does not work**, because it requires an headset plugged.
+The pinout seems to be iPhone-like: left, right, ground and mic (Tip, Ring, Ring, Sleeve), so I wired an adapter cable "4 to 3 poles" to get the audio into my car, but only the left channel is working. To change the audio routing I used the [[https://play.google.com/store/apps/details?id=com.woodslink.android.wiredheadphoneroutingfix|SoundAbout]] app by David Woods.
+Someone reported that [[https://www.avforums.com/threads/star-g9000.1888308/#post-21505064|extending the length of the jack]] can solve the problem; it requires a small lathe to modify the jack.
+===== Networking =====
+This is the state with data connection enabled, WiFi disabled:
+<code>
+root@706v92_jbla_fhd:/ # ip addr show
+: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
+    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+    inet 127.0.0.1/8 scope host lo
+    inet6 ::1/128 scope host
+       valid_lft forever preferred_lft forever
+: ifb0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN qlen 32
+    link/ether 46:2a:bc:c3:79:5b brd ff:ff:ff:ff:ff:ff
+: ifb1: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN qlen 32
+    link/ether b6:bb:e4:c9:8d:54 brd ff:ff:ff:ff:ff:ff
+: tunl0: <NOARP> mtu 1480 qdisc noop state DOWN
+    link/ipip 0.0.0.0 brd 0.0.0.0
+: sit0: <NOARP> mtu 1480 qdisc noop state DOWN
+    link/sit 0.0.0.0 brd 0.0.0.0
+: ip6tnl0: <NOARP> mtu 1452 qdisc noop state DOWN
+    link/tunnel6 :: brd ::
+: ccmni0: <NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
+    link/ether 5a:6d:81:13:4a:27 brd ff:ff:ff:ff:ff:ff
+    inet 10.200.148.163/8 scope global ccmni0
+: ccmni1: <NOARP> mtu 1500 qdisc noop state DOWN qlen 1000
+    link/ether 2a:9a:3b:cc:26:60 brd ff:ff:ff:ff:ff:ff
+: ccmni2: <NOARP> mtu 1500 qdisc noop state DOWN qlen 1000
+    link/ether ba:59:39:c0:bd:e1 brd ff:ff:ff:ff:ff:ff
+</code>
+<code>
+root@706v92_jbla_fhd:/ # ip route show
+default via 10.200.148.163 dev ccmni0  scope link
+.200.148.163 dev ccmni0  scope link
+</code>
+===== Charging problem: disassembling the G9000 =====
+After three months of use, the phone started suffering from **charging problem**.
+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. Sometimes, when the phone was plugged for the nightly charge, the orange LED turned on, but the morning after the phone was completely discharged ad the LED was off. Sometimes applying a light force to the USB connector (blending it toward the back of the phone) seemed to help, but everything was extremly unreliable.
+It was not a cable or connector problem, it turned out that the power connector required a **soldering reflow**. Fortunately only a partial disassemble of the phone was required: just removing the **back frame** you can detach the **power board**.
+{{.:g9000:g9000_dis01_screws.jpg?direct&200|}}
+{{.:g9000:g9000_dis03_back-frame.jpg?direct&200|}}
+{{.:g9000:g9000_dis05_bottom-board-screw.jpg?direct&200|}}
+Remove the 10 screws which keep the back frame. Divaricate the metal-plated frame from the screen glass using your thumb's nails. Facing the screen: the glass comes toward you and the frames goes to the back. Beware of the volume and power buttons.
+The **power board** at the bottom is secured with a single **screw**. Before removing it, detach the **antenna cable** and pull the **vibrator** out from its seat, where is secured with some adhesive.
+{{.:g9000:g9000_dis02_frame.jpg?direct&200|}}
+{{.:g9000:g9000_dis04_button.jpg?direct&200|}}
+{{.:g9000:g9000_dis06_bottom-board.jpg?direct&200|}}
+Now you can rotate the power board and see the **flat connector**. The **white piece of plastic** keeps the connector locked-in: flip it, so the connector is released.
+{{.:g9000:g9000_dis07_lock-flip.jpg?direct&200|}}
+{{.:g9000:g9000_dis08_power-connector.jpg?direct&200|}}
+Now the power board is free and you can reflow the soldering. I put very little **soldering flux** over the contacts, a bit of **tin** (a good **silver-alloy**) on the soldering iron. I used a 2 mm soldering tip, larger than the contacts, so I used very few tin for a very short time. Clean the flux with a needle, **cotton swab and alcohol**; inspect closely to avoid short-circuits.
+After some days of use, it seems that **the charging problem is solved**.
 ===== Link =====
@@ Line 457: / Line 535: @@
   * [[http://www.chinaphonearena.com/forum/Thread-Tutorial-Backup-MTK6592-MTK6589-MTK6577-and-all-MTK-Phones|Backup MTK6592 MTK6589 MTK6577 and all MTK Phones]]
   * [[http://www.chinaphonearena.com/forum/Thread-How-To-Create-new-Touch-or-nonTouch-CWM-Recovery-on-MTK-Phones|Create new Touch or nonTouch CWM Recovery on MTK Phones]]
+----
+<php>echo '<a rel="me" href="https://profiles.google.com/100662196154811835450">Profilo Google+</a>' . "\n";</php>