[SOLVED] Read careful through the thread, and if you have the same problem, check the messages on the second page for a solution
Hi all,
Recently got a Lenovo P780 4gb, Chinese version.
It came with VIBE UI 1.0, installed by the vendor.
Now, I wanted to have a different ROM without the Chinese characters here and there, and reading through the forums, I decided to flash a stock ROW version, and then upgrade to another custom ROM.
So I downloaded the 4Gb P780_S123_ROW_131231 version from elsewhere on the forum.
Using the SP Flash tool, it started flashing, and on the bottom I saw some info saying DRAM 8Gb, which worried me because I thought it might have been the wrong version, but the flash completed, green circle shown.
Then tried to reboot...nothing. Phone wouldn't even turn on.
Plugged it again into PC through USB, and the red light comes on, and instead of the device being recognized as a MT Preloader device, it now connects just as a MediaTek USB Port.
The SP Flash tool still recognizes 'something', but when trying to download or upgrade firmware (with another ROM), then the red progress bar goes to 100% quickly, but then hangs, and I see the error message in the log (timestamps removed):
BROM_DLL[4312][2988]: ERROR: MT6589EMISettingFactory::IsComboDiscreteDram(): Bootloader sub-version (MTK_BLOADER_INFO_SUB_VER_00) is not supported! (FlashToolLib/source/common/generic/src/emi_setting.cpp:557)
BROM_DLL[4312][2988]: ERROR: DummyEMISetting::GetDramEMISetting(): Unsupported! (FlashToolLib/source/common/generic/src/emi_setting.cpp:610)
BROM_DLL[4312][2988]: ERROR: FlashTool_Connect(0x05CA13A8): SyncWithDA(): fail! (FlashToolLib/sv5/common/generic/src/flashtool_api.cpp:937)
BROM_DLL[4312][2988]: ERROR: FlashTool_Connect(0x05CA13A8): fail! "S_FT_ENABLE_DRAM_FAIL"(4032). (FlashToolLib/sv5/common/generic/src/flashtool_api.cpp:990)
BROM_DLL[4312][2988]: com_sentry::Close(\\.\COM6, 0000284C): OK! (FlashToolLib/host/windows/com_sentry.cpp:650)
Now, the above error is supposedly caused by using an incorrect ROM. But what would be a correct one ? I assume chinese but what version or it doesn't matter ?
I also downloaded the P780_S135_130917_rooted_twrp_gapps but when opening the scatter file, I see an entry UBOOT that is not available in the ROM, and I cannot download it(above error) or upgrade (UBOOT missing).
Any tips or do I now have a fancy paperweight ?
casaben said:
Hi all,
Recently got a Lenovo P780 4gb, Chinese version.
It came with VIBE UI 1.0, installed by the vendor.
Now, I wanted to have a different ROM without the Chinese characters here and there, and reading through the forums, I decided to flash a stock ROW version, and then upgrade to another custom ROM.
So I downloaded the 4Gb P780_S123_ROW_131231 version from elsewhere on the forum.
Using the SP Flash tool, it started flashing, and on the bottom I saw some info saying DRAM 8Gb, which worried me because I thought it might have been the wrong version, but the flash completed, green circle shown.
Then tried to reboot...nothing. Phone wouldn't even turn on.
Plugged it again into PC through USB, and the red light comes on, and instead of the device being recognized as a MT Preloader device, it now connects just as a MediaTek USB Port.
The SP Flash tool still recognizes 'something', but when trying to download or upgrade firmware (with another ROM), then the red progress bar goes to 100% quickly, but then hangs, and I see the error message in the log (timestamps removed):
BROM_DLL[4312][2988]: ERROR: MT6589EMISettingFactory::IsComboDiscreteDram(): Bootloader sub-version (MTK_BLOADER_INFO_SUB_VER_00) is not supported! (FlashToolLib/source/common/generic/src/emi_setting.cpp:557)
BROM_DLL[4312][2988]: ERROR: DummyEMISetting::GetDramEMISetting(): Unsupported! (FlashToolLib/source/common/generic/src/emi_setting.cpp:610)
BROM_DLL[4312][2988]: ERROR: FlashTool_Connect(0x05CA13A8): SyncWithDA(): fail! (FlashToolLib/sv5/common/generic/src/flashtool_api.cpp:937)
BROM_DLL[4312][2988]: ERROR: FlashTool_Connect(0x05CA13A8): fail! "S_FT_ENABLE_DRAM_FAIL"(4032). (FlashToolLib/sv5/common/generic/src/flashtool_api.cpp:990)
BROM_DLL[4312][2988]: com_sentry::Close(\\.\COM6, 0000284C): OK! (FlashToolLib/host/windows/com_sentry.cpp:650)
Now, the above error is supposedly caused by using an incorrect ROM. But what would be a correct one ? I assume chinese but what version or it doesn't matter ?
I also downloaded the P780_S135_130917_rooted_twrp_gapps but when opening the scatter file, I see an entry UBOOT that is not available in the ROM, and I cannot download it(above error) or upgrade (UBOOT missing).
Any tips or do I now have a fancy paperweight ?
Click to expand...
Click to collapse
Hi. This phones are a little tricky to reflash after is softbriked. Just in case try to reflash with Life 0.7 for 4GB Firmware.
Here is the link:
http://forum.xda-developers.com/lenovo-p780/development/life-rom-lenovo-p780-t2666626
Here is a litle HOW TO in case of softbriked Lenovo P780:
Step by step you wil do this:
>>>>> USE WINDOWS 7 FOR THIS TUTORIAL <<<<<<<<<<<
>>>>>>>>>>REMOVE THE USB CALBLE FROM PHONE! <<<<<<<<<<<<<
NOW:
- Unpack FlashTools, and Click on Flash_tool.exe
- Select a the MT6589_Android_scatter_emmc.txt in ROM from target_bin folder
- Wait file to be added into Flash Tool
- choose Option->USB Model,click USB Model SKIP THIS STEP IFF SELECTED
–> Choose Option->DA DownLoad All->Speed->High Speed, click High Speed
- Turn off your phone - skip this step if is allready powered off
- "Press F9 (hit Download button)" OR " if upgrade ROM Firmware->Upgrade "
- and ONLY NOW connect your phone into the computer via USB data cable.
- The process will start and a red progress bar will appear after color purple, yellow.
- And green circles display
- Finish !
- You can now safely disconnect your phone and turn it on!
After this tell me iff something goes wrong !
OR
Tell me if your phone is from 04.2014 production.
If it is you must remove the checkbox of the preloader when you flash your custom ROM.
Also highly recommended before manipulation of the phone to do a full backup and backup of NVRAM.
Hi,
Well I flashed the initial ROM with everything checked, so don't know if that can be undone?
I tried flashing the life version you linked to, and tried some other stock roms (like P780_S125_130529,P780_S129_130710), but it's all the time the same.
I start the tool, then unplug phone, press reset button, then click download or upgrade firmware.
In the status bar of the tool, I see a speed in bps, EMMC, COM5 (as long as phone not plugged in, this is USB).
Other ROMS froze the timer in this status bar straight away, it remained 0:00 sec, but with the Life ROM, it keeps counting.
But in the end, it always ends with the same error.
I've attached the log, which includes multiple tries (with PRELOADER unchecked, then again with PRELOADER and PRELOAD unchecked, then with all checked, update and download).
Can't I do something like format it all, then do a fresh install ? Guess it's not that simple
I used the flashtool included, and SP_Flash_Tool_v3.1332.0.187, no difference.
Don't see production date, only see sticker with 02-5707-131911 Lenovo P780 and a number. CMIT ID : 2013CP5888 on the battery itself there is a number 140315
Thanks already for your help and tips.
casaben said:
Hi,
Well I flashed the initial ROM with everything checked, so don't know if that can be undone?
I tried flashing the life version you linked to, and tried some other stock roms (like P780_S125_130529,P780_S129_130710), but it's all the time the same.
I start the tool, then unplug phone, press reset button, then click download or upgrade firmware.
In the status bar of the tool, I see a speed in bps, EMMC, COM5 (as long as phone not plugged in, this is USB).
Other ROMS froze the timer in this status bar straight away, it remained 0:00 sec, but with the Life ROM, it keeps counting.
But in the end, it always ends with the same error.
I've attached the log, which includes multiple tries (with PRELOADER unchecked, then again with PRELOADER and PRELOAD unchecked, then with all checked, update and download).
Can't I do something like format it all, then do a fresh install ? Guess it's not that simple
I used the flashtool included, and SP_Flash_Tool_v3.1332.0.187, no difference.
Don't see production date, only see sticker with 02-5707-131911 Lenovo P780 and a number. CMIT ID : 2013CP5888 on the battery itself there is a number 140315
Thanks already for your help and tips.
Click to expand...
Click to collapse
Hi. Can you do something for me? Open the case of the phone. Look on the accumulator. Tell me iff on the label there is writen something with 04.2014.
stympy said:
Hi. Can you do something for me? Open the case of the phone. Look on the accumulator. Tell me iff on the label there is writen something with 04.2014.
Click to expand...
Click to collapse
Nope, Just the numbers from previous post, IMEI, SN, and some other number, but nothing like 04.2014.
The original ROM (when received), was VIBEROM_V1.0_1415_2_ST_P780_OLK_W_A291.
Only found this rom as CWM recovery flashable, not SP Flash.
But at this point, it seems hopeless
casaben said:
Nope, Just the numbers from previous post, IMEI, SN, and some other number, but nothing like 04.2014.
The original ROM (when received), was VIBEROM_V1.0_1415_2_ST_P780_OLK_W_A291.
Only found this rom as CWM recovery flashable, not SP Flash.
But at this point, it seems hopeless
Click to expand...
Click to collapse
Tonight ill try to download for you. I do not know how long it will take me to download the flashable with Flash Tools.
stympy said:
Tonight ill try to download for you. I do not know how long it will take me to download the flashable with Flash Tools.
Click to expand...
Click to collapse
Wow thanks The closest version I found on needrom is VIBEROM_V1.0_1415_DEV_P780_OLK_W_A291 but I don't know what format it is, it's still downloading.
And then again, I got it with this VIBEROM already flashed on it, and going into the settings and even built in diagnostics menu (when I could still get there) I don't recall seeing any version numbers even closely related to the numbers I find on the stock roms.
From the official VIBEUI site, it's the wrong format. The software version said something with name lenovohome.net, but I gave up on that, Chinese is beyond my knowledge and Google translate doesn't quite get it
Further, read some people advise just try to dowload PRELOADER, and others talk about volume- and power while plugging in (META-mode?).
But I guess that is not related to the problem.
As I understand it, PRELOADER and bootloader versions do not work together ?
It's a real pity since I used one of the official stock roms found on this site, and it actually flashed without problems.
PS : I see the option to format, including bootloader. In other roms I find UBOOT image. Is there something in this area that I can try
So... What i found is like this:
Your ex system is not a system that installs with Flash Tools.
Here is something what i found:
First Install
1. Flash rom china P780_S129_130710 with Flash Tools
2. Root rom china with Framaroot
3. Install MobileUncleTools
4. Install P780_CN_CWM-recovery with MobileUncleTools
Second Install From CWM
5. Install VIBEROM_V1.0_1415_2_ST_P780_OLK_W_A291.zip
6. Install GApps_Core_4.2.2.zip
7. Install SuperSU.zip
8. Wipe Data/Factory Reset
9. Reboot
Here is the Link:
https://drive.google.com/folderview?id=0B2ORIgaV4iacUk5wdEg3ejhhbGM&usp=sharing
stympy said:
So... What i found is like this:
Your ex system is not a system that installs with Flash Tools.
Here is something what i found:
First Install
1. Flash rom china P780_S129_130710 with Flash Tools
2. Root rom china with Framaroot
3. Install MobileUncleTools
4. Install P780_CN_CWM-recovery with MobileUncleTools
Second Install From CWM
5. Install VIBEROM_V1.0_1415_2_ST_P780_OLK_W_A291.zip
6. Install GApps_Core_4.2.2.zip
7. Install SuperSU.zip
8. Wipe Data/Factory Reset
9. Reboot
Ill upload the files Tonight iff you want !
Click to expand...
Click to collapse
I already tried that file, but it was no different than the others. I'm downloading it again from the link on this site (http://forum.xda-developers.com/lenovo-p780/general/stock-rom-lenovo-p780-stock-roms-guides-t2656441).
So hold off downloading/uploading any files
I appreciate your help in this matter, although the outlook of things is not so good right now.
casaben said:
I already tried that file, but it was no different than the others. I'm downloading it again from the link on this site (http://forum.xda-developers.com/lenovo-p780/general/stock-rom-lenovo-p780-stock-roms-guides-t2656441).
So hold off downloading/uploading any files
I appreciate your help in this matter, although the outlook of things is not so good right now.
Click to expand...
Click to collapse
Update : so no, same error.
Since nothing to loose at this point, decided to try SP Flash format (EXCEPT bootloader), and I spotted these lines in the log :
05/14/14 01:24:14.618 BROM_DLL[676][1172]: DEBUG: MT6589EMISettingFactory::LoadEMICfgSetting(): sizeof(BLoaderInfo_v05_ST)(112), m_identifier(MTK_BIN), m_version(V116"Ʉ3Щ, m_start_addr(0x700090), m_num_emi_settings(1). (FlashToolLib/source/common/generic/src/emi_setting.cpp:481)
05/14/14 01:24:14.618 BROM_DLL[676][1172]: DEBUG: MT6589EMISettingFactory::LoadEMICfgSetting(): Type(0x202) (FlashToolLib/source/common/generic/src/emi_setting.cpp:488)
05/14/14 01:24:14.618 BROM_DLL[676][1172]: DEBUG: MT6589EMISettingFactory::IsComboMCPDram(): EMI list size(1), index(0), type(202317c57ba). (FlashToolLib/source/common/generic/src/emi_setting.cpp:522)
Given the rom I use comes from a Russian forum, and I see Russian characters, it might be from the image, but maybe something relevant.
Would it help or make it worse to format everything including bootloader, then just flash ...well...something ?
casaben said:
Update : so no, same error.
Since nothing to loose at this point, decided to try SP Flash format (EXCEPT bootloader), and I spotted these lines in the log :
05/14/14 01:24:14.618 BROM_DLL[676][1172]: DEBUG: MT6589EMISettingFactory::LoadEMICfgSetting(): sizeof(BLoaderInfo_v05_ST)(112), m_identifier(MTK_BIN), m_version(V116"Ʉ3Щ, m_start_addr(0x700090), m_num_emi_settings(1). (FlashToolLib/source/common/generic/src/emi_setting.cpp:481)
05/14/14 01:24:14.618 BROM_DLL[676][1172]: DEBUG: MT6589EMISettingFactory::LoadEMICfgSetting(): Type(0x202) (FlashToolLib/source/common/generic/src/emi_setting.cpp:488)
05/14/14 01:24:14.618 BROM_DLL[676][1172]: DEBUG: MT6589EMISettingFactory::IsComboMCPDram(): EMI list size(1), index(0), type(202317c57ba). (FlashToolLib/source/common/generic/src/emi_setting.cpp:522)
Given the rom I use comes from a Russian forum, and I see Russian characters, it might be from the image, but maybe something relevant.
Would it help or make it worse to format everything including bootloader, then just flash ...well...something ?
Click to expand...
Click to collapse
Update : tried formatting including bootloader : same error.
Tried enabling/disabling different modules : same error.
Seems the phone is hard bricked...
casaben said:
Update : tried formatting including bootloader : same error.
Tried enabling/disabling different modules : same error.
Seems the phone is hard bricked...
Click to expand...
Click to collapse
Indeed... I think you should go to some service and take a look...
Send us some feedback when you get it back...
Good luck.
Sent from my Lenovo P780 using XDA Free mobile app
stympy said:
Indeed... I think you should go to some service and take a look...
Send us some feedback when you get it back...
Good luck.
Sent from my Lenovo P780 using XDA Free mobile app
Click to expand...
Click to collapse
Hi, in another thread, where you were also active, a user mentions P780_136_140306.
Do you know where I can get that ROM ? It would be the only ROM I didn't try yet
Thanks!
casaben said:
Hi, in another thread, where you were also active, a user mentions P780_136_140306.
Do you know where I can get that ROM ? It would be the only ROM I didn't try yet
Thanks!
Click to expand...
Click to collapse
Here is the link:
https://drive.google.com/folderview?id=0B2ORIgaV4iacT01mTm5JVzFuRGs&usp=sharing
Good Luck.
Problem SOLVED !
Hi,
The phone is back to life!
So, here is what I did: thanks to user stympy, who gave some valuable advise, and was actually on the right track.
The phones with a production date starting from 03.2014 have an updated PRELOADER. If you try to use flashing the PRELOADER of any other rom here on these phones, you'll end up like me.
The production date, I think, is printed on the battery (if you have a Chinese model at least).
YOU CANNOT FLASH A PRELOADER OF THE ROMS ON THE FORUM ON PHONES WITH A PRODUCTION DATE 03.2014 OR LATER (at this moment)
So, I found on a Russian forum (sorry XDA but for Lenovo there is a lot more to find on 4PDA than here), a backup of the correct,new preloader.
- I took the P780_S129_130710 ROM, and replaced the preloader.bin with the one in this rom.
- Next, deleted the checksum.ini file in the rom to avoid errors
- Open SPFT, selected the ROM, made sure PRELOADER entry was pointing to the correct preloader.bin
- USB disconnected, I clicked Download with DA DL All with checksum activated
- Plugged in USB
- Flashed without issue, disconnected, and voila, boot!!!
Well, that gave me a Chinese interface, but some screenshot tutorials enabled me to switch it to English.
I luckily took a backup with MobileUncleTools of my IMEI, since that was gone.
Phone seems to work normal, with 2 SIM cards, but a lot of Chinese bloatware.
While I was at it in SPFT, I tried to flash pre-rooted, or ROW versions, but that was unsuccessful so far. Always the good old 4032 error, although I updated the preloader, or some other failures.
However, the problem I'm trying to fight now, is the recovery mode. Can't backup (and not going to try flash ROM through recovery), since I can't mount /data, /emmc, and other crucial partitions. I'm using CWM. My goal is to flash the SLX ROM or any other rom with less bloatware, in English, and stable.
Update : Flashed :
- P780_S135_130917_rooted_twrp_gapps + modified preloader and works fine: had to manually link the UBOOT to the LK file (SPFT did not do it by itself)
- VIBEUI_V1.5_1419_5_DEV_P780_rooted_twrp_gapps + modified preloader and works fine : same problem with UBOOT
- Some other (Chinese) versions. ALWAYS put in the preloader file I attached, and everything went smooth and OK
Decided to not use CWM anymore, it's buggy. I use the built in TWRP recovery, and that works like a charm. No issues whatsoever.
Decided to keep VIBEUI_V1.5_1419_5_DEV_P780_rooted_twrp_gapps, but my preferred one until now was just the old stock version.
Simple and good
I've attached the preloader.bin I used (use at your own risk!), I guess it might come in handy for all of you with the same problem
Note that this particular preloader worked for me on a Chinese model 4Gb, production date 15/03/2014
And thanks again to Stympy for all the help!
casaben said:
Hi,
The phone is back to life!
So, here is what I did: thanks to user stympy, who gave some valuable advise, and was actually on the right track.
The phones with a production date starting from 03.2014 have an updated PRELOADER. If you try to use flashing the PRELOADER of any other rom here on these phones, you'll end up like me.
The production date, I think, is printed on the battery (if you have a Chinese model at least).
YOU CANNOT FLASH A PRELOADER OF THE ROMS ON THE FORUM ON PHONES WITH A PRODUCTION DATE 03.2014 OR LATER (at this moment)
So, I found on a Russian forum (sorry XDA but for Lenovo there is a lot more to find on 4PDA than here), a backup of the correct,new preloader.
- I took the P780_S129_130710 ROM, and replaced the preloader.bin with the one in this rom.
- Next, deleted the checksum.ini file in the rom to avoid errors
- Open SPFT, selected the ROM, made sure PRELOADER entry was pointing to the correct preloader.bin
- USB disconnected, I clicked Download with DA DL All with checksum activated
- Plugged in USB
- Flashed without issue, disconnected, and voila, boot!!!
Well, that gave me a Chinese interface, but some screenshot tutorials enabled me to switch it to English.
I luckily took a backup with MobileUncleTools of my IMEI, since that was gone.
Phone seems to work normal, with 2 SIM cards, but a lot of Chinese bloatware.
While I was at it in SPFT, I tried to flash pre-rooted, or ROW versions, but that was unsuccessful so far. Always the good old 4032 error, although I updated the preloader, or some other failures.
However, the problem I'm trying to fight now, is the recovery mode. Can't backup (and not going to try flash ROM through recovery), since I can't mount /data, /emmc, and other crucial partitions. I'm using CWM. My goal is to flash the SLX ROM or any other rom with less bloatware, in English, and stable.
I've attached the preloader.bin I used (use at your own risk!), I guess it might come in handy for all of you with the same problem
And thanks again to Stympy for all the help!
Click to expand...
Click to collapse
Thank you for your feedback. I hope this information that you gived us today will help other people too.
Sent from my Lenovo P780 using XDA Free mobile app
The same problem, but...
Hi, I have the same problem - chinese P780 4GB, brand new, 04-2014.
After flashing wrong (as i know it now, but not 2 hours ago) ROM P780_S135_130917_rooted_twrp_gapps my brand new P780 don't want to turn on and seems to be bricked. :crying:
During flashing everything was ok - no errors, mistakes, or something something else wrong. Flashing finished with green circle. I've read carefully all the posts in this thread but I can not repeat your solution cause now Flash Tool can't connect to device. When USB cable is plugged into the phone red light turn on, but my computer didn't see any new devices - no "MTK USB port", or "Android device" or even "unknown device".
Any suggestions?
nagoHaK said:
Hi, I have the same problem - chinese P780 4GB, brand new, 04-2014.
After flashing wrong (as i know it now, but not 2 hours ago) ROM P780_S135_130917_rooted_twrp_gapps my brand new P780 don't want to turn on and seems to be bricked. :crying:
During flashing everything was ok - no errors, mistakes, or something something else wrong. Flashing finished with green circle. I've read carefully all the posts in this thread but I can not repeat your solution cause now Flash Tool can't connect to device. When USB cable is plugged into the phone red light turn on, but my computer didn't see any new devices - no "MTK USB port", or "Android device" or even "unknown device".
Any suggestions?
Click to expand...
Click to collapse
Here is a litle HOW TO in case of softbriked Lenovo P780:
Step by step you wil do this:
>>>>> USE WINDOWS 7 FOR THIS TUTORIAL <<<<<<<<<<<
>>>>>>>>>>REMOVE THE USB CALBLE FROM PHONE! <<<<<<<<<<<<<
NOW:
- Unpack FlashTools, and Click on Flash_tool.exe
- Select a the MT6589_Android_scatter_emmc.txt in ROM from target_bin folder
- Wait file to be added into Flash Tool
- choose Option->USB Model,click USB Model SKIP THIS STEP IFF SELECTED
–> Choose Option->DA DownLoad All->Speed->High Speed, click High Speed
- Turn off your phone - skip this step if is allready powered off
- "Press F9 (hit Download button)" OR " if upgrade ROM Firmware->Upgrade "
- and ONLY NOW connect your phone into the computer via USB data cable.
- The process will start and a red progress bar will appear after color purple, yellow.
- And green circles display
- Finish !
- You can now safely disconnect your phone and turn it on!
Flash this one: https://drive.google.com/folderview?id=0B2ORIgaV4iacT01mTm5JVzFuRGs&usp=sharing
It will work.
PROBLEM SOLVED / Thx casaben
Hello,
today i tried to flash my P780. The Build-Number of my phone was P780_S136_140306.
I flashed ROM P780_S135_130917_rooted_twrp_gapps with Smart Phone Tools and after that my phone was dead.
I flashed this ROM because i want to flash the ROM AOSP-4.4.2-v.1.8 after that.
Thx stympy for your tutorial to bring back my phone back to life!
I don´t know if my phone is chinese or not. There is no date on the battery, only chinese letters.
I need help to flash ROM AOSP-4.4.2-v.1.8.
Thx
Related
I have just received my Iocean X7 Elite and was about to install a new rom. I had successfully rooted the device and then was trying to flash
the recovery with SP Flash Tool.
After the recovery flashed my phone refuses to turn on I believe its somehow bricked but have no idea how this could have happened. I did
format flash i only downloaded the recovery to the device.
In Device Manager when i plug the phone it it either shows up as 'DA USB VCOM Port' or 'MTK USB Port'.
When I try to use SP Tool to flash the stock Rom back onto the device I get an error saying 'BROM ERROR : S_FT_ENABLE_DRAM_FAIL(4032)'
I have no idea what to do next can someone help me.
I have tried what this thread suggests:
bump
same as u..but differ phone model.(N9589)
had a few upgrd...til the recent brick it.
Tried a few version of flash tool and still the same
Joshafc said:
I have just received my Iocean X7 Elite and was about to install a new rom. I had successfully rooted the device and then was trying to flash
the recovery with SP Flash Tool.
After the recovery flashed my phone refuses to turn on I believe its somehow bricked but have no idea how this could have happened. I did
format flash i only downloaded the recovery to the device.
In Device Manager when i plug the phone it it either shows up as 'DA USB VCOM Port' or 'MTK USB Port'.
When I try to use SP Tool to flash the stock Rom back onto the device I get an error saying 'BROM ERROR : S_FT_ENABLE_DRAM_FAIL(4032)'
I have no idea what to do next can someone help me.
I have tried what this thread suggests:
Click to expand...
Click to collapse
Same problem here - tried to install stock firmware and got this error...
these are common problems when flashing MT65xx based phones,
ie : error 4008, 4xxx, 5xxx whatever those codes mean, no explanation after extensive search on google.
once I managed to flash this one phone successfully, but I don't know exactly what I did.
as long as I recall, I tried to delete the whole flashtool folders, re-extract them, let the phone cool down a bit
and oh, try to press volume up, or down button (varies on devices) while connecting to USB, once the flashing progress bar starts, release the button.
In the flashtool option, at the OPTIONS-->DA DOWNLOAD ALL-->, check WITHOUT BATTERY.
and in the option, DA DOWNLOAD ALL--> SPEED, check DO NOT SWITCH SPEED.
try flashing your phone without battery inserted, it works many times for me.
NOTE : BEWARE, flashing your MTK65xx based phone, sometimes this tool tried to REMOVE YOUR PHONE's IMEI information, so take caution !
I haven't managed how to prevent IMEI removal when flashing those phones, because I'm not a developer.
Hope this helps.
tukulll said:
these are common problems when flashing MT65xx based phones,
ie : error 4008, 4xxx, 5xxx whatever those codes mean, no explanation after extensive search on google.
once I managed to flash this one phone successfully, but I don't know exactly what I did.
as long as I recall, I tried to delete the whole flashtool folders, re-extract them, let the phone cool down a bit
and oh, try to press volume up, or down button (varies on devices) while connecting to USB, once the flashing progress bar starts, release the button.
In the flashtool option, at the OPTIONS-->DA DOWNLOAD ALL-->, check WITHOUT BATTERY.
and in the option, DA DOWNLOAD ALL--> SPEED, check DO NOT SWITCH SPEED.
try flashing your phone without battery inserted, it works many times for me.
NOTE : BEWARE, flashing your MTK65xx based phone, sometimes this tool tried to REMOVE YOUR PHONE's IMEI information, so take caution !
I haven't managed how to prevent IMEI removal when flashing those phones, because I'm not a developer.
Hope this helps.
Click to expand...
Click to collapse
Thank you for your reply, but this doesn't help... ;(
Anyone?
I think I figured out that the error above means you are trying to flash an incorrect ROM. Make sure you are using the right one and also make sure you're using the latest version of sp flash tool.
Once I downloaded a later version of the flash tool it began installing the ROM but then a different error appeared.
So I formatted the nand with the sp flash tool.
Then I flashed the stock ROM again and it worked
Formatting it seemed to make the errors go away even though its advised not to do so.
Sent from my iOCEAN X7 using xda app-developers app
vessk0 said:
Anyone?
Click to expand...
Click to collapse
I fixed this error by completely removing and reinstalling other drivers for mtk vcom loader
anyone heard Iocean will recall all of the x7 elite's? i've had a mail today they should do it, but i don't know if it's true or not.
Schumi_wk said:
anyone heard Iocean will recall all of the x7 elite's? i've had a mail today they should do it, but i don't know if it's true or not.
Click to expand...
Click to collapse
I haven't heard about that. Maybe its a fake email. Did it say what the fault was?
Joshafc said:
I think I figured out that the error above means you are trying to flash an incorrect ROM. Make sure you are using the right one and also make sure you're using the latest version of sp flash tool.
Once I downloaded a later version of the flash tool it began installing the ROM but then a different error appeared.
So I formatted the nand with the sp flash tool.
Then I flashed the stock ROM again and it worked
Formatting it seemed to make the errors go away even though its advised not to do so.
Sent from my iOCEAN X7 using xda app-developers app
Click to expand...
Click to collapse
How to format the nand with sp flash tool, I use the latest version?
And can you point me to good original stock ROM?
Thank you!
lolet said:
I fixed this error by completely removing and reinstalling other drivers for mtk vcom loader
Click to expand...
Click to collapse
I tried reinstalling drivers, also tried other drivers, but this doesn't help...
I've had the same problem with the following installation Sp Tools
SP_Flash_Tool_exe_v3.1316.0.150
Rom: MP_mt89_v9_iocean_ousheng_jb2_20130520-184014_zhongyeqing_PC
http://d-h.st/ESX
Iocean X7 Youth
I don't have the same problem but i flashed the latest version of official rom for iOcean x7 Youth : 03 july 2013 : and wtf no more internal sdcard only the rom stockage. So i can't download anything, i can't use camera .
On the official website, I read that before flashing the 20 may 2013 rom one and the 03 July 2013 one, your baseband version have to be 23/04 or higher( you have to flash the 23/04 official rom first). This is only avalaible for the YOUTH version.
So tomorrow i will try what i said below to see if i have internal sd card again.
noob question::: since the iocean x7 young and turbo are the same phones...only different clock rates...will flashing the firmware for turbo on iocean x7 young work??assuming that the mtk6589T and mtk6589 are the same chipset only different clock rates??
Micromax A116 (Cant flash Rom)Brick Problem Solved
tukulll said:
these are common problems when flashing MT65xx based phones,
ie : error 4008, 4xxx, 5xxx whatever those codes mean, no explanation after extensive search on google.
once I managed to flash this one phone successfully, but I don't know exactly what I did.
as long as I recall, I tried to delete the whole flashtool folders, re-extract them, let the phone cool down a bit
and oh, try to press volume up, or down button (varies on devices) while connecting to USB, once the flashing progress bar starts, release the button.
In the flashtool option, at the OPTIONS-->DA DOWNLOAD ALL-->, check WITHOUT BATTERY.
and in the option, DA DOWNLOAD ALL--> SPEED, check DO NOT SWITCH SPEED.
try flashing your phone without battery inserted, it works many times for me.
NOTE : BEWARE, flashing your MTK65xx based phone, sometimes this tool tried to REMOVE YOUR PHONE's IMEI information, so take caution !
I haven't managed how to prevent IMEI removal when flashing those phones, because I'm not a developer.
Hope this helps.
Click to expand...
Click to collapse
Thanks a lot. My Micromax a116 was brick. Now its alive.
Here I am with the same problem in a N920e... AND IT'S NOT MINE! :crying:
I'll have to pay it to the owner if I can't solve this:
DaniPhii said:
Here I am with the same problem in a N920e... AND IT'S NOT MINE! :crying:
I'll have to pay it to the owner if I can't solve this:
View attachment 2243401
Click to expand...
Click to collapse
Clearly: Wrong driver. I had also this error. SPflash tool did not readback. I did not flash anything! I fixed this by showing the nonpresent devices in devicemanagement (google for show nonpresent devices for explanation)
Go to com ports, and delete all mediatek drivers except preloader driver. Now start over. It can help if you choose the same usb port where you had success last time.
SP flash tool shows in the statusbar which driver it is using.
mistraller said:
Clearly: Wrong driver. I had also this error. SPflash tool did not readback. I did not flash anything! I fixed this by showing the nonpresent devices in devicemanagement (google for show nonpresent devices for explanation)
Go to com ports, and delete all mediatek drivers except preloader driver. Now start over. It can help if you choose the same usb port where you had success last time.
Click to expand...
Click to collapse
Yes, you got it
SP Flash Tool couldn't find my phone, but now it works
It's exactly a windoze driver problem.
Going to devicemanagement, in LAN-Devices I a had an Alcatel device,
chosing driver by hand and use the mtk usb driver, now Flashtool finds the phone
Thanks a lotttttttt....
shiv.kbh said:
Thanks a lot. My Micromax a116 was brick. Now its alive.
Click to expand...
Click to collapse
Thanks a lot man i unbricked my bolt a58 with this...thanks thanks...
Hello guys, it's nice to be part of this great community. My English are not that good so please be patient with my explanations.
Well , I'm quite desperate here. A friend of mine gave me this phone (Xiaomi Redmi 1) bricked.
First of all the mobile can't boot, it says tool dl image fail. Even worst I can't even select the options in the boot menu, the tool dl image fail appears again. That means the memory is almost empty...
According to my experience the solution was only 1, Flash tools.
But again , I tried the Firmware/Update option of these ROMs: Xiaomi Hongmi WCDMA (HM2013023_images_JHBCNAL5.0_4.2)/ TD (Hongmi_images_HBJ2.02_4.2) - unbrick 5.0 and....NOTHING!
If I choose the download option but the bar reaches only 1% and theen I have this : s_ft_download_fail (4008). I tried the HM2013023_images_JHBCNAH4.0_4.2 but with the same results.
An extra detail is that IF I choose the format option, althought it doesn't complete...my mobile doesn't open after that. In order to be working again, I just have to choose the download option (till the 1%) and the it boots with the above problems.
To be more clear I installed the necessary drivers, I removed them, I installed them again...NOTHING. I changed the USB port, the same results..
An interesting quotation is that if I try to connect the device with a different USB cable that the original, the pc doesn't even recognize it (mobile). Also, I've noticed that the flash tools cannot install these (from the scatter) : Android, Cache, UserData & Fat.
As for the CMW Recovery ... no luck at all. They are all in image format which means, I can not install it.
Any help will be appreciated....althought I'm pretty sure the phone is 99% dead..
Any news?
Scattyyy said:
Hello guys, it's nice to be part of this great community. My English are not that good so please be patient with my explanations.
Well , I'm quite desperate here. A friend of mine gave me this phone (Xiaomi Redmi 1) bricked.
First of all the mobile can't boot, it says tool dl image fail. Even worst I can't even select the options in the boot menu, the tool dl image fail appears again. That means the memory is almost empty...
According to my experience the solution was only 1, Flash tools.
But again , I tried the Firmware/Update option of these ROMs: Xiaomi Hongmi WCDMA (HM2013023_images_JHBCNAL5.0_4.2)/ TD (Hongmi_images_HBJ2.02_4.2) - unbrick 5.0 and....NOTHING!
If I choose the download option but the bar reaches only 1% and theen I have this : s_ft_download_fail (4008). I tried the HM2013023_images_JHBCNAH4.0_4.2 but with the same results.
An extra detail is that IF I choose the format option, althought it doesn't complete...my mobile doesn't open after that. In order to be working again, I just have to choose the download option (till the 1%) and the it boots with the above problems.
To be more clear I installed the necessary drivers, I removed them, I installed them again...NOTHING. I changed the USB port, the same results..
An interesting quotation is that if I try to connect the device with a different USB cable that the original, the pc doesn't even recognize it (mobile). Also, I've noticed that the flash tools cannot install these (from the scatter) : Android, Cache, UserData & Fat.
As for the CMW Recovery ... no luck at all. They are all in image format which means, I can not install it.
Any help will be appreciated....althought I'm pretty sure the phone is 99% dead..
Click to expand...
Click to collapse
any news??
I have the phone (hongmi) bricked too....
when I try to use SP Flash tool after choose the correct rom, i try to fix the firmware and after done 100%(red bar) an error comes out (4032)....
My phone sometimes start (but goes in black screen quickly) often NO.... do you have any information for me? Or some other forum that can I check)
Tnx in advance
So, here is the firmware flash guide for B15Q. It assumes either a Win7 x86 machine or a x64 with driver signature verification disabled (but Win8/8.1 in any variant or W7x64 is NOT RECOMMENDED).
I assume no warranty for bricked devices, especially not if you manage to kill your PRELOADER or DSP_BL. Double and triple check before downloading.
0) Driver and toolkit setup
Get the driver set, scatter file and spFlashTool from this thread: http://forum.xda-developers.com/general/general/stock-rom-cat-b15q-rom-development-t2988774
Remove back shell from phone, remove battery (!)
Attach phone via USB. Windows should now, approx. once every 2-3s, make a sound similar as if you put in a USB stick and then pull it out again.
Start=>Run=>devmgmt.msc, in the View menu choose "Devices by connection"
Click yourself through the tree until you find an unknown device (MT65xx Preloader or similar)
Rightclick on the device and press "Install drivers"; you shall find the drivers in "MTKUsbAll_0.9.2\New inst. win 7&8x64" folder.
Launch "SP Flash Tool v5.1352.01\flash_tool.exe"
In the tab "Download", click on the "Scatter loading" button and select the downloaded file "MT6582_Android_scatter.txt". spFlashTool usually remembers this across restarts.
Unplug the phone at the computer side if you want to work with it later (the MicroUSB ports don't like too many inserts, they wear out physically).
A) ReadBack for backup of existing firmware/userdata
This will involve a ****load of typing for the first readback.
Open the scatterfile using Notepad++ or any editor capable of handling UNIX line endings, NOT notepad
You will see a lot of blocks like
Code:
- partition_index: SYS0
partition_name: PRELOADER
file_name: preloader.bin
is_download: true
type: SV5_BL_BIN
linear_start_addr: 0x0
physical_start_addr: 0x0
partition_size: 0xC00000
region: EMMC_BOOT_1
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: BOOTLOADERS
reserve: 0x00
In spFlashTool, select the "Readback" tab.
For all the blocks you see in the scatterfile (IDs 0-23), repeat the following:
Click "Add"
Double-click on the newly appeared row
Choose a filename (e.g. preloader.bin for the first block; some blocks will have name = NONE, use the partition_name here for the filename) and click SAVE
A window "Readback block start address" will appear
Choose Type = "hex". Copy (Ctrl+C,Ctrl+V, and take care to exactly select the hex value! Do NOT type the hex values by hand!) the value from linear_start_address (with the 0x) into the "Start address" box and the partition_size value in the "Length" box, press OK.
Unless you are at the SYS23 partition BMTPOOL, proceed to the next block, repeat from above.
The SYS23 partition can not be backed up, because it has invalid lengths. Do not enter it into spFlashTool.
CHECK THE VALUES FOR START ADDRESS AND LENGTH IN THE TABLE. CHECK THEM ANOTHER TIME.
Press "Read back" button at the top.
Plug in the phone with the battery removed(!) and wait. This process will take time and consume approx. 3-4GB of disk space.
Archive the files you created somewhere safe. Do NOT distribute anything to other people except the BOOTIMG, RECOVERY and ANDROID partitions, because the other partitions contain data that is hardcoded to your board (e.g. IMEI/MAC addresses, sensor calibrations,...) or your private data and app data (SYS22/USRDATA).
If you want a full backup to disassemble by hand lateron (aka you trust in nothing going wrong and don't want to do the hard work except when you need it), just create one readback section with start=0x0 and length=0xE5720000 - this backups everything in one file.
B) Download for flashing new firmware
In spFlashTool, select the "Download" tab
In the dropdown box below the scatter file, keep it at "Download only" or set it if this is not the case
Uncheck all the boxes in the table
Double click on the "Location" column of the BOOTIMG, RECOVERY, ANDROID or USRDATA rows which you want to flash, select the appropriate image file.
Check that you selected the correct images for the correct partitions!
CHECK THAT ONLY THE ROWS WHICH YOU WANT TO FLASH ARE CHECKED. ESPECIALLY, NEVER EVER CHECK THE PRELOADER, MBR AND EBR PARTITIONS. YOU HAVE BEEN WARNED.
Press Download
Plug in the phone with the battery removed and wait. spFlashTool will tell you when it's done.
Unplug phone from computer (!) and put in the battery.
If you get an error "PMT changed for the ROM; it must be downloaded", reboot your machine.
When you have a running ROM on it, you may also try to keep the battery in the phone during flashing; just press Download on the PC, then select Shutdown in the Android menu that appears after holding Power pressed. Once the phone has shut down, it will vibrate shortly and then be detected by spFlashTool. I also recommend using a high-quality USB cable and not a worn out one because USB cables with worn out plugs may lead to issues during transmission.
NAND reflush?
Excellent stuff you wrote here - thank you.
Any hints on how to resurrect dead B15Q that has damaged/erased NAND or a Preloader?
In this link http: // forum . xda-developers . com/ showthread.php?t=1943442 a forum member
claims that mt65xx have META mode even if they appear dead - like mine B15Q is right now - and could be
revived with SPFT and proper W7 drivers.
Does under those circumstances PRELOADER might be reflashed?
I read just afterwards that one should not do fully ticked Memory Test as it silently reformats NAND.
I guess this is what happened in my case.
Also, a reason to do this test was that reflashing the phone with 1.010 BOOTIMG, ANDROID and RECOVERY, having it back for a brief moment and then upgrading it via OTA to 1.019 that had bricked it in a reboot loop.
Any clue would be welcome.
uhuru-meditation said:
Excellent stuff you wrote here - thank you.
Any hints on how to resurrect dead B15Q that has damaged/erased NAND or a Preloader?
In this link http: // forum . xda-developers . com/ showthread.php?t=1943442 a forum member
claims that mt65xx have META mode even if they appear dead - like mine B15Q is right now - and could be
revived with SPFT and proper W7 drivers.
Does under those circumstances PRELOADER might be reflashed?
I read just afterwards that one should not do fully ticked Memory Test as it silently reformats NAND.
I guess this is what happened in my case.
Also, a reason to do this test was that reflashing the phone with 1.010 BOOTIMG, ANDROID and RECOVERY, having it back for a brief moment and then upgrading it via OTA to 1.019 that had bricked it in a reboot loop.
Any clue would be welcome.
Click to expand...
Click to collapse
Bigal1337's image should also contain a preloader, but I guess in your total-dead state it'd be better to send in the device for warranty... after all no one can prove what exactly zeroed out your NAND.
harddisk_wp said:
.....but I guess in your total-dead state it'd be better to send in the device for warranty... after all no one can prove what exactly zeroed out your NAND.
Click to expand...
Click to collapse
It is all OK now and B15Q is alive and works well, as it did before the "big brick" Christmas blackout.
The main thing is that thanks to MTK low-level USB communication on chipset as is in B15Q makes it "unbrickable", really.
The other thing is my bad clicking around and "checking memory" while not really knowing what I am doing.
As well as Windows x64 drivers, admin rights and all the other voodoo lurking in there.
What troubles me more is how come that CAT ppl. allowed "bricking" device upon system update, while root or no root shouldn't really matter there?
They sell it unlocked, so they should sell it, as well, with an easy option to root it. As Nexus One from Google had this "build-in" option.
I still hope that future updates will not have the same behaviour and also that there will be an alternate option for some other flavour of Android.
uhuru-meditation said:
It is all OK now and B15Q is alive and works well, as it did before the "big brick" Christmas blackout.
The main thing is that thanks to MTK low-level USB communication on chipset as is in B15Q makes it "unbrickable", really.
The other thing is my bad clicking around and "checking memory" while not really knowing what I am doing.
As well as Windows x64 drivers, admin rights and all the other voodoo lurking in there.
What troubles me more is how come that CAT ppl. allowed "bricking" device upon system update, while root or no root shouldn't really matter there?
They sell it unlocked, so they should sell it, as well, with an easy option to root it. As Nexus One from Google had this "build-in" option.
I still hope that future updates will not have the same behaviour and also that there will be an alternate option for some other flavour of Android.
Click to expand...
Click to collapse
I think I have found something... this chinese rooter apparently messed with internal symlinks, and the firmware update broke as it assumed "stock" contents...
Another reason not to trust rooters where one can't even read the description because its chinese...
harddisk_wp said:
Another reason not to trust rooters where one can't even read the description because its chinese...
Click to expand...
Click to collapse
I agree there. I gave up on rooting B15Q.
On the side note: lately I had 2 spontaneous reboots after this reflash and resurrect.
It happened after I used "official" messaging app more precisely after I send a message and close the app..
.
Did anyone noticed this? - it is 1022 I have up and running.
Other than that it works fine.
Hello,
I tried your workaround but haven't succeeded yet. And yes my phone also is bricked, unfortunately.
My phone halts where you have to choose a language after a factory reset. At that moment I get some messages that some services had stopped. Like Google keyboard, Youtube and some more. I can click OK but this doesn't get me passed these messages and they reappear. I only can switch off the phone.
I tried your workaround on a x64 machine (and got the PMT message) because that's what I have. I am preparing a x86 machine which has XP on it but on launching SP Flash Tools I get the message the configuration of the computer is not correct. Will W7 32-bits do the trick?
Also two more questions.
The downloaded images are : boot.img, recovery.img, system.img and uboot.img.
In your explanation you're mentioning : BOOTIMG, RECOVERY, ANDROID or USRDATA.
I presume that in SP Flash Tool I have to use the system.img in the row ANDROID?
Or should it be in the row USRDATA?
You don't use uboot.img. What's the reason for that? For what purpose is this image?
Update 19 april 2015.
I managed bringing back my phone to life. I did another attempt by rebooting my 64-bits computer (as you wrote in the beginning) because at that moment I didn't had a 32-bits machine. It worked wonderwell. So, I'm using my phone again. Like uhuru-meditation I give up rooting for the moment. Nevertheless Android 4.4.2 I still like this phone. Hope it won't let me down after this major reset. Keep fingers crossed.
harddisk_wp many thanks for your hard working in making this workaround. It sure has cost you more then an hour's work.
I hope you read my questions and can or will answer them.
CAT B15 help
Hi guys, i'm sorry i have to ask this in this forum but i've been asking for a couple of months now, and got no answer. I have a CAT B15 (not the B15Q). It is single sim version (IMEI write on the back) and i managed to do plenty of things in it. I swapped memory and worked fine, and even i installed a Dual Sim android rom and i managed to use the secondary Sim bay in it (that was tapped with a plastic fake sim) and used the phone with 2 sims for like 2 weeks. Then i started to play with deodex and build.prop and softbricked the phone, but it was piece of cake since it is easy to unbrick. The problem was that i wrongly flashed the phone with scatter file, and flashed all partitions in it, EBR1, MBR, UBOOT, etc, etc. The result was a non-working dual SIM phone. Everything works, but the SIMS, it does not detect any SIMs in it, in any of the SIM bays, and the IMEIs are wrong numbered. I did no buckup of the phone so i'm pretty screwed. I've been asking for someone to upload the EMEA_SS or US_SS ROM for the CAT B15, but nobody responded. I thaught maybe the CAT B15Q has a similar software/bands flashing partitions, but that i leave to you for answer. Anyway, if any of you has the possibility of taking the images of a single sim CAT B15 it would save me this awesome phone for me. I'm also willing to give a 20GB account of ownCloud server for 1-year free of charge if storage space is needed, no problem. This are the links i've been searching and asking.
All About CAT B15: http://forum.xda-developers.com/show....php?t=2430904
Root for Catterpillar B15: http://forum.xda-developers.com/show....php?t=2263455
Best regards,
2 Questions
Good day
I have the same questions as a previous user, but I cannot find any answer to it:
"Also two more questions.
The downloaded images are : boot.img, recovery.img, system.img and uboot.img.
In your explanation you're mentioning : BOOTIMG, RECOVERY, ANDROID or USRDATA.
I presume that in SP Flash Tool I have to use the system.img in the row ANDROID?
Or should it be in the row USRDATA?
You don't use uboot.img. What's the reason for that? For what purpose is this image?"
Could you please help with these? Should I use uboot.img as well? And does system.img go to the Android row?
I added this 3d question later: is it safe to flash SS phone with the DS file?
Kind regards
"PMT changed for the ROM" and SP Flash Tool version
Hello,
I'd like to say big thanks and report that my B15Q was saved thanks to this thread, after a failed upgrade to the 1.016.00 firmware (due to the Chinese root app).
Moreover, I would like to point out that the procedure worked only with the v5.1352.01 version of SP Flash Tool. All other versions I've tried bailed out with the "PMT changed for the ROM; it must be downloaded" message. Unfortunately, the thread which is listed in the instructions refers to a version of SP Flash Tool more recent than v5.1352.01. A link to the said version can be found in this post: http://forum.xda-developers.com/showpost.php?p=58810386&postcount=4
Regards,
Aurél
harddisk_wp said:
0) Driver and toolkit setup
Get the driver set, scatter file and spFlashTool from this thread: http://forum.xda-developers.com/general/general/stock-rom-cat-b15q-rom-development-t2988774
Remove back shell from phone, remove battery (!)
Attach phone via USB. Windows should now, approx. once every 2-3s, make a sound similar as if you put in a USB stick and then pull it out again.
Start=>Run=>devmgmt.msc, in the View menu choose "Devices by connection"
Click yourself through the tree until you find an unknown device (MT65xx Preloader or similar)
Rightclick on the device and press "Install drivers"; you shall find the drivers in "MTKUsbAll_0.9.2\New inst. win 7&8x64" folder.
Launch "SP Flash Tool v5.1352.01\flash_tool.exe"
...
...
If you get an error "PMT changed for the ROM; it must be downloaded", reboot your machine.
Click to expand...
Click to collapse
my b15 loopboot
Hello such greetings from Venezuela have a cat b15q dual sim to load the firmware with sp flashtool v3 makes the whole process but remains frozen on the logo even doing a wipe and there no moves have the rom that is posted here I can I am doing wrong excuse my English but I use a translator
Thanks on advanced . Worked fine on my b15q cat . Really much apreciated .
Hello, I'd like to say big thanks and report that my B15Q was saved thanks .Thanks this rom launch perfect
uhuru-meditation said:
It is all OK now and B15Q is alive and works well, as it did before the "big brick" Christmas blackout.
The main thing is that thanks to MTK low-level USB communication on chipset as is in B15Q makes it "unbrickable", really.
...
Click to expand...
Click to collapse
Would you please care to share how you achieved that?
(Following some guide which said that upon ""PMT changed for the ROM..." error one should format the device before downloading, we did that (after reading back everything) but unfortunately, spFlashTool doesn't like the readback PRELOADER partition we extracted.)
goodnight I hope will help me have a cat b15q and remained in recovery mode and I need to flash it revive hope help me thank you .. I'm from Venezuela and one who does not get that software. Excuse my English but q use the translator
CAT B15Q - My Rear Camera doesn't work anymore
Good evening everyone.
After a bad update, my rear camera on CAT B15Q doesn't work anymore. I read all the posts here and I'm using Windows Vista Home Premium 32 bits. I downloaded all the necessary files and when I open the SP Flash Tool, I think it didn't recognize my smartphone and when I try to download any file to the phone the status bar on SPFT still stopped, like if anything is going on. I buy this B15Q on Paraguay. Could this fact be my problem? Anyone could help me, please???
Hello , Guys
Since you all probably know, Lenovo A7020a48 has Android 6.0 Marshmallow which cannot be rooted because of the following :
1 - We got a locked bootloader, we can't flash or boot into custom recoveries and sadly at the moment I couldn't find a way to unlock it.
2 - We don't even have a custom recovery made for that model yet, I tried different version of TWRP for A7020a40 ~ A7020a46 models and they all crashed upon booting to them.
3 - Kingroot and similiar apps can't root Android 6.0.
So the only way to root your phone would be to downgrade it to Android 5.1 Lolipop which is easy.
Here is download links for the stock roms :
A7020a48_LL_S125_160419_ROW.rar.7z
A7020a48_S259_160721_ROW.7z
When you finish downloading please don't forget that we are going to use the SP Flash Tool provided in the rom as only that version "SP_Flash_Tool_5.1552.00" worked for me with no errors however with latest versions i got problems.
Obviously you are going to install the USB drivers and CDC drivers located at the "DRV_Tools" folder in the rom you downloaded.
after installing the drivers correctly turn off your phone, open SP flash tool, and choose the scatter file located at : "\SW\target_bin\MT6755_Android_scatter.txt" and then choose "Download Mode" then wait for it to finish checking the files, then click on the download button on the top left corner.
Then connect your device and wait for it to detect the device .
Wait until the flashing is complete Then After the green circle appears, simply disconnect your phone and boot into system normally.
Note: You might see a black box in the bottom left corner saying "efuse flash done or similar stuff" don't worry about it" it won't appear again however if you got an error saying "DL image failed" then you did something wrong repeat the previous steps again and make sure you choose everything correct especially your rom.
Now to the last part, finish the first time setup screens by skipping most of them and DO NOT UPDATE YOUR SYSTEM AT ALL
if you got a notification to update, simply ignore it or press cancel, and open google chrome, download king root and wait for it to simply root you phone.
Congratulations that's the first part for rooting your phone.
Now to Fixing Your IMEI
Simply Enable USB debugging in options and enable OEM unlocking.
Then power off your phone.
Download this tool : MauiMETA_v9.1635.23.rar
Yes Again it has to be that specific versions, with other versions i couldn't connect to my device however with this version i could.
Extract it to a random location on your pc and MauiMeta.exe and click on options and enable "enable composite kernel usb (adb)" then click on reconnect.
Now you have to connect your device with usb and turn it on, don't worry MauiMeta will change the boot to META mode automatically after it starts booting leave it as it's and wait for the tool to connect to your phone.
***After it connects simply choose IMEI download and a new window should appear, first click on upload from flash button then click yes to retrieve the modem file from your phone, then simply type your IMEI ( Please note that changing your IMEI is illegal however you should only use this method to fix your IMEI not change it ! , you have been warned)
Note : IMEI numbers should be 15 numbers however with MauiMeta you should only type the first 14 number as the 15th number is only a checksum number and will be added automatically.
After typing the IMEIs and checking them simply click on download to flash.
After it says "flashing is successful" then close the window and click Disconnect, and your phone should turn off automatically and you should start it up again.
*** Note : If you have a corrupted NVRAM file on your phone then you are lucky since that rom comes with the modem db file as well to fix NVRAM issues, simply click "Change NVRAM database file" then click No to choose the file, The file exists in the ROM package you downloaded earlier in the following location : "SW\modemdb\MDDB_InfoCustomApp....etc.EDB" and continue the rest of the steps normally.
Please Note that I won't provide support for this, I have only created this tutorial to save time for other people and I'm not expert yet to fix all the problem you may face however after following these steps i managed to root my device and even fix the invalid imei errors i got.
Also if you found errors in my thread or mistakes Please let me know so i can fix them.
Good luck and Don't hard brick your phone XD
I get this error in SP FLASH TOOL 5.1552.00- STATUS_SEC_PL_VFY_FAIL (-10*****)
Any idea ?
Error coming?
i got the same error in SP FLASH TOOL 5.1552.00- (BROM ERROR : STATUS_SEC_PL_VFY_FAIL (-1073610746))
nishkarshxda said:
i got the same error in SP FLASH TOOL 5.1552.00- (BROM ERROR : STATUS_SEC_PL_VFY_FAIL (-1073610746))
Click to expand...
Click to collapse
Use This Version Of Flash tool enable usb and storage checksum hit download ( Use different usb port better use backside of CPU )
Sp-flash-tool-V5-1548
10000% Working
mobile not getting switched on after downgrading
Hi, I tried to flash my Lenovo vibe K5 note (a7020a48 4 GB RAM). It was done without any error but I couldn't switch on my mobile nor it was detected in my computer. Please help me
Bro i download and flashed successfully but phone cant turn on but i flashed again marshmallow phone will turn on...Why lollipop cant boot... Second link for rom is lollipop or not
Any proof?
Bro where did you get these two rooms from? Tell us the source. Otherwise, how will we know?
after flash mobile no on anybody can u help me to how to flash 5.0 in lenovo k5 note
It worked great thanks .......though minor glitches may occur such as not playing any sound and not supporting JIO sim card. These can be fixed by System Updating your phone to the latest version preferably through a sound wifi connection.
Hi folks,
Today it's a great day for me : I have successfully patched the kernel to have a 100% working TWRP 3.2.1 for our Maze Alpha 4G.
I have port a Jemmini build for Bluboo S1 and I have patch the kernel to have a working touch panel
I have followed this Thead
For the Maze Alpha 6G version, you can test it and tell me please.
How to flash:
I Fastboot method (must unlock device) :
1- Reboot your phone in bootloader mode : adb reboot bootloader or phone off, press and hold at the same time POWER and Vol+ buttons
2- Connect your phone to your computer with adb/fastboot already installed
3- Unlock your bootloader : fastboot oem unlock (it will erase you data, only data)
4- Flash the recovery : fastboot flash recovery recovery_maze_alpha_4G_twrp-321.img
II SPFlashTool method (no need to unlock device) :
1- Download latest version of SPFlashTools.
2- Execute it and load the provided scatter (the recovery image must be in the same folder as the scatter and must be renamed to recovery.img) then press "Dowbload" button
3a- windows SPFlashTools users : phone off, press VOL+ and connect it to your PC (running SPFlashTool and waiting for phone connetion)
3b- linux SPFlashTools users : phone off and connected to PC , press VOL+ and POWER while your PC is running SPFlashTool (with sudo) and waiting for phone connetion.
Update : you can found here the latest version: TWRP 3.3.0 for MAze Alpha 4Ghttps://github.com/dreambo/android_device_maze_alpha/releases/tag/3.3.0
have a nice day.
Works great on Maze alpha 4G. Thanks.
But I forgot to save original recovery...
super_sonic said:
Works great on Maze alpha 4G. Thanks.
But I forgot to save original recovery...
Click to expand...
Click to collapse
You can get the original recovery from the stock rom designed for SPFlashTool, provided here
dreambo said:
You can get the original recovery from the stock rom designed for SPFlashTool, provided here
Click to expand...
Click to collapse
Thanks. Can you share stock recovery.img, if you have it? I have recovery-verified.img from V05 but I don't know if there is a new update and if size is correct: 11,54MB. Your TWRP recovery has got a size of 14.24MB...
Can you make a small procedure on how to install it? Will help many nOOb's out.
And people need to report back issues and successes !!!! Again I see many questions and people with issues that we seniors try to help out with that end up in no more response which to me is not done and not helping others.
I have a 6GB version that I could test on but at the moment I am using it for other stuff and I can't risk bricking it this week.
Would finally love to start some stuff happening on this phone.
Ok in the process of doing so on my 6GB/64GB version.
edit : congratz I now have a 'phone' that can only go into TWRP . Should have never ever done this!
Says no OS installed ... really nice
Edit 2: after hours wasted was able to get your zipped rom on the Maze but I got no boot with that TWRP, so flashed recovery-verified.img from the 6GB rom from Alpha I had downloaded ... It would then start up but show 4GB out of 6GB. No good but at least all the rest seemed to work. All other effort to get it going back with the proper kernel etc resulted in frustration.
So now to flash the official rom back via their tool... that one got me really frustrated and was completely my fault that I couldn't figure it out. But you know angry, frustrated, must get it back to work, can do this ... After all these years of toying with phones we are so used to pressing 'power and vol+ or vol-' together to make something work. Now in the end I re-read the manual again and saw that you only have to push vol+ and NOT vol+ and power together or it wont go in the mode it should go to make it flash!!
In case this happens : The best advice I can give to people is to download the proper MTK drivers. Search for vcom drivers for MTK and you will find.
Print out the instructions and mark every step you do to the letter. The flashing itself only takes like 3 or 4 minutes
lukesan said:
Ok in the process of doing so on my 6GB/64GB version.
edit : congratz I now have a 'phone' that can only go into TWRP . Should have never ever done this!
Says no OS installed ... really nice
Edit 2: after hours wasted was able to get your zipped rom on the Maze but I got no boot with that TWRP, so flashed recovery-verified.img from the 6GB rom from Alpha I had downloaded ... It would then start up but show 4GB out of 6GB. No good but at least all the rest seemed to work. All other effort to get it going back with the proper kernel etc resulted in frustration.
So now to flash the official rom back via their tool... that one got me really frustrated and was completely my fault that I couldn't figure it out. But you know angry, frustrated, must get it back to work, can do this ... After all these years of toying with phones we are so used to pressing 'power and vol+ or vol-' together to make something work. Now in the end I re-read the manual again and saw that you only have to push vol+ and NOT vol+ and power together or it wont go in the mode it should go to make it flash!!
In case this happens : The best advice I can give to people is to download the proper MTK drivers. Search for vcom drivers for MTK and you will find.
Print out the instructions and mark every step you do to the letter. The flashing itself only takes like 3 or 4 minutes
Click to expand...
Click to collapse
Haha I did the same exact thing..and managed to get it working after flashing it with the spflash tool but the trick is if you have Windows 10 latest version you won't be able to do this..at least I couldn't because of driver incompatibility so in my case:
1 I installed Windows 7 and installed mtk drivers for spflash tool
2.booted into twrp
2.1 if you can't boot into twrp or it doesn't turn on you can still try this
3.Start sp flash tool and download the zip the one(in case of trouble)that the moderator published
4. Load the scatter file and make sure that all of the files and the scatter are in the same folder.
5.click download and leave it like that
6.plug in your phone in fastboot if you can't try one of the following
6.1 just plug it in turned off and monitor spflash tool status
6.2 plug it in holding volume up key (just volume not power)
6.3 in twrp go to boot and boot into bootloader
And the tool should do the rest
If all else fails check the drivers one more time
After all that if you are feeling adventurous flash twrp one more time and do not factory reset through twrp ! Because that was the problem in my case and after you unlock bootloader boot your phone and go through the setup without setting the password because twrp will be locked.
Good luck.
frumac96 said:
Haha I did the same exact thing..and managed to get it working after flashing it with the spflash tool but the trick is if you have Windows 10 latest version you won't be able to do this..at least I couldn't because of driver incompatibility so in my case:
1 I installed Windows 7 and installed mtk drivers for spflash tool
2.booted into twrp
2.1 if you can't boot into twrp or it doesn't turn on you can still try this
3.Start sp flash tool and download the zip the one(in case of trouble)that the moderator published
4. Load the scatter file and make sure that all of the files and the scatter are in the same folder.
5.click download and leave it like that
6.plug in your phone in fastboot if you can't try one of the following
6.1 just plug it in turned off and monitor spflash tool status
6.2 plug it in holding volume up key (just volume not power)
6.3 in twrp go to boot and boot into bootloader
And the tool should do the rest
If all else fails check the drivers one more time
After all that if you are feeling adventurous flash twrp one more time and do not factory reset through twrp ! Because that was the problem in my case and after you unlock bootloader boot your phone and go through the setup without setting the password because twrp will be locked.
Good luck.
Click to expand...
Click to collapse
Wait a sec., missing a couple of things here.
1) Do you have a 6GB ?
2) In case you have a 6GB did you manage to get it working, rooted and all?
Your point 6) well I flashed mine on the latest 64bit win10 ... but.... if the phone is off and you connect the usb cable my phone tried to boot up either in twrp with no com port. Also booting it in bootloader doesn't make the comport visible so you can't flash.
The only way to make mine visible for the flashtool was to press vol+ and then connect the usb cable.
Btw I am glad someone finally responds and spreads information. A very good post! Your first 'thanks' well deserved!
I wonder where the guys are that I was trying to help. Did they throw their phones away or something? Sharing is caring I thought.
I want to root mine to alter the camera settings and the media xml file. I find it strange that our sensor, which is the same as in my wife's Xiaomi's, takes seriously bad pictures.
lukesan said:
Wait a sec., missing a couple of things here.
1) Do you have a 6GB ?
2) In case you have a 6GB did you manage to get it working, rooted and all?
Your point 6) well I flashed mine on the latest 64bit win10 ... but.... if the phone is off and you connect the usb cable my phone tried to boot up either in twrp with no com port. Also booting it in bootloader doesn't make the comport visible so you can't flash.
The only way to make mine visible for the flashtool was to press vol+ and then connect the usb cable.
Btw I am glad someone finally responds and spreads information. A very good post! Your first 'thanks' well deserved!
I wonder where the guys are that I was trying to help. Did they throw their phones away or something? Sharing is caring I thought.
I want to root mine to alter the camera settings and the media xml file. I find it strange that our sensor, which is the same as in my wife's Xiaomi's, takes seriously bad pictures.
Click to expand...
Click to collapse
Sorry forgot to mention I have a 4 GB version but since maze is not providing the roms on their website any further development will be limited..thank God for dreambo he is the only guy doing any work here and like you said nobody is responding to any questions asked..shame really because maze is a great phone with a terrible camera..which drivers did you use on Windows 10? because I tried a hundred of them and non of them recognize my phone..and in adb I can run the command fastboot reboot bootloader but after reboot none of the commands are working .
And yes I did manage to install twrp and root using magisk and I to hope that all those other guys didn't brick their phones
frumac96 said:
Sorry forgot to mention I have a 4 GB version but since maze is not providing the roms on their website any further development will be limited..thank God for dreambo he is the only guy doing any work here and like you said nobody is responding to any questions asked..shame really because maze is a great phone with a terrible camera..which drivers did you use on Windows 10? because I tried a hundred of them and non of them recognize my phone..and in adb I can run the command fastboot reboot bootloader but after reboot none of the commands are working .
And yes I did manage to install twrp and root using magisk and I to hope that all those other guys didn't brick their phones
Click to expand...
Click to collapse
This is the filename I used on Windows 10 VCOM Drivers (All MTK Devices & All Windows OS version).zip I think I downloaded it from XDA somewhere.
Also something you must know https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
Another thing I experienced is that one USB connector is not the other one on a pc. Always connect it to the ones directly on the main board next to the other device outputs like audio etc. and preferably not go through ones that have been extended via a cable like the ones on top of the casing or so. Also a must have application is usbdeview.
Well should be easy to get it going if you can boot it into 'fastboot' then you can try as much as you want to. But djeeeeezzzz the letters are very small when you boot it with a power+volume up . Also check that volume up will toggle between 'fastboot', 'recovery' and 'normal start' and volume minus will select it, not the power button which would be more logical to me.
I might have another go at trying to get it working on my 6GB but it involves having a lot of time and knowing that I will get frustrated. Installing all apps and settings is also a time consuming thing. Once you have TWRP on it it all becomes easy to backup. So many things to test or try.
Maybe dreambo has an idea on how to get mine up to a 6GB one as it is probably only indicated in the kernel.
Anyway I will continue to write down my progress.
Ok more frustration. Done multiple things to try to get this running. It's good to know that the original rom is easy to install again after practice.
Take 1: Try to install clean 6GB rom and immediately install TWRP.
Results: Dreambo forgot 1 step and that is to allow OEM unlock in the developer options. If you do the adb command to unlock press volume up and it will unlock (very hard to see, very small letters on the display in bootloader mode)
Well TWRP starts but immediately I get a message 'mount decrypt data password' which I tried a couple of things but no go. Also googled... different solutions but always ending in a bootloop to TWRP
A possible solution that I read was to create a startup pin .... no go 'pin not valid'
Take 2: Take all the rom files and change the scatter file with the one dreambo provided.... Thought it was successful but ended up with the same Chinese recovery. Trying to figure out why since the filename was correct like indicated in the scatter file. Came to the conclusion that the original file was/is called recovery-verified.img and not recovery.img. Really really strange this one as in the original scatter file it also points to recovery.img. So this one I will have to investigate. Renaming the TWRP file to recovery-verified.img lead to a error during the initial scan of the flashtool.
So moral of the story is that I am back on square 1 and lost 2 hours today (plus putting all apps and settings back) today.
I get a bit lost, is this TWRP method only working with the 6GB or also with the 4GB version?
CYberdog11 said:
I get a bit lost, is this TWRP method only working with the 6GB or also with the 4GB version?
Click to expand...
Click to collapse
There is no fundamental difference between 6G and 4G version.
It must works in boat versions.
If you have issues with SPFlashTool try this (no need to install any drivers on Windows 10) :
Put the preloader.bin (found in the rom package designed for SPFlashTool) in the same folder as the recovery.img without checking it the list of partitions (only recovery must be checked) and click on Download to flash the recovery, as usual.
Perhaps SPFlashTool cannot read by himself the preloader in the EMMC, and we must provide it.
The linux version of SPFlashTool not works at this moment, I do not know why
With the SPflashtool I always get the error:
ERROR:STATUS_DA_HASH_MISMATCH (0xC0070004)
HINT
CYberdog11 said:
With the SPflashtool I always get the error:
ERROR:STATUS_DA_HASH_MISMATCH (0xC0070004)
HINT
Click to expand...
Click to collapse
From another thread:
mmakdz said:
google translate
Hello
I had the same problem, (error BROM ERROR: STATUS_DA_HASH_MISMATCH)
what I did: I use Windows 7 System
1- clear all drivers for smartphones with "usbdeview-2-17"
2- install Drivers "Drivers_Auto_Installer_v1.1236.00"
3- install "PdaNetA4170"
4- use "SP_Flash_Tool_v5.1708_Win" to flash the rom. first flash the preloader alone and then flash the others.
the problem was the bad installation of the drivers, after that everything went well for me.
try it can work for you too.
the mentioned software is easy to find on google
Click to expand...
Click to collapse
dreambo said:
There is no fundamental difference between 6G and 4G version.
It must works in boat versions.
If you have issues with SPFlashTool try this (no need to install any drivers on Windows 10) :
Put the preloader.bin (found in the rom package designed for SPFlashTool) in the same folder as the recovery.img without checking it the list of partitions (only recovery must be checked) and click on Download to flash the recovery, as usual.
Perhaps SPFlashTool cannot read by himself the preloader in the EMMC, and we must provide it.
The linux version of SPFlashTool not works at this moment, I do not know why
Click to expand...
Click to collapse
If there is no difference between the 4GB and 6GB then why did I literally spend days on trying this and documenting what happened?
lukesan said:
If there is no difference between the 4GB and 6GB then why did I literally spend days on trying this and documenting what happened?
Click to expand...
Click to collapse
Do you have the 2 versions of the phone and do you have notice any difference of the flashing procedure ?
dreambo said:
Do you have the 2 versions of the phone and do you have notice any difference of the flashing procedure ?
Click to expand...
Click to collapse
I only have the 6GB version of the Maze Alpha. But you wrote that the procedure should work for both versions. I think I wrote down what happened with mine if I installed TWRP.
I tried both the 'regular' flashing and then the full rom install with the trick to put the files in the directory and rename but both ended up as I've written in my previous post.
lukesan said:
I only have the 6GB version of the Maze Alpha. But you wrote that the procedure should work for both versions. I think I wrote down what happened with mine if I installed TWRP.
I tried both the 'regular' flashing and then the full rom install with the trick to put the files in the directory and rename but both ended up as I've written in my previous post.
Click to expand...
Click to collapse
From times to times, I notice trouble with flashing using SPFlashTools.
First (when I post my first post relating of the root) I use the linux version : no issues it works perfect, no need of any drivers!
Actually, no way to have it working on linux, why I do not know!
I have tried Windows 10 and I notice that we have to provide the preloader to have it working, as I write in my post.
In theory, and only in theory, the SPFlashTool must works the same manner in any phone with a Mediatek SOC.
But in reality, we have notice that with exactly the same phone the flashing procedure works for some users and not for others!
SPFlashTool is a very capricious software, there is no warranty to have it 100% working in any platform, even with the same OS.
dreambo said:
From times to times, I notice trouble with flashing using SPFlashTools.
First (when I post my first post relating of the root) I use the linux version : no issues it works perfect, no need of any drivers!
Actually, no way to have it working on linux, why I do not know!
I have tried Windows 10 and I notice that we have to provide the preloader to have it working, as I write in my post.
In theory, and only in theory, the SPFlashTool must works the same manner in any phone with a Mediatek SOC.
But in reality, we have notice that with exactly the same phone the flashing procedure works for some users and not for others!
SPFlashTool is a very capricious software, there is no warranty to have it 100% working in any platform, even with the same OS.
Click to expand...
Click to collapse
The thing is that I have no issue with flashing the software as I can perfectly flash the original rom. The problem is that when flashing the TWRP file, in both options by the way, so also via method 1, I get a boot loop.