soft bricks! - AT&T, Rogers HTC One X, Telstra One XL

soft bricks! - AT&T, Rogers HTC One X, Telstra One XL

my one x at&t on hboot 2.18, radio 1.3axxxxx, twrp 2.0.7.8, lollilop 4.3 Rom...now my issue: i install twrp App on App Store, choose At&t one x (evitaeul as i remember..), and choose twrp 2.5.0.0 for my honey, then install, a warning sign : something is wrong :, CLOSE and REBOOT, and black screen, i can't press power button or any do anything else, i plugged it into windows 8, and try to install driver, at first time, the windows recognise as a adroid 1.0, and install Htc driver on windows, and then Windows recognised as d My HTC, i change it to Adroid ADB interface, what next step i have to do to save my honey? pleaseaaaaaaaaaa save me! help me!

fastboot devices commands, it show my phone are in fastboot mode: t♥☻ fastboot

Related

[Q] [HELP] Nexus S Drivers? I9020T Wind Mobile

I am trying to root my Nexus S. Actually, I'm trying to play around with the ADP developer terminal but I can't seem to get my drivers working. I even called Samsung but they told me they're supposed to not be installed (sigh).
It says that the drivers for Nexus S are missing
it also says the drivers for Android 1.0 are missing
I tried to install the Android 1.0 drivers manually through device manager (I am using Windows 7 64). I have the latest version of the android SDK installed along with the Google USB Driver package, revision 4
I navigate to C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver but windows just says,
"Windows was unable to install your Android 1.0
Windows could not find driver software for your device.
If you know the manufacturer of your device, you can visit its website and check the support section for driver software."
I checked the directory myself and it has a few files in it
android_winusb.inf
androidwinusb86.cat
androidwinusba64.cat
source.properties
Does anyone know what is going on and how I fix this?

Never mind, it just worked.
I right clicked the item in device manager and went to "scan for hardware changes" and then went to properties and navigated to the driver tab and went update driver and put in the directory again except this time with a trailing backslash and it worked.
I also rebooted the phone into regular mode instead of the power button + volume up boot loader.
I'm not sure which of those things made it work since I know I did the scan for hardware changes and properties / update driver thing several times without it working before.
*shrugs*
Thanks

WAIT!!
I spoke too soon. Apparently, when I boot it back into the bootloader (power button + volume up) it changes back to Android 1.0 and says it is missing drivers. Once again it will not let me install the drivers no matter what I try.
Even though I successfully installed the driver in regular mode, now it says the driver can't be found and there's nothing I can do about it.
Please help!

Aro2220 said:
WAIT!!
I spoke too soon. Apparently, when I boot it back into the bootloader (power button + volume up) it changes back to Android 1.0 and says it is missing drivers. Once again it will not let me install the drivers no matter what I try.
Even though I successfully installed the driver in regular mode, now it says the driver can't be found and there's nothing I can do about it.
Please help!
Click to expand...
Click to collapse
uninstall what you installed, then go to PDAnets' website http://junefabrics.com/android/ download the free installer. then start the program, follow the on-screen instructions, and let it install the drivers for you.

"Install to phone failed
Installer fail to open device"
When I go into windows device manager it shows up as Android ADB Interface on my computer...even when in the boot loader.
But if I try adb devices it doesn't list it as a connected device.

Aro2220 said:
Install to phone failed
Installer fail to open device
Click to expand...
Click to collapse
did you go to the phones main settings, applications, development.. and enable usb/android debugging?

Yes, I did that originally before I started having any of these problems.
When the phone is booted normally I can adb devices and it shows up. I can connect to it as well with adb shell and see all my files.
Then, I power down my phone and boot it back up holding the volume up and power button.
Now I am on the FASTBOOT MODE screen:
Code:
FASTBOOT MODE
PRODUCT NAME - HERRING
HW VERSION - REV 11
BOOTLOADER VERSION - I9020XXKA3
BASEBAND VERSION - I9020XXKF1
CARRIER INFO - TMB
SERIAL NUMBER - 12345ETC
LOCK STATE - LOCKED
SELECT - VOL UP or VOL DOWN
EXECUTE - POWER
REBOOT BOOTLOADER
REBOOT
RECOVERY
POWER OFF
USB Control Init
USB Control Init End
STANDARD_SET_CONFIGURATION
Now I adb devices and nothing is there.

Aro2220 said:
Yes, I did that originally before I started having any of these problems.
When the phone is booted normally I can adb devices and it shows up. I can connect to it as well with adb shell and see all my files.
Then, I power down my phone and boot it back up holding the volume up and power button.
Now I am on the FASTBOOT MODE screen:
Code:
FASTBOOT MODE
PRODUCT NAME - HERRING
HW VERSION - REV 11
BOOTLOADER VERSION - I9020XXKA3
BASEBAND VERSION - I9020XXKF1
CARRIER INFO - TMB
SERIAL NUMBER - 12345ETC
LOCK STATE - LOCKED
SELECT - VOL UP or VOL DOWN
EXECUTE - POWER
REBOOT BOOTLOADER
REBOOT
RECOVERY
POWER OFF
USB Control Init
USB Control Init End
STANDARD_SET_CONFIGURATION
Now I adb devices and nothing is there.
Click to expand...
Click to collapse
do a fastboot devices

Might be because you can't use adb in fastboot.
Sent from my Nexus S MV from the XDA Premium app.

Fastboot devices found my device. I was able to unlock it and follow the instructions on http://forum.xda-developers.com/showthread.php?t=895545
But I run into a problem whenever I enter the recovery mode. It just gives me the android with the exclamation mark in a triangle symbolizing that something went wrong.
EDIT: I think I didn't know how to use the recovery module. If you press volume up then power then let go of power or something like that it shows you some command options at the top of the screen.
But I realized that wasn't clockwork and after doing some reading I think when I rebooted the phone it auto-flashed the recovery module back to the default one.
So I flashed clockwork recovery.img again using the same steps except this time I went straight into the recovery option instead of rebooting my phone and then I saw clockwork.
I followed the rest of the steps from that work and everything seems to be working.
Thanks again ;-)

Aro2220 said:
Fastboot devices found my device. I was able to unlock it and follow the instructions on http://forum.xda-developers.com/showthread.php?t=895545
But I run into a problem whenever I enter the recovery mode. It just gives me the android with the exclamation mark in a triangle symbolizing that something went wrong.
Any ideas?
Click to expand...
Click to collapse
fastboot a custom recovery like clockwork or twrp. then flash whatever rooted rom(and gapps) you plan on flashing.

Go To The Link From Your PC and Click the Box Within The YouTube video. Watch the video and in description should be a download link named NexusRootNew
http://m.youtube.com/#/watch?deskto...e.com/watch?v=xwe4sWH67dk&v=xwe4sWH67dk&gl=US
Download it
Extract it
Place into C Drive
Within the file are the drivers, Recovery and superuser
Just follow the Video and u should be ok
Sent from my Nexus S using xda premium

Revolutionary doesn't seem to work..

I have been messing around with this revolutionary tool for some time now.
I connect up my phone to my pc, enter htc sync mode and start up that program. After I enter my BETA key it works fine, until it enters Fastboot. It just sits there with that white screen while nothing happens, while on my CMD screen (on my pc) it says; "Waiting for fastboot..."
What did I do wrong? I followed this guide to the letter.

impy101 said:
I have been messing around with this revolutionary tool for some time now.
I connect up my phone to my pc, enter htc sync mode and start up that program. After I enter my BETA key it works fine, until it enters Fastboot. It just sits there with that white screen while nothing happens, while on my CMD screen (on my pc) it says; "Waiting for fastboot..."
What did I do wrong? I followed this guide to the letter.
Click to expand...
Click to collapse
Manually put phone into fastboot mode through bootloader then reconnect to pc
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium

Needs to be in charge only mode not htc sync.
sent from my Sensation XD

I have the same problem. Revolutionary doesn't detect my htc sensation regardless of mode. I don't know how to access the bootloader though.

impy101 said:
I have been messing around with this revolutionary tool for some time now.
I connect up my phone to my pc, enter htc sync mode and start up that program. After I enter my BETA key it works fine, until it enters Fastboot. It just sits there with that white screen while nothing happens, while on my CMD screen (on my pc) it says; "Waiting for fastboot..."
What did I do wrong? I followed this guide to the letter.
Click to expand...
Click to collapse
Have you checked your htboot in bootloader? I'm pretty sure you are on revolutionary hboot already. Now just find a recovery in PG58 file and update from fastboot, or use adb and push recovery.img using fastboot flash recovery recovery-image-name.img

tinky1 said:
Have you checked your htboot in bootloader? I'm pretty sure you are on revolutionary hboot already. Now just find a recovery in PG58 file and update from fastboot, or use adb and push recovery.img using fastboot flash recovery recovery-image-name.img
Click to expand...
Click to collapse
Now that is some heavy tech talk right there. I didn't learn any of that android talk so I'm just gonna walk away from rooting for now.

Dude its simple. Like so simple. Plug phone in to charge only revolutionary gives u all the info to fill in. Its easier than connecting the dots.
sent from my Sensation XD

Datastreamx said:
Now that is some heavy tech talk right there. I didn't learn any of that android talk so I'm just gonna walk away from rooting for now.
Click to expand...
Click to collapse
Lol. It's not near as bad as it looks. Just google things like hboot, bootloader, fastboot, adb and you'll be fine. It took me 2-3 non stop hours of reading when rooting Desire just to start to understand things. Once you get basic idea, learning goes a lot faster.

Or pay someone local to do it for you
sent from my Sensation XD

I suppose. Right now I'm stuck at unlocking the bootloader. when I want to get_identifier_token it just keeps endlessly waiting for my device. I noticed that it does so on anything. HTC Sync, revolution, fastboot, adb. Eh, I'll get through I suppose.
It also doesn't recognize it with the command "adb devices"

Start over. Download the revolutionary tool zip and extract it to your desktop in a new folder named(what ever the f%#k)
1. Plug phone into comp
2. Mount as disk drive
3. Copy superuser zip to ur sd card. Dont put it in folders but the root of ur sd card.
4. Mount as charge only.
5.make sure htc drivers are installed.
6. Type in your info at revolutionarys page to generate the beta key.
7. Type in the device serial number
8.hit enter, beta key created
9. Run revolutionary
10. Type in your beta key. If a letter is capital then capitalize the letter.
11. Hit enter and sit tight.
12. When it asks to download recovery type "Y" and hit enter
13. Revolutionary will close, now u are on the bootloader.
14. Push the power button on "bootloader. It will look for the pc36img. Dont worry about it.
15. Now were back at the bootloader. Use volume down to highlight recovery and push power.
16. Choose zip from sd.
17 find su 2.6.whateve its called.
18. Power to flash it. Now ur rooted go back and reboot.
I literally just told you each step to the T on how to do this. If your device isnt online then uninstall the htc drivers and reinstall. To uninstall the drivers go to device manager and uninstall by right click.
sent from my Sensation XD

If su fails to download find chainsdd site and dl the newest SU.zip
sent from my Sensation XD

Other noobs stuck in a loop?

I am a noob and I bricked my HTC Sensation 4G. (Admitting you have a problem is the first step.)
This was after the official OTA ICS update; rooted with S-ON, unlocked HBOOT 1.27. It was one of two things: 1) I was very lazy and used 1X to unlock Hboot, then subsequently flashed the HTC One X kernel without realizing it; 2) I inappropriately used writesecureflag 3.
Either way, I was stuck in a bootloop (white screen with green HTC) for the last week. I tried every solution I could find in in these forums to no avail, but I finally fixed it myself. If someone already posted these steps, sorry I wasn't trying to steal your thunder. I saw many others are having this problem, so I’m sharing my solution as a noob to noob how-to:
I did this on Windows 7, 64 bit to a T-mobile 4G model which was rooted with HTC Dev unlocked Hboot 1.27, S-ON, and CWM. It should work on other models, but I don’t know about other Hboots.
Update your SDK tools and drivers (excellent guide here) and download the stock RUU appropriate to your model (excellent guide here)
Remove your SIM card and insert an empty, formatted sd card into your phone
Put your phone in fastboot (easiest way is hold the ‘down’ volume button and power button on your Sensation at the same time, then select fastboot with the volume buttons and press power) and connect your device to a USB 2 port with a reliable USB cable. You should now see the words “fastboot usb”
Navigate to the folder containing adb and fastboot, press Shift and right click your mouse; select “open command window here”. At the prompt type “fastboot oem lock” (without quotation marks) and press enter. Your device should now say something like “Relocked” at the top and may say “Security Warning”. Don’t touch it.
Run the RUU executable that you downloaded earlier. It should take about 5-10 minutes and will then say that your device is ready for use, just wait for it to reboot on its own.
You should now be the proud owner of a shiny new LOCKED, UN-rooted device all ready to be screwed with again.:good:

bricked huawei g730

hello there,
I have huawei g730-u10
"MTK6582, quadcore cortex A7, 1GB Ram, 4GB Rom"
last week, I was trying to install a CWM recovery using "mobile uncle" app. after it finished , a prompt for restarting appears and I pressed "yes".
it was the last time seeing my phone alive!!! it restarts to huawei logo for about 20 seconds and restarts again and again and again....
unfortunately my device doesn't have a rom online, even on HUAWEI website, so, I downloaded a similar phone ROM "hdc-s5-gold" to use its preloader, cache, boot , etc
the problem is when I connect the phone to SP flashtools the red bar appears and then it holds for seconds and a message with connection loss appears while the phone is going in its infinite restart.. so the flashtools seems to find the phone for a while but fails to write to it thanks to power loss.
notes:
1. I have tried many flashtool versions
2. I have tried with and without battery connection, and with and without volume up holding.
3. the phone can't access to CWM, download mode or factory reset mode.
4. the drivers are installed shows: "MT65xx preloader" and I think there is no driver problem
5. even when I connect the phone to charger, it keeps restarting and the charging logo doesn't appear
I appreciate any help

SP log files attached
thanks

I have same problem.How to solve it.

same problem, what to do???

elkhopoa said:
hello there,
I have huawei g730-u10
"MTK6582, quadcore cortex A7, 1GB Ram, 4GB Rom"
last week, I was trying to install a CWM recovery using "mobile uncle" app. after it finished , a prompt for restarting appears and I pressed "yes".
it was the last time seeing my phone alive!!! it restarts to huawei logo for about 20 seconds and restarts again and again and again....
unfortunately my device doesn't have a rom online, even on HUAWEI website, so, I downloaded a similar phone ROM "hdc-s5-gold" to use its preloader, cache, boot , etc
the problem is when I connect the phone to SP flashtools the red bar appears and then it holds for seconds and a message with connection loss appears while the phone is going in its infinite restart.. so the flashtools seems to find the phone for a while but fails to write to it thanks to power loss.
notes:
1. I have tried many flashtool versions
2. I have tried with and without battery connection, and with and without volume up holding.
3. the phone can't access to CWM, download mode or factory reset mode.
4. the drivers are installed shows: "MT65xx preloader" and I think there is no driver problem
5. even when I connect the phone to charger, it keeps restarting and the charging logo doesn't appear
I appreciate any help
Click to expand...
Click to collapse
Universal unbrick guide:
Terminology - types of bricks:
Soft brick - often occurs in the shape of a bootloop or any other problems with booting such as always getting to recovery or not getting past the carrier logo. This type of a brick, which shows some signs of life, can in most cases be fixed.
Hard brick - As the name implies, your phone can essentially used as a brick and it shows no signs of life. This kind of a brick is rare and in theory should be unfixable. However there are advanced methods of fixing your phones such as JTAG, but they require extra tools and accessories.
The decision:
Is my phone soft or hard bricked?
If you answer yes to all of the questions below you probably have a hard birck:
Test as said in order!
Nothing happenes when you hold or press the power button
You cannot get the screen to even turn on by pressing or holding any combination of buttons on your phone
Nothing happenes if you do the same as about but with your phone plugged into a charger
Nothing happenes when you plug your phone into a computer
When you plug in your phone into a computer it does not recognize it as a phone, storage or any other media device
Nothing happenes when you try all of the above again, but with removing the battery in between steps for 10 seconds and putting it back in again
Nothing happenes when you try all of the above again, but after leaving the phone plugged into a charger for 2 hours
If all of the questions are a "yes", then you either have a broken charging port and and a discharged battery or you have a hard brick.
The unbricking:
There are many methods of unbricking and they are all different to each phone. Here I will list the most common methods that often succeed.
Samsung users skip to 4. method.
1. If you have access to a stock recovery:
Method 1:
1. Shut down / turn off your phone.
2. Boot into Recovery mode – hold down the volume down button and then hold the power button (the button combination is different for every phone. Look yours up on Google)
3. Use volume keys to navigate the menus, and power button to select the menu items (Again, might be different for every phone)
4. Choose “Wipe Cache Partition”.
5. Choose “Wipe Data / Factory Reset” to delete all your settings and apps, using the correct ROM.
6. Reboot your device.
Method 2:
Download the stock rom for your phone. It should be in ".zip" format. Make sure it's the official version
(Find it by Googling something like "[your phone model] stock rom")
Put the file on your phone's external SD card.
Make sure that the rom is for your exact phone model.
1. Shut down / turn off your phone.
2. Boot into Recovery mode – hold down the volume down button and then hold the power button (the button combination is different for every phone. Look yours up on Google)
3. Use volume keys to navigate the menus, and power button to select the menu items (Again, might be different for every phone)
4. Select "apply update from external storage"
5. Navigate to the zip file you copied to your phone
6. Install it.
If you get Status Error 7 that means you didn't download an official stock rom.
2. If you have access to a custom recovery:
Method 1:
Try stock recovery method 1
Method 2:
1. Find a stable custom rom for your phone or if you want to download the stock rom
Make sure that the rom is for your exact phone model.
2.. Copy the zip file to the phone's external SD.
3. Install the zip
(If you have a custom recovery you probably know the drill)
3. If you have access to fastboot mode:
First install ADB and fastboot drivers (if you haven't already):
To install it on windows there is a handy tool called the 15 Second ADB installer which will install pretty much everything you need.
On Ubuntu install with:
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
On Fedora:
Code:
sudo dnf install android-tools
On OS X using Homebrew:
Code:
brew install android-platform-tools
Once you have the drivers installed you have to find a recovery image for your phone to install a custom recovery.
You can try one of the popular recoveries such as CWM or TWRP.
You need to get the recoveryNameHere.img file for your phone.
Find it by Googling:
"[your phone model] TWRP recovery"
or
"[your phone model] CWM recovery"
Make sure that the recovery is for your exact phone model.
Now on your phone enter fastboot mode:
Turn your phone off.
You can try different button combinations. For my phone it's holding power and volume down buttons.
Once you're in fastboot mode plug your phone into a computer and open your terminal/cmd.
Type in:
Code:
fastboot devices
You should see a list of devices. There should be only one device ID number.
If you see the ID it's working. If you don't you didn't install the Google USB driver properly (on Windows) and if it says "'fastboot' is not a recognized command" or "No command 'fastboot' found" then you didn't even install your drivers.
If you have problems with installing Google "how to install adb and fastboot drivers"
Now that you know fastboot is working type in:
Code:
fastboot flash recovery C:\Path\To\Recovery.img
Replace "C:\Path\To\Recovery.img" with an actuall path of the recovery file you downloaded.
It should say success.
If it doesn't try to execute:
Code:
fastboot oem unlock
This will delete all data you had on your phone (games, game progress, apps...).
Now try
Code:
fastboot flash recovery C:\Path\To\Recovery.img
again.
Once you're done type in:
Code:
fastboot reboot
And your phone should still not work. Now what you have to do it try the custom recovery method above (number 2.)
4. If you have a Samsung device:
Try this tutorial of unbricking with Odin: click here

Soft bricked device, can't unlock, need help.

I'm on Android 5.0.1. I changed my PIN screen lock of my xperia and 20 minutes later I forgot it out of lots of things happening at once. I try to guess it 120 times (5.0 doesn't have "Enter google password" after x tries) without any progress (I was still at school at this point). I tried to boot to recovery and wipe it, but because I had Cyanogenmod recovery it didn't work. (it doesn't work at all, when I try to wipe it, it just displays the Android and flashes a few times and that's it.). At home, I tried to use Android Device Manager to erase it, but it just rebooted into Android. I tried to unlock the screen with the lock feature, but it didn't work at all, nothing happened (if I put something in the text field it allowed me to call owner. Pressing back or home puts me back in the lock screen "swipe up to unlock" state. I tried reflashing it with flashtool, but I couldn't even connect my device through ADB, it only said
Code:
04/034/2015 18:34:13 - INFO - Device connected with USB debugging off
04/034/2015 18:34:13 - INFO - For 2011 devices line, be sure you are not in MTP mode
even though USB debugging was on, even the notification said so. ADB just doesn't find it at all. When I plug my device in my computer the window that pops up says "This folder is empty". Am I really screwed? I guess my only chance is to keep guessing the password... I don't remember the first number or how many numbers were in it... help?

pefu19 said:
I'm on Android 5.0.1. I changed my PIN screen lock of my xperia and 20 minutes later I forgot it out of lots of things happening at once. I try to guess it 120 times (5.0 doesn't have "Enter google password" after x tries) without any progress (I was still at school at this point). I tried to boot to recovery and wipe it, but because I had Cyanogenmod recovery it didn't work. (it doesn't work at all, when I try to wipe it, it just displays the Android and flashes a few times and that's it.). At home, I tried to use Android Device Manager to erase it, but it just rebooted into Android. I tried to unlock the screen with the lock feature, but it didn't work at all, nothing happened (if I put something in the text field it allowed me to call owner. Pressing back or home puts me back in the lock screen "swipe up to unlock" state. I tried reflashing it with flashtool, but I couldn't even connect my device through ADB, it only said
Code:
04/034/2015 18:34:13 - INFO - Device connected with USB debugging off
04/034/2015 18:34:13 - INFO - For 2011 devices line, be sure you are not in MTP mode
even though USB debugging was on, even the notification said so. ADB just doesn't find it at all. When I plug my device in my computer the window that pops up says "This folder is empty". Am I really screwed? I guess my only chance is to keep guessing the password... I don't remember the first number or how many numbers were in it... help?
Click to expand...
Click to collapse
Hi bro.
Download this file Here.
Extract it on your desktop.
Now this file will install the cwm recovery.
Open a command window in the folder you have extracted.
Type
fastboot flash boot boot.IMG
Now before pressing enter you just need to power off your phone connecting it to the computer while holding volume + key .
Now you can press enter.
After you flash the recovery boot to recovery and make a factory reset.
Note: after this process the WiFi may not work you just need to install this app http://forum.xda-developers.com/xperia-l/development/app-recoveries-recovery-installer-t3187915 and give root and install TWRP.
And don't worry windows won't show the internal or the external memory because your phone is locked it's kind of protecting your files .
Don't forget to hit thanks

n78 shadow said:
Hi bro.
Download this file Here.
Extract it on your desktop.
Now this file will install the cwm recovery.
Open a command window in the folder you have extracted.
Type
fastboot flash boot boot.IMG
Now before pressing enter you just need to power off your phone connecting it to the computer while holding volume + key .
Now you can press enter.
After you flash the recovery boot to recovery and make a factory reset.
Note: after this process the WiFi may not work you just need to install this app http://forum.xda-developers.com/xperia-l/development/app-recoveries-recovery-installer-t3187915 and give root and install TWRP.
And don't worry windows won't show the internal or the external memory because your phone is locked it's kind of protecting your files .
Don't forget to hit thanks
Click to expand...
Click to collapse
I did what you told me to do, and it says < waiting for device > in the console. The device displays a blue LED after I volume+ and plug the USB in. I then enter the command and it's just stuck at < waiting for device >.

pefu19 said:
I did what you told me to do
Click to expand...
Click to collapse
Did you have fastboot driver installed?
If not go to flashtool folder then to drivers there you will see a exe file ,open it and install fastboot drivers and xperia l derivers.
Edit: and I think it should be installed automatically by windows just wait for it.

n78 shadow said:
Did you have fastboot driver installed?
If not go to flashtool folder then to drivers there you will see a exe file ,open it and install fastboot drivers and xperia l derivers.
Edit: and I think it should be installed automatically by windows just wait for it.
Click to expand...
Click to collapse
I think I have them installed, but when I go to the flashtool drivers folder and install those drivers, I select xperia L drivers and the 2 on top, it says Install Failed for all of them

What windows do you use???
If 8 I think it won't work , you should try it on another one

n78 shadow said:
What windows do you use???
If 8 I think it won't work , you should try it on another one
Click to expand...
Click to collapse
I have Windows 10 x64

pefu19 said:
I have Windows 10 x64
Click to expand...
Click to collapse
Sorry bro that won't work try it on another computer with 7 or lower.
Don't forget to hit thanks if I hleped you

pefu19 said:
I have Windows 10 x64
Click to expand...
Click to collapse
windows 10 has a special 3rd party driver protection... you must disable it and install fastboot driver... AND you need a USB2.0 because 3.0 has known issues
Sent from my Xperia T using XDA Free mobile app

In Window 10 go to setting>update&security>Recovery>Advanced startup and restart pc >then choose troubleshoot>Advanced Option>Startup Setting and restart>and it will ask option choose Disable Driver signature enforcement and done......
if you have any problem ask...:laugh:

Database Info

welcome