Database Info

Semi Brick, STUCK ON DOWNLOAD MODE. HELP

Hello everyone, I totally pulled a noob earlier, with all the excitement going around with the official ICS update going around, accidentally I pushed a 19100 ROM into my sgs2 by sprint; and now my device is semi brick, neither Kies, Odin nor SimpleDownloaderTool for SPH-D710 recognizes the device, after downloading the correct drivers into my computer.. now what do I do?

If you have a Galaxy S 4G SGH-T959V follow the second link in my signature, read thoroughly and follow directions.

sgs4g SGH-T959V always reboot into download mode, even after successful oneclick
lumin30 said:
If you have a Galaxy S 4G SGH-T959V follow the second link in my signature, read thoroughly and follow directions.
Click to expand...
Click to collapse
Hi, I used OneClick. Things seems to work. The flash was successful. If I do a reboot using the phone's power button or if I pull its battery, the phone always boot back into download mode, thus negating the flash and I have to start over. When the phone is in this state, I am not able to connect via adb or reboot into recovery mode.
One strange thing is if the reboot is done via 'adb reboot', via the OneClick process, or via the reboot option in recovery mode, it boots normally. So esstentially it means after a successful flash, the phone has to remain on forever, with an occasional adb reboot.
Is there anything I can do to restore this phone? Or as a consolation prize, force a normal restart on a one off basis via my computer somehow.
P.S. I'm new to the forum. Please let me know if this is not the right place to post this. Thank you.

Pro tip: Open a new thread if you need to ask a question or need help. Don't "hi-jack" other threads. (considering that the original thread is from 2012)
But it's done...
teevoo said:
Hi, I used OneClick. Things seems to work. The flash was successful. If I do a reboot using the phone's power button or if I pull its battery, the phone always boot back into download mode, thus negating the flash and I have to start over. When the phone is in this state, I am not able to connect via adb or reboot into recovery mode.
Click to expand...
Click to collapse
Did you follow @lumin30's guide?
teevoo said:
One strange thing is if the reboot is done via 'adb reboot', via the OneClick process, or via the reboot option in recovery mode, it boots normally. So esstentially it means after a successful flash, the phone has to remain on forever, with an occasional adb reboot.
Click to expand...
Click to collapse
The phone is in download mode. The phone isn't being reset by adb, it's being reset by heimdall/odin. I think this sounds like a USB issue.
teevoo said:
Is there anything I can do to restore this phone? Or as a consolation prize, force a normal restart on a one off basis via my computer somehow.
P.S. I'm new to the forum. Please let me know if this is not the right place to post this. Thank you.
Click to expand...
Click to collapse
I've seen this problem a few times, and usually I found it was a bad cable or a bad USB port.
Also make sure the usb port is clean of any lint/objects/dirt.
I had a dell laptop once, where none of the usb ports worked with heimdall or odin. I tried the same one-click on my apple mac, and on another HP laptop. I found that I also had a bad cable. I replaced the cable and everything worked on my Mac and HP, but still nothing on my dell. Same setup - debian linux - on each laptop. The one-click looks like everything flashes, but if you pull the battery and turn it on, it's back at the download mode screen.

bhundven said:
Did you follow @lumin30's guide?
Click to expand...
Click to collapse
Yes. Oh and I made several posts (not hijack ) regarding this issue elsewhere in the forum but got no response. One thing I forgot to mention in this version is that originally, the download mode on phone was triggered physically somehow. My uncle accidentally dropped the phone in water. He then blew it dry with a strong fan and must have turned it back on too early. Since then the phone's been in download mode.
bhundven said:
The phone is in download mode. The phone isn't being reset by adb, it's being reset by heimdall/odin. I think this sounds like a USB issue.
Click to expand...
Click to collapse
I'm now wondering if there is a program that can do a reset like heimdall/odin without going through the whole reflashing process. Assuming the phone's memory components haven't been physically damage, at least this would mean I can restart the phone to normal mode quickly.
bhundven said:
I've seen this problem a few times, and usually I found it was a bad cable or a bad USB port.
Also make sure the usb port is clean of any lint/objects/dirt.
I had a dell laptop once, where none of the usb ports worked with heimdall or odin. I tried the same one-click on my apple mac, and on another HP laptop. I found that I also had a bad cable. I replaced the cable and everything worked on my Mac and HP, but still nothing on my dell. Same setup - debian linux - on each laptop. The one-click looks like everything flashes, but if you pull the battery and turn it on, it's back at the download mode screen.
Click to expand...
Click to collapse
Ok, I'll try to find a different computer to do this with, although right now I'm thinking USB is not the case as I have successfully performed the same flash on a different sgs4g and it works just fine (the difference was that phone was never stuck in download mode to begin with). For the problem phone, I have tried a couple of ports and 2 different cables on my Mac. From what you just told me, perhaps the phone's usb port is the culprit.
Thanks for your reply, and thanks for all the programming work you've contributed to this forum :good:

RUU Error 171 Stuck on waiting for boot loader

As the title says, RUU attempts booting my phone but it never comes back on. Even selecting restart boot loader in fastboot or a command it doesn't power itself back on. I have read through other forums and nothing has worked for me yet.
EDIT: I should probably clarify fastboot usb WORKS. Ruu must see my phone considering it detects the ROM version and turns the phone off in attempt to reboot. Anything that I do that requires a reboot doesn't work. I have tried unlocking the bootloader again, everything is fine until it comes to rebooting then I must turn the phone on myself and nothing changes...... IT DOESN'T REBOOT ITSELF therefore seemingly nothing wants to work. And the HTC boot screen is gone??
More background information: http://forum.xda-developers.com/showthread.php?p=39046436#post39046436

What we're your steps exactly? Did you relock your bootloader

a box of kittens said:
What we're your steps exactly? Did you relock your bootloader
Click to expand...
Click to collapse
Yes I did through fast boot with the oem lock command. I've tried installing RUU with a Windows 7 laptop (has HTC sync software) and Windows 8 desktop (basic drivers). Both failed, tried using Windows XP/Vista in compatibility modes and running as an admin with the same results.

Error 171 is a connection error, meaning the RUU can't connect to/find your phone.
Try uninstalling HTC Sync, rebooting your pc, and installing it again. If you've got the Android SDK installed, be sure it's also fully updated.

iElvis said:
Error 171 is a connection error, meaning the RUU can't connect to/find your phone.
Try uninstalling HTC Sync, rebooting your pc, and installing it again. If you've got the Android SDK installed, be sure it's also fully updated.
Click to expand...
Click to collapse
No luck. And I believe it does see the phone in the beginning of the installation. It makes it reboot to the boot loader and that's where it loses the connection. The phone just isn't booting itself back up. I appreciate the reply, if you have anymore ideas please let me know.

Could be something got corrupted. Try redownloading the ruu. Does adb see the phone?

iElvis said:
Could be something got corrupted. Try redownloading the ruu. Does adb see the phone?
Click to expand...
Click to collapse
Re-downloaded RUU and still no go. And adb doesn't see my phone, will it on the fastboot menu? I'm not to familiar with it.

Does anybody else have some more ideas?

Okkoto said:
And adb doesn't see my phone, will it on the fastboot menu? I'm not to familiar with it.
Click to expand...
Click to collapse
No. If adb doesn't see it, fastboot won't either. Does the command "adb devices" (no quotes) show the device as connected?
It sounds like the connection might be working for a few things (like rebooting the phone, as you mentioned). But I still think a connection issue is the main problem.

redpoint73 said:
No. If adb doesn't see it, fastboot won't either. Does the command "adb devices" (no quotes) show the device as connected?
It sounds like the connection might be working for a few things (like rebooting the phone, as you mentioned). But I still think a connection issue is the main problem.
Click to expand...
Click to collapse
Fastboot does see it but adb does not. And what I mean by rebooting the phone in my last post is RUU attempts rebooting it from the boot loader which does turn the phone off but it stays turned off. I've used other commands to reboot the phone from the fastboot screen and those too turn off the phone then again it doesn't come back on like a reboot should do.

I have about completely gave up and going back to using a regular feature phone. I have watched a video about a jtag repair service and was wondering about that or just selling the phone as bricked on ebay.

Okkoto said:
I have about completely gave up and going back to using a regular feature phone. I have watched a video about a jtag repair service and was wondering about that or just selling the phone as bricked on ebay.
Click to expand...
Click to collapse
don't sell it as bricked since it is obviously not bricked. you could get more money just saying you dont wtf your doing and gave up on it. but ill buy it as a bricked phone =) ill give you 50 bucks.

DvineLord said:
don't sell it as bricked since it is obviously not bricked. you could get more money just saying you dont wtf your doing and gave up on it. but ill buy it as a bricked phone =) ill give you 50 bucks.
Click to expand...
Click to collapse
Well if it's not bricked then I sure wish somebody would lead me to the right direction. I have tried 5 different PCs (which all show as connected through fastboot) and they all came with the same error. I've tried everything I could possibly think of and I haven't seen anyone else with quite the same problem I'm having.
I still have not completely gave up and have already decided against selling it as "bricked". The bootloader still comes up so there is at least some hope.

i just had the same problem. the solution was simple - i switch usb-port from front one to the backside one which is directly on motherboard.

Okkoto said:
Well if it's not bricked then I sure wish somebody would lead me to the right direction. I have tried 5 different PCs (which all show as connected through fastboot) and they all came with the same error. I've tried everything I could possibly think of and I haven't seen anyone else with quite the same problem I'm having.
I still have not completely gave up and have already decided against selling it as "bricked". The bootloader still comes up so there is at least some hope.
Click to expand...
Click to collapse
when you say it shows connected through fastboot what do you mean?
how are you getting the device into fastboot - through recovery??
oh, and what was on your device before you tried loading the RUU?

kkm68 said:
i just had the same problem. the solution was simple - i switch usb-port from front one to the backside one which is directly on motherboard.
Click to expand...
Click to collapse
Yes this + if you're on a usb3 port try usb2. Also make sure you're using the cable that came with the phone as I understand other cables may cause issues like this. Also, avoid using a hub or usb extension.

Solution to error 171
I had the same problem and after many attempts I finally got it to work!
-Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
-Make sure you leave the sdk and adb stuff that you downloaded.
-Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
-A pop-up asking to install HTC Sync will appear, just ignore it.
-Make sure you set Fast Boot OFF on your phone, and Debugging ON.
-Leave your phone ON and run the RUU set up.
-Then follow the steps on the wizard and everything should work just fine!

diegoyabishh said:
I had the same problem and after many attempts I finally got it to work!
-Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
-Make sure you leave the sdk and adb stuff that you downloaded.
-Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
-A pop-up asking to install HTC Sync will appear, just ignore it.
-Make sure you set Fast Boot OFF on your phone, and Debugging ON.
-Leave your phone ON and run the RUU set up.
-Then follow the steps on the wizard and everything should work just fine!
Click to expand...
Click to collapse
I have a similar problem with my HTC One. I am stuck in the bootloader and any action I take leads straight into a boot loop. If I try to reboot, reboot-bootloader, go into recovery (twrp), or factory reset it goes into a boot loop. Also I can't lock the bootloader and flashing my recovery doesn't help, even though it says its a success. I've tried three computers and deleted and reinstalled drivers but still the computers only find my phone in fastboot usb and can't find it using adb.
This solution above won't help me since I can't get my phone on for the life of me. I tried running RUU and All-in-One Toolkit but no luck. RUU fails finding the bootloader since my phone gets stuck in its boot loop. I am fresh out of ideas so any other ways to fix this issue would be greatly appreciated.
BTW I found my phone is this condition when I pulled it out of my pocket. I never installed custom ROMs on it. It is unlocked and rooted though running 4.2.2 (3.05.651.6) hoot 1.55. The only thing I can think of is that an OTA update got pushed to my phone and bricked it. That or for some strange reason something went wrong with phone from the rooting process after two weeks of it working perfectly.

jondon156 said:
I have a similar problem with my HTC One. I am stuck in the bootloader and any action I take leads straight into a boot loop. If I try to reboot, reboot-bootloader, go into recovery (twrp), or factory reset it goes into a boot loop. Also I can't lock the bootloader and flashing my recovery doesn't help, even though it says its a success. I've tried three computers and deleted and reinstalled drivers but still the computers only find my phone in fastboot usb and can't find it using adb.
This solution above won't help me since I can't get my phone on for the life of me. I tried running RUU and All-in-One Toolkit but no luck. RUU fails finding the bootloader since my phone gets stuck in its boot loop. I am fresh out of ideas so any other ways to fix this issue would be greatly appreciated.
BTW I found my phone is this condition when I pulled it out of my pocket. I never installed custom ROMs on it. It is unlocked and rooted though running 4.2.2 (3.05.651.6) hoot 1.55. The only thing I can think of is that an OTA update got pushed to my phone and bricked it. That or for some strange reason something went wrong with phone from the rooting process after two weeks of it working perfectly.
Click to expand...
Click to collapse
Nobody here can help you as we don't have any experience with your device. You'd be much better off asking in the HTC One forum which you'll find here:
http://forum.xda-developers.com/htc-one
Sent from my Evita

Heisenberg said:
Nobody here can help you as we don't have any experience with your device. You'd be much better off asking in the HTC One forum which you'll find here:
http://forum.xda-developers.com/htc-one
Sent from my Evita
Click to expand...
Click to collapse
hi all..
facing same problem with HTC Desire 816 n 4g... have anyone got any solution??
plz pass it..
thank you

[Q] Hard-Bricked, no boot. Failed during flash

OK,
I was trying to flash a new ROM and had some issues where it would continously reboot so, after some reading it seemed like I needed a new version of TWRP, so I updated it. That didn't help.
I decided to reflash the stock rom on the device but after doing that, it wouldn't boot past the ASUS boot screen. So I tried again (via fastboot), same result. So I tried again and this time fastboot crashed in the middle of the load and now the tablet won't boot or anything.
It seems like the tablet still has power because windows makes a funky sound when you plug it in.
I saw this post but pressing the tiny button with a paperclip doesn't do anything.
Edit:
Windows can tell I plugged something in but says there is an error and doesn't recognize it anymore. Therefore, I don't have adb or fastboot access.
Edit: I installed the naked drivers and got it to recognize the device as an apx. I then pointed it to the normal driver and is recognizes it as an adb device but I can't connect via adb.
Edit: Nevermind, it came unplugged and when I plugged it in again windows didn't recognize it.
Where in the crap do I go from here?

gtgeek said:
OK,
I was trying to flash a new ROM and had some issues where it would continously reboot so, after some reading it seemed like I needed a new version of TWRP, so I updated it. That didn't help.
I decided to reflash the stock rom on the device but after doing that, it wouldn't boot past the ASUS boot screen. So I tried again (via fastboot), same result. So I tried again and this time fastboot crashed in the middle of the load and now the tablet won't boot or anything.
It seems like the tablet still has power because windows makes a funky sound when you plug it in.
I saw this post but pressing the tiny button with a paperclip doesn't do anything.
Edit:
Windows can tell I plugged something in but says there is an error and doesn't recognize it anymore. Therefore, I don't have adb or fastboot access.
Edit: I installed the naked drivers and got it to recognize the device as an apx. I then pointed it to the normal driver and is recognizes it as an adb device but I can't connect via adb.
Edit: Nevermind, it came unplugged and when I plugged it in again windows didn't recognize it.
Where in the crap do I go from here?
Click to expand...
Click to collapse
+1

gtgeek said:
OK,
I was trying to flash a new ROM and had some issues where it would continously reboot so, after some reading it seemed like I needed a new version of TWRP, so I updated it. That didn't help.
I decided to reflash the stock rom on the device but after doing that, it wouldn't boot past the ASUS boot screen. So I tried again (via fastboot), same result. So I tried again and this time fastboot crashed in the middle of the load and now the tablet won't boot or anything.
It seems like the tablet still has power because windows makes a funky sound when you plug it in.
I saw this post but pressing the tiny button with a paperclip doesn't do anything.
Edit:
Windows can tell I plugged something in but says there is an error and doesn't recognize it anymore. Therefore, I don't have adb or fastboot access.
Edit: I installed the naked drivers and got it to recognize the device as an apx. I then pointed it to the normal driver and is recognizes it as an adb device but I can't connect via adb.
Edit: Nevermind, it came unplugged and when I plugged it in again windows didn't recognize it.
Where in the crap do I go from here?
Click to expand...
Click to collapse
So will the tablet not boot into the bootloader ?
Thx Josh

lj50036 said:
So will the tablet not boot into the bootloader ?
Thx Josh
Click to expand...
Click to collapse
Nothing, just the black screen.
I only know something is going on when I connect it to a pc I can here it connect/disconnect when I hold the power button or press the reset button. Also checked the hdmi output on another screen to make sure that wasn't the problem....it wasn't.

gtgeek said:
Nothing, just the black screen.
I only know something is going on when I connect it to a pc I can here it connect/disconnect when I hold the power button or press the reset button. Also checked the hdmi output on another screen to make sure that wasn't the problem....it wasn't.
Click to expand...
Click to collapse
I see....
If you dont have your nvflash blobs, its a brick ...
Sorry for the bad news ....
Thx Josh

lj50036 said:
I see....
If you dont have your nvflash blobs, its a brick ...
Sorry for the bad news ....
Thx Josh
Click to expand...
Click to collapse
That was the conclusion I was coming to.
Now, for a nerdier question. If I had physical access to the processor, could I program it directly using it's programming ports?

gtgeek said:
That was the conclusion I was coming to.
Now, for a nerdier question. If I had physical access to the processor, could I program it directly using it's programming ports?
Click to expand...
Click to collapse
Nope there is just no way...
The chip is locked down ... :crying:
There is lots of info out there but its just info ...
No one to date has come back from where you are ....
Thx Josh

S7 reset recovery flag

Hi all, bit of a strange problem here.
I've recently updated TWRP from the official app and installed the latest recovery for my phone.. Problem is my TWRP screen is now green, and I cant touch any on screen buttons when in recovery. Because the recovery flag was set last time I rebooted the phone it keeps going into recovery and just freezing
To add insult to injury my USB port seems to be faulty (has been for a while) so I can't even connect with ODIN to reflash the recovery.. So I seem to be stuck in a predicament here. Windows advises the machine has malfunctioned and will not recognise the device. I wish this was a driver issue but after testing with a number of cables / machines I can safely say it's a hardware issue.
Is there anyway to reset the recovery flag so I can at least get back on my phone? Or any other options?

The Windows errors occur even when the phone is in Download Mode?

*Detection* said:
The Windows errors occur even when the phone is in Download Mode?
Click to expand...
Click to collapse
Yep. Got a new USB port coming in the post which should hopefully fix that.
I think it's looping into recovery because the recovery flag was set when I rebooted the phone (I selected reboot into recovery from my rom) Wondering if this flag will be reset if the battery is drained to 0%?
Because really, the phone itself should be functional, just getting past this recovery loop is the real problem

Interesting...
So I've replaced the USB port on the phone and STILL get the same error. Tried another laptop, same error. Tried removing samsung drivers from the windows driver store and reinstalling using smart switch... same error!
Pulling my hair out here guys!

clownstyle said:
Hi all, bit of a strange problem here.
I've recently updated TWRP from the official app and installed the latest recovery for my phone.. Problem is my TWRP screen is now green, and I cant touch any on screen buttons when in recovery. Because the recovery flag was set last time I rebooted the phone it keeps going into recovery and just freezing
To add insult to injury my USB port seems to be faulty (has been for a while) so I can't even connect with ODIN to reflash the recovery.. So I seem to be stuck in a predicament here. Windows advises the machine has malfunctioned and will not recognise the device. I wish this was a driver issue but after testing with a number of cables / machines I can safely say it's a hardware issue.
Is there anyway to reset the recovery flag so I can at least get back on my phone? Or any other options?
Click to expand...
Click to collapse
Did you manage to fix this? Mine is doing the exact same thing, it's green and uninteractable... I don't get any windows errors tho.

clownstyle said:
Interesting...
So I've replaced the USB port on the phone and STILL get the same error. Tried another laptop, same error. Tried removing samsung drivers from the windows driver store and reinstalling using smart switch... same error!
Pulling my hair out here guys!
Click to expand...
Click to collapse
Did you ffix this? I've the same prob

And guess what, you guys can't use fast charging ability..
https://forum.xda-developers.com/galaxy-s7/help/galaxy-s7-fast-charge-mtp-computers-t3694866
Take a look at my post. This is a growing problem I think.

Oneplus One will not turn on or charge.

Hi, so about a week ago I was happily going over instagram untill my phone restarted. I thought nothing of it as I'm rooted and have the latest version of Nitrogen OS "Nitrogen OS ► [7.1.2 ► NJH47B]" so im used to a random restart or two, after about 5 minutes of the phone coming back on it randomly shut off, no boot logo or anything and from that day on I can not turn it on again. I have tried plugging it in to the wall and to my computer to recover files but my computer does not pick up the phone. I thought it may have been the battery so I orderd a new one and installed it and nothing has changed, now when I put the phone on charge the upper part of the phone warms up (where there is the metal cage covered in black tape) and I can hear a faint clicking sound every second or two.)
I have followed all procedures given by OnePlus as well and I can't seem to get it to work. Is it a lost hope?
Here is some info:
- I have had the phone since about June 2015 (2 years)
- I am rooted, with Nitrogen OS ► [7.1.2 ► NJH47B] so custom recovery as well. TWRP-3.0.2-0
- I have had a soft brick but I managed to get myself out of it a month or two ago.
- I left it with no charge for about 3 days and then left it on charge for a day and abit extra and still no signs of life.
- I can't boot to Recovery or Fastboot. I can't boot at all.
(If you need anything extra please ask)
Thanks for any help and I'm sorry if I'm using the forums incorrectly or bothering anyone

francosis said:
Hi, so about a week ago I was happily going over instagram untill my phone restarted. I thought nothing of it as I'm rooted and have the latest version of Nitrogen OS "Nitrogen OS ► [7.1.2 ► NJH47B]" so im used to a random restart or two, after about 5 minutes of the phone coming back on it randomly shut off, no boot logo or anything and from that day on I can not turn it on again. I have tried plugging it in to the wall and to my computer to recover files but my computer does not pick up the phone. I thought it may have been the battery so I orderd a new one and installed it and nothing has changed, now when I put the phone on charge the upper part of the phone warms up (where there is the metal cage covered in black tape) and I can hear a faint clicking sound every second or two.)
I have followed all procedures given by OnePlus as well and I can't seem to get it to work. Is it a lost hope?
Here is some info:
- I have had the phone since about June 2015 (2 years)
- I am rooted, with Nitrogen OS ► [7.1.2 ► NJH47B] so custom recovery as well. TWRP-3.0.2-0
- I have had a soft brick but I managed to get myself out of it a month or two ago.
- I left it with no charge for about 3 days and then left it on charge for a day and abit extra and still no signs of life.
- I can't boot to Recovery or Fastboot. I can't boot at all.
(If you need anything extra please ask)
Thanks for any help and I'm sorry if I'm using the forums incorrectly or bothering anyone
Click to expand...
Click to collapse
Looks like a hard brick..
Try this,
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
If having problem with drivers,switch to win7.

Mr.Ak said:
Looks like a hard brick..
Try this,
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
If having problem with drivers,switch to win7.
Click to expand...
Click to collapse
The phone does not connect to my PC. The PC does not pick up anything.

francosis said:
The phone does not connect to my PC. The PC does not pick up anything.
Click to expand...
Click to collapse
It doesn't show anything in device manager>ports?
It should show "QHS-Bulk" or "Qualcomm HS-USB Diagnostics 9006".
Which windows you're using?
Take note- This method is not equivalent to fastboot mode and it works on USB Diagnostic Port,so it will not work on fastboot drivers,you must have to install diagnostic drivers from the toolkit (drivers.exe),or alternatively you'll have to manually install drivers from this- http://www.androidbrick.com/download/latest-2017-qualcomm-diag-qd-loader-windows-10-drivers-signed/

Mr.Ak said:
It doesn't show anything in device manager>ports?
It should show "QHS-Bulk" or "Qualcomm HS-USB Diagnostics 9006".
Which windows you're using?
Take note- This method is not equivalent to fastboot mode and it works on USB Diagnostic Port,so it will not work on fastboot drivers,you must have to install diagnostic drivers from the toolkit (drivers.exe),or alternatively you'll have to manually install drivers from this-
Click to expand...
Click to collapse
I am using windows 10 and when I check device manager with device plugged I only have "Communications port (COM1) in the ports section.

francosis said:
I am using windows 10 and when I check device manager with device plugged I only have "Communications port (COM1) in the ports section.
Click to expand...
Click to collapse
Drivers installed?

Mr.Ak said:
Drivers installed?
Click to expand...
Click to collapse
Yes everyting which was asked to be installed, is installed.

francosis said:
Yes everyting which was asked to be installed, is installed.
Click to expand...
Click to collapse
You should try on win7.

Mr.Ak said:
You should try on win7.
Click to expand...
Click to collapse
I don't have any device with windows 7 though

francosis said:
I don't have any device with windows 7 though
Click to expand...
Click to collapse
Also I can't turn on the phone even if I hold power + vol up nothing happens at all.

francosis said:
Also I can't turn on the phone even if I hold power + vol up nothing happens at all.
Click to expand...
Click to collapse
You don't have to turn the device on.
I don't think dual-booting win7 alongside takes long.