Develop Bugs

USB Device Not Recognized

Was updating to FD26 phone died..... got back into odin mode with jig, plugged into comp now it says USB Device not recognized and cant odin any firmware and wont boot since it didnt finish the last firmware upgrade. Any suggestions?

Jaromewg said:
Was updating to FD26 phone died..... got back into odin mode with jig, plugged into comp now it says USB Device not recognized and cant odin any firmware and wont boot since it didnt finish the last firmware upgrade. Any suggestions?
Click to expand...
Click to collapse
I hate to say it but it sounds like it might be a brick.
Are you getting the flashing blue light with a blank screen when you try to boot our are you getting a boot loop? Are you able to boot into Recovery?

no it says "Firmware upgrade encountered an issue. Please select recovery mode in kies & try again. " i cant boot into recovery, i can into dl mode. ima try a different comp.

Jaromewg said:
no it says "Firmware upgrade encountered an issue. Please select recovery mode in kies & try again. " i cant boot into recovery, i can into dl mode. ima try a different comp.
Click to expand...
Click to collapse
If you're getting that message I can tell you its not going to work. It sounds like you were trying to flash the international version kernel for the SGSII rather than the Epic 4G Touch. When you try to flash the international version it will fail and gives you the error you're getting. Another unfortunate side-effect is that it ruins your USB (due to differences in the way the USB works). I've heard that some JTAG services can fix it but I haven't done it myself.
At this point you unfortunately are stuck with a brick. :-(
Sorry!

I might have misunderstood the other posts but I thought flashing the international version completely disabled the USB port. Yet OP seems that device is being picked up in Windows but not successfully installed.
OP, can you please confirm? Check Device Manager and look for a device with a yellow exclamation point or triangle (if Win). If you can see it here you may just need to reinstall the Samsung drivers and get it installed that way. At the worst you're not any further along than you were before...
Alternatively you could try updating the driver manually, search C:\Program Files\SAMSUNG to see if it picks up.

If you haven't done so already, uninstall Kies and download the full Samsung driver suite from here:
http://org.downloadcenter.samsung.c...342248/Sprint_d710_USB_Driver_v1_3_2360_0.exe
Install the driver and maybe we can help you from there. Or if it works, there ya go.

I just went through this...what happened on my end:
-computer froze up while i was doing stock odin repack
-went to boot up phone and that messaged flashed
what i did:
-flashed stock el26 kernel(if you can't get into odin but pull the battery and keep trying..thats what i did)
-flash a rom like you normally would
PROFIT!

AT&T Galaxy SIII Bricked While Trying to Flash Back to Stock... Desperate For Help

AT&T Galaxy SIII Bricked While Trying to Flash Back to Stock... Desperate For Help
Had my AT&T Galaxy S III rooted, stock ROM. Was having some issues after rooting so I decided to go back to bone stock, completely unroot so I flashed the I747UCALEM build from these forums on Odin 3.07. Needless to say the phone was held up mid flash, and I got a "FAIL" in Odin. When I tried to reboot the phone, I got a "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" When I reboot the phone this comes up and it's almost like a permanent download mode. I tried to reflash in Odin to unbrick the phone and it fails every single time.
Am I completely screwed? If I send it back to Samsung like this they'll see the that I rooted (didnt trip the flash counter) and void my warranty. Not sure what to do here. Thanks for any advice guys.

statusnone said:
Had my AT&T Galaxy S III rooted, stock ROM. Was having some issues after rooting so I decided to go back to bone stock, completely unroot so I flashed the I747UCALEM build from these forums on Odin 3.07. Needless to say the phone was held up mid flash, and I got a "FAIL" in Odin. When I tried to reboot the phone, I got a "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" When I reboot the phone this comes up and it's almost like a permanent download mode. I tried to reflash in Odin to unbrick the phone and it fails every single time.
Am I completely screwed? If I send it back to Samsung like this they'll see the that I rooted (didnt trip the flash counter) and void my warranty. Not sure what to do here. Thanks for any advice guys.
Click to expand...
Click to collapse
Sounds like you got a bad file re-download the AT&T software again from here http://forum.xda-developers.com/showthread.php?t=1737848 make sure you have Kies disabled i do think if its running in the background odin won't flash right don't hold me to it.and as long as you can get in download mode you should be able to fix it.also check here http://forum.xda-developers.com/showthread.php?t=1727443

statusnone said:
Had my AT&T Galaxy S III rooted, stock ROM. Was having some issues after rooting so I decided to go back to bone stock, completely unroot so I flashed the I747UCALEM build from these forums on Odin 3.07. Needless to say the phone was held up mid flash, and I got a "FAIL" in Odin. When I tried to reboot the phone, I got a "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" When I reboot the phone this comes up and it's almost like a permanent download mode. I tried to reflash in Odin to unbrick the phone and it fails every single time.
Am I completely screwed? If I send it back to Samsung like this they'll see the that I rooted (didnt trip the flash counter) and void my warranty. Not sure what to do here. Thanks for any advice guys.
Click to expand...
Click to collapse
Hmm this actually happened to me first time I tried to root (stupid computer fell asleep mid flash) however I was just able to reenter download mode and flash again, curious though , what did the screen say and where In the flash process did the Odin fail, for Me luckily it was 2/3 of the way through flashing system so I didn't have much to worry about. Though I imagine if it was writing something important like the sbl or somethimg and it failed you might be in trouble . All in all I would say try flashing again a few times maybe the file you downloaded is bad.

bec48 said:
Sounds like you got a bad file re-download the AT&T software again from here http://forum.xda-developers.com/showthread.php?t=1737848 make sure you have Kies disabled i do think if its running in the background odin won't flash right don't hold me to it.and as long as you can get in download mode you should be able to fix it.also check here http://forum.xda-developers.com/showthread.php?t=1727443
Click to expand...
Click to collapse
Downloading the UCALEM build from that link now on my laptop (my PC is notorious for connection issues with this phone, I should of known) and I'll pray for the best. Thank you very much for the help, I'll post back once I'm on my way.

I can't even download either firmwares. The direct downloads stop for some random reason at around 33 MB and there's 0 seeders for the torrent versions. Any other way to get these firmwares? Samsung updates isn't being nice tonight.

statusnone said:
I can't even download either firmwares. The direct downloads stop for some random reason at around 33 MB and there's 0 seeders for the torrent versions. Any other way to get these firmwares? Samsung updates isn't being nice tonight.
Click to expand...
Click to collapse
The update is in Kies as well.

Finally got the update to download, used a different browser. Flashed the new build through Odin and it worked, unbricked the phone. Apparently it is the connection through my regular PC. Thanks for everyones help!

[Q] Bricked Note 2?

First and foremost, thank you for any help and advise at all.
Had 4.3 ota.... Flashed cwm thru odin. Restarted the phone, it will not boot past the "samsung galaxy note 2" screen. Flashed stock rom thru odin, still stuck at the samsung note 2 screen. I can get into download mode with no issues whatsoever. I cannot get into recovery mode, whether stock or cwm. Nothing. Can I flash another 4.3 or 4.4 rom thru odin? I just need my phone working again..... thanks gentlemen

Also, I have tried flashing back to stock with odin, I have tried flashing to and earlier version with odin. Nothing. As stated above, I can get into download mode. I cannot get into recovery of any kind. Also, I have no idea how to enter emergency recovery mode to try and restore with kies...... I am lost and have a paper weight as of now thanks again guys

http://forum.xda-developers.com/showthread.php?t=2581321
This is the only known method so far and it is not working for everyone but at this point I'd say it is your best and only hope.
Did you thank your Developer today?

Thanks.... Tried that but nothing still samsung note 2 screen only...... Downloading newest odin and a 4.3 stock rom, we shall see......

solomon316 said:
Thanks.... Tried that but nothing still samsung note 2 screen only...... Downloading newest odin and a 4.3 stock rom, we shall see......
Click to expand...
Click to collapse
Where I can get those 4.3 stock and odin?

https://mega.co.nz/#!bg4QVLqI!H-nB_jZlsStgzcF4POd432atbOVHwkzrOPIeHQPOQUQ

Ok, guys, finally made some if little progress..... got the phone into kies firmware recovery mode........ now, I'm still waiting for kies to recognize my note 2 been connecting for 5 minutes now...... If it would just see the phone I could do the emergency recover (HOPEFULLY) and waiting.......

And still waiting for kies to connect to my note 2.......

solomon316 said:
And still waiting for kies to connect to my note 2.......
Click to expand...
Click to collapse
It wont connect!! Stop wasting your time.... I've been there.......................

Rooted 4.3 OTA?
solomon316 said:
First and foremost, thank you for any help and advise at all.
Had 4.3 ota.... Flashed cwm thru odin. Restarted the phone, it will not boot past the "samsung galaxy note 2" screen. Flashed stock rom thru odin, still stuck at the samsung note 2 screen. I can get into download mode with no issues whatsoever. I cannot get into recovery mode, whether stock or cwm. Nothing. Can I flash another 4.3 or 4.4 rom thru odin? I just need my phone working again..... thanks gentlemen
Click to expand...
Click to collapse
Was your 4.3 OTA rooted before you flashed CWM?

I'm having similar issues. Stuck on the Note II screen, and no recovery. I have only ever had stock recovery. I can get into download mode, but ven after using Odin to get back to stock, I have the same issue. I assume this has something to do with the boot loader. Does anyone have a fix for this?

Use Kies to emergency recover back to stock 4.1.1.
Steps. (READ ALL BEFORE STARTING)
1.) Downloads Kies onto your pc
2.) Install drivers to pic
3.) Open Kies and go to TOOLS > instal/upgrade firmware.
4.) Kies will ask you for you device model. AT&T = SHE I317. And your serial number. Located behind the battery.
5.) Hit start in Kies it will down load the stock firmware to your PC. Follow the instructions.
6.) It will eventually ask you to put your phone in download mode and connect it to the pc. Do this.
7.) Don't touch it. It is going to take about 10-20 min depending on your Internet speed and your computer.
When it is complete your phone will be back to stock. The same it was the day you pulled it out of the box.
***I would also make sure you back up any data on your phone because it will delete the sd card. It is also wise to remove any external storage sd.
****when finished you can re root using cf auto root or take the OTA update to get you back to 4.3.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

ShrekOpher said:
Use Kies to emergency recover back to stock 4.1.1.
Steps. (READ ALL BEFORE STARTING)
1.) Downloads Kies onto your pc
2.) Install drivers to pic
3.) Open Kies and go to TOOLS > instal/upgrade firmware.
4.) Kies will ask you for you device model. AT&T = SHE I317. And your serial number. Located behind the battery.
5.) Hit start in Kies it will down load the stock firmware to your PC. Follow the instructions.
6.) It will eventually ask you to put your phone in download mode and connect it to the pc. Do this.
7.) Don't touch it. It is going to take about 10-20 min depending on your Internet speed and your computer.
When it is complete your phone will be back to stock. The same it was the day you pulled it out of the box.
***I would also make sure you back up any data on your phone because it will delete the sd card. It is also wise to remove any external storage sd.
****when finished you can re root using cf auto root or take the OTA update to get you back to 4.3.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
Kies doesnt work. It does the whole process and then fails with an error message and put the phone in emergency recovery mode but does not give you a recovery code.

What is the error you get in Kies?
If you are using Kies correctly it should work. It is designed to completely restore your phone.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

ShrekOpher said:
Use Kies to emergency recover back to stock 4.1.1.
Steps. (READ ALL BEFORE STARTING)
1.) Downloads Kies onto your pc
2.) Install drivers to pic
3.) Open Kies and go to TOOLS > instal/upgrade firmware.
4.) Kies will ask you for you device model. AT&T = SHE I317. And your serial number. Located behind the battery.
5.) Hit start in Kies it will down load the stock firmware to your PC. Follow the instructions.
6.) It will eventually ask you to put your phone in download mode and connect it to the pc. Do this.
7.) Don't touch it. It is going to take about 10-20 min depending on your Internet speed and your computer.
When it is complete your phone will be back to stock. The same it was the day you pulled it out of the box.
***I would also make sure you back up any data on your phone because it will delete the sd card. It is also wise to remove any external storage sd.
****when finished you can re root using cf auto root or take the OTA update to get you back to 4.3.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
It does not take my phone model number "sgh i317".
---------- Post added at 10:29 AM ---------- Previous post was at 09:34 AM ----------
ShrekOpher said:
Use Kies to emergency recover back to stock 4.1.1.
Steps. (READ ALL BEFORE STARTING)
1.) Downloads Kies onto your pc
2.) Install drivers to pic
3.) Open Kies and go to TOOLS > instal/upgrade firmware.
4.) Kies will ask you for you device model. AT&T = SHE I317. And your serial number. Located behind the battery.
5.) Hit start in Kies it will down load the stock firmware to your PC. Follow the instructions.
6.) It will eventually ask you to put your phone in download mode and connect it to the pc. Do this.
7.) Don't touch it. It is going to take about 10-20 min depending on your Internet speed and your computer.
When it is complete your phone will be back to stock. The same it was the day you pulled it out of the box.
***I would also make sure you back up any data on your phone because it will delete the sd card. It is also wise to remove any external storage sd.
****when finished you can re root using cf auto root or take the OTA update to get you back to 4.3.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
It gives you an error! It does not say what kind of error, it said, just an error, and contact Samsung support.
Yet, on phone display I am getting : "Unsupported Version" in red message.
So, I am guessing - THIS is a good way to recover your Note2 IF, and only IF your phone is NOT bricked.
Damn, I am very close to smash that thing into the wall.................
Lets arrange the facts, BC there must be the way out................
One CAN get back from 4.3 (or even from 4.4) to 4.1.1. I know i did.
All was fine until receiving first OTA update to 4.1.2
And this is when one got stock in white letters Galaxy Note II screen............any ideas why?

fuzio1963 said:
It does not take my phone model number "sgh i317".
---------- Post added at 10:29 AM ---------- Previous post was at 09:34 AM ----------
It gives you an error! It does not say what kind of error, it said, just an error, and contact Samsung support.
Yet, on phone display I am getting : "Unsupported Version" in red message.
So, I am guessing - THIS is a good way to recover your Note2 IF, and only IF your phone is NOT bricked.
Damn, I am very close to smash that thing into the wall.................
Lets arrange the facts, BC there must be the way out................
One CAN get back from 4.3 (or even from 4.4) to 4.1.1. I know i did.
All was fine until receiving first OTA update to 4.1.2
And this is when one got stock in white letters Galaxy Note II screen............any ideas why?
Click to expand...
Click to collapse
OKAY GUYS!!!! SOLUTION FOUND!!!!
Just un-zip, and install this http://www.androidfilehost.com/?fid=23212708291677024 in ODIN 3.07
Finally, it worked for me!!!!

fuzio1963 said:
OKAY GUYS!!!! SOLUTION FOUND!!!!
Just un-zip, and install this http://www.androidfilehost.com/?fid=23212708291677024 in ODIN 3.07
Finally, it worked for me!!!!
Click to expand...
Click to collapse
I can confirm this worked. Phone is no longer bricked.

fuzio1963 said:
OKAY GUYS!!!! SOLUTION FOUND!!!!
Just un-zip, and install this http://www.androidfilehost.com/?fid=23212708291677024 in ODIN 3.07
Finally, it worked for me!!!!
Click to expand...
Click to collapse
Not sure how you came to try this but great job. I did massive testing yesterday with Zen trying to get from stock LJ2 ODIN, all the way to the 4.3 update.
I never thought it was possible, but encountered the same problem of not being able to get to recovery. Regardless of what I tried.
Luckily I remembered you and found this.
That was crazy, I thought my phone was toast. Thanks again.

Had a similar experience recently moving to jedi master x2
After reboot I was left staring at the galaxy note 2 screen for an hour.
Nothing I would typically have done worked including a restore of my nandroid.
So i went back to basics.
Used Odin 2.85
Switched to CWM from TWRP(i prefer and am back on TWRP)
From CWM I was able to finally install the rom and get to swipe screen.
I was still anxious on boot and it took a while though.
good luck

You rocked. This worked absolutely fine. Where did you find this file.
dicksteele said:
Not sure how you came to try this but great job. I did massive testing yesterday with Zen trying to get from stock LJ2 ODIN, all the way to the 4.3 update.
I never thought it was possible, but encountered the same problem of not being able to get to recovery. Regardless of what I tried.
Luckily I remembered you and found this.
That was crazy, I thought my phone was toast. Thanks again.
Click to expand...
Click to collapse
This worked absolutely fine. Even I was stuck on Samsung logo and dint know wat to do I just flashed this file via odin 3.07 and my phone started like a charm. Thanks a lot

attempted to root and failed, need help please

Hi, I started out with a stock tmobile s3 and tried to root it for the first time today, I followed this video
http://www.youtube.com/watch?v=mndQZqom3Ac
which asked me to use this cf-root 6.4
http://forum.xda-developers.com/showthread.php?t=1695238
when I hit start on that .tar file under odin, it failed stating "complete (write)operation failed)
since then, my device would boot with error "firmware upgrade encountered an issue" nothing else would happen.
I tried to go into recovery mode again and this time when I tried to retry the odin tar install, it would give me a new fail of cannot open com3
When I tried to use kies, it would just forever try to connect and never connect. so I couldnt do anything there.
What can I do? I would preferably try to retain all my saved data.
I also suspect my usb port might be faulty, sometimes need to press it in firmly to make the usb mass storage to work properly.
Thanks in advance

What is your Current android version ?

Perseus71 said:
What is your Current android version ?
Click to expand...
Click to collapse
i really didnt note which version i have... noob mistake i kmow. i think it is 4.2...is there any way i can check?

Ok, I totally messed up when I first attempted this. The .tar I used was for an international s3 and I have a tmobile us version!. the OP of the thread says it may even brick my phone if I attempt this on a non international version.
competely my fault, but what should I do to fix this and save my phone?
I cannot connect to kies, reinstalled the drivers and it still wont connect. just gets stuck in "connecting"
The odin now doesnt load a tar because it says "cannot open com3 "
EDIT:
fixed it, odin was not working due to kies running in the background and I finally was able to flash the correct chainfire for my phone

Glad its sorted out. I assume no issues now ?

[Q] S4 mini i9195 bricked

Ok guys, I was an idiot and got a little greedy and opened a thread saying update your s4 mini LTE to an OFFICIAL 4.4.2 kitkat. Without even checking the comments I just downloaded and followed the instructions. It was a 4.2.2 "upgrade" and it didn't work.. Used Odin 3.09. and it showed the error "FAIL! (Ext4)"
Now my phone is stuck in download mode with the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." Well, that would all be nice if I could. Kies doesn't let me connect my phone to it, when I try Emergency recovery it doesn't show it in the list of devices, initialisation is not available for GT-19195 (??) (it's the option where i type in my phone model and serial number).
I can't put the phone itself into recovery mode, pressing volume up, home and power buttons, so that option is also out.
I have no idea what else to do right now, and I would appriciate any help you guys can provide.
What do I do to get my phone working again?!
Thanks in advance.

iwanvs said:
Ok guys, I was an idiot and got a little greedy and opened a thread saying update your s4 mini LTE to an OFFICIAL 4.4.2 kitkat. Without even checking the comments I just downloaded and followed the instructions. It was a 4.2.2 "upgrade" and it didn't work.. Used Odin 3.09. and it showed the error "FAIL! (Ext4)"
Now my phone is stuck in download mode with the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." Well, that would all be nice if I could. Kies doesn't let me connect my phone to it, when I try Emergency recovery it doesn't show it in the list of devices, initialisation is not available for GT-19195 (??) (it's the option where i type in my phone model and serial number).
I can't put the phone itself into recovery mode, pressing volume up, home and power buttons, so that option is also out.
I have no idea what else to do right now, and I would appriciate any help you guys can provide.
What do I do to get my phone working again?!
Thanks in advance.
Click to expand...
Click to collapse
So you can get to download mode but odin fails?
What are you trying to flash?
You can also flash a full samsung firmware via odin (you can find it at sammobile.com)
If this doesn't work you can try to flash cwm recovery

I've had this issue myself before and found flashing a cwm recovery via Odin then adb sideload either a custom or stock rom generally fixes the issue.
Hope all work's out for you
Sent from my GT-I9195 using Tapatalk

I have managed to find a 4.2.2 stock ROM from ny region, it's for the Telenor network, I am not on it but my carrier is another, although that does not seem to be a problem. Flashed it through Odin, v3.09, and I'm happy to say I'm writing this from my phone!
To answer your question, yes, the only thing i was able to start download mode on my phone, just turning it on, it went straight to that. Also, I had to wipe cache from recovery to stop it from looping the samsung logo and also had to do a factory reset & delete everything once i got past samsung logo loop. It's working as inteded now, and well, I guess a new fresh start is not that bad.
Thanks for your ideas guys.

GT-I9195 bRICKED SAME ISSUE
superkoal said:
So you can get to download mode but odin fails?
What are you trying to flash?
You can also flash a full samsung firmware via odin (you can find it at sammobile.com)
If this doesn't work you can try to flash cwm recovery
Click to expand...
Click to collapse
Hi i have the same problem. worried the phone is soft bricked. cant do any thing now. What do u mean by "try flash cwm recovery" how sould i do it any links would be helpful...
Please please help me...
Thanks...
---------- Post added at 03:52 PM ---------- Previous post was at 03:43 PM ----------
superkoal said:
So you can get to download mode but odin fails?
What are you trying to flash?
You can also flash a full samsung firmware via odin (you can find it at sammobile.com)
If this doesn't work you can try to flash cwm recovery
Click to expand...
Click to collapse
Scopewiz said:
I've had this issue myself before and found flashing a cwm recovery via Odin then adb sideload either a custom or stock rom generally fixes the issue.
Hope all work's out for you
Sent from my GT-I9195 using Tapatalk
Click to expand...
Click to collapse
Hi how do u do the cwm recovery andadb sideload the custom or stock rom... i am very new to this tech... please guide and help
Thanks & regards
Jeetesh
---------- Post added at 04:00 PM ---------- Previous post was at 03:52 PM ----------
iwanvs said:
I have managed to find a 4.2.2 stock ROM from ny region, it's for the Telenor network, I am not on it but my carrier is another, although that does not seem to be a problem. Flashed it through Odin, v3.09, and I'm happy to say I'm writing this from my phone!
To answer your question, yes, the only thing i was able to start download mode on my phone, just turning it on, it went straight to that. Also, I had to wipe cache from recovery to stop it from looping the samsung logo and also had to do a factory reset & delete everything once i got past samsung logo loop. It's working as inteded now, and well, I guess a new fresh start is not that bad.
Thanks for your ideas guys.
Click to expand...
Click to collapse
Hi dude,
please share the link and how to go about it as i am struck with th same issue... tensed & worried please help
Thanks & Regards

s4 mini bricked
Hi i have problem i tried to root my phone(cwm recovery i cant post link yet ) but this is only for android 4.2.2 jelly bean but my is 4.2.2 kitkat and i root the phone and i folowed the steps but when i try to power up the phone in top left corner it says set waranty bit:karnel and after that i hear samsung power up sound and then just black screen i tried everything can anyone help me please?

the guy 1950 said:
Hi i have problem i tried to root my phone(cwm recovery i cant post link yet ) but this is only for android 4.2.2 jelly bean but my is 4.2.2 kitkat and i root the phone and i folowed the steps but when i try to power up the phone in top left corner it says set waranty bit:karnel and after that i hear samsung power up sound and then just black screen i tried everything can anyone help me please?
Click to expand...
Click to collapse
Shouldn't be a problem if you use the arco recovery wipe cache, warranty bit kernel means h that you're using different kernel from the original that came with the phone, probably you have tripped Knox 0x1 voiding warranty, you could flash an kk kernel and will be fine

Frends please help i put bad TWRP via terminal and now I cant go to download mode so can some solutions for me

Lybross said:
Frends please help i put bad TWRP via terminal and now I cant go to download mode so can some solutions for me
Click to expand...
Click to collapse
I've never had this sort of problem and I am no expert but this is what I would try. The good news is it should be recoverable, lets hope one of the experts sees this. You really need to give more info!
If in a boot loop you may be able to get into download mode by just pressing the vol down & home key (not power as you are already powered up). If this doesn't work try all other key combos as you need to get out of the current reboot mode into something else.
If that doesn't work or you are not in a bootloop then use ADB to see if device shows up, if it does, then "reboot bootloader"
If that doesn't work make or buy a jig, that will allow you to set download mode.