Database Develop

Help!!!! My htc wont connect to fastboot

Hey guys my htc is stuck on a boot loop so i try to connect fast boot to flash a new boot.img but my fastboot just says usb device not recognized please guys i really need help
My symptoms
Stuck on htc boot logo
Cannot access Recovery
Fastboot wont connect

Locky123 said:
Hey guys my htc is stuck on a boot loop so i try to connect fast boot to flash a new boot.img but my fastboot just says usb device not recognized please guys i really need help
My symptoms
Stuck on htc boot logo
Cannot access Recovery
Fastboot wont connect
Click to expand...
Click to collapse
Put the stock ROM on your sdcard and rename it from ROM.zip to ph39IMG.zip and go to bootloader.

mohamed_moscow said:
Put the stock ROM on your sdcard and rename it from ROM.zip to ph39IMG.zip and go to bootloader.
Click to expand...
Click to collapse
No luck it just goes through and says no image found

U got the HTC USB drivers?
Sent from my Vivid 4G using Tapatalk 2

ZeRo2o9 said:
U got the HTC USB drivers?
Sent from my Vivid 4G using Tapatalk 2
Click to expand...
Click to collapse
ok yes i can acess it but no matter what rom i install it is just stuck on the htc logo but i can access recovery

Locky123 said:
ok yes i can acess it but no matter what rom i install it is just stuck on the htc logo but i can access recovery
Click to expand...
Click to collapse
Did you ever find a solution to this? I am in the same boat now. I managed to flash carbon rom and used fastboot to flash boot.img but now I can't go back, fastboot seems broken. USB works fine within the ROM, just not from fastboot. USB Device Not Recognized. Not a driver issue, it's before it even tries to load the drivers.

rewen said:
Did you ever find a solution to this? I am in the same boat now. I managed to flash carbon rom and used fastboot to flash boot.img but now I can't go back, fastboot seems broken. USB works fine within the ROM, just not from fastboot. USB Device Not Recognized. Not a driver issue, it's before it even tries to load the drivers.
Click to expand...
Click to collapse
Are you using Windows 8? I found it does the same with my Sony phone. It sucks!

rewen said:
Did you ever find a solution to this? I am in the same boat now. I managed to flash carbon rom and used fastboot to flash boot.img but now I can't go back, fastboot seems broken. USB works fine within the ROM, just not from fastboot. USB Device Not Recognized. Not a driver issue, it's before it even tries to load the drivers.
Click to expand...
Click to collapse
Yea I fixed it I ended up flashing the kernal then flashing the rom then flashed the kernal once again and it works fine after that but i dont know how i could help any other way

Locky123 said:
No luck it just goes through and says no image found
Click to expand...
Click to collapse
Remember to put all letters in capital and also to relock your bootloader before using the zip file.

My 'USB Device Not Recognized' issue turned out to be Windows 8. I originally flashed my boot.img using Windows 7 at work and forgot that I'd done it from there, so I'd been under the impression that it worked once for me on Windows 8 so it should work again. But in fact, it never worked on Windows 8.
I installed Windows 7 on a second partition at home and it worked without issue. FYI I wasn't using USB 3.0 or anything and I tried a couple of Windows 8 PCs before resorting to installing Windows 7. It's also worth noting that the error in Windows 8 seems to happen before the actual drivers are installed/loaded, so it's not just a matter of picking the proper driver afaik. I did have the proper drivers and HTC Sync Manager, and tried forcing the driver install, but it didn't help. This also means you can't use a virtual machine to work around the issue.
Hope this helps others who run into the 'USB Device Not Recognized' error on Windows 8...
---------- Post added at 11:45 AM ---------- Previous post was at 11:45 AM ----------
Locky123 said:
Yea I fixed it I ended up flashing the kernal then flashing the rom then flashed the kernal once again and it works fine after that but i dont know how i could help any other way
Click to expand...
Click to collapse
Did you wipe data/factory reset after flashing? I didn't see you mention that anywhere. Also, are you sure you're using the right ROMs for the One XL (evita) and not the regular One X? Or the other way around in case you're in the wrong forum?

Htc one soft brick(i think) help!

I tried installing a rom on my HTC one and it messed everything up. I have no data and no OS on my phone. I i did not make a backup as well....
ive been trying to use twrp sideload but my device wont connect to adb. what do i doooo? i can only get into the fastboot menu and trwp recovery. can i use a otg cord and transfer another rom into my phone or do i have to wait for att ruu? please help me! thanks

Miilkman said:
I tried installing a rom on my HTC one and it messed everything up. I have no data and no OS on my phone. I i did not make a backup as well....
ive been trying to use twrp sideload but my device wont connect to adb. what do i doooo? i can only get into the fastboot menu and trwp recovery. can i use a otg cord and transfer another rom into my phone or do i have to wait for att ruu? please help me! thanks
Click to expand...
Click to collapse
you should be able to access adb even without sideload

Miilkman said:
I tried installing a rom on my HTC one and it messed everything up. I have no data and no OS on my phone. I i did not make a backup as well....
ive been trying to use twrp sideload but my device wont connect to adb. what do i doooo? i can only get into the fastboot menu and trwp recovery. can i use a otg cord and transfer another rom into my phone or do i have to wait for att ruu? please help me! thanks
Click to expand...
Click to collapse
Does it say anything when you type the adb lust devices command?
Sent from my HTC One using xda premium

matt95 said:
you should be able to access adb even without sideload
Click to expand...
Click to collapse
My device won't connect to adb no matter what I do.. It just says adb is out of date killing server, and I have the most updated adb too. I have the correct drivers too

Miilkman said:
My device won't connect to adb no matter what I do.. It just says adb is out of date killing server, and I have the most updated adb too. I have the correct drivers too
Click to expand...
Click to collapse
so that's pc's fault, try to reinstall the sdk completely

matt95 said:
so that's pc's fault, try to reinstall the sdk completely
Click to expand...
Click to collapse
Ok I'll try that!
But if that doesn't work can I just USB otg transfer a rom onto my phone and then flash it?

Miilkman said:
Ok I'll try that!
But if that doesn't work can I just USB otg transfer a rom onto my phone and then flash it?
Click to expand...
Click to collapse
never tried that feature by myself so i can't say anything about it, however you should be able to use adb which is much more simple

matt95 said:
never tried that feature by myself so i can't say anything about it, however you should be able to use adb which is much more simple
Click to expand...
Click to collapse
Alright I'll try adb on another pc see if that works...

Miilkman said:
Alright I'll try adb on another pc see if that works...
Click to expand...
Click to collapse
good idea, try also to change the usb if it gives problems again

matt95 said:
good idea, try also to change the usb if it gives problems again
Click to expand...
Click to collapse
if this doesnt work what do i do?

Use the all in one toolkit and flash twrp, mount your USB in twrp using an otg cable. Flash the ROM from usb
Sent from my Nexus 10 using XDA Premium HD app

Miilkman said:
if this doesnt work what do i do?
Click to expand...
Click to collapse
suicide :laugh: just kidding we'll find a solution in that case

Bladerunner1825us said:
Does it say anything when you type the adb lust devices command?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
when i type adb devices it say killing adb server then starts up a daemon....

Im having this same issue, after trying to flash android revolution on my unlocked/rooted rogers One, it froze on the successfully installed part and I had to wait for it to die to try to restart it.
I cannot boot into recovery or connect it to my computer in any way, ./adb reboot bootloader doesnt work it says cannot find device.
When I vol down + power the bottom lights just blink and the phone does nothing.
Any idea on how I can reflash the phone?

Slicka70 said:
Im having this same issue, after trying to flash android revolution on my unlocked/rooted rogers One, it froze on the successfully installed part and I had to wait for it to die to try to restart it.
I cannot boot into recovery or connect it to my computer in any way, ./adb reboot bootloader doesnt work it says cannot find device.
When I vol down + power the bottom lights just blink and the phone does nothing.
Any idea on how I can reflash the phone?
Click to expand...
Click to collapse
I have this same problem as well. I also believe I have bricked my HTC One (ATT) and I tried to flash the stock boot.img but when connected to my computer, the phone is completely empty with no download folder, apps folder or anything like it was on stock. I'm on TWRP Recovery but how to I reinstall the boot.img and fix the phone and put it back into factory settings?

Fastboot not working on my HTC One

Hi all,
I can't get my phone recognised when it's in fastboot mode. I tried all the drivers i found (my PC runs W8.1), with or without HTC Sync installed, with different adb and fastboot aplications but still nothing. Also I noticed that when I connect my phone to the PC in fastboot mode it in the beginning shows "FASTBOOT" and then, if I go up/down, it starts showing "FASTBOOT USB".
I don't know how to fix this. Can someone help me please?
Thank you all very much!

Which version of Win are you running?
And, if you open the device manager how is recognized the phone?

Fastboot usb is normal, try using win 7 instead of win 8, I had the same problem
Sent from my HTC One using xda premium
Stock ROM, CWM Recovery

Arcellano said:
Hi all,
I can't get my phone recognised when it's in fastboot mode. I tried all the drivers i found (my PC runs W8.1), with or without HTC Sync installed, with different adb and fastboot aplications but still nothing. Also I noticed that when I connect my phone to the PC in fastboot mode it in the beginning shows "FASTBOOT" and then, if I go up/down, it starts showing "FASTBOOT USB".
I don't know how to fix this. Can someone help me please?
Thank you all very much!
Click to expand...
Click to collapse
I guess I'll paste my answer from the last post asking the same question
You'll need another PC to make it work.
The only for sure way to get fastboot working on windows 8.1 is to update your hboot to 1.55.000 and up or the hboot 1.54.000 from the GPE from the Android 4.4 update. Once your on these hboot fastboot and adb work fine in windows 8.1 x86 or x64.
the dark bootloader files here are all updated to the newer version hboot
http://www.htc1guru.com/downloads/firmware-downloads/
You need S-off for these to work
Click to expand...
Click to collapse

Guich said:
Which version of Win are you running?
And, if you open the device manager how is recognized the phone?
Click to expand...
Click to collapse
Hi, my PC runs Windows 8.1 32bit. If my phone is normally on, my PC recognizes it as "Android Devices", My HTC or something similar. If my phone is in the bootloader my device manager recognised it as unknown USB device, with error 43.

clsA said:
I guess I'll paste my answer from the last post asking the same question
You'll need another PC to make it work.
Click to expand...
Click to collapse
So you're saying I need to upload my HBoot to 1.55 and then it will work? The problem is that I can't get my One S-Off if my PC doesn't recognize it when in fastboot mode, so I guess I can't upload the HBoot yet.

Arcellano said:
So you're saying I need to upload my HBoot to 1.55 and then it will work? The problem is that I can't get my One S-Off if my PC doesn't recognize it when in fastboot mode, so I guess I can't upload the HBoot yet.
Click to expand...
Click to collapse
you can RUU to version 3.xx.xxx.x to get the new hboot
find your phones RUU here>> http://forum.xda-developers.com/showthread.php?t=2428276

ADB Works but Fastboot does not...
So tonight I decided to venture into the idea of pushing the GPE on to my HTC One. I unlocked the bootloader and got S-Off (The 2 prerequisites for the conversion). I loaded TWRP for the recovery mod and rooted it by installing SuperUser. Then came time to push the GPE RUU over to the phone using these instructions: http://forum.xda-developers.com/showthread.php?t=2358781
Before I pushed the ROM my bootloader screen looked like this: https://www.dropbox.com/s/r7jodkxh8gq7epy/2014-04-22 21.07.51.jpg
When I was pushing it, everything stalled, and it disconnected from the computer. I now no longer have any access to the Fastboot, my computer is saying that the usb device is not recognized by my computer and my bootloader screen now looks like this: https://www.dropbox.com/s/0zap1jiykeqrd9a/2014-04-23 00.00.06.jpg
If I boot into Android, it boots up in the stock AT&T version and I still have ADB control over USB. I run the prompt [ADB reboot bootloader] and it does what it is supposed to, boots it up to the bootloader, but again it is the broken version that I have no access to fastboot with.
I can still load up TWRP and run anything in there that I need. I have tried clearing all caches and doing factory resets with no success. I am at a loss and everything I am finding online is telling me that it is a driver issue or windows 8.1 issue, but if that were the case, then why would I have had Fastbook access before attempting to push the GPE ROM?
Any help here would be amazing. The phone still works as a phone which is a plus, but I would really like to be able to either successfully load the Google Play Edition on it or get everything back to stock for warranty reasons. Thanks so much for your help in advance!! I look forward to trying some new solutions soon!

zpeverman said:
windows 8.1 issue, but if that were the case, then why would I have had Fastbook access before attempting to push the GPE ROM?
Click to expand...
Click to collapse
It's because you're original hboot was 1.55 which works with Win 8.1, but after the first flash hboot got downgraded and therefore "broke" for Win8.1.
Use a Windows 7 PC to complete the conversion, or if you don't have access to one, you can make an Ubuntu Live USB (you can check in my guide under the FAQs how to do that).
and do not ever go S-On again!!!!

@nkk71 Is there any way to get the hboot back to 1.55? I did get it working last night by accident. I used my wife's Win7 computer just to try a different USB port, didn't know why it fixed it but just went with it hoping to understand it later. I would however love to get my phone back to a state that I don't feel like it is broken when I load the bootloader.
Thanks for the response though. Glad I at least understand what happened to it.
Sent from my HTC One using XDA Premium 4 mobile app

zpeverman said:
@nkk71 Is there any way to get the hboot back to 1.55? I did get it working last night by accident. I used my wife's Win7 computer just to try a different USB port, didn't know why it fixed it but just went with it hoping to understand it later. I would however love to get my phone back to a state that I don't feel like it is broken when I load the bootloader.
Thanks for the response though. Glad I at least understand what happened to it.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yes their are newer black GPE firmware that work look for the firmware at htc1guru in my sig.
I was also able to get fastboot working on windows 8.1 with this fix
http://forum.xda-developers.com/showthread.php?p=49131915
use the old dirty method described

Hello,
My Htc One M7 when connected to PC with Windows 7 shows fastboot ac instead of fastboot usb, any idea what could be the problem
My M8 get connected properly & shows fastboot usb
can someone help

abedi75 said:
Hello,
My Htc One M7 when connected to PC with Windows 7 shows fastboot ac instead of fastboot usb, any idea what could be the problem
My M8 get connected properly & shows fastboot usb
can someone help
Click to expand...
Click to collapse
Probably a bad usb cabpe or usb port. fastboot ac = phone only get power, no data connection.

How do push a file via TWRP on this phone?

well, I did something stupid and wiped everything, including the 2 zip files needed to flash the KK rom for Tmobile..
my twrp is working fine; is there a easy way to transfer the 2 zip files back onto my phone via twrp?
thanks!

Does adb work in or twrp? If so it's just
Adb push ZIPNAME /sdcard
Sent from my LG-D959 using Tapatalk

I dont know; there is an adb sideload command in twrp, but it doesnt seem to do anything; Plus I am not sure if my phone is connected via adb..
I know I have the right lg drivers on my computer, but when I run any adb command, the phone doesnt respond.

Honestly I think what you need to do is restart and just lgflash JB then you can just access your sdcard
Sent from my LG-D959 using Tapatalk

This is where external storage comes in handy
Sent from my LG-D959 using Tapatalk

you can say that again; this is the first phone that I have had in a long time without an sd card, and it was "mental muscle memory" that made me wipe everything..
Now, my phone is viewed as an F340k, since that's what the twrp on this phone is based on, so I wonder if I would have a problem using lg flash...this is a tmobile phone, but it might "think" its an f340k..
If I can flash the drivers for a f340 on my computer, then I might be able to adb sideload via twrp..otherwise I am not sure what will happen.
I have been leaving my phone just sit in recovery, as I dont know what would happen if I shut if off, and rebooted to system..
Hope its not brick city for me..

Well try to go to download mode and flash stock. You should be able to get back into recovery again if needed.
Sent from my LG-D959 using Tapatalk

wase4711 said:
you can say that again; this is the first phone that I have had in a long time without an sd card, and it was "mental muscle memory" that made me wipe everything..
Now, my phone is viewed as an F340k, since that's what the twrp on this phone is based on, so I wonder if I would have a problem using lg flash...this is a tmobile phone, but it might "think" its an f340k..
If I can flash the drivers for a f340 on my computer, then I might be able to adb sideload via twrp..otherwise I am not sure what will happen.
I have been leaving my phone just sit in recovery, as I dont know what would happen if I shut if off, and rebooted to system..
Hope its not brick city for me..
Click to expand...
Click to collapse
How did you make out? I have been trying to figure out what drivers I need for adb to recognize my phone in twrp. Hope you recovered

Got to adb sideload. Swipe to enable. Open up a command promp on computer and type adb sideload then place your zip file here and hit enter
Sent from my LG-LS980 using XDA Premium 4 mobile app

PattyNYC said:
How did you make out? I have been trying to figure out what drivers I need for adb to recognize my phone in twrp. Hope you recovered
Click to expand...
Click to collapse
Thanks, still can't get the phone to be recognized by the computer..
justinswidebody said:
Got to adb sideload. Swipe to enable. Open up a command promp on computer and type adb sideload then place your zip file here and hit enter
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have been trying that; the problem is, that my phone now "thinks" its a f340k, and not a d959
I have been trying to install drivers so my win 8.1 machine can "see" the phone, so I can run adb sideload, but for some reason, I cant get it to "see" the phone in ADB..I keep getting a message in the command prompt, "device not found"
.I have downloaded drivers that "should" work, but its a WHQL win driver from LG, and it doesnt seem to have the proper drivers to enable my computer to "see" the phone in ADB..
Not a happy camper right now..

Maybe a usb otg would work if you put the rom.zip on the flash drive. There is an option to mount USB-OTG

PattyNYC said:
Maybe a usb otg would work if you put the rom.zip on the flash drive. There is an option to mount USB-OTG
Click to expand...
Click to collapse
I dont think that would help because my phone isn't being "seen" by my computer, while in twrp recovery
If I could just find the f340k driver by itself, without the WHQL "bundle", I think I could get it to recognize the phone, and then transfer files on to it..
I've looked everywhere, and cant seem to find that driver by itself anywhere..

Not sure but it worked on the similar G2 http://forum.xda-developers.com/showthread.php?t=2492911 sorry just read further in that thread and you may be right. sorry

I can get into download mode, but I cant get the lg flash tool to see the phone either...any suggestions at this point?
thanks
EDIT:
How can I boot to recovery at this point?
When I hold power and down, I get a screen with all Chinese writing on it, and my IEMI code on the bottom of the page..Power and up gets me the same thing..

another guess. I know with windows 7 the only way I could use fastboot was with the pdanet drivers otherwise my phone wouldn't connect to the pc. http://www.theandroidsoul.com/android-drivers-adb-and-fastboot-android-phones-tablets/

thanks, but the computer still doesnt see the phone..
do you know how I can get the phone into recovery at this point?
TWRP should still be on it, but I cant get i to boot into twrp.

wase4711 said:
Thanks, still can't get the phone to be recognized by the computer..
I have been trying that; the problem is, that my phone now "thinks" its a f340k, and not a d959
I have been trying to install drivers so my win 8.1 machine can "see" the phone, so I can run adb sideload, but for some reason, I cant get it to "see" the phone in ADB..I keep getting a message in the command prompt, "device not found"
.I have downloaded drivers that "should" work, but its a WHQL win driver from LG, and it doesnt seem to have the proper drivers to enable my computer to "see" the phone in ADB..
Not a happy camper right now..
Click to expand...
Click to collapse
Just flash the kdz files that is gona be the only way to fix that.

D-FUSE said:
Just flash the kdz files that is gona be the only way to fix that.
Click to expand...
Click to collapse
I've been trying all day to do just that, but my phone isnt being seen by my computer..
I think the problem is that my phone is a d959 tmo, but, the freedomflex recovery installed,(twrp) has changed my phone to a f340k, and I cant get any drivers to recognize the phone, so without that, I can't do anything with it..
Since the last working thing was TWRP recovery, is there a way for me to boot into twrp at this point?
All I can do is get in download mode, or another mode which shows all Chinese text/language on it, with my IEMI code on the bottom of the page..
Otherwise, I will have to ebay this thing, and hope someone with more dev skills than me can restore it somehow..
thanks!

wase4711 said:
I've been trying all day to do just that, but my phone isnt being seen by my computer..
I think the problem is that my phone is a d959 tmo, but, the freedomflex recovery installed,(twrp) has changed my phone to a f340k, and I cant get any drivers to recognize the phone, so without that, I can't do anything with it..
Since the last working thing was TWRP recovery, is there a way for me to boot into twrp at this point?
All I can do is get in download mode, or another mode which shows all Chinese text/language on it, with my IEMI code on the bottom of the page..
thanks!
Click to expand...
Click to collapse
Are turning off your antivirus and editing the host file
Sent from my LG-D959 using Tapatalk
---------- Post added at 01:55 PM ---------- Previous post was at 01:55 PM ----------
D-FUSE said:
Are turning off your antivirus and editing the host file
Sent from my LG-D959 using Tapatalk
Click to expand...
Click to collapse
Have you tried a different port
Sent from my LG-D959 using Tapatalk

Or different computer all together. The aboot and recovery shouldn't mess up your drivers
Sent from my LG-D959 using Tapatalk

[Solved]M7 Soft bricked,ADB/Fastboot not working,No OS as well,TWRP 2.6.3.3

Hello.I am in some kind of a trouble..I just bought a phone with firmware problems,hoping i could make it work.The problem is this,someone tried to update the firmware,unsuccesfully,and now it's stuck with no OS.I can only start recovery and bootloader.
Recovery is Teamwin 2.6.3.3.Already tried to clear cache and everything,to use an USB with OTG,but it's not recognised,ADB sideload also it's not working.
adb devices shows the phone is not connected,and FastBoot says "Waiting for device".Any idea? I've tried,read a lot,but I can't really work it out..
Also,I can't find the device in Device Manager,neither in ADB nor Fastboot.
I tried using Windows 8.1 and 7..Same deal.
Thank you!

chris_b0ss said:
Hello.I am in some kind of a trouble..I just bought a phone with firmware problems,hoping i could make it work.The problem is this,someone tried to update the firmware,unsuccesfully,and now it's stuck with no OS.I can only start recovery and bootloader.
Recovery is Teamwin 2.6.3.3.Already tried to clear cache and everything,to use an USB with OTG,but it's not recognised,ADB sideload also it's not working.
adb devices shows the phone is not connected,and FastBoot says "Waiting for device".Any idea? I've tried,read a lot,but I can't really work it out..
I tried using Windows 8.1 and 7..Same deal.
Thank you!
Click to expand...
Click to collapse
Is it a M8 or a M7, because your title says M8 but you have posted in the M7 forum.

Sorry,I am quite scared.It's M7.

chris_b0ss said:
Sorry,I am quite scared.It's M7.
Click to expand...
Click to collapse
First, follow instructions given in this post to install the latest android sdk-tools and the latest htc drivers. Also make sure you don't have HTC Sync installed on your computer.
Then connect your phone to you computer with the original cable (or any other cable already known to work for data transfer - some usb cable are only providing power), reboot the phone in bootloader mode by holding vol down and power. Make sure you see the red "fastboot usb" caption on the screen, if not use vol up/down and power to select the "fastboot" menu. Once there open a command window form the android sdk-tools folder and type "fastboot getvar all". Copy/paste the ouput of this command here (except the imei and serialno).

I've followed that,and still not working.pics attached.
It's very weird,because I was expecting for a soundfrom the Windows,like a new device connected .But ..nothing
Sent from my GT-I9100 using XDA Free mobile app

chris_b0ss said:
I've followed that,and still not working.pics attached.
It's very weird,because I was expecting for a soundfrom the Windows,like a new device connected .But ..nothing
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
With your phone in bootloader/fastboot mode, go to your windows device manager, take a screenshot of your device manager and post it here please.

The unknown device is related to my laptop.Nothing happens when I connect the phone.

chris_b0ss said:
The unknown device is related to my laptop.Nothing happens when I connect the phone.
Click to expand...
Click to collapse
Ok so its not detected at all
Might be caused by
a bad usb cable --> Try another one that you are 100% sure its working
a bad usb port on the computer (use only usb 2.0 ports btw)
a problem with the computer ---> Try another computer.
a bad usb port on the phone ---> need to replace the usb/front mic board
Might also worth to fix your laptop drivers problem. Might be causing problem if the "unknown" device is an adapter or usb controller...
Then reboot the computer.

I think we can exclude the first two,because I've tried 2 different USB cables,and with my S2 ,both of them are working,even ADB.I will try to replace the usb port from the phone,and then try again.But,do you think it will work ?
Thank you!

chris_b0ss said:
I think we can exclude the first two,because I've tried 2 different USB cables,and with my S2 ,both of them are working,even ADB.I will try to replace the usb port from the phone,and then try again.But,do you think it will work ?
Thank you!
Click to expand...
Click to collapse
Its hard to tell, there isn't any background info about what was done on that phone. The usb board is pretty cheap so it worth a try if you are 100% sure everything else is fine (computer, cables etc..)

I understand,but,I mean,as far as I know,it's not hard brick,because the phone is still booting..in some way ..so if I manage to connect it,I can flash the rom..am I right?
Sent from my GT-I9100 using XDA Free mobile app

chris_b0ss said:
I understand,but,I mean,as far as I know,it's not hard brick,because the phone is still booting..in some way ..so if I manage to connect it,I can flash the rom..am I right?
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
Normally it should be pretty easy to fix if you can get fastboot and adb connectivity. You could then update the firmware so you can flash the correct RUU to restore the phone back to stock, already made the research and all the files (firmware and ruu) you'll need are available.

alray said:
Normally it should be pretty easy to fix if you can get fastboot and adb connectivity. You could then update the firmware so you can flash the correct RUU to restore the phone back to stock, already made the research and all the files (firmware and ruu) you'll need are available.
Click to expand...
Click to collapse
Sorry for the late reply,the phone is now in service,in 1-2 days they should fix the USB board,and I will get back with more info soon.
Thank you very much for your quick answers and for taking time to help me!

Good news,I've managed to unbrick it.I asked a friend with a Mac to check it out,and his Mac recognized with no problems.Installed the Os,but still,Windows can't detect it.I've tried on 2 pc's(7 and 10) with the proper drivers.Weird..
Anyway,thank you for your time @alray !