• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root I think I messed up somewhere

KutuluKid

Well-Known Member
I am trying to flash the DU rom and GAPPS on my phone, I did the backups of the EFS and system data folders. Copied to PC. Then booted into twrp and did the Wipe and now I cannnot find the DU rom or my backup. Should I have put them in a certain folder? Can I put them back on the device after I wiped the data? I am kinda a noob, please be gentle guys and girls. I am kinda freaking out that i may have finally bricked a phone, even though I have read that this one cant be bricked. This is the nicest phone I have ever owned and I would hate myself if I screw the pooch on this one. Thanks in advance everyone.
 
It sounds like you did an internal wipe rather than just a data, cache, and dalvik wipe. The easiest way around this would be to adb push the roms from a computer to the device. Once that's done, you should be able to find them on twrp and flash them. If you don't have them already, download the rom and gapps to your computer and then connect the Nexus 5 to the computer while in twrp. If the computer recognizes the device as an adb device, you can use the command line to copy them to the device.

adb push path/to/file.zip /sdcard/file.zip
 
Yeah, I figured that much. So much for reading before proceeding huh. I am D/Ling the rom to the pc now.
 
Ok. So adb sideload on the phone, check. windows command prompt open. The first part after adb push should be the path of the zip on the pc right?
the second path should I put the file name of the zip at the end or leave it like you said
 
enabling adb sideload on the phone makes it look for an ota update. Just letting it sit on the main menu should be sufficient.

As for the the command, you are correct. Just make sure you do that for both the rom and gapps. Once both pushed to the phone, just flash the rom like normal.
 
I dont think my pc is recognizing the ADB sideload. I use the command prompt in windows or is this another program or shell?
 
it's a program ran from the command prompt in windows. If you don't have the sdk installed, you can grab our mini-sdk from here.

Extract the zip file, and then put the rom and gapps in the same folder. If you're not sure if you have the adb drivers installed, you can grab them here.
 
getting device not found if at main menu of twrp. I have the zip in the folder with the adb application so I am just typing the file name, should i type the full path? should i be using sideload instead of push ?
 
if you're getting device not found, it means adb can't find your device (likely drivers missing). If you use the command adb devices, it should return your serial number if it sees the device, or return nothing if it can't find it. If it doesn't see it, make sure the drivers for adb are installed.
 
OK, right. Yellow triangle in device manager. Install driver, Windows was unable to install your AOSP on HammerHead. hmm. Google USB Drivers right? D/L'd twice to make sure good driver. WTF? I feel like a moron here.
 
Nope same error. Ok so is it safe to turn off the phone at all? I was thinking about rebooting everything. New cables, etc. I don't know what to do from here, I did already wipe the phone, so just makes me nervous.
 
Depending on what you wiped, it may not boot (if you wiped system, it has nothing to boot into). If that's the case, it will likely get stuck at the Google splash page. Try a different port on the computer and see if that will allow proper installation.
 
Okay. I am going to leave this thing alone for a while and clear my head. I'll come back on a different laptop and try again.
 
First I'll have to get ADB to recognize the device, going to eat. I'll think better on a full stomach.
 
Are you using the mini or full SDK?
What is the whole file directory path to your ADB/fastboot folder on your PC?
You might need to try and install a different set of PC drivers, eg. Universal naked drivers, Google USB drivers or the LG united drivers.

If you still can't get adb/fastboot working, then I might suggest installing Wugfresh's tool kit and using his built-in driver program. You can go through all the drivers installed on the whole PC and you can use it to see what drivers are installed for the N5 and also uninstall any driver that is set for the N5 and then reinstall the drivers, all with his program. Works very well. Nexus Root Toolkit v1.8.6 | WugFresh

Edit:
For some reason, I've noticed that when I do a clean install of a ROM, my PC drivers usually have to be set up again.
 
Ok. Have the mini-sdk. Removed all associated drivers. Just tried the wug kit, installed google usb drivers, no luck.
 
I tried unistalling all associated drivers and reinstalled the google usb driver. No luck, used the wug kit and followed the directions as best as possible. I could not check the mtp part since I cannot disable/enable usb debugging. I even tried the universal drivers with no luck. If I disconnect and plug back in it autodetects and installs aosp on hammerhead driver. should i out recovery and try to install drivers in fastboot or something?
 
I tried unistalling all associated drivers and reinstalled the google usb driver. No luck, used the wug kit and followed the directions as best as possible. I could not check the mtp part since I cannot disable/enable usb debugging. I even tried the universal drivers with no luck.

Do you have an OTG cable and a card reader or thumb drive?
TWRP has OTG support.... Put the ROM and Gapps package on the thumb drive and connect it to your N5.
Is fastboot working?
 
Back
Top Bottom