I have a Samsung galaxy S3 SGH-I747 ATT. I followed the steps on xda developers forum here to root and unlock bootloader using the samsung galaxy toolkit. I have not installed any custom roms as yet. I just copied the zip for Hyderdrive onto my phone and restarted it. Boom! Phone doesn't start. Tried recovery,download and just powering on, no luck. The phone doesn't get recognized on Odin. But, it still gets detected on the toolkit. But for me to do anything it asks me to enable USB debugging, which I am not able to cause the phone doesn't switch on. I tried just pluggin in and plugging out the usb cable. It makes the beep noise that we hear when we connect the phone to the system, but that's about it. Doesn't get recognized as a drive on the computer. Is this a hardbrick?
Edit: I don't think it's being recognized on the toolkit. I don't see any serial number on it.
Hyderdrive? whats that? You don't need to unlock the bootloader for the s3, it comes unlocked. Your phone can't be bricked just by copying a zip file to it.
What exactly did you do?
m82a1 said:
Hyderdrive? whats that? You don't need to unlock the bootloader for the s3, it comes unlocked. Your phone can't be bricked just by copying a zip file to it.
What exactly did you do?
Click to expand...
Click to collapse
That's pretty much exactly what happened.
Installed device drivers.
Backed up my data.
Rooted the phone by following all the steps. [ The problem is I do not remember if I chose Clockworkmod Recovery or TWRP Touch Recovery ]
Installed and Ran EZ-Unlock -- to unlock bootloader.
** At this point, My phone is rooted and I can access superU and EZ-Unlock apps.
**Here's the part I'm not too sure of.
From the main menu of the toolkit, I chose:
option 5 [Flash Custom Recovery via Odin] and chose option 1 [Flash Clockworkmod Recovery] -- This I am certain of.
So using Odin-->Pad-->I browse to the directory of the recovery file in the toolkit folder and Run it. I get the RESET Okay message on Odin. Should I be seeing a green PASS message on top? I'm not too sure. I only got a RESET in purple.
Exit out of odin.
Downloaded Hyperdrive RLS15 from here
Copied the Zip into my phone.
[Phone works perfectly fine till here]
I power off the phone and try to start in the recovery, download mode. Nothing works.
You ran an app to unlock a Verizon S3 bootloader, a process which 1. is unnecessary on an AT&T S3 and 2. will seriously mess with the bootloader which will hard brick your phone. If you take a look in this thread, you'll see that you pretty much have to send it somewhere to get it fixed.
FoxTrotz said:
You ran an app to unlock a Verizon S3 bootloader, a process which 1. is unnecessary on an AT&T S3 and 2. will seriously mess with the bootloader which will hard brick your phone. If you take a look in this thread, you'll see that you pretty much have to send it somewhere to get it fixed.
Click to expand...
Click to collapse
Well, that explains a lot. Thanks for your help. I'll probably have to send it in to get it fixed. FML.
Related
been looking around on here. im stuck now
Ok iv unlocked and have root and can load into Clockwork 5.5.0.2
But when in Clockwork i get
E:can't mount /sdcard/
When i reboot the nexus now all i get is the Google Logo with the unlock Padlock.
Once it did load back into OS and then rebooted it self now stuck on Google logo and Unlock padlock... i Didnt copy over my ROM too the SDCard....
How do i get back into the OS
Flash the factory Google images via fastboot. Search the forum. There a quite a few threads with step by step instructions.
Sent from my Galaxy Nexus using xda premium
Try pressing the volume down button and power button until you reach recovery. When you a red triangle, press Vol+/Vol-/Power at the same time, you will now see a menu, select factory data reset.
I've been in your shoes, and I doubt a factory reset will help. If I were you, I would download the stock images first (lte or GSM nexus?). After that, try seeing if your drivers are configured and that tour phone is being recognized by your computer when it is plugged in with the USB cable. The drivers will need to be configured for when the phone is showing the Google logo, but also configured again when the phone is in the boot loader. (Ask if you need more instructions for this).
OK, what worked for me was locking and then unlocking my phone again. Type fast boot OEM lock, and if the drivers are good then the boot loader will lock. Then type fast boot OEM unlock and it will wipe everything--even Android backups. It shoud also delete the problem. After that you can push files to it from the computer but you might have to configure your drivers again (I did). Hope this helps, it worked for me.
??
throwbot said:
I've been in your shoes, and I doubt a factory reset will help. If I were you, I would download the stock images first (lte or GSM nexus?). After that, try seeing if your drivers are configured and that tour phone is being recognized by your computer when it is plugged in with the USB cable. The drivers will need to be configured for when the phone is showing the Google logo, but also configured again when the phone is in the boot loader. (Ask if you need more instructions for this).
OK, what worked for me was locking and then unlocking my phone again. Type fast boot OEM lock, and if the drivers are good then the boot loader will lock. Then type fast boot OEM unlock and it will wipe everything--even Android backups. It shoud also delete the problem. After that you can push files to it from the computer but you might have to configure your drivers again (I did). Hope this helps, it worked for me.
Click to expand...
Click to collapse
I can connect the phone and lock n unlock the bootloader. so the USB drivers ar working. but iv got no way of pushing the files onto it
NxsLS said:
I can connect the phone and lock n unlock the bootloader. so the USB drivers ar working. but iv got no way of pushing the files onto it
Click to expand...
Click to collapse
Have you tried flashing via fastboot? I would assume if fastboot oem unlock/lock works, then flashing using fastboot/android sdk should work.
...though, as a non dev, i have been wrong before
what do you mean by "pushing the files"? What are you trying to push?
Sent from my Galaxy Nexus using XDA App
Good, make sure you boot loader has been unlocked. You can use a program like the root toolkit (I don't think I can put a link to a different website) but he root toolkit for the nexus should help you push the stock image to your phone. Go to droid-life (.com, cough cough) and there is a set of instructions for returning back to stock. You can also use those same instructions to try and get her back up and running. Try the root toolkit they have on there, too. The only problem you might run into is having your phone set to USB debugging after unlocking the boot loader, bit it should still accept fast boot commands while I'm the bootloader
---------- Post added at 09:48 PM ---------- Previous post was at 09:42 PM ----------
sorry, by pushing the files I mean pushing the stock image file (the stock software, including the stock operating system, stock bootloader, and stock radios). A rom is a custom tweaked version of the stock software. When you unlock the bootloader, if you don't have stock software on there (which you wont if you were running a rom when it crashed) then it might erase everything, including the from you were running. You will have to push that stock software (stock image file) back to your phone using commands from your computer
no worrys o2 just sending me a new nexus :x
report lost n stolen :x only £30 ex
NxsLS said:
report lost n stolen :x only £30 ex
Click to expand...
Click to collapse
I hate that.. because you didn't know what you were doing and screwed up your phone someone is supposed to provide you with a new one? As a few posters have already said, it should be a fairly easy fix. You didn't even acknowledge that you tried any of the suggested fixes. If you're going to mess around with your phone make sure you know what you're doing, or at the very least exhaust all potential options to get yourself out of a soft brick. I'm sure an experienced Android user could have you up and running in 10 minutes. It's no wonder providers don't want to unlock bootloaders on some phones.. Jesus...
i tryed all i got it too boot back into the OS but reset itself and locked in google with unlocked padlock. so gave up and will not make the same mistake of not copying over the rom after the root n unlock.. i have flashed/unlocked my samsung s2 with ODIN which was easy but the Nexus i used Galaxy Nexus ToolKit
Ok, so i rooted my phone on my mac from galaxys3root.com
I then decided i wanted to root my phone from windows instead as i thought it was a more stable way (new to rooting)
so i went through the unrooting steps on that same website. downloaded triangle away and reset the binary.
step 2 was to put into download mode, so i help vol down, home and power button. screen went black and thats it.
now phone wont turn on, and wont go into download mode.
am i screwed?
So you were already rooted, then unrooted and tried to root again? Why? As long as the phone is rooted you can flash ROMs regardless of computer, as long as u can get all the files onto ur phone to flash in recovery
Sent from my SGH-I747 using xda app-developers app
DarthDerron said:
So you were already rooted, then unrooted and tried to root again? Why? As long as the phone is rooted you can flash ROMs regardless of computer, as long as u can get all the files onto ur phone to flash in recovery
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
im not sure, im new to rooting.
i thought it wasnt stable or something because rooting through mac you dont go into download mode or recovery mode
(i cant get into download or recovery. My phone is completely off, the only sign of life ive seen from it now is a red led light come on when i plug into usb without the batter in)
can anyone help?
MarkBonz said:
im not sure, im new to rooting.
i thought it wasnt stable or something because rooting through mac you dont go into download mode or recovery mode
(i cant get into download or recovery. My phone is completely off, the only sign of life ive seen from it now is a red led light come on when i plug into usb without the batter in)
Click to expand...
Click to collapse
Then sorry, nothing I can help you with
I suggest taking it to AT&T. That was the only sign of life I had after I dropped my rooted phone, they replaced it under warranty. To be clear, my phone was under two out-of-warranty conditions, and it was replaced because the cause of failure isn't so readily apparent in this case. Just say you don't know why it won't turn on. Too easy.
mag7ear appears
When plugged into my computer, it says
found new hardware QHSUSB_DLOAD
does that mean anything
I think that means it's dead, though I could be mistaken. I'm surprised no one recommended finding a USB jig. They're supposed to force the phone into download mode when nothing else will. It's not clear if that would work in this case, but they're extremely cheap.
MarkBonz said:
When plugged into my computer, it says
found new hardware QHSUSB_DLOAD
does that mean anything
Click to expand...
Click to collapse
Send it to samsung They can fix it for freee.
But for 60 bucks or so JTAG can get it done allittle bit quicker
Before you try sending it away, I would try downloading MSKIP's Galaxy S3 toolkit. Make sure you have all the relevant drivers and see if the toolkit is able to see it and kick it into download mode. You can find the download link here http://forum.xda-developers.com/forumdisplay.php?f=1633
There are very clear, explicit instructions provided with the toolkit - I would also take the time to view wwjoshdew's video, very helpful. If you are able to get the phone into download mode, re-flash a stock, rooted rom from here: http://forum.xda-developers.com/showthread.php?t=1739426
Not sure what else to tell you, but that's what I would try. Hope it helps.
-GB
GladdBag said:
Before you try sending it away, I would try downloading MSKIP's Galaxy S3 toolkit. Make sure you have all the relevant drivers and see if the toolkit is able to see it and kick it into download mode. You can find the download link here http://forum.xda-developers.com/forumdisplay.php?f=1633
There are very clear, explicit instructions provided with the toolkit - I would also take the time to view wwjoshdew's video, very helpful. If you are able to get the phone into download mode, re-flash a stock, rooted rom from here: http://forum.xda-developers.com/showthread.php?t=1739426
Not sure what else to tell you, but that's what I would try. Hope it helps.
-GB
Click to expand...
Click to collapse
thanks anyways, but toolkit cant read phone
Newbie to rooting, using a VZW Galaxy Nexus.
I tried flashing 4.2.2 this evening, and somewhere along the way I bricked my phone. Simply turning on the phone results in the Google and Unlock icon screen, as does pressing Power and Volume Up. I can only boot into Odin mode (with Power + Volume Down), which I discovered by accident, and I've no idea what that does.
At this point, I'd be happy just getting back to stock 4.1.1. Any and all help greatly appreciated.
ODIN has no place being used on a Nexus device. You are in fastboot mode. There are several stickies at the top of this section on how to properly root your device. Read them.
063_XOBX said:
ODIN has no place being used on a Nexus device. You are in fastboot mode. There are several stickies at the top of this section on how to properly root your device. Read them.
Click to expand...
Click to collapse
I wasn't trying to use Odin; it's simply the only thing my phone will do at this point. The actual rooting of the phone went fine - I used Nexus Root Toolkit (1.6.3). The phone bricked when I was attempting to restore the backup I'd made.
My computer won't recognize the phone when plugged in. I downloaded drivers from Samsung - nothing. The Toolkit doesn't find the phone when attached.
I'm at a loss.
Again. Follow the stickies right at the top of this section.
You're at a loss because you used a toolkit rather than the slightly more challenging and infinitely more educational "right" way.
Have you tried booting with volume up+down+power, to see if the bootloader is still there?
salvation eedsfur
bodh said:
Have you tried booting with volume up+down+power, to see if the bootloader is still there?
Click to expand...
Click to collapse
Just tried and yes, bootloader is still there. But since my computer won't recognize the phone (I've tried installing and re-installing the ADB drivers), I can't figure out how to flash a ROM (stock or otherwise).
http://forum.xda-developers.com/showthread.php?t=1626895 You need fastboot drivers in fastboot / bootloader mode. And you're all set.
bodh said:
http://forum.xda-developers.com/showthread.php?t=1626895 You need fastboot drivers in fastboot / bootloader mode. And you're all set.
Click to expand...
Click to collapse
So far, so good. Still had issues installing the ADB driver, but finally got it to work. Many, many thanks.
If you can't flash your device in a regular way (via fastboot) there's also a possibility for Odin flash. It's not recommended but it works (it has never let me down). There are few threads about it.
m.kochan10 said:
If you can't flash your device in a regular way (via fastboot) there's also a possibility for Odin flash. It's not recommended but it works (it has never let me down). There are few threads about it.
Click to expand...
Click to collapse
Thanks, m.kochan - the problem was getting the computer to recognize the device. It finally came down to trail-and-error with installing and re-installing drivers. I had to boot into recovery, uninstall every Samsung/Google/Android related driver, reboot the computer, then install only the ADB driver. From there, I was able to flash the stock image using efrant's guide for dummies.
I just got the Galaxy note 2 L900. It is rooted and modified for international using. It works perfect and I was about to explore the Jelly bean 4.2.2 several times but later the battery felt out (phone has no back cover). I inserted the battery back and booted but it only started then stopped at xiaomi.com logo and the phone was frozen as brick with no control at all.
So how could I recover the custom ROM. I have never done this and I really need help. Thank you you all.
Are you able to get the device into Download mode? When turning the device on hold the power button, vol down, and the home button and the device should enter download mode.
icu814 said:
Are you able to get the device into Download mode? When turning the device on hold the power button, vol down, and the home button and the device should enter download mode.
Click to expand...
Click to collapse
Thank you. I did this before I posted this matter but the question is which files I need to download and where I can find these files? Is is in the phone already? as I said I have never done this before.
If you can get into Download mode you can ODIN any ROM you would like to the device and fix the not booting problem. You can re-flash the ROM you were using if you choose. You would need to find an ODIN tar file to use this option to get your device working again.
icu814 said:
If you can get into Download mode you can ODIN any ROM you would like to the device and fix the not booting problem. You can re-flash the ROM you were using if you choose. You would need to find an ODIN tar file to use this option to get your device working again.
Click to expand...
Click to collapse
Thanks again for your reply. It must be easier for me if I do the rooting or flashing of this phone from the beginning. I would read and following instruction step by step but right now it likes I am right in the middle of the jungle and really don't know where I should start. I looked for "ODIN tar file" and one link lead me to download the "odin multi downloader v3 95 exe.rar" but I found in here many files to download and one of these files is "Root mobile ODIN Pro v3 65 full" is the only file close to what I am looking for but I am not sure this is the file I need. I really needed help on this matter. You are the only one who replied my question and I believe that you can help. I wonder that you could text and help me through this matter. I would appreciate this. Thank you again
Abtran 941-882-0382
Send me the service provider you use and I will see if I can find an ODIN flashable ROM for your device. I can link you to the download and we can go from there. The first part though is finding a flashable image.
icu814 said:
Send me the service provider you use and I will see if I can find an ODIN flashable ROM for your device. I can link you to the download and we can go from there. The first part though is finding a flashable image.
Click to expand...
Click to collapse
I have no idea. This phone has bad ESN and was modified for international using so it has a SIM card port now for GSM network (that the seller told me). I just have this phone in 2 day only and as I said I just played with in about 1 hours to see what options the phone could provide before the battery felt out issue. I not sure it can be use with ATT or Tmobile when it has bad ESN. I didn't tried it. I bought it on ebay for my cousin in Vietnam (price cheaper to Good ESN). So I guess it must be best for an ODIN flashable ROM for gsm network. Thank you.
The phone might not have a bad ESN it just might not be recognizing a network due to an invalid SIM or no SIM at all. The phone might work and find a network if a good SIM is put into the device. The first thing I would do though is find a stock image that is for a GSM phone. You can attempt to find out what service provider your cousin is going to use but to be honest it really does not matter with a GSM carrier and a phone that does not have SIM card restrictions which I am sure this one does not. You can look for a flashable image for Docomo, AT&T, or some other GSM provider. That will at least get you into the device so you can check out the options. You could always contact the person you got the device from and see what ROM they had installed and go back with that. Just a few suggestions.
icu814 said:
The phone might not have a bad ESN it just might not be recognizing a network due to an invalid SIM or no SIM at all. The phone might work and find a network if a good SIM is put into the device. The first thing I would do though is find a stock image that is for a GSM phone. You can attempt to find out what service provider your cousin is going to use but to be honest it really does not matter with a GSM carrier and a phone that does not have SIM card restrictions which I am sure this one does not. You can look for a flashable image for Docomo, AT&T, or some other GSM provider. That will at least get you into the device so you can check out the options. You could always contact the person you got the device from and see what ROM they had installed and go back with that. Just a few suggestions.
Click to expand...
Click to collapse
So why we don't try Tmobile (I am using Ptel and Ptel base on Tmobile). IF it works on Tmobile then it can be unlocked later. (but I am sure the seller he told this phone has bad ESN)
Thank you.
From what I have found T-Mobile did not put out the Galaxy Nexus device. There is an option that you can try though. You can use the Galaxy Nexus Toolkit to flash stock images through ODIN and root any build you choose to use.
http://forum.xda-developers.com/showthread.php?t=1392310
Check out this thread for the download. The toolkit provides step by step instructions when you are performing the various actions. You will need to manually boot into download mode like you did before in order to use the ODIN feature in the toolkit. Make sure you select a stock/factory image for a GSM device.
icu814 said:
From what I have found T-Mobile did not put out the Galaxy Nexus device. There is an option that you can try though. You can use the Galaxy Nexus Toolkit to flash stock images through ODIN and root any build you choose to use.
http://forum.xda-developers.com/showthread.php?t=1392310
Check out this thread for the download. The toolkit provides step by step instructions when you are performing the various actions. You will need to manually boot into download mode like you did before in order to use the ODIN feature in the toolkit. Make sure you select a stock/factory image for a GSM device.
Click to expand...
Click to collapse
Wow. It seems too complicated. I downloaded and installed the Galaxy Nexus toolkit with GSM model 4.2.2 JDQ39 Build
in the menu it says: install/uninstall device driver on your PC [unplug device first] and many other instructions after that
But my question is where I should start from which application? I open the Galaxy Nexus toolkit folder and there are many applications in there. Should I use the Odin3_v3.07 to begin?
Do you know any "step by step instruction from the beginning"? I don't even know how to use the Odin3_v3.07 yet.
No there should be something in the ToolKit forlder named ToolKit.exe and that is what you want to open. All commands are run through the toolkit and when running it will look like a command prompt window with number options that you will type in. Commands will be displayed on the screen and you just type in the corresponding number to select options. The on screen instructions will tell you what to do at each step.
icu814 said:
No there should be something in the ToolKit forlder named ToolKit.exe and that is what you want to open. All commands are run through the toolkit and when running it will look like a command prompt window with number options that you will type in. Commands will be displayed on the screen and you just type in the corresponding number to select options. The on screen instructions will tell you what to do at each step.
Click to expand...
Click to collapse
I did come to the prompt window and enter the option 1 : Install/Uninstall Device Driver on your PC (checked and saw driver on toolkit). Then reboot the phone (I guess in fastboot mode but holding vol down power and home keys) but I cannot get the serial number as show in the instruction and the phone show no activity at all. I checked toolkit and did see the USB connected Did I do something wrong?
There is a note in the command prompt window: make sure your device is booted fully into android. (how I am sure the phone is fully boot into android)
Please advice. Thank you
All the options that are listed that say booted into Android your not going to be able to use. You should be able to use any option that says via ODIN in the name of the option. When the toolkit attempts to reboot the phone and wait for fastboot you should be good if you are already in Download mode. You might have the option to flash a stock ROM via ODIN. If so that will at least get you into the phone and you can use other options in the toolkit from that point.
icu814 said:
All the options that are listed that say booted into Android your not going to be able to use. You should be able to use any option that says via ODIN in the name of the option. When the toolkit attempts to reboot the phone and wait for fastboot you should be good if you are already in Download mode. You might have the option to flash a stock ROM via ODIN. If so that will at least get you into the phone and you can use other options in the toolkit from that point.
Click to expand...
Click to collapse
I tried most of the options but I could not get any control of phone in download mode. EX: I click on option 11: boot or flash .img file to device then it prompted "file not found." Other options I only message "waiting for the device" but there was nothing happen then.
I researched for the flashing the phone from beginning again but it seems nothing works for the bricked phone.
abbuyacc said:
I tried most of the options but I could not get any control of phone in download mode. EX: I click on option 11: boot or flash .img file to device then it prompted "file not found." Other options I only message "waiting for the device" but there was nothing happen then.
I researched for the flashing the phone from beginning again but it seems nothing works for the bricked phone.
Click to expand...
Click to collapse
Pull the battery, wait 10 seconds. Put battery back in and press Vol. Down, Home (Middle button) and Power until you see a warning come on the screen. Press Up and you should see a picture of an Android with "Downloading" and "Odin Mode" in the upper left corner.
Once here try flashing via Odin again. If it's really a Sprint Note 2 I still suggest the MC2 Unrooted Restore to give yourself a clean slate.
garwynn said:
Pull the battery, wait 10 seconds. Put battery back in and press Vol. Down, Home (Middle button) and Power until you see a warning come on the screen. Press Up and you should see a picture of an Android with "Downloading" and "Odin Mode" in the upper left corner.
Once here try flashing via Odin again. If it's really a Sprint Note 2 I still suggest the MC2 Unrooted Restore to give yourself a clean slate.
Click to expand...
Click to collapse
OK Here are what I did:
open toolkit at command window with many options and I have chosen options:
*** 17 for GSM model adroid 4.2.2
*** 25 for USA GSM model adroid 4.2.2
and even tried ***45 CDMA LTE model adroid 4.2.2 (when I tried I did notice some downloaded files on command window and this is the only activity I have notice in entire procedure but after file is downloaded it returned to main menu and nothing happened then.
When I choose option 17 or 25 or 45 I got into the same menu with many of fastboot , ADB mode... options. As I said I tried most of these but nothing works.
you said try flashing via Odin again. I tried to locate the MC2 Unrooted Restore but could not find it. Please advice. Thanks
abbuyacc said:
OK Here are what I did:
open toolkit at command window with many options and I have chosen options:
*** 17 for GSM model adroid 4.2.2
*** 25 for USA GSM model adroid 4.2.2
and even tried ***45 CDMA LTE model adroid 4.2.2 (when I tried I did notice some downloaded files on command window and this is the only activity I have notice in entire procedure but after file is downloaded it returned to main menu and nothing happened then.
When I choose option 17 or 25 or 45 I got into the same menu with many of fastboot , ADB mode... options. As I said I tried most of these but nothing works.
you said try flashing via Odin again. I tried to locate the MC2 Unrooted Restore but could not find it. Please advice. Thanks
Click to expand...
Click to collapse
Let's skip the toolbox for a moment.
1) Download this file:
http://www.rwilco12.com/Files/Devic...rooted/SPH-L900_MC2_1090526_Stock_Restore.exe
2) Open it. It will unpack another EXE in Odin-OC.
3) Set phone into Odin mode as previously posted.
4) Connect USB cable to PC, open EXE in Odin-OC folder.
Once shows connected, click Start.
That should get you going. If you still have problems let me know.
garwynn said:
Let's skip the toolbox for a moment.
1) Download this file:
http://www.rwilco12.com/Files/Devic...rooted/SPH-L900_MC2_1090526_Stock_Restore.exe
2) Open it. It will unpack another EXE in Odin-OC.
3) Set phone into Odin mode as previously posted.
4) Connect USB cable to PC, open EXE in Odin-OC folder.
Once shows connected, click Start.
That should get you going. If you still have problems let me know.
Click to expand...
Click to collapse
Cool. Thank you very much. You are really big help. Just restored the phone back to the Original Sprint android version 4.1.2 Hard ware version L900.09. It works perfect now but this phone was modified to use with GSM carriers (it got sim card lot) so I guess I will have to flash it. What should I do next. I prefer to AT&T or Tmobile.
I was unrooting my phone and I must've skipped a few steps but now my phone is bricked I guess. All I can do at the moment is get into the bootloader but whenever I try and flash anything (recovery,roms etc) I don't permission since I locked my bootloader (it said in a tutorial.. whoops). I tried to follow the unbricking guide here on XDA but it tells you to install weird qualcomm drivers and whenever I try and apply it to my device in device manager it just says that it's not compatible with my device.
So yeah, my bootloader is locked but I need to flash a recovery to get me out of this mess, what do I do?
Have you tried fastboot oem unlock?
It "might" work even if the related setting (in Developer Options) is disabled.
After doing that, try to normally restore the stock firmware.
Ps note that you'll definitely lose all data
Simone98RC said:
Have you tried fastboot oem unlock?
It "might" work even if the related setting (in Developer Options) is disabled.
After doing that, try to normally restore the stock firmware.
Ps note that you'll definitely lose all data
Click to expand...
Click to collapse
Yeah but it just fails
edit- i'll retry the unbricking guide tomorrow
The guide still doesn't work for me, I'm just having problem with the drivers you're meant to use.
I posted on there my issue on more detail.
Update- I fixed it.
I wasn't going into proper recovery mode (I had to turn it off completely and hold volume while plugging in). Then, it popped up on device manager under USB and the drivers worked. Afterwards, I just followed the rest of the tutorial haha.