Related
Dear guys!
I want to flash ftf JB file for my phone, but problem is:
I cant enter flash mode, actually, phone only stay in flash mode for a while (about 20 seconds) then it auto turn off.
Im using XZXperience 2 rom, and i have tried to install both e-lite kernel and arkama v1.7 kernel but not help!
Any advice for my problem?
PS: I installed flashtool on win8 laptop! Flashtool showed my phone connected in flash mode.
Same problem with fastboot mode!
Check that the USB port is 2.0 and not 3.0. And please post in the correct section in Q&A.
Most likely your drivers aren't installed properly (are you on Win7 x64 or Win8?). There's a trick to install them by opening the device manager (on your pc) and manually installing the drivers. I've also read that you can install the drivers along with Flashtool nowadays, there should be an option somewhere. So try that first, if that doesn't work ..
Use this method. Ignore the bit of editing drivers and go to the "lazy" method:
And if you are very lazy, you can download my "android_winusb.inf", which I attached - put it into *\Android\android-sdk\extras\google\usb_driver.
Once you finished that, just turn off your phone, hold the search button and connect it to your PC while still holding the search button (boot into fastboot).
Via the device-manager or the device center you can now see a device called "S1Boot Fastboot" with a warning sign - rightclick it, press on "Properties", click on the Hardware tab and then again on "Properties".
After that click on the driver tab and press on "update driver".
Choose the option to look manually for the driver and then guide to the usb_driver folder, which I mentioned above.
Now you should be able to access the fastboot-tool via PC.
Hope I could help you and I'm sorry if I made some language mistakes, but English is a foreign language for me.
Have a nice day,
Janitor
Click to expand...
Click to collapse
You can download the driver from the link. Oh and "search" is volume up/down (the one you're using to get into flash mode, I forget which is which ), that guide was written for Xperia Play.
If I were you, I'd just install the CWM zip DooMLorD posted though, don't use flashtool.. Although you'd need fastboot to flash the custom kernel if you want a recovery, but no flashtool.
Lastly, development is not the Q&A thread, you aren't supposed to create threads for asking questions, this will most likely get moved. Please read the forum rules before creating threads. Saying that you didn't know the rules is no excuse, that just means you didn't bother to read them and shows your lack of respect.
I flash twrp v2.7.1.1 as my recovery mode.
Managed to go in the recovery, but failed to flash any ROM.
It keep telling me "Installing '/eternal_sd/rom-to-be-installed.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Error flashing zip '/external_sd/rom-to-be-installed.zip'
Updating partition details...
What should i do? I've done wipe the cache and factory reset but still no luck to install and now i'm stuck and going now where...
please help, i've download the official firmware as well to flash back but yet still the same error... =(
can anyone please help me on this?
:crying::crying::crying:
danieltanz said:
I flash twrp v2.7.1.1 as my recovery mode.
Managed to go in the recovery, but failed to flash any ROM.
It keep telling me "Installing '/eternal_sd/rom-to-be-installed.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Error flashing zip '/external_sd/rom-to-be-installed.zip'
Updating partition details...
What should i do? I've done wipe the cache and factory reset but still no luck to install and now i'm stuck and going now where...
please help, i've download the official firmware as well to flash back but yet still the same error... =(
can anyone please help me on this?
:crying::crying::crying:
Click to expand...
Click to collapse
Does this even happen flashing tar file of official firmware through Odin?
pdolton2000 said:
Does this even happen flashing tar file of official firmware through Odin?
Click to expand...
Click to collapse
I can't get Odin connected. I plug in windows detected and shows on the task at there but grey off can't accessed it. Odin can't find where it was connected too
danieltanz said:
I can't get Odin connected. I plug in windows detected and shows on the task at there but grey off can't accessed it. Odin can't find where it was connected too
Click to expand...
Click to collapse
Check out device manager whilst connected via USB in download mode, if there's any devices with yellow symbols it probably means you need the adb drivers found here
http://developer.android.com/sdk/win-usb.html
Then Odin should pick up your tab and your in business, Odin is your way out of this I believe.
pdolton2000 said:
Check out device manager whilst connected via USB in download mode, if there's any devices with yellow symbols it probably means you need the adb drivers found here
Then Odin should pick up your tab and your in business, Odin is your way out of this I believe.
Click to expand...
Click to collapse
It does detect in my windows now i can see and through device manager, it has been assigned to com port 2 but odin still failed to detect any incoming port...can i manually tell odin that transfer it via com port 2? Because i did realized when i boot to recovery the first thing will appear is TWRP...that cause the the Odin cant detect it through...
danieltanz said:
It does detect in my windows now i can see and through device manager, it has been assigned to com port 2 but odin still failed to detect any incoming port...can i manually tell odin that transfer it via com port 2? Because i did realized when i boot to recovery the first thing will appear is TWRP...that cause the the Odin cant detect it through...
Click to expand...
Click to collapse
Okay show me a screenshot of device manager whilst tablet is connected in download mode, also expand any sub catogeries that contain either your adb device in it or anything with samsung in it if you can...you shouldn't need to play with com ports really, if the adb USB drivers are installed and the adb device shows up in device manager Odin's meant to detect it automatically, also right click on the adb device in device manager and click properties, and go to the section where it shows driver version and screen shot that just so I can verify a couple of things...sounds to me like its not using googles adb driver but can't be sure.
pdolton2000 said:
Okay show me a screenshot of device manager whilst tablet is connected in download mode, also expand any sub catogeries that contain either your adb device in it or anything with samsung in it if you can...you shouldn't need to play with com ports really, if the adb USB drivers are installed and the adb device shows up in device manager Odin's meant to detect it automatically, also right click on the adb device in device manager and click properties, and go to the section where it shows driver version and screen shot that just so I can verify a couple of things...sounds to me like its not using googles adb driver but can't be sure.
Click to expand...
Click to collapse
What I did is, I uninstall the driver from device manager, reboot my laptop let windows re-detect it again and walla..it found the new hardware and driver being installed again. Run odin, my device added and I flash back the original rom with the download mode and everything back to normal. Thank you so much for your help spending your time to help me troubleshoot together.
Appreciate all your help.
danieltanz said:
What I did is, I uninstall the driver from device manager, reboot my laptop let windows re-detect it again and walla..it found the new hardware and driver being installed again. Run odin, my device added and I flash back the original rom with the download mode and everything back to normal. Thank you so much for your help spending your time to help me troubleshoot together.
Appreciate all your help.
Click to expand...
Click to collapse
That's perfect mate glad it all worked outout for ya.
pdolton2000 said:
That's perfect mate glad it all worked outout for ya.
Click to expand...
Click to collapse
I would like to flash it too lolipop but is it good enough? Will it cause me hang again like before? Any advice
I cannot give you any advice for lollipop as I've never tried it, I only have t805 which its not available for yet, but if I did own a t705 I would definitely take a look at this:
http://forum.xda-developers.com/galaxy-tab-s/development/rom-blisspop-team-bliss-t2987234
Some people love it, some don't...but it seems feature packed anyway...good luck pal enjoy your working tab.
I will explain how to set the device tampered back to "false" on the Wileyfox Swift.
Required:
7z
WFS.7z (https://drive.google.com/file/d/0B6Ge199bCD5_NF9RWGhVLVhxajA/view?usp=sharing)
Windows 7 or 8
Driver Signature Enforcement disabled
Step 1: Brick the device on purpose
Hold Volume Up button+Volume Down button while plugging in USB
You should be see QHS_USB BULK in Device Manager
S
Step 2: Install Driver
Reboot with Driver Signature Enforcement disabled ( Google if you must)
Plug device in and make sure you see QHSUSB BULK in Device Manager
If you see Relink HS QDLoader 9008 uninstall it and delete driver software
Then refresh and you should see QHS USB BULK
Manually Update Driver software and navigate to driver folder extracted in WFS.7z
Step 3 : Install QPST provided in WFS.7z
I think its pretty straight forward
Step 4: Flash Firmware
Open QFil
Select Port and choose your device if not already chosen
Select Flat Build
Programmer Path must be prog_emmc_firehose_8916.mbn in the Maincode folder from WFS.7z
Build Path should automatically appear
Hit load XML.
Click rawprogram_upgrade.xml
Click patch0.xml
Click Download
Once done remove and reinsert battery
Step 5: Verify Tampered:False
boot into fastboot
type the following:
fastboot oem device-info
and it should say Device tampered : false and Device Unlock : False
NB: If you get a SaharaDownload fail or something just remove battery and USB for 5 seconds. Plug battery in. Then plug USB in.
NB: I do not accept any responsibility for damaged devices or anything. You point your finger at me and I will laugh at you
If it works don't hesitate to donate me a cup of coffee
PayPal : [email protected]
yasteellutch said:
Step 2: Install Driver
Reboot with Driver Signature Enforcement disabled ( Google if you must)
Plug device in and make sure you see QHSUSB BULK in Device Manager
If you see Relink HS QDLoader 9008 uninstall it and delete driver software
Then refresh and you should see QHS USB BULK
Manually Update Driver software and navigate to driver folder extracted in WFS.7z
Click to expand...
Click to collapse
This does not work for me, no matter wht I try, in the device manager I just get "Android" with a yello triangle.
No manual driver install / update (or update via windows update) solve that problem.
Try it on two Windows 7 PCs (x32 & x64) with Firewall, Antivirus and driver signature are disabled.
On a Windows 10 PC, the device connects as "Marshall London Device".
I don't think ur swift is bricked
when puting battery in jut get the screen "wileyfox"; recovery does not start (vol- and pwr) but fastboot mode ist working (vol+ and pwr). so it's not bricked?
so I repeat step 1 but still in windows 7 device manager having "Other Devices -> Android" with no yellow triangle.
I get SaharaDownload fail. Removing battary is useless. What else can i try? Thanks in advance
Now you get Sahara Fail. I think this is some sort of 'Lock Mode'. I fixed it by removing battery. Reinserting battery and immediately plugging in USB and hitting download
yasteellutch said:
Now you get Sahara Fail. I think this is some sort of 'Lock Mode'. I fixed it by removing battery. Reinserting battery and immediately plugging in USB and hitting download
Click to expand...
Click to collapse
I try and try do it again but i have only got sahara fail again and again.....
void2000 said:
I try and try do it again but i have only got sahara fail again and again.....
Click to expand...
Click to collapse
Upload a screenshot
yasteellutch said:
Upload a screenshot
Click to expand...
Click to collapse
Probably I have to use a special cable?
See it gets the SharaVersion right so I'm guessing that phone is in a correct state. The problem there could be that it didn't decompress properly. Maybe the integrity of your decompressed WFS.7z is not intact. Go to Android One(2nd Gen) dedicated page. I got help there. I guess all you need is to look there.
Maybe u didn't installQPSt right or the driver is a issue. I flashed stock like 3 days ago and it works perfectly
cyaneo said:
This does not work for me, no matter wht I try, in the device manager I just get "Android" with a yello triangle.
No manual driver install / update (or update via windows update) solve that problem.
Try it on two Windows 7 PCs (x32 & x64) with Firewall, Antivirus and driver signature are disabled.
On a Windows 10 PC, the device connects as "Marshall London Device".
Click to expand...
Click to collapse
Hey @cyaneo. If you still have the Yellow Android triangle this is because your drivers aren't installed correctly. I tried it. But that also means your fastboot is working.
Hi all,
Ive been a way from Android for a long time so I'm no expert but the method posted above failed for me. Like others, all my PC would recognise the phone as was "Marshall London Device" and essentially my phone was useless.
Can I ask why we need to erase and/or brick the phone?
Instead what worked for me was to reboot into fastboot mode, download Cyanogen OS signed zip, extract and run flash-radio.sh, then flash recovery and system manually. Reboot phone into working OS and then turn off OEM Unlock.
Once that's done I rebooted into fastboot and confirmed bootloader was locked and that tampered was false (as an official signed OS is installed I take it?).
Anyway as I say, I'm no expert but surely that's an easier and cleaner way than erasing/bricking a phone and only needs fastboot and the latest official signed rom from Cyanogen OS directly?
void2000 said:
Probably I have to use a special cable?
Click to expand...
Click to collapse
Hi,
This is my first post. (active lurker previously) hopefully its not too late.
In my experience on other device running 8916, a sahara failure can be overcame by holding the power button when entering download mode. (E.g: if you enter download mode by pressing and holding vol+/- simultaneously and plugging in usb cable, try holding the power button as well when you plug in the cable). This is normally a result of battery too low.
After bricking my Swift with some gymnastics around Android One firmware images, this tool worked flawlessly!
I was a bit confused when it came to the part of deleting/ manually reinstalling the driver. After the device was shown as "QHS_USB BULK", I manually installed the " Relink HS QDLoader 9008". Everything else went really smoothly. The device is good as new
For the adventurous ones with a Swift- this is one tough little phone. Hard-brick ain't a reason to stop
Pak0St said:
After bricking my Swift with some gymnastics around Android One firmware images, this tool worked flawlessly!
I was a bit confused when it came to the part of deleting/ manually reinstalling the driver. After the device was shown as "QHS_USB BULK", I manually installed the " Relink HS QDLoader 9008". Everything else went really smoothly. The device is good as new
For the adventurous ones with a Swift- this is one tough little phone. Hard-brick ain't a reason to stop
Click to expand...
Click to collapse
Lol I agree. This baby took some hits. I clocked it to 1.6 at stable. At 1.9 she became instable and started crashing #YeahITakeRisks
xfile087 said:
Hi all,
Ive been a way from Android for a long time so I'm no expert but the method posted above failed for me. Like others, all my PC would recognise the phone as was "Marshall London Device" and essentially my phone was useless.
Can I ask why we need to erase and/or brick the phone?
Instead what worked for me was to reboot into fastboot mode, download Cyanogen OS signed zip, extract and run flash-radio.sh, then flash recovery and system manually. Reboot phone into working OS and then turn off OEM Unlock.
Once that's done I rebooted into fastboot and confirmed bootloader was locked and that tampered was false (as an official signed OS is installed I take it?).
Anyway as I say, I'm no expert but surely that's an easier and cleaner way than erasing/bricking a phone and only needs fastboot and the latest official signed rom from Cyanogen OS directly?
Click to expand...
Click to collapse
Of course there is. Don't get me wrong I understand your point. But you need to remember there are log files and a bunch of other stuff lying around if you fastboot. When you use QFil it basically rewrites all the partitions thus no logs. I returned my first Swift with the IMEI issue and they gave me a new one in a week
Hi,
my Swift is also Bricked.... that means no bootloader boot or etc. i tried to flash the phone with this method but no success. my error with QFIL is this
COM Port number:20
Sahara Version:2
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
bei QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
bei QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
Click to expand...
Click to collapse
Thanks for response
Error
Download failded
Code:
Dowload fail:House fail failed to Upload the emmc images to phone using firehouse
vadimnew said:
Download failded
Code:
Dowload fail:House fail failed to Upload the emmc images to phone using firehouse
Click to expand...
Click to collapse
You made a mistake @vadimnew
Hi everyone,
My zenfone 2 ZE551ML is bricked, so i followed this guide http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
The problem comes when i arrived to the step of IntelSoc:
I install it, no problem until here, i got IntelSoc driver in my device manager .
But when i want to have the MOOREFIELD driver, I cant get it. Following this perfectly
Ash back to the Zenfone 2, shutdown, press simultaneously the key "source" + "volume +", of course you will see a screen hanging cables( I don't have hanging cables though, I just have the Logo Asus and write on the top in blue Fastboot mod !!!).
-Connect to your computer via USB cable, to standard Intel SOC driver position, wait a few seconds if the current add an item immediately below another MOOREFIELD new devices is successful.
-If You have not been, the test performed as follows: turn off the machine, plug the cable into the computer, press the power button until the device vibrates slightly, then release.
If you have an idea can you help me please. I think this is the only thing who blocks me in repairing my phone...
Thank you
Yea that problem also persists with my zenfone 2,cant install moorefield 'cause pc cant recognize my phone. Somebody please help us out.
Anagh21 said:
Yea that problem also persists with my zenfone 2,cant install moorefield 'cause pc cant recognize my phone. Somebody please help us out.
Click to expand...
Click to collapse
it is clearly instructed in that thread you mentioned. just keep few things in mind.. uninstall every mobile related driver before installing isoc. uninstall xFSTK tool if you already installed it before installing isoc. third as you are concerned about the line you mentioned morefield under intel soc. well during soc install you will see windows like attached below. at this stage you need to power cycle your device . ( turn off your device holding power button for 10 sec. then connect to pc and turn on. leave connected to pc and turn off again and turn on second time to make sure so driver are installed) don't worry if you don't see morefield under soc now. just go ahead and install xFSTK. now your concern that your device don't stays in morefield download stage ( i mean it appears in device manager and disapear) . after installing xFSTK. run it as administrator and load files. and change gp flag value. also change device detection timeout to 120. now click begin download it will start waiting for device. now turn off your device completely and connect to pc and turn on. xFSTK will force it to stay in required mode. if download do not starts. just power cycle the device while being connected to the tool.
( note: it is strongly recomended that you install isoc and connect mobile before installing. if you have already installed xFSTK then plz uninstall it and install it after performing above said steps. remove all other mobile related drivers also and if you are using windows 8 or 10 disable driver signature enforcement again even if you did it earlier)
The problem with asus flash tool solved
Solution : Open device manager i.r. Windows + X .... if your phone is not being detected... switch it on and off ... there will be ( other devices menu ) that will show your phone there..
right click on the phone , click update drivers, ofcoarse no drivers online, locate the drivers manually , wherever your bootloader file is i.e. the 1 gb file you download or the raw file as we can speak ... i didn't pin pointed it ... my file was on the desktop so I just chose desktop and it searched it and installed it.
After that the phone was successfully in the computer and being detected by the flash tool.
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?