Related
Hello guys I got a x920 and was working good until it started doing something similar like Samsung Galaxy S3 Sudden Death.
The phone would randomly get a screen freeze, and the half bottom of the screen got distorted like green and pink lines, then slowly, the pixels were turning to black until the whole screen gets black, but the backlight would remain on.
I had to pull the battery out, and sometimes the phone would work again instantly, some other times, it wouldn't turn on, only after some time, and after a lot of battery pulls.
But last time I got this sudden death, the phone never came back.
I had the stock rom and only root.
My model version is: e2001v21_v89_zlh_hd
Most people with this phone have the e2001_v89_zlh_hd, and most roms on needrom.com are for e2001_v89_zlh_hd, there are a lot of roms for e2001v21_v89_zlh_hd though but I tried everything and I got DRAM Failed.
I use windows 8
SP flash tool v3.1304.0.119, v3.1308.0.125, v3.1316.0.150
And several other roms for both versions.
There is a solution from a French guy about the DRAM failed problem here, but I got the S5 rom downloaded as he stated, and can't get pass the first red bar on SP flash tool.
Do you have any idea what is going on with the 2 versions of the phone? People say that they read on chinese forum that v2.1 (e2001v21_v89_zlh_hd) has got different EMMC. So I guess roms from the e2001_v89_zlh_hd wont work.
I would like to know if you guys have any working rom for my e2001v21_v89_zlh_hd because I really need the phone at the moment. I must get it back to life.
ps (Is windows 8 suitable for flashing? I have installed mtk drviers normally through a weird process enabling manual driver installation through the advanced startup thingy on Windows 8, otherwise it wouldn't let me install the drivers.)
Voliminal_8 said:
Hello guys I got a x920 and was working good until it started doing something similar like Samsung Galaxy S3 Sudden Death.
ps (Is windows 8 suitable for flashing? I have installed mtk drviers normally through a weird process enabling manual driver installation through the advanced startup thingy on Windows 8, otherwise it wouldn't let me install the drivers.)
Click to expand...
Click to collapse
ok, there is no difference for using window 8 , xp, win 7, as long as u have installed the driver correctly.
as u said u can see the red bar, that mean yr driver was installed correctly.
all u need is the right preloader.bin
as i can understand from my past experiance, i think that the later batch of the phone, the manufacturer might use different DRAM or they might have changed the coding of the ram. that is why we see quite often there is complaint of DRAM fail when u try to flash the official rom for the phone. Not for newer model of the phone ( yr phone has two/three batches).
so may be u could ask the http://www.needrom.com/mobile/star-tengda-x920/ - smartdigi to create a preloader.bin from their phone for u , then u replace the preloader.bin in yr rom and flash it.
smartdigi is a team from Greece, and so am I, so yes, I just sent a message.
I hope I'll find a solution.
Voliminal_8 said:
smartdigi is a team from Greece, and so am I, so yes, I just sent a message.
I hope I'll find a solution.
Click to expand...
Click to collapse
i had read tru the needrom wed regarding thier rom, i saw there is a instruction to pass tru the "DRAM fail."
had u tried that before.
they also had rom that match with yr version.
Yes, I downloaded the rom, and still got DRAM failed.
Is there any way to install smartdigi rom through sp flash tool and not sd card?
here's the link http://www.needrom.com/mobile/star-tengda-x920
Yes, I downloaded the rom, and still got DRAM failed.
Is there any way to install smartdigi rom through sp flash tool and not sd card?
here's the link http://www.needrom.com/mobile/star-tengda-x920
Voliminal_8 said:
Yes, I downloaded the rom, and still got DRAM failed.
Is there any way to install smartdigi rom through sp flash tool and not sd card?
here's the link http://www.needrom.com/mobile/star-tengda-x920
Click to expand...
Click to collapse
ok, i just want to know if the procedure as they decribe will work, as i cannot test it, as i don.'t have the phone.
did u manage to get the preloder from them.
if u get the preloader from smartdigi , u stilll get the "DRAM fail" , then i think , may be their phone is an older batch,
for me, if u can read back from from the SP flash tool, (version 3.1316, (i justy learn that there is v3.1328 available)), then definitely u can flash yr phone with this preloader.bin
note
since u can't even go to recovery, then there is no way u can flash the rom with card flash rom from smartdigi, the only way to recover yr phone is tru cable flash rom that mean, u have to pass tru the "DRAM fail"
Well, I found the problem, the drivers installed are MTK USB Port, and not Preloader VCOM drivers.
I use windows 8 x64, I restarted with bypassing the signature thing.
The problem is, when I try to manually select the vcom driver, after the installation it shows up as MTK USB Port, and not as a vcom port.
Any solution?
Voliminal_8 said:
Well, I found the problem, the drivers installed are MTK USB Port, and not Preloader VCOM drivers.
I use windows 8 x64, I restarted with bypassing the signature thing.
The problem is, when I try to manually select the vcom driver, after the installation it shows up as MTK USB Port, and not as a vcom port.
Any solution?
Click to expand...
Click to collapse
no, it does not matter if it is preloader port or vcom port, actually they don,t make difference if u flash the rom.
that mean yr computer is talking to the phone correctly.
now the most important part is the "preloader.bin" file in yr rom must match the dram in yr phone.
that is why u hve to ask who has yr exactly same model of yr phone to create a preloader.bin.
or just try to download the preloader.bin as many as u can.
if u have a friend who has the phone same as as yours, then i can help to create from his phone, or u can create the preloader.bin from his phone
edit,
try to download the latest sp flas tool v3.1324 or v3.1328 ,flash the rom with it.
I tried several roms, with different preloader.bin files, non seems to work.
I tried with all sp flash tool versions, all 3.13904.0.119, 3.1308.0.125, 3.1316.0.150, 3.1328.0.183
Some versions of SP, are not showing up all the files gathered from the scatter file. Some other do.
Well, a smartdigi member, told me to use windows 7, because the mediatek drivers have gone as fas as windows 7 x64.
Voliminal_8 said:
I tried several roms, with different preloader.bin files, non seems to work.
I tried with all sp flash tool versions, all 3.13904.0.119, 3.1308.0.125, 3.1316.0.150, 3.1328.0.183
Some versions of SP, are not showing up all the files gathered from the scatter file. Some other do.
Well, a smartdigi member, told me to use windows 7, because the mediatek drivers have gone as fas as windows 7 x64.
Click to expand...
Click to collapse
ya, u could try with win7.
for me i can flash with win8 also.
i use win 7 at home, win8 at office, no problem.
u could try with win7, i think most likely , u will get the same result.
i had brick my s7589, i unbrick it with the right preloader. after that i tried with the preloader.bin that was originally came with the rom.
this time , it can pass tru the "dram fail", get the purple color, then yellow, then finish with green color. then i try to swith on the phone, but, no response from the phoe. it was bricked again.
then i flash back with the right preloader.bin, the phone back to life again.
did u manage to get preloader.bin from smartdigi?
for me, it is the best solution to unbrick the phone. may be there is some other ways that i don't know
stevenma61 said:
ya, u could try with win7.
for me i can flash with win8 also.
i use win 7 at home, win8 at office, no problem.
u could try with win7, i think most likely , u will get the same result.
i had brick my s7589, i unbrick it with the right preloader. after that i tried with the preloader.bin that was originally came with the rom.
this time , it can pass tru the "dram fail", get the purple color, then yellow, then finish with green color. then i try to swith on the phone, but, no response from the phoe. it was bricked again.
then i flash back with the right preloader.bin, the phone back to life again.
did u manage to get preloader.bin from smartdigi?
for me, it is the best solution to unbrick the phone. may be there is some other ways that i don't know
Click to expand...
Click to collapse
Well... installed windows 7 in another partition.
It was like I never did it, exactly the same result. Everything behaved the same.
I don't know... maybe I have crappy mtk drivers, or I'm doing something wrong while installing them.
Let me describe the steps, and if I'm somewhere wrong you can tell me.
Well, after a clean windows 7 install, I connect the phone to the pc (with or without battery,I think I tried both, didn't see something change) it gets to "other devices" as an "unknown device". right click to update driver software, select the folder with vcom drivers.
It gets recognized as a mtk usb port.
Try to flash like that, same results.
Then I go to update driver again, but this time I click "let me pick from a list of device drivers on my computer." I uncheck show compatible hardware, then I choose MTK Preloader USB VCOM Port.
the device now shows up to the device manager as "MTK Preloader USB VCOM Port".
Try to flash, everything is the same...
I read somewhere, that the normal installation of vcom drivers is kinda different, that it get's shown up as "MTK Preloader USB VCOM Port" right away, and I read that when you install the vcom driver correctly, it connect and disconnects the device every 3 seconds.
Well.. I didn't manage to get the preloader.bin yet, I'll ask for it, but why the official rom on needrom.com preloader.bin is not working with my phone? And why would smatdigi preloader.bin would work for me?
I tried roms that are for e2001v21_v89_zlh_hd but even their preloader wouldn't work for me.
first of all, stop playing with those preloaders. random flashing will brick your motherboard of your computer too, if you flash a wrong BIOS file. clear? okay. the DRAM error occurs if the Rom is mismatching the "signature" of your device. so, before trying to flash it, take another one, in this case, the right one. ( for example: my device (n9770) got few cameras, few board revisions, ddr or ddr2 Ram and so on, only one Rom or a mix of different files will work)so flashing a wrong firmware causes more "damage" or "errors". have you backed up your firmware before rooting?
you need to find a full backup of your device ( most likely a Rom directly from your vendor) including ALL needed partitions for flashtool. ROM's of new devices are hard to find, even for n9770 (mt6577) there are ROM versions from 06-2012 till now. so, if you got a "newer" device, you need to get the correct firmware and flashtool should flash without problems. also, your drivers are working perfectly, otherwise flashtool won't show the red bar wich is checking the device.you may need to check if the "second" driver is installed correctly, because the device will switch from preloader mode to "flash mode". maybe the driver for the preloader is installed correctly, but it can't switch to flash mode.
Chrizzly92 said:
first of all, stop playing with those preloaders. random flashing will brick your motherboard of your computer too, if you flash a wrong BIOS file. clear?
Click to expand...
Click to collapse
Clear bro, but I never really managed to do a flash. Just never. I only get dram failed.
Chrizzly92 said:
okay. the DRAM error occurs if the Rom is mismatching the "signature" of your device. so, before trying to flash it, take another one, in this case, the right one. ( for example: my device (n9770) got few cameras, few board revisions, ddr or ddr2 Ram and so on, only one Rom or a mix of different files will work)so flashing a wrong firmware causes more "damage" or "errors". have you backed up your firmware before rooting?
Click to expand...
Click to collapse
I don't think I did any more harm, since nothing really fot flashed.
Not I don't have a backup :/
Chrizzly92 said:
you need to find a full backup of your device ( most likely a Rom directly from your vendor) including ALL needed partitions for flashtool.
Click to expand...
Click to collapse
I bought it from focalprice, even if they send me any rom, it will be one of the officials found in needrom.com ... So I don't think they'll handle it.
Chrizzly92 said:
also, your drivers are working perfectly, otherwise flashtool won't show the red bar wich is checking the device.you may need to check if the "second" driver is installed correctly, because the device will switch from preloader mode to "flash mode". maybe the driver for the preloader is installed correctly, but it can't switch to flash mode.
Click to expand...
Click to collapse
How can I check that the second drivers is installed correctly?
just open your device manager and check, if the device gets recognized correctly. start a flash and check, if there are any devices gets loaded while trying to flash. if so, install the correct driver. there are some issues with that sometimes.
if this won't work, try using MTD tool. flasing through there should work always, but it got some issues with vcom drivers. you need to assign every vcom port to the mtk device. explaining of this is retty hard since english isn't my motherlanguage, so its best to check google or xda for that.
also, can you start your device into recovery, or is it really "dead"? no bootlogo, nothing?
No the device is hard bricked, no recovery at all. Not anything. :/
I can't use MtkDroidTool, it doesn't detect my device.
hmn, i would suggest its a hardware failure. never saw a device "dying" without flashing before.
btw: i meant SPMultiPortFlashDownloadProject tool, this is a more advanced variant of sp flash tool. just google for it and put a log in here, so i (we) can check whats the matter.
Chrizzly92 said:
hmn, i would suggest its a hardware failure. never saw a device "dying" without flashing before.
btw: i meant SPMultiPortFlashDownloadProject tool, this is a more advanced variant of sp flash tool. just google for it and put a log in here, so i (we) can check whats the matter.
Click to expand...
Click to collapse
I already have this tool and used it with the same results.
Which log do you need? It has 3 but 2 of them are really long, cant fit them in one post.
Voliminal_8 said:
I already have this tool and used it with the same results.
Which log do you need? It has 3 but 2 of them are really long, cant fit them in one post.
Click to expand...
Click to collapse
did u manage to get the preloader from smartdxxx............. ???????
it just takes 5 minutes (the most) to create the preloader from the phone.
take up the battery from the phone, run sp flash tool, connect the phone to computer, 5 sec, the rom_0 is read
put back battery, on the phone, connect the phone to computer, run mtk droik tool, 30 secs later, the preloader is created.
china phones
stevenma61 said:
did u manage to get the preloader from smartdxxx............. ???????
it just takes 5 minutes (the most) to create the preloader from the phone.
take up the battery from the phone, run sp flash tool, connect the phone to computer, 5 sec, the rom_0 is read
put back battery, on the phone, connect the phone to computer, run mtk droik tool, 30 secs later, the preloader is created.
Click to expand...
Click to collapse
been to a lot off repair phones shop and all stead screen x920 done buy a SquareTrade 2 yr warranty £30.99 ins on phones
[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
Apparently sometimes it's not the best idea to use the flashing software that the manufacturer of your phone released.
I have a Wiko Lenny(technically a MediaTek MT6572) that has(or had - now it's dead) the habit of simply rebooting into a bootloop every few months. Fixing that was simple; just start SP Flash Tool, format everything then flash the stock ROM back. Last time I did that was around 4 months ago, and since then I have upgraded to Windows 10, and as such, lost the tools I had installed.
Yesterday it went into a bootloop again. I didn't remember exactly what tools I used, so I assumed they were the tools that Wiko supplied a while back with the V10 ROM. Well, they weren't. I still thought I'd give them a try. I mean, it's from the manufacturer's site, so they must work even better that the ones I was using.
I was wrong. The tool flashed the ROM "successfully", but the only thing it actually succeeded to do is corrupt the preloader. For those who don't know, corrupting the preloader basically means the phone won't even power on(not boot, actually power on), won't charge, and the PC won't detect anything if you connect the phone. Practically, it's the hardest brick a phone can get.
The fastest way to fix that is by either using a JTAG connection to flash everything manually, or by entering something called the Mediatek META mode(don't quote me on this one, though - I never heard of it before). JTAG - well I don't have the tools or expertise necessary to do that(although I'd love to learn how to do it - if anyone can point me to a well-written guide or two about that, please do!), and I simply can't get the phone to enter the META mode.
Is JTAG the only way to do it? Is META mode just a myth? Is there a way to save my phone, or should I just say "RIP" and buy a new one(I have the money for a Samsung Galaxy A3, the new one, but I was planning to buy a new computer with that money - is it worth it?)?
TL;DR (It's not that long but anyway...):
I have a Wiko Lenny(Mediatek MT6572) with a corrupted preloader after I flashed it with Wiko's tool. Can I repair it or should I just buy a new phone?
Link to the culprit that killed my phone(AKA Wiko V10 ROM): https://docs.google.com/uc?id=0BzeAvoIC2yhHMTZESUU1Y3hUM0E
Come on people, let's fix this little guy.
EDIT: Please, just tell me what your ideas are... A tip, a crazy idea, some details about MTK devices that could help, anything is appreciated.
Please...
Looks like I'm getting the 10 posts just by begging people to say something... :crying:
I have an MTK phone and its always going wrong and not booting/turning on because I mess with it and break it
I'm sure I flash the backup I made in mtktools with spflash, and plug the phone in with no battery attached, I also have to use windows 7 on a dual boot as windows 10 never played ball properly. You also need the mtk VCOM driver installed, not just adb and normal drivers. If you have all these, and have tried them, then that is the end of my knowledge sadly. Only other thing is going to needrom and seeing if they have a full rom/backup with partition tables/preloader etc.
Also, had to try a few versions of sptools as certain versions didnt work, forget which one I have and which didnt work. And also had to use a samsung USB lead as the stock one didnt work, or the other way round. I just remember it was a ball-ache but did eventually work. Am not on that pc so cant be more helpful, sorry....
robneymcplum said:
I have an MTK phone and its always going wrong and not booting/turning on because I mess with it and break it
I'm sure I flash the backup I made in mtktools with spflash, and plug the phone in with no battery attached, I also have to use windows 7 on a dual boot as windows 10 never played ball properly. You also need the mtk VCOM driver installed, not just adb and normal drivers. If you have all these, and have tried them, then that is the end of my knowledge sadly. Only other thing is going to needrom and seeing if they have a full rom/backup with partition tables/preloader etc.
Also, had to try a few versions of sptools as certain versions didnt work, forget which one I have and which didnt work. And also had to use a samsung USB lead as the stock one didnt work, or the other way round. I just remember it was a ball-ache but did eventually work. Am not on that pc so cant be more helpful, sorry....
Click to expand...
Click to collapse
Thanks for replying. I'm not sure if I have the VCOM drivers, but I'll check. Luckily I also have a Win7 PC besides this one, so I'll try it there too.
You need to repair preloader. Contact me !
gsm-decode said:
You need to repair preloader. Contact me !
Click to expand...
Click to collapse
Please do a nice thing, and tell me how to repair it here. Maybe there will be people in the exact same situation...
Can't fix MIne too !
DragonSky87 said:
Please do a nice thing, and tell me how to repair it here. Maybe there will be people in the exact same situation...
Click to expand...
Click to collapse
I also got an android phone that is INTEX AQUA I5 hd , i was flashing my phone and unfortunatly my pc got off while flashing . And my preloader got currepted .
When i tries to flash my phone it connects to pc as Mediatek Viacom port , but after 3-4 sec it connects as a usb port .
I continuously gots connceted and dissconnected .
and my Sp flash tool shoes error " S_DA_SDMMC_READ_FAILED(3153) "
Can anybody help me with it ? please help me as soon as possible.
You need to flash preloader by Testpoint,after that flash rom.
Dont remember exactly the testpoint but you can try
DragonSky87 said:
Apparently sometimes it's not the best idea to use the flashing software that the manufacturer of your phone released.
I have a Wiko Lenny(technically a MediaTek MT6572) that has(or had - now it's dead) the habit of simply rebooting into a bootloop every few months. Fixing that was simple; just start SP Flash Tool, format everything then flash the stock ROM back. Last time I did that was around 4 months ago, and since then I have upgraded to Windows 10, and as such, lost the tools I had installed.
Yesterday it went into a bootloop again. I didn't remember exactly what tools I used, so I assumed they were the tools that Wiko supplied a while back with the V10 ROM. Well, they weren't. I still thought I'd give them a try. I mean, it's from the manufacturer's site, so they must work even better that the ones I was using.
I was wrong. The tool flashed the ROM "successfully", but the only thing it actually succeeded to do is corrupt the preloader. For those who don't know, corrupting the preloader basically means the phone won't even power on(not boot, actually power on), won't charge, and the PC won't detect anything if you connect the phone. Practically, it's the hardest brick a phone can get.
The fastest way to fix that is by either using a JTAG connection to flash everything manually, or by entering something called the Mediatek META mode(don't quote me on this one, though - I never heard of it before). JTAG - well I don't have the tools or expertise necessary to do that(although I'd love to learn how to do it - if anyone can point me to a well-written guide or two about that, please do!), and I simply can't get the phone to enter the META mode.
Is JTAG the only way to do it? Is META mode just a myth? Is there a way to save my phone, or should I just say "RIP" and buy a new one(I have the money for a Samsung Galaxy A3, the new one, but I was planning to buy a new computer with that money - is it worth it?)?
TL;DR (It's not that long but anyway...):
I have a Wiko Lenny(Mediatek MT6572) with a corrupted preloader after I flashed it with Wiko's tool. Can I repair it or should I just buy a new phone?
Link to the culprit that killed my phone(AKA Wiko V10 ROM): https://docs.google.com/uc?id=0BzeAvoIC2yhHMTZESUU1Y3hUM0E
Click to expand...
Click to collapse
Repair your own device
Soft Brick: Soft brick is the state of android device which occur due to some software problems like boot loops or phone freezing at some point during boot. This only occurs if some software problem occurred in the device mainly during OS upgrade or ROM flashing. If your device is in such state then you are luck there are 99% chances that you can recover your beloved device without needing any professional help or spending hundred of dollars.
Hard Brick Hard brick is the state of android device that occurs when your device won’t boot at all i.e. no boot loop,no recovery and also not charging. This occurs due to trying to flashed firmwere not made for your device or flashed incorrectly. This is more difficult to resolve and often require professional help
in MTK Android there is many Partitions in your phone. like Preloader, Recovery, Bootimg etc….. if somehow Preloader get Corrupted then you phone will not able to DETECT WITH PC !!! in other words you will have phone with BOOT DEAD.
How Preloader get corrupted ?
There could be few reasons but main reason could be that someone or you Flash your complete phone (include Preloader) with wrong files or with wrong ver. Also there could be reason someone Delete Preloader or you Deleted.
How could i know my phone have preloader dead ?
Preloader can be dead if some one Flash it wrong and after flash your mobile will not detect with pc any more. for confirm
1.sp flash tools does not detect your phone anymore and also the computer does not as there is a pop sound when usb is connected to device
2.open device manager
take battery out from phone
insert usb
insert battery
and check is computer detecting any device
If it’s not detect then you have phone which Preloader is dead AKA Boot Dead
How can i repair it ?
requirement
1.screwdriver (by which you can open the screw from handset)
2.bricked device
3.a usb cable
4.a copper wire( for sold test points)
5.a pc with sp flash tool,mtk drivers and stock firmwere for your mobile
now you have to disassemble your phone and take pcb out. check there should be some Golden points. check these points there should be written on them Rx,Tx,GND,Vcc,Vcharge etc… check there should be written “COLO” or “KOLO” or“KCOLO” you have to Sold that point with GND After Sold Attach usb now your phone will detect with USB !! and now ready to Flash.
In some phones “COLO” or “KOLO” or “KCOLO” not written for those type of phones you have to test all points one by one Short Golden point with GND and attach usb cable which point short with gnd can able to detect your phone by pc isForce Preloader Mode Test Point !! Keep in mind Don’t Short Vcc,Vcharge or any other pin which have 4.x Volts also i had tested “Colo” or “Kolo” or “KCOLO” don’t have any kind of volts.
need help
gsm-decode said:
You need to repair preloader. Contact me ![/QUOTE
i have samsung clone A9 MT6580 After reflash phon,e is dead by sptool..i thinkl preloader is damaged..i dont have back up..but ditecting VCOM BUT Always "Sft Enable Dram_Fail (4032)" in format or fullfash in all tools
Click to expand...
Click to collapse
help me i corrupted my pre loader
gsm-decode said:
You need to repair preloader. Contact me !
Click to expand...
Click to collapse
hi sir I try to flash a stock rom downloaded from internet
its a vivo v5 android mobile phone
I tried to flash but I got a few alerts
the selected model does not support model verification
and
if I tried it gives me a brom error
now my phone condition is hard bricked and responding to flash tool
gsm-decode said:
You need to repair preloader. Contact me !
Click to expand...
Click to collapse
HI sir how can I contact you
Hi I also have the same problem - when I flashed the stock rom of my LG K7 X-210 (MT6580__lge__LG-X210__m13g__5.1__ALPS.L1.MP6.V2.19_ARIMA6580.WE.L_P42) with the SP Flash tool when I was in a bootloop, I accidentally forgot to uncheck the preloader option. I flashed it to my phone and from that point onwards it didn't want to start up any more, nor would it react if I tried charging it. So conclusion: the preloader is corrupt...
However, I read online that MTK devices (mine is MT6580) have a 'meta' mode which allows your device to still connect to SP Flash tool even if it is hardbricked (in my case by pressing the volume up button, and then simultaneously plugging it in the computer). It is then recognized as MTK Com port something in device manager.
Luckily I have the same phone (but it's not mine) and I was wondering if it was possible to make a full rom dump from that device and restore it on mine? (a method that is safe for the other device as well)
i have a proble on my new phone since i flash preloader my touch is not working anymore, any solutions ?
gsm-decode said:
You need to repair preloader. Contact me !
Click to expand...
Click to collapse
I need to repair preloader of My Nokia G20.
hello this is very simple.
i solved this problem.
i wrte english very small.
flash atarken yanlış attığın preloader dosyası ile başlat.cihazı bilgisayara bağla.format bittikten hemen sonra doğru preloader dosyasını klasörün içine yapıştır.ama çok hızlı olmalısın.yani uyumsuz preloader dosyası ile cihaza yükleme yaparken tam format esnasında uyumlu olan preloader dosyasını hızlıca yapıştır.
gsm-decode said:
You need to repair preloader. Contact me !
Click to expand...
Click to collapse
Hello, is it too late to write?
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.
this phone use mt6739.so i want to flash it the twrp to my phone.i dunno to unlock the bootloader but the twrp file not have for this device.
I just saw this post as I too have a Honor 7S
There is NO TWRP for our device.
The TWRP for the Honor 7A/7C/7X and Honor 7 doesn't work on our device and you got to pay 4 euros to unlock the bootloader before you can even flash TWRP (and there isn't one)
This Device is treble compatible but now I've found out there is zero development and no Devs Interested in it it's a complete and utter waste of time and has gone back into its box, never to be seen again.
hi there, I get this phone recently (because is old) and I created twrp for i,t so here it is, if you want some fun
you can flash it via flashtool on locked bootloader in to boot partition and after that you push twrp.img via adb to internal storage and flash it in to erecovery and recovery slot, and you are good to go
Samuel Ladziansky said:
hi there, I get this phone recently (because is old) and I created twrp for i,t so here it is, if you want some fun
you can flash it via flashtool on locked bootloader in to boot partition and after that you push twrp.img via adb to internal storage and flash it in to erecovery and recovery slot, and you are good to go
Click to expand...
Click to collapse
Hi I have a problem. I'm having brom issues in trying to flash it
Hi
I thinking you dont have "Authentication file" so you using "mtksecurebootdisabler",
so you need patch your drivers with libusb "patch".
Try this one, for me it works.
So open libusb that you install.
connect your honor7s to the pc with disconnected batery and hold volume down.
in patch option select your usb mtk device "idk how is called" and patch it
after patching reconnect phone and it will works.
usab1oy said:
Hi I have a problem. I'm having brom issues in trying to flash it
Click to expand...
Click to collapse
and little hint
dont flash whole rom if the phone can boot becasue after clean flash "format+download"
you lost log and cust partition because the image files are not secureboot signed and your phone get in to bootloop
and also you lost imei codes so no cellular after that
If you do so
you can fix it in that recovery were I enabled option to format log partition
after you format log to ext4, your phone will boot but without huawei/honor bootanimation
you dont need to worry about cust partition, if you didnt format it it still boot but without bootanimation and you lost some of garbage apps that are in that partition (amazon etc...)
(twrp boots in russian language, idk for now how to change it to boot in english or slovak lanuage (because Im from slovakia) and also it have Lenovo Logo becasuse I use sources from Lenovo A5 that have same cpu)
I will make in future separated thread for this....
Thanks alot for this.. I don't know maybe I should try the disconnected battery. But from a yt link I saw
The link : Honor 7s Dua-Al000
I wonder how his worked
I'll have to know how to disconnect the battery thou. I'm a noob at this.
Samuel Ladziansky said:
Hi
I thinking you dont have "Authentication file" so you using "mtksecurebootdisabler",
so you need patch your drivers with libusb "patch".
Try this one, for me it works.
So open libusb that you install.
connect your honor7s to the pc with disconnected batery and hold volume down.
in patch option select your usb mtk device "idk how is called" and patch it
after patching reconnect phone and it will works.
Click to expand...
Click to collapse
Sorry for the noob question but after patching with the battery disconnected. When I want to use spflash tools would I still use disconnect the battery to flash the recovery and co.
usab1oy said:
Sorry for the noob question but after patching with the battery disconnected. When I want to use spflash tools would I still use disconnect the battery to flash the recovery and co.
Click to expand...
Click to collapse
you can patch it or flash it without disconecting the battery
Here is how:
turn it off
Push and hold volume down
While holding volume down connect usb cable
But is recomended to disconect battery because the phone can boot up instead to go in flash mode.
usab1oy said:
Thanks alot for this.. I don't know maybe I should try the disconnected battery. But from a yt link I saw
The link : Honor 7s Dua-Al000
I wonder how his worked
I'll have to know how to disconnect the battery thou. I'm a noob at this.
Click to expand...
Click to collapse
Well he did with the battery and he add more steps that are not necessary for flashing, like scanning for COM port etc...
When I first try flash my 7s I download flashtool and didn't change any settings, I just load the rom and flash it.
So you must try to find your best way how to do and I will help you
And I wonder how he can flash the Log and Cust partition via flashtool, Maybe he have unlocked bootloader or something
Update: he have in the video description link for "lib usb" but didn't show it in video, or I'm just blind or something
Samuel Ladziansky said:
Well he did with the battery and he add more steps that are not necessary for flashing, like scanning for COM port etc...
When I first try flash my 7s I download flashtool and didn't change any settings, I just load the rom and flash it.
So you must try to find your best way how to do and I will help you
And I wonder how he can flash the Log and Cust partition via flashtool, Maybe he have unlocked bootloader or something
Update: he have in the video description link for "lib usb" but didn't show it in video, or I'm just blind or something
Click to expand...
Click to collapse
Yeah. For the flash mode, I wonder why his own he said I need to hold the volume up and down button at the same time. But thanks I'll do it and let you know.
here is version 3 of twrp recovery port
-fixed language form russia to english
-lenovo banner replaced with original TWRP
Samuel Ladziansky said:
here is version 3 of twrp recovery port
-fixed language form russia to english
-lenovo banner replaced with original TWRP
Click to expand...
Click to collapse
At this point. Might just abandon it. Thanks for everything. Ran into laptop issue on my third trial lol.
Yeah I see, drivers issues, it happens to me too, but I install windows 7 and everything works... but I think is not worth it to format your laptop and install win7 only for this mediatek crap, where you can't unlock bootloader or anything because Huawei trying to protect customers and they believe that their android is best for they're phones
Samuel Ladziansky said:
Yeah I see, drivers issues, it happens to me too, but I install windows 7 and everything works... but I think is not worth it to format your laptop and install win7 only for this mediatek crap, where you can't unlock bootloader or anything because Huawei trying to protect customers and they believe that their android is best for they're phones
Click to expand...
Click to collapse
Honestly. I spend a whole night researching videos for the phone. Only to get that link I send. And after all that. It still didn't work. Lol. I have a Poco x3 pro. I wonder if snapdragon android 12 can be rooted. Probably going to try it next month or so.
Snapdragon is eazy for root.
I have Redmi note 11 and it was easy, now I running on Android 13 from stock android 11, if you will need some help with something, I'm here, and I think there is device forum so there is community for that device