Hovatek Forum MOBILE Android Diamond Max Zero X4000 bootloop/Black Screen of Death
Can't login? Please, reset your password.
Hovatek is recruiting! Apply Now


Diamond Max Zero X4000 bootloop/Black Screen of Death

Diamond Max Zero X4000 bootloop/Black Screen of Death

Pages (2): 1 2 Next
amodu
amodu
amodu
Enthusiastic Member
8
22-09-2019, 07:09 PM
#1



Please somebody help!!!!!!!!!
Pls be patient and read carefully to understand the problem
A month ago my android phone(Zero Diamond Max Model X4000).  all by it's self requested for permission to access some files of which I denied thinking it must be some virus or malware trying to install it self and cause havoc.The phone then went off and rebooted then stopped at the android logo lying down with exclamation mark on it with some error message which I can't remember, it then reboots itself to this very spot again(bootloop).

I was able to boot into recovery through the power key/volume up and do factory wipe/clear cache and user data which did not help matters as the bootloop continues , but I was able to stop it by using the shut down icon in recovery menu, unless I press the power button it stays off. After some research on the net I decided to flash the phone with original stock rom which I have no backup but have to google it using its model number as keyword, this search yielded nothing.

since I could boot into fastboot mode via the recovery menu,I decided to install TWRP hoping it will help solve the problem.TWRP was successfully installed but upon reboot it displayed black lighted screen.Faced with this problem after further research I installed qtadb on my Linus(ubuntu) system.when I boot into qtadb I see the menu tab for twrp and when I click it the only active tabs are wipe and flash, the flash tab does not work but the wipe works.I could also boot into fastboot mode from the fastboot tab on qtadb.
While in recovery mode I see the following details on top:
SPRD/SP7731C_1H10_32V4_OVERSEA/SP7731C_1H10_6.0/MRA58K/W16.42-1-16

In order to know the real stock rom on my android phone a gave the command: adb -s <device id> shell getprop

The above command revealed the following details:

Code:

[dalvik.vm.dex2oat-Xms]: [64m]
[dalvik.vm.dex2oat-Xmx]: [512m]
[dalvik.vm.heapgrowthlimit]: [128m]
[dalvik.vm.heapminfree]: [4m]
[dalvik.vm.heapsize]: [256m]
[dalvik.vm.heapstartsize]: [12m]
[dalvik.vm.heaptargetutilization]: [0.75]
[dalvik.vm.image-dex2oat-Xms]: [64m]
[dalvik.vm.image-dex2oat-Xmx]: [64m]
[dalvik.vm.isa.arm.features]: [div]
[dalvik.vm.lockprof.threshold]: [500]
[dalvik.vm.stack-trace-file]: [/data/anr/traces.txt]
[debug.hwui.render_dirty_regions]: [false]
[fw.max_users]: [3]
[fw.show_multiuserui]: [1]
[init.svc.adbd]: [running]
[init.svc.healthd]: [running]
[init.svc.recovery]: [running]
[init.svc.set_permissive]: [stopped]
[init.svc.ueventd]: [running]
[keyguard.no_require_sim]: [true]
[media.stagefright.legacyencoder]: [true]
[media.stagefright.less-secure]: [true]
[mtp.crash_check]: [0]
[net.bt.name]: [Android]
[net.change]: [net.bt.name]
[persist.logd.logpersistd]: [logcatd]
[persist.modem.w.enable]: [1]
[persist.modem.w.nvp]: [w]
[persist.msms.phone_count]: [2]
[persist.msms.phone_default]: [0]
[persist.msmslt]: [0]
[persist.radio.multisim.config]: [dsds]
[persist.service.adb.enable]: [1]
[persist.service.debuggable]: [1]
[persist.sys.dalvik.vm.lib.2]: [libart.so]
[persist.sys.engpc.disable]: [0]
[persist.sys.modem.diag]: [,gser]
[persist.sys.root_access]: [1]
[persist.sys.sprd.modemreset]: [1]
[persist.sys.sprd.wcnreset]: [1]
[persist.sys.storage_preload]: [1]
[persist.sys.usb.config]: [adb,adb]
[ro.adb.secure]: [0]
[ro.allow.mock.location]: [0]
[ro.baseband]: [unknown]
[ro.board.platform]: [sc8830]
[ro.boot.ftm]: [0]
[ro.boot.hardware]: [sp7731c_1h10_32v4]
[ro.boot.serialno]: [16714294558715]
[ro.bootloader]: [unknown]
[ro.bootmode]: [unknown]
[ro.build.characteristics]: [My28s]
[ro.build.date.utc]: [1517417596]
[ro.build.date]: [Wed Jan 31 22:53:16 +06 2018]
[ro.build.display.id]: [cm_My28s-userdebug 5.1.1 LMY49J 7b5c10af4c test-keys]
[ro.build.flavor]: [cm_My28s-userdebug]
[ro.build.host]: [Naimur9800]
[ro.build.id]: [LMY49J]
[ro.build.tags]: [test-keys]
[ro.build.type]: [userdebug]
[ro.build.user]: [devnull]
[ro.build.version.all_codenames]: [REL]
[ro.build.version.base_os]: []
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [7b5c10af4c]
[ro.build.version.release]: [5.1.1]
[ro.build.version.sdk]: [22]
[ro.build.version.security_patch]: [2016-07-01]
[ro.cm.device]: [My28s]
[ro.com.android.dataroaming]: [false]
[ro.com.google.locationfeatures]: [1]
[ro.com.google.networklocation]: [1]
[ro.config.swappiness]: [130]
[ro.config.zram.compressor]: [lz4]
[ro.config.zram.disksize]: [512M]
[ro.dalvik.vm.native.bridge]: [0]
[ro.debuggable]: [1]
[ro.egl.destroy_after_detach]: [true]
[ro.factorytest]: [0]
[ro.hardware]: [sp7731c_1h10_32v4]
[ro.hwui.drop_shadow_cache_size]: [6]
[ro.hwui.gradient_cache_size]: [1]
[ro.hwui.layer_cache_size]: [48]
[ro.hwui.path_cache_size]: [32]
[ro.hwui.r_buffer_cache_size]: [8]
[ro.hwui.text_large_cache_height]: [1024]
[ro.hwui.text_large_cache_width]: [2048]
[ro.hwui.text_small_cache_height]: [1024]
[ro.hwui.text_small_cache_width]: [1024]
[ro.hwui.texture_cache_flushrate]: [0.4]
[ro.hwui.texture_cache_size]: [72]
[ro.modem.w.assert]: [/dev/spipe_w2]
[ro.modem.w.count]: [2]
[ro.modem.w.dev]: [/proc/cpw/]
[ro.modem.w.diag]: [/dev/slog_w]
[ro.modem.w.eth]: [rmnet]
[ro.modem.w.fixnv_size]: [0x40000]
[ro.modem.w.id]: [0]
[ro.modem.w.loop]: [/dev/spipe_w0]
[ro.modem.w.nv]: [/dev/spipe_w1]
[ro.modem.w.runnv_size]: [0x60000]
[ro.modem.w.snd]: [1]
[ro.modem.w.tty]: [/dev/stty_w]
[ro.modem.w.vbc]: [/dev/spipe_w6]
[ro.modem.wcn.assert]: [/dev/spipe_wcn2]
[ro.modem.wcn.count]: [1]
[ro.modem.wcn.dev]: [/dev/cpwcn]
[ro.modem.wcn.diag]: [/dev/slog_wcn]
[ro.modem.wcn.enable]: [1]
[ro.modem.wcn.id]: [1]
[ro.modem.wcn.tty]: [/deiv/stty_wcn]
[ro.msms.phone_count]: [2]
[ro.opengles.version]: [131072]
[ro.product.board]: [sc7731g]
[ro.product.brand]: [My28s]
[ro.product.cpu.abi2]: [armeabi]
[ro.product.cpu.abi]: [armeabi-v7a]
[ro.product.cpu.abilist32]: [armeabi-v7a,armeabi]
[ro.product.cpu.abilist64]: []
[ro.product.cpu.abilist]: [armeabi-v7a,armeabi]
[ro.product.device]: [My28s]
[ro.product.hardware]: [SC7731G_V1.0.0]
[ro.product.locale.language]: [en]
[ro.product.locale.region]: [US]
[ro.product.manufacturer]: [My28s]
[ro.product.name]: [cm_My28s]
[ro.revision]: [0]
[ro.ril.gprsclass]: [10]
[ro.ril.hsxpa]: [1]
[ro.ril.telephony.mqanelements]: [6]
[ro.secure]: [0]
[ro.serialno]: [16714294558715]
[ro.sf.lcd_density]: [200]
[ro.sf.lcd_height]: [90]
[ro.sf.lcd_width]: [154]
[ro.telephony.ril.config]: [setPrefNwTypeOnUnsolConnected]
[ro.telephony.ril_class]: [SC7731CRIL]
[ro.twrp.boot]: [1]
[ro.twrp.version]: [3.1.1-0]
[ro.wifi.channels]: []
[ro.zygote]: [zygote32]
[security.perf_harden]: [1]
[service.adb.root]: [1]
[sys.usb.config]: [mtp,adb]
[sys.usb.gser.count]: [4]
[twrp.action_complete]: [0]
[twrp.crash_counter]: [0]

From the above information it can be seen that my phone is actually a my28s brand, product name cm_my28s. there is no mention of Zero Diamond max X4000 at all, which probably explains why i could not get a stock rom by that name or model.
Naively believing that a my28s stock rom will also work on my phone I searched and downloaded MyPhone My28S Version 4_18.zip.
regretably I decided to first flash the boot.img from twrp console. it flashed successfully. But things really went awry thereafter.Can't boot by pressing the power button anymore, the only sign of life is when I insert it into my PC usb port or use the charger, it powers up displays the brand logo zero and then remains at a black lighted screen with nothing at all, after unplug this remains for about 30 seconds before it goes off.

While in this state the commands adb devices or fastboot devices return nil both in ubuntu and windows environment.
However in windows environment I observe it makes the usb connect and disconnect sound, and the device manager sees it as an sprd device for 2 seconds before disconnect/reconnect and then complete disconnection.The spd flash tool is able to connect to the phone but because of the per second boot loop flashing cannot proceed.

Please how do I solve this problem even if it means flashing a custom stock rom. I also observe there are many people in other forum with this same device and same or similar problem but it seems I got lucky by having access to its exact specifications as stated above which I hope will help in solving the problem.Please help me out.
This post was last modified: 23-09-2019, 09:48 AM by X3non.
X3non
X3non
X3non
Recognized Contributor
22,062
23-09-2019, 09:58 AM
#2
(22-09-2019, 07:09 PM)amodu ...
Please how do I solve this problem even if it means flashing a custom stock rom. I also observe there are many people in other forum with this same device and same or similar problem but it seems I got lucky by having access to its exact specifications as stated above which I hope will help in solving the problem.Please help me out.

can either you or any of the others with this same phone / problem get access to a working phone with same model?
http://www.mediafire.com/file/c43cxe7w9x...D.zip/file ; is this the same firmware you downloaded?
try flashing only boot, system & userdata.img from the firmware in the link above using research download tool; refer to https://www.hovatek.com/forum/thread-28774.html
amodu
amodu
amodu
Enthusiastic Member
8
24-09-2019, 07:36 PM
#3
Thanks for your prompt response.
The version I tried using that got me into trouble is MyPhone_My28s_Openline_Firmware_v1
I flashed only the boot.img file from it.
I will try your suggestion and get back to you soon.
I will also try to see if we can find a working phone of the same make and specs
amodu
amodu
amodu
Enthusiastic Member
8
26-09-2019, 05:34 PM
#4
Good evening Hovatek
I have acted as instructed but cannot flash because when I click download and plug the phone via usb cable with the battery inserted,  I here the connection sound once and disconnection sound once. and the phone lights up with dark screen and remains like that for about one minute after unplug, then goes off.
At the same time I observe the status in the sp research/download tool change from checking baudrate to unplugged, the progress column shows red text "failed: user cancel".
If I remove the battery and connect the phone without the battery, it begins a series of connect and disconnect showing the same info as above in the sp research/download tool until I unplug the usb.
The only time the boot logo displays is when the phone is plugged into a charger. the zero logo displays briefly for 2 seconds only, then the lighted black screen comes on and stays lighted for about 2 minutes before going off after unplug.
Find attached a screen shot of the sp research/download tool during flash
This is the situation report Sir, I earnestly await your help and guidance
Attached Files
.png
Screenshot (2).png
Size: 49.28 KB / Downloads: 4
xerxes
xerxes
xerxes
Senior Member
8,355
26-09-2019, 07:00 PM
#5



(26-09-2019, 05:34 PM)amodu Good evening Hovatek
I have acted as instructed but cannot flash because when I click download and plug the phone via usb cable with the battery inserted,  I here the connection sound once and disconnection sound once. and the phone lights up with dark screen and remains like that for about one minute after unplug, then goes off.
At the same time I observe the status in the sp research/download tool change from checking baudrate to unplugged, the progress column shows red text "failed: user cancel".
If I remove the battery and connect the phone without the battery, it begins a series of connect and disconnect showing the same info as above in the sp research/download tool until I unplug the usb.
The only time the boot logo displays is when the phone is plugged into a charger. the zero logo displays briefly for 2 seconds only, then the lighted black screen comes on and stays lighted for about 2 minutes before going off after unplug.
Find attached a screenshot of the sp research/download tool during flash
This is the situation report Sir, I earnestly await your help and guidance

try disconnecting/reconnecting the phone battery before connecting it to pc.
you can also try holding the vol + or - before connecting the phone to flash tool.
amodu
amodu
amodu
Enthusiastic Member
8
30-09-2019, 03:30 PM
#6
Good afternoon Sir,
I can now connect to spd research /download tool. I do so by first removing and putting  back the battery and then press the volume down key while connecting the the phone via usb to the PC
but I get the following error:
Port:7
Step: FDL
Status: Finish
Progress: Failed: The second enumeration port time out
time :1s
Pls help how do I overcome this Sir
xerxes
xerxes
xerxes
Senior Member
8,355
30-09-2019, 10:28 PM
#7
(30-09-2019, 03:30 PM)amodu Good afternoon Sir,
I can now connect to spd research /download tool. I do so by first removing and putting  back the battery and then press the volume down key while connecting the the phone via usb to the PC
but I get the following error:
Port:7
Step: FDL
Status: Finish
Progress: Failed: The second enumeration port time out
time :1s
Pls help how do I overcome this Sir

Try the fix @ https://www.hovatek.com/forum/thread-4870.html
What happen when you connect the phone without holding any button? any error?
amodu
amodu
amodu
Enthusiastic Member
8
02-10-2019, 07:52 PM
#8
If I connect the phone without holding any key, flashing does not initialize even though the phone comes up with a black lighted screen.
I have installed the research download tool on another pc (windows 7the first one is windows 10 ) including adb /fastboot. I use two different usb cables all new.
I get the same error message and adb does not see my device when I give the command "adb devices"
X3non
X3non
X3non
Recognized Contributor
22,062
03-10-2019, 11:06 AM
#9
(02-10-2019, 07:52 PM)amodu If I connect the phone without holding any key, flashing does not initialize even though the phone comes up with a black lighted screen.
I have installed the research download tool on another pc (windows 7the first one is windows 10 ) including adb /fastboot. I use two different usb cables all new.
I get the same error message and adb does not see my device when I give the command "adb devices"

adb won't work probably cause usb debugging isn't enabled
are you still able to boot the device into fastboot mode? if yes, you can try flashing the items using fastboot
amodu
amodu
amodu
Enthusiastic Member
8
03-10-2019, 06:52 PM
#10



I use to boot into fastboot mode and adb before I flashed the boot.img file. it was after flashing the boot.img file that fastboot and adb became inaccessible so I can't flash from there. Have I reached a dead end?
Pages (2): 1 2 Next
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)
YtWhTl
live chat
whatsapp telegram instagram