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...
[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
The definite guide to rooting Samsung Galaxy J3(2016) SM-J320FN & FRP Locked Bootloop
As first I have to say, I had to create a thread in Q&A because of the low rank, but I am sure this can be moved to the J3 section as there are many questions on how to gain root access to this device. This guide can work on the SM-J320F model as well, but it hasn't been tested on other models, so don't try it !
Lets start :
Dont forget to Backup all your data before the process !!!
1. Tick USB Debugging and OEM Unlock in Developer Mode (OEM has to be ticked to unlock the bootloader)
2. Connect to PC with USB Cable and open Odin
3. Power off and reboot into Download Mode (VOL.DOWN+HOME+POWER)
4. Add twrp.zip to AP tab
5. Untick Auto-Reboot and Start
6. Wait to finish
7. When it's finished hold (VOL.DOWN+VOL.UP+HOME+POWER) to Power Off
8. Load into TWRP Mode (VOL.UP+HOME+POWER)
9. In TWRP first go to the Wipe Tab, check Cache and Data and click Wipe
10. Copy SuperSU into internal memory from your PC
11. Go back to TWRP and select Install, select the SuperSU from the internal memory and click install without ticking anything, then reboot
12. Wait for the phone to reboot, it may boot-loop a few times, and it boots slowly but dont interrupt the process !
13. From there on, check the root status by downloading Root Checker from PlayStore
KEEP OEM-UNLOCK ON ALL THE TIME, IF YOU DONT WANNA END UP WITH A BRICKED DEVICE(CUSTOM BINARY WAS BLOCKED BY FRP LOCK)!!!
If that happens, here is an official guide from the Samsung Kies Support Page :
IMPORTANT: You may need your device model name, S/N number, or IMEI number in order to proceed. This information can be found on the label underneath your device battery.
WARNING: This process permanently deletes all personal information from the device. The information will not be recoverable if you proceed with this process.
1. Open Kies 3 and click Tools > Firmware Upgrade and Initialization.
2. Enter your device Model name and click OK.
3. Enter the device S / N number and click OK.
4. Kies 3 will verify that the feature is available for your device. If the feature is available, click OK to continue.
5. The firmware version is displayed along with a note that the information on your device will be permanently deleted during this process. Click OK to continue.
6. Follow the steps to prepare your device for emergency recovery. Mark the checkbox next to I have read all of the above information. Select whether you agree to share this update with Samsung. Connect your device to Kies when you have activated the download mode. When your device is in download mode and connected to Kies 3, the Start upgrade button is available. Click Start upgrade to reinstall the firmware.
7. Touch Create backup to create a copy of selected items before proceeding. Touch Skip backup to proceed without backing up any items.
8. Kies 3 will download and prepare your system to update the firmware. This process can take some time. The time will vary based on your network and computer capabilities.
9. Respond to any security warnings about installing software.
10. The progress screen is shown during the upgrade process. The process will take several minutes to complete. Do not disconnect your device, turn the device off, or turn off your computer during this process.
11. Click OK when the upgrade is finished.
Therefore I provide you all the needed files to do this :
How to root SM-J320FN.rar
Works like a charm on J320FN.
I signed up just to say, after hours of trying different guides, accidentally factory resetting once or twice, and getting my phone stuck in a boot loop, this method worked. BUT it did factory reset my phone, but that's fine I've everything backed up and it wont take long to get it back. Maybe I pressed something I shouldn't have.
Some info on my phone in case it helps anyone in a similar position to how I was:
At one point I installed stock firmware from to get my phone out of the boot loop, I can't link it but if you google "J320FNXXU0APB4_J320FNO2C0APC1_O2C" (WITH quotes) you should find the page.
After doing that:
Android version: 5.1.1
Model number: SM-J320FN
Kernel version: 3.10.65-7225942 (Sun Feb 14 2016)
Build no: LMY47V.J320FNXXU0APB4
Baseband version: J320FNXXU0APB5
I hope I typed all that right. Thank you so much!!
have anyone tried on j320v?
kekambas18 said:
have anyone tried on j320v?
Click to expand...
Click to collapse
Going to attempt that right now wish me luck.
---------- Post added at 08:06 PM ---------- Previous post was at 07:09 PM ----------
And it didn't work. Not suprised, but I at least tried.
GN9166 said:
4. Add twrp.zip to AP tab
10. Copy SuperSU into internal memory from your PC
Click to expand...
Click to collapse
Hey, why this guide doesn't mention that I have to download something. It's definitely NOT definitive! What is twrp.zip? Where do I take it from? What is AP tab? Where exactly do I copy SuperSU? What will happen in the download mode?
Problems in Root J320AZ
My name is Dario Lobos. I am working as a gardener and I am making a little application in my phone. I don't have computer so I did it in Java n-ide. I started with a Samsung core prime but the screen was broken and I did change it and the technicians broke it and gave me an Samsung s320. Android 6 (api23) and after that the java n-ide don't compiles the permits that I am requesting in the manifest so I can't grant permissions to my apk. Parallel of it the phone always show a notice unauthorized actions have been made please restart the phone to undo the unauthorized actions. And the lookout said message root access detected. I wrote Samsung without any positive answer. No technical assistance at all. But the roots checkers says that I have no root in my phone. Now I am trying to do a root. But I don't know if someone have a hidden root access in my phone. A page suggest Framaroot and you suggest kingroot. I don't want to store all my phone in their server to root it. Does any program that don't access to all the data to root the phone?. I am writing you since you have more experience to request you if it is in your possibilities. Also to ask you about prompt root commands. Where I can find info about that. A suggestion to solve my problem. My simple all is here
....github.com/DarioLobos/sistemariego
....github.com/tranleduy2000/javaide/issues/163
....1drv.ms/u/s!Asr3Ewn45KOLtGOqDkoMq20A-hbc?e=24Wwx3
The system don't let me put url since I am new add please http...
Well thank you in advance and any help is wellcome
Regards,
Dario Lobos
Adding more information to what I did to try to find a an answer. I tried to root with Frama root 1.9.3 and the installation only request me access to the camera and after installed the programs showed a banner that said can't root your device.
Today I downloaded from firmware.mobi some zip and img files but I already I couldn't learn how to use them properly.
I am trying to avoid the exploids system because maybe is a hacker in the middle. Always I am trying to root w/o SIM card and with Wi-Fi off. So I think that kingroot and kingoroot are not useful for my.
I am trying to buy an old desktop computer as an alternative.
Well any suggestion is usefull and wellcome.
Before of all of that I did two factory reset in recovery mode.
Then I installed an apk Dev Tools (trinea) and one menu request me developer permit in accesibility setting. The phone started to change the color of the screen and the outside padding start to flashing red. Then was open a setting menu and the language was changed suddenly to Japanese or Korean while the screen was lighting like receiving knoks. I turned of the phone and restarted and hopefully I remembered the position in settings to change the language.
After that I had to use an apk repair system and fix Android and the screen get better but the padding outside still flashing in red ones in a while.
Also where added plenty sha certificates (settings user certificates) like system certificates
Go daddy
VeriSign
Some governments (Turkish, Spain, Japan, Germany, Holland, and more)
The Catholic religion with 6 certificates called
Quo Basis
And much more.
So I did another factory reset recovery mode. And the screen problem disappeared and the certificates that I turned off manually firt too (All) but the root alert in the look out and the security notice didn't disappeared.
Today I wanted to print your forum page and the phone put error. Only put error in your forum page.
Other thing that I had to to just after the unpackage the restored Android is disable the setup and transfer. Because I think that is this apk that were using to access and modify my files and grants permissions.
I installed the TWRP application but said the phone have no root.
Today I opened the developer option in settings and turned to on the OEM option to unlock the boot loader but instead of put a banner saying that all data will be erased put a banner saying that the device protection will be not work and didn't do the reboot or nothing more that put this dialog.
Dario Lobos
great, unlocken/rooten worked here. But after that, the mobile became unusable. All google apps complain no connection is available. I cannot update google play store, cannot update other google apps like youtube, or install any app now.
And perhaps it does not have anything to do with the mentioned process, but before I started the process, I made sure all nessacary file were on the sd card. But now I have finished wiping the data / cache from the recovery and all files on the sd card are gone.
I cannot login to google photos to see if the apps are backupped because every google app complains no internet connection is available.
So yes, rooting/unlocking worked, but that's the only thing that worked here. I now got a useless Samsung J3 2016...
I need assistant trying to root my J320FN, which I mistakenly wipe some backed up recovery file now, I can not get through with the rooting and I can get back to forma phone setting am locked up , samsung phone not coming up again please what can I do ?
GN9166 said:
The definite guide to rooting Samsung Galaxy J3(2016) SM-J320FN & FRP Locked Bootloop
As first I have to say, I had to create a thread in Q&A because of the low rank, but I am sure this can be moved to the J3 section as there are many questions on how to gain root access to this device. This guide can work on the SM-J320F model as well, but it hasn't been tested on other models, so don't try it !
Lets start :
Dont forget to Backup all your data before the process !!!
1. Tick USB Debugging and OEM Unlock in Developer Mode (OEM has to be ticked to unlock the bootloader)
2. Connect to PC with USB Cable and open Odin
3. Power off and reboot into Download Mode (VOL.DOWN+HOME+POWER)
4. Add twrp.zip to AP tab
5. Untick Auto-Reboot and Start
6. Wait to finish
7. When it's finished hold (VOL.DOWN+VOL.UP+HOME+POWER) to Power Off
8. Load into TWRP Mode (VOL.UP+HOME+POWER)
9. In TWRP first go to the Wipe Tab, check Cache and Data and click Wipe
10. Copy SuperSU into internal memory from your PC
11. Go back to TWRP and select Install, select the SuperSU from the internal memory and click install without ticking anything, then reboot
12. Wait for the phone to reboot, it may boot-loop a few times, and it boots slowly but dont interrupt the process !
13. From there on, check the root status by downloading Root Checker from PlayStore
KEEP OEM-UNLOCK ON ALL THE TIME, IF YOU DONT WANNA END UP WITH A BRICKED DEVICE(CUSTOM BINARY WAS BLOCKED BY FRP LOCK)!!!
If that happens, here is an official guide from the Samsung Kies Support Page :
IMPORTANT: You may need your device model name, S/N number, or IMEI number in order to proceed. This information can be found on the label underneath your device battery.
WARNING: This process permanently deletes all personal information from the device. The information will not be recoverable if you proceed with this process.
1. Open Kies 3 and click Tools > Firmware Upgrade and Initialization.
2. Enter your device Model name and click OK.
3. Enter the device S / N number and click OK.
4. Kies 3 will verify that the feature is available for your device. If the feature is available, click OK to continue.
5. The firmware version is displayed along with a note that the information on your device will be permanently deleted during this process. Click OK to continue.
6. Follow the steps to prepare your device for emergency recovery. Mark the checkbox next to I have read all of the above information. Select whether you agree to share this update with Samsung. Connect your device to Kies when you have activated the download mode. When your device is in download mode and connected to Kies 3, the Start upgrade button is available. Click Start upgrade to reinstall the firmware.
7. Touch Create backup to create a copy of selected items before proceeding. Touch Skip backup to proceed without backing up any items.
8. Kies 3 will download and prepare your system to update the firmware. This process can take some time. The time will vary based on your network and computer capabilities.
9. Respond to any security warnings about installing software.
10. The progress screen is shown during the upgrade process. The process will take several minutes to complete. Do not disconnect your device, turn the device off, or turn off your computer during this process.
11. Click OK when the upgrade is finished.
Therefore I provide you all the needed files to do this :
How to root SM-J320FN.rar
Click to expand...
Click to collapse
The link says "the key is invalid"
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.
Hi, I'm new to the forums.
Back to July 2020, I tried to install custom ROM for my Redmi Cactus and it has no problem until I wipe the data from TWRP and install the custom ROM but failed, I couldn't remember why. And now the phone is dead, it won't boot, no vibration what so ever, when I charge it the LED turns on but when I plug it to PC it won't detect the phone, no sound and nothing in Device Manager even though I have the MTK driver installed on my PC. I've read this thread and couldn't understand the first step as it says "Open REV4 Bypass tool, off your phone. Click BYPASS Connect phone to PC and Turn ON your phone." but I can't turn on my phone. Also on Step 2 which is the SP Flash Tool thing, it says "Open SPFLASHTOOL choose in Download-Agent No_Auth.bin" but on my SP Flash Tool archive I can't find No_Auth.bin, is it somewhere from third-party or from the firmware itself? Currently I'm downloading the firmware and will try to flash it using SP Flash Tool to see if it works. Any help with this?
Best Regards,
Rev.
bioib said:
Hi, I'm new to the forums.
Back to July 2020, I tried to install custom ROM for my Redmi Cactus and it has no problem until I wipe the data from TWRP and install the custom ROM but failed, I couldn't remember why. And now the phone is dead, it won't boot, no vibration what so ever, when I charge it the LED turns on but when I plug it to PC it won't detect the phone, no sound and nothing in Device Manager even though I have the MTK driver installed on my PC. I've read this thread and couldn't understand the first step as it says "Open REV4 Bypass tool, off your phone. Click BYPASS Connect phone to PC and Turn ON your phone." but I can't turn on my phone. Also on Step 2 which is the SP Flash Tool thing, it says "Open SPFLASHTOOL choose in Download-Agent No_Auth.bin" but on my SP Flash Tool archive I can't find No_Auth.bin, is it somewhere from third-party or from the firmware itself? Currently I'm downloading the firmware and will try to flash it using SP Flash Tool to see if it works. Any help with this?
Best Regards,
Rev.
Click to expand...
Click to collapse
Follow this https://www.droidwin.com/unbrick-realme-6-6i-6s-sp-flash-tool/, of course, skip to download and flash the files that are for the other model, instead, replace from your phone's files.
The whole idea, is that you have to install the LibUSB drivers, so your device get recognized and can bypass the DA/SLAA restrictions for BROM mode, in MediaTek devices. When you can bypass it, then you can flash the proper firmware for your device, you don't need to power on your device for that, as your device is bricked...
Hi, sorry it took me so long to reply, the phone is finally fixed thanks to your guide! How can I make this thread or your post as a solution?
bioib said:
Hi, sorry it took me so long to reply, the phone is finally fixed thanks to your guide! How can I make this thread or your post as a solution?
Click to expand...
Click to collapse
Good to know that. Feel free to post any you consider useful for any user.
if you want to mark this thread, you should edit the tittle, in the thread, adding the word (Solved)