Develop Bugs

[GUIDE][SOLUTION]MediaTek SPFlashTool failure - Disconnect after 2 sec is by design!

Hey everyone
This mostly applies to those of us that have a bricked MediaTek device. Yes the ones amongst us that are the most desperate I am sorry to say. Some of you laugh at that cause your Flashing experience has worked perfectly from the get go and you have flashed successfully with functioning device. Well that's great. Good for you! You're awesome. Sooner or later you are going to make a mistake and panic is going to set in and you will be where I have been. I am sorry to say that is not a very nice place.
For me it was not my device which makes matters worse. I was translating a device for an older gentleman who purchased it from Alibaba; it's an MTK6589 device to be precise.
Anyway I am sure a lot of you out there are frustrated with why your device is doesn't work with SPFlashTool even though you have been following the most of the tutorials to a T? Why your device disconnects from device manager 2 seconds after you plug the thing in and it disappears out of the device list? Like WTF right? Well would you look at me strangely if I said that this is actually by design? That yup your MediaTek device is actually meant to do that?!
If you have experienced this, then I have answers for you and I have an explanation as to why your MediaTek device is doing this, and why your device has not been able to be flashed by SPFlashTool.
Really we are our own worst enemy when it comes to this MediaTek woes; Why? Cause we are impatient and we go off looking for answers in the wrong direction when in fact they are right in front of us all along. Here I will hopefully expand your understanding about these devices and why/how things work so that you can apply it in the future.
I will explain my situation and what I discovered in the process. Hopefully it sheds some light on disconnect device driver situations and lays some thing to rest....hey maybe even some of you who had given up and tossed your cheapo China phone in the bedside draw cause nothing worked and it wasn't worth the price to send back, maybe you guys might want to give this a go and revive your MediaTek device?
Follow this guide step by step BUT READ EVERY STEP EVER SO CAREFULLY.... also take note of the points below that I am going to emphasise that AREN'T emphasised anywhere in this tutorial nor any other tutorials I have followed, so pay attention.
http://forum.xda-developers.com/showthread.php?t=1982587
The part that is not emphasised is this
Turn off your phone, remove the battery and replace it after some seconds (and don't turn on the phone).
Press F9 (or hit Download button) and connect your phone into the computer via USB data cable.
The process will start and a red progress bar will appear.
Click to expand...
Click to collapse
In both cases the word 'and' should be replaced with the word 'THEN' so that people will understand.
What isn't really mentioned on any tutorials is that the MTK6589 is different to how you flash other mediatek devices with SPFlashTool; why? Because you MUST put the battery back in before you flash unlike other MTK devices where they explicitly say DO NOT put it in and/or that you should flash without the battery in place. THIS IS INCORRECT!
Next thing to emphasise is this: You must have the phone disconnected when you click on the download button inside SPFlashTool. You press download then you put the battery back in your phone with the USB connected to the phone., wait and when the download part finishes (only a few seconds) THEN you plug the phone in to the computer (yes with the battery still in place) but do not switch the phone on.
When the phone is detected by Windows and starts to load the drivers like it usually does and then disconnects...well what happens now is that when it loads drivers for a second SPFLashTool engages the phone and holds open the connection. It will pause for a couple of seconds (but you will notice it doesn't disconnect) and then SPFlashTool will show a red/orange progress bar that goes quickly....then it will write the firmware when you see the yellow progress bar.
Something to note here (I downloaded literally hundreds of drivers by the way) that you only need 1 driver and that is the one mentioned in the tutorial.
You don't need to do all the bullsh!t with device manager and removing drivers etc with USBDview....this should only be if the phone doesn't read initially as MTK65xx preloader OR doesn't end up registering as MediaTek DA USB VCOM.
So I will explain...when you plug it in on a clean WIndows 7 PC for he first time it will appear as MTK65xx preloader under device manager under unknown device and Windows will attempt to download the correct drivers and then fail. This is normal.
DO NOT GO AND INSTALL PDANET DRIVERS!!! This doesn't work.
Yes the drivers ARE more stable and don't disconnect nearly as much as the other MediTek drivers, however what this does is register the devices as an Android ADB device, and allows you to use ADB. We want to use SPFlashTool, not ADB at the moment.
Installing other MediaTek drivers after PDANet for some reason causes a conflict and interferes with communication with the device?? I suspect that this is what was causing much of the issues I was experiencing? You may use the PDANet drivers after you have flashed via SPFlashTool if you cannot get an ADB connection, however in my case once the new firmware was written to the device and it was restored and fully functional; when I plugged it in the ADB drivers loaded automatically anyway
Ok next points to make. Unplug your device. Install the drivers (I have attached the ones that worked for me). NOTE: You may need to log in allowing unsigned drivers as mentioned in other tutorials. To do this you can use EasyBCD, go into advanced settings for the Windows 7 bootmenu entry and allow the use of unsigned drivers and put a wait of say 10seconds on the menu count down (in stock form Windows has assigned 30 seconds but standard it bypasses the boot menu - this makes it harder to press the F8 key during boot up). After finishing in EasyBCD reboot and when you come to the Windows boot menu press F8 anyway and choose allow use of unsigned drivers. This is a just in case thing.
Get EasyBCD from HERE
Once in Windows, plug in your device WITH THE BATTERY IN and device switched off. Open Windows device manager (a quick way is type devmgmt.msc in Start menu or Run menu from the start menu - if you search for the management console by full file name you can right click the devmgmt.msc and pin it to the Start menu this is what I have done).
In device manager you NEED to see the device registered as MediaTek DA USB VCOM. If it is not appearing push the volume up button + but keep the phone OFF. When it appears for just a second make sure it is MediaTek DA USB VCOM. *This is important* It must NOT be registered as Preloader or any other MediaTek driver ie. Preloader USB VCOM port OR MediaTek USB VCOM (Android) etc. IT MUST BE MediaTek DA USB VCOM Just look for the one that has DA in the name and is a VCOM driver. This is the driver we want:good:
Ok here is where I will mention that USBDview removal of drivers is not necessary and does absolutely nothing anyway because Windows 7 remembers every single driver you have installed regardless of the fact that you have removed/uninstalled and even checked the box delete drivers or what ever. It doesn't matter...every driver you have ever tried will be in the device driver list. USBDview is only good for unregistering the device association with a registered driver. It doesn't remove drivers.
So now where was I? Ahh right, yep. When you plug in your device (switched off and the battery in place) and it appears momentarily in device manager it must be MediaTek DA USB VCOM, If not Or if it disappeared too fast; just push the volume up button again and this time as it appears quickly, click to expand the (PORTS COM &LPT) listing, then quickly right click the MediaTek listing and go to Update Driver Software. You may need to do this several times to get it. Unplugging the USB from the PC and plugging it back in again may help.
Resist the urge to search for new drivers as the device IS actually detected but not as a PORTS COM &LPT, and doing so will be fruitless as you will only assign the incorrect drivers to the incorrect function. So unplug and replug it in again pressing volume up.
Note: It does not matter if the device disconnects and disappears out of Device Manager when you are in the Upgrade Device Driver software menu....this is normal. The most important point here is that the correct driver is being registered to the correct device protocol (pressing the volume up button to get COM&LPT).
The device needs to appear as MediaTek DA USB VCOM and this must be registered specifically to the (PORTS COM &LPT) in device manager. If it lists elsewhere as a USB device and has the MediaTek DA USB VCOM driver assigned to it, then you need to uninstall the driver from the device listing and start again. Don't go looking for more drivers PLEASE!
Click for explanation
Ok I will digress again for a moment to explain why all this is so important and what many of us are not realising especially with all the tutorials around; the important point here is that MediaTek devices may be listed many numerous devices in device manager and this is normal. They could be an ADB android device, a MediaTek USB Port version etc and these are not the functions we want to use for flashing with SPFlashTool are they? I know when I plug in my Galaxy S3 it loads at least 5 different drivers! Same with these devices.
We need to have the (PORTS COM &LPT) registered as MediaTek DA USB VCOM and this ONLY achieved when we press the volume up button!! If the device disappears from the list after plugging it in and appears as something else and then we register the MediaTek DA USB VCOM driver to this function we are likely trying to use the MediaTek DA USB VCOM driver to load the MediaTek USB Port function and this is obviously NOT the protocol that SPFlashTool is using to communicate with the device to write new firmware.
Ok I will continue now, once you have got into the Upgrade Driver Software menu,
Go to 'Browse my computer for device software',
Then select the second option 'Let me pick from a list of device drivers on my computer', just choose the 'show all' at the top of the list
Next you *should* see MediaTek DA USB VCOM listed in amongst various MediaTek drivers., select this one.
* However if you do not see MediaTek DA USB VCOM listed in the list there then uncheck the box next to 'Show compatible drivers' and it should now show a few more drivers.
You may need to scroll in the right menu bar down to MediaTek.
You will be hit with an overwhelming list of MediaTek drivers! See Pic for reference
Select the required MediaTek DA USB VCOM driver from the list. If its not there (then and only then) you should try install another set of drivers and restart the process again. Try the drivers I have attached below first though.
At this point please resist the urge to click 'Have disk' then 'Browse' to and go scouting for a specific driver in the hopes that this will be the one; THIS IS WRONG! and should not be recommended like it is in just about every tutorial I have seen so far.
{
"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"
}
It's funny how even the drivers you previously removed are included in that list eh? You know...the ones that everyone told you, you need to delete bla bla bla...THEY ARE STILL THERE DAMN IT!
Once you have selected the driver as MediaTek DA USB VCOM and closed out of the menu you will notice that it has actually gone from the list in device manager? This is normal. The driver is only meant to appear when we do a specific thing and that is pressing the volume up button to write firmware using SPFlashTool and nothing else.
As I mentioned earlier, this is by design. You will note that MediaTek devices, have these protocols USB Mass Storage, MTP, PTP, ADB and COM &LPT.
Now unplug your device. I would at this point do a reboot of Windows (again ensuring unsigned drivers by pressing F8 - just incase)
Once you're back inside Windows, open device manager again.
Keep the device off and have the battery in.
Plug the MicroUSB end into the device first (it's easier - trust me you will understand when I explain).
Now keeping it switched off but press and hold the the volume up button and then plug the cable into the PC USB port; watch as it registers inside device manager as MediaTek DA USB VCOM.
When it does, disconnect the cable from the USB port. - You are now good to go
Now Open SPFlashTool.
Select the scatter file.
Uncheck the following from the list (Preloader, MBR1, EBR1, Uboot, Sec_Ro, Logo, EBR2 and FAT - note fat is for the internal sdcard). We want to write to system, recovery and boot pretty much. If you have ruined your device with the incorrect preloader,
Keep the device UNplugged. Click the download button. You will see the purple progress bar but for only a very brief moment. This is ok and is normal.
IF you have completely obliterated your device by flashing an incorrect preloader click below
I have been advised that you may need to first flash the Preloader, MB1, EBR1,Uboot and EBR2) to setup the partitioning again. The preloader I assume is similar to a PIT file for Samsung devices?
Now we do as we did before. Plug the MicroUSB end in first to your device. Have it switched off but with the battery in place. Press and hold the volume up + button and then plug the cable in to the PC USB port again.
At this point you will hear the device register with Windows as you normally would however you should notice that it doesn't disconnect straight away like it normally does?
This is because the MediaTek DA USB VCOM is registered to the PORTS COM &LPT and SPFlashTool is listening on this port.
Then shortly after progress with a Red/Orange bar.
It will pause for a what seems like a long time..... but please leave the device plugged in! [shouldn't be longer than 10min - if it is you've done something wrong, disconnect and do the process again and read making sure you understand every one of the points I have made in this post]
Once you see the yellow progress bar you can breath with relief.
Congratulations you have just revived your bricked device! :good:
Additional Info: After a reboot when you plug the device into the PC USB port again you should start to see Windows identify the extra protocols associated with your MediaTek device. I noted than this one I was working on appeared back as an MTP Portable device, also as an ADB Android device further up the list and as an MTK USB Port when the volume up button is pressed (I guess now Windows knows what it is it is assigning it a different driver?)

But what if it doesn't disappear? I have the problem with ZTE V967s that i cannot flash it (probably dead), because I have "ENABLE DRAM FAILED (4032)" issue.
This is probably because the phone cannot exit the VCOM status, it is visible under this state for many minutes in device manager. Do you have any ideas how to solve this problem?

How i unbricked my Lenovo K3 Note (MTK6752)
Hi,
First of all I am thanking God Jesus Christ for helping me find a solution.
My Lenovo K3 Note was hard bricked when i accidently unplugged it while sp flash tool was flashing the firmware. The screen was not at all lighting up(Not even boot logo). When battery is inside and press power button i could see a feable red colour light near the proximity sensor. When i connect my phone to PC without battery (As many sp flash tool procedures says us to remove battery and connect) , it was not at all being detected by pc. This was my condition..!!!
I searched tried a lot for 5 hrs.. Continously.. Yes literally..
At last I started my own experiments. I downloaded complete stock firmware. and loaded it to sp flashtools by selecting scatter file. I selected the format+download option in sp flash tools. I clicked download button in sp flashtool. Now sp flash tool is waiting for my phone to get connected.
I removed the battery of phone, then i pressed the volume buttons, power buttons etc.. to remove static charges if present (for 10 seconds). "Then i put the battery back to the phone. "
I connected the usb cable to phone ,keep pressed the volume up key, then the other end was connected to the computer. SP flashtool detected my phone and flashing started(Now i released volume up key press). Wait for sometime till flashing completed and we get OK pop up in sp flash tool. Wait for some 10 seconds . Dont remove phone from computer. Press and hold the power button for switching on the phone without removing from computer.
If screen doesnot light up, release the buttons, remove the phone from computer . Press the power button two three times(Dont hold). Now press and hold power button to switch ON your phone. Thank God and Be happy seeing your phone booting up. :laugh::laugh:

if cant non-removeable battery(0% battery) for mtk phone. what shoud i do? power + volup ??? or something

[TUTO] [STOCK ROM] How to unbrick HTC Desire 310 dual/uni SIM ?

(I am sorry if this is not the right location to post this tutorial)
(Remember that this will remain your own risk. Neither our page and the author of this article shall not be held liable for any damage to your device)​
What you need for this guide:
1. SP-FlashTool (version designed for our phone, please do not use another version!):
2. Stock ROM:
* UNI SIM
* DUAL SIM
3. Drivers
Step 1: Prepare for SP-FlashToo:
1. Create a new folder on the C: drive called SP-FlashTool. Extract the contents of the SP-FlashTool.
2. ROM folder searching in the archives of the Stock ROM -em (HTC Desire 310 blah blah blah -> UserMode -> ROM) and unpack it to the root folder of the SP-FlashTool.
{
"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"
}
Step 2: Install the drivers:
1. Turn off the phone. When it's off, connect the USB cable to the computer, but do not start the cell!
2. When the screen displays your battery charge level (percent) disconnect it.
3. Enter the Device Manager, select View, then Show hidden devices.
4. Other devices should appear MTK65XX Preloader, right-click on it and update the driver.
Step 3: Prepare for flashing:
1. Start flash_tool.exe with administrator rights.
2. Select Options and then Option ..., or press CTRL + O combinations.
3. Go to the Connection tab, and select the option: High Speed ​​and w / o battery.
4. Go to the tab and select the option Download DA DL All with checksum and exit from the options menu.
Step 4: Flashing:
1. Go to the Download tab.
2. Press the Download Agent and choose DA_SWSEC.bin.
3. Press the Scatter-loading and choose MT6582_scatter_1.01.862.1.txt for UNI SIM, and MT6582_scatter_1.00.1136.5.txt for DUAL SIM in the ROM folder and look forward to the appearance of the file list.
4. Under the name of the scatter-loading File drop-down menu, we have. We develop them and select Download Only.
5. Uncheck Preloader
Finally, it should look like this:
6. After checking that all is well done, press the button that says Download and green an arrow pointing down.
7. Turn off the phone and pull the batteries.
8. Connect the USB while holding the volume button is responsible for volume down! (VERY IMPORTANT!). When you begin to flash, you can let go of the button.
Wait patiently.
Congratulation, you have a new phone again
FAQ - OR DOES NOT WORK !! HOW TO REPAIR ?!
Q: I have a strange name for the internal memory!
A: So far I do not know what it may be due. The problem should not cause problems, it can only look bad from the point of aesthetic.
Q: It annoys me that error CID! You can delete it?
A: The Russians agreed that sometimes the only thing that can work is to enter the code # 243 # on the keypad. At the moment there is no other way.
Q: I can not install the drivers for Windows 8 / 8.1!
A: ANSWER
Q: I get an error IMEI / I can not send or receive calls / sms / I have no coverage at all!
A: All the problems come down to one reason: you have selected Preloader. There is as yet no solution.
Source

I have windows 8, will I be able to flash the drivers? :/

Error 2004
I am getting BROM ERROR : S_BROM_DOWNLOAD_DA_FAIL (2004). I tried different USB ports, 2.0 and 3.0 and different PCs(I also tried on Win XP with XP drivers). After I press download and connect the phone, SP-FlashTool won't "catch" the MediaTek PreLoader USB VCOM Port. It will disconnect and connect every 2 seconds, for 9 seconds, then it will give me that error.
If anyone has an idea of what can I do to fix this, please tell me.
EDIT: Solved by renaming "checksum.ini" to "checksum.old"

Jaskirat_Panjrath said:
I have windows 8, will I be able to flash the drivers? :/
Click to expand...
Click to collapse
You can try..

greenro said:
I am getting BROM ERROR : S_BROM_DOWNLOAD_DA_FAIL (2004). I tried different USB ports, 2.0 and 3.0 and different PCs(I also tried on Win XP with XP drivers). After I press download and connect the phone, SP-FlashTool won't "catch" the MediaTek PreLoader USB VCOM Port. It will disconnect and connect every 2 seconds, for 9 seconds, then it will give me that error.
If anyone has an idea of what can I do to fix this, please tell me.
Click to expand...
Click to collapse
I think it's you who contacted me in the blog, so it's work now, congrats

Yes
MalekJandali said:
You can try..
Click to expand...
Click to collapse
Yes, you will. I flashed with Windows 8.1 and it worked.

Rom request
Does anyone have this rom with build 1.00.401.4 or CWM for the same build?

I have succesfully installed the drivers on Windows 8.1 64bit (after a bit of hard work ), but when SPFTool starts downloading the Flash it gives out the error BROM-ERROR Download failed (4008). I have google it and it says it has something to do with the battery, but the battery is charged, the USB cable is OK, I have changed USB ports... What can I do to finish the flashing process? How can I fix this error? Thank you!

Need more help for htc desire 310
My htc desire 310 stuck with htc logo, and vibrate again and again.. This happened while flashing cmw ..after flashing complete its asking to reboot into recovery.. I just do that to check the cmw. But now it stuck with htc logo.. Cannot go for bootloader option or device default recovery mode.. And its rooted device.. Need help...

This is exactly why I want to flah it again... I bet you followed that Ishan guy's tutorial, right?
Sent from my SM-G386F using XDA Free mobile app

Help me to download one missing file which is System.
i want it for my HTC Desire 310 Dual Sim, i have downloaded the ROM and Database files individually except System.img (inside ROM folder).. am i ok without this file or i have to have this file? if this file is also required please inbox me that file
Thankx

Hi guys, its being ages for me to write a comment in the forum but this time was a must in order to thank MalekJandali for this "life saving" thread.
I ended up after following some instructions on how to make CWM recovery and bricked the phone!
After it successfully created the CWM it asked if i wanted to reboot in recovery mode so i pressed yes. After that the nightmare began , constant reboot every 2 seconds.
Following this thread brought the phone back to life but i would like to let you know that on the step where it says "Turn the phone off , pull out the battery and connect having the volume down pressed", the flash would not start and in device manager the MT65xx driver was going on and off every second. Tried the procedure from the beginning in order to reload drivers as said but to tell you the truth when the battery indicator was coming up and i disconnected the cable then in other devices there was no MT65xx preloader (nor at my very first try.).
So what i did was to pull out the battery and do the step of the flashing, as soon as the device manager showed the MT65xx i right clicked on it and followed the driver update procedure (manually! as the Win7 could not find any drivers).
Then on to the flashing step again just to find out that nothing was happening.... So i put the battery in the phone and tried once again and that did the trick!!!
Don't really no guys what went wrong really, was it my drivers? was it the phone? Anyway at the end i saved it with this wonderful thread!!
Thank you so much.

Need help
Dreamlander said:
Hi guys, its being ages for me to write a comment in the forum but this time was a must in order to thank MalekJandali for this "life saving" thread.
I ended up after following some instructions on how to make CWM recovery and bricked the phone!
After it successfully created the CWM it asked if i wanted to reboot in recovery mode so i pressed yes. After that the nightmare began , constant reboot every 2 seconds.
Following this thread brought the phone back to life but i would like to let you know that on the step where it says "Turn the phone off , pull out the battery and connect having the volume down pressed", the flash would not start and in device manager the MT65xx driver was going on and off every second. Tried the procedure from the beginning in order to reload drivers as said but to tell you the truth when the battery indicator was coming up and i disconnected the cable then in other devices there was no MT65xx preloader (nor at my very first try.).
So what i did was to pull out the battery and do the step of the flashing, as soon as the device manager showed the MT65xx i right clicked on it and followed the driver update procedure (manually! as the Win7 could not find any drivers).
Then on to the flashing step again just to find out that nothing was happening.... So i put the battery in the phone and tried once again and that did the trick!!!
Don't really no guys what went wrong really, was it my drivers? was it the phone? Anyway at the end i saved it with this wonderful thread!!
Thank you so much.
Click to expand...
Click to collapse
Hey man, Can you briefly explain the procedure? I have the same issue. Phone connects and reconnects every 2 seconds. I did CWM recovery and my phone into boot loop and after that i did something using sp flash tool and now it wont turn on. I have updated the drivers manually. How can I get out of this hole? Its my first experiment gone havoc. Any help would be appreciated? thanks in advance

after 2 weeks of doing this instruction with various results(e.g a bad headache :crying except any success :silly:, i achieved a great experience:
my computer's OS is win 8.1.
Run SP FlashTool in compatibility mode for windows 7!:cyclops:
Right click on .exe file and click on properties. then check the "run this program in compatibility mode for" and then select the windows 7.
Try it and save your phone and comback and knock the thanks maybe it heal my head!

help please i need the driver, its no longer available!!!!!
help please i need the driver, its no longer available!!!!!

keep failing on brom error

worked fine...but not until I installed driver and spflashtool on Win 7 machine
tried to revive bricked phone with the "help" of mofo Windows 10.
Nothing worked. Installed the driver without signed certificate...everything! All ok...but no connection and BROM error.
windows detects phone for 10 miliseconds and after that driver crashes (no connection). And restarts the driver again. It's like bootloop for the driver too )
Switched to wife's Win 7 machine...
& everything went smooth like a little baby's bottom.
Good to know:
I had this ver. before Brick & found it on the web: 0PA2IMG_V1_DUG_JB422_SENSE51_htc_asia_sea_wwe_1.03.708.1_Radio_MOLY.WR8.W1315.MD.WG.MP.V19_release
*later edit: actually my version before brick was 1.03.708.10. there was a ~14mb update from 1.03.708.1
It is the version sold in Romania - HTC 310 dual sim BLUE (512mb ram) After install: everything works. NO imei error, NO gsm signal problems, NOT ONE PROBLEM
also, I actualy left the phone without battery when instaling driver and when flashing firmware (ticked "w/o battery").
you can dl the win 7 drivers bellow my post
Thanks for the good Tut.
PS: I bricked the phone as everyone else....Trying to install CWM with RASHR.apk as seen in that friggin youtube clip (because it stated: tutorial for 1.03.708.12 phones or SIMILAR <<bad idea!)

request firmware
where to download the firmware for uni sim htc desire 310?
I'm suffering a boot loop which only shuts down and restarts my htc

anormal bootloop on htc desire d310 uni sim
hi there...i'm suffering a non normal bootloop which shuts down and restarts my desire d310 uni sim and can't do nothing with sp flash tool because it keeps restarting and reconecting to my pc :'( :'( :'( :'(
---------- Post added at 01:29 PM ---------- Previous post was at 01:24 PM ----------
MalekJandali said:
I think it's you who contacted me in the blog, so it's work now, congrats
Click to expand...
Click to collapse
help me pleaseeeeeee...same problem happening to me,what can I do? plzzzzzzzz help..
---------- Post added at 01:39 PM ---------- Previous post was at 01:29 PM ----------
Vijay_35 said:
Hey man, Can you briefly explain the procedure? I have the same issue. Phone connects and reconnects every 2 seconds. I did CWM recovery and my phone into boot loop and after that i did something using sp flash tool and now it wont turn on. I have updated the drivers manually. How can I get out of this hole? Its my first experiment gone havoc. Any help would be appreciated? thanks in advance
Click to expand...
Click to collapse
hi there...same problem for me too,so if u know what to do plz tell me.

cundr said:
hi there...i'm suffering a non normal bootloop which shuts down and restarts my desire d310 uni sim and can't do nothing with sp flash tool because it keeps restarting and reconecting to my pc :'( :'( :'( :'(
---------- Post added at 01:29 PM ---------- Previous post was at 01:24 PM ----------
help me pleaseeeeeee...same problem happening to me,what can I do? plzzzzzzzz help..
---------- Post added at 01:39 PM ---------- Previous post was at 01:29 PM ----------
hi there...same problem for me too,so if u know what to do plz tell me.
Click to expand...
Click to collapse
trial and error...
remove battery, connect to pc holding volume down(-) button. OR try with battery atached and holding volume down. Sometimes works even without pressing volume down. Whatever suits.
in Windows Device Manager: Right when device is detected proceed to manualy install drivers.
Sometimes crappy Windows 8, 8.1, or 10 have trouble installing and starting the driver. In win10 you get error: "driver not migrated. device cannot start " or something like that (Device manager/Driver properties)
You should try in windows 7.
Disconnect phone
Open SP Flash with "Run as administrator" and set it up corespondingly(see first post), without the phone!
press "download" ->Sp Flash will wait for you to reconnect phone to pc...
try connection with battery atached... try connection without battery atached and atach it when usb cable connected...
Sp Flash tool as soon as it detects phone, it starts to flash firmware.
MOST IMPORTANT: write down which SP Tool errors you get!!!!!!!!!!!!!!!!!!!!!!! and POST BACK

LG g3 bricked. Could not load Qualcomm 9008 driver.

Hello,
I have a LG G3 d855 which is bricked while updating ROM. It is hard bricked meaning I could not see anything on the display. I went to the LG service center. They had a suggestion to replace complete mother board. I went through few forums on XDA on how to unbrick the dead phone.
Here is the procedure which I have followed,
I was not able to see "LGE AndroidNet USB serial port" and "Qualcomm HS-USB QDLoader 9008" .. The suggestions were to short the pins.
After shorting pins and replacing the battery, I am able to "LGE AndroidNet USB serial port" only.
Here are couple of links I went through,
http://forum.gsmhosting.com/vbb/f49...ts-fix-qhsusb-bulk-_-qualcomm-9008-a-2029025/
https://forum.xda-developers.com/lg-g3/general/unbrick-lg-g3-qhsusbbulk-qualcomm-9008-t3072091
How do I get "Qualcomm HS-USB QDLoader 9008" in the driver list instead of "LGE AndroidNet USB serial port" ?

Just keep trying, with no battery. You should be doing it pretty fast, in less than 30 seconds, else, windows picks your phone as an unknown device.
Also try making the shorting of the 'pins' as strong as possible with something you know it's really conductive (for me, paper staples if can't get copper) and holding it still for 5 seconds.
I have to try for about 10 times to make it right, and sometimes BoardDiag still says it's not in QDLmode and have to redo the process.
When u manage to get HS-USB in Device Manager, try boardDiag3.99a and boardDiag2.99a as I've seen that on my laptop, 3.99 says that phone is not in QDLmode, yet 2.99 work perfectly

AKAndrew41 said:
Just keep trying, with no battery. You should be doing it pretty fast, in less than 30 seconds, else, windows picks your phone as an unknown device.
Also try making the shorting of the 'pins' as strong as possible with something you know it's really conductive (for me, paper staples if can't get copper) and holding it still for 5 seconds.
I have to try for about 10 times to make it right, and sometimes BoardDiag still says it's not in QDLmode and have to redo the process.
When u manage to get HS-USB in Device Manager, try boardDiag3.99a and boardDiag2.99a as I've seen that on my laptop, 3.99 says that phone is not in QDLmode, yet 2.99 work perfectly
Click to expand...
Click to collapse
hey, thanks a lot. It worked. I could get the phone flashed using the BoardDiag.
Now. Another issue which I am facing is, I am not able to flash the phone using the LG Flash Tool.
Here are the steps which I have followed,
1. Pressed Volume UP key .. while holding the same key I can attached USB to the phone.
2. Phone went into download mode.
3. PC has also recognized that the device. But it showing Qualcomm 9008 driver (which is not expected I suppose) . I should be able to see LGE driver in the port section.
4. I have installed all necessary LG drivers.
Still, I went ahead and tried the LG flash tool. But once it shows all ports are ready. I removed the cable to for 5 sec and reattached. Now, It's showing unknown driver in the USB controllers. It should be flashing the phone on this step.
Am I missing something ? Appreciate your help.

I assume that you are not getting the "Firmware upgrade" screen. The easiest way is, in BoardDiag, select AP, EMMC and SDRAM (and the path to the extracted .tot) and press start. It should get you to the screen.
From there you should follow the normal flashing procedure using one of the flashing tools.
If in your device manager under Ports you see a AndroidNet port, you must install LG usb Drivers.

AKAndrew41 said:
I assume that you are not getting the "Firmware upgrade" screen. The easiest way is, in BoardDiag, select AP, EMMC and SDRAM (and the path to the extracted .tot) and press start. It should get you to the screen.
From there you should follow the normal flashing procedure using one of the flashing tools.
If in your device manager under Ports you see a AndroidNet port, you must install LG usb Drivers.
Click to expand...
Click to collapse
Hey Andrew,
You mean If I see the firmware upgrade screen, I should be able to see LG usb driver loaded (instead of Qualcomm 9008). I did try the the AP, EMMC and SDRAM, but did not reach to the firmware upgrade (Still I will try once again). BTW, I tried multiple tools including LGUP, LG Flash tool (2014 Mod), LG Flash tool (kdz method). I am getting weird errors like model info check failed, KDZ method abruptly stops or LGUP shows null model after detection.
Is there any way we could chat somewhere. (may be on Gmail/WebEx, if don't mind). Really appreciate you help.

rushikesh005 said:
Hey Andrew,
You mean If I see the firmware upgrade screen, I should be able to see LG usb driver loaded (instead of Qualcomm 9008). I did try the the AP, EMMC and SDRAM, but did not reach to the firmware upgrade (Still I will try once again). BTW, I tried multiple tools including LGUP, LG Flash tool (2014 Mod), LG Flash tool (kdz method). I am getting weird errors like model info check failed, KDZ method abruptly stops or LGUP shows null model after detection.
Is there any way we could chat somewhere. (may be on Gmail/WebEx, if don't mind). Really appreciate you help.
Click to expand...
Click to collapse
[update]
Hi Andrew,
I followed the steps you have mentioned (Tried AP, EMMC and SDRAM). Then disconnected from the USB. Placed Battery. and while holding the up key reattached the USB.
I can see it went into 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"
}
But after that it shows blank screen( instead of firmware upgrade).
And Qualcomm driver is getting loaded. (which is not expected, I should be able to see
the firmware upgrade screen right ?).
Still I tried the LG flash tool. But it failed with model check error.
With above method I was getting Qualcomm driver loaded. (which was not expected).
I tried another way, where I booted the phone (it went into kernel panic) as written over there I pressed up key and reattached USB.
Now I can see the LGE Android drivers loaded. But still I am not seeing the firmware upgrade screen. And LG flash tools are also not working in this stage.
Am I missing something ?

Give it another try using LGUP8974.dll but you must have Firmware Upgrade screen. I don't think it will work through Qualcomm unless you flash each partition with BoardDiag but it is painfully slow.
I've read about this problem on the forum and this should have solved it. Worked for me too, most of the times.
Make sure you have a charged battery. Spend a whole day trying to get firmware upgrade screen just to found out wasn't getting it due to low battery...

AKAndrew41 said:
Give it another try using LGUP8974.dll but you must have Firmware Upgrade screen. I don't think it will work through Qualcomm unless you flash each partition with BoardDiag but it is painfully slow.
I've read about this problem on the forum and this should have solved it. Worked for me too, most of the times.
Make sure you have a charged battery. Spend a whole day trying to get firmware upgrade screen just to found out wasn't getting it due to low battery...
Click to expand...
Click to collapse
Thanks Andrew.
Not sure if this is low battery issue in my case. I am able to see LG logo without connecting it to USB. (was it the same case with you).
Still I will charge my phone again. Will do the SDRAM test again to see if phone shows firmware upgrade screen.
If this does not work, I will have to write all partitions using BoardDiag. Should I follow any sequence for the same ?
I have read on the other posts about the sequence. Would it matter ?
Let me know.

rushikesh005 said:
Thanks Andrew.
Not sure if this is low battery issue in my case. I am able to see LG logo without connecting it to USB. (was it the same case with you).
Still I will charge my phone again. Will do the SDRAM test again to see if phone shows firmware upgrade screen.
If this does not work, I will have to write all partitions using BoardDiag. Should I follow any sequence for the same ?
I have read on the other posts about the sequence. Would it matter ?
Let me know.
Click to expand...
Click to collapse
You can follow the partition order from this link(listed in steps 18 & 19)... https://forum.xda-developers.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928
aboot, BackupGPT, boot, dbi, laf, PrimaryGPT, recovery, rpm, tz and finally sbl1 (MAKE SURE THIS IS THE LAST ONE FLASHED(it causes the phone to reboot)
*do not flash system or user data partitions with board diag - they take over an hour and they will be re-flashed once you get download mode working anyway
*if a partition fails to write you may need to erase it first
*another good guide for reference... https://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
Good luck!:good:

If you want to avoid using LG Flashtool I think(no sure) u can flash them through BoardDiag. The order is the one mentioned by startswithPendswithOOH but I thing u can add system partition and the others right befor sbl1.
I couldn't make my G3 stable even at the best GSM service in my city - due to notorious CPU/eMMC fails (overheating, protected storage etc.) and ther response was RIP. No chance to make it work again, will always crash whenever I will get the cpu reach 100%. I will never in my life buy LG phones again. Glad I won't lose more than 60$

Hello. I know that this thread is quite old but I am trying hard to revive my hard bricked LG G3 D855 these days. I have installed Qualcomm Drivers but I cannot get my device recognized on my PC. As soon as I plug in my phone I receive a "USB Device not recognized" error. I believe I am shorting the pins correctly and everything regarding drivers installation has been done as described. But I have tried too many times and I still receive that error. Please note that my phone is dead. It used to light up when I connected it on the PC but now its totally unresponsive. Could anyone please let me know what I could be doing wrong? Does the type of wire used to short the pins play significant role? Any images of a wire that I could use?

LG-K430T and Sp Flash Tool

Hey!
I have a K10 2016 phone (K10 LTE, reported as K430T, motherboard k430ds), which I bricked, but I "resurrected" it doing circuit-bridge.
Now my phone get recognized by PC, but as "0E8D:0003" under Device Manager. But LGUP, or even Uppercut doesn't seem to recognize it for proper flashing.
I installed all the known drivers: VCOM drivers, Mediatek USB drivers, for Windows 10 x64 with driver signature off.
I downloaded latest SP Flash Tools 5.1728 from here and a scatter file for chipset MT6753 here.
I have LG stock rom for the model 2016 (named K430T10b_01_0805.kdz) and extracted it using KDZ Extract.
I got all the necessary files (preloader, lk, boot, recovery, logo, secro, tee1, tee2 and system) from the KDZ rom.
I loaded scatter file into SP Flash Tools.
Then, clicked "recovery" and browse to the extracted recovery_190464.bin file, loaded OK, then preloader was autoloaded also. Ticked both and set SP to "Firmware upgrade".
But when I click "Download", an error appears, saying S_AUTH_IS_NOT_READY (5000), refering to a secure base-band chip, and needs an "authentication file first".
This is where I get lost. I don't really know what a secure base-band chip means, I know latest Mediatek chipsets are 64bits architecture, and latest SP Flash Tool can handle 64bits well, and, that they're already encrypted or have some kind of encryption.
So I downloaded an (I think) generic auth file from here, loaded it and then pressed "Download" again, with scatter, preloader, recovery and "Firmware upgrade" settings.
But then, inmediately, this message appears: "ERROR : S_SECURITY_SEND_AUTH_FAIL (6029) , MSP ERROE CODE: 0x00 [HINT]:" and then pressed OK, and don't know what else to do.
I tried FWUL but is too dificult, Linux doesn't even recognize any other usb plugged into it.
Help please! Thank you

HELP
I am with the same problem I would like to find a solution because I am without cell phone now.

I had fallen into same situation. It's due to signature verification fail as we can understand from the error text. Thanks to LG, they didn't share any authentication file which could help us to flash something through SP Flash tool (though they didn't enable it). In fact, if they wanted us to be able to flash something unofficial, they would let dm-verity go when we unlock the bootloader...
You have to either disassembly the emmc of your mother board and re-write whole stock partitions or directly replace the mother board.
I tried something similar to first option. I soldered emmc pin-outs to card reader in order to be able to see the partitions of the emmc on my pc. It didn't work actually. When I plug in the usb, the phone is recognized as MTK Serial Com while it was recognized as LGE Serial Com right before I soldered the card reader. When pc recognizes the device as MTK Serial Com, SP Flash tool is able to write/flash something but as I said above, security measures doesn't let it to do.
If you happen to ask that how I fixed it, I sent my phone to official LG Service saying that it had suddenly turned off while installing stock firmware via LG Bridge.
Update 7th March 2018: They replaced my K10 with LG G4 in 1st March.
Good luck whoever faces this damn...

You may have to deal with seccfg and NVRAM as well, or at least that was what I can attest with secure MTK SoCs like the MT8127. For the heck of it, have you tried flashing using SP Flash Tool 5.1532? The phone may not even work after flashing but let me know if it makes any difference. What I know is that there is a quirk with said version where unsigned images can be fed on a secure device.
There is also a tool by MTK for signing images through Linux but I dunno if it supports MT67xx-series chips.

panchowatkins said:
Hey!
I have a K10 2016 phone (K10 LTE, reported as K430T, motherboard k430ds), which I bricked, but I "resurrected" it doing circuit-bridge.
Now my phone get recognized by PC, but as "0E8D:0003" under Device Manager. But LGUP, or even Uppercut doesn't seem to recognize it for proper flashing.
I installed all the known drivers: VCOM drivers, Mediatek USB drivers, for Windows 10 x64 with driver signature off.
I downloaded latest SP Flash Tools 5.1728 from here and a scatter file for chipset MT6753 here.
I have LG stock rom for the model 2016 (named K430T10b_01_0805.kdz) and extracted it using KDZ Extract.
I got all the necessary files (preloader, lk, boot, recovery, logo, secro, tee1, tee2 and system) from the KDZ rom.
I loaded scatter file into SP Flash Tools.
Then, clicked "recovery" and browse to the extracted recovery_190464.bin file, loaded OK, then preloader was autoloaded also. Ticked both and set SP to "Firmware upgrade".
But when I click "Download", an error appears, saying S_AUTH_IS_NOT_READY (5000), refering to a secure base-band chip, and needs an "authentication file first".
This is where I get lost. I don't really know what a secure base-band chip means, I know latest Mediatek chipsets are 64bits architecture, and latest SP Flash Tool can handle 64bits well, and, that they're already encrypted or have some kind of encryption.
So I downloaded an (I think) generic auth file from here, loaded it and then pressed "Download" again, with scatter, preloader, recovery and "Firmware upgrade" settings.
But then, inmediately, this message appears: "ERROR : S_SECURITY_SEND_AUTH_FAIL (6029) , MSP ERROE CODE: 0x00 [HINT]:" and then pressed OK, and don't know what else to do.
I tried FWUL but is too dificult, Linux doesn't even recognize any other usb plugged into it.
Help please! Thank you
Click to expand...
Click to collapse
Could you tell me how you did the circuit-bridge? in which pin of the motherboard?
Sorry for my english

Dear members of the forum. Who knows how to restore TA? was flashed with firmware k430ds11i lowered by k430ds11k TA died (Brick) It is not determined by anything! Who can tell me what? And if there is a possibility? share loader k430ds11i.img

Unbrick guide for 5T

Is there a OP5T unbrick guide? Or is it the same as the OP5?

nikolajkracht said:
Is there a OP5T unbrick guide? Or is it the same as the OP5?
Click to expand...
Click to collapse
I'd start by looking through this other question thread: https://forum.xda-developers.com/oneplus-5t/help/please-help-hardbricked-oneplus-5t-t3716057

OnePlus 5T unbrick tutorial
Link - http://www.oneplusbbs.com/forum.php?mod=viewthread&tid=3836845&extra=page=1&filter=typeid&typeid=136

would you please bring this tool because he need replay in fourm i cannot all chinese i try to register but i cannot
thankyou

GUIDE FOR UNBRICK ONEPLUS 5T:
This guide will fix all brick problems INCLUDING bootlocked, oem locked. It will fix the "Your device is corrupt and will not boot" problem. It will also works if you flashed the Oneplus 5 phone and ended with a upside-down screen, unusable touch screen.
guide inspired by https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Use the following file for unbrick (Msmdownloadtool)
https://mega.nz/#!QOJjGYRT!oLL9gRKQF9sE1PcVl241WvMQL-dhBaG24T5-ixo2pzs
It includes a Windows-only flasher and a recent OPS file.
Usage:
- Poweroff your phone (keep the power button for 40 seconds)
- Hold the volume up button for 10 seconds
- Connect USB-C cable
- Open device manager and ensure you have a "Qualcomm 9008 (COM3)" listed in Com ports. I had no driver to install (Windows 10).
- Unrar the 2GB file. It contains no error
- open the "dumpling_43_O.06_171206" folder
- Launch "MsmDownloadTool V4.0.exe"
- Click "Verify"
- Wait for "Md5 Check Ok!"
- Click "Start"
This will completely wide your device (oneplus 5T only !) and reinstall EVERYTHING (OxygenOS 4.7.2). The phone reboots automatically.
It will fix all brick problems.

thank you i will tested
thank you i will test it .

EDIT 2 : The MSM Download Method worked for me! Thanks !
Did it work ?
https://androidfilehost.com/?fid=889964283620773422
If you want to try out the second method! (downloading right now to test it, since my device is unusable after oreo update...)
EDIT : Second method did help a bit but phone is still unconscious. Trying the MSM Download Tool right now

diminou91 said:
EDIT 2 : The MSM Download Method worked for me! Thanks !
Did it work ?
https://androidfilehost.com/?fid=889964283620773422
If you want to try out the second method! (downloading right now to test it, since my device is unusable after oreo update...)
EDIT : Second method did help a bit but phone is still unconscious. Trying the MSM Download Tool right now
Click to expand...
Click to collapse
were u on 128GB or 64GB version?

Bradl79 said:
were u on 128GB or 64GB version?
Click to expand...
Click to collapse
I have the 64GB version of OP5T, but I'm guessing the files are the same since we use the same OOS update. Should work for the 128GB version too

thankyou

Thank yo elwin94 ! It worked like a charm !
Thank A LOT !!!

Doenst work for me, sahara communication fails.

BazzBeater said:
Doenst work for me, sahara communication fails.
Click to expand...
Click to collapse
U need to check ur drivers

what do I do if the QUALCOMM 9008 is not listed?

brendonppagel said:
what do I do if the QUALCOMM 9008 is not listed?
Click to expand...
Click to collapse
make sure the drivers are installed
it should look like below
How To:
Code:
Step 1: Download Driver and Unbricktool
Step 1: Extract Drivers and Recovery Tool files on Desktop.
Step 2: If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :
http://www.howtogeek.com/167723/how....igned-drivers/
Step 3: Press the power button for 40 seconds to turn off the phone.
Step 4: Press the volume up button for 10 seconds, while connecting the device with the computer.
Step 5: Open your device-manager and make sure in "Unknown devices" is one device with the name "QHUSB_BULK".
Step 6: Right Click on your device in the device manager and select Update Device Software. Choose manually the drivers folder and install the driver.
Step 7: When the device shows as "Qualcomm 9008", go run the MSM Download Tool as administrator.
Step 8: Click start at top left corner and wait for it to finish (green text will come).
Step 9: Disconnect phone from PC and boot into system.

elwin94 said:
GUIDE FOR UNBRICK ONEPLUS 5T:
This guide will fix all brick problems INCLUDING bootlocked, oem locked. It will fix the "Your device is corrupt and will not boot" problem. It will also works if you flashed the Oneplus 5 phone and ended with a upside-down screen, unusable touch screen.
guide inspired by https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Use the following file for unbrick (Msmdownloadtool)
https://mega.nz/#!QOJjGYRT!oLL9gRKQF9sE1PcVl241WvMQL-dhBaG24T5-ixo2pzs
It includes a Windows-only flasher and a recent OPS file.
Usage:
- Poweroff your phone (keep the power button for 40 seconds)
- Hold the volume up button for 10 seconds
- Connect USB-C cable
- Open device manager and ensure you have a "Qualcomm 9008 (COM3)" listed in Com ports. I had no driver to install (Windows 10).
- Unrar the 2GB file. It contains no error
- open the "dumpling_43_O.06_171206" folder
- Launch "MsmDownloadTool V4.0.exe"
- Click "Verify"
- Wait for "Md5 Check Ok!"
- Click "Start"
This will completely wide your device (oneplus 5T only !) and reinstall EVERYTHING (OxygenOS 4.7.2). The phone reboots automatically.
It will fix all brick problems.
Click to expand...
Click to collapse
I can't thank you enough! You saved my ass today good sir!!

Bradl79 said:
make sure the drivers are installed
it should look like below
How To:
Code:
Step 1: Download Driver and Unbricktool
Step 1: Extract Drivers and Recovery Tool files on Desktop.
Step 2: If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :
http://www.howtogeek.com/167723/how....igned-drivers/
Step 3: Press the power button for 40 seconds to turn off the phone.
Step 4: Press the volume up button for 10 seconds, while connecting the device with the computer.
Step 5: Open your device-manager and make sure in "Unknown devices" is one device with the name "QHUSB_BULK".
Step 6: Right Click on your device in the device manager and select Update Device Software. Choose manually the drivers folder and install the driver.
Step 7: When the device shows as "Qualcomm 9008", go run the MSM Download Tool as administrator.
Step 8: Click start at top left corner and wait for it to finish (green text will come).
Step 9: Disconnect phone from PC and boot into system.
Click to expand...
Click to collapse
does your phone goes in fastboot mode, or this is not really for those devices which are not really dead but just want to restore it

dryspuri said:
does your phone goes in fastboot mode, or this is not really for those devices which are not really dead but just want to restore it
Click to expand...
Click to collapse
this is for if u cannot go into fastboot mode or if u cannot load ur OS through fastboot, if u are in fastboot mode the qualcomm driver will not show up, u have to power ur phone off completely and hold the vol up button for 10 sec, then plug in ur cable, ur screen will still stay black and u will see the qualcomm driver show up, then u will open the msm tool

Thanks that did the trick.
Sent from my BKL-L09 using Tapatalk

Hi! friends, can someone help me please, some of you have a download link that is not MEGA?