Android users need help with my phone! I am trying to manually turn on USB debugging (to access files on phone through update thru ADB mode in recovery options, I can install the driver for the phone but won't work until USB debugging is turned on) while my phone cannot boot into the OS. Is there a secret way to turn on USB debugging through recovery mode? (I do not want to wipe the data, and phone unfortunately is not rooted)
USB debugging has nothing to do with adb via recovery. It is an Android only setting. Recovery cannot use it and does not need it.
Adb doesn't work in stock recovery. I wrote a useful thread for people who are new to adb, as you are. You can get to it via the link in my signature. The thread is called "adb and fastboot. What isn't?".
It teaches you how to set it up and use it correctly.
Sent from my Nexus 5 using Tapatalk
rootSU said:
USB debugging has nothing to do with adb via recovery. It is an Android only setting. Recovery cannot use it and does not need it.
Adb doesn't work in stock recovery. I wrote a useful thread for people who are new to adb, as you are. You can get to it via the link in my signature. The thread is called "adb and fastboot. What isn't?".
It teaches you how to set it up and use it correctly.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
My main issue is that I am trying to retrieve my non backuped data on the phone and the phone itself will not boot into the Android OS.
I have looked into unlocking the fastboot/bootloader but it will wipe the data which would be pointless.
The data on the phone is more critical to me than the phone itself (and yes I was dumb enough to not back it up, didn't expect a flagship phone less than a year to crash on me, but I have learned for next time).
I am looking for any possible way to retrieve the data. I have tried to access the phone from the computer but I cannot access it since USB debugging is turned off and the phone is not rooted or doesn't have any other modifications.
Is there any way at this point I can retrieve the data off the phone with a non bootable OS and locked and stock Android OS?
Y is it non bootable?
Sent from my Android 5.0 Nexus 5
You are stuck. Stock recovery, locked bootloader, and OS will not boot. As RootSU mentioned, USB debugging has nothing to do with this. Stock recovery will not connect to adb.
Unless you can get the phone to boot looks like data is lost. Sorry.
Yoda8232 said:
Is there any way at this point I can retrieve the data off the phone with a non bootable OS and locked and stock Android OS?
Click to expand...
Click to collapse
No.
Yoda8232 said:
didn't expect a flagship phone less than a year to crash on me
Click to expand...
Click to collapse
Expect it from every electronic device. Especially expensive and complicated ones.
So I actually had warranty left from Google (bought directly from Google) and was going to RMA it but I decided not to because the data on there is important to me and worth more than the phone itself (yes I should of backuped everything but oh well what can I do now). And I bought a new phone so this Nexus 5 will be my little side project to try and revive it; somehow.
I will try to keep going at it, I have small programming/coding skills but it would be nice to find a way to open up the USB debugging option on the locked stock phone somehow that doesn't bootup.
Any suggestions on where I should start to start testing different "procedures"?
Related
Hi folks. I've tried searching on this subject and looks like every thread I've seen on this site related to a stuck Google screen was the result of trying to root the device. My situation is different. I have a stock phone given to me by Google (I'm a former Googler) and up until recently the phone started to go awry whenever I had to reboot it. It would stay stuck at the Google logo. I've tried recover, clearing the cache and also factory wipe and it will always restart and get stuck at the logo. I've found some threads on Google's support forums that mention it may be hardware related with faulty memory being the issue. I'm trying here as a last resort.
The phone is the regular Nexus S 3G for Tmobile. Please help before I smash this phone into the wall.
I'd try rooting and installing a custom rom. If it works after that and you want it to be stock again you could just reverse the process. If none of that works then I'm guessing it's similar to the other phones with hardware problems.
ex-googler said:
Hi folks. I've tried searching on this subject and looks like every thread I've seen on this site related to a stuck Google screen was the result of trying to root the device. My situation is different. I have a stock phone given to me by Google (I'm a former Googler) and up until recently the phone started to go awry whenever I had to reboot it. It would stay stuck at the Google logo. I've tried recover, clearing the cache and also factory wipe and it will always restart and get stuck at the logo. I've found some threads on Google's support forums that mention it may be hardware related with faulty memory being the issue. I'm trying here as a last resort.
The phone is the regular Nexus S 3G for Tmobile. Please help before I smash this phone into the wall.
Click to expand...
Click to collapse
have you tried manually flashing the stock signed by google rom through your stock recovery yet? it sounds like it got corrupted or has some corrupted data. id try to manually flash it.
aliiasgar said:
I'd try rooting and installing a custom rom. If it works after that and you want it to be stock again you could just reverse the process. If none of that works then I'm guessing it's similar to the other phones with hardware problems.
Click to expand...
Click to collapse
I can't seem to root it. I've installed the adb drivers and windows detects it whenever I plug the USB in, but I can't unlock it to root it. When I run this command, "fastboot oem unlock" it just keeps trying to detect the phone but never does. I think it's because USB debugging isn't enabled and I can't enable it without being able to get back into the phone.
ex-googler said:
I can't seem to root it. I've installed the adb drivers and windows detects it whenever I plug the USB in, but I can't unlock it to root it. When I run this command, "fastboot oem unlock" it just keeps trying to detect the phone but never does. I think it's because USB debugging isn't enabled and I can't enable it without being able to get back into the phone.
Click to expand...
Click to collapse
you need the nexus s drivers go to the pdanet website http://junefabrics.com/android/ and download and install the free version on your desktop. then follow the on screen instructions and it will install the drivers for you. thats the easiest way to install the drivers.
simms22 said:
you need the nexus s drivers go to the pdanet website and download and install the free version on your desktop. then follow the on screen instructions and it will install the drivers for you. thats the easiest way to install the drivers.
Click to expand...
Click to collapse
I've already installed that. It won't detect the phone properly because I can't enable the USB thing within the android OS since I'm blocked from fully loading up the phone.
It sounds like the sdcard memory won't mount. This is a hardware issue.
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
It sounds like the sdcard memory won't mount. This is a hardware issue.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
That's interesting you say that because I do notice an error during recovery and selecting data wipe. I had a colleague in the android dept tell me it's most likely bad flash memory.
"E:format_volume: make_extf4fs failed on /dev/block/platform/s3c-sdhci.0/by-name/userdata"
I'm gonna call Samsung tomorrow.
hi there.
maybe I am using wrong words but I cannot find any post similar to my subject.
I am on stock ICS but it is not working well - I wanted to downgrade, but it looks like it is not possible to downgrade on stock recovery. I know I have to change the recovery to sth else like ClockWork.
I know about fastboot way - and here my problems starts.
I have all the drivers, phone is visible in Device Manager while it is booten into Android. I can go into Fastboot mode BUT
when phone is in fastboot mode it is not visible in Windows Device Manager at all.
It is not a driver problem. There is no new device I can use the driver for.
I tried different computers. Win7 64bit and 32bit and WinXP 32bit
My phone does not show up on any of them.
I think it ia a problem with the bootloader - my current version is XXKL1 - as when I am in the fastboot mode my volume keys are not working, while they work perfectly well in recovery or in the OS.
Any ideas appreciated.
Cheers
My phone wasn't showing in w7 i had turn on usb debugging in settings -> developer options. I m not sure if this helps but might be worth a try
Sent from my Nexus S using Tapatalk
Thx gm'
It is not an issue for me to connect to Windows when I am booten into android.
Only when I am in fastboot mode the phone is not discovered by windows - and in fastboot mode thre is no USB debbuging - but thx anyway
..
vstar said:
Thx gm'
It is not an issue for me to connect to Windows when I am booten into android.
Only when I am in fastboot mode the phone is not discovered by windows - and in fastboot mode thre is no USB debbuging - but thx anyway
Click to expand...
Click to collapse
Know what u mean.
Windows finds u phone but not in recovery mode.
Download pdanet for android and this will solve ur problem buddy.
http://junefabrics.com
I just realize that what I done a while ago.
You don't need install pdanet app on ur phone as long u have drivers u might get some errors if u press not install but will work anyway.
Hope this will help.
Sent from my Nexus S using Tapatalk
XXK1 sounds like the baseband/radio to me. Granted I never actually looked in the bootloader for a model number. You sure that's not the radio?
What rom is on the phone now? Does it work? Are you rooted? If you got working phone with root you can flash custom recovery from inside the os. Boot directly into it via terminal or adb or any app that does it.
The volume buttons not working sounds odd and does worry me though
did you try to boot into bootloader/fastboot without being connected to any machine (holding vol up + power) to check if your volume keys work or not?
your issue might not be driver related, but you can always try if the test above was ok.
http://forum.xda-developers.com/showthread.php?t=1138755
best of luck
OK guys. I am on 4.0.3 stock. Works almost fine. This phone is unlocked but not rooted. So no chance for any other recovery but the stock one as far as I know. So I am not able to downgrade easily. Yes I can boot into fast boot without being attached to USB. Volume keys still not working here. But working in recovery mode no problem. GM no drivers will help if phone does not show in windows device menadzer at all. I have tried Linux approach but it looks phone is not being discovered there in fast boot mode as well. I have tried unbrick software - does not discover the phone.
And yes it says on fast boot screen boot loader : I9020XXK1
I have run out of ideas.
Downgrade would be best but how to put any recovery manager without root privileges
Sent from my Nexus S using XDA App
you can use ROM manager to jump back to 2.3.x
..
I am not rooted so I cannot use from manager and I do have stock recovery not clockwork so I cannot install superuser.zip
Sent from my Nexus S using XDA App
And for SuperOneClick phone needs to be visible in fastboot mode.
Sent from my Nexus S using XDA App
vstar said:
And for SuperOneClick phone needs to be visible in fastboot mode.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
for SuperOneClick phone needs to be visible in usb debugging mode.
Sorry mate but it only starts in USB Debug/Android mode - then it reboots the phone to fastboot shell and then same issue - phone is not discovered by windows hence nothing else happens.
Is there no other way of gaining root access instead of fastboot option - this would solve all my pains
Thx everyone for input
..
i suggest just follow zedomax tutorial on how to root your ics phone. He also have the download links for all the files that you will need. once your phone is rooted then you can download the old stock version of your phone.
http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/
Looks like a driver issue, when phone isn't discovered by windows in fast boot mode. (You are booting with vol up+power, right?)
Forget about any one-click-stuff etc - unlocking and cwm is the way to go. Everything else just makes troubles.
What I don't get is how you unlocked your phone without fastboot working?! That's not possible... for the moment forget about rooting - superuser isn't needed to flash stuff via fastboot/cwm.
Concentrate on getting fastboot to work. After that it's a piece of cake. Check you have drivers and fastboot set up properly on your PC.
Edit:
By this I mean following the sticky-guides, using the sdk from Google (not any downloads pretending to make it quick'n'easy. Go the official way!)
You should also give the 4.0.4-stockrom (ported from ns4g-leak) a try - it's way better than 4.0.3!
Edit: talking about this one: http://forum.xda-developers.com/showthread.php?t=1474878
OK guys - I have no idea how should I say it in different way - this is not a matter of a driver - the phone is physically not visible to the computer. There is no unknown device of anykind so I have nothing to use a driver for. It is not that fastboot command does not recognize the phone - the phone does not exists in Windows Device Manager. Looks like when phone is in fastboot mode the usb port is dead. So no chance of rooting in standard way.
And I have unlocked it as it was working before. I did realize it is not working when I tried to downgrade recently.
Election Day: I have tried 3 different cables, couple of computers and 3 different operating systems - ubuntu included. How this trick with hairdrier works? If it is a flash why does it work for everything else but not fastboot mode? Should I heat it up without cover and battery? Any specific area? Should I plug in while hot?
Thx guys.
usb working with sys booted up, but broken on bootloader?! makes no sense at all, i hope you can see that for yourself. can't be a hw-failure (then it would be broken everywhere).
have you reinstalled the driver from the sdk? the problem is on your pc, not the phone...
and forget about rooting for the moment, you don't need that to flash a rom. or are you mixing things up?!
that nonsense about heating up the phone with a hair drier was a joke, right?
..
Hi all,
I've got a Nexus S 4G CDMA Sprint phone running Stock ICS 4.0.4 IMM76D.
My bootloader is unlocked from previous roots and whatnot.
My problem is that my phone is not being recognized by my computer at all. We're talking complete nonrecognition. No yellow triangle in device manager, no pop-ups, nothing. This phone will just not be read by my computer! I've tried different cords, different computers, re-installation of drivers after resetting my computer, installed PDA net, did a factory reset on the phone, I've literally been on Google for hours upon hours upon hours trying to figure this out and can't figure out why the computer is not recognizing the phone and why the phone is not allowing me to put it into usb mounting. It is however, charging via the computer and wall plug. I can get into stock 3e android recovery, fastboot using V-Up and Power and I can get it into download mode. It is NOT recognized in any modes by the computer nor other computers including my Linux box. The phone states that the usb control initializes but then ends a moment later. I am thinking this is a hardware issue but that leaves me with two issues:
If I was to go to Sprint to have it fixed they would realize my bootloader was unlocked thus voiding the warranty and I'd feel like quite an idiot at the store
If it is hardware related why is the charge working on the device.
I have also tried to bend up the usb plate to make it touch the pins better but that did not help at all. I am at my wits end and really need some help here, I've done everything I could find on Google and here plus more. I want to just return it but with the bootloader unlocked this is really not a possibility. I am looking for help to either become able to lock the bootloader without it having to be connected via the computer so I can then get it fixed if it is hardware related or if I can get the darn thing to be read by the computer once more. so yea, this is where I am at and I would appreciate it so much if someone could help me out, thanks guys!!!
Wireless adb in playstore should help.
Sent from my Nexus S 4G using XDA
That would be perfect! Only problem is that it requires root access on the phone which I am unable to obtain because I cannot access the phone. Is there a way to root the phone without having to connect it via the computer? Something like an update.zip with files able to be flashed through android recovery 3e? If I can get root access than wireless adb would be perfect.
*ultimately if I could remove signature checking in Android Recovery 3e that would work so I could in turn try to root the phone and install a different recovery to then try a different rom to see if that in turn fixes the issue.
Ebicoustic said:
That would be perfect! Only problem is that it requires root access on the phone which I am unable to obtain because I cannot access the phone. Is there a way to root the phone without having to connect it via the computer? Something like an update.zip with files able to be flashed through android recovery 3e? If I can get root access than wireless adb would be perfect.
*ultimately if I could remove signature checking in Android Recovery 3e that would work so I could in turn try to root the phone and install a different recovery to then try a different rom to see if that in turn fixes the issue.
Click to expand...
Click to collapse
You might be able to download your rom of choice and rename it update.zip. I'm not sure if it will flash though....someone else chime in if I'm wrong. You can use wireless file transfer if needed.
Sent from my Nexus S 4G using XDA
Yea I've tried that, everything gets shot down by the recovery with a E:Signature Verification Failed. Thank you for your help so far but I don't think this is something that is going to be helped. I've put in a ticket to Samsung for a repair under it's warranty. In the past I've sent in a rooted phone and they've fixed it so I think I'm going to give that a shot. Just don't want to be without a phone for 2+ weeks.
Well good luck...you are running stock unrooted so it shouldn't matter. It is a dev phone for damn sake. Sorry couldn't help.
Sent from my Nexus S 4G using XDA
Well if you want to download a custom rom... Since you are on this forum. Download any rom (preferably CM9 since its quite good from my experience). Flash the stable version and wait till everything is completed. Now when you flash make sure you download a recovery...eg ClockWorkMod Recovery from google market. You should now have a custom rom installed and download wireless adb as chappy said. See if that works
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Use this guide to recover your device.
Thanks, but my issue is that I can't install the drivers, could it be a windows 8 thing?
Everything seems to require that I enter USB debugging first, which is impossible for me now.
I think the ADB driver is impossible to install, unless I can do it over CWM, and every fastboot driver I've tried has failed too.
How did you erase everything? Was it through fastboot or CWM?
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
maxmalynowsky said:
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
Click to expand...
Click to collapse
In my opinion, its safer to erase everything from fastboot.
If fastboot recognizes your phone, then you can erase or install whatever you want.
If fastboot does not recognize your phone, then you can't erase it. You then need to find out why. Bad drivers, wrong folders, bad usb cable...In the meantime you phone will still work.
On my windows 7 box, under the administrator account, it took a while to set up the drivers, don't know why, but windows would not take it at first.
Maybe you can mail the phone to a xda member to get it going again...
maxmalynowsky said:
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Click to expand...
Click to collapse
I am sorry to hear about your phone. You are not alone I did the exact same thing a few days ago. Don't beat yourself up I have done that enough for both of us. Through my research into this i found there a few things that you might try (I don't own a PC so I haven't yet)
To get the drivers, I read a couple people had success downloading PDANet and installing them that way. I think they are located in "legacy drivers"
From the original "root, un-root" thread for your model download the stock boot img and try to flash that using ADB
follow the instructions to un-root and start over with rooting.
I also was going to look into Wug's toolkit (in the dev section) it looks like that may be an easy option to flash a working boot and recovery img.
I hope this helps please let me know.
I gave up to quick and ordered a GNex but I'm not touching that until I get my NS4G sorted out (my faith in my abilities is shaken and I could not handle bricking a brand new phone). I will be going to a friends house tonight to use their PC and try to get my NS running. I will be back to let you known what works and what doesn't. If you try or find anything would you please post? Two heads working on this issue are better then one. Thanks and good luck.
Sent from my temp PC36100 while my Nexus is sick using Tapatalk 2
*** success ***
The solution was an easy one thanks to our developers, the hard part was finding the answer and of course, beating myself up for making the mistake in the first place. Here's what you do...
Leave your phone with the battery out for a while. Download "Wug's Nexus Toolkit" In found it in the NS4G dev section but I believe it covers all variants (not sure which you have) at the select your model and custom JB ROM download the drivers (from the actual toolkit) turn on, plug in and select flash stock img, relock boot loader, pick the stock ROM you want and press go and your phone will be flashed and reboot in under a minute. Sign in on your phone (the toolkit should auto populate your new ROM and then just follow the steps to unlock, flash and install a custom recovery then pick any ROM you want and start over.
I really hope this helps you as I'm sure you find the whole situation as stomach-churning as I did. Please PM me and let me know.
If it does work please leave a thank you or donation to the dev for creating such an awesome tool. Again, good luck hope you get your nex back online.
Sent from my Galaxy Nexus using Tapatalk 2
The Nexus Toolkit was actually my first option, it's helped me out before. I went back and tried installing the drivers using the 3 options it gives. # 3 & #2, RAW and Samsung signed drivers don't work. Option #1, the PDAnet drivers didn't work last time I tried it (all 3 options require USB debugging enabled). However, I just tried #1 again by turning on the device in CWM and that seemed to work, but I'm not sure (installation went according to the guide). However, once I tried to flash stock img, it gave me errors about not being able to reach the device in fastboot. Can you elaborate on those two steps, driver installation and flashing? As soon as I can get fastboot to recognize my device I can pretty much take it from there. BTW, I've got a i9020A and using NRT 1.6.1; and what's the significance of leaving the phone with the battery out for a while?
Mine was in the box with the battery out overnight. When I had access to a PC and plugged it in it said something at the bottom of the fastboot screen in grey that it did not before and I actually think that was the trick (System normal or system OK or something like that and when replugged to the USB the message just repeated and stacked up on the lower left of the fastboot screen). Try letting the phone sit for a while. All driver options failed for me except the tool kit.
Sent from my Galaxy Nexus using Tapatalk 2
Tried your fix, but the phone remains unable to have it's drivers installed. It's always giving "USB device not recognized" errors no matter what I do. I'm just going to shelf it and accept my loss. Thanks for the help though!
edit: Tried using some Linux tools, much greater success! This guide finally got my device listed under fastboot: http://forum.xda-developers.com/showthread.php?t=1447040
edit2: Up and running again with the android-tools-fastboot package for Linux and a standard stock image flash: http://forum.xda-developers.com/showthread.php?t=1572307
I am so glad to hear it! I stayed subscribed to the nexus s forum just to keep up on your progress and to try and help. Good for you.
Sent from my Galaxy Nexus using Tapatalk 2
Hello everyone !
This morning, out of the blue (I think it was during a Whatsapp automatic backup), my Google Pixel 2 XL shut down. I can't get it started and the phone is stuck on the white screen with the Google Logo. I can access the bootloader and Recovery though, so that's something. I spent my whole day skimming through the forum and other websites/videos. but I only have a slight understanding of what is happening and I'm not sure where my problem lays. Now when I click on the Start option in the bootloader, it just starts back in the bootloader screen.
I've been a bad scholar and did not backup my data. So if there is a solution, I'd rather not factory reset my phone.
Got my phone a month ago.
I unlocked the bootloader and rooted the phone (Magisk).
Stock Rom
Today,
I tried to connect my phone to my computer but so far it is not recognised by my computer and I can't access OEM unlocking/usb modes.
I verified. I have the latest adb and fastboot version on my computer, dowloading the latest SDK platforms tools.
I downloaded the usb driver packages from the SDK manager.
I tried using an universal android adb driver tool.
I've used multiple usb-c to usb-c and usb-c to usb-a cables, on different ports.
I restarted my phone and computer multiple times (just to make sure)
My phone doesn't appear in the Device manager.
I am now completely lost and would really much appreciate your help.
Thank you for reading this. Thank you for helping me !
Sounds bad.....maybe in first instance try letting tge device shut off due to low battery. Maybe this helps to hard reset. So just leave it on in fastboot mode
donkeydances said:
Hello everyone !
This morning, out of the blue (I think it was during a Whatsapp automatic backup), my Google Pixel 2 XL shut down. I can't get it started and the phone is stuck on the white screen with the Google Logo. I can access the bootloader and Recovery though, so that's something. I spent my whole day skimming through the forum and other websites/videos. but I only have a slight understanding of what is happening and I'm not sure where my problem lays. Now when I click on the Start option in the bootloader, it just starts back in the bootloader screen.
I've been a bad scholar and did not backup my data. So if there is a solution, I'd rather not factory reset my phone.
Got my phone a month ago.
I unlocked the bootloader and rooted the phone (Magisk).
Stock Rom
Today,
I tried to connect my phone to my computer but so far it is not recognised by my computer and I can't access OEM unlocking/usb modes.
I verified. I have the latest adb and fastboot version on my computer, dowloading the latest SDK platforms tools.
I downloaded the usb driver packages from the SDK manager.
I tried using an universal android adb driver tool.
I've used multiple usb-c to usb-c and usb-c to usb-a cables, on different ports.
I restarted my phone and computer multiple times (just to make sure)
My phone doesn't appear in the Device manager.
I am now completely lost and would really much appreciate your help.
Thank you for reading this. Thank you for helping me !
Click to expand...
Click to collapse
Flash latest factory image (either 8.1 or DPx/P/9.0).
mrorange2108 said:
Sounds bad.....maybe in first instance try letting tge device shut off due to low battery. Maybe this helps to hard reset. So just leave it on in fastboot mode
Click to expand...
Click to collapse
I'm trying that. Thank you !
xFirefly93 said:
Flash latest factory image (either 8.1 or DPx/P/9.0).
Click to expand...
Click to collapse
Thank you for your answer. How would you do that ? I can't get it to be recognized by my computer.
donkeydances said:
Thank you for your answer. How would you do that ? I can't get it to be recognized by my computer.
Click to expand...
Click to collapse
Have you tried with the Fastboot protocol?
xFirefly93 said:
Have you tried with the Fastboot protocol?
Click to expand...
Click to collapse
Like I said, I can't get my phone to be recognized by my computer so no Fastboot protocol. I am not sure why it doesn't get recognized though.