[Android Q&A, Help & Troubleshooting] g256w:
Hey Rovogen - this is Stuart, i posted the Google forum help post about the Voga V.

I did a check of the build.prop to find all the ID's that have the space in "VOGA V" so we know which ones may be causing the issue.. here is a sample dump of my build.prop file:

126|VOGA V:/sdcard $ getprop

[gsm.project.baseband]: [E55909_VOGA_LWG(LWCTG_MP3)]

[gsm.project.baseband.2]: [E55909_VOGA_LWG(LWCTG_MP3)]

[gsm.version.baseband]: [E55909_VOGA_LWG_N_MP_V0.0.1_S171129, 2017/12/01 17:24]

[gsm.version.baseband1]: [E55909_VOGA_LWG_N_MP_V0.0.1_S171129, 2017/12/01 17:24]

[ro.boot.hardware.sku]: [VOGA_V04_06122017]

[ro.bootimage.build.fingerprint]: [ALLVIEW/X4_Soul_Vision/X4_Soul_Vision:7.0/NRD90M/1505797643:user/release-keys]

[ro.build.custom_int_version]: [E55909_VOGA_C1_V0.4.3_S1206]

[ro.build.custom_version]: [VOGA_V04_06122017]

[ro.build.description]: [full_e55909_e_commerce-user 7.0 NRD90M 1512528365 release-keys]

[ro.build.display.id]: [VOGA_V04_06122017]

[ro.build.fingerprint]: [ALLVIEW/X4_Soul_Vision/X4_Soul_Vision:7.0/NRD90M/1505797643:user/release-keys]

[ro.build.flavor]: [full_e55909_e_commerce-user]

[ro.build.host]: [80-32]

[ro.build.id]: [NRD90M]

[ro.build.product]: [VOGA V]

[ro.build.tags]: [release-keys]

[ro.build.type]: [user]

[ro.build.user]: [jenkins]

[ro.build.version.all_codenames]: [REL]

[ro.build.version.base_os]: []

[ro.build.version.codename]: [REL]

[ro.build.version.incremental]: [1512528365]

[ro.build.version.preview_sdk]: [0]

[ro.build.version.release]: [7.0]

[ro.build.version.sdk]: [24]

[ro.build.version.security_patch]: [2017-09-05]

[ro.camera.sound.forced]: [0]

[ro.carrier]: [unknown]

[ro.com.android.mobiledata]: [true]

[ro.com.google.clientidbase]: [android-VOGA]

[ro.com.google.clientidbase.am]: [android-VOGA]

[ro.com.google.gmsversion]: [7.0_r10]

[ro.crypto.fs_crypto_blkdev]: [/dev/block/dm-1]

[ro.crypto.state]: [encrypted]

[ro.hardware]: [mt6755]

[ro.internal.version]: [E55909_VOGA_C1_V0.4.3_S1206]

[ro.mediatek.chip_ver]: [S01]

[ro.mediatek.platform]: [MT6755]

[ro.mediatek.project.path]: [device/emobile/e55909_e_commerce]

[ro.mediatek.version.branch]: [alps-mp-n0.mp7]

[ro.mediatek.version.release]: [alps-mp-n0.mp7-V1.24_rgk6750.65.n]

[ro.mediatek.version.sdk]: [4]

[ro.mediatek.wlan.p2p]: [1]

[ro.mediatek.wlan.wsc]: [1]

[ro.product.board]: [e55909_e_commerce]

[ro.product.brand]: [VOGA V]

[ro.product.cpu.abi]: [arm64-v8a]

[ro.product.cpu.abilist]: [arm64-v8a,armeabi-v7a,armeabi]

[ro.product.cpu.abilist32]: [armeabi-v7a,armeabi]

[ro.product.cpu.abilist64]: [arm64-v8a]

[ro.product.device]: [VOGA V]

[ro.product.locale]: [en-US]

[ro.product.locale.language]: [fr]

[ro.product.locale.region]: [FR]

[ro.product.manufacturer]: [VOGA V]

[ro.product.model]: [VOGA V]

[ro.product.name]: [VOGA V]

[ro.ptp.label]: [VOGA V]

I tried to update the build.prop with a flashable zip, but of course that doesn't work as i don't have root. We need root access to be able to edit the build.prop, or wait for an OTA update from Ragentek / GreenOrange so get us past this issue.

Alternatively, we find someone who can get us a flashable recovery like TWRP or CWM - the Blackview S8 has a very similar spec / chipset to the Voga V, so maybe that's a path.

Lastly, there are 3 other phones that are semi-clones of the Voga V:

Allview X4 Soul Vision

Quantum V

Moviphone

the all appear to be the same phone, but some have only 3GB / 32GB of ram/storage as opposed to ours which has 4GB / 64GB

---------- Post added at 05:36 AM ---------- Previous post was at 04:54 AM ----------

Another interesting angle that i'm exploring is the MTK Engineering Mode / Application. You can access it by opening the dialer and typing:

*#*#3646633#*#*