I tried to flash my iMacwear SPARTA M7 Smart Watch Phone , 4 GB ROM, Android 4.4 OS, bought in April 2015. I did use http://forum.xda-developers.com/oma...rom-omate-truesmart-ironman-firmware-t2998434 for that.
SP Flash Tool worked fine until the final window Download Ok. After that I can not reboot or strat my watch.
I tried to solve this problem, using different Omate Roms with different scatter text files. Every time I removed battery plugged again for flashing. It goes OK , shows "Download DA 100%" in red bar. After some seconds comes error S_FT_ENABLE_DRAM_FAIL (4032). I tried formatting, downloading, memory test byt the result was the same.
I think I need iMacwear m7 original factory rom 4.4.2 for flashing.
Please help with rom or any tips to unbrick my device!
Papi62 said:
I tried to flash my iMacwear SPARTA M7 Smart Watch Phone , 4 GB ROM, Android 4.4 OS, bought in April 2015. I did use http://forum.xda-developers.com/oma...rom-omate-truesmart-ironman-firmware-t2998434 for that.
SP Flash Tool worked fine until the final window Download Ok. After that I can not reboot or strat my watch.
I tried to solve this problem, using different Omate Roms with different scatter text files. Every time I removed battery plugged again for flashing. It goes OK , shows "Download DA 100%" in red bar. After some seconds comes error S_FT_ENABLE_DRAM_FAIL (4032). I tried formatting, downloading, memory test byt the result was the same.
I think I need iMacwear m7 original factory rom 4.4.2 for flashing.
Please help with rom or any tips to unbrick my device!
Click to expand...
Click to collapse
Did you manage to find a stock 4.4.2. ROM?
I'd need it as well cause my M7 came with 4.2.2 and i'd like to update it while I did not find any OTA update to the 4.4.2 release so far (don't know if OTA even works cause it says error connecting to the network even though it also says the system is uptodate).
Should you still need the stock 4.4 ROM, there are a couple of members in this thread http://forum.xda-developers.com/showthread.php?t=3089024 who got sent a 4.4 m7 firmware, you could try it out with a backup from them.
M7 flashing
Papi62 said:
I tried to flash my iMacwear SPARTA M7 Smart Watch Phone , 4 GB ROM, Android 4.4 OS, bought in April 2015. I did use http://forum.xda-developers.com/oma...rom-omate-truesmart-ironman-firmware-t2998434 for that.
SP Flash Tool worked fine until the final window Download Ok. After that I can not reboot or strat my watch.
I tried to solve this problem, using different Omate Roms with different scatter text files. Every time I removed battery plugged again for flashing. It goes OK , shows "Download DA 100%" in red bar. After some seconds comes error S_FT_ENABLE_DRAM_FAIL (4032). I tried formatting, downloading, memory test byt the result was the same.
I think I need iMacwear m7 original factory rom 4.4.2 for flashing.
Please help with rom or any tips to unbrick my device!
Click to expand...
Click to collapse
Hi,
I got X01 today...I would like to flash it ...but how to do it? How to switch the watch into flash mode? There is no volume buton as on ordinary mobile. And how to put the watch in recovery mode? Which button or how to switch the watch.
Thank you very much in advance for assistance..
Regards
Filik
I have a backup of stock room if neededfirst thing I did was take a nand backup
Related
Hello,
I've bought a new device - Evolveo StronPhone Q4, MTK6589 based phone. The stock ROM is basically vanilla Android 4.2.1. I've successfully rooted it using Framaroot.
Then I've created scatter file using MTK Droid Tools (all partitions that were formated were ext4).
Then I've decided to create a backup before I start playing with it, so I've tried backing up flash using SP Flash Tool (using Readback), it was running fine and downloaded approx. 20%, then crashed. I've tried that once or twice more times, always failed. Now after I plug it in, windows display "This device can perform faster" and FlashTool won't detect the device. If I connect it without battery with VolDn key pressed, FlashTool detects it and I get S_DL_GET_DRAM_SETTING_FAIL.
However, the phone boots fine, just GPS/Wifi/BT is not working. (No GPS icon appers, and I get errors like BT_open: WMT turn on BT fail in dmesg). Looks like an issue with kernel/HW issue.
Any ideas what could have gone wrong and how to fix it?
In the meantime, I've asked manufacturer for a stock FW image, but I'm not sure it helps...
Update: Okay, I have no clue what just happened. However I've unrooted, reverted everything I've modified on the phone so far so I'll be able to return it to manufacturer as "deffective"... And just for the curiosity connected it to the computer and tried downloading ROM one more time. And it succeeded - I'll upload the ROM once I get access to faster internet connection. I've removed the battery (phone was stuck in Preloader mode because I cancelled ongoing RAM test.), put it back and now everything works.
So, it looks like everything is fine now, however I'd love to know what happened, if you have any clue, please let me know!
fw problem
Mrkvak said:
Hello,
I've bought a new device - Evolveo StronPhone Q4, MTK6589 based phone. The stock ROM is basically vanilla Android 4.2.1. I've successfully rooted it using Framaroot.
Then I've created scatter file using MTK Droid Tools (all partitions that were formated were ext4).
Then I've decided to create a backup before I start playing with it, so I've tried backing up flash using SP Flash Tool (using Readback), it was running fine and downloaded approx. 20%, then crashed. I've tried that once or twice more times, always failed. Now after I plug it in, windows display "This device can perform faster" and FlashTool won't detect the device. If I connect it without battery with VolDn key pressed, FlashTool detects it and I get S_DL_GET_DRAM_SETTING_FAIL.
However, the phone boots fine, just GPS/Wifi/BT is not working. (No GPS icon appers, and I get errors like BT_open: WMT turn on BT fail in dmesg). Looks like an issue with kernel/HW issue.
Any ideas what could have gone wrong and how to fix it?
In the meantime, I've asked manufacturer for a stock FW image, but I'm not sure it helps...
Update: Okay, I have no clue what just happened. However I've unrooted, reverted everything I've modified on the phone so far so I'll be able to return it to manufacturer as "deffective"... And just for the curiosity connected it to the computer and tried downloading ROM one more time. And it succeeded - I'll upload the ROM once I get access to faster internet connection. I've removed the battery (phone was stuck in Preloader mode because I cancelled ongoing RAM test.), put it back and now everything works.
So, it looks like everything is fine now, however I'd love to know what happened, if you have any clue, please let me know!
Click to expand...
Click to collapse
hello,
could you please upload somewhere original fw for Evolveo Strongphone Q4. im in bootloop now
Hi all,
can you hel me with strongphone Q4, do you know any better rom for this phone?
Maybe by PM in czech? ...
hello i just get my hdc g9000 octacore. i update with the official firmware but my back camera stop working, only front camera works...someone can help to fix it, please it a new phone no more than 1 hour in my hands and crash it...please help me
leo_hacker82 said:
hello i just get my hdc g9000 octacore. i update with the official firmware but my back camera stop working, only front camera works...someone can help to fix it, please it a new phone no more than 1 hour in my hands and crash it...please help me
Click to expand...
Click to collapse
Do you still have a stock backup of the rom ? If so, how did it look like ?
ive got the same problem as you do.. when putting other roms on my phone the back camera stops working, all works fine on my stock original rom tho..
I flash muy backup with flashtools but todo make the camera work i have todo make files for flashtools with mtk droid tools...then i flash and muy camera works....no roms works...onlybstock
Hi, Do you have your lk.bin from your backup?
If you have it, try flashing just lk.bin after the non-stock rom, could work.
And could you send me your lk.bin so I can try it too?
Regards :good:
yea i have it the lk.bin, send me your email adress cuz here i cant upload the file.
Thanks, but I found the orignial lk.bin, but I guess it doesn't work from 4.2 to 4.4...
I have the cell phone working with the original 4.2.2 (store provided) since I couldn't find a 4.4 with both cameras working, could only get the front one to work...
Stips on my display after flashed my phne
Hello, I have received, few hours ago, my STAR G9000 smartphone, with Android 4.4.2 KK. After making the root using VROOT successfully, I tried to update the rom, downloading it from the site needrom the latest version of 27.08.2014. I have upgraded using the "Firmware Upgrade" function (Flash Tool). After a first failed attempt, the second has been good, but when I turned on the smartphone, appeared to me initially a gray screen (all vertical lines), then the strips have changed color and I also heard the sound that indicates the startup of the phone.
I have could also, knowing the position of the lock on the display, perform the unlock the screen (type noise water), but I still see only stripes.
The phone did not take any shock and the strips have appeared only after flashing the phone.
Does anyone know of a similar problem and can help me solve it?
reflash ur stock rom, from newestrom.com or need rom, if u make a backup reflash...
camera
Could you send me driver lk.bin at my email man???
Hi all,
I tried for a few days and seek no solution, therefore I would like to ask if anyone have such situation and got a solution.
Model: Lenovo S939
It was with android 4.2.2 which is the stock rom until I successfully flash it to android 4.4.2 which is the official VIBEUI_V2.0_1507_7.9.1_ST_S939_WC36 about two months ago.
I think I accidently deleted some apps in the phone(I was trying to clear personal contents) and now the phone cannot turn on at all. I am able to connect the phone to my PC using USB and have the driver for it. So I can use SP_Flash_Tool_v5.1524.00.000. I have stock roms S939_S129_140217 and S939_S126_140109 in scatter form.
I flash one of them using the SP tool, but when I finish downloading and reboot, it go back to android vibe UI v2.0, and all sort of system processes stopped continuously, I cannot access the phone at all.
Then I reboot and boot into recovery ( CWM 5 for S939, get from Needroom). I have quite some customs roms saved in my Sd cards which I got from needroom.com:
VIBEUI_V2.0_1501_7.5.1_DEV_S939_WC19.ZIP
VIBEUI_V2.0_1507_7.9.1_ST_S939_WC36.zip
Material_ROM_V3.zip
Loli_Dark_S939_FASTCHIP.zip
I try to flash every one of them, all of them say successful, but when reboot, I boot back to vibe UI 2.0 and all systems processes stopped continuously. I tried to patiently click “OK” and try to access the system setting to enable to USB debugging, but no success.
Have any one got such experience and a solution of it? Spent too much time trying to figure out and appreciate any input.
Regards,
Lacer
when i try to flash roms in recovery...
additional infos, when i try to flash roms in recovery mode, there are warning about no context
and if i go into meta mode and click the option to clear emmc, it restart itself and go back to the vibe ui with non stop pop out of processes stop error.
Lacerlacer said:
Hi all,
I tried for a few days and seek no solution, therefore I would like to ask if anyone have such situation and got a solution.
Model: Lenovo S939
It was with android 4.2.2 which is the stock rom until I successfully flash it to android 4.4.2 which is the official VIBEUI_V2.0_1507_7.9.1_ST_S939_WC36 about two months ago.
I think I accidently deleted some apps in the phone(I was trying to clear personal contents) and now the phone cannot turn on at all. I am able to connect the phone to my PC using USB and have the driver for it. So I can use SP_Flash_Tool_v5.1524.00.000. I have stock roms S939_S129_140217 and S939_S126_140109 in scatter form.
I flash one of them using the SP tool, but when I finish downloading and reboot, it go back to android vibe UI v2.0, and all sort of system processes stopped continuously, I cannot access the phone at all.
Then I reboot and boot into recovery ( CWM 5 for S939, get from Needroom). I have quite some customs roms saved in my Sd cards which I got from needroom.com:
VIBEUI_V2.0_1501_7.5.1_DEV_S939_WC19.ZIP
VIBEUI_V2.0_1507_7.9.1_ST_S939_WC36.zip
Material_ROM_V3.zip
Loli_Dark_S939_FASTCHIP.zip
I try to flash every one of them, all of them say successful, but when reboot, I boot back to vibe UI 2.0 and all systems processes stopped continuously. I tried to patiently click “OK” and try to access the system setting to enable to USB debugging, but no success.
Have any one got such experience and a solution of it? Spent too much time trying to figure out and appreciate any input.
Regards,
Lacer
Click to expand...
Click to collapse
it seems like something to do with the error 1041. I failed to test the nand flash
It seems like something to do with the error 1041. I failed to run a dedicated memory test in SP tool. Anyone have any though?
Lacerlacer said:
additional infos, when i try to flash roms in recovery mode, there are warning about no context
and if i go into meta mode and click the option to clear emmc, it restart itself and go back to the vibe ui with non stop pop out of processes stop error.
Click to expand...
Click to collapse
Hi everyone! Sorry for my english))
Today I get some troubles with my TCL M2U. After some errors with google apps on the phone I tried to reboot my device, but its not want booting. Booting stopped on bootanimation and nothing can helps. Then I tried to flash the device with flash tools v5.1504.00.000 100% working lewaos 4.4.4 but nothing changed. The device don't booting. I was trying to use another version of flashtools and another firmware but problem the same. During flashing there are no errors no troubles. Everything is ok. Firmwares 100 % work. I used it before I tried to change in FT "download only" to "firmware update" but nothing changed. Can some one help me?
trist13 said:
Hi everyone! Sorry for my english))
Today I get some troubles with my TCL M2U. After some errors with google apps on the phone I tried to reboot my device, but its not want booting. Booting stopped on bootanimation and nothing can helps. Then I tried to flash the device with flash tools v5.1504.00.000 100% working lewaos 4.4.4 but nothing changed. The device don't booting. I was trying to use another version of flashtools and another firmware but problem the same. During flashing there are no errors no troubles. Everything is ok. Firmwares 100 % work. I used it before I tried to change in FT "download only" to "firmware update" but nothing changed. Can some one help me?
Click to expand...
Click to collapse
Try newer FlashTool version first. Recommended FT version for MT67xx is 5.1444 or newer.
Hi!
My girlfriend has an LG L70 Dual Sim (D325f 0814) phone. About one moth ago, the phone started suddenly restarting. After one restart this image showed in the screen. hZZZttZZZps://wwZZZw.dropZZZbox.com/s/teklp3uZZZpaz6f5mz/20170118_ZZZ194100.ZZZjpg?dl=0
I have never used other battery in the phone. (replace all triple ZZZ to nothing and you can have the correct link)
After that I tried a factory reset. But it did't helped. After the reset, the phone always shows me com.android.systemui has stopped error message. So i decide to install other room. I don't know, other ROM solve this problems, but I don't have any other idea. So Where can I find ROM for this phone? And how can I install it? I only need a working phone, i don't want android 5 or any costum things. The phone currently running Android 4.4.2 (kernel version 3.4.0+ build number KOT49I.A1464618841)
Please help!
Thanks.
Normally installing mods or messing with system causes this errors
Ultimate solution is reflash the ROM using stock ROM
You can download the ROM using google and flash it via stock recovery
This will solve your problems
Thanks for the answer The Hard Gamer. I install D32510F_00 firmware from csmgdl.lgmobile.com. The com.android.systemui message goes away. Now i wait for other system error messages.