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
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? ...
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
Hi guys please help me i need to have my phone working back |:.... today i updated my wiko fever 4g but i got an error... now when i boot it an android icon shows with "no command." text. Tryed with v.39 program on wiko website but its not working for me... when arrow becomes green download wont start.
I'm thinking to recover system fom sd card but i cannot find roms please help me |: thanks in advance
Same issue here... Finally decided to upgrade the system from stock firmware, and got "error" when it rebooted the phone. Then "no command".
Darknezz89 said:
Hi guys please help me i need to have my phone working back |:.... today i updated my wiko fever 4g but i got an error... now when i boot it an android icon shows with "no command." text. Tryed with v.39 program on wiko website but its not working for me... when arrow becomes green download wont start.
I'm thinking to recover system fom sd card but i cannot find roms please help me |: thanks in advance
Click to expand...
Click to collapse
I solved my issue by restoring Lollipop (v.39) with the tool from the wiko website and then performing the update again; the phone started again (at v.41) and I was able to download Marshmallow from the next system update.
Issue was probably caused by some configuration or application.
Still slowly downloading Marshmallow now, so cannot say anything about the next update, but I guess that will go well, since the phone is reset now.
Just to follow up: Marshmallow is working fine on my Wiko Fever, much better than Lollipop. Amazing update.
Instructions for others after having read some comments from other people experiencing issues with the upgrade:
- BACKUP all your data before upgrading from Lollipop to Marshmallow, as if you would buy a new phone; I luckily did, as I wanted to set the microSD from removable to internal
- remove the microSD and (after having a backup of all your data as per step above) format the card as FAT32 on your PC; better to have a clean MicroSD card for after the upgrade I think
- reboot the phone in recovery mode and do a: wipe cache+reset to factory settings
- once the phone is reset and started, proceed with upgrading to Marshmallow
- don't know if needed after the upgrade to do an additional wipe cache+factory settings reset, doesn't harm to do it though
- be unhappy for the hours lost in restoring the phone data + apps + reconfigure everything
- be happy of the improved phone software
Questions upon questions.
So, i got the notification for the update last week, and i saved it until today to install it. The file downloaded was just 7 mb, i had enough battery for the intallation of the update (30% recomended by the software), something got messed up and an error message with the dead android character appeared. I know i lost all my things contacts and sd card... tried to hard reset the damn thing and nothing. I already googled the problem and i found nothing similar to what i get, i'm stuck in the recovery screen and the phone doenst shut down, every time i force it, it just boots back up after 15 30 seconds. I got to be honest i tought it was just another update but aparently its a "new" operating androind system. They could have told me with a update log or something...
After I stilled root and xposed with TWRP for this post: https://forum.xda-developers.com/honor-8/development/twrp-t3566563 , it worked fine, but after I tried installing a different type of root, xposed framework stopped working as it should. I tried using a backup of complete stock, but when I booted the device with the restored backup, it was like only half of the ROM was restored. I was missing muliple of stock apps, and thos that was there didn't work. Not even settings.
Then I did my attempt at flashing the stock EMUI with the "dload" folder method. But every time I try it just says "Update Failed".
As I last resort I went to custom ROM's cause I need a device with basic Internet and phone supper atleast. But when I flash ANY custom ROM, it just reboots a few times and the screen stay black. It's like the device is still on, and I know this because when I plug it in my PC in this stage, windows gives out a unknown device plugged in.
I have been trying and googeling for the past two days. And I really am lost...
I apriciate any attempt to help me!
I registered my account on this website just to share my awesome experience with Nokia 1.
I am very much thankful to XDA and many other sites whose text assisted me in recovering my mobile.
WARNING: VERY LARGE TEXT BELOW AND ITS JUST MY EXPERIENCE, I AM NOT RESPONSIBLE IF SOMEONE TRY TO GET ANY IDEAS FROM IT AND BRICK HIS PHONE
I purchased Nokia 1 (TA-1047). My only objective was to automatically record sound from 8AM to 2 PM. So I started root process (Devmode: OK, boot loader unlock: OK, TWRP flashing and running: OK)
BUT WHAT? TWRP is asking for a password... this was not provided in the guide. I tried blank password... not OK. Then I searched the Internet and learned that if I cancel on password screen and then Wipe data then it will be fine. I did that, then made full backup (ADB), and flashed Magisk (ADB)..OK. Restarted the phone and "bump": Phone told me it failed to decrypt and then it went into TWRP boot-loop.
Then I searched again and found TA-1060 recovery bin (from this site) and stock images. I flashed TA-1060 recovery (at that time I did not know that I could go to Boot-loader from TWRP and wasted like an hour to do it using buttons - Correct method is: power off the phone, connect the usb cable, press power and volume down till you see android logo). After flashing 1060 recovery I was able to reset phone and "voila" Magisk was also there.
Now I installed Schedule Voice Recorder, Team-Viewer Host (to transfer big files remotely), App locker (to lock settings and play store), Autostart and Stay (because recorder was getting closed), Dropbox and Dropsync --- and you can guess what would have happened. My mobile kept closing them randomly even if I made Recorder and AutoStart system app and whitelisted in developer setting and set to NOT optimized battery. So I tried to disable Nokia bloat-wares and damaged the system again. This happened for a few iterations before I realized that the Nokia 1 RAM is not sufficient to handle all these apps and I got an idea to upload earlier android version (Spoiler! Hard-brick is coming).
I searched on internet for similar mobile and found Huawei Y3 2017 with same chipset and configuration, Y5 with same chipset but higher configuration. Downloaded stock rom for both. First tried flashing boot and system from TWRP but failed saying that size was different? Downloaded SP flash tool, somehow passed through drivers issue (this would require another thread ). Tried flashing (with formatting) both Y3 2017 UO00 (which was different chipset but i altered scatter file) and Y5 but it failed on some check error. After that my phone was hard bricked!
Then I downloaded nokia 1 stock firmware but it was bad scatter file (only nvram and nvdata was showing), altered it, format+flash: failed again. Searched on internet and found that if I flash wrong preloader then I am done. I was not sure if I had already done it. I altered the scatter file again to include only preloader and thankfully it showed success but any other rom after it, it failed to flash. Found something like Nokia 3 DA and tried it but also failed.
FINALLY: I found nokia 1 nb0 rom and nb0 extractor, extracted rom using that, flash it and "voila" my phone was back alive. Tried to root but failed (because serial number was not same as before and new number did not work). Then I started iterations by mixing roms from my backup and using my "proinfo.bin" and stock rom my phone revived with my own serial number. BUT, then I flashed stock preloader and lk but everything else from Huawei, it failed with check error and then also refused to format for stock rom. Searched on internet about manual formatting, did that (WARNING: starting from address where preloader ends otherwise you would format your preloader as well) then it was back okay.
Rooted again, copied scheduler in sys-priv, whitelisted, not optimize battery. Also team viewer host (normal settings) and dropbox and sync (normal settings). As a work around I have now scheduled the app to record 24 hours instead of 8AM to 2PM so that it always remain as foreground app. 11 hour testing so far so good.
QUESTION: Can I not upload lesser android version (e.g. 4.4 or 5 or 6)? If I can then how.?
UPDATE: The Recorder is killed by OS again as well as team viewer host (even when recorder apk was in system/priv-app)
Is there any way to keep it always ON?
Or is there any way to installed some previous version of android?
goodboy84h said:
UPDATE: The Recorder is killed by OS again as well as team viewer host (even when recorder apk was in system/priv-app)
Is there any way to keep it always ON?
Or is there any way to installed some previous version of android?
Click to expand...
Click to collapse
Every Nokia 1 user is facing background app crash problem. Infact Nokia 5 users also. It simply crashes background apps like pressing force close and as of now there is no solution. we have to wait until nokia releases a fix.
By the way which build number are you using?
coolboyforeva said:
Every Nokia 1 user is facing background app crash problem. Infact Nokia 5 users also. It simply crashes background apps like pressing force close and as of now there is no solution. we have to wait until nokia releases a fix.
By the way which build number are you using?
Click to expand...
Click to collapse
TA-1047
coolboyforeva said:
Every Nokia 1 user is facing background app crash problem. Infact Nokia 5 users also. It simply crashes background apps like pressing force close and as of now there is no solution. we have to wait until nokia releases a fix.
By the way which build number are you using?
Click to expand...
Click to collapse
Maybe you have so many apps in the background, I had Instagram, YouTube and Facebook life in the background and I get rare force closes or I might be lucky I have a Nokia 1 TA-1060
mattwhite7102 said:
Maybe you have so many apps in the background, I had Instagram, YouTube and Facebook life in the background and I get rare force closes or I might be lucky I have a Nokia 1 TA-1060
Click to expand...
Click to collapse
No its an os bug from nokia side. It fails to work as it should after a particular update. Maybe u r not facing coz u have only 3 apps that too light ones from good app makers, google and fb. But if u add some more like any call recorder ( as mentioned by op)u would also face same problem i believe. It doesnt thows a FC but simple kills the app in background and u dont get notified.
UPDATE :- Here is the solution
https://forum.xda-developers.com/showpost.php?p=77685710&postcount=4
goodboy84h said:
UPDATE: The Recorder is killed by OS again as well as team viewer host (even when recorder apk was in system/priv-app)
Is there any way to keep it always ON?
Or is there any way to installed some previous version of android?
Click to expand...
Click to collapse
Try this to avoid app crash. it works.
https://forum.xda-developers.com/showpost.php?p=77685710&postcount=4
HELP!!! Mine is stuck at Nokia logo screen
goodboy84h said:
I registered my account on this website just to share my awesome experience with Nokia 1.
I am very much thankful to XDA and many other sites whose text assisted me in recovering my mobile.
WARNING: VERY LARGE TEXT BELOW AND ITS JUST MY EXPERIENCE, I AM NOT RESPONSIBLE IF SOMEONE TRY TO GET ANY IDEAS FROM IT AND BRICK HIS PHONE
I purchased Nokia 1 (TA-1047). My only objective was to automatically record sound from 8AM to 2 PM. So I started root process (Devmode: OK, boot loader unlock: OK, TWRP flashing and running: OK)
BUT WHAT? TWRP is asking for a password... this was not provided in the guide. I tried blank password... not OK. Then I searched the Internet and learned that if I cancel on password screen and then Wipe data then it will be fine. I did that, then made full backup (ADB), and flashed Magisk (ADB)..OK. Restarted the phone and "bump": Phone told me it failed to decrypt and then it went into TWRP boot-loop.
Then I searched again and found TA-1060 recovery bin (from this site) and stock images. I flashed TA-1060 recovery (at that time I did not know that I could go to Boot-loader from TWRP and wasted like an hour to do it using buttons - Correct method is: power off the phone, connect the usb cable, press power and volume down till you see android logo). After flashing 1060 recovery I was able to reset phone and "voila" Magisk was also there.
Now I installed Schedule Voice Recorder, Team-Viewer Host (to transfer big files remotely), App locker (to lock settings and play store), Autostart and Stay (because recorder was getting closed), Dropbox and Dropsync --- and you can guess what would have happened. My mobile kept closing them randomly even if I made Recorder and AutoStart system app and whitelisted in developer setting and set to NOT optimized battery. So I tried to disable Nokia bloat-wares and damaged the system again. This happened for a few iterations before I realized that the Nokia 1 RAM is not sufficient to handle all these apps and I got an idea to upload earlier android version (Spoiler! Hard-brick is coming).
I searched on internet for similar mobile and found Huawei Y3 2017 with same chipset and configuration, Y5 with same chipset but higher configuration. Downloaded stock rom for both. First tried flashing boot and system from TWRP but failed saying that size was different? Downloaded SP flash tool, somehow passed through drivers issue (this would require another thread ). Tried flashing (with formatting) both Y3 2017 UO00 (which was different chipset but i altered scatter file) and Y5 but it failed on some check error. After that my phone was hard bricked!
Then I downloaded nokia 1 stock firmware but it was bad scatter file (only nvram and nvdata was showing), altered it, format+flash: failed again. Searched on internet and found that if I flash wrong preloader then I am done. I was not sure if I had already done it. I altered the scatter file again to include only preloader and thankfully it showed success but any other rom after it, it failed to flash. Found something like Nokia 3 DA and tried it but also failed.
FINALLY: I found nokia 1 nb0 rom and nb0 extractor, extracted rom using that, flash it and "voila" my phone was back alive. Tried to root but failed (because serial number was not same as before and new number did not work). Then I started iterations by mixing roms from my backup and using my "proinfo.bin" and stock rom my phone revived with my own serial number. BUT, then I flashed stock preloader and lk but everything else from Huawei, it failed with check error and then also refused to format for stock rom. Searched on internet about manual formatting, did that (WARNING: starting from address where preloader ends otherwise you would format your preloader as well) then it was back okay.
Rooted again, copied scheduler in sys-priv, whitelisted, not optimize battery. Also team viewer host (normal settings) and dropbox and sync (normal settings). As a work around I have now scheduled the app to record 24 hours instead of 8AM to 2PM so that it always remain as foreground app. 11 hour testing so far so good.
QUESTION: Can I not upload lesser android version (e.g. 4.4 or 5 or 6)? If I can then how.?
Click to expand...
Click to collapse
HELP: mine, TA-1047 is stuck at Nokia logo screen.
Please share me a life saver as you mentioned "I found nokia 1 nb0 rom and nb0 extractor, extracted rom using that, flash it and "voila" my phone was back alive."
I tried many many solutions like SP Flash Tool, Miracle Box, fastboot, .... but still failed and stuck.
I'm suffering day by day trying with no hope and now see your post. Please support me!
Much appreciate!
HELP!!!
My Nokia 1 (TA-1047) was hard bricked and won't turn on. I tried to flash my phone by SP Flashtool but my PC didn't recognize my phone. :crying::crying:
Could you give me the drivers you use and steps to recover my phone. Please help me. Thank u.