Lenovo META mode - Android Q&A, Help & Troubleshooting

Lenovo META mode - Android Q&A, Help & Troubleshooting

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

Related

[GUIDE] How to 'unbrick' your Mediatek MT65xx

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:

[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.

[Q] QPST & MiFlash Issue on Lenovo K910

Ok.
If you're having problems regarding how quick COM/USB port changes, please read my solution on post 4
Story.
I bought this phone last week and he came with android 4.2.2
After 2 hours i was able to get the 4.4.2 rooted but then...
...i just installed s.th that i can´t remember that cracks my boot.img
The this is that 4.2.2 version had the bootloader cracked but the 4.4.2 hasn't. That means i can't push anything to solve my .img issue.
After a few searches i reach to htcmania witch they have 2 possible solutions for my problem. Here's the 1st and here's the 2nd.
Now.
After i spend to much time trying to install the drivers correctly (initially without success) my phone just died. I lost Lenovo logo and ended up with just a red light blinking. Witch i though...F&%K!!!
If there's anyone who ended up like me, here's the solution for a pseudo-dead-phone:
remove your battery disconecting the cable inside the phone
plug the phone into a PC through a usb cable
insert your battery back
voilá. phone back alive
Now that i was able to get lenovo logo back again...
... i need your help (Lenovo K910 fans or someone with a great idea )to understand something that's has been cracking my head.
How the hell should i put this in download mode?!
I mean. Each time i plug the usb cable into PC with the volume up pressed, the device manager was able to reach Lenovo_blabla_2008 (witch seams to be the correct port so that my phone communicate with PC) but after a brief moment it changes to lenovo_composite_adb_interface (and this one doesn't work).
Now the question itself:
When should i press and where to stop that happening?! Because when i start the phone with those keys combination the phone restarts twice and not just one.
Here is a picture with my phone in download mode.
I quickly press the download button but then the just just restarts and i loose the download mode
{
"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"
}
GRRRRR!!!!!!
Thanks

after more than 24h pretty helpfull :good:

Hey, same probleme no download mode...only for few seconds... No chance to force them

Solution and new problem
Well...
...after all these days without any success, today i must awake with a lamp over my head
Question: If our/mine problem regarding COM/USB port is the quickness that it changes to USB how can we slow it down?!
Answer: Plug an USB extension (big) between phone and PC and...voilá
Simple, isn't it?
Now i got another problem
Probably i made some mistake between step 7th & 8th on QPST tip for our K910 on HTCMania (you may use google translator to translate from spanish into your language, but english work better) and i ended with a complete black screen that doesn't respond to power button, no red light even if i unplug battery cable inside K910.
Any sugestion?!
Thanks

Here is a pic.
As you can see, device manager sees my port as QDLoader 9008 and it stays there.
QPST Configurator sees my port COM11 but doesn't recognize phone
and eMMC Software doens't connect on DW mode and it gives me that error

check this maybe usefull
Code:
http ://lefenbbs.lenovo.c om/forum.php?mod=viewthread&tid=179762&extra=page%3D1

hadi-dvb said:
check this maybe usefull
Code:
http ://lefenbbs.lenovo.c om/forum.php?mod=viewthread&tid=179762&extra=page%3D1
Click to expand...
Click to collapse
Thank you
But apart google translator work as bad as possible i believe from wht i've read (bad) this is how use QPST, not my last problem described.
Anyway, thanks again

@Crowds,
have you a blue LED then you press VolUP and plug in the USB cable?
I had no LED, nothing, no Red, no blue.
Here i get 2 PM's from Editl, he has tried me to help, without sucess.
Here i share:
Hi,
I do not want to intruding, but I saw that you have similar problem as I had. I still cannot post on Lenovo thread as I do not have 10 posts on xda.
Your message:
“Hello, now my phone Stuck on Lenovo logo and locked bootloader, too.
had 1431_-dev on it witch unlocked bootloader and recovery from 4pda (VIBEUI_V2.0_1431_6_DEV_K910_NK_W_66FC_RR) on it
Today i flash Recovery TWRP 2.7.1.2 on it, with success... all fine.
Boot in recovery and wipe all data to install 1433_4_ST_k910_246M" from the bbs forum on it.Vol + and -
after flash i clear Cache data again.. twrp reboot and now i stuck on lenovo logo and cant acces anything,fastboot says locked.
what can i do now?
Boot with Vol+- dont work and twrp boot wont work”
Possible resolution:
I had the same problem as you are just with different rom. I have flashed RUS_VIBEUI_V2.0_1433_4_ST_K910_WC97_RR with TWRP 2.7.1.2 using standard SDfuse method. After that I wanted to flash another rom. I have entered TWRP with boot to recovery option and wipe the system, dalvik and system cache.
Tried to flash new rom over sideload option build in the TWRP but phone returned bad checksums. Immediately after, I have rebooted phone and stuck onto Lenovo screen.
Boot with Vol- and power did work and twrp boot did not work either, tried so many times. I finally find on some forum that TWRP 2.7.1.2 have a bug and that if you want to enter TWRP 2.7.1.2 you need to hook your usb cable into the phone and then hold Vol +, Vol – and power together and then to plug usb cable to computer usb port then TWRP recovery will show up.
I have succeeded after few tries on one laptop with Win8.1 pro 64bit. One odd thing is that on that Laptop I had a Lenovo drivers installed but those drivers did not recognise phone that had just TWRP 2.7.1.2 recovery even if I had use that laptop for so many time to flash the phone over adb using SDfuse method.
On the end I used another laptop with Win7 HP 64bit with installed generic adb drivers to recognise phone with just TWRP 2.7.1.2 and pushed rom thru sideload and finally I revive my phone back to original state.
I am hoping that you can revive yours as well.
If you find this solution fix your problem, please post the link on xda.
Cheers.
Click to expand...
Click to collapse
Quote:
Originally Posted by gekkorist
Hello, thanks for your message... But dont work ((( reboot after few seconds, test in 3 different Workstations with XP, 7 and vista...
I have find similar procedure on one forum. Give a try, you do not have anything to lose.
"LED bootloop is it with blank screen and blue light LED? can't boot OS and can't go into recovery.
last time i once stuck in these condition. after some trial and error manage to go into fastboot by shut down the phone (hold power button for more than 10 seconds) and then hold vol + & - then connect cable to computer (or is it vol - only)
somehow i've experienced this kind of brick few month ago. my solution was:
1. turn off the phone using the PWR + VOL UP method.
2. press both Vol UP/DOWN while the phone still turned off and plug in the usb into the computer
3. you will feel the vibration.
4. while in computer it should detect and the phone will be in fastboot mode.
5. run adb command to either load the cwm or etc
i forgot what step i choosed that time but somehow i managed to flash back the system and revive the phone."
By the way, do you have or know where to download international rom VIBEROM_V1.0_1407_2_ST_K910 ?
Thanks. Cheers.
Click to expand...
Click to collapse
Now i search a support Center in China

gekkorist said:
@Crowds,
have you a blue LED then you press VolUP and plug in the USB cable?
I had no LED, nothing, no Red, no blue.
Here i get 2 PM's from Editl, he has tried me to help, without sucess.
Here i share:
Now i search a support Center in China
Click to expand...
Click to collapse
Hi @gekkorist
First of all thank you for your feedback :good: bad that one didn't came sooner :laugh:
I don't know if you're suffering exactly as i.
Like you, i don't have red, blue, yellow, orange, gfreen :laugh: plus...NO LOGO since my last step as explained on 4th post.
If you're stuck like i was (no leds but with lenovo logo) follow this BUT plug your phone with an USB extension like i've mentioned in 4th post. I´m pretty sure with this trick this will work on any PC despite OS used.
Regarding the solutions presented by @EdiTL both cases won't work cause this time i can't even turn on (?) my phone. This is very strange since if i plug in the usb cable pc recognizes that something is plugged but can't detect on QPST despite device manager recognizes COM port as QDLoader 9008

now i try with a 5 meter cable, same issue with short detect in 9008 and go after 2 seconds back to adb. no chance with qpst.

gekkorist said:
now i try with a 5 meter cable, same issue with short detect in 9008 and go after 2 seconds back to adb. no chance with qpst.
Click to expand...
Click to collapse
That is odd
It worked with me at 1st try...sorry

I got exacly same as you had... How the hek you got it succesfull???? I´v tryed your instructions so many times and nothing (( With XP x32 and Win7x64... But I don´t have win8 as you had... :S

ekkilm said:
I got exacly same as you had... How the hek you got it succesfull???? I´v tryed your instructions so many times and nothing (( With XP x32 and Win7x64... But I don´t have win8 as you had... :S
Click to expand...
Click to collapse
I'm convinced that WIN8 had nothing to do with it.
Everyone that i've talked to when i had my problema told me to put Win98 32 bits and i've managed with Win8 64 bits so...
Check my signature and follow everything without execption.
Like i wrote there it tool me 1 entire month!!!
...and unfortunately there's no other way, except...back to Lenovo and pay

Crowds said:
I'm convinced that WIN8 had nothing to do with it.
Everyone that i've talked to when i had my problema told me to put Win98 32 bits and i've managed with Win8 64 bits so...
Check my signature and follow everything without execption.
Like i wrote there it tool me 1 entire month!!!
...and unfortunately there's no other way, except...back to Lenovo and pay
Click to expand...
Click to collapse
So what I read your sadly history., your phone dosent regodnize it ether with battery? Did you get it succesful with or without battery? Cause I read HTCmania it is possible have succes without battery, is it true? In my case it has to be driver issue or driver signatures.... I downloaded win 8 x32 and will try it tomorrow without battery. Cause I quess my battery is empty. I regodnize that when I plug the microusb to the phone a little bit, the red light shows and I quess it will charge it a bit (~5min) and after that I plug the phone to the pc it shows qualcomm QDLodaer port not usb device. But It will discharge pretty fast and then pc regodnizes it as USBdevice. So what is my question is, Is it possible make that process without battery? Thank you, I really aprechiate your help.
P.s. Sorry my bad language, and one thing is sure. I wont send phone back in china. I´ll fight on my last day with this thing

ekkilm said:
So what I read your sadly history., your phone dosent regodnize it ether with battery? Did you get it succesful with or without battery? Cause I read HTCmania it is possible have succes without battery, is it true? In my case it has to be driver issue or driver signatures.... I downloaded win 8 x32 and will try it tomorrow without battery. Cause I quess my battery is empty. I regodnize that when I plug the microusb to the phone a little bit, the red light shows and I quess it will charge it a bit (~5min) and after that I plug the phone to the pc it shows qualcomm QDLodaer port not usb device. But It will discharge pretty fast and then pc regodnizes it as USBdevice. So what is my question is, Is it possible make that process without battery? Thank you, I really aprechiate your help.
P.s. Sorry my bad language, and one thing is sure. I wont send phone back in china. I´ll fight on my last day with this thing
Click to expand...
Click to collapse
Be sure that you install the correct drivers for COM port accordly to your OS.
And yes. I played so many times with my phone trying to get back alive that I ended with an empty battery (post #6 on my thread). By that time I had to remove the battery till all process is completed and restart the phone.
Like I said it took me 1 month until I was able to do with and like you one thing was sure...I won't send it back either
Good luck...you gonna need it

Crowds said:
Be sure that you install the correct drivers for COM port accordly to your OS.
And yes. I played so many times with my phone trying to get back alive that I ended with an empty battery (post #6 on my thread). By that time I had to remove the battery till all process is completed and restart the phone.
Like I said it took me 1 month until I was able to do with and like you one thing was sure...I won't send it back either
Good luck...you gonna need it
Click to expand...
Click to collapse
That your story gives me so much hope and that spark to not give up. Like I told you earlier, if I some miracle get that phone back in business I'll bye you a BEER!

Crowds said:
Ok.
If you're having problems regarding how quick COM/USB port changes, please read my solution on post 4
Story.
I bought this phone last week and he came with android 4.2.2
After 2 hours i was able to get the 4.4.2 rooted but then...
...i just installed s.th that i can´t remember that cracks my boot.img
The this is that 4.2.2 version had the bootloader cracked but the 4.4.2 hasn't. That means i can't push anything to solve my .img issue.
After a few searches i reach to htcmania witch they have 2 possible solutions for my problem. Here's the 1st and here's the 2nd.
Now.
After i spend to much time trying to install the drivers correctly (initially without success) my phone just died. I lost Lenovo logo and ended up with just a red light blinking. Witch i though...F&%K!!!
If there's anyone who ended up like me, here's the solution for a pseudo-dead-phone:
remove your battery disconecting the cable inside the phone
plug the phone into a PC through a usb cable
insert your battery back
voilá. phone back alive
Now that i was able to get lenovo logo back again...
... i need your help (Lenovo K910 fans or someone with a great idea )to understand something that's has been cracking my head.
How the hell should i put this in download mode?!
I mean. Each time i plug the usb cable into PC with the volume up pressed, the device manager was able to reach Lenovo_blabla_2008 (witch seams to be the correct port so that my phone communicate with PC) but after a brief moment it changes to lenovo_composite_adb_interface (and this one doesn't work).
Now the question itself:
When should i press and where to stop that happening?! Because when i start the phone with those keys combination the phone restarts twice and not just one.
Here is a picture with my phone in download mode.
I quickly press the download button but then the just just restarts and i loose the download mode
GRRRRR!!!!!!
Thanks
Click to expand...
Click to collapse
Hey. I did exacly what is in your instructions (recover k910) for prepare things . Can you explane why my device show as a port but in conf QPST it just hangs on half a way? Here is screen what I mean. And yes, I installed win 8. x64 but still that anoying broblem. This is why I ask this about you beacause your battery was also drained like mine. ( I plugged the phone to the pc battery unplugged.)
Tell me what was your magical touch secret.

ekkilm said:
Hey. I did exacly what is in your instructions (recover k910) for prepare things . Can you explane why my device show as a port but in conf QPST it just hangs on half a way? Here is screen what I mean. And yes, I installed win 8. x64 but still that anoying broblem. This is why I ask this about you beacause your battery was also drained like mine. ( I plugged the phone to the pc battery unplugged.)
Tell me what was your magical touch secret.
Click to expand...
Click to collapse
That's one the of anoying problems you'll find like i.
U had to be quick enough in order that QPST won't losse COM connection.
Most probably your QPST in that "midle way" disconnects as COM wright?
Well...keep tryng...i did it for one month

Crowds said:
That's one the of anoying problems you'll find like i.
U had to be quick enough in order that QPST won't losse COM connection.
Most probably your QPST in that "midle way" disconnects as COM wright?
Well...keep tryng...i did it for one month
Click to expand...
Click to collapse
I did this. 1. (Disable signining) Installed QPST, reboot/(Disable signining). 2. Plugged phone to pc, got port/QHSUSB Bulk-> updated drivers win7x64 folder, reboot/(Disable signining). 3.Installed Lenovo drivers, (Disable signining). 5. Unpacked rom C:\bin/..6. Change the flash_local. 7. Open that Device manager and QPST config. AND THIS IS THE PART WHEN I SEE MY PHONE AS HALF A WAY PORT. It won´t dissapear there. It just connects and hangs on the half way, if i do the rest of instructions i got just emmc QPST hanging "download" and will search the device... aaaaand the result is "device not found"...
Actually, when I connect the phone to the computer it will only appear as in the picture and stays there. I do not have a big old USB cable. Do I need it for that purpose?

[GUIDE][FIX][DISCUSSION] LG G3 Hard Brick Recovery

UPDATE: I have updated this post with a file named "board diag v2.99.zip" This should now support more phones!!!
Several people have been having issues with hard bricks and there are several posts with a bit of info about how to fix them but no simple instructions so I'm posting a (hopefully) fool proof guide to fixing your hard brick. Tested on windows 7 and windows 10.
First what is a hard brick? A hard brick is a phone that does not boot, or is stuck in a boot loop, or has a security error AND cannot access recovery or download mode.
Disclaimer: Your warranty is now void etc. I am not responsible etc. You have to open your phone to do this so it is a last resort. Read the entire tutorial before beginning!
Required Materials:
Bricked LG G3
Stock USB cable <-- or at least one that you know is good
a short thin but stiff wire to short pins
Qualcomm high speed usb drivers
BoardDiag by willcracker <-- other versions don't seem to work
The tot file of the rom that you were running. (not older not newer same version) You can find these easily on XDA or google but it varies depending on your software version
First you need to install the Qualcomm high speed usb drivers. Your phone will be detected as Qualcomm 9008 (COM) later on in the tutorial but you need these drivers. I will include the drivers in this post. If you are on a 64 bit system you will need to disable driver signing. Here is how:
Step 1. Open the Windows command prompt as “Run as Administrator”.
Step 2. Run
Code:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
Step 3. To finalize the process run
Code:
bcdedit -set TESTSIGNING ON
Step 4. Reboot and you’re done.
I have attached both the 32 bit version and the 64 bit version be sure to only use the 64bit one on 64bit and likewise only use the 32bit one on 32bit, you do not need both sets of drivers.
1. Open your phone and take out the battery. Remove the top half of the phone housing. You do not need to remove the bottom half by the usb. Also you don't need to remove the screw next to the camera. If you do remember that it is a different size so keep it separate.
2, You will see a big metal shield. You need to remove it. It is pretty easy just pry it off and it pops back into place when you are done.
3. Next you need to short the pins as shown in the following picture. While continuing to short the pins plug in your usb cable. You should hear windows detect the phone almost instantly. Keep shorting the pins for the count to 5 and then you can release the wire. See image below, ignore the ethernet connector.
{
"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. Now open device manager in windows and it should show your phone under com ports as Qualcomm 9008 (COM #). If it doesn't try the process over again. When it does work remember this number. It is going to be used later.
5. Now fire up BoardDiag by willcracker be sure to run it as administrator. It is in this post named willcracker.rar There are some pictures on how to flash with this app but I will describe it as well. First we are going to need to extract your tot file. This can take some time. Like 10 mintues on a decent PC. The app may look like it froze up but it is just thinking. When it is complete move on to the next step.
6. You need to tell the program the com port that you are using that we found earlier and the folder where you extracted the firmware to.
7. once you have extracted the firmware and set up the program with the correct port you need to Check "AP" and "EMMC" then press start. Be sure not to select any partitions or change any other options than the firmware directory and comport.
It should come back as PASS. If it throws an error about not being in dload mode you need to restart the shorting process. Hold the short for a bit longer this time.
8. Flash all of the partitions except for Cache, System, Userdata, and Sbl1. Sbl1 will be flashed later and causes the phone to reboot.
You can flash System, Userdata, and cache but it takes a really long time so I don't recommend it. It is better to get your phone into download mode and use LG flash tool to do a full restore.
9. Once you have finished flashing all of the partitions one after the other put in the battery and flash Sbl1. Your phone will now reboot and try to boot into android. If your system is messed up it wont. You will still be in a boot loop. But you should now be able to enter download mode and recovery.
10. Open up LG Flash Tool and flash your tot using Board DL mode. Everything you need at this point is in the following thread http://forum.xda-developers.com/spr...de-how-to-restore-sprint-lg-g3-ls990-t2852042
Hope that this helps, also if you find any problems or need help please post so I can update this post.
NOTES: If you get an error about a dll missing you need to download and install the following http://www.microsoft.com/en-us/download/details.aspx?id=5555
Also make sure that you use "B2 (MSM8974AC)" as the AP Chipset for the LG G3.

thanks a lot brother.... just one Q...where can I get the TOT file?

paragxx said:
thanks a lot brother.... just one Q...where can I get the TOT file?
Click to expand...
Click to collapse
I assume that you are using sprint ls990 if so here is are the latest tot files. ZV8 and ZV6 can be found here http://downloads.codefi.re/autoprime/LG/LG_G3/LS990 thank autoprime. The files are zipped just extract the zip and then do the process above.
ZV4 can be found here direct link. http://downloads.codefi.re/wolfgart/LG_G3/LS990/ZV4/LS990ZV4_04.51101.zip

Any chance this works on ATT D850?

For myself and the benefit of others, I'm just clarifying something. I've always understood there to be the "hard brick" and the "soft brick". The soft brick is what you describe above where your phone lights up but doesn't boot. A hard brick is where nothing lights up, and your phone doesn't respond at all.
If someone were to describe what you describe above, I'd say that's not a hard brick. There's hope for a soft brick but not a hard brick. Am I wrong, or have the terms morphed a bit in the past several years?

mjjcb said:
For myself and the benefit of others, I'm just clarifying something. I've always understood there to be the "hard brick" and the "soft brick". The soft brick is what you describe above where your phone lights up but doesn't boot. A hard brick is where nothing lights up, and your phone doesn't respond at all.
If someone were to describe what you describe above, I'd say that's not a hard brick. There's hope for a soft brick but not a hard brick. Am I wrong, or have the terms morphed a bit in the past several years?
Click to expand...
Click to collapse
I was always told that a soft brick could be repaired with either recovery or fastboot and that a hard brick was anything that you needed more tools to fix. But I guess that everyone's definition is different. Also This method works on any kind of brick as long as there isn't a hardware issue. No screen on, no power on etc.

BlackSportD said:
Any chance this works on ATT D850?
Click to expand...
Click to collapse
Sorry that I missed your post.... but yes this should work on all variations of the LG G3 as long as it has the points on the motherboard posted in the picture. I do know that the international dual sim version has different pins and I don't know those pins but ATT, Sprint, Verizon, should all work.

l33tlinuxh4x0r said:
Sorry that I missed your post.... but yes this should work on all variations of the LG G3 as long as it has the points on the motherboard posted in the picture. I do know that the international dual sim version has different pins and I don't know those pins but ATT, Sprint, Verizon, should all work.
Click to expand...
Click to collapse
hey, mine is F460K (snapdragon 805) APQ8084 and not msm8974. My device shows as Qualcomm HS-USB QDLoader 9008 (COM6) . I assume i dont need to sort wire as its sole purpose is to show the device as Qualcomm in Device manager.
I think i need to create a file under model like B2 (MSM8974AC) with 2nd_loader.hex etc. Can you help me on this or is it unnecessary ?
currently i get the error
No response from the device. Check PMIC first and if still boot problem, replace AP

Pannam said:
hey, mine is F460K (snapdragon 805) APQ8084 and not msm8974. My device shows as Qualcomm HS-USB QDLoader 9008 (COM6) . I assume i dont need to sort wire as its sole purpose is to show the device as Qualcomm in Device manager.
I think i need to create a file under model like B2 (MSM8974AC) with 2nd_loader.hex etc. Can you help me on this or is it unnecessary ?
currently i get the error
No response from the device. Check PMIC first and if still boot problem, replace AP
Click to expand...
Click to collapse
You are right about not needing to short the wire and also about needing the correct 2nd_loader.hex etc. However I don't know how to make those. Attached are some more models that I found online. Hope that this helps.

l33tlinuxh4x0r said:
You are right about not needing to short the wire and also about needing the correct 2nd_loader.hex etc. However I don't know how to make those. Attached are some more models that I found online. Hope that this helps.
Click to expand...
Click to collapse
Thanx man, but they dont show my chipset.

Pannam said:
Thanx man, but they dont show my chipset.
Click to expand...
Click to collapse
What phone do you have? This tutorial is for the LG G3 from what I just googled the chipset that you are looking for is the Samsung Galaxy Note 4?

l33tlinuxh4x0r said:
What phone do you have? This tutorial is for the LG G3 from what I just googled the chipset that you are looking for is the Samsung Galaxy Note 4?
Click to expand...
Click to collapse
this is my phone it is lg g3 but upgraded version. http://www.gsmarena.com/lg_g3_lte_a-6520.php

Pannam said:
this is my phone it is lg g3 but upgraded version. http://www.gsmarena.com/lg_g3_lte_a-6520.php
Click to expand...
Click to collapse
I don't know then. I know that this method works on the carrier versions of the lg g3 but people have had issues with other versions.

l33tlinuxh4x0r said:
Several people have been having issues with hard bricks and there are several posts with a bit of info about how to fix them but no simple instructions so I'm posting a (hopefully) fool proof guide to fixing your hard brick. Tested on windows 7 and windows 10.
First what is a hard brick? A hard brick is a phone that does not boot, or is stuck in a boot loop, or has a security error AND cannot access recovery or download mode.
Disclaimer: Your warranty is now void etc. I am not responsible etc. You have to open your phone to do this so it is a last resort. Read the entire tutorial before beginning!
Required Materials:
Bricked LG G3
Stock USB cable <-- or at least one that you know is good
a short thin but stiff wire to short pins
Qualcomm high speed usb drivers
BoardDiag by willcracker <-- other versions don't seem to work
The tot file of the rom that you were running. (not older not newer same version) You can find these easily on XDA or google but it varies depending on your software version
First you need to install the Qualcomm high speed usb drivers. Your phone will be detected as Qualcomm 9008 (COM) later on in the tutorial but you need these drivers. I will include the drivers in this post. If you are on a 64 bit system you will need to disable driver signing. Here is how:
Step 1. Open the Windows command promt as “Run as Administrator”.
Step 2. Run
Code:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
Step 3. To finalize the process run
Code:
bcdedit -set TESTSIGNING ON
Step 4. Reboot and you’re done.
I have attached both the 32 bit version and the 64 bit version be sure to only use the 64bit one on 64bit and likewise only use the 32bit one on 32bit, you do not need both sets of drivers.
1. Open your phone and take out the battery. Remove the top half of the phone housing. You do not need to remove the bottom half by the usb. Also you don't need to remove the screw next to the camera. If you do remember that it is a different size so keep it separate.
2, You will see a big metal shield. You need to remove it. It is pretty easy just pry it off and it pops back into place when you are done.
3. Next you need to short the pins as shown in the following picture. While continuing to short the pins plug in your usb cable. You should hear windows detect the phone almost instantly. Keep shorting the pins for the count to 5 and then you can release the wire. See image below, ignore the ethernet connector.
4. Now open device manager in windows and it should show your phone under com ports as Qualcomm 9008 (COM #). If it doesn't try the process over again. When it does work remember this number. It is going to be used later.
5. Now fire up BoardDiag by willcracker be sure to run it as administrator. It is in this post named willcracker.rar There are some pictures on how to flash with this app but I will describe it as well. First we are going to need to extract your tot file. This can take some time. Like 10 mintues on a decent PC. The app may look like it froze up but it is just thinking. When it is complete move on to the next step.
6. You need to tell the program the com port that you are using that we found earlier and the folder where you extracted the firmware to.
7. once you have extracted the firmware and set up the program with the correct port you need to Check "AP" and "EMMC" then press start. Be sure not to select any partitions or change any other options than the firmware directory and comport.
It should come back as PASS. If it throws an error about not being in dload mode you need to restart the shorting process. Hold the short for a bit longer this time.
8. Flash all of the partitions except for Cache, System, Userdata, and Sbl1. Sbl1 will be flashed later and causes the phone to reboot.
You can flash System, Userdata, and cache but it takes a really long time so I don't recommend it. It is better to get your phone into download mode and use LG flash tool to do a full restore.
9. Once you have finished flashing all of the partitions one after the other put in the battery and flash Sbl1. Your phone will now reboot and try to boot into android. If your system is messed up it wont. You will still be in a boot loop. But you should now be able to enter download mode and recovery.
10. Open up LG Flash Tool and flash your tot using Board DL mode. Everything you need at this point is in the following thread http://forum.xda-developers.com/spr...de-how-to-restore-sprint-lg-g3-ls990-t2852042
Hope that this helps, also if you find any problems or need help please post so I can update this post.
Click to expand...
Click to collapse
hi
i get the error
No response from the device. Check PMIC first and if still boot problem, replace AP
model ls740 volt
G2MLTE (MSM8926)
help

nemran said:
hi
i get the error
No response from the device. Check PMIC first and if still boot problem, replace AP
model ls740 volt
G2MLTE (MSM8926)
help
Click to expand...
Click to collapse
Sorry I don't have that device to test. This is confirmed on the carrier version of the LG G3 only.

Thank You
I found a post similar to this that no matter where I looked - I was always referred back to that post - which was written in poor english - no download links worked. I appreciate this post. Saved my ass.

EMMC test fail
using D855 16gb
any fix ??

zohaibkhan143 said:
EMMC test fail
using D855 16gb
any fix ??
Click to expand...
Click to collapse
I have never had that error myself but it means either that you are using the wrong firmware images or that you have a hardware issue.

l33tlinuxh4x0r said:
I have never had that error myself but it means either that you are using the wrong firmware images or that you have a hardware issue.
Click to expand...
Click to collapse
tot is correct. I think so its a hardware issue.. I need a medusa box for fix maybe its the last solution for my G3:crying:
LGD855AT-00-V10e-EUR-XX-JUL-08-2014-16G+0
using this tot. Is it fine ?

l33tlinuxh4x0r said:
Several people have been having issues with hard bricks and there are several posts with a bit of info about how to fix them but no simple instructions so I'm posting a (hopefully) fool proof guide to fixing your hard brick. Tested on windows 7 and windows 10.
First what is a hard brick? A hard brick is a phone that does not boot, or is stuck in a boot loop, or has a security error AND cannot access recovery or download mode.
Disclaimer: Your warranty is now void etc. I am not responsible etc. You have to open your phone to do this so it is a last resort. Read the entire tutorial before beginning!
Required Materials:
Bricked LG G3
Stock USB cable <-- or at least one that you know is good
a short thin but stiff wire to short pins
Qualcomm high speed usb drivers
BoardDiag by willcracker <-- other versions don't seem to work
The tot file of the rom that you were running. (not older not newer same version) You can find these easily on XDA or google but it varies depending on your software version
First you need to install the Qualcomm high speed usb drivers. Your phone will be detected as Qualcomm 9008 (COM) later on in the tutorial but you need these drivers. I will include the drivers in this post. If you are on a 64 bit system you will need to disable driver signing. Here is how:
Step 1. Open the Windows command promt as “Run as Administrator”.
Step 2. Run
Code:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
Step 3. To finalize the process run
Code:
bcdedit -set TESTSIGNING ON
Step 4. Reboot and you’re done.
I have attached both the 32 bit version and the 64 bit version be sure to only use the 64bit one on 64bit and likewise only use the 32bit one on 32bit, you do not need both sets of drivers.
1. Open your phone and take out the battery. Remove the top half of the phone housing. You do not need to remove the bottom half by the usb. Also you don't need to remove the screw next to the camera. If you do remember that it is a different size so keep it separate.
2, You will see a big metal shield. You need to remove it. It is pretty easy just pry it off and it pops back into place when you are done.
3. Next you need to short the pins as shown in the following picture. While continuing to short the pins plug in your usb cable. You should hear windows detect the phone almost instantly. Keep shorting the pins for the count to 5 and then you can release the wire. See image below, ignore the ethernet connector.
4. Now open device manager in windows and it should show your phone under com ports as Qualcomm 9008 (COM #). If it doesn't try the process over again. When it does work remember this number. It is going to be used later.
5. Now fire up BoardDiag by willcracker be sure to run it as administrator. It is in this post named willcracker.rar There are some pictures on how to flash with this app but I will describe it as well. First we are going to need to extract your tot file. This can take some time. Like 10 mintues on a decent PC. The app may look like it froze up but it is just thinking. When it is complete move on to the next step.
6. You need to tell the program the com port that you are using that we found earlier and the folder where you extracted the firmware to.
7. once you have extracted the firmware and set up the program with the correct port you need to Check "AP" and "EMMC" then press start. Be sure not to select any partitions or change any other options than the firmware directory and comport.
It should come back as PASS. If it throws an error about not being in dload mode you need to restart the shorting process. Hold the short for a bit longer this time.
8. Flash all of the partitions except for Cache, System, Userdata, and Sbl1. Sbl1 will be flashed later and causes the phone to reboot.
You can flash System, Userdata, and cache but it takes a really long time so I don't recommend it. It is better to get your phone into download mode and use LG flash tool to do a full restore.
9. Once you have finished flashing all of the partitions one after the other put in the battery and flash Sbl1. Your phone will now reboot and try to boot into android. If your system is messed up it wont. You will still be in a boot loop. But you should now be able to enter download mode and recovery.
10. Open up LG Flash Tool and flash your tot using Board DL mode. Everything you need at this point is in the following thread http://forum.xda-developers.com/spr...de-how-to-restore-sprint-lg-g3-ls990-t2852042
Hope that this helps, also if you find any problems or need help please post so I can update this post.
Click to expand...
Click to collapse
I'm going to go insane. I'm stuck at doing the gnd and the capacitor. My laptop detects the device but it says devce not recognized. i installed the qualcomm high speed drivers you had in download on 32bit windows 7 and also tried on 64bit windows 8. Exact same thing, usb device not recognized. Also, I've installed the verizon lg g3 specific drivers and tried too but it doesnt work. Please HELP !

[GUIDE][G,U,Ch] DFU Unbrick Guide - Disassembly

DFU Unbricking Guide - When nothing else works

Heads-up: Now this guide is not the only way forward - EDL Tool has an integrated function to get out of DFU, and MultiDL (zte's tool) also works if you prefer MiFlash.
It is possible that you might still need to do a testpoint procedure to get into EDL.
Vick78 said:
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 manipulations give the same DFU mode (even when you force to install Qualcomm HS-USB QDLoader 9008, in reality it is still a DFU mode).
Click to expand...
Click to collapse
This guide is based off of @Vick78 's 4th Category Brick Repair Manual. I had to follow the guide in mid-April, and after doing it I realized that rewriting the thread would help all of us.
Please thank Vick78 on the other thread. I've been endlessly sending people there to fix their phones, and it works like a charm.
All of this is at your own risk, however obvious that may be... If you don't think you can make it, take it to someone experienced and show 'em this guide.
Patience is key! Be really careful when doing this, or you can break something inside and lose functionality. Flex cables are awful.
0) Know your Model:
Turn your phone around and see what model it is. If you screw up and flash another model's ROM you can lose your IMEIs.
In some cases (AliExpress) the phones come with A2017G software even though they are A2017 models. Just beware.
1) What you Need:
• A Windows PC with (preferrably) 64-bit support. Win7 will do, although Win10 may make stuff slightly easier. If it is a tower PC, use the rear USB ports, not the front ones!
• Your corresponding FULL_EDL package. Download it from @WesTD 's Latest Stock ROMs thread. (Thank him too! :good
• MiFlash. Get it from Yandex or Mega, same file. Thanks @djkuz for the link.
• Metal paper clip or needle to short circuit the test point.
• Tiny Phillips screwdriver or at least a knife, to get the screws off.
• Stock USB cable, or at least one that works good with data transfer.
2) Disassembly Video
JerryRigEverything made a full teardown video. Watch the teardown part a couple of times (up to 3:40) until you're familiar with the parts. You don't have to take the speakers or the USB-C module off though, just keep them there.
3) Teardown Hands-On
Images are also from Vick78's thread.
Make sure that the phone is completely off before starting! Also take the SIM card tray off before separating the screen from the back housing or you'll break something
a) Take the speaker grilles out by prying on the edges. You don't need a heat gun for this. Remove the black material to expose the screws, but be careful not to break it if possible, because it protects the speakers.
{
"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"
}
b) Remove all the screws and VERY CAREFULLY separate the screen from the back housing, to avoid breaking the FP sensor's flex cable. After that, disconnect the FP cable with your nail or some preferably non-conductive thing
c) Take the protective metal piece out, then disconnect the battery, USB-C and display/power connector, then get all those screws out. Put them somewhere so that you won't lose them (piece of tape, maybe a magnet).
d) Take the motherboard out and disconnect the antenna wire that's below it, on the lower part.
e) Disconnect the rear camera. Leave the front one connected.
And now you can see the TEST POINT that you have to short
f) Since the testpoint is in the back of the motherboard, and you need to have the battery and USB-C connected, I advice you to pry the battery off. You can rupture it very easily though. If you don't want to do it, don't worry, it is possible to make without taking it off, but you might break a flex cable and, honestly, it's much harder to hold the connection on the test point while the mobo is facing downwards.
If you will pry out the battery, be REALLY careful and don't force it.
g) Put the motherboard with the test point facing towards you. Connect the battery and the USB-C module to it, and the USB-C cable to the USB-C module (But NOT to the PC yet!). Be VERY GENTLE with the "little lego connectors" as I broke a couple of pins from the USB-C connector (It still works fully, I believe they have redundant pins in case someone like me screws up)
4) Connection to the PC
Before flashing, we need to make sure that the drivers are the correct ones.
- Open Device Manager (if on win10, right click on the start menu button and select device manager), find "Ports (COM & LPT)", and open it. Leave Device Manager open for now.
- Find an USB port on your PC that you can reach while you short circuit the test pad. If you have a desktop PC, it has to be one of the rear ports (NOT the front ports, those have a lot of interference) and they should be USB 2.0 if possible.
- Take the clip and connect the test pad to the big chunk of metal that's right beside it:
-Insert the USB cable (previously connected to the phone) to your PC's USB port.
-Watch Device Manager now. The phone should appear as "Qualcomm HS-USB QDLoader 9008". If it does, just go to the next point. If it doesn't, see if it is called "QUSB_BULK" under USB devices (This happens if you used Zadig). If this happens, find the QUSB_BULK device, right click, Uninstall device, Delete the driver software for this device. After that disconnect the cable from the PC, disconnect the battery, and connect it again; and redo the clip thing up to this point. The correct driver should install itself.
5) MiFlash
- Open MiFlash, keep it ready
- Unpack the FULL_EDL file to a folder with the same name, then open the folder and make sure that the files are directly there (i.e. they aren't inside another folder), put it somewhere, and select it from miflash ("select" button, select the folder).
- Hold the connection with the clip, as stated in the image above
- Click on Refresh from MiFlash, as soon as it detects a device hit "flash"
- If all goes well, it should say "send configure command". Wait 3 seconds and get the clip out. If it doesn't get to this part or if it fails, just disconnect it from the PC, disconnect the battery and reconnect it, and try again. Do this until it succeeds and it flashes. You might need to do this more than 5 times! If it doesn't work, try leaving the test pad connected for more or less time, like 2 seconds, 2.5 seconds, 3.5 seconds, 4 seconds... But 3 seconds works for most.
-If the flashing works, once it ends, go to the recovery and factory reset the phone. Otherwise there might be conflicting information in /data.

actually you don't need to open your phone. I was same situation and made a deepflash cable. it needs a little electronic ability and passion. you can enter edl mode with this method but it is too hard and you must be very patient.
I got edl mode one time but miflash didn't install correctly stock rom and couldn't again. @asderdd helped me and my device is okay now.

WesTD said:
actually you don't need to open your phone. I was same situation and made a deepflash cable. it needs a little electronic ability and passion. you can enter edl mode with this method but it is too hard and you must be very patient.
I got edl mode one time but miflash didn't install correctly stock rom and couldn't again. @asderdd helped me and my device is okay now.
Click to expand...
Click to collapse
The deep flash cable works only sometimes. I didn't try but most people bought a bunch of normal ones and they didn't work

@Choose an username... bro should I take out the daughter board (which held usb c port) too? what should I do about the usb c module u've mentioned above?

andrizmitnick said:
@Choose an username... bro should I take out the daughter board (which held usb c port) too? what should I do about the usb c module u've mentioned above?
Click to expand...
Click to collapse
It's not necessary, just taking out the board and the battery is usually enough. Be careful with the USB-C flex cable though, those are fragile

just my 2 cents here, better off getting cable like this
https://www.amazon.com/gp/product/B06XXCLMGM
bought one just to have one in any sort of emergency and even tested and works like a charm and is not just for ZTE devices but any snapdragon device out there....

Choose an username... said:
It's not necessary, just taking out the board and the battery is usually enough. Be careful with the USB-C flex cable though, those are fragile
Click to expand...
Click to collapse
I ended up taking out the daughter board, I got it working on my 2nd try. my axon is working fine now, thank u so much for the guide, really helpful for urgent situation like I had atm ?
edit: I forgot to ask, do u know any solution on how I can recovery my bootloader mode back? I already try flashing official rom from stock recovery but no luck.
DrakenFX said:
just my 2 cents here, better off getting cable like this
https://www.amazon.com/gp/product/B06XXCLMGM
bought one just to have one in any sort of emergency and even tested and works like a charm and is not just for ZTE devices but any snapdragon device out there....
Click to expand...
Click to collapse
i'm too lazy to wait, so today i'm following this guide and it's a success. thanks btw for the link, gonna order it next week for future needs

Will try this, my Axon 7 is still bricked af. Can't boot into Recovery, Bootloader, System or anything else without Reboots. Hope this Guide does the Trick...

Miustone said:
Will try this, my Axon 7 is still bricked af. Can't boot into Recovery, Bootloader, System or anything else without Reboots. Hope this Guide does the Trick...
Click to expand...
Click to collapse
And? Did you manage to pull it back together?

I have my Axon 7 since March 2017. After a month of owning it, when Android 7.0 was released, I rushed to flash a chinese rom. The result, a nice brick.
I tried with 3 EDL cables and shorting that pin, many many times. No luck. So back then I decided to put the phone back in its box, forget about it and move on. So eventually I purchased a new phone, wich I hated so much because it was more expensive than the Axon 7 and lacked in every aspect. So I sold it as well, and bought another phone, which I loved, but again, lacked in comparison to the Axon 7, until I was mugged. So I remembered that I had an Axon 7 lying around in its box, and decided to search XDA for a solution. That's when I found this thread and I decided to try and revive the phone.
All can I say is thank you. You brought my beloved Axon 7 back to me.
Thank you so much.

Thanks for the Guide! Annoyed at myself for my bonehead move that got me here in the first place, no biggie though as I used to repair phones for a living. If was any good with solder, I'd contemplate sticking a dab on that pin and never worry about not getting into EDL Mode again. I really like this phone, but the crap they've pulled in making it a nightmare to tinker with has me not desiring to get another one ever. OnePlus will probably get my next dollar set cuz of how open they are currently.

Harmtan2 said:
Thanks for the Guide! Annoyed at myself for my bonehead move that got me here in the first place, no biggie though as I used to repair phones for a living. If was any good with solder, I'd contemplate sticking a dab on that pin and never worry about not getting into EDL Mode again. I really like this phone, but the crap they've pulled in making it a nightmare to tinker with has me not desiring to get another one ever. OnePlus will probably get my next dollar set cuz of how open they are currently.
Click to expand...
Click to collapse
i don't think that would be a good idea. your phone would probably ONLY enter EDL mode. But I thought seriously about soldering a pushbutton on it. thing is that if you somehow rip the pad off, your mobo is dead.

Thank you for this guide my phone is working on chinese rom now but the big problem is
i cant flash any thing now .
vol up + pwr then the fastboot keep restart
vol up + vol down + pwr send me to dfu mode
vol down + pwr send me to ftm mode and when i send (( adb reboot edl )) i get qualcomm usb but mi flash keep say (( can't receive hello packet )) i tried many many times with 3 versions of mi flash but nothing works
please help me i cant live with chinese rom .

Reyad_W_K said:
Thank you for this guide my phone is working on chinese rom now but the big problem is
i cant flash any thing now .
vol up + pwr then the fastboot keep restart
vol up + vol down + pwr send me to dfu mode
vol down + pwr send me to ftm mode and when i send (( adb reboot edl )) i get qualcomm usb but mi flash keep say (( can't receive hello packet )) i tried many many times with 3 versions of mi flash but nothing works
please help me i cant live with chinese rom .
Click to expand...
Click to collapse
Try Flashing with the Axon 7 EDL Tool. The problem can also be the EDL package you are trying to flash. Try now a different one. If you can get to EDL mode, then it should work.

Woke up today to see my phone not turning on. Having troubles booting up and when I choose to go to recovery or fastboot through the unlocked bootloader warning menu it just bootloops. I connect my phone to my PC and it is already showing the "Qualcomm HS-USB QDLoader 9008" in device manager. Do I still need to open my phone and do the paper clip test in Step 4? Or can I continue on with the rest of the guide?

Hylex said:
Woke up today to see my phone not turning on. Having troubles booting up and when I choose to go to recovery or fastboot through the unlocked bootloader warning menu it just bootloops. I connect my phone to my PC and it is already showing the "Qualcomm HS-USB QDLoader 9008" in device manager. Do I still need to open my phone and do the paper clip test in Step 4? Or can I continue on with the rest of the guide?
Click to expand...
Click to collapse
You should be able to just connect and do the final part. As long as your emmc is all right, of course

Thanks for the quick reply. Heh, how often is flash storage failing a problem with other users? =X

Hylex said:
Thanks for the quick reply. Heh, how often is flash storage failing a problem with other users? =X
Click to expand...
Click to collapse
Maybe I've seen it once, but i'm on the q&a section all the time, so it's extremely rare. If it tries to boot then maybe it's just something much simpler

From FTM mode ( hold volume + and plug in USB cable) adb should be enabled. If the phone has a Qualcomm chip and Qualcomm drivers have been installed on your computer. Use "adb reboot edl" to reboot the phone into edl / Qualcomm 9008 mode. No need for cables or tearing the phone apart. This does not work on every phone.
Sent from my SM-G935V using Tapatalk

Choose an username... said:
You should be able to just connect and do the final part. As long as your emmc is all right, of course
Click to expand...
Click to collapse
Successfully flashed B35 EDL. Phone is unresponsive to any power or volume key presses. MicroSD card is removed. Still no cigar. Can't get the phone to be recognized as EDL mode anymore either. Phone detected with different USB port for EDL. Flashed again. Still nothing. Any suggestions? I still have the option of taking the phone apart, but that is a last resort if that makes the ability to RMA void.
I can feel the phone warming up when I plug it into a charger. That's the only sign of life I see in the phone.

Better Mobile App

welcome