[GUIDE] How to 'unbrick' your Mediatek MT65xx - Android Q&A, Help & Troubleshooting

[GUIDE] How to 'unbrick' your Mediatek MT65xx - Android Q&A, Help & Troubleshooting

i've seen far too many times that fellow xda member make this same mistake over & over again, including myself...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So pls pls people, don't use SP Flash Tool to download ROM not meant for your phone, it will brick it & there is no way to revive it back ! After you have download wrong PRELOADER, your phone will be completely dead, cannot power on, no charging, no recovery, no PreLoader USB vcom detection & you can say
to it...
Here is the WARNING again :
NEVER DOWNLOAD ROM NOT MEANT FOR YOUR PHONE. IT WILL BRICK IT !
----------------------------------------------------------------------
Even with the the WARNING & you still do it...
Inspired by fellow xda member to start this thread to help out other xda member that run in to similar problem so here are the solution but it might not work for all MT65xx... :fingers-crossed:
If you have already brick it by flashing wrong PRELOADER then you still have a 50/ 50 chance to revive it so keep you fingers-crossed... :fingers-crossed:
For MT6573
Requirement : Your MT6573 factory ROM, SP Flash Tool
MT6573 Meta Driver - If you don't have, download it from here
First you will need to open Device Manager, switch off your phone, press & hold Menu button but don't let go, now plug-in your usb cable will activate META mode(Thanks to Master Shifu Cybermaus for his insight knowledge)...You'll notice Mediatek USB VCOM will appear at Device Manager -> Ports
Mediatek USB VCOM will stay connected until you download factory ROM then it will auto disconnect, reconnect as PRELOADER USB VCOM & continue downloading...
After factory ROM download completed, it will be auto disconnected & you'll have your phone raise from the dead ! :laugh:
This hidden feature will enable you to download factory ROM when you brick it by flashing wrong PRELOADER meant for other phone however for some MT6573 there is no way to access META mode except by dismantling the whole phone...
If you can't find your model factory ROM, try to hunt for similar ROM. I have had feedback from fellow xda member it actually works ! Luckily, most MT65xx ROM are very similar to each other. Try to look for similarity at build.prop -> ro.build.product for eg, typical build are bird73_gb , e1109_v73_jy1, huaqin73_gb, tinnoes73_s8030_2g, mt73_w831_a9100_yingt & etc... google search is your friend... :good:
For MT6575/ 77
With the battery out, hold the volume up, don't let go & plug in the USB cable will activate META mode for few seconds...Typically, you need to click Download at SP Flash Tool before entering META mode or it will auto disconnected...
If all doesn't work & you don't have a local service center for your MT65xx then may be you would want to try rua1's method but its not for the ordinary user... :fingers-crossed: Use google chrome for translation...
Attach is few photos that i've downloaded from that forum as it can only be viewed by members at that forum.... :good:
----------------------------------------------------------------------
Added on Nov 23, 2012 - MT65xx is truly UNBRICKABLE
it seems that MT65xx is really 'unbrickable' thanks to whitetigerdk who inform me with his how-tos :good:
So you can raise your DEAD MT65xx back to life...
The trick is quite simple, for whitetigerdk case, he flash his GooPhone Y5 with Zopo100 factory ROM & the phone went DEAD...
He proceed to reinstall preloader driver from Zopo & was able to use FlashTool again and flash back his factory GooPhone ROM & thats how he brought back his MT6575 back to life... :good:
Updates
i've pm'ed whitetigerdk & got a reply from him confirming that indeed his GooPhone Y5 has this META mode built-in (plug in USB while holding VOL +)
Device Manager will detect new device... Having said that, not all MT65xx device has this feature...
----------------------------------------------------------------------
Added on Dec 20, 2012 - DO NOT USE MEMORY TEST AT SPFT !
There has been confirmed cases that fellow xda member brick their MT6575/ 77 by using the MEMORY TEST function at SP Flash Tool !
When you put a check mark at NAND Flash Test or EMMC Test what it does is that it actually FORMAT it & this will brick your device !
For those who are having problem such as 3013 S_DA_SOC_CHECK_FAIL or 8038 SP FLASH TOOL ERROR for MT6575/ 77 even with testpoint, you will need SP_Flash_Tool_v3.1224.0.sn85
I have upload it to here for ease to fellow xda member, Credits to Master Shifu rua1...
----------------------------------------------------------------------
Added on Jan 06, 2013 - DO NOT JUST FLASH ANY ROM WHEN YOU BRICK YOUR DEVICE !
Well known brands like Lenovo, Zopo, ZTE & etc do provide FACTORY ROM at their webpage for download...
However, for those lesser known brand, its hard to say so you will have to hunt for it & do as the title says...
Credits to XDA Senior Member cybermaus, he has put up a simple guide on How to search for replacement rom...
----------------------------------------------------------------------
Added on Feb 11 2013 - Guide for Backing Up your device Factory ROM
This guide here is meant for you to pass to a good Samaritan that will help you unbrick your device, hopefully... :fingers-crossed:
----------------------------------------------------------------------
Added on Feb 20 2013 - Mediatek Driver Auto Installer
Found a Mediatek Driver Auto Installer, download it from here... Will be useful for those having drivers issues...
Works on WinNT, WinXP, Win2003, WinVista, Win7 be it x86 or x64, just double-click Install...
But remember to turn off User Account Control Settings...
----------------------------------------------------------------------
Added on Feb 25, 2013
Operation to Support & Reward our MTK SoC Developers
Head up to here & show your support...
----------------------------------------------------------------------
Added on May 13, 2013 - Reward for a Job Well Done
It is Master Shifu rua1 that discovered MTK devices can be unbrick via testpoint & he has developed a great tool & continuously updating it, the MTK Droid Root & Tools that can backup Factory ROM out of an unknown MTK devices, get hardware information, Root it, port CWM & many many more...
Its sad to see users are taking advantage of all these free infos & tool developed by Master Shifu... Recent check with Master Shifu & he told me he only get 3 donations from xda Come on people...
Please understand the significant amount of time and effort required to understand how the MTK devices works, then developing a software, a new function, bug fixes, add new features, testing it & etc before releasing it as a free tool...
Master Shifu never demanded any payment for using his software & inline with the xda spirit to Gives Credit Where Credit is Due you should start hitting the DONATE button now...
As i have mention in this thread before, when you have unbrick your MTK devices using these infos & tool by Master Shifu, it means you don't have to fork out another USD 200+ to get a new devices... :laugh:
So how about spending Master Shifu breakfast, lunch or dinner that you have manage to save $$$
Pls pls consider making a donation to the Master Shifu rua1 to support him to continue development of this free great tool...
Free software/ tool on xda = you download it, use it & it help you = Hit that DONATE button

Hi.
I've my M Pay Royalty Note 2 bricked, my pc detect as "MTK usb com port" and Preloader don't start to upload again the firmware.
I don't understand if is possible unbrick the phone and how to do this.
The only thing that work with SP Flash Tool is the read-back function.
Please help me.

Normally for most MT65xx, you can't access META mode, to access it on my Lenovo, i have to take out the battery, press & hold volume up(don't let go) & plugin USB cable & the Device Manager will pop-up MTK USB COM for few seconds then disappear...( As the youtube video above ) Only at this MTK USB COM, the factory ROM can be downloaded without PRELOADER, according to Master Shifu cybermaus, thats how they download factory ROM at the first place...
Typically when you have MTK USB COM show up at Device Manager meaning you have factory META mode then you should be able to download your factory ROM with it too... No need to dismantle up your phone & look for testpoints... :laugh: Did you press the Download button at SP Flash Tool first then only plugin USB cable... Or maybe you should try pressing the Volume Up button too while plugging in USB cable... :fingers-crossed:
Did you try reinstall driver as per whitetigerdk trick...
What is the error message you got... If you can upload then you should be able to download with it too... :fingers-crossed:
Good Luck...

27ylliw said:
I've my M Pay Royalty Note 2 bricked, my pc detect as "MTK usb com port" and Preloader don't start to upload again the firmware.
Click to expand...
Click to collapse
I am not as optimistic as Yuweng in that it is 'unbrickable', but if you mean to say that your PC *does* still detect a MTK usb com port, then I would indeed suggest we may be able to salvage the device. But before you try anything else, lets first get a proper idea of where you are, and how you got there:
1) Please describe properly what phone you have. Exact model, brand, where you bought it. Links to it may be useful. Do you remember what ROM it originally came with?
2) Please describe *how* you bricked the device. What did you do, what firmware did you try to load, what steps did you try to take, and how did it fail.
3) Please confirm if indeed you still see the MTK com port when you connect it to PC.
4) If you still see the MTK com port, you say you cannot flash. Please tell us why not. What flash method are you trying, using what ROM, and how is it failing?
In your answers, be descriptive and verbose. Foto's (or better screenshots) should be added if possible. Yes, this means a lot of effort, but if you think we can help you save your phone based on one-liners, you are wrong.
PS: Yuweng: can you please drop the 'master shifu' honorific? I am not any master builder, just hobbyist hacking about. Also I did not see the movie yet. Also, while impolite to ask, could I ask you to take a non-animated signature? Its funny at first, but after a while very distracting.

Bricked phone mtk6577
Hello,
I purchased s3 clone, brand : ALPS, Model - N-93000, MTK 6577, 1.2 ghz dual core, 8 mp camera, 512 ram, android Jelly bean 4.1.0 from alibaba.com
Now my problem is one sim slot working fine and another sim slot "not able to register on network" and not working magnetic sensor. i complain to supplier but he does not want to listen and telling we sent mobile after testing. and last he told send back us mobile. now money wise its not possible me for send back mobile to him.
i tried to root mobile for updating baseband, but mobile hang at boot logo. then i searched flash file and SP Tool, In sp tool i selected all file from scattered.txt and pressed download for flashed mobile,
then after mobile is totally not recognized by pc.
]Please provide solution and rom for my device as my supplier is not supporting me.
I am attaching internal circuit photos and mobile pics and video for your ready reference. please reply on [email protected]
cybermaus said:
I am not as optimistic as Yuweng in that it is 'unbrickable', but if you mean to say that your PC *does* still detect a MTK usb com port, then I would indeed suggest we may be able to salvage the device. But before you try anything else, lets first get a proper idea of where you are, and how you got there:
1) Please describe properly what phone you have. Exact model, brand, where you bought it. Links to it may be useful. Do you remember what ROM it originally came with?
2) Please describe *how* you bricked the device. What did you do, what firmware did you try to load, what steps did you try to take, and how did it fail.
3) Please confirm if indeed you still see the MTK com port when you connect it to PC.
4) If you still see the MTK com port, you say you cannot flash. Please tell us why not. What flash method are you trying, using what ROM, and how is it failing?
In your answers, be descriptive and verbose. Foto's (or better screenshots) should be added if possible. Yes, this means a lot of effort, but if you think we can help you save your phone based on one-liners, you are wrong.
PS: Yuweng: can you please drop the 'master shifu' honorific? I am not any master builder, just hobbyist hacking about. Also I did not see the movie yet. Also, while impolite to ask, could I ask you to take a non-animated signature? Its funny at first, but after a while very distracting.
Click to expand...
Click to collapse

@ashishp.grims
The only way to solve your problem is by finding the correct ROM...So you better hope for one good Samaritan that has the same device, help you to back it up & upload it for you... :fingers-crossed:
Use this tool here by Russian Grand Master rua1... :good: It is able to backup full factory ROM out of a working MT65xx...
@cybermaus
not only you, even my own head is spinning when i browse back my own thread...
Point taken...

not recognized by pc
But my phone is not recognized by PC. I tried to press volume up button and connect USB cable to pc then also it is not detected by PC. how to make it detectable.
yuweng said:
@ashishp.grims
The only way to solve your problem is by finding the correct ROM...So you better hope for one good Samaritan that has the same device, help you to back it up & upload it for you... :fingers-crossed:
Use this tool here by Russian Grand Master rua1... :good: It is able to backup full factory ROM out of a working MT65xx...
@cybermaus
not only you, even my own head is spinning when i browse back my own thread...
Point taken...
Click to expand...
Click to collapse

Haha, if you say it is not detected by the PC then you have no other choice but to refer to this thread here...
Good Luck... :fingers-crossed:

Bricked MTK 6577
Dear,
My circuit board is different then shown in thread. i find only one point and not other and not able to understand how to use multimeter.
You can find photos of my mobile circuit in first post. if you able to show me which are the two points to use and about multimeter setting.
Thanks for helping me
yuweng said:
Haha, if you say it is not detected by the PC then you have no other choice but to refer to this thread here...
Good Luck... :fingers-crossed:
Click to expand...
Click to collapse

According to alexaglob, he use the multimeter as a jumper so that means to say you can just use any wires...
Having said that, of course the multimeter sharp probe is easier to use than jumper cables... :laugh: A much easier way if you don't have access to multimeter is to use one wire & two paper clips; strip both ends & just twist the wire to the paper clip, one at one end... It is the same principal... :laugh: Typically, the screw on the pcb is the GRD so if the testpoint doesn't work, then move on to other testpoint but GRD remain at the screw position... :fingers-crossed:
Switch on your PC speaker & hear for the Windows Hardware Insert sound just like when you insert your USB thumb drive sound...(As advice by rua1)
Follow alexaglob guide for remaining steps... :fingers-crossed:
But most importantly is, do you have factory ROM... No point doing this if you don't have it... :fingers-crossed:

Bricked MTK 6577
Dear Friend,
I dont have rom and i asked to supplier for providing firmware but he does not provide me yet. if you find please give me link.
yuweng said:
According to alexaglob, he use the multimeter as a jumper so that means to say you can just use any wires...
Having said that, of course the multimeter sharp probe is easier to use than jumper cables... :laugh: A much easier way if you don't have access to multimeter is to use one wire & two paper clips; strip both ends & just twist the wire to the paper clip, one at one end... It is the same principal... :laugh: Typically, the screw on the pcb is the GRD so if the testpoint doesn't work, then move on to other testpoint but GRD remain at the screw position... :fingers-crossed:
Switch on your PC speaker & hear for the Windows Hardware Insert sound just like when you insert your USB thumb drive sound...(As advice by rua1)
Follow alexaglob guide for remaining steps... :fingers-crossed:
But most importantly is, do you have factory ROM... No point doing this if you don't have it... :fingers-crossed:
Click to expand...
Click to collapse

Unbricked mobile
Hi friend,
Thanks for help i unbricked my mobile with your support and from this forum member "pierloca" http://translate.google.co.in/trans...phone.ru/viewtopic.php?f=70&t=23206&start=120.
But i need one more favor from you that my mobile one inner sim slot detecting sim but not able to connect with network. Please help me on this matter. :laugh::laugh::laugh::laugh::laugh::laugh::laugh::laugh::highfive::highfive::highfive::highfive::highfive:
ashishp.grims said:
Dear Friend,
I dont have rom and i asked to supplier for providing firmware but he does not provide me yet. if you find please give me link.
Click to expand...
Click to collapse

Congrats, less one MT6577 ends up to junkyard... :laugh:
When either SIM is not working, mainly it means the ROM is not your factory ROM...
But no worries, it can be solved by replacing modem.img at /system/etc/firmware
Again, you have to rely on a good Samaritan to help copy it & upload it for you... :fingers-crossed:
Just copy over via root explorer & reboot...
if still it doesn't work then you have to hunt for compatible one that works...

Network problem
But when i received brand mobile at that time this two problem is there first inner sim "not able to connect with network at this time" and second one is magnetic sensor not working. and due to these problem my phone bricked but thanks of you, i make it live my phone.
Is it issue with imei no?
yuweng said:
Congrats, less one MT6577 ends up to junkyard... :laugh:
When either SIM is not working, mainly it means the ROM is not your factory ROM...
But no worries, it can be solved by replacing modem.img at /system/etc/firmware
Again, you have to rely on a good Samaritan to help copy it & upload it for you... :fingers-crossed:
Just copy over via root explorer & reboot...
if still it doesn't work then you have to hunt for compatible one that works...
Click to expand...
Click to collapse

i presume the manufacturer wouldn't have supplied you a faulty unit... :fingers-crossed:
i've seen feedback here that at some country SIM2 just refuse to work...
Haha, since you mention, it might be an IMEI issue too...
hunt for it, as there are few IMEI writer apk for MT65xx here at xda too... :good:
Some report back that after using IMEI writer, their SIM2 works !
As for your magnetic sensor, typically the calibration is at settings -> display -> most bottom end
PS : You haven't share with us how you manage to unbrick your MT6577... Which testpoint that you had it jumpered to have SP Flash Tool work ?

yuweng said:
Normally for most MT65xx, you can't access META mode, to access it on my Lenovo, i have to take out the battery, press & hold volume up(don't let go) & plugin USB cable & the Device Manager will pop-up MTK USB COM for few seconds then disappear...( As the youtube video above )
Click to expand...
Click to collapse
I'm getting like you, MTK USB COM for 2-3 seconds then it disappears, how could I flash ROMs???

Unbrick MTk 6577
In SP Tool press download button then connect your mobile usb and follow TP point rules. then mobile will be flash.
leopesto said:
I'm getting like you, MTK USB COM for 2-3 seconds then it disappears, how could I flash ROMs???
Click to expand...
Click to collapse

ashishp.grims said:
In SP Tool press download button then connect your mobile usb and follow TP point rules. then mobile will be flash.
Click to expand...
Click to collapse
what I'll say is that I get this 3 seconds and progress bar goes 'till 100% red, but no green circle of flash complete, nothing applied...

Magnetic sensor MTK 6577
I solved all my problem except one magnetic sensor. as per android sensor box my magnetic sensor detected but when i click on that then there is no graph movement. please guide me.
yuweng said:
i presume the manufacturer wouldn't have supplied you a faulty unit... :fingers-crossed:
i've seen feedback here that at some country SIM2 just refuse to work...
Haha, since you mention, it might be an IMEI issue too...
hunt for it, as there are few IMEI writer apk for MT65xx here at xda too... :good:
Some report back that after using IMEI writer, their SIM2 works !
As for your magnetic sensor, typically the calibration is at settings -> display -> most bottom end
PS : You haven't share with us how you manage to unbrick your MT6577... Which testpoint that you had it jumpered to have SP Flash Tool work ?
Click to expand...
Click to collapse
---------- Post added at 06:24 PM ---------- Previous post was at 06:20 PM ----------
You must have first five file as per you mobile specification. First five file is very important to start your phone. if it is not match with your mobile configuration then progress not going beyond red.
ashishp.grims said:
In SP Tool press download button then connect your mobile usb and follow TP point rules. then mobile will be flash.
Click to expand...
Click to collapse

@ashishp.grims
You still haven't share on how you manage to unbrick & solved all you problems... Your detail explanations will greatly benefit & help out fellow xda member who just brick their MT6577...
i've seen on other thread did mention that new ROM update solve their problem while others says their MT6577 doesn't support Magnetic Sensor so E-Compass app won't work...
@leopesto
Same advice, try to hunt for your factory ROM as ashishp.grims did or post a new thread at Q&A so that a good Samaritan can help upload factory ROM backup with latest MTK Droid Tools, credits to Master Shifu bgcngm who has given this great tips... :good:

Related

Lenovo META mode

yuweng said:
i had the same issue like you when i tried to mod Bruno Martins's Extended User Data to my A789...
Then i think to myself how did lenovo flash in ROM at the first place & with that google leads me to this post about Power On sequences, thank you so much Master Shifu.... :good:
However, i can't exactly recall which or the correct sequence as i was trying all combinations with Flash Tool set at download mode all the time & voila, suddenly Flash Tool starts to download & i got my A789 back...
Click to expand...
Click to collapse
adeelahmed11 said:
Ohh realy you gave me new hope because its completely dead like no power on no charging tried all posible combinations
but now i have to try all seq in download mode but the issue is A660 factory not out yet i search so many chineas forms.
But atleast if it detects then there is some hope. I alredy packed to send back to china but i will try and tell you please pray for me and if you remember key sequence please write here thanks for giving me hope
Click to expand...
Click to collapse
yuweng said:
if not mistaken, its the Vol-Dn + Power goes into META mode... :fingers-crossed:
my best guess is the preloader as cybermaus has mention, for my case i use A789 preloader at first for my modding & internal memory just increase 100MB then i download the V970's preloader_mt6577_phone.bin which i though was generic then ends up problem just like you... It actually doesn't detect the phone but with the right combinations of Power on sequences it accepts Flash Tool download...
But first did you do a full ROM backup ?
Your case is a completely different than mine so i guess we'll have to wait for Master Shifu cybermaus to further advice you since you don't have a full factory ROM... :fingers-crossed:
Good Luck... :fingers-crossed:
Click to expand...
Click to collapse
@yuweng; @adeelahmed11
Yes, META mode is to flash without preloader. With it you can format the entire eMMC chip, just like we used to do on our MT6516 first generation of Mediatek Android chips. And indeed, it is how the factory puts on the preloader in the first place.
However, I was under the assumtion the following 3 issues would make this hard to use for adeelahmed11:
- The meta mode does not use USB, but bootstrap using serial, and requires a special cable in the 3.5mm audio port.
- On the A660 phone PowerDown+Volume down goes into FACTORY mode, so META mode must be a different one, but he has no more buttons to try.
- He would still need a factory original flash package to flash onto the A660
Now, if what yuweng said is true, and he really broke his preloader, and fixed it without special cable, then I would have to assume somehow Mediatek worked around the serial cable requirement. Maybe they integrate the PL2303 USB to Serial hardware in the chipset. That would be sweet. Or maybe they can drive the USB without preloader software in some rudimentary mode.
Tell us yeweng: Did you ever put a PL2303 device driver on your PC? Also, did you put the flash program in serial mode instead of USB mode (it's an option in the flash program menu.
As to adeelahmed11, if you want to try this, it may be better to first wait for a real A660 ROM. If somehow you get the phone into META mode, and the flash utility starts to flash, you want it to flash the right stuff. If you overwrite it with more wrong stuff using this deeper level, well, it will not improve matters

Wow, now that you mention so many stuff here in fact (1) i did have PL2303 USB driver that i use at work for serial downloading software but that usb to serial converter was not plug in to the pc. It didn't show up as active device at device manager...OS Win7 x86, i've attach the report generated by USBDeview...
(2) i use android-sdk usb_driver as the mediatek preloader driver doesn't work on my pc...(3) can't recall which version of Flash Tool i use for downloading, either version 3.1224.01 or 3.1222.00
(4) i did tried disable/ enable USB Mode at Flash Tool but can clearly recall it was in USB Mode when it starts to downloading...
(5) i was using only five files PRELOADER, DSP_PL, MBR, EBR1 & RECOVERY during my modding & first, i use all files from A789 with modded scatter.txt. As said, the mod wouldn't work & i started to use each file one by one from V970 & my last try was the preloader that got it 'brick'...
(6) For my case it was full ROM download but i presume download with the correct preloader would have 'unbrick' it...
Mostly said Mediatek is 'unbrickable' so lets hope we'll be able to 'unbrick' adeelahmed11 A660... :fingers-crossed:

You kept a USB sniffer active while you were messing with your phone? Or is this a USB sniffer-log of a different time?
If the first, then I take of my hat to you for foresight! If the latter, then I am not sure if I want to spent time analyzing it. So please do tell me which. Edit, its not a stiffer-log, just a list of installed devices. How do you know it was not active during your rescue?
Reading your story, it is less encouraging: You tried Druno's repartitioning, so that scatter file would have messed with the MBR and maybe EBR partitions. And while you did reprogram the preloader, you did so from the original phone? I can imagine that if you break your MBR, the phone would appear to be very bricked, but not as deeply as when the preloader itself is broken. I am thinking your preloader, and therefore your USB client-side software, was always OK.
A further hint would be: Did you have to reprogram your IMEI number and/or WiFi/Bluetooth MAC addresses? If not that is a further hint your phone was not truly bricked.
As a reference: The way I see the preloader is as the BIOS of the phone. It initializes some core hardware, so the actual boot, the uboot, can kick off. But first, it initializes the USB port, and has some bytes of software so that the USB port can be used to communicate and reflash. It waits a second in this state, before really kicking off the uboot The way I see META mode is as a sort of JTAG interface, so that with no software at all on the phone, through a simple serial port, you can very slowly program the flash chip from scratch.
Of course. that is what I suspect, and we have learned to distrust my suspicions.

Thank you Master Shifu for sharing your insight... :good: USBDeview is what i use for trouble-shooting for my usb to serial converter & the log was taken after the 'unbricking' process...Whoops, i can't confirm what was active during the rescue but i can confirm nothing shows up at device manager before the download starts & i didn't check what is there at device manager during the download...
i actually did the modding with caution but never thought wrong preloader would 'brick' the phone.... I've compare both files from A789 & V970 & to my surprise it is the same bit for bit except for PRELOADER & EBR1...even the scatter file is the same except for __NODL_FAT 0x629e8000 ! Bruno's Extended Data mod doesn't download everything... Fyi, i actually use scatter from Lewa ROM & earlier i have ported bruno's V970 to A789 with no patching at all, everything works except WiFi, GPS & a few others... Even after patching firmware folder with few related *.so, the problem remain the same... Well, i guess V970 is for V970 after all but it is very similar to A789 system files... :laugh:
So i guess for adeelahmed11 case, he has to get the correct preloader file to 'unbrick' it...
Found new info for downloading preloader for 'brick' MT6575/ 77
These russians are 'terror'...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
rua1 mention that some MT6575/ 77 can't access META mode because not all has the right combinations key button to access it...
The original thread is here...i use Google Chrome built-in translator & its translation make sense compare to other translator...
It might be useful for fellow xda member that 'brick' their MT6575/ 77 preloader other than Lenovo... :good:
Other useful tuts from russia here & here... :good:

Yes, that Russian site you found is the *normal* thinking that I also have/had. You need a USB-to-serial cable, and you need to connect the cable to a serial port. For a lucky few, the serial connection is hidden in the 3.5mm port, but that may not be on every brand and model. You notice how that guy is happy he found a point on the board that is the serial connection? You can bet he tried the 3.5mm first. Next he went to look on the circuitboard itself. It what I would have tried, if I had a brick in my hands. But unless if you have the tools and skills, it is not for the normal user.
You however claimed you did it *without* serial cable, *without* serial port, *without* 3.5mm connector. That is what surprised me. Either you did not really brick your preloader. Or Mediatek build in the USB2Serial module into the later chips, in which case that Russian link you found is nice, but on the too difficult and thus unneeded track that I would have gone also.
If true, the trick must be in the fact you had the PL2303 driver installed. When cold-staring your Android, the phone briefly linked up its PL2303 mode with the driver. And you had your flash tool set to serial. So it simply worked. If I recall correctly, a button combination may not even be needed, if you have the PL2303 driver active the flash tool will simply send a command over it to go into the programming mode automatically. Or at least, it did so for the MT6516 chip, as described here.
But for now, lets simply wait until a A660 ROM turns up. Or someone else with a brick in his hands and a matching flashable ROM to go with it.

Thank you so much for creating the thread and your help, i tried all possible key combinations, but there is no last breath i think i should not waste time and try to claim the warranty because its almost a week old, so better chance to get back, i can try the usb to serial but i need the cable and its not available in my city and if i order from web it takes time, also still A660 Rom not available, etotalk.com claiming that they have rooted rom but they are not selling it , they are selling with phone only.
if i get back a new phone i will try the flash again but without selecting the lo level files like MBR and preloader
anyway thanks guys

My dear Master Shifu cybermaus,
Just as you suspected, indeed, it become serial port...
i don't have to press the power button, with the battery out, i just hold the volume up on my A789 while plugging in the USB cable will activate META mode... :laugh:

I'll watch the video later.
Also, I see that a ROM has surfaced: A660_S019_120824
I will download it if I have a change, and try to create a recovery / ROW ROM for it

cybermaus said:
I'll watch the video later.
Also, I see that a ROM has surfaced: A660_S019_120824
I will download it if I have a change, and try to create a recovery / ROW ROM for it
Click to expand...
Click to collapse
What video boss and did you found the a660 rom so then i can try vol + and plug the cable

Ah, so you still have it then? Warranty not accepted? Bad for you, but strictly speaking correct, the shop did not send you a faulty product.
The ROM is this one with password bbs.lenovomobile.com
Do try to see if you can get it to work, by setting the flash tool to serial (not-USB), but to be honest, I still have my doubts about yuweng's case. I still wonder if his preloader was truly bricked. The video above shows the serial as it is provided from the preloader.
I did a full USB sniff/trace on the bootup process. In it, I did see above COM port, but not one before that.
But if he is correct, then the procedure will most likely be to remove the battery, connect the cable, start the download in the flash program and insert the battery.
You can also then try any button pressing, like power+volume-up to go into META mode. But this is I suspect controlled by the preloader, so that must be working. We need something before that phase.

Need CMW Recovery for Tooky(T1982) MT6575
Hi,
I tried this Rom with pressing vol+ while connecting to PC but nothing happened any way i sent back to china.
now i need help in my other china phone which is Tooky T1982. it is MT6575 so i tried Lenovo A750 Recovery but its not working, can you compile for me ? or guide me how do i it my self ?
here is i uploaded for your reference Tooky T1982 Rooted Rom
My 2nd question there is another model of Tooky T1981 and it has ICS 4.0 Rom can i port it to my Tooky T1982
here is i uploaded for your reference Tooky T1981 Rom
Waiting for your positive reply
Regards,
Adeel

i refuse to believe Lenovo has taken out META mode feature on newer device...
Have you tried all other combinations...
At Device Manager -> Ports, there should be MediaTek USB VCOM(Android) ComXX or at least an unknown device should pop-up with the usual device connect sound if you have ur speaker switch on...
Refer to my video, however, for your case, the PRELOADER shouldn't have shown up since i capture it when i have already 'unbrick' it & i don't dare try to 'brick' it again to have the video capture again... :laugh:

I tried all possible key combinations but no device detected but i have also ZTE V970(not bricked ) so i power off the device and while press the VOL+ button plug the usb cable and PC detect some APEX device under windows 7 but Vcom drivers did not apply on it

Ok ok, one last try if still cannot then no choice you have to sent it back... :fingers-crossed:
From my experience with 2 types of MT6577 as follows :
With battery inserted
Switch on ur speaker so that you will know if there is a new device connected (the sound is exactly just as u plug in ur USB thumbdrive)
1) Hold Volume Up, don't let go, now plugin USB cable ( this doesn't work on ur A660 )
2) Hold Volume Down, don't let go, now plugin USB cable
3) Hold both Volume Up & Power, don't let go, now plugin USB cable
4) Hold both Volume Down & Power, don't let go, now plugin USB cable
or may be u wanna try the unlisted method...
1) Hold both Volume Up & Down, don't let go, now plugin USB cable
2) Hold all button (Volume Up/Down with Power), don't let go, now plugin USB cable
With battery taken out
Same as above methods but with battery taken out
You have to have SP Flash Tool set to Download mode all the time while trying above steps & see if it starts to download if not then only try next method...May be u would also wanna try different USB port too if ur mobo supports USB2.0 or 3.0
I've also experience before with the battery taken out method, it may fail half way...What i did was, when it starts, reinsert back the battery & SP Flash Tool went on all the way ( this method i did was uploading system.img )
If it doesn't detect as Mediatek VCOM then fast fast double click it at Device Manager & force update it to Mediatek driver...
:fingers-crossed: :fingers-crossed: :fingers-crossed:

Thanks buddy but its already in china bcoz already waste too much time now lets see what lenovo service centre says

adeelahmed11 said:
now i need help in my other china phone which is Tooky T1982. it is MT6575 so i tried Lenovo A750 Recovery but its not working, can you compile for me ?
My 2nd question there is another model of Tooky T1981[/URL] and it has ICS 4.0 Rom can i port it to my Tooky T1982
Click to expand...
Click to collapse
That may be less easy than you think. Firstly, trat 1982 phone seems to not have hardly any hardware buttons. So you would need the Touch version of the recovery. But with a different resolution the Touch version that I have may not work. I will attempt, but I cannot give any guarantees.
For the same reason porting 1981 to 1982 is difficult. Different hardware buttons. Would be interesting to do if I had both phones in my hand, but as a blind build it is too error prone.

adeelahmed11 said:
Hi,
I tried this Rom with pressing vol+ while connecting to PC but nothing happened any way i sent back to china.
now i need help in my other china phone which is Tooky T1982. it is MT6575 so i tried Lenovo A750 Recovery but its not working, can you compile for me ? or guide me how do i it my self ?
here is i uploaded for your reference Tooky T1982 Rooted Rom
My 2nd question there is another model of Tooky T1981 and it has ICS 4.0 Rom can i port it to my Tooky T1982
here is i uploaded for your reference Tooky T1981 Rom
Waiting for your positive reply
Regards,
Adeel
Click to expand...
Click to collapse
I have the rom to but with CWM_5.5.0.4. and it's working great.
just download the .img rename and replace it.http://forum.xda-developers.com/images/icons/icon8.gif
http://ge.tt/6qy1HrO/v/5

joostboonstra said:
I have the rom to but with CWM_5.5.0.4. and it's working great.
just download the .img rename and replace it.http://forum.xda-developers.com/images/icons/icon8.gif
http://ge.tt/6qy1HrO/v/5
Click to expand...
Click to collapse
Thank you so much joostboonstra you really save so much time for reinventing the wheel are you using "T1982_V2.0.4_A3_S3_SVN1042_201207252315" or is there any update available? my phone soft restart after some time.

question
yuweng said:
i refuse to believe Lenovo has taken out META mode feature on newer device...
Have you tried all other combinations...
At Device Manager -> Ports, there should be MediaTek USB VCOM(Android) ComXX or at least an unknown device should pop-up with the usual device connect sound if you have ur speaker switch on...
Refer to my video, however, for your case, the PRELOADER shouldn't have shown up since i capture it when i have already 'unbrick' it & i don't dare try to 'brick' it again to have the video capture again... :laugh:
Click to expand...
Click to collapse
There are unknown device pop up in my bricked a789 phone
i try other a789 which are not bricked it able detect
any solution to get the device to detected?
Already solve by manually install mt6577 driver

[Q] Zhou Xing - How do I get the files to flash with SP Flash tool from stock ROM?

[update 2013/04/10]
And it is back to life! :victory:
I still cannot believe it! I decided to have another go using the Haier W718 USB cable and guess what? The cable supplied with the Zhou Xing i9300 is basically a big piece of s****.
I can confirm that the test point which worked for me are also GND + KCOL0
I have flashed the ROM wich link yuweng supplied. Thanks, again, bro :good:
Most things work except:
1) The ribbon cable running from the volume keys to the upper board is detached and I am not sure of how to fix this. Is it crazy to "superglue" it?
2) The IMEIs are not recognised. I have tried setting them up manually (following a video from Colonel Zap and taking the digits printed underneath the battery slot). No joy, no matter what SIM card slot I try, I get "IMEI invalid". In engineer mode, under bandmode, I have actually noticed that no band is selected. I check those applicable in Spain and click on "Set", but it basically ignores it.
So I am trying to get now a new ROM, hopefully closer to our settings in Spain. I have contacted a fellow member from a Spanish forum. Fingers crossed.
Oh, I almost forgot. Since the volume keys are not working because of the detached ribbon cable, I have ported TWRP recovery for the Zhou Xing. I thought a touch screen recovery would come in particularly handy now! Here it is.
BACKGROUND STORY BELOW:
Hi all!
I softbricked my Zhou Xing i9300 (MT6577) and now it won't boot :silly:. I cannot even get into recovery mode.
The only way I can access the phone is by SP Flash Tool. Thanks to another member of this forum (Dragonevo) I got hold of the stock ROM. However, this file is in a zip format, so the kind I have seen updating from recovery mode. Only the boot.img file is found out of all the files SP Flash tool looks for. Is there a way I can get the rest of the files for SP Flash Tool from this stock ROM zip including the scatter text?
Thanks!
khankll said:
so what is the update ?
copy all the info in first post so it is easy to keep track of goings so far.
Click to expand...
Click to collapse
Thanks, khankll So here is the update on the 1st post. Sorry, but I am leaving in an hour and will be away for the whole week, so this is as much I can tell at this point.
khankll said:
the first thing is that you make it recognizable by pc .
Click to expand...
Click to collapse
At first I still got it recognised as MTK device, but right now the best I get is an "Unknown device" under USB devices (not under COM ports). This is with the phone completely assembled and battery inserted. When I dismantle the phone to try to trigger test point, no sign of life whatsoever. If I try to update the drivers, I get something like "Windows determined the best drivers are already present". I guess Windows is only detecting the device as some kind of USB memory and that is it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
khankll said:
for rom do search at china-iphone.ru forum .. also 4pda.ru ..
Click to expand...
Click to collapse
I already found a ROM thanks to dragonevo's pointer here. The problem is, I guess, this ROM is in a format to be used when you can boot into Recovery mode. I say "I guess" because I have never got to see Recovery mode on this phone. I am not even sure of the key combination (tried Power & Volume + and Power & Volume -). I am using SP Flash Tool and it looks first for a scatter text file, and several other files that are not in that ROM zip, (only the boot.img is there). And from what I gather all these files also are specific to the phone model.
This is why I raised my original question in this post, so that I could use the ROM found in Flash Tool.
khankll said:
try all the connections to be ok .. usb connector should be making proper connection .. try checking continuity b/w the pins inside connector and the point where they attach to pcb.. ( u can attach a thin wire to the probe of multimeter and insert that into usb port .. its hard but possible . i did checked like it ..)
Click to expand...
Click to collapse
I am not sure I get this, but I will try when I get back in one week
khankll said:
also what is the battery voltage ? is it charged ?
Click to expand...
Click to collapse
2.9 v (I have a spare one which reading is 4.1 v)
Reminder: when I try the test point, the battery is not present (it cannot be since the board has to be completely dismantled on this phone to access KCOL and GND points. commonwarrior has another phone model but exactly the same board and it has worked for him this way. If I got this right, the battery is not required and Flash Tool (since yesterday I am using the latest supplied by commonwarrior) actually has an option called "Autodetect", which is supposed to work either way, with and without battery). file is in a zip format, so the kind I have seen updating from recovery mode. Only the boot.img file is found out of all the files SP Flash tool looks for. Is there a way I can get the rest of the files for SP Flash Tool from this stock ROM zip including the scatter text?
Thanks!
[update 2013/02/14]
Sorry about vanishing, guys. I actually bumped into a bigger problem. My PC hard disk crashed. Anyway, I recovered my older (and smaller capacity) hard disk and installed it. As to the OS, I have just installed Ubuntu 12.04 + Windows XP as a virtual machine. I am a novice to Ubuntu, so please forgive me if the ending of this story is still delayed as I have other priorities to take care of right now.
Thanks a bunch again to yuweng for the correction for the test point and finally the files to flash from SP Flash Tools. I have downloaded the files and will have another go when I get the chance.
To be continued...
[update 2013/02/18]
I am afraid I am giving up on the Zhou Xing. No matter what test point I try, I never get any response in Flash Tool (I have also tried different versions including the latest one uploaded by commonwarrior).
With all the handling, the flat small cable that runs from the Volume up and down keys is detached from the contacts on the main board and I cannot see how I could weld these back.
So I am closing this chapter on my end. I hope it has been helpful to other people. At least now we have the files to flash from Flash Tools for this phone model. I wish we had found them before I screwed it completely.
Thanks again for all your help, particularly to yuweng and commonwarrior

Zhou xing bricked.
2x1 said:
Hi all!
I softbricked my Zhou Xing i9300 (MT6577) and now it won't boot :silly:. I cannot even get into recovery mode.
The only way I can access the phone is by SP Flash Tool. Thanks to another member of this forum (Dragonevo) I got hold of the stock ROM. However, this file is in a zip format, so the kind I have seen updating from recovery mode. Only the boot.img file is found out of all the files SP Flash tool looks for. Is there a way I can get the rest of the files for SP Flash Tool from this stock ROM zip including the scatter text?
Thanks!
Click to expand...
Click to collapse
I bricked my Zhou xing.
It's dead...
I followe the system explained here http://forum.xda-developers.com/showthread.php?p=34912486#5...but I don't know exactly the test point on the mother board...so without success
Do you know a system to enter again in recovery ? also by spflash?
Could you shared the original rom..please.?
Thanks in advance...in this moment I'm in a big panic:crying:

pigu36 said:
I bricked my Zhou xing.
It's dead...
I followe the system explained here http://forum.xda-developers.com/showthread.php?p=34912486#5...but I don't know exactly the test point on the mother board...so without success
Do you know a system to enter again in recovery ? also by spflash?
Could you shared the original rom..please.?
Thanks in advance...in this moment I'm in a big panic:crying:
Click to expand...
Click to collapse
Sorry, pigu36, I actually never got into Recovery mode. I flashed mine (and softbricked it) with SP Flash Tool.
Regarding the stock ROM, you will find the link in Dragonevo's post.
Maybe in that same thread, somebody will be able to tell you how to get into Recovery mode. As far as I am concerned, I have tried pressing "Power + Volume up" keys, but it has never worked.
Whatever I find out, I will share it here and in the other thread.
Good luck!

so whats the issue of playing with test points if u can make it detect thorugh spf ?
just search for ok rom and flash it ..

khankll said:
so whats the issue of playing with test points if u can make it detect thorugh spf ?
just search for ok rom and flash it ..
Click to expand...
Click to collapse
Sorry about the confusion, khankll.
This was before I tried to flash something else because I thought it could not get worse and maybe I could flash some kind of Recovery which would allow me to update from the SD card (where I have a copy of the stock ROM in a zip file).
However... things could get worse and they did. The phone is not detected any more even in SP Flash Tool, not charging... well you know the symptoms. So I found the test point thread and fingers crossed with all the advice you guys are helping with
If I am lucky with the test point method, I will still need the type of files SP Flash Tool looks for. Unless you know a way of getting them (converting repacking, I don't know what the right word would be) from the stock ROM zip file.
Model: ZhouXing I9300 MTK6577 Dual Core Android 4.0 3G GPS 4.7 Inch 8.0 MP Camera Smart Phone
Some pics

so what is the update ?
copy all the info in first post so it is easy to keep track of goings so far.
the first thing is that you make it recognizable by pc .
for rom do search at china-iphone.ru forum .. also 4pda.ru ..
try all the connections to be ok .. usb connector should be making proper connection .. try checking continuity b/w the pins inside connector and the point where they attach to pcb.. ( u can attach a thin wire to the probe of multimeter and insert that into usb port .. its hard but possible . i did checked like it ..)
also what is the battery voltage ? is it charged ?

2x1 said:
Is there a way I can get the rest of the files for SP Flash Tool from this stock ROM zip including the scatter text?
Thanks!
Click to expand...
Click to collapse
Sent you pm previously & notice that you haven't been online since 8th February 2013 08:20 AM...
Good news, found your Stock ROM here, credits to Анатолий... :laugh:
it turns out the testpoint KCOL0 & GND is wrong, credits to orx65...
Hopefully, this infos here will be useful for Zhou Xing users to unbrick their device too... :fingers-crossed:
Cheers...

Many, many, thanks for this rare rom. So I was able to unbrick my phone without any hardware experiments. I searched several Weeks!
My only problem is, that there is no touchscreen-response.
Any Idea to solve this problem?
Thanks and regards
Herby53

Hmmm, could i be that you forgot to install back the Touch Screen panel Flex Ribbon Cable...
Attach example is my friend's Touch Diamond2 9300 i help him replace the Touch Screen panel, hopefully it will be useful as a guide...
Another possibility is that may be this ROM is not for your Zhou Xing... :laugh:
Could you comfirm that the testpoint for your Zhou Xing is KCOL0 & DM

yuweng said:
Hmmm, could i be that you forgot to install back the Touch Screen panel Flex Ribbon Cable...
Attach example is my friend's Touch Diamond2 9300 i help him replace the Touch Screen panel, hopefully it will be useful as a guide...
Another possibility is that may be this ROM is not for your Zhou Xing... :laugh:
Could you comfirm that the testpoint for your Zhou Xing is KCOL0 & DM
Click to expand...
Click to collapse
Thanks for the fast response, Yuweng
I have installed back the Ribbon Cable, but not correct and without complete contacts. Now the TouchScreen works, but the touches lands not there where they should. Especially noticeable when using the phone keypad #1-3 = #4-6. I think I have to calibrate the touchscreen, but don't know how.
Second problem: the hardware- (volume up / down) - and sensor buttons (menu, home and back) are without function. I hope I did not damaged the flat cable searching the testpoint.
Your question about the testpoint:
See thread ..... / / forum.xda-developers.com/showthread.php? p = 36908056
# 240
The first image shows the backsite of the board. Testpoint for me wars KCOLO & GND to start flashtool download => there is no Point DM.
Greetings
Herby

Hmm, according to orx65 photo on previous page, its definitely not KCOL0 & GND ( the two red dots )....
Big problem ! To calibrate Touch Screen, you need to boot into Factory mode....
Shut down the phone then hold Volume Down, don't let go & press power button until you see that it boots into Factory mode then only let go... :fingers-crossed:
Then it will display all the keys that you need to press once then only you can proceed with the Factory mode calibration...
ESC, BACK, MENU, VOLUME UP, VOLUME DOWN, POWER

Thanks once more!
I first have to repair the definitly broken flat cable for the hardware buttons. It already looked a bit cracked out of delivery.
But my fingers and my soldering iron are to big. :laugh: I must look even if there's a trick!?
Testpoint:
The combination on first picture (with phone 9 ContactPoints) ist KCOLO (2nd row/ center) & GND (first row/ center) worked for me.
It's shown in the picture thereunder.
There is no Contact with DM. 3rd Row right Contact is named DP, but I don't know if this ist what you are looking for.

There is one crazy idea on repairing the Flex Ribbon Cable here with a staple... :laugh:
Can't see it clearly on those photos, so what i meant was : does KCOL0 with DP works, if not then i'll remove the photo on previous page...

... for me only KCOLO & GND works ...

Hey! You don't have ti flash it under a virtual machine. It causes problems. 1st of all, you have to download the stok rom, unpack.it on a pc with a windows installed. Install the.phone.drivers. disassembly the.phone and do a little.test point.to recognize the.flash mode. Run the.flash tool.loading the scatter file of.your stok, start the flashing in all the ports using the Automatic flag in battery section, the Preloader flag under the battery section. Also check.the usb option, just enable.the.Usb and not mpre.connetions kind. Start the flashing.in alk the ports, make.a.little test point and you.will see the loading.flashing.bar sorry for the errors in my typing.thw qwerty touch is very hard to use
Sent from my lt29i modded phone!

commonwarrior said:
Hey! You don't have ti flash it under a virtual machine. It causes problems. 1st of all, you have to download the stok rom, unpack.it on a pc with a windows installed. Install the.phone.drivers. disassembly the.phone and do a little.test point.to recognize the.flash mode. Run the.flash tool.loading the scatter file of.your stok, start the flashing in all the ports using the Automatic flag in battery section, the Preloader flag under the battery section. Also check.the usb option, just enable.the.Usb and not mpre.connetions kind. Start the flashing.in alk the ports, make.a.little test point and you.will see the loading.flashing.bar sorry for the errors in my typing.thw qwerty touch is very hard to use
Sent from my lt29i modded phone!
Click to expand...
Click to collapse
Thanks, commonwarrior
Just for the record, I never tried flashing under a virtual machine. The Ubuntu + VirtualBox set up took place after many tests under Windows 7 when my hard disk failed. I may have another go on my laptop (running Windows XP) and if I succeed, I will let you know.
Cheers!

2x1 said:
Thanks, commonwarrior
Just for the record, I never tried flashing under a virtual machine. The Ubuntu + VirtualBox set up took place after many tests under Windows 7 when my hard disk failed. I may have another go on my laptop (running Windows XP) and if I succeed, I will let you know.
Cheers!
Click to expand...
Click to collapse
This is a capture for the flash tool settings. In option, leave just the usb flag and disable the RID flags. Just copy all the options you see in this picture and start the flashing in all the ports to be sure.
Sent from my lt29i modded phone!

I solved the problem
pigu36 said:
I bricked my Zhou xing.
It's dead...
I followe the system explained here http://forum.xda-developers.com/showthread.php?p=34912486#5...but I don't know exactly the test point on the mother board...so without success
Do you know a system to enter again in recovery ? also by spflash?
Could you shared the original rom..please.?
Thanks in advance...in this moment I'm in a big panic:crying:
Click to expand...
Click to collapse
If you don´t have solved the problem I have the original Zhou xing android 4.1.1 rom flash usb cable intallation

USB problem?
Hi guys. I few weeks ago I received my Zhou Xing i9300 and everything work great, but now, some days ago it start to no be recognized by my PC.
It simply dont do nothing.
I already try a new USB cable and even try to connect to another PC here i my home, and stay won't working.
Any idea about what possibly happens?
Any help will be veeeeeery appreciated.

[HOWTO][GUIDE] Root & Backup of almost EVERY mt65xx based Device

THIS WILL ONLY WORK WITH DEVICES USING EMMC PARTITION LAYOUT!
otherwise flashtool cannot properly readback needed files wich will cause a bricked device. for rooting mt6573 or mt6575 without emmc partition layout,
refere to this method by rua1: http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5
You need to upload the needed files to your Computer using the Read Page Only feature.
ALSO, MAKE SURE YOUR DON'T TRY THAT ON AN ALCATEL (OR SIMILAR) DEVICE, INDICATOR HERE IS A CUSTPACK PARTITION IN SCATTERFILE.
those devices have mt65xx, but have a totally different partition strukture. You can try this tutorial, BUT IF YOU BRICK YOUR DEVICE; I CANNOT HELP YOU OUT!!!
since a lot of devices have different hardware - e.g. Display or Camera - making a Backup of your device should have highest priority. Flashing a wrong ROM can brick your phone!!
What is needed:
VCOM Driver, thx to n2k1
ADB, thx to n2k1
MTK Droid Tools V2.46
If you wan't to use the newest Versionof MTK Droid Tools, refere to here:
http://forum.xda-developers.com/showthread.php?p=38337401#post38337401
also, you can buy Master Shifu rua1 a coffee for his great tool!
Support for the newest Version of Droid Tools is NOT given in this thread! I personally don't use his tool so if something unexpected happens, its not my fault.
SP Flashtool V3.1224 for mt6589, newer flashtool is needed!!! if there are some problems with reading back or flashing the device, newer flashtool is needed.
Install the needed drivers. installing VCOM drivers might take a while, because it will show up just a few seconds while connecting the phone(off).
and now the Step-by-Step tutorial to backup your boot.img, recovery.img and system.img for rooting.
1. enable USB-debugging under Settings-Development->USB debugging
2. phone should now get recognized as "Android Phone - Android Composite ADB Interface" -> if this is a Unknown Device, you should install the ADB drivers.
3.Open MTK Droid Tools
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. Connect device to USB (USB Debugging has to be enabled)
5. Device informations has been loaded, Press on "Blocks Map"
We'll need to find the lines bootimg, recovery and Android. We'll need to write down Start-adress(Scatter) and the Size for every line.
(i made a screenshot, writing down isn't necessary.)
In MY Case, this is:
bootimg: 00F88000 size: 00600000
recovery: 01588000 size: 00600000
Android: 026E8000 size: 31900000
6. Now we'll need to click on "Create Scatter File" and you can save it as "MT6577_Android_scatter_emmc.txt"
7. You can Close MTK Droid Tools now.
8. Now we need to open SP Flash Tool and we need to load the scatter file.
9. Now we'll need to click on "Read Back" in the top of SP Flash Tool.
Click on "ADD" 3 Times, we will create "ROM_0", "ROM_1" and "ROM_2".
10. Doubleclick on "ROM_0", and select a place to save it, e.g. C:/N9770_backup/ and rename it to"boot.img"
11. now it will ask you for the Start Adress and lengh for bootimg, we wrote down earlier.
this is in my case: Start Address: 0x00F88000; Lenght: 0x00600000. the first "0x" MUST remain at its place!
12. the same thing you'll need to do for "recovery" and "android".
13. disconnect, shut down and remove the battery of your Device.
13. Now we'll need to click on "Read Back", insert your battery and connect your device to USB. (VCOM driver is needed now, you'll need to install it before getting to the next steps)
14. if this were correct, a red bar should appear on the bottom of SP Flash Tool. you'll need to wait until the green ring appears.
15.Flash Tool now read back the 3 files. system.img isn't that important, but boot.img and recovery.img should be around 6 MB. if the file is smaller or bigger, the length is different to my device or there was a failure while reading back your firmware. So make sure, that at least recovery or boot.img has the right size!!
16. Back to droid tools. reconnect your device to USB , debugging should be enabled, too. switch to "root, backup, recovery" tab in MTK Droid Tools.
select "to choose the boot.img" and press on "Recovery and boot". select your backup boot.img and recovery,img. MTK droid tools will patch boot.img, so you obtain permanent shellroot.
(optional) a window will pop-up and ask you, if you want to install CWM-r. i cannot tell you if that will work, but you can try it, since you backed up your recovery before. )
(optional) a window will pop-up and ask you for the name of your device(you connected it before starting droidtools, so this should not ask you for the name). you can just press enter or you can enter a name for your device.
17. Droid Tools should have modified the boot.img. "--a task is complete--" text should show up in the right of droidtools.
18. Back to Flashtool
You'll need to load the Scatter (like in Step 8)
select boot.img and recovery.img. make sure you select the modified files. (.../Droidtools/recovery/boot.img and recovery.img)
only boot and recovery should be selected!!
19.disconnect, shout down and remove the battery of your device. press on "Download", a window will show up that you have not selected all images. you can press on "OK".
20. insert the battery and connect your device to USB. Flash process should start and if it worked, green ring will appear.
21. Back to DroidTools. device needs to be connected and debugging enabled. switch to "root, backup, recovery" again and press on "SuperUser". this will push superuser, SU binary and busybox to your device.
22. Your Device is rooted now. you can make a Full backup with Droid Tools now.
thx to n2k1 and tommy0815 for the needed files and the original tutorial!!
if i helped you, don't forget to press on "thanks"

reserved for future updates

Testing on my Acer Z120 MT6575 base, I hope this will work, feedback later *fingers crossed*
FEEDBACK:
It totally worked, My Acer z120 is now rooted.
(optional) a window will pop-up and ask you, if you want to install CWM-r. i cannot tell you if that will work, but you can try it, since you backed up your recovery before.
Click to expand...
Click to collapse
Do not use CWM, it will cause your phone not to boot properly, that is my experience on my phone.
Thanks!

yeah never tested it though, thx for the reply!

Re: [HOWTO][GUIDE] Root & Backup of almost EVERY MT65xx based Device
is there anyone here who tried to follow this thread and successfully rooted his android phone?lenovo s720 user here.waiting for more positive feedbacks.

Will this method work on a Vodafone Smart III (975N) probably with 6575?

Guys, this will work on every mt65xx device, if you installed all drivers sucessfully .this whole thing basically changes a value in Boot.IMG To obtain permanent root in the shell. This is the same on EVERY mt65xx based smartphone. Basically you are rooted now. Just needs To push busybox, su and superuser To your device. Thos whole thing seems complex, but you make a backup oft your modified files before modifiing. I never Had device this tutorial was not working every mt6575, 6577 and 6589 should work without an problem. Mt6573 can be a Problem because oft their YAFFS partition strukture.

Chrizzly92 said:
Guys, this will work on every device, if you installed all drivers sucessfully .this whole thing basically changes a value in Boot.IMG To obtain permanent root in the shell. This is the same on EVERY mt65xx based smartphone. Basically you are rooted now. Just needs To push busybox, su and superuser To your device. Thos whole thing seems complex, but you make a backup oft your modified files before modifiing. I never Had device this tutorial was not working every mt6575, 6577 and 6589 should work without an problem. Mt6573 can be a Problem because oft their YAFFS partition strukture.
Click to expand...
Click to collapse
Thanks, I will try!
Sent from my Samsung I9300 with tapatalk4

thank you for this :thumbup:
Sent from my PICOpad GEW using xda app-developers app

dbius said:
Will this method work on a Vodafone Smart III (975N) probably with 6575?
Click to expand...
Click to collapse
Yes, i rooted my vodafone 975N with this method (CWM recovery working) :good:

Gynekolog said:
Yes, i rooted my vodafone 975N with this method :good:
Click to expand...
Click to collapse
:good: That sounds great! Thx man for the informations!
Edit:
Now i tried to root the phone. Everything is went fine till phase nr.19. At this point when the flashtool tried to write back the modified boot.img and recovery.img it gave back me the attached error window.
What should be the problem? I went through the steps with doublecheck and everything was fine till that point. I tried this step two or three times more, but every time gave me this error message.
What should I do now? If it helps I can upload the log folder content here.

Make sure the scatterfile is correct and the files should not be bigger than 6 MB. Flash tool tells you that you need to flash a full image cause the scatter is different from you phone.
Sent from my Star N9770 using xda app-developers app

Chrizzly92 said:
Make sure the scatterfile is correct and the files should not be bigger than 6 MB. Flash tool tells you that you need to flash a full image cause the scatter is different from you phone.
Sent from my Star N9770 using xda app-developers app
Click to expand...
Click to collapse
!EDIT!
Thanks for your answer!
Tonight I found a newer version for flash tool (v3.1304.0.119). Using that version rooting the phone was successful, so thanks, finally it worked.

VCOM Ports
Gynekolog said:
Yes, i rooted my vodafone 975N with this method :good:
Click to expand...
Click to collapse
I still cant root my device. I think its the VCOM ports, because i cant flash
When i click "Read Back" the device is not there..
Can you help me?
Thanks!

This will be very helpful. I have a china phone running on MT6577. I've successfully installed a ported V970 ROM to ZA-985 (which is compatible to my unit in terms of hardware and appearance). I wanna try porting a JB V970 Lewa OS ROM to Kata i1 (identical to ZA-985).

dbius said:
!EDIT!
Thanks for your answer!
Tonight I found a newer version for flash tool (v3.1304.0.119). Using that version rooting the phone was successful, so thanks, finally it worked.
Click to expand...
Click to collapse
thx for your reply, i updated Post #1 , that for mt6589 newer flashtool is required nad sumtimes youll need to play with them. this is because the widely spread devices, they are not the same and sometimes big differences in partitionlayout, SoC revision and so on.
@verntechguy: after rooting, make sure you get a full backup of your device using mtk droid tools. porting lewa is not that hard, but you maybe need to try different platforms to port from. you can refere to here, master shifu yuweng made a pretty good tutorial abut porting Roms.
@Beirajunior: is your device recognized as "mt65xx preloader" when connection to USB? (phone should be off) if not, you can try pressing VOL Up or down while connecting to USB. for flashing, VCOM port 1-16 should be assigned to the drivers.
6

Chrizzly92 said:
thx for your reply, i updated Post #1 , that for mt6589 newer flashtool is required nad sumtimes youll need to play with them. this is because the widely spread devices, they are not the same and sometimes big differences in partitionlayout, SoC revision and so on.
@verntechguy: after rooting, make sure you get a full backup of your device using mtk droid tools. porting lewa is not that hard, but you maybe need to try different platforms to port from. you can refere to here, master shifu yuweng made a pretty good tutorial abut porting Roms.
@Beirajunior: is your device recognized as "mt65xx preloader" when connection to USB? (phone should be off) if not, you can try pressing VOL Up or down while connecting to USB. for flashing, VCOM port 1-16 should be assigned to the drivers.
6
Click to expand...
Click to collapse
Can you help me by team viewer ? :x i still cant do the flash..and the phone is reconized as "mt65xx preloader" but after a while he disconect.
My email is: [email protected]
I appreciate any help.
Cheers

no, i cannot help you via teamviewer, my internet connection is too slow, cause i`m on tethering. some additional infos will be helpfull. device? mt6573,75,77,89?
if the device gets found, everything should work. you`ll need to assing the VCOM ports. just look in the driver settings or google it. i`m sure there is some kind of tutorial for it. also, trying another PC or OS will help, too. alot of guys have problems with that, just switching to XP or so will mostly help without tweaking the drivers.
device should be disconnected and battery should not be inserted. now press readback in flashtool, insert battery and connect the device to USB. now phone should be found by flashtool. if not, like i said, check VCOM ports.

Chrizzly92 said:
no, i cannot help you via teamviewer, my internet connection is too slow, cause i`m on tethering. some additional infos will be helpfull. device? mt6573,75,77,89?
if the device gets found, everything should work. you`ll need to assing the VCOM ports. just look in the driver settings or google it. i`m sure there is some kind of tutorial for it. also, trying another PC or OS will help, too. alot of guys have problems with that, just switching to XP or so will mostly help without tweaking the drivers.
device should be disconnected and battery should not be inserted. now press readback in flashtool, insert battery and connect the device to USB. now phone should be found by flashtool. if not, like i said, check VCOM ports.
Click to expand...
Click to collapse
Hi,
Im already done, but im receiving this error when i try to modified the backuped files (boot and recovery) on MTK Droid Root.I sai no to similar CWM, and i get this error:
"--- ERROR :Boot unthe public mailing list [email protected]"
" --- task is complete ---"
What do you suggest ?
Cheers!

what SoC? mt6573?

Lenovo Tab a10-30 bricked or fixable?

Hello everyone,
I will share my experience with you, and I hope for a solution!
A few days ago I rooted my Lenovo tab 2 A10-30 successfully using Kingroot. Then, I tried to change Kinguser with SuperSU, which I also successfully did. However, I noticed that although the main root app was SuperSU, Kingroot was still on my phone, so I deleted it using a bloatware removal app and restarted the tablet. Now it won't turn on. It gets stuck at the Lenovo loading screen, and that's about it. When I press the power button + volume down button, it gets me to a Chinese menu that is not the recovery mode (there is no MMC, just options about voloume, colors, mic test etc). If I press the volume up+ volume down + power button, it just brightens the screen and shows nothing.
I tried flashing the stock ROM using the Smart Phone Flash Tool, but the PC does not recognize fully the tablet (it just prompts me to install the Lenovo USB drivers, and I cannot access the tablet's internal storage). Moreover, the Lenovo windows applications do not recognize the tablet when I connect it to the PC.
I really do hope that there is a way I can fix it.. Thank you all in advance.

Hi,
I did almost exactly the same... Kingroot, tried to remove bloatware with another app, and ended up with a bricked tablet I can still access the bootloader, but flashing the tablet from there is to no avail.
I am still looking for the original ROM, which seems nowhere to be found. Did you, by any chance, make a backup first?

Another one here But I'am able to go into recovery and into adb sideload, from there I can view internal memory(/system). And it looks like system is trying to load supersu-daemon which was removed and it can't get past that. I tried to recover paths (to original ones), but it still wont go past loading screen. (it is just restarting the app_process32).
Now if we only could get the hold on original factory firmware... from there one we can sideload it via fastboot.
And for the drivers you need andorid usb drivers https://developer.android.com/studio/run/win-usb.html#top
TLDR; we are looking for TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip

So, I have spent about 5 hours attempting to find a way to dump the firmware without first rooting the device, so that I could share it with you guys (and have a backup for myself in case I attempt to root it myself.) Unfortunately it seems like it needs to be rooted before I can create a nandroid backup through adb. Unfortunately the tablet is not based on mtk, and I cannot find any qualcomm utils that can dump the firmware.
The one Qualcomm util I found (QFIL) seems like it is only for flashing, and for backing up some individual data for the tablet (I assume it may contain such as license keys for the commercial features in the recent phones such as Sony Xperia Z3). I also looked into fastboot, and that too can only flash a new firmware.
So, unless the tablet gets rooted I don't see any way to make a proper backup.
I am unable to post links in messages, so you need to do some manual editing.
dz0ny said:
TLDR; we are looking for TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip
Click to expand...
Click to collapse
This however seems like very valuable information, unfortunately the only places I can find that has this available for download is charging money for access to the file.
50$ at dlgsm,com www DOT dlgsm DOT com/register.php?file=TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip&dir=%2FFLASH-FILES%2FLENOVO%2FT_Series%2FTB2-X30F
or from 10$ at pars-hamrah,com: www DOT pars-hamrah DOT com/%D8%A7%D8%AE%D8%A8%D8%A7%D8%B1-%D9%85%D8%B1%DA%A9%D8%B2-%D8%AF%D8%A7%D9%86%D9%84%D9%88%D8%AF-%D8%A7%D8%AE%D8%AA%D8%B5%D8%A7%D8%B5%DB%8C-%D9%BE%D8%A7%D8%B1%D8%B3-%D9%87%D9%85%D8%B1%D8%A7%D9%87/38027-%D8%B1%D8%A7%D9%85-%D8%A7%D9%88%D8%B1%D8%AC%DB%8C%D9%86%D8%A7%D9%84-%D9%84%D9%86%D9%88%D9%88-lenovo-tb2-x30f-%D9%86%D8%B3%D8%AE%D9%87-s000015-%D8%A7%D9%86%D8%AF%D8%B1%D9%88%DB%8C%D8%AF-5-1-1-%D8%AF%D8%B1-%D9%85%D8%B1%DA%A9%D8%B2-%D8%AF%D8%A7%D9%86%D9%84%D9%88%D8%AF-%D9%82%D8%B1%D8%A7%D8%B1-%DA%AF%D8%B1%D9%81%D8%AA.html"]Here[/URL]
It might also be available www DOT fars-gsm DOT com/75531-tb2-x30f_usr_s000015_1601151950_q8009_row_qpst-zip.html, at least they list the changelog for the firmware.
Since I have no use for a firmware right now, I will not be buying access to one (unless I at some point manage to brick mine as well). But if anyone decides to do so, please share it so others can enjoy it as well. I also suspect that if the file was available, it would increase the probability of someone attempting to make a custom rom at some point as well, it is a very cheap tablet when on sale, so it should have good potential for a community.
PS: I also stumbled over something called vRoot, that might be an alternative to Kingroot, although I have no idea whether it is as good at rooting and not installing unwanted extra apps. I guess someone who has used it on a tablet/phone that has a backup available might be able to shed some light on that.
---------- Post added at 08:08 PM ---------- Previous post was at 08:02 PM ----------
omrtpsycho said:
If I press the volume up+ volume down + power button, it just brightens the screen and shows nothing.
Click to expand...
Click to collapse
This is the QFIL (Qualcomm Flash something system) mode, however I do now know whether that helps anything at all. Since it seems to me it probably wont accept the TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip file mentioned in the thread. It seems to expect some xml file, maybe the zip file contains that?

Hi guys i have been strugling with this unit The last 3 days. I have eksakt same problem. I found these files: lenovo-forums.ru/files/category/106-прошивки-lenovo-tab-2-a10-30/
I extracted Them but dont know how to flash Them ?? Hope u guys Can help (sorry for bad english)
To Download files from Lenovo-forums.ru i logged in with my Google account

[PUT ROM TEMPORARILY HERE: https://www.wetransfer.com/download...024ee2974a44f8aa50e3dcd120160615184237/a84735 ]
Wow, suddenly action! With the help of Dead2 and Andersbp I have made some progress. Here are my steps:
I purchased the ROM from the Iranian site, and downloaded the other from the Russian forum. So now I have 2 ROMs:
65M TB2-X30F_S000015_160115_ROW_TO_TB2-X30F_S000016_160602_ROW_WCA72E4AB5.zip (Russian)
1.1G TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip (Iranian)
The smaller one is simply an update, which you could install easily:
1) boot into Recovery Mode
2) select "Apply Update from ADB"
3) run: adb sideload TB2-X30F_S000015_160115_ROW_TO_TB2-X30F_S000016_160602_ROW_WCA72E4AB5.zip
Which works... UNLESS YOU ROOTED THE DEVICE. Then it fails, and does not want to update. Thanks Lenovo
So, the larger one is a different type of ROM. This one will not load with adb sideload (gives footprint and signature error). But it DOES contain all the files to flash with QFIL (Qualcomm Flash something system).
Here I'm stuck. I followed this guide:
http://guidebelajar.blogspot.nl/2016/03/guide-how-to-flash-firmware-lenovo-vibe-p1.html
and tried to install these packages:
1) You must download and install USB Driver for Lenovo on your windows computer or PC.
2) QPST-2.7.422-qfil-qcom-Upgrade-Tool-20140422
3) Download Qualcomm HSUSB USB COM Drivers
(Note that you need to register and log in to needrom.com FIRST. Then click the link, but it will give an access error. Remove all in the URL after needrom.com (so go back to the main site), then go back to the download link, and it will work - the file is there.)
1) and 2) install pretty fine, but 3) is just a zip with a lot of drivers, no installer. I have no clue on how to install the proper driver...
Furthermore, the site suggests to install something on the device itself:
5) Create a folder with the name sdfuse in the root of the SD-card phone
6) Put the qsb-firmware (file with the extension .qsb) in the folder sdfuse.
Here I have 2 problems: First, my device does not boot, so I cannot create/copy files. Seconly: I cannot find qsb-firmware.qsb anywhere...
@ Dead2: How did you go through these steps?

Zwartoog said:
I purchased the ROM from the Iranian site, and downloaded the other from the Russian forum. So now I have 2 ROMs:
65M TB2-X30F_S000015_160115_ROW_TO_TB2-X30F_S000016_160602_ROW_WCA72E4AB5.zip (Russian)
1.1G TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip (Iranian)
Click to expand...
Click to collapse
Great, thanks for sharing the firmware, I hope you and everyone else with a softbricked tablet can get it fixed now
I am sure some of those would be willing to donate a couple of bucks to you if they get theirs working again.
Zwartoog said:
3) Download Qualcomm HSUSB USB COM Drivers
(Note that you need to register and log in to needrom.com FIRST. Then click the link, but it will give an access error. Remove all in the URL after needrom.com (so go back to the main site), then go back to the download link, and it will work - the file is there.)
1) and 2) install pretty fine, but 3) is just a zip with a lot of drivers, no installer. I have no clue on how to install the proper driver...
Click to expand...
Click to collapse
Ok, I used a LenovoUsbDriver_v1.0.12.exe driver installer, and that includes the HSUSB drivers needed, and I can confirm that windows recognizes the tablet as being in HSUSB mode with those. Whether QFIL does I have not tested.
I got the driver package from here: www DOT teamandroiders DOT com/lenovo-usb-drivers-download/
Zwartoog said:
@ Dead2: How did you go through these steps?
Click to expand...
Click to collapse
After you get past installing the HSUSB driver, you are officially the one that has gotten furthest on this.
I will assist in any way I can, but I will not attempt flashing my own tablet until I actually need to

Dead2 said:
After you get past installing the HSUSB driver, you are officially the one that has gotten furthest on this.
Click to expand...
Click to collapse
We'll get this working
Dead2 said:
Ok, I used a LenovoUsbDriver_v1.0.12.exe driver installer, and that includes the HSUSB drivers needed, and I can confirm that windows recognizes the tablet as being in HSUSB mode with those. Whether QFIL does I have not tested.
Click to expand...
Click to collapse
I tried that one too, but to no avail When I try to execute the executable, it ask for administrator permission, and after that vanishes...
I am running Windows 8, 64 bit. You?
Other question: when is your tablet recognised by Windows? Also in Recovery Mode?
Thanks!

Great work so far guys ! I Will try tomorrow with The new information! Mine is rootet so dont look good for me :/
Zwartoog:
The russian site also have Big files (1gb)
You Saw Them ?

Andersbp said:
Great work so far guys ! I Will try tomorrow with The new information! Mine is rootet so dont look good for me :/
Zwartoog:
The russian site also have Big files (1gb)
You Saw Them ?
Click to expand...
Click to collapse
No, I have spent too many hours translating Farsi today, was quite happy to find this one easily accessible on the Russian site
Can you check one of the bigger files? Might come in handy if my version seems incompatible for some reason...

Zwartoog said:
No, I have spent too many hours translating Farsi today, was quite happy to find this one easily accessible on the Russian site
Can you check one of the bigger files? Might come in handy if my version seems incompatible for some reason...
Click to expand...
Click to collapse
Sure Will try tomorrow

Huge breakthrough
I now have a unrootet, unbricked and stable unit again!
First i followed this guide:
https://2.bp.blogspot.com/-YxnBnMMx7Xg/VnaiVim76VI/AAAAAAAAURo/pz5IiaVdlcQ/s320/qfil.jpg
But insted of this:
9. Now, enter your Lenovo Vibe P1 into recovery mode. you can do it by :
Press the Volume Up button and keep holding it while connecting it to the computer/laptop using USB cable.
Lenovo Vibe P1 will vibrate one time, and you will see black screen.
You need to hold in VOLUME UP AND VOLUME DOWN AND POWER button at same time. Until you see
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now you can continue with the guide, and use QFIL.
I used this firmware: https://drive.google.com/open?id=0B9affStJ4JQ1U3JXUTZFTDJ6NU0
Extract the rar file. Inside you will find the files needed in QFIL.
Hope this helps you guys

Andersbp said:
Huge breakthrough
I now have a unrootet, unbricked and stable unit again!
First i followed this guide:
https://2.bp.blogspot.com/-YxnBnMMx7Xg/VnaiVim76VI/AAAAAAAAURo/pz5IiaVdlcQ/s320/qfil.jpg
But insted of this:
9. Now, enter your Lenovo Vibe P1 into recovery mode. you can do it by :
Press the Volume Up button and keep holding it while connecting it to the computer/laptop using USB cable.
Lenovo Vibe P1 will vibrate one time, and you will see black screen.
You need to hold in VOLUME UP AND VOLUME DOWN AND POWER button at same time. Until you see
Now you can continue with the guide, and use QFIL.
I used this firmware: https://drive.google.com/open?id=0B9affStJ4JQ1U3JXUTZFTDJ6NU0
Extract the rar file. Inside you will find the files needed in QFIL.
Hope this helps you guys
Click to expand...
Click to collapse
Super! Will try this tonight. Just in case: which Windows version are you using?

Zwartoog said:
Super! Will try this tonight. Just in case: which Windows version are you using?
Click to expand...
Click to collapse
I use windows 10

Andersbp said:
Huge breakthrough
I now have a unrootet, unbricked and stable unit again!
Click to expand...
Click to collapse
Great work! I am glad I was able to help you guys get this fixed
Andersbp said:
You need to hold in VOLUME UP AND VOLUME DOWN AND POWER button at same time. Until you see
Click to expand...
Click to collapse
Yep, its at the bottom of my first post also, found that out by accident while trying to get into the normal recovery.
Now, hopefully someone will want to port TWRP and CM13 or Paranoid to this tablet

Doh i did not see that Dead2
Thanks everybody together we defeated the problem !

SUPER! Succes here as well! The trick was indeed to hold both vol UP and DOWN
Now: brand-new unrooted device
Thanks
Btw: I noticed that the rom from Andersbp is a TB2-X30L rather than the TB2-X30F. I used my F file (paid for it, dammit ), and that one also works well.
I am currently checking if I can modify the stock ROM to enable root / mult-user. Any hints?

Nice zwartoog !
I Can root with kingroot.. Are there better alternatives ? Kingroot is Full of bloatware

Andersbp said:
Nice zwartoog !
I Can root with kingroot.. Are there better alternatives ? Kingroot is Full of bloatware
Click to expand...
Click to collapse
Noo, no Kingroot. That's where all the disasters began. It is full of bloatware. Trying to uninstall Kingroot lead to bricking the device
Personally I am only interested in re-enabling the multi-user feature from lollipop. WHICH IS FOR SOME REASON DISABLED BY LENOVO Even when rooted and modifying the system/build.prop did not re-enable it.
I'm giving up now. At least I have a workable device. Restored pride. And more important: 3 happy kids

I think the TB2-X30L is the LTE version of the tablet, while the TB2-X30F is the wifi-only version. If correct, then there should be no problem
when using the LTE on a non-LTE model, but the other way around could potentially cause LTE to not work. The LTE firmware might have some
extra apps and settings enabled to cater to this ability, but it might also be completely identical. Btw, what does the model information say
after being flashed with the L firmware? In any case it is useful to know that they are cross-compatible, since sometimes there can be differences
in chipsets or screens that can cause minor or major problems.
As I mentioned earlier, another root alternative to kingroot seems to be vRoot, but I have not tried it myself. But now that it is possible to
recover a bricked tablet, it is also less risky to test such things.
BTW: Please remember to use the "Thanks!" button on posts you find helpful, I have tried to do so myself on the posts that I find helpful

A2017 4th category brick repair manual (when ZTE ... ... Interface DFU mode ony)

Hi folks!
I have great news for those of you who have bricked your devices completely and you don't have any possibility to apply this as a warranty case. By this I mean that your Axon 7 is not booting to system or any other possible modes except the DFU mode which detects by PC (Device Manager) as ZTE Handset Diagnostic Interface(DFU) (COM...). And neither any of the software tools nore Deep Flash cable didn't manage to help to unbrick it.
There is a solution! Please pay precise attention to each step and make sure that you are capabale of doing all the actions otherwise refer to a professionals to do the job!
Axon 7 restore manual from bricked conditions when only ZTE Handset Diagnostic Interface(DFU) (COM...) mode is detected
All actions you do at your own risk. If you are not sure that you can do it by yourself then refer to a professional!
Method description:
Device repair is performed with MiFlash tool with forcing the phone into EDL mode. To do that you will need to disassemble the phone and circuit the TEST-POINT. After that Windows Device Manager will detect your phone as Qualcomm HS-USB QDLoader 9008 (COM...).
Terms and Definitions:
Repair package – folder on PC that contains all necessary files to flash the phone with MiFlash tool in EDL mode.
4th category brick – phone status which does not allow to boot into next modes: Recovery, Fastboot, FTM, EDL. In Windows Device Manager the phone detects as ZTE Handset Diagnostic Interface(DFU) (COM...) whrn you connect it via USB cable. Any of possible manupulations give the same DFU mode (even when you force to install Qualcomm HS-USB QDLoader 9008, in reality it is still a DFU mode).
ATTENTION!!!
Considering that this method requires the phone dassasembling, please pay your attention to the teardown video and evaluate your capabilities of doing that. The build quality is good enough, so it will be quite a challenge to dissasemble it without parts damage, if you don't have experience and tools. The best way to do it is to give the phone to a specialit (preferable trusted one) along with this manual.
Special thanks to:
Stas13071992 - the first ever person who have found the TEST-point (critical spot for flashing).
djkuz - the guy who have helped to find this solution, created this manual and already helped to repair a bunch of bricks distantly.
brenic - guy who have collected required files to create Repair package.
Device teardown manual
Here you can see the complete teardown video from JerryRigEverything.
And then...
Major actions after body dismantle:
1. Disconnect ribbon cable of the finger print scanner.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Remove the screw with the silver bracket covering the extension ribbon cable.
3. Unclip all indicated connectors with plastic tool. Notice! The extension ribbon cable marked with green arrow (Main – going from type-c board to motherboard) has to be connected back during flashing!
4. Unscrew four screws of the motherboard.
5. Gently lift off the motherboard (it is held/glued with the thermal grease of the processor).
6. Detach signal antenna wire from the right side of the motherboard.
7. Unsnap the rear facing camera.
8. Here you go, the Test-point (marked with red arrow)! (do not forget to connect the extension ribbon cable back (going from type-c board to motherboard).
Repair process
First download Repair package with B13 firmware, Android 6.0 (for China models) A2017_B13_FULL_EDL_UNBRICK_DFU (mirror on yandex.disk). Unpack all the files to separate folder.
Second download and install Qualcomm drivers and MiFlash.
MiFlash manual.
1. Connect original USB Type-C cable to the phone.
2. Circtuit Test-point on the housing (there is sim-cards slot body nearby).
3. Connect USB cable to PC USB-port (preferably USB 2.0 version).
4. You will hear the USB device connection sound from PC (but you will not notice any vibration of the phone or red diode indicator blinking).
5. Make sure that Windows Device Manager have detected the phone as Qualcomm HS-USB QDLoader 9008 (on COM port). If it is not so or if it has detected an unknown device then make sure that you have installed Qualcomm drivers (even forced installation if required). You can release Test-point at this moment. Then disconnect USB cable from PC USB-port.
Repeat the procedure of Test-point circuiting on the housing to make sure that PC detects the phone as Qualcomm HS-USB QDLoader 9008 (COM...) in the Device Manager.
6. Circtuit Test-point on the housing again and hold it (do not release or brake this circuit)!
7. Run MiFlash on your PC, then specify the path to the firmware folder and push "Refresh" button. You should see the device detected in the program window.
8. Then push "Flash" button and the flashing process will begin. NOTICE: you should hold the Test-point cuircited until you see the sign "send configure command", then you can release Test-point circuit.
9. After flashing is completed you should re-assemble everything back and turn the device on.
10. If the device is turning on successfully then don’t forget to go to recovery mode and perform "Factory Reset" (because in userdata there can be some garbage that left from Android 7.1.1, it can interfere successful load to the system).
Here you can download this whole manual in English in MS Word format.
I'm sorry that some of the links are in Russian language since the content is located on 4PDA.ru forum. You can use translate.google.com to understand how to access the files. Or you can find the files with drivers and MiFlash somewhere else.
Good luck and be carefull with your devices!
Status: tested and works!!!

Thanks, I'm sure it'll help some people, but performing this when your phone has a software problem and you still have 3 years left of warranty seems a little crazy to me.

aLexzkter said:
Thanks, I'm sure it'll help some people, but performing this when your phone has a software problem and you still have 3 years left of warranty seems a little crazy to me.
Click to expand...
Click to collapse
Good point, but it mostly concerns chinese models when you buy the phone with no warranty.
Moreover, if you bricked you phone it is likely not a guarantee case.

Anyone define what "Circtuit" means?

gpz1100 said:
Anyone define what "Circtuit" means?
Click to expand...
Click to collapse
Like connect to housing, or body. Sorry for my bad English!

Vick78 said:
Like connect to housing, or body. Sorry for my bad English!
Click to expand...
Click to collapse
So connect to ground?

gpz1100 said:
So connect to ground?
Click to expand...
Click to collapse
Sounds more likely

Vick78 said:
Good point, but it mostly concerns chinese models when you buy the phone with no warranty.
Moreover, if you bricked you phone it is likely not a guarantee case.
Click to expand...
Click to collapse
If the phone is completely bricked how can they prove it was your fault?

aLexzkter said:
If the phone is completely bricked how can they prove it was your fault?
Click to expand...
Click to collapse
I think by default you can't brick the phone with locked bootloader, on the other hand if you have bricked the phone, you have unblocked bootloader. And this is not a guarantee case.
In reality, I know that Chinese shops from AliExpress will not even bother with any kind of investigation. As minimum they will replace motherboard, as maximum replace the phone, but they will charge some fee in any case.

Vick78 said:
First download Repair package with B13 firmware, Android 6.0 (for China models) [URL="https://mega.nz/#!0ghjXDQI!N-2-gbswn2QfrET8drrD-JCMScRJlAyOlpM2iP-
Click to expand...
Click to collapse
Okay, all doable, except this part. I have an A2017G. Does anyone know what the package consists of, i.e. what we have to flash instead? Is there any package for G, or does anyone know about a way to do it on non-chinese?

Choose an username... said:
Okay, all doable, except this part. I have an A2017G. Does anyone know what the package consists of, i.e. what we have to flash instead? Is there any package for G, or does anyone know about a way to do it on non-chinese?
Click to expand...
Click to collapse
I would say all the above except you'd use a European rom, specifically for the A2017G.
It should work if all the hardware is the same...

Choose an username... said:
Okay, all doable, except this part. I have an A2017G. Does anyone know what the package consists of, i.e. what we have to flash instead? Is there any package for G, or does anyone know about a way to do it on non-chinese?
Click to expand...
Click to collapse
A2017G_B10_FULL_EDL.zip
with aboot and fbop for unlock
https://mega.nz/#!ZhwR1BAD!PuIWa5Vivk3DxZ1Dgk-wAoITxiKmBiR-j1U8wZZidTw

djkuz said:
A2017G_B10_FULL_EDL.zip
with aboot and fbop for unlock
https://mega.nz/#!ZhwR1BAD!PuIWa5Vivk3DxZ1Dgk-wAoITxiKmBiR-j1U8wZZidTw
Click to expand...
Click to collapse
:fingers-crossed:
If this works I'll friggin donate to you, I swear

djkuz said:
A2017G_B10_FULL_EDL.zip
with aboot and fbop for unlock
https://mega.nz/#!ZhwR1BAD!PuIWa5Vivk3DxZ1Dgk-wAoITxiKmBiR-j1U8wZZidTw
Click to expand...
Click to collapse
I got to the send configure command but it's failing every time... i'm keeping the pin held there

Done! It's the most finicky process I ever made, what with the tiny copper contact and MiFlash flashing stuff only when it's on the mood. After around 30 tries and a successful flash of a zip I didn't have to flash, I managed to get to the configure command thing and left the short circuit there for 3 seconds more. after that it started flashing and I almost shat myself

Choose an username... said:
Done! It's the most finicky process I ever made, what with the tiny copper contact and MiFlash flashing stuff only when it's on the mood. After around 30 tries and a successful flash of a zip I didn't have to flash, I managed to get to the configure command thing and left the short circuit there for 3 seconds more. after that it started flashing and I almost shat myself
Click to expand...
Click to collapse
Did the phone come to life eventually?

djkuz said:
Did the phone come to life eventually?
Click to expand...
Click to collapse
Yeah, perfectly fine as of now. I noticed that the bootloader was not unlocked when on B10 (no The software can't be checked for corruption message) but it got unlocked after updating to official 7.1.1 B01 for some reason.

Choose an username... said:
Yeah, perfectly fine as of now. I noticed that the bootloader was not unlocked when on B10 (no The software can't be checked for corruption message) but it got unlocked after updating to official 7.1.1 B01 for some reason.
Click to expand...
Click to collapse
This message did not appear because in my B10 package I replaced aboot (used from the USA version of the phone B20). When installing firmware B01 7.1.1 aboot changes to the original and the message appears again!

So I'm trying to do this with my A2017g, but it only stay in com for like 3 seconds, then it's gone. I don't have the time to flash anything...
---------- Post added at 01:04 AM ---------- Previous post was at 12:47 AM ----------
I swear to god, if this work, I'm staying stock forever.

Okay, now this is annoying. is the EDL mode supposed to last 2 seconde, is there something really wrong with my phone ??? I don't have the time to flash anything before it dissapear ! I can't reach the "configure command" step...

Better Mobile App

welcome