Just after updating to lollipop I completly smashed my screen. It doesn't show any usefull information and touch is not working.
Since I'm not in the mood to buy a new screen because I already bought a Note 4, I wanted to pull the data from the phone. It's pin protected but fastboot is still working, adb however is not.
After reading up a bit I found that going into cwm recovery I would still be able to acces adb.
So I with fastboot I booted cwm recovery (fastboot boot recovery.img) only to find that adb still won't find my devices.
Is there any way left to pull the data from my phone? I also have acces to a external keyboard/mouse with a otg cable but that won't seem to work either.
Boot into recovery and with your device plugged into your pc go to device manager. Do you see your device there?
Sent from my Nexus 9 using XDA Free mobile app
In recovery it doesn't show up.
On a normal boot it does, only no files are showing because of the pin lock.
Wiisper said:
In recovery it doesn't show up.
On a normal boot it does, only no files are showing because of the pin lock.
Click to expand...
Click to collapse
Google 15 second adb install xda. It has drivers as well as sets up adb and fastboot on your pc which you'll need if you can get your device detected
Edit, also download the twrp image from here and boot into it fastboot boot twrp.img (use the full name of the twrp image file) cwm sucks. http://techerrata.com/browse/twrp2/hammerhead
Sent from my Nexus 9 using XDA Free mobile app
I think I got it working, I already had adb working but it wouldn't find the correct drivers for the nexus 5.
I tried to update the drivers from google but windows said that it didn't find any correct drivers for the devices so I had to get "naked drivers" from somewhere.
After that it showed up as galaxy nexus adb interface in the device managers and adb was able to find it.
It's now pulling all the data.
Thanks you for your help!
I will report back when it's done pulling.
Wiisper said:
I think I got it working, I already had adb working but it wouldn't find the correct drivers for the nexus 5.
I tried to update the drivers from google but windows said that it didn't find any correct drivers for the devices so I had to get "naked drivers" from somewhere.
After that it showed up as galaxy nexus adb interface in the device managers and adb was able to find it.
It's now pulling all the data.
Thanks you for your help!
I will report back when it's done pulling.
Click to expand...
Click to collapse
Np, glad it seems to be working
Sent from my Nexus 9 using XDA Free mobile app
Okay got all the files from the phone!
Thanks for helping.
Related
I was trying to root my Nexus S
I got to bootloader, flashed rootboot.img and clockwork. Now I'm stuck on the unlocked google reboot.
When I try mounting the sdcard via usb in clockwork I can't get it to show on my comp, so I can't drop the zip files in there to update the phone. I believe that's the last step I need to get my baby working again.
If this is the case do you have any suggestions on how I can get files in there? I thought there might be a fastboot command to move the files there but I can't seem to figure it out.
If not can you please point me in the right direction
I tried searching the forums for a solution but everything I come across does not seem to help my particular needs, I apologize if I missed the solution elsewhere but I'm at wit's end right now
All suggestions are greatly appreciated
Thanks!
I am almost having the same issue. I unlocked the bootloader and flashed recoverymod but was unable to locate the superuser zip file so I rebooted my nexus. When I tried to start over again and fastboot I'm getting an error with CMD saying its waiting for device. On the nexus when in fastboot mode at the very bottom it says fastboot failsomething or another.
Any suggestions as to how I can get fast boot working again?!
Sent from my Nexus S 4G using XDA Premium App
I'm obviously no pro! but from what I gather it sounds like your phone's not being recognized. I had that problem and this guide seemed to solve it so you might find it of some help
nexusshacks.com/nexus-s-hacks/how-to-install-nexus-s-windows-usb-drivers
Thanks, it can't be a driver issue though since I was able to use fastboot to unlock the bootloader. Although it sure does seem like its not connecting properly.
Sent from my Nexus S 4G using XDA Premium App
blahhhh you jinxed me. I just realized how to use ADP, figured it was the way to push the files I needed to SD card and now I'm getting your error. I'll reply with a solution if I find one, hope you do the same! two noobs are better than one after all!!
Yikes! Please do, it's driving me insane!
Sent from my Nexus S 4G using XDA Premium App
Fixed it, a simple battery pull fixed my problem. Rooted it this morning!
Sent from my Nexus S 4G using XDA Premium App
Think you can tell me what driver you're using? When I plug my phone in I see the following in the device manager
ADB Interface
SAMSUNG Android Composite ADB Interface
I tried your battery trick to no avail, I even had ADB running and tried the battery trick and it won't work
Also, fastboot is recognizing my device.
Any help would really be appreicated. it's day 3 with no phone now
I'm at work now till 9 and I'm in CA. Ill look it up when I get home. U have to DL the Google something or another driver in sdk. I remember 4 was at the end of it. Ill post when I get home.
Your phones not working at all?!
Sent from my Nexus S 4G using XDA Premium App
vintagetonez said:
I am almost having the same issue. I unlocked the bootloader and flashed recoverymod but was unable to locate the superuser zip file so I rebooted my nexus. When I tried to start over again and fastboot I'm getting an error with CMD saying its waiting for device. On the nexus when in fastboot mode at the very bottom it says fastboot failsomething or another.
Any suggestions as to how I can get fast boot working again?!
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
hi there
i'm trying to root my xperia x8 using superoneclick, ADB start OK.... waiting.... and i'm waiting more than 5 min i think.... but nothing happen...
-i've extracted/copied xrecovery into sd, phone browser but nothing happen.
- boot the phone and press "back <--" key multiple time.... but phone start as usual ...
can somebody teach me how or give link to show how to root step by step please...
i'm new here..... TT
-- sorry for english.... not my language..
yeah I just switched to the google android service 4 "something or other" not in the mindset to find it. My phone's working it's just in super retardo mode right now. All that's working is the bootloader screen and the clockwork orange screen. I've kind of abandoned all hopes of getting adb to work on it because I've tried EVERTHING (except for what will work). I'm trying to figure out how to get clockwork to work with my pc that way I can get files into the sdcard which is what I was trying to use adb for in the first place.
ps... can you send a pic of your homescreen? I miss mine
U don't need adb to transfer files to your nexus s. Make sure debugging is turned on and mount your SD. You should get a promt to transfer files to and from your device via comp. You can use cmd to transfer with fastboot. I just got home and haven't even downloaded anything for root other than free tethering so I'm not sure which app will allow screen shot capture.
Sent from my Nexus S 4G using XDA Premium App
I'm relatively sure debug is still on otherwise I would not have been able to do what I already did. what's the command to transfer files to sd via fastboot? I tried "push" but that did not seem to work.
Once you plug the phone in.and mount SD.windows will automatically recognize it and prompt what woulf you like to do. Just choose transfer files. Go to the file you want yo transfer and right click. Choose send to E. At least on my comp the nexus shows up as e drive so choose which one it shows up as.
Sent from my Nexus S 4G using XDA Premium App
Thanks for all your help, I really appreciate it. It seems the phone's not being recognized by the computer when I mount it. The drivers show up in device manager when I boot to bootloader but then disappear when I go into clockwork. So I never get a chance to see it in "computer" when I try mounting the sdcard. Any thoughts?
Hey folks.
I have been trying to get my wife's NS4G back to stock to get the JB OTA. I have downloaded all drivers multiple times on multiple computers (windows). I have tried 3 or 4 different USB cables. I have downloaded pdanet. I have downloaded the JAVA SDK and updated everything about it.
My computers cannot connect to the NS4G.
USB debugging is on. When I try to turn on tether, it tells me USB is not plugged in.
I have been able to restore the stock ROM (2.3.7) via CWM, but now I no longer have a recovery. It is still rooted and unlocked. Rom Manager is installed and it will not download CWM Recovery.
I need some way to get a recovery onto it. CMW or stock.
Does ANYONE have any suggestions?
Thanks in advance for all suggestions and particularly to the one that will work.
SemperFratres said:
Hey folks.
I have been trying to get my wife's NS4G back to stock to get the JB OTA. I have downloaded all drivers multiple times on multiple computers (windows). I have tried 3 or 4 different USB cables. I have downloaded pdanet. I have downloaded the JAVA SDK and updated everything about it.
My computers cannot connect to the NS4G.
USB debugging is on. When I try to turn on tether, it tells me USB is not plugged in.
I have been able to restore the stock ROM (2.3.7) via CWM, but now I no longer have a recovery. It is still rooted and unlocked. Rom Manager is installed and it will not download CWM Recovery.
I need some way to get a recovery onto it. CMW or stock.
Does ANYONE have any suggestions?
Thanks in advance for all suggestions and particularly to the one that will work.
Click to expand...
Click to collapse
If you are running Windows 7 hold down the shift key and right click then select open command prompt here. type ADB devices and if your drivers are installed then you will see your serial number. Remember to be in fastboot when you install drivers. then use ADB to reboot bootloader. when in fastboot type "fastboot devices" and you should again see your serial number to know that your drivers are all installed correctly. You need to fastboot flash a new recovery image. Hope that helps
ken3669 said:
If you are running Windows 7 hold down the shift key and right click then select open command prompt here. type ADB devices and if your drivers are installed then you will see your serial number. Remember to be in fastboot when you install drivers. then use ADB to reboot bootloader. when in fastboot type "fastboot devices" and you should again see your serial number to know that your drivers are all installed correctly. You need to fastboot flash a new recovery image. Hope that helps
Click to expand...
Click to collapse
Drivers are installed, as I can see my S3 fine as well as adb getting my serial number. The computer, nor adb, can see my NS4G. I have tried a desktop as well as 2 laptops.
Will be trying Vaelek's idea of wireless adb this evening.
Thanks for the suggestion.
Sent from my SPH-L710 (that's a Galaxy S3 to you) via tapatalk.
SemperFratres said:
Drivers are installed, as I can see my S3 fine as well as adb getting my serial number. The computer, nor adb, can see my NS4G. I have tried a desktop as well as 2 laptops.
Will be trying Vaelek's idea of wireless adb this evening.
Thanks for the suggestion.
Sent from my SPH-L710 (that's a Galaxy S3 to you) via tapatalk.
Click to expand...
Click to collapse
Drivers are NOT installed properly then. Drivers are installed on a per device basis. If your phone doesn't get recognized, then they are not installed.
Chances are your device ID isn't found in the .inf file of the drivers. I know back when I rooted my phone over a year ago I had to manually change the inf file and add my device.
If you start your phone in fastboot mode and plug it in, when you go in device manager you should see an unrecognized device with a yellow question mark. Right click it, then Properties, then Details tab. Give me the information in the Device Instance Path.
Will check this out and post info when I get home tonight. Thanks for the input.
Sent from my SPH-L710 (that's a Galaxy S3 to you) via tapatalk.
polobunny said:
Drivers are NOT installed properly then. Drivers are installed on a per device basis. If your phone doesn't get recognized, then they are not installed.
Chances are your device ID isn't found in the .inf file of the drivers. I know back when I rooted my phone over a year ago I had to manually change the inf file and add my device.
If you start your phone in fastboot mode and plug it in, when you go in device manager you should see an unrecognized device with a yellow question mark. Right click it, then Properties, then Details tab. Give me the information in the Device Instance Path.
Click to expand...
Click to collapse
Started phone in fastboot mode. Plugged it in and watched Device Manager. Closed device manager and re-opened it for a good refresh. I get nothing new. No unrecognized device and no Android Device like when I plug in my S3. ADB Wireless wont connect.
OK... I just cleared my sd card and was able to install CWM. One hurdle cleared...
I still need to get stock ROM and recovery. Is there anyway to do this WITHOUT being able to connect via adb?
Thanks again for any input.
Hey guys, semi-noob here. Here is the situation:
1) encrypted device yesterday (Nexus 5 w/ stock android 4.4.2 and CWM Recovery)
2) 4.4.3 came out, downloaded and installed (yee! new dialer)
3) restarted after install (so excited! :fingers-crossed
4) enter the bootloop
5) try to do fastboot -> recovery mode
6) nope. recovery mode = bootloop
What do, XDA? I searched the forums, and nothing seems to address this. The N5 isn't even showing up on the devices list for my comp (W7 w/ ADB installed and ran before). I can't talk to it through my computer.
haloux said:
Hey guys, semi-noob here. Here is the situation:
1) encrypted device yesterday (Nexus 5 w/ stock android 4.4.2 and CWM Recovery)
2) 4.4.3 came out, downloaded and installed (yee! new dialer)
3) restarted after install (so excited! :fingers-crossed
4) enter the bootloop
5) try to do fastboot -> recovery mode
6) nope. recovery mode = bootloop
What do, XDA? I searched the forums, and nothing seems to address this. The N5 isn't even showing up on the devices list for my comp (W7 w/ ADB installed and ran before). I can't talk to it through my computer.
Click to expand...
Click to collapse
Hi.
Boot into bootloader
open cmd
Type fastboot devices
See if your device gets detected or not.
If yes..you can flash stock factory IMG.
If not make sure u have installed the drivers and adb set up is there.
Sent from my Nexus 5 using XDA Free mobile app
Vivek_Neel said:
Hi.
Boot into bootloader
open cmd
Type fastboot devices
See if your device gets detected or not.
If yes..you can flash stock factory IMG.
If not make sure u have installed the drivers and adb set up is there.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Hi,
Thanks for the quick response.
Win7 doesn't even detect the N5. Device manager doesn't even show that it exists (as android device or anything else). I've unplugged and replugged, no sound, multiple different ports.
Whatever you do don't use a toolkit try and fix it.If something else happens trying to diagnosis it would be very hard.Manual installation and fixing is the Best. Plus you learn how to get out of jams.
habitformer said:
Whatever you do don't use a toolkit try and fix it.If something else happens trying to diagnosis it would be very hard.Manual installation and fixing is the Best. Plus you learn how to get out of jams.
Click to expand...
Click to collapse
Will do (or won't do?). Thank you for the advice. Any tips on how to get my system to recognize the device?
So here are a list of things I've tried so far.
Verified that ADB works and is capable of recognizing an android device
Booted into fastboot and attached to 2 different computers (with no response or indication of the device on both)
Verified that ADB and all SDK software was up to date
Restarted computer to verify USB controller status
Refreshed device manager list before and after plugging in N5.
I'm at a loss. ADB was used in the past, the drivers are up to date. It's as though the N5 isn't even sending a signal to my computer that it's alive. I'm losing hope here guys. Please, someone help.
haloux said:
So here are a list of things I've tried so far.
Verified that ADB works and is capable of recognizing an android device
Booted into fastboot and attached to 2 different computers (with no response or indication of the device on both)
Verified that ADB and all SDK software was up to date
Restarted computer to verify USB controller status
Refreshed device manager list before and after plugging in N5.
I'm at a loss. ADB was used in the past, the drivers are up to date. It's as though the N5 isn't even sending a signal to my computer that it's alive. I'm losing hope here guys. Please, someone help.
Click to expand...
Click to collapse
I swear I went through this 2 days ago @scarmon25 will tell,we had a late night hangouts session.
I used a one of my many nexus cables and it finally linked up.Not to sound like a jerk but you've got USB debugging on right?
I reread your OP.If.you can get into recovery just restore a back up!!! Than all should be good.
haloux said:
So here are a list of things I've tried so far.
Verified that ADB works and is capable of recognizing an android device
Booted into fastboot and attached to 2 different computers (with no response or indication of the device on both)
I'm at a loss. ADB was used in the past, the drivers are up to date. It's as though the N5 isn't even sending a signal to my computer that it's alive. I'm losing hope here guys. Please, someone help.
Click to expand...
Click to collapse
One thing you haven't stated. Do you have the fastboot drivers installed? They're different from adb. Since you're not seeing the device after "fastboot devices", I would check and make sure.
habitformer said:
I swear I went through this 2 days ago @scarmon25 will tell,we had a late night hangouts session.
I used a one of my many nexus cables and it finally linked up.Not to sound like a jerk but you've got USB debugging on right?
I reread your OP.If.you can get into recovery just restore a back up!!! Than all should be good.
Click to expand...
Click to collapse
Yea, USB debugging was on. The recovery mode just yields the dead android.
adrman said:
One thing you haven't stated. Do you have the fastboot drivers installed? They're different from adb. Since you're not seeing the device after "fastboot devices", I would check and make sure.
Click to expand...
Click to collapse
How would I verify that? I assumed that fastboot drivers were installed bc I used them in the past.
Code:
fastboot devices
(yields)
No devices found.
I would do a search here for "windows fastboot drivers". I can't be of much help to you as I haven't used windows for several years now. Also, if you have a working Android device, see if it shows up when connected in bootloader mode as a test.
Sent from my Nexus 5 using Tapatalk
Small breakthrough:
Used a diff cable like someone suggested and my device appeared. Updated device driver and fastboot driver. ADB devices still yields no device attached though.
haloux said:
Small breakthrough:
Used a diff cable like someone suggested and my device appeared. Updated device driver and fastboot driver. ADB devices still yields no device attached though.
Click to expand...
Click to collapse
if you are in fastboot mode (or bootloader) you should use the fastboot command and not the adb.
type: fastboot devices
any signs of life?
Tapatalk-kal küldve az én Nexus 5-el
bitdomo said:
if you are in fastboot mode (or bootloader) you should use the fastboot command and not the adb.
type: fastboot devices
any signs of life?
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
Wow. It worked! The device showed up! Thank you guys.
haloux said:
Wow. It worked! The device showed up! Thank you guys.
Click to expand...
Click to collapse
Not sound like a turd but I mentioned using a nexus USB cable in post #7 after mentioning my issue.
Hello everyone,
I have done something utterly stupid with my Nexus 5, I wiped the internal storage and lost my roms, I really wasnt thinking.
I have tried looking at options like adb sideload but cant find a decent tutorial
Could I just get a micro usb to usb adapter and install a rom off that?
Would anyone be able to point me in the right direction with adb sideload?
Other problems are I can't get on the android SDK because the CMD box only flashes up.
Does the adb sideload option in TWRP actually do anything if you wait for it? Its been waiting for about 1 hour now and nothings happening.
Please guys any help is appreciated
osamarchie2000 said:
Hello everyone,
I have done something utterly stupid with my Nexus 5, I wiped the internal storage and lost my roms, I really wasnt thinking.
I have tried looking at options like adb sideload but cant find a decent tutorial
Could I just get a micro usb to usb adapter and install a rom off that?
Would anyone be able to point me in the right direction with adb sideload?
Other problems are I can't get on the android SDK because the CMD box only flashes up.
Does the adb sideload option in TWRP actually do anything if you wait for it? Its been waiting for about 1 hour now and nothings happening.
Please guys any help is appreciated
Click to expand...
Click to collapse
Why don't you flash the factory image using fastboot?
The Cmd box you are referring to happens because you need to navigate to that directory using Cmd and run it from there. You cannot just click it.
Thanks but I cant get the SDK to work at all. Im still looking into it but at the moment it wont work
Please somebody help me with the SDK, I dont know what else to do.
I cant open the SDK manager and I cant open it through eclipse either.
Someone else must have had this problem before
Click the link in my signature and then "adb and fastboot. What is it?"
This will help you configure adb properly. It also helps you learn commands. Like adb push.
adb sideload is the same as push but you type sideload instead.
FYI as much as people round here say it, there is no such thing as a soft brick. Its brick or not brick.
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
Switched off my phone and now I cant get it into recovery mode. Only the google logo which just stays there for ages
What do I do now?
osamarchie2000 said:
Switched off my phone and now I cant get it into recovery mode. Only the google logo which just stays there for ages
What do I do now?
Click to expand...
Click to collapse
Show down and don't panic. Your device is easily fixed. Hold the power button for 20 seconds. This will shut down the phone. Then press and hold the vol down then press the power button. That'll bring your into the bootloader.
Sent from my Nexus 5 using XDA Free mobile app
osamarchie2000 said:
Switched off my phone and now I cant get it into recovery mode. Only the google logo which just stays there for ages
What do I do now?
Click to expand...
Click to collapse
Power + volume down button brings you in the bootloader, from there go into recovery (navigate with volume buttons and select with power button)
In recovery follow this guide: http://forum.xda-developers.com/showthread.php?t=2559200.
Or flash the factory image in the bootloader. (that should work because you need to unlock your bootloader in fastboot)
Thanks guys,
It wasnt working because water damage had interfered with the volume buttons previously.
I have a micro usb to usb adapter now.
Can i put a rom on a USB drive and install that way?
Thanks guys
osamarchie2000 said:
Thanks guys,
It wasnt working because water damage had interfered with the volume buttons previously.
I have a micro usb to usb adapter now.
Can i put a rom on a USB drive and install that way?
Thanks guys
Click to expand...
Click to collapse
Yeah that will work too. Water damage is never good for a phone even if it stil works after that. But that's another story
osamarchie2000 said:
Thanks guys,
It wasnt working because water damage had interfered with the volume buttons previously.
I have a micro usb to usb adapter now.
Can i put a rom on a USB drive and install that way?
Thanks guys
Click to expand...
Click to collapse
Yes you can. You'll have to "tell" twrp where to find the rom zip.
Sent from my Nexus 5 using XDA Free mobile app
Only problem now is I cant get the SDK to work for my life. Ive spent 5 hours trying to fix my phone already today, I have the JDK installed. I open the eclipse thingy and when i try to open the SDK with eclipse it wont work either. Please somebody help with this
osamarchie2000 said:
Only problem now is I cant get the SDK to work for my life. Ive spent 5 hours trying to fix my phone already today, I have the JDK installed. I open the eclipse thingy and when i try to open the SDK with eclipse it wont work either. Please somebody help with this
Click to expand...
Click to collapse
You don't need the SDK. You're not developing here
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
TWRP cant find any of the files on my USB-OTG
with the CMD, it gives me my device and its serial number and says recovery for
C:\adb devices
but for C:\fastboot devices
I get nothing.
Any ideas please?
osamarchie2000 said:
with the CMD, it gives me my device and its serial number and says recovery for
C:\adb devices
but for C:\fastboot devices
I get nothing.
Any ideas please?
Click to expand...
Click to collapse
Did you read my thread that I told you to read?
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
osamarchie2000 said:
with the CMD, it gives me my device and its serial number and says recovery for
C:\adb devices
but for C:\fastboot devices
I get nothing.
Any ideas please?
Click to expand...
Click to collapse
Here's a hint, read rootSU's sticky rollup and look for the 15 second fastboot adb installer.
Sent from my Nexus 5 using XDA Free mobile app
Very sorry, Ive just re-read what Im looking for
Appologies
thankyou all, phone is well and good and im on CM11.
Thanks guys, anyone who helped is the best
Hi all,
Before explaining what the problem is, I want to state I have searched Google, XDA and various other websites to solve it myself. I do know the #1 rule of XDA
Today I've tried to use ADB Sideload to install a rom on my Nexus 5. I've done this before one time, when I accidentally formatted my entire phone, and it worked. Currently my phone is in TWRP Recovery, and ADB does recognize my phone when I type in 'adb devices' in the command prompt. However, when I click ADB Sideload on TWRP to sideload the rom from my laptop, the phone disconnects from my laptop (I hear the 'ding' from Windows), and I can't sideload anything at all.
I did update all possible drivers (ADB and Google), tried all USB-ports available, and even tried another laptop, but nothing worked.
Can you guys help me out, or provide new information about the issue?
Thanks in advance
With your device connected to your pc and booted into to twrp, go to device manager on your pc. Do you see an icon with a yellow exclamation mark? If so go to where you can choose from a list on your computer. Choose Android adb composite driver.
Sent from my Nexus 9 using XDA Free mobile app
Or just scrap off adb. Download stock img's from Google and fastboot em in bootloader to get your phone up and running again
Sent from my Nexus 5 using Tapatalk
jd1639 said:
With your device connected to your pc and booted into to twrp, go to device manager on your pc. Do you see an icon with a yellow exclamation mark? If so go to where you can choose from a list on your computer. Choose Android adb composite driver.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
So far I did this, and ADB finally allows my phone and laptop to sideload files (so thanks a lot). I did install two seperate roms at two seperate moments via sideload, but after booting up and showing the 'android' logo for a couple of minutes, the screen stays black (for both roms). I know the first boot takes a while, but this never happened to me before, and the phone won't start up anything further. Any new ideas?
Edit: tried it again with a third rom, and this one does install completely (Cataclysm, with AROMA). Even my laptop recognizes my phone and automatically starts Dropbox, but the screen stays black. Did I kill my phone?
Ben36 said:
Or just scrap off adb. Download stock img's from Google and fastboot em in bootloader to get your phone up and running again
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Edit: it worked. I apparently followed the wrong tutorial, because it did flash it after all. Thanks!