Database Info

[q] nexus s 4g cant flash stock plz help!!!!

I can do everything with my phone except for flash stock no matter how many times and ways I try it won't work. Have tried using SW Updater and it gives me the following message:
"Error Occured! Cancel Download!"
I also tried with fastboot and after the phone reboots I get this message:
<waiting for device>
For some reason the phone continues to show these two lines at the bottom of the bootloader screen:
USB Control Init
USB Control Init End
I am really in need of help. Can somebody please help me?

KJOM said:
I can do everything with my phone except for flash stock no matter how many times and ways I try it won't work. Have tried using SW Updater and it gives me the following message:
"Error Occured! Cancel Download!"
I also tried with fastboot and after the phone reboots I get this message:
<waiting for device>
For some reason the phone continues to show these two lines at the bottom of the bootloader screen:
USB Control Init
USB Control Init End
I am really in need of help. Can somebody please help me?
Click to expand...
Click to collapse
Hi,
What are coming from? rooted with what ROM.. what recovery?
And are you trying to flash the newest ICS from stock recovery?
I guess Im just trying to see what you did and what you had before it all happened.
Thanks

Im currently running the [AOSP][4.0.4]Codename Android 2.0.0RC|Fully Open Source+Nightly Builds Rom and I have CWM Recovery and I am trying to flash the OTA ICS Update.

http://forum.xda-developers.com/showthread.php?p=24297394
[OFFICIAL][ROM][CWM] NS4G IMM76D 4.0.4 | Rooted | Zipalign | ETC
This is what u want if ur already rooted
Good luck
Vs Nexus S 4G

I already know how to do everything else, my problem is flashing back to stock because of those messages. I only want to flash back to stock.

I had an issue where fastboot wouldn't recognize my device when I was in bootloader. For whatever reason it worked if I hooked up my phone via usb then rebooted into bootloader.
Anyway you can use this method
http://forum.xda-developers.com/showthread.php?t=1575502
Sent from my Nexus S 4G using Tapatalk 2

Did you install the wrong bootloader by any chance?

KJOM said:
I already know how to do everything else, my problem is flashing back to stock because of those messages. I only want to flash back to stock.
Click to expand...
Click to collapse
That's why I asked for some clarity on ur post.
U want to Unroot and return to stock.
Its a big difference when someone reads and tried to help.
What root method did u use?
Vs Nexus S 4G

@vidaljs, I used the fastboot method to install IMM26D & @psg190, I don't think so.

KJOM said:
@vidaljs, I used the fastboot method to install IMM26D & @psg190, I don't think so.
Click to expand...
Click to collapse
Boot into the bootloader (volume up + power button) and tell me what it says for bootloader version.

It says:
FATBOOT MODE
PRODUCT NAME -HEARING
HW VERSION - D720SPAKE1
BASEBAND VERSION - D720SPALC1
CARRIER INFO - SPR
SERIAL NUMBER - 32************EC
LOCK STATE - UNLOCKED
SELECT - VOL UP or VOL DOWN
EXCUTE - POWER
REBOOT BOOTLOADER
REBOOT
RECOVERY
POWER OFF
USB Control Init
USB Control Init End

KJOM said:
It says:
FATBOOT MODE
PRODUCT NAME -HEARING
HW VERSION - D720SPAKE1
BASEBAND VERSION - D720SPALC1
CARRIER INFO - SPR
SERIAL NUMBER - 32************EC
LOCK STATE - UNLOCKED
SELECT - VOL UP or VOL DOWN
EXCUTE - POWER
REBOOT BOOTLOADER
REBOOT
RECOVERY
POWER OFF
USB Control Init
USB Control Init End
Click to expand...
Click to collapse
Well, that's good that you have the right bootloader. Mine had the same problem, but I accidentally flashed the wrong bootloader. Pretty sure that's why I had no fastboot or USB mount. I had to send mine into Samsung for repairs.

So what's wrong with it?

KJOM said:
So what's wrong with it?
Click to expand...
Click to collapse
With yours? I don't know.
With mine? I don't know.

lol dam

KJOM said:
lol dam
Click to expand...
Click to collapse
Sent my jacked up phone into Samsung. It was unlocked and had TWRP on it (like I said before, no fastboot and none of my computers with any combination of OS/USB cable would recognize the phone). Samsung either repaired or replaced it and it is shipping back to me today.

Thats good for u. But I still can't flash stock, other than that, I'm doing great with mine.

RESOLUTION: Assuming you've installed the correct Samsung ADB drivers, you will have had to go to Device Manager, and tell it which driver to use. Good job at getting to to the fastboot screen! You're almost done.
At this point, (on fast boot) open up Device Manager again on your computer. Now your phone is being recognized as something completely different: Android 1.0 was what mine said. Right click on it, 'update driver software', 'browse my computer for...', 'let me select from a list of...", then choose "ADB Interface" from the list. If ADB interface is missing from the list, you haven't installed the drivers.
It will then give you a list of ADB Samsung phone drivers to choose from. I just chose the most updated ones (2012 was at the end of the strand of information about it, as opposed to 2010 which was further down). The second you click next, your phone (assuming you still have the command prompt up on your computer, saying its searching or waiting for your phone) will start to fly through the process of returning you back to stock.
DONE!
Good luck.

Thanks jackharvest. I didn't know Samsung had their own ADB drivers. That was the key! After I configured Windows Device Manager, as you indicated, to use the Samsung driver, all I had to do was run the windows batch file "flash-all.bat" which I had downloaded from google's "Factory Images for Nexus Devices." Unfortunately, their instructions don't tell use about the steps you identified!

[Q] Rooting Issues

Hello,
So I'm trying to unlock and root my tf700t now that my warranty is expired and hope for an ASUS update is diminishing. I downloaded the unlock app from the website and went through the procedure. It took a few weeks and several emails with ASUS support but I think it is unlocked. The reason I say I think its unlocked is whenever I reboot the device, I don't get the message that says its unlocked. The unlock app however says the device is unlocked. So is my device unlocked?
I operated under the assumption that it was and tried to install the twrp recovery using the minimal adb and fastboot exe file. My tablet is recognized by my PC and I put the tablet in fastboot. The error I get when I do that is a writing error. It says writing recovery.... FAILED <remote: <INVALID STATE>>. Does this mean that I am not unlocked or did I do something incorrectly? Any help would be appreciated. I've been working on this for a few weeks and really want to get it moving.

Never heard that before..... If your bootlaoder is unlocked it should say so when you boot up.
Did you run the tool again?
If in doubt call Asus support and check if they have it as unlocked in their database.
But my guess is, since the recovery flash did not take, it's not.

berndblb said:
Never heard that before..... If your bootlaoder is unlocked it should say so when you boot up.
Did you run the tool again?
If in doubt call Asus support and check if they have it as unlocked in their database.
But my guess is, since the recovery flash did not take, it's not.
Click to expand...
Click to collapse
They contacted me today and told me that it is unlocked. Everytime I run the tool, It says the device is unlocked. When I do the power + Vol down, I get the three icons ( RCK, Wipe data, and an android). Ill try applying the recovery again later tonight.

Jkeeper18 said:
They contacted me today and told me that it is unlocked. Everytime I run the tool, It says the device is unlocked. When I do the power + Vol down, I get the three icons ( RCK, Wipe data, and an android). Ill try applying the recovery again later tonight.
Click to expand...
Click to collapse
Sounds like you are all set. You run fast boot from a pc when connected over USB and on that screen with 3 icons If it fails you have a driver issue.

sbdags said:
Sounds like you are all set. You run fast boot from a pc when connected over USB and on that screen with 3 icons If it fails you have a driver issue.
Click to expand...
Click to collapse
I attached a picture of the message I get from the minimal ADB tool. I'm also using the universal Drivers ( the ASUS Fastboot Interface). I tried the ASUS Android Bootloader Interface as well.

Jkeeper18 said:
I attached a picture of the message I get from the minimal ADB tool. I'm also using the universal Drivers ( the ASUS Fastboot Interface). I tried the ASUS Android Bootloader Interface as well.
Click to expand...
Click to collapse
I suspect your bootloader ist not unlocked.
Post a screen shot of when you issue the command 'fastboot devices' please.

berndblb said:
I suspect your bootloader ist not unlocked.
Post a screen shot of when you issue the command 'fastboot devices' please.
Click to expand...
Click to collapse
It says waiting for device. It stayed that way until i manually put it into fastboot. I've attached a screen shot of what it looks like when i did that. If my tablet isnt unlocked, how would I get it unlocked then? The unlock app ( both version) says the device is unlocked.

I am in the same boat - they think it is unlocked but it is not
The Asus v7 and v8 bootloaders both say "device is unlocked" but the fastbook info shows that it is not. I do not see any unlock inormation after the boot process starts. Also , the unlocker did not automatically restart my tablet. It also asked for my google credentials the first 5 times until the unlock said it worked. Now it does not ask that, it just says that it is unlocked. When I try to fastboot install the TWRP rom, it fails.
(remote - invalid state)
I called Asus and they have my tabler listed as unlocked. They are opening a case so that I can prove that it is unlocked.Then hopfully if they reset that setting, I can re-unlock it...
I was following this thread:
http://forum.xda-developers.com/showthread.php?t=2571542
Is there any work around? Please help!
I want TWRP and CM 10.2 on this slow TF700T tablet.
Thanks!

Jkeeper18 said:
It says waiting for device. It stayed that way until i manually put it into fastboot. I've attached a screen shot of what it looks like when i did that. If my tablet isnt unlocked, how would I get it unlocked then? The unlock app ( both version) says the device is unlocked.
Click to expand...
Click to collapse
Well you typed fastboot device not fastboot devices.

Did you 2-step verification enabled for Google by any chance?
I think Asus need to update their database so you get another chance ... Good luck
Sent from my XT894 using Tapatalk

berndblb said:
Did you 2-step verification enabled for Google by any chance?
I think Asus need to update their database so you get another chance ... Good luck
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
No, I did not have two-step verification. I hope Asus creates a case and actually looks into it and resets my device's status in their system. It sounds like that is my only option -- a very lengthy and painful one.

I disabled 2 step authentication since it interfered with the app. I would get invalid password errors until I disabled it and then the app worked.
Well you typed fastboot device not fastboot devices.
Click to expand...
Click to collapse
I attached a picture of what happens when I type the command fastboot devices. It looks like my device is not unlocked and Im going to have to contact ASUS. Are there any other tools that would unlock the device?

Jkeeper18 said:
I disabled 2 step authentication since it interfered with the app. I would get invalid password errors until I disabled it and then the app worked.
I attached a picture of what happens when I type the command fastboot devices. It looks like my device is not unlocked and Im going to have to contact ASUS. Are there any other tools that would unlock the device?
Click to expand...
Click to collapse
Are you sure your device gets recognized at all by your computer?
Usually the dialog just stays on "waiting for device" if the computer detects anything attached.
You have the necessary drivers installed?
Check in Device Manager (if you are running Windows) if there is a yellow triangle next to the entry for your tablet.
There is no other way to unlock. The bootloader is encrypted and only Asus has the key.

berndblb said:
Are you sure your device gets recognized at all by your computer?
Usually the dialog just stays on "waiting for device" if the computer detects anything attached.
You have the necessary drivers installed?
Check in Device Manager (if you are running Windows) if there is a yellow triangle next to the entry for your tablet.
There is no other way to unlock. The bootloader is encrypted and only Asus has the key.
Click to expand...
Click to collapse
The device is recognized by the computer. It says waiting for device when i type in "fastboot device" instead of "fastboot devices". Theres no yellow triangle either. I've sent an email to ASUS and I'm waiting on their reply.

Jkeeper18 said:
The device is recognized by the computer. It says waiting for device when i type in "fastboot device" instead of "fastboot devices". Theres no yellow triangle either. I've sent an email to ASUS and I'm waiting on their reply.
Click to expand...
Click to collapse
Fastboot device doesn't do anything.
I think you just need the right drivers. Let me see if I can dig them up from my collection. No point contacting Asus, they won't help you.
Try these, you need to unzip to same folder as fastboot and update device manager when in fastboot.
http://www.androidfilehost.com/?fid=23212708291675384

sbdags said:
Fastboot device doesn't do anything.
I think you just need the right drivers. Let me see if I can dig them up from my collection. No point contacting Asus, they won't help you.
Try these, you need to unzip to same folder as fastboot and update device manager when in fastboot.
http://www.androidfilehost.com/?fid=23212708291675384
Click to expand...
Click to collapse
Sorry Im still new at this. Where is the fastboot folder?

Jkeeper18 said:
Sorry Im still new at this. Where is the fastboot folder?
Click to expand...
Click to collapse
Where ever you are running fast boot from.
You must open a cmd window in the same directory or change to it using the CD command.

sbdags said:
Where ever you are running fast boot from.
You must open a cmd window in the same directory or change to it using the CD command.
Click to expand...
Click to collapse
So I've been trying for the past couple of days to get root and flash a new rom but it doesnt seem to be working. I've contacted ASUS and they said my tablet is unlocked as of December 16th but they will contact Taiwan to see if something is wrong. Do i have any options if they say the same thing? Thanks again for all your help. I appreciate it.

Jkeeper18 said:
So I've been trying for the past couple of days to get root and flash a new rom but it doesnt seem to be working. I've contacted ASUS and they said my tablet is unlocked as of December 16th but they will contact Taiwan to see if something is wrong. Do i have any options if they say the same thing? Thanks again for all your help. I appreciate it.
Click to expand...
Click to collapse
I have followed the TF700 forums for the last year pretty extensively and until about 2 weeks ago never read about anyone having this problem: Asus database having you unlocked, but it actually isn't. Since then I think I've read about 4 cases.
My best guess: It's a problem with the v8 Unlock app or the way their servers store/process the information they get from the Unlock Tool.
That you got to a support person willing to contact Taiwan is a big plus already. Other users just ran into a wall of: We do not support unlocking this device.
So stick with the person you contacted already. Take pictures of your boot process (to document that it does NOT say: This device is unlocked) and they always seem to ask for a screen shot of your About Tablet page with your SN number and MAC address.
Persistence seems to be the key. And luck to get someone at Asus willing to help....
There is no other way to unlock the bootloader. So you would be limited to rooting the tablet which would give you more freedom to tweak it and uninstall bloatware, but you still would have to deal with the slow stock rom.... :fingerscrossed:

[Completed] Ares 8 and Rooting

Truth: I don't generally use or develop for Android devices, but I got one today to use as a testing platform for an app I'm working on. So pardon me in advance if I'm sounding like a noob. I promise I mostly know what I'm doing with this thing. Just having some trouble...
I purchased the Nextbook Ares 8 and am marveling at what you get for the cost these days considering my first personal PC ran about 18.3x slower than this thing, with 1\4 the power, and was considerably bigger. Amazing.
But I wanted to root it and put Marshmallow on it. Now, here's the thing: I don't have a MicroSD. So I'm being a bit hasty and trying to do this via strictly USB. I've read every post on this site about this specific tab and rooting it. I've also installed KingoRoot, iRoot, VRoot, King Root... all with no luck. They all fail.
I figure it's because the device is encrypted? I've been attempting to get around that all day.
And yes, it's been put into developer mode with USB debugging enabled, too.
I've also tried doing "adb reboot bootloader", and then "fastboot oem unlock", and it'll reboot fine, but it'll just hang in CMD on <waiting for device>.
I know if I had a MicroSD, I could pull it off, but I don't at the moment. Am I screwed until I do?
Thank you guys! :fingers-crossed:

domilu said:
Truth: I don't generally use or develop for Android devices, but I got one today to use as a testing platform for an app I'm working on. So pardon me in advance if I'm sounding like a noob. I promise I mostly know what I'm doing with this thing. Just having some trouble...
I purchased the Nextbook Ares 8 and am marveling at what you get for the cost these days considering my first personal PC ran about 18.3x slower than this thing, with 1\4 the power, and was considerably bigger. Amazing.
But I wanted to root it and put Marshmallow on it. Now, here's the thing: I don't have a MicroSD. So I'm being a bit hasty and trying to do this via strictly USB. I've read every post on this site about this specific tab and rooting it. I've also installed KingoRoot, iRoot, VRoot, King Root... all with no luck. They all fail.
I figure it's because the device is encrypted? I've been attempting to get around that all day.
And yes, it's been put into developer mode with USB debugging enabled, too.
I've also tried doing "adb reboot bootloader", and then "fastboot oem unlock", and it'll reboot fine, but it'll just hang in CMD on <waiting for device>.
I know if I had a MicroSD, I could pull it off, but I don't at the moment. Am I screwed until I do?
Thank you guys! :fingers-crossed:
Click to expand...
Click to collapse
Hello,
You need proper drivers for your device, also adb and fastboot tools. (Here's an easy one Minimal ADB and Fastboot)
Also you may visit here Root Nextbook Ares 8 & TWRP Recovery, If you mess up somewhere here's How to restore your Nextbook Ares 8 to stock
Good luck!
-Vatsal

Vatsal said:
Hello,
You need proper drivers for your device, also adb and fastboot tools. (Here's an easy one Minimal ADB and Fastboot)
Also you may visit here Root Nextbook Ares 8 & TWRP Recovery, If you mess up somewhere here's How to restore your Nextbook Ares 8 to stock
Good luck!
-Vatsal
Click to expand...
Click to collapse
Well all drivers are installed properly. adb devices returns the serial number (YFAV1015088537), and fastboot devices returns BaytrailB94034F3. Both are valid identifiers.
Now, however, no matter what fastboot command I do, such as fastboot oem unlock, it returns FAILED (remote: unknown command)
This is exactly why I don't do Android, right here. It's like a never ending track full of hurdles.

domilu said:
Well all drivers are installed properly. adb devices returns the serial number (YFAV1015088537), and fastboot devices returns BaytrailB94034F3. Both are valid identifiers.
Now, however, no matter what fastboot command I do, such as fastboot oem unlock, it returns FAILED (remote: unknown command)
This is exactly why I don't do Android, right here. It's like a never ending track full of hurdles.
Click to expand...
Click to collapse
Hello,
You may try the link I posted above.
Also, if you have any issues with them, please post in the respective threads. The experts there maybe able to assist you.
Good luck!
-Vatsal

HTC One Mini (M4_U4) Softbricked, OEM not unlocked, USB debug not enabled, bootloop

Hi all,
My HTC One Mini crashed one month after warranty (Boo!). I can get to the FASTBOOT and BOOTLOADER screen and select options. However, the Factory reset and recovery just cause a vibration and get be back to FASTBOOT menu. The phone is *** LOCKED ***.
After a few false starts on linux and mac machines, I've installed WinDroid Toolkit v3.1 on Windows 7. I have gotten the Token ID and used it to get an Unlock_code.bin via email from the HTC developers website (Cannot link as newb). However, when I follow the instructions in WinDroid it recommends that newer devices require "Enable OEM Unlock" to be set:
I cannot do this now. I continue but when it says a menu will appear on the phone, the menu does not and the phone remains in *** LOCKED *** state. I tried continuing with step 2 "Flashing a TWRP" but it does nothing.
TL;DR Am I screwed with having previously unlocked OEM on my HTC One Mini, now that it is soft-bricked?

I'm not that good at this stuff, but managed to get mine unlocked and a recovery on it via this link
sadly mine still has a problem in that it's now stuck in a boot loop, so don't use Oneclickroot as I did in my post here
hopefully you will get yours to work ok, but when you get to instruction 17 you may find that HTC website is quite fussy with the code you copy/paste
when you copy the Identifier block into Notepad or whatever, ensure you don't get any leading blank spaces before you submit it to HTC.
this excerpt from mine had blank spaces where I have inserted red X's, but it worked with them removed and HTC then emailed me the Unlock_code.bin file
XX<<<< Identifier Token Start >>>>
XX36ADF279412BE14D5002935236B24913
XXetc
XXetc
XX<<<<< Identifier Token End >>>>>
I hope this is of some use mate
---------- Post added at 02:39 PM ---------- Previous post was at 02:26 PM ----------
sorry,
lost the plot on my first reply and forget about the OEM unlock bit ...
to get that OEM unlock bit you would normally
first Enable Developer Modeon your phone by Launching the Settings Application -
Scroll Down and Tap on About Phone(or About Device) - Locate the Build Number Section - Tap on the Build Number Option 7 Times -
Go Back to the Main Settings Page - Scroll Down and Tap on Developer Options and it's found there
but given that you are in is bad a place as me in that we cannot get a bootup, I'm afraid I can't offer any more info,
but it's worth knowing anyway in case you do get booted up

Hi, i have the same issue, but a little different.
My phone was in a box for like 2 months, and then i decide to turn it on again, and i faced the same problem as the OP, but my One Mini is UNLOCKED, and i can't lock it again because i get an error in ADB. I try to enter on recovery (and flashed three differents recoveries without sucess), and reboot in bootloader, then try to factory reset, and reboot bootloader again. It don't do anything, only turn on when i plug the usb and enter in bootloader but no more than that. i've try to flash a RUU too, but it give me the error 171. i tried too the method with the rubber band pressing the power button to cause a reboot loop and get enough charge to launch the system but nothing, i don't see any results. I'm one step closer to give up, please help, i tried everything and nothing has worked for me. If need more information don't doubt on asking me. I really appreciate any help you can provide.

I'll try mate ... but perhaps you are asking for help from the wrong guy! - firstly I have to say mine is still in a very bad place! -
I managed to get a permanent TWRP on it, installed a lovely rom named InsertCoin on it, rebooted, and all seemed fine, but then the battery drained rapidly and it would not charge - that issue is ongoing and I'm spending ages on it just now..
Firstly can you confirm that you can enter Bootloader and select Fastboot, and that your phone is then recognised by your PC?
ie: let me know what happens when you press power and vol down together, select fasboot, goto PC, run ADB, cable phone to PC,
then issue the command ADB devices
can you also upload a photo of your bootloader screen

carkev said:
I'll try mate ... but perhaps you are asking for help from the wrong guy! - firstly I have to say mine is still in a very bad place! -
I managed to get a permanent TWRP on it, installed a lovely rom named InsertCoin on it, rebooted, and all seemed fine, but then the battery drained rapidly and it would not charge - that issue is ongoing and I'm spending ages on it just now..
Firstly can you confirm that you can enter Bootloader and select Fastboot, and that your phone is then recognised by your PC?
ie: let me know what happens when you press power and vol down together, select fasboot, goto PC, run ADB, cable phone to PC,
then issue the command ADB devices
can you also upload a photo of your bootloader screen
Click to expand...
Click to collapse
i don't need to press vol down and power together, the phone enter in bootloader once you plug the usb cable. it do that alone.
This is what i get
C:\adb>adb devices
List of devices attached
C:\adb>
the phone is recognized by HTC Sync manager but i can't see it in ADB.

a few things things jump out at me ...
1. from your photo the screen is shattered! - even though I don't like being beaten by phones I would scrap it
the repair would cost more than you can get one from ebay for - about £40.00
2. "abd devices" should return you something like ... "List of devices attached sh3d7h3dj631f6a7" - when it doesn't it show a device number it's usually your drivers
3. you may think that's not it since you say that it is recognised by HTC Sync when on your PC, but I had read that HTC sync is unreliable and that the drivers are not the best
the one's I used were HTC-Mobile-USB Driver-v4.17.0.001.exe but I can't remember where I got them and will upload them later today and send you a link.
(also, it pays to plug your usb cable into a rear port on your PC when doing this kind of work as front are not as reliable)
4. your Hboot is shown as 2.22 -this also can be a problem for TWRP see this link
5. the download link he has is broken, so get any TWRP above 2.7 from their website here

carkev said:
a few things things jump out at me ...
1. from your photo the screen is shattered! - even though I don't like being beaten by phones I would scrap it
the repair would cost more than you can get one from ebay for - about £40.00
Click to expand...
Click to collapse
Hahaha, i know, i have the replacement here, i'll change it once i solve this problem.
carkev said:
2. "abd devices" should return you something like ... "List of devices attached sh3d7h3dj631f6a7" - when it doesn't it show a device number it's usually your drivers
3. you may think that's not it since you say that it is recognised by HTC Sync when on your PC, but I had read that HTC sync is unreliable and that the drivers are not the best
the one's I used were HTC-Mobile-USB Driver-v4.17.0.001.exe but I can't remember where I got them and will upload them later today and send you a link.
(also, it pays to plug your usb cable into a rear port on your PC when doing this kind of work as front are not as reliable)
4. your Hboot is shown as 2.22 -this also can be a problem for TWRP see this link
5. the download link he has is broken, so get any TWRP above 2.7 from their website here
Click to expand...
Click to collapse
2. I will leave you down here exactly what i get when i type "adb devices" (with an attached image)
3. i have installed the latest HTC drivers, and i tried connecting my phone to front an rear usb ports, both of them. No results.
4. Down here i'll leave you an attached image of what i get when i try to install a recovery by typing "fastboot flash recovery recovery.img" (i changed the name to recovery.img of course) and the phone seems installing the recovery in fastboot but it gave me that error in adb and when i try to enter in recovery it reboots on bootloader.

your first image does not 'see' your device mate, so there is no point in trying a flash of anything
until you get a response from "adb devices" that shows a device number you have no chance of getting anywhere!
I am quite certain that the problem MUST be with your drivers
my advice would be to uninstall the HTC Sync and clean out any drivers on your PC and to install the drivers and flash the TWRP I mentioned earlier
sorry I didn't upload earlier as I've been very busy indeed - they are now on my Google Drive ... links here .... and here

carkev said:
your first image does not 'see' your device mate, so there is no point in trying a flash of anything
until you get a response from "adb devices" that shows a device number you have no chance of getting anywhere!
I am quite certain that the problem MUST be with your drivers
my advice would be to uninstall the HTC Sync and clean out any drivers on your PC and to install the drivers and flash the TWRP I mentioned earlier
sorry I didn't upload earlier as I've been very busy indeed - they are now on my Google Drive ... links here .... and here
Click to expand...
Click to collapse
Ok, don't worry mate, i'll try that and then i'll tell you.
Thanks for taking your time helping me.
EDIT: adb still seeing nothing with that drivers

Little Snevil said:
Ok, don't worry mate, i'll try that and then i'll tell you.
Thanks for taking your time helping me.
EDIT: adb still seeing nothing with that drivers
Click to expand...
Click to collapse
Hello guys, I've been following this thread and I'm having same issue. Adb does not sees my phone.
Fastboot does, but when I run ruu , it disconnects and give error 171
Tried usb 2 instead of 3.nothing.
I also think it's the drivers, but I can't seem to find the correct one for this phone. Any help is appreciated

my phone only starts in bootloader it have s-on and i cant use the toolkit cause usb debugging isnt active
adb writes waiting for device
can anyone help me?

Oneplus 3 stuck in fastboot mode with locked bootloader and no working recovery

Hi all android gurus, I have a little problem to which I wonder if there is a solution or not
I was given a oneplus 3 that I can keep if I can get it to work.
The guy had installed twrp and CM14.1
and then he doesn't know how but it's stuck in fastboot mode with locked bootloader.
trying to unlock via adb say it can't be done remotely.
All commands I tried say it's "not allowed remotely"
Windows device manager say it is an "android device"
Trying to boot to recovery or os doesn't work
both these options just give lines of text saying what don't work.
What do all you experts say, is there a way out of this, or should I throw the phone away?
He already bought a new phone so I guess it's mine to either fix or trash.

meonit said:
Hi all android gurus, I have a little problem to which I wonder if there is a solution or not
I was given a oneplus 3 that I can keep if I can get it to work.
The guy had installed twrp and CM14.1
and then he doesn't know how but it's stuck in fastboot mode with locked bootloader.
trying to unlock via adb say it can't be done remotely.
All commands I tried say it's "not allowed remotely"
Windows device manager say it is an "android device"
Trying to boot to recovery or os doesn't work
both these options just give lines of text saying what don't work.
What do all you experts say, is there a way out of this, or should I throw the phone away?
He already bought a new phone so I guess it's mine to either fix or trash.
Click to expand...
Click to collapse
If its stuck in Fastboot, you can fastboot flash the stock firmware for your device.
I DO NOT GIVE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Don't worry dude, There is always a way.
meonit said:
Hi all android gurus, I have a little problem to which I wonder if there is a solution or not
I was given a oneplus 3 that I can keep if I can get it to work.
The guy had installed twrp and CM14.1
and then he doesn't know how but it's stuck in fastboot mode with locked bootloader.
trying to unlock via adb say it can't be done remotely.
All commands I tried say it's "not allowed remotely"
Windows device manager say it is an "android device"
Trying to boot to recovery or os doesn't work
both these options just give lines of text saying what don't work.
What do all you experts say, is there a way out of this, or should I throw the phone away?
He already bought a new phone so I guess it's mine to either fix or trash.
Click to expand...
Click to collapse
Try flashing a new recovery of your choice in Fastboot mode, but for flashing it first you have to unlock your Bootloader, which you can do it with the help of an Android-SDK package for your pc.

sanjeevikrishna said:
Try flashing a new recovery of your choice in Fastboot mode, but for flashing it first you have to unlock your Bootloader, which you can do it with the help of an Android-SDK package for your pc.
Click to expand...
Click to collapse
when I try to unlock bootloader i am getting:
FAILED (remote: oem unlock is not allowed)

meonit said:
when I try to unlock bootloader i am getting:
FAILED (remote: oem unlock is not allowed)
Click to expand...
Click to collapse
Not all bootloader can be unlocked, and the ones that can be unlocked can't all unlock via Fastboot.
I DO NOT GIVE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE