Database Info

[SOLVED] Recovery and fastboot problems (soft bricked?)

I was given my friends tablet to try and fix for him. Basically the recovery (TWRP 2.5.0.0) cannot mount any partitions at all (and asks for a password for some reason - can be bypassed with the cancel button). The tablet will boot straight into the recovery mentioning that no OS is installed. I have attempted to boot into fastboot to flash an older version of the recovery (which I've read up on a few websites that say it will fix the mounting problem) however while pressing VOL DOWN and POWER it will boot up to the ASUS logo and no message appears about fastboot in the top-left. I'm out of ideas now and the only way I'll be able to fix this (from what I know) is either by flashing the ASUS firmware or an older version of TWRP via fastboot. Has anyone got any ideas on how I can fix this? Thanks.
EDIT: May be of reference https://github.com/TeamWin/Team-Win-Recovery-Project/issues/138
EDIT 2: I have finally solved the problem! I have quoted the important parts below in case anyone else has the same problem.
Basically I had some problems with the drivers the whole time on Windows 8. So what I did was disabled driver signature enforcement in Windows 8 (I think it re-enables after some time). I downloaded the drivers from this post and followed this other post , specifically this part:
jpasher said:
Making Windows recognize the TF300T
You will need to add the hardware IDs for the TF300T in the driver to make it recognize the ADB interface
Open the file android_winusb.inf in the naked drivers directory.
Look for the section titled [Google.NTx86] (for 32-bit systems) or [Google.NTamd64] (for 64-bit systems)
Add the following lines to make it recognize the TF300T hardware (it doesn't matter where, but I put it after the existing entries for the TF201 APX interface)
Code:
%AsusTransformerADBInterface% = USB_Install, USB\VID_0B05&PID_4C81&REV_0232&MI_01
%AsusTransformerADBInterface% = USB_Install, USB\VID_0B05&PID_4C81&MI_01
%AsusTransformerADBInterface% = USB_Install, USB\VID_0B05&PID_4C83&REV_0232
%AsusTransformerADBInterface% = USB_Install, USB\VID_0B05&PID_4C83
After the information is added, you should be able to install the drivers as usual for the device. If for some reason the device is still not recognized, you'll need to find its hardware IDs and add those to the file.
Click to expand...
Click to collapse
Then I booted up the tablet and connected to my computer. The drivers finally worked! I went into command prompt and typed "adb devices" and the device was there! Then I typed "adb reboot bootloader" and I got into the bootloader.
I had to look for the SKU too and since I couldn't find it cause I couldn't boot into Android it was in really small text in the bootloader at the top. Unfortunately after trying to flash the firmware in the bootloader it would not write over the system every time. So I followed this post instead: http://forum.xda-developers.com/showpost.php?p=49164067&postcount=167
After following the procedure it finally worked! Thanks cmendonc2 and everyone for your help, my friend is happy!

firtvid20 said:
I was given my friends tablet to try and fix for him. Basically the recovery (TWRP 2.5.0.0) cannot mount any partitions at all (and asks for a password for some reason - can be bypassed with the cancel button). The tablet will boot straight into the recovery mentioning that no OS is installed. I have attempted to boot into fastboot to flash an older version of the recovery (which I've read up on a few websites that say it will fix the mounting problem) however while pressing VOL DOWN and POWER it will boot up to the ASUS logo and no message appears about fastboot in the top-left. I'm out of ideas now and the only way I'll be able to fix this (from what I know) is either by flashing the ASUS firmware or an older version of TWRP via fastboot. Has anyone got any ideas on how I can fix this? Thanks.
EDIT: May be of reference https://github.com/TeamWin/Team-Win-Recovery-Project/issues/138
Click to expand...
Click to collapse
What bootloader is it on? It is on the top left corner of the screen wneh you enter the recovery menu in the bootloader.

cmendonc2 said:
What bootloader is it on? It is on the top left corner of the screen wneh you enter the recovery menu in the bootloader.
Click to expand...
Click to collapse
It doesn't say in TWRP recovery. When I boot the device straight up in the top-left corner it saw device is unlocked. However holding VOL DOWN does nothing and the tablet boots straight into TWRP

firtvid20 said:
It doesn't say in TWRP recovery. When I boot the device straight up in the top-left corner it saw device is unlocked. However holding VOL DOWN does nothing and the tablet boots straight into TWRP
Click to expand...
Click to collapse
You can still use fastboot in TWRP, but you will need to find the bootloader in order to figure out which recovery to flash over TWRP. There should be a fastboot command to find out.

cmendonc2 said:
You can still use fastboot in TWRP, but you will need to find the bootloader in order to figure out which recovery to flash over TWRP. There should be a fastboot command to find out.
Click to expand...
Click to collapse
Okay that's good to know. I am still unfortunately not able to get into fastboot. So I'll have to figure out what version the bootloader is before flash the firmware over.

Okay I got access to APX mode (useless from my understanding since my friends has no backups via nvflash), the bootloader while the recovery is loaded (although the driver isn't working for the bootloader), but I CANNOT GET INTO THE BOOTLOADER VIA VOLUME DOWN + POWER. Please help, somebody!

Here's a video explaining my problem.

firtvid20 said:
Here's a video explaining my problem.
Click to expand...
Click to collapse
Have you tried pressing the reset pin, then going into TWRP and going into ADB mode.
Then type ADB reboot bootloader and then try getting into fastboot by pressing volume down.

cmendonc2 said:
Have you tried pressing the reset pin, then going into TWRP and going into ADB mode.
Then type ADB reboot bootloader and then try getting into fastboot by pressing volume down.
Click to expand...
Click to collapse
Hmm I'll give that a go. Is ADB already on when I'm in TWRP? Otherwise how do I get into ADB mode?

firtvid20 said:
Hmm I'll give that a go. Is ADB already on when I'm in TWRP? Otherwise how do I get into ADB mode?
Click to expand...
Click to collapse
Its an option somewhere in TWRP called "ADB sideload".

cmendonc2 said:
Its an option somewhere in TWRP called "ADB sideload".
Click to expand...
Click to collapse
I tried it out but I get the the message "ADB Sideload Complete" and below it a message in red" Failed". I have it plugged into the computer and I didn't hear a connection sound.
I have also looked in Device Manager and there is the Transformer with no driver loaded with it. Further searching using the device information gave me this link: http://binarydb.com/driver/ASUS-Android-Bootloader-Interface-208738.html
EDIT: Found a driver on softpedia and installed it: http://drivers.softpedia.com/get/Ot...iver-4004-for-Vista-Windows-7-Windows-8.shtml Doesn't look like it's working though.

firtvid20 said:
I tried it out but I get the the message "ADB Sideload Complete" and below it a message in red" Failed". I have it plugged into the computer and I didn't hear a connection sound.
I have also looked in Device Manager and there is the Transformer with no driver loaded with it. Further searching using the device information gave me this link: http://binarydb.com/driver/ASUS-Android-Bootloader-Interface-208738.html
EDIT: Found a driver on softpedia and installed it: http://drivers.softpedia.com/get/Ot...iver-4004-for-Vista-Windows-7-Windows-8.shtml Doesn't look like it's working though.
Click to expand...
Click to collapse
While the ADB is attempting to connect, reinstall the naked drivers. If you are on Windows 8, use test mode.

cmendonc2 said:
While the ADB is attempting to connect, reinstall the naked drivers. If you are on Windows 8, use test mode.
Click to expand...
Click to collapse
Sorry, what is test mode? I am on Windows 8.

firtvid20 said:
Sorry, what is test mode? I am on Windows 8.
Click to expand...
Click to collapse
This should help: http://www.wugfresh.com/faq/8/

cmendonc2 said:
This should help: http://www.wugfresh.com/faq/8/
Click to expand...
Click to collapse
Hi cmendonc. I have already disabled driver signature enforcement. I have installed the drivers however I don't think I've had luck with them unfortunately.

firtvid20 said:
Hi cmendonc. I have already disabled driver signature enforcement. I have installed the drivers however I don't think I've had luck with them unfortunately.
Click to expand...
Click to collapse
Hmm. Try using a different USB cable ( if u have it) or a different USB port.

cmendonc2 said:
Hmm. Try using a different USB cable ( if u have it) or a different USB port.
Click to expand...
Click to collapse
I tried out both USB 2.0 and 3.0 ports on my computer but I still have the failed message come up. Any ideas still?

firtvid20 said:
I tried out both USB 2.0 and 3.0 ports on my computer but I still have the failed message come up. Any ideas still?
Click to expand...
Click to collapse
I vaguely remember someone posting that he succeeded to use adb/fastboot by installing a VirtualBox with Linux. You might have to search for the details.
Sent from my TF300T using Tapatalk

cmendonc2 said:
Hmm. Try using a different USB cable ( if u have it) or a different USB port.
Click to expand...
Click to collapse
Just an update. I got it working!! I did the following on this post to the universal drivers and then tried installing them on Windows 8. After booting my tablet to TWRP and plugging it in to my computer ADB works! I can reboot into fastboot now. Now I either have the option of flashing a JB compatible recovery or flashing the Asus firmware...

Since I'm not able to boot into Android would anyone be able to tell me what is the SKU on the picture below? So I can flash the correct firmware.
EDIT: Found it in the bootloader in small text. -.- It was the "WW" version.

[Q] Nexus 5 shows up in ADB but not Fastboot

So recent got my Nexus 5 and have decided to root it, I've been following this guide http://forum.xda-developers.com/showthread.php?t=2507905 however I cannot get past the part where I need to type
Code:
fastboot devices
Simply because my device doesn't show up, nothing does.
My device does show up in adb devices though which seems odd, Yes I'm in fastboot when i use fastboot devices. I have tried all the methods from the guide on trying to fix the drivers but to no avail, any help would be greatly appreciated. Thanks

Try these drivers: http://forum.xda-developers.com/showthread.php?t=2588979

Chromium_ said:
Try these drivers: http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Still shows up in ADB but not fastboot

Krashem said:
Still shows up in ADB but not fastboot
Click to expand...
Click to collapse
Watch this guide.

Chromium_ said:
Watch this guide.
Click to expand...
Click to collapse
Still not working, followed the guide exactly. I'm not sure if this helps but when I plug my Nexus in while its in fastboot windows says its an unrecognized device.

Krashem said:
Still not working, followed the guide exactly. I'm not sure if this helps but when I plug my Nexus in while its in fastboot windows says its an unrecognized device.
Click to expand...
Click to collapse
Did you do the thing at the end of the guide (around 3:40)? You need to go into device manager where the phone is unrecognized and select the appropriate drivers.

Chromium_ said:
Did you do the thing at the end of the guide (around 3:40)? You need to go into device manager where the phone is unrecognized and select the appropriate drivers.
Click to expand...
Click to collapse
I think hes using W7 whereas I'm using 8.1, the part with all the drivers come up for him (e.g. Android Phone) doesn't show for me. I would post a picture although I don't think I can yet..

Krashem said:
I think hes using W7 whereas I'm using 8.1, the part with all the drivers come up for him (e.g. Android Phone) doesn't show for me. I would post a picture although I don't think I can yet..
Click to expand...
Click to collapse
With windows 8 this is what you'll need to do to get the drivers installed.

Chromium_ said:
With windows 8 this is what you'll need to do to get the drivers installed.
Click to expand...
Click to collapse
Tried this before also didn't make a lot of difference

Krashem said:
Tried this before also didn't make a lot of difference
Click to expand...
Click to collapse
weird, it must be something wrong.
did you try changing usb port, cable...
any way, simple steps,
uninstall driver,
for window 8.1:
1) From the Window 8.1 Start screen, move your mouse to the top (or bottom) right corner, and click Settings;
2) Click "Change PC Settings";
3) click Update and Recovery;
4) Under Advanced startup, click "Restart Now";
5) Wait for it to restart;
6) Click "Troubleshoot";
7) Click "Advanced options";
8) Click "Startup settings";
9) Click "Restart";
10) Wait for it to restart;
11) Press F7 (i.e, the F7 function key);
Now you can install the driver.

Dont worry I got it to work, thanks for all your help. I missed something while I was uninstalling previous fail attempt drivers..

I now have another issue I have unlocked bootloader and flashed ClockworkMod recovery but I cant push the SuperSU zip. It keeps telling me the device is not found and it is also not showing up in adb devices while I'm in recovery..

Krashem said:
I now have another issue I have unlocked bootloader and flashed ClockworkMod recovery but I cant push the SuperSU zip. It keeps telling me the device is not found and it is also not showing up in adb devices while I'm in recovery..
Click to expand...
Click to collapse
Just boot it up normally and download SuperSU from the phones browser: download.chainfire.eu/supersu
Then go back into recovery and flash it.

[Q] oneplus one stuck at boot menu and ADB sideload refusing

hello everybody,
so my phones speakers stopped working and I couldn't fix them so I went to twrp recovery and executed a factory reset. This resulted in the device hanging at the boot screen. I then spent half an hour trying to get the drivers working and when it finally saw the phone and I wanted to sideload the 33R zip it just gave me this long list with possible command (see screenshot attached).
in fastboot it's not seeing the phone for some reason
I have access to the following:
TWRP Recovery
Fastboot
Any idea on how to get my phone working again?

RacerBas said:
hello everybody,
so my phones speakers stopped working and I couldn't fix them so I went to twrp recovery and executed a factory reset. This resulted in the device hanging at the boot screen. I then spent half an hour trying to get the drivers working and when it finally saw the phone and I wanted to sideload the 33R zip it just gave me this long list with possible command (see screenshot attached).
in fastboot it's not seeing the phone for some reason
I have access to the following:
TWRP Recovery
Fastboot
Any idea on how to get my phone working again?
Click to expand...
Click to collapse
Do you have a backup or even a ROM zip on the phone you can install from TWRP?

bp328i said:
Do you have a backup or even a ROM zip on the phone you can install from TWRP?
Click to expand...
Click to collapse
If I had I wouldn't be here

RacerBas said:
If I had I wouldn't be here
Click to expand...
Click to collapse
First on your PC try typing adb devices it should return the device serial number in the command prompt.
If it does then in TWRP click advanced, ADB Sideload, then swipe the blue arrow.
Then on your PC command prompt type adb sideload "ROM/File Name.zip" without the quotes.
It should load from there.

bp328i said:
First on your PC try typing adb devices it should return the device serial number in the command prompt.
If it does then in TWRP click advanced, ADB Sideload, then swipe the blue arrow.
Then on your PC command prompt type adb sideload "ROM/File Name.zip" without the quotes.
It should load from there.
Click to expand...
Click to collapse
That's what I tried but it came up with what's shown in the screenshot

RacerBas said:
That's what I tried but it came up with what's shown in the screenshot
Click to expand...
Click to collapse
Ok try adb push "ROM/File.zip" /sdcard
That will put the rom zip on the root of your sdcard and you can flash from there.

bp328i said:
Ok try adb push "ROM/File.zip" /sdcard
That will put the rom zip on the root of your sdcard and you can flash from there.
Click to expand...
Click to collapse
I'm getting this now: error: closed
attached a screenshot of how the phone turns up in windows

RacerBas said:
I'm getting this now: error: closed
attached a screenshot of how the phone turns up in windows
Click to expand...
Click to collapse
After it shows my device id number it says recovery, yours says host? Are you doing this with TWRP booted?
Hold on it looks like you need to update your drivers...

bp328i said:
After it shows my device id number it says recovery, yours says host? Are you doing this with TWRP booted?
Hold on it looks like you need to update your drivers...
Click to expand...
Click to collapse
yea, I've been trying to get that working for a while, guess I got the wrong ones. That would explain everything though XD

RacerBas said:
yea, I've been trying to get that working for a while, guess I got the wrong ones. That would explain everything though XD
Click to expand...
Click to collapse
Try uninstalling the ones you have and installing this one.
https://github.com/koush/UniversalAdbDriver
Good luck man, I've got to get back to work.
I know the adb push "ROM/File.zip" /sdcard works because I tested on my phone prior to posting.
One last thought is your SDK might need to be updated as well.

bp328i said:
Try uninstalling the ones you have and installing this one.
https://github.com/koush/UniversalAdbDriver
Click to expand...
Click to collapse
Currently trying it on my laptop which has a fresh reinstall, removing the drivers completely will take too long.
Your driver saw it as a google galaxy nexus adb Interface, when I used adb devices it didn't see it.
EDIT: when I go to reboot it says that there is no os installed so yea...
Another Edit: I will try this driver when I get home and report back. OnePlus adb drivers windows

I managed to fix it using the oneplus one toolkit by manudroid

[Q] Retrieving files with a dead screen

Hello,
I just broke my nexus 5 screen but the device is still working. I'd like to retrieve some files from my phone before buying a new one, like pictures or SMS for example.
Here is what I can do :
- Boot in fastboot mode
- Flash a custom recovery (ex : TWRP)
Here is what is not working :
- Device is not recognized in Windows file folder, then I suppose that MTP is not enabled
- no developer mode enabled
- no USB debugging mode enabled
- Then ADB is not working
By the way, the device is not unlocked and not rooted.
I tried to flash and boot into TWRP mode but I don't know how to "drive" it from my computer as the device screen is not working.
Could somebody help me please ?

pilipe75 said:
Hello,
I just broke my nexus 5 screen but the device is still working. I'd like to retrieve some files from my phone before buying a new one, like pictures or SMS for example.
Here is what I can do :
- Boot in fastboot mode
- Flash a custom recovery (ex : TWRP)
Here is what is not working :
- Device is not recognized in Windows file folder, then I suppose that MTP is not enabled
- no developer mode enabled
- no USB debugging mode enabled
- Then ADB is not working
By the way, the device is not unlocked and not rooted.
I tried to flash and boot into TWRP mode but I don't know how to "drive" it from my computer as the device screen is not working.
Could somebody help me please ?
Click to expand...
Click to collapse
Then i suppose there is nothing you can do if almost nothing works and adb doesn`t recognise your phone, good luck mate
BTW next time enable google foto`s backup.

gee2012 said:
Then i suppose there is nothing you can do if almost nothing works and adb doesn`t recognise your phone, good luck mate
Click to expand...
Click to collapse
Using ADB would have been to easy
There is nothing I can do with a custom recovery ? or a modified boot ?

pilipe75 said:
Using ADB would have been to easy
There is nothing I can do with a custom recovery ? or a modified boot ?
Click to expand...
Click to collapse
You can`t, the bootloader is locked so you can`t flash custom stuff like a recovery. And even then you couldn`t know what buttons you`ld press if you can`t see what you`re doing.

gee2012 said:
You can`t, the bootloader is locked so you can`t flash custom stuff like a recovery.
Click to expand...
Click to collapse
I can unlock and root it, but I guess that it'll erase everything, right ?

pilipe75 said:
I can unlock and root it, but I guess that it'll erase everything, right ?
Click to expand...
Click to collapse
Unlocking the device wipes the device, so this kills the whole purpouse of your question. Might as well do nothing and get the phone repaired or buy a another one.

gee2012 said:
Unlocking the device wipes the device, so this kills the whole purpouse of your question. Might as well do nothing and get the phone repaired or buy a another one.
Click to expand...
Click to collapse
ok thanks for your help I'm still opened to news ideas if somebody is able to do miracles.
It's Christmas after all

pilipe75 said:
Here is what I can do :
- Flash a custom recovery (ex : TWRP)
By the way, the device is not unlocked and not rooted.
Click to expand...
Click to collapse
if bl is not unlocked... you won't be able to flash a custom recovery to use ADB to pull files.. so.. you're done here.

I maybe found a solution but I need a specific apk.
I may use the sideload mode to push and install a ROM or an apk. The best would be to push/install an apk from sideload mode, and this apk would automatically launch itself at device startup and will activate USB debugging mode which will allow me to fully use adb.
What do you think about that ? Would you know an apk which would do that ?
Or secondary option, push a specific ROM with USB debugging enabled by default. But I'm afraid that it could erase all my data.

Have you tried a TV out adapter?

rootSU said:
Have you tried a TV out adapter?
Click to expand...
Click to collapse
Great idea but i don't have any and, above all i'm afraid that the touch screen is not working either, so i'm not sure if it could really help

pilipe75 said:
Great idea but i don't have any and, above all i'm afraid that the touch screen is not working either, so i'm not sure if it could really help
Click to expand...
Click to collapse
Well I guess you're a bit stuck unfortunately.

Can you try ubuntu.
download a live cd version and boot into ubuntu or maybe a smaller version of linux (i know ubuntu works)
once booted into ubuntu plug in the phone.
usually linux can read the file system even when windows can't

You can't flash anything unsigned with stock recovery.
a hammerhead wrote this.

qnc said:
Can you try ubuntu.
download a live cd version and boot into ubuntu or maybe a smaller version of linux (i know ubuntu works)
once booted into ubuntu plug in the phone.
usually linux can read the file system even when windows can't
Click to expand...
Click to collapse
It's not working

pilipe75 said:
It's not working
Click to expand...
Click to collapse
We don't even know if your phone boots up... Does it ring when you call it?

rootSU said:
We don't even know if your phone boots up... Does it ring when you call it?
Click to expand...
Click to collapse
Yes it does. And it's responding in fastboot and sideload mode. So the phone is working, it's just the screen which ia dead.

The only way is to install a custom recovery. There is no other way. However as you said, unlocking the bootloader will erase everything.

pilipe75 said:
Yes it does. And it's responding in fastboot and sideload mode. So the phone is working, it's just the screen which ia dead.
Click to expand...
Click to collapse
... But your bootloader is locked and you think you have stock recovery and MTP mode doesn't work?

pilipe75 said:
Yes it does. And it's responding in fastboot and sideload mode. So the phone is working, it's just the screen which ia dead.
Click to expand...
Click to collapse
sorry that did not work.
when connected to ubuntu and you type "fastboot devices" do you get a response?
If so ubuntu can not browse file system in fastboot mode, you need to reboot back to the OS.
type fastboot reboot and when the phone reboots try to browse the file system.

[Q] How to install custom ROM on stock phone (HBOOT 1.xx/2.xx)

I'm really new to this, and don't want to break my device.
What exact steps do I have to do to root my device, and install a custom rom on it?
Got the HTC One S

rifek4 said:
http://forum.xda-developers.com/wiki/HTC_One_S
http://forum.xda-developers.com/showthread.php?t=2076086
http://forum.xda-developers.com/showthread.php?p=51291053
Links are a little bit older but good. Look at forum General and Development category for more stuff.. You must first do a unlock bootloader, then flash custom recovery (newest unofficial TWRP is best), then you can install new ROM which doesn't need S-OFF/superCID after that flash new kernel for it ROM via fastboot. You must looking some thread's on forum, explore the possibilities, find out what and how you can use... I can't say you everything in one word - I don't have such power
Click to expand...
Click to collapse
I tried all this, but once I get in the bootloader and try to get my "Token ID" or whatever to root it, it just says device not found and that its waiting for device.
Its in USB Debugging mode, and the drivers are fine, its latest drivers and the command to goto bootloader works fine.
Not sure what to do.
I appreciate you taking the time to link me all this though
Just not sure how to do it, I'm probably doing something wrong.
But I got as far as getting to the bootloader.

rifek4 said:
http://forum.xda-developers.com/showthread.php?t=1583427
Try unlock with this thread, not with toolkit. You use newest HTC Drivers? Delete old drivers, install this one then restart PC and try again with above thread.
Click to expand...
Click to collapse
In fastboot menu, got the CMD in right directory, typed the command to get identifier token, says "Waiting For Device..."
Still same issue :/

rifek4 said:
You do reinstall drivers? You see "FASTBOOT USB" text on fastboot menu after connect cable?
Click to expand...
Click to collapse
Says "FASTBOOT" with red highlight.
Then just has instructions, says "BOOTLOADER", Reboot, Reboot Bootloader and Power Down as options.
Also, said that driver you linked isn't compatible with my OS.
I'm on Windows 8.1
Edit: Followed those instructions, went back to repeat and try again. Still did same thing, saying waiting for device.

rifek4 said:
So is not good. After connect USB cable there must be "FASTBOOT USB" text. Check link now, I change URL. If you are on Windows 8.1 install new drivers from right URL (I change now one post before) and look HERE.
Click to expand...
Click to collapse
Says Fastboot USB now.
Going to try it out!

LunarSAF said:
Says "FASTBOOT" with red highlight.
Then just has instructions, says "BOOTLOADER", Reboot, Reboot Bootloader and Power Down as options.
Also, said that driver you linked isn't compatible with my OS.
I'm on Windows 8.1
Edit: Followed those instructions, went back to repeat and try again. Still did same thing, saying waiting for device.
Click to expand...
Click to collapse
Fastboot Win 8.1 fix
Latest official driver
Seems as you already got it

rifek4 said:
So is not good. After connect USB cable there must be "FASTBOOT USB" text. Check link now, I change URL. If you are on Windows 8.1 install new drivers from right URL (I change now link in this post before or they are JUST HERE) and look HERE. You must do fix fastboot for Windows 8.1.
Click to expand...
Click to collapse
Installing that driver now.
Then going to restart PC and reconnect phone, will let you know if it works!

rifek4 said:
Link for fix doesn't work I give him the same version drivers
Click to expand...
Click to collapse
Links fixed

rifek4 said:
After it, do a also fix fastboot for Windows 8.1
Click to expand...
Click to collapse
Sweet, just got the token! Doing the rest of the tutorial!
Believe everything is going to work now
This happened on next step:
c:\fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Too many links))
finished. total time: 0.000s

rifek4 said:
Good luck!
EDIT:
Try again, reconnect phone etc.
Click to expand...
Click to collapse
Tried reconnecting phone, bootloader says "Fastboot USB" and everything, tried to put it in and still same error.

rifek4 said:
Reboot phone / reboot PC / try again?
P.S.
Sorry for asking again but you do fix for Win 8.1 ?
Click to expand...
Click to collapse
Just rebooted phone, restarted PC and did the Win 8.1 Fix thing.
Still failed D:

LunarSAF said:
Just rebooted phone, restarted PC and did the Win 8.1 Fix thing.
Still failed D:
Click to expand...
Click to collapse
Generate a new unlocktoken
BTW did you uninstall HTC sync?

LS.xD said:
Generate a new unlocktoken
BTW did you uninstall HTC sync?
Click to expand...
Click to collapse
Got it working!
Now, I'm at Step 3.
Issue is, when I go to recovery, it doesn't actually open ClockWorkMod which is the one I installed. http://www.clockworkmod.com/rommanager (6.0.4.8).
It said everything went fine in command prompt, but just boots the device instead of recovery.
Should I try with the Paul one?

LunarSAF said:
Got it working!
Now, I'm at Step 3.
Issue is, when I go to recovery, it doesn't actually open ClockWorkMod which is the one I installed. http://www.clockworkmod.com/rommanager (6.0.4.8).
It said everything went fine in command prompt, but just boots the device instead of recovery.
Should I try with the Paul one?
Click to expand...
Click to collapse
Flash TWRP 2.8.5.0
Recovery can be entered by starting up bootloader mode and select "recovery"

rifek4 said:
Why not unofficial TWRP v2.8.5.5?
Click to expand...
Click to collapse
Missing option to clean sd card. And the developer says "should work, give me feedback". As @LunarSAF just starts modding the phone official should totally do it. At least he shouldn't go for CWM.

Trying to flash TWRP v2.8.5.0
sending 'recovery' is taking forever, and hasn't finished yet.
Will edit post with results once its finished!
Not sure why its taking so long.
Edit: been a while, decided to try and restart it, reconnected phone and new CMD.
Still didn't work.
"fastboot flash recovery twrp.img"
Edit: Nvm just finished.
Going to get into recovery, install SU and see how it goes from there!

Hmm....
I put the TWRP v2.8.5.0 on the device.
Tried to get into Recovery, and it just rebooted device, wouldn't get into recovery.

rifek4 said:
Flash THIS ONE - unofficial TWRP v2.8.5.5.
Click to expand...
Click to collapse
That link doesn't work :/ Found twrp-2.8.5.5-ville.img online though.
Will that work?

rifek4 said:
Link changed. Yes I think. After write unlocktoken you choose right option on display your phone? Vol + & Power button to confirm unlock?
Click to expand...
Click to collapse
Just restarted from write unlocktoken part.
Put it in to flash it and it said it did it successfully, but isn't showing up with anything to confirm.
Confirmed something way earlier when I did it though, so might not have to do it again.
Going to try writing TWRP again and booting into recovery.
Edit: Just did that, tried to go in recovery now and it doesn't work. It just reboots the device. Don't understand why.

rifek4 said:
For me wipe internal storage option work without problems
Click to expand...
Click to collapse
On HBOOT 2.15 the option is totally missing