Related
[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.
Good morning.
I got a problem yesterday with my LG L5 II Dual phone: I caught my sisters pressing any buttons on it and when I saw what they did, there was an Android image on it. Now, every time I try to boot it, it cannot finish the initial setup, saying "Unfortunately, LGSetupWizard stopped."
I've rooted this phone some time ago, but the root seems to have no effect now. For instance, I deleted the following apps:
- Facebook
- Twittter
- All of "TIM" resources ("TIM Recarga, TIM Música, TIM this, TIM that"); "TIM" is the mobile operator of my phone.
I tried to follow the steps described in this post: "[Tutorial] Flashing KDZ on LG L5 II (E455/E460) and other LG phones", but I can't get my phone detected under "Download Mode", what I accessed using (Vol Up) + (Vol Down) keys while booting the phone. Unfortunately, it couldn't be detected in any workaround provided by this guide.
When connected under "Download Mode", I see a device called "LGE AndroidNet USB Modem" under "Modems" category on Windows Device Manager. It seems to be the only mode my phone could be detected under this mode.
Playing around with it, I could access a "Recovery Mode" by (Vol Up) + (Quick Access) keys while booting up the phone. I tried to get some info about it and I could, at least, use it with ADB. But I have read-only access, not read-write anymore. Searching more trying to get an answer to "ADB Force Root Mode", I got some things to notice, like the file "default.prop" under the phone's root system.
This "default.prop" shows the following 6 first lines:
Code:
ro.secure=1
ro.allow.mock.location=0
persist.mtk.aee.aed=on
ro.debuggable=0
persist.sys.usb.config=charge_only
persist.service.acm.enable=0
which means, I think, the phone now isn't configured for USB debugging neither for system write permission.
What can I do to, at least, try to delete some files on it, specifically the 4 setup wizard ones, located at "/system/app/" under the names "LGSetupWizard_JB.apk", "LGSetupWizard_JB.odex", "SetupWizard.apk" and "SetupWizard.odex", since these are the ones which I'm dealing with?
Ah. I tried on computers running Windows 8.1 and Windows XP SP3. No luck.
(edit: 2014-04-02, 23:16 UTC -03:00)
I've playing around with ADB trying to run it with another mode. I don't know if this can help, but sending the phone to recovery mode using ADB
Code:
adb reboot recovery
I get an Android lying with a red triangle sign over it... Still searching for a procedure or an answer to fix the phone, but still with no luck.
[Solved] Guide to solve this kind of problem
After looking for a while on how to fix the problem either by trying to run an ADB shell as root either by flashin the ROM, I could figure another way to flash the original "TIM" rom for my phone instead of the one described on the topic "[Tutorial] Flashing KDZ on LG L5 II (E455/E460) and other LG phones". Here's the way out:
1. Downloading firmware KDZ Flash ROM
First, you have to download the original KDZ ROM for your phone. It can be found at the link below:
LG Optimus L5 II Firmware List
The ones for Brazilian users are described in the page. For TIM users, I suggest using firmware 33 BTM/TIM(BRAZIL), size 599.09 MiB.
Since my phone was sold by TIM, I can't tell about another mobile operators, like Claro, Oi, and VIVO.
2. Extracting a binary file from the KDZ Flash ROM
After that, you will need to extract the KDZ file using LGExtractor (and not DZExtractor).
You can download it from here as an autoextractor file: <4shared>. It will extract itself to C:\RecoverE455\Extract.
Put your KDZ file on an easy access folder. I will assume you will use C:\RecoverE455\ROM for this.
Launch an Administrator command line prompt, and run this command:
Code:
C:\RecoverE455\Extract\LGExtractor -kdz C:\RecoverE455\ROM\<KDZ-ROM-FileName>.kdz
Again, I assume you will put evertything under C:\RecoverE455.
Now, you have a cabinet (CAB) file in the same folder of your KDZ ROM. Extract it directly and you will get some structure similar to this:
DLL (folder)
LGE... (binary rom)
LGUP... (dll file)
3. Getting a most recent version of LGFlashTool
After this procedure, you will have to download LGFlashTool in order to flash you newly extracted BINARY rom.
You can download it from here as an autoextractor file: <4shared>. It will extract itself to C:\RecoverE455\Flasher.
Run the Setup program attached within it and it will install itself under the folder C:\LG\LGFlashTool. Overwrite the file MegaLock.dll under this folder with the one you just extracted in C:\RecoverE455\Flasher.
4. Install the correct LG Support Drivers for your E455 phone
Instead of installing the most recent version of LG Drivers provided by LG, you will install the following ones:
LG United Mobile Driver 3.8.1
LG Windows Mobile 1.0
LG SmartPhone DUN Modem Driver 1.0
They are packaged and you can download them from here as an autoextractor file: <4shared>. It will extract itself to C:\RecoverE455\Drivers. Install them in the order described above then restart your computer.
5. Put your phone under Download Mode
To do this, turn off your phone either directly either removing and reinserting the battery.
Plug the phone - WHILE TURNED OFF - on your computer by the USB cable.
Hold (Vol Up) + (Vol Down) and turn on the phone. Keep holding (Vol Up) + (Vol Down) until you see the line "==>Download mode" in bottom of the screen. If it doesn't appear, try until you get this.
6. Configuring your computer to flash under USB download mode
After plugging your device under Download Mode, open Windows Device Manager and search for some LGE AndroidNet USB Serial Port (COM##):
{
"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"
}
If it is not (COM41), you must set it to port (COM41). Set properties of the serial port, select tab "Port Settings", then click "Advanced":
Here, select (COM41) for COM number port.
7. Launch LGFlashTool and flashing
Open your newly modified LGFlashTool (yes, the one you downloaded here and replaced some DLL). It immediately will ask for your BINARY rom and a DLL:
Click the "..." button and select the LGUP***.DLL in the same folder as your .BIN file you extracted in step 2.
Click the "Add" button immediately below (side S/W box), then select the LGE***.BIN you extracted in step 2.
Click OK.
Click the serial port button --
--, and let this dialog be equal as this one, with only "16 ports\Port 1 ~ Port 16\1" marked:
And now click the forward button --
.
It will display READY on box with port COM41.
Disconnect your phone, turn it off, then turn it on under Download Mode as described on step 5.
If you manage to turn it on Download Mode without connecting to your computer, plug it back to the computer.
It will begin flashing by itself. No action needed.
DO NOT DISCONNECT YOUR PHONE. I DON'T KNOW WHAT MAY HAPPEN IF YOU DO SO, BUT PROBABLY YOU WILL BREAK DEFINITIVELY YOUR DEVICE.
After all, your phone will restart with all its original configuration and LGFlashTool will display an error. After you manage to finish LGSetupWizard on the phone, you may close everything.
Man, you are a HERO.
I was having trouble debranding and updating my phone, but with your tutorial, it was EASY! Now I have a debranded and updated phone (V10K).
MANY MANY MANY THANKS!!!
Again, I assume you will put evertything under C:\RecoverE455.
Now, you have a cabinet (CAB) file in the same folder of your KDZ ROM. Extract it directly and you will get some structure similar to this:
DLL (folder)
LGE... (binary rom)
LGUP... (dll file)
i couldn't find these, i've done instructions carefully ... help me pleasee !!! :crying:
reresatria said:
Again, I assume you will put evertything under C:\RecoverE455.
Now, you have a cabinet (CAB) file in the same folder of your KDZ ROM. Extract it directly and you will get some structure similar to this:
DLL (folder)
LGE... (binary rom)
LGUP... (dll file)
i couldn't find these, i've done instructions carefully ... help me pleasee !!! :crying:
Click to expand...
Click to collapse
solved :laugh: , just doin' little mistake ... thanks man for tutorial
Hi! I'm here again!
I'm trying to do everything again, but now in my new phone, a D685 (LG G Pro Lite Dual).
But, when I connect it in download mode, FlashTool give me an error just after "USB Connection established". No description of the error, just a "F0000002"...
You know how to solve this?
LG 455 IMEI Problem
Hi,
I flash my phone following this instructions a month ago, all gone ok but yesterday both sims come into negative band and i discover IMEIS changed. I try to rewrite imeis from back label under batteries by all the ways i know, but none works. The AT command method via engineer menu or Putty console responds OK but doesnt change anything; same thing with MTKTools.
The las chance, i think, its by meta mode imei an sn change tools, like Maui META or SN_STATION, but i cant enter the phone in meta mode or cant find the correct drivers; every times programs fail attemping to connect to phone...
Please if some know some clues make me know!!!!
niconiconico111 said:
Hi,
I flash my phone following this instructions a month ago, all gone ok but yesterday both sims come into negative band and i discover IMEIS changed. I try to rewrite imeis from back label under batteries by all the ways i know, but none works. The AT command method via engineer menu or Putty console responds OK but doesnt change anything; same thing with MTKTools.
The las chance, i think, its by meta mode imei an sn change tools, like Maui META or SN_STATION, but i cant enter the phone in meta mode or cant find the correct drivers; every times programs fail attemping to connect to phone...
Please if some know some clues make me know!!!!
Click to expand...
Click to collapse
The AT commands worked for me. In putty, be sure to get "IMEI changed" as response, and check the number. If I remember, the IMEI is comma seppareted.
[SOLVED]
romulocarlos said:
The AT commands worked for me. In putty, be sure to get "IMEI changed" as response, and check the number. If I remember, the IMEI is comma seppareted.
Click to expand...
Click to collapse
Hi, thanks for the reply!
Yes, finally the solution was simple, instead of using AT+EGMR command I use AT%IMEI=, that worked!!
can u solve it ?
romulocarlos said:
Hi! I'm here again!
I'm trying to do everything again, but now in my new phone, a D685 (LG G Pro Lite Dual).
But, when I connect it in download mode, FlashTool give me an error just after "USB Connection established". No description of the error, just a "F0000002"...
You know how to solve this?
Click to expand...
Click to collapse
hii, how about this problem ? have you solved it ? can u tell me how do it ... i've got same problem,
reresatria said:
hii, how about this problem ? have you solved it ? can u tell me how do it ... i've got same problem,
Click to expand...
Click to collapse
FlashTool can't work with this phone. Instead, search here on XDA about flashing KDZ larger than 1Gb. Is an offline method.
help
romulocarlos said:
FlashTool can't work with this phone. Instead, search here on XDA about flashing KDZ larger than 1Gb. Is an offline method.
Click to expand...
Click to collapse
thx for reply, i'm using L5 II E455 before i've tried your method about twice and it's work, but since i restart my phone and got an android laying with a red triangle over it, i can't flashing again, it got problem error F0000002 ...
goo(dot)gl/R43Jmj if you don't mind click the url
reresatria said:
thx for reply, i'm using L5 II E455 before i've tried your method about twice and it's work, but since i restart my phone and got an android laying with a red triangle over it, i can't flashing again, it got problem error F0000002 ...
goo(dot)gl/R43Jmj if you don't mind click the url
Click to expand...
Click to collapse
I'm sorry, I make a mistake. My answer above was for another thread.
This method works with E455, just check the drivers and everything else again, and if possible, use a clean computer.
Again, sorry for my mistake.
still can't
romulocarlos said:
I'm sorry, I make a mistake. My answer above was for another thread.
This method works with E455, just check the drivers and everything else again, and if possible, use a clean computer.
Again, sorry for my mistake.
Click to expand...
Click to collapse
still i can't flash my phone,
Thank you very much, I could not recover the phone all the time, the update always stuck to 4%. When this has helped me! Just when I launched the BAT extractor, it deleted all the contents of the parent folder.
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 !
Hi folks!
I have great news for those of you who have bricked your devices completely and you don't have any possibility to apply this as a warranty case. By this I mean that your Axon 7 is not booting to system or any other possible modes except the DFU mode which detects by PC (Device Manager) as ZTE Handset Diagnostic Interface(DFU) (COM...). And neither any of the software tools nore Deep Flash cable didn't manage to help to unbrick it.
There is a solution! Please pay precise attention to each step and make sure that you are capabale of doing all the actions otherwise refer to a professionals to do the job!
Axon 7 restore manual from bricked conditions when only ZTE Handset Diagnostic Interface(DFU) (COM...) mode is detected
All actions you do at your own risk. If you are not sure that you can do it by yourself then refer to a professional!
Method description:
Device repair is performed with MiFlash tool with forcing the phone into EDL mode. To do that you will need to disassemble the phone and circuit the TEST-POINT. After that Windows Device Manager will detect your phone as Qualcomm HS-USB QDLoader 9008 (COM...).
Terms and Definitions:
Repair package – folder on PC that contains all necessary files to flash the phone with MiFlash tool in EDL mode.
4th category brick – phone status which does not allow to boot into next modes: Recovery, Fastboot, FTM, EDL. In Windows Device Manager the phone detects as ZTE Handset Diagnostic Interface(DFU) (COM...) whrn you connect it via USB cable. Any of possible manupulations give the same DFU mode (even when you force to install Qualcomm HS-USB QDLoader 9008, in reality it is still a DFU mode).
ATTENTION!!!
Considering that this method requires the phone dassasembling, please pay your attention to the teardown video and evaluate your capabilities of doing that. The build quality is good enough, so it will be quite a challenge to dissasemble it without parts damage, if you don't have experience and tools. The best way to do it is to give the phone to a specialit (preferable trusted one) along with this manual.
Special thanks to:
Stas13071992 - the first ever person who have found the TEST-point (critical spot for flashing).
djkuz - the guy who have helped to find this solution, created this manual and already helped to repair a bunch of bricks distantly.
brenic - guy who have collected required files to create Repair package.
Device teardown manual
Here you can see the complete teardown video from JerryRigEverything.
And then...
Major actions after body dismantle:
1. Disconnect ribbon cable of the finger print scanner.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Remove the screw with the silver bracket covering the extension ribbon cable.
3. Unclip all indicated connectors with plastic tool. Notice! The extension ribbon cable marked with green arrow (Main – going from type-c board to motherboard) has to be connected back during flashing!
4. Unscrew four screws of the motherboard.
5. Gently lift off the motherboard (it is held/glued with the thermal grease of the processor).
6. Detach signal antenna wire from the right side of the motherboard.
7. Unsnap the rear facing camera.
8. Here you go, the Test-point (marked with red arrow)! (do not forget to connect the extension ribbon cable back (going from type-c board to motherboard).
Repair process
First download Repair package with B13 firmware, Android 6.0 (for China models) A2017_B13_FULL_EDL_UNBRICK_DFU (mirror on yandex.disk). Unpack all the files to separate folder.
Second download and install Qualcomm drivers and MiFlash.
MiFlash manual.
1. Connect original USB Type-C cable to the phone.
2. Circtuit Test-point on the housing (there is sim-cards slot body nearby).
3. Connect USB cable to PC USB-port (preferably USB 2.0 version).
4. You will hear the USB device connection sound from PC (but you will not notice any vibration of the phone or red diode indicator blinking).
5. Make sure that Windows Device Manager have detected the phone as Qualcomm HS-USB QDLoader 9008 (on COM port). If it is not so or if it has detected an unknown device then make sure that you have installed Qualcomm drivers (even forced installation if required). You can release Test-point at this moment. Then disconnect USB cable from PC USB-port.
Repeat the procedure of Test-point circuiting on the housing to make sure that PC detects the phone as Qualcomm HS-USB QDLoader 9008 (COM...) in the Device Manager.
6. Circtuit Test-point on the housing again and hold it (do not release or brake this circuit)!
7. Run MiFlash on your PC, then specify the path to the firmware folder and push "Refresh" button. You should see the device detected in the program window.
8. Then push "Flash" button and the flashing process will begin. NOTICE: you should hold the Test-point cuircited until you see the sign "send configure command", then you can release Test-point circuit.
9. After flashing is completed you should re-assemble everything back and turn the device on.
10. If the device is turning on successfully then don’t forget to go to recovery mode and perform "Factory Reset" (because in userdata there can be some garbage that left from Android 7.1.1, it can interfere successful load to the system).
Here you can download this whole manual in English in MS Word format.
I'm sorry that some of the links are in Russian language since the content is located on 4PDA.ru forum. You can use translate.google.com to understand how to access the files. Or you can find the files with drivers and MiFlash somewhere else.
Good luck and be carefull with your devices!
Status: tested and works!!!
Thanks, I'm sure it'll help some people, but performing this when your phone has a software problem and you still have 3 years left of warranty seems a little crazy to me.
aLexzkter said:
Thanks, I'm sure it'll help some people, but performing this when your phone has a software problem and you still have 3 years left of warranty seems a little crazy to me.
Click to expand...
Click to collapse
Good point, but it mostly concerns chinese models when you buy the phone with no warranty.
Moreover, if you bricked you phone it is likely not a guarantee case.
Anyone define what "Circtuit" means?
gpz1100 said:
Anyone define what "Circtuit" means?
Click to expand...
Click to collapse
Like connect to housing, or body. Sorry for my bad English!
Vick78 said:
Like connect to housing, or body. Sorry for my bad English!
Click to expand...
Click to collapse
So connect to ground?
gpz1100 said:
So connect to ground?
Click to expand...
Click to collapse
Sounds more likely
Vick78 said:
Good point, but it mostly concerns chinese models when you buy the phone with no warranty.
Moreover, if you bricked you phone it is likely not a guarantee case.
Click to expand...
Click to collapse
If the phone is completely bricked how can they prove it was your fault?
aLexzkter said:
If the phone is completely bricked how can they prove it was your fault?
Click to expand...
Click to collapse
I think by default you can't brick the phone with locked bootloader, on the other hand if you have bricked the phone, you have unblocked bootloader. And this is not a guarantee case.
In reality, I know that Chinese shops from AliExpress will not even bother with any kind of investigation. As minimum they will replace motherboard, as maximum replace the phone, but they will charge some fee in any case.
Vick78 said:
First download Repair package with B13 firmware, Android 6.0 (for China models) [URL="https://mega.nz/#!0ghjXDQI!N-2-gbswn2QfrET8drrD-JCMScRJlAyOlpM2iP-
Click to expand...
Click to collapse
Okay, all doable, except this part. I have an A2017G. Does anyone know what the package consists of, i.e. what we have to flash instead? Is there any package for G, or does anyone know about a way to do it on non-chinese?
Choose an username... said:
Okay, all doable, except this part. I have an A2017G. Does anyone know what the package consists of, i.e. what we have to flash instead? Is there any package for G, or does anyone know about a way to do it on non-chinese?
Click to expand...
Click to collapse
I would say all the above except you'd use a European rom, specifically for the A2017G.
It should work if all the hardware is the same...
Choose an username... said:
Okay, all doable, except this part. I have an A2017G. Does anyone know what the package consists of, i.e. what we have to flash instead? Is there any package for G, or does anyone know about a way to do it on non-chinese?
Click to expand...
Click to collapse
A2017G_B10_FULL_EDL.zip
with aboot and fbop for unlock
https://mega.nz/#!ZhwR1BAD!PuIWa5Vivk3DxZ1Dgk-wAoITxiKmBiR-j1U8wZZidTw
djkuz said:
A2017G_B10_FULL_EDL.zip
with aboot and fbop for unlock
https://mega.nz/#!ZhwR1BAD!PuIWa5Vivk3DxZ1Dgk-wAoITxiKmBiR-j1U8wZZidTw
Click to expand...
Click to collapse
:fingers-crossed:
If this works I'll friggin donate to you, I swear
djkuz said:
A2017G_B10_FULL_EDL.zip
with aboot and fbop for unlock
https://mega.nz/#!ZhwR1BAD!PuIWa5Vivk3DxZ1Dgk-wAoITxiKmBiR-j1U8wZZidTw
Click to expand...
Click to collapse
I got to the send configure command but it's failing every time... i'm keeping the pin held there
Done! It's the most finicky process I ever made, what with the tiny copper contact and MiFlash flashing stuff only when it's on the mood. After around 30 tries and a successful flash of a zip I didn't have to flash, I managed to get to the configure command thing and left the short circuit there for 3 seconds more. after that it started flashing and I almost shat myself
Choose an username... said:
Done! It's the most finicky process I ever made, what with the tiny copper contact and MiFlash flashing stuff only when it's on the mood. After around 30 tries and a successful flash of a zip I didn't have to flash, I managed to get to the configure command thing and left the short circuit there for 3 seconds more. after that it started flashing and I almost shat myself
Click to expand...
Click to collapse
Did the phone come to life eventually?
djkuz said:
Did the phone come to life eventually?
Click to expand...
Click to collapse
Yeah, perfectly fine as of now. I noticed that the bootloader was not unlocked when on B10 (no The software can't be checked for corruption message) but it got unlocked after updating to official 7.1.1 B01 for some reason.
Choose an username... said:
Yeah, perfectly fine as of now. I noticed that the bootloader was not unlocked when on B10 (no The software can't be checked for corruption message) but it got unlocked after updating to official 7.1.1 B01 for some reason.
Click to expand...
Click to collapse
This message did not appear because in my B10 package I replaced aboot (used from the USA version of the phone B20). When installing firmware B01 7.1.1 aboot changes to the original and the message appears again!
So I'm trying to do this with my A2017g, but it only stay in com for like 3 seconds, then it's gone. I don't have the time to flash anything...
---------- Post added at 01:04 AM ---------- Previous post was at 12:47 AM ----------
I swear to god, if this work, I'm staying stock forever.
Okay, now this is annoying. is the EDL mode supposed to last 2 seconde, is there something really wrong with my phone ??? I don't have the time to flash anything before it dissapear ! I can't reach the "configure command" step...
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.